CN109981414B - method for acquiring packet loss number between mpls network nodes - Google Patents

method for acquiring packet loss number between mpls network nodes Download PDF

Info

Publication number
CN109981414B
CN109981414B CN201910253140.2A CN201910253140A CN109981414B CN 109981414 B CN109981414 B CN 109981414B CN 201910253140 A CN201910253140 A CN 201910253140A CN 109981414 B CN109981414 B CN 109981414B
Authority
CN
China
Prior art keywords
message
lmm
lmr
value
mep node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910253140.2A
Other languages
Chinese (zh)
Other versions
CN109981414A (en
Inventor
李云龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fiberhome Telecommunication Technologies Co Ltd
Original Assignee
Fiberhome Telecommunication Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fiberhome Telecommunication Technologies Co Ltd filed Critical Fiberhome Telecommunication Technologies Co Ltd
Priority to CN201910253140.2A priority Critical patent/CN109981414B/en
Publication of CN109981414A publication Critical patent/CN109981414A/en
Application granted granted Critical
Publication of CN109981414B publication Critical patent/CN109981414B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • H04L43/0829—Packet loss
    • H04L43/0835—One way packet loss
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Abstract

The method is characterized in that the sending and receiving of the LMM message and the LMR message of the TMP, TMC and TMS layers are carried out between the first MEP node and the second MEP node, and the calculation of the packet loss number is carried out by respectively obtaining the TxFCf, RxFCf, TxFCb and RxFCb values in the TMP, TMC and TMS layers from the sent and received LMM message and LMR message. Because the same LMM and LMR data frame is used in the data transmission packet loss number of the three layers of TMC, TMP and TMS, in the process of transmitting the data from the first MEP node to the second MEP node once, the specific fields in the LMM and LMR messages at different moments are obtained: the numerical values of TxFCf, RxFCf, TxFCb and RxFCb can be calculated to obtain the packet loss number of TMC, TMP and TMS three-layer data transmission in one LMM and LMR message sending and receiving process through a specific formula, and the method is simple in process, easy to implement and high in accuracy.

Description

method for acquiring packet loss number between mpls network nodes
Technical Field
The invention relates to the field of network data transmission, in particular to a method for acquiring packet loss number between mpls network nodes.
Background
Multi-Protocol Label Switching (MPLS) networks are formed by connecting MPLS nodes in communication with each other through NNI ports (network-side ports) of various forms, customer services such as E1/T1, FE, GE, 10GE are accessed to the network through UNI ports (user-side ports), corresponding TMC (Transport MPLS Channel, circuit layer) is selected after being processed by a service layer, TMC of the same route is bound to TMP, and the services are transmitted through the NNI-side TMP tunnel. In the MPLS network, there are three network layers TMC, TMP, TMS.
Where TMC (T-MPLS Channel) provides T-MPLS transport network traffic paths, one TMC connection transports one customer service entity (comprising one single customer service or a group of customer services).
TMP (T-MPLS Path) providing transport network connection Path, one TMP connection transporting one or more TMC signals between the borders of the TMP domain.
TMS (T-MPLS Section), an optional TMS provides segment layer functions, providing OAM monitoring between two adjacent T-MPLS nodes. Since there is one-to-one between the TMS instance and the service layer path, it does not need a tag. Furthermore, the service layer path must be point-to-point.
The function of the Measurement of the packet Loss of the Mpls network (LM: Loss Measurement) is to realize the statistics of the packet Loss performance by sending a request OAM message to an opposite-end maintenance end point, receiving a response OAM message (LM message) of the opposite-end maintenance end point and calculating the counter values of the messages sent and received by the maintenance end point carried in the message. When the function works in an active mode, the function is realized through continuously detecting OAM messages. If the operation is in the on-demand mode, the OAM message is measured through special packet loss. The information carried by the special packet loss measurement OAM message includes: a special label, an OAM frame header (OAM type FT, version number, flag bit, etc.), a counter (the value of a local counter when the source MEP sends a packet loss measurement packet, the value of a local counter when the destination MEP receives a packet loss measurement packet, the value of a local counter when the destination MEP returns a delay measurement packet).
The above processes show that the existing TMC, TMP and TMS packet loss number test methods are complex, three different data test packets need to be designed separately between two MEP nodes for testing in the sending and receiving processes, so that the implementation is complex, and due to the need of three data packets in the sending and receiving processes for many times, the processes are prone to errors.
Disclosure of Invention
The invention aims to solve the problems that three different data test packets are needed to be designed to realize complexity and error easily in order to calculate the packet loss number of each layer of data transmission of two MEP nodes in the MPLS network, and aims to provide a calculation method of the packet loss number of each layer between MPLS network nodes.
Therefore, the invention provides the following technical scheme:
the invention provides a method for acquiring packet loss numbers of each layer between nodes of a mpls network, which is used for acquiring packet loss numbers of TMP, TMC and TMS layers in a data packet transmission process between two MEP nodes in the mpls network, and is characterized in that the LMM messages and the LMR messages of the TMP, TMC and TMS layers are transmitted and received between a first MEP node and a second MEP node, and TxFCf, RxFCf, TxFCb and RxFCb values in the TMP, TMC and TMS layers are respectively acquired from the transmitted and received LMM messages to calculate the packet loss numbers;
sending and receiving an LMM message and an LMR message between a first MEP node and a second MEP node, wherein chip custom message headers of the LMM message, the LMR message and an OAM message of a TMP layer have the same encapsulation, and TxFCf, RxFCf, TxFCb and RxFCb values of the TMP layer of the LMM message and the LMR message at T1 and T2 are obtained;
the method comprises the steps that LMM messages and LMR messages are sent and received between a first MEP node and a second MEP node, chip custom message headers of the LMM messages, the LMR messages and OAM messages of a TMC layer are packaged in the same mode, and TxFCf, RxFCf, TxFCb and RxFCb values of the TMC layer at T1 and T2 of the LMM messages and the LMR messages are obtained;
sending and receiving an LMM message and an LMR message between a first MEP node and a second MEP node, wherein chip custom message headers of the LMM message, the LMR message and an OAM message of a TMS layer have the same encapsulation, and TxFCf, RxFCf, TxFCb and RxFCb values of the TMS layer of the LMM message and the LMR message at T1 and T2 are obtained;
wherein the content of the first and second substances,
for TMP layer
When the sent OAM message is an LMM message, taking the sending counter value of the service layer LSP of the first MEP node as the value of TxFCf;
when the second MEP node detects that the received OAM message is an LMM message, taking the receiving counter value of the service layer LSP of the second MEP node as an RxFCf value;
when the sent OAM message is an LMR message, taking the sending counter value of the service layer LSP of the first MEP node as the value of TxFCb;
when the second MEP node detects that the received OAM message is an LMR message, taking the receiving counter value of the service layer LSP of the second MEP node as the RxFCb value;
for TMC layer
When the sent OAM message is an LMM message, taking the sending counter value of the service layer PW of the first MEP node as the value of TxFCf;
when the second MEP node detects that the received OAM message is an LMM message, taking the receiving counter value of the service layer PW of the second MEP node as an RxFCf value;
when the sent OAM message is an LMR message, taking the sending counter value of the service layer PW of the first MEP node as the value of TxFCb;
when the second MEP node detects that the received OAM message is an LMR message, taking the receiving counter value of the service layer PW of the second MEP node as the RxFCb value;
for TMS layer
When the sent OAM message is an LMM message, taking the sending counter value of the logic port of the service layer of the first MEP node as the value of TxFCf;
when the second MEP node detects that the received OAM message is an LMM message, taking the receiving counter value of the logic port of the service layer of the second MEP node as an RxFCf value;
when the sent OAM message is an LMR message, taking the sending counter value of the logic port of the service layer of the first MEP node as the value of the TxFCb;
and when the second MEP node detects that the received OAM message is an LMR message, taking the receiving counter value of the logic port of the service layer of the second MEP node as the RxFCb value.
The method for acquiring the number of lost packets of each level between the nodes of the mpls network provided by the invention can also have the characteristics that the lost packets are obtained according to a formula
The remote packet loss is | TxFCf [ T2] -TxFCf [ T1] | - | RxFCf [ T2] -RxFCf [ T1] |,
the number of near-end lost packets is | TxFCb [ T2] -TxFCb [ T1] | - | RxFCb [ T2] -RxFCb [ T1] |,
calculating the far-end packet loss number and the near-end packet loss number of the TMC, TMP and TMS layers,
wherein, TxFCf [ T2] is a TxFCf value obtained at a time T2, TxFCf [ T1] is a TxFCf value obtained at a time T1, RxFCf [ T2] is an RxFCf value obtained at a time T2, RxFCf [ T1] is an RxFCf value obtained at a time T1, TxFCb [ T2] is a TxFCb value obtained at a time T2, TxFCb [ T1] is a TxFCb value obtained at a time T1, RxFCb [ T2] is an RxFCb value obtained at a time T2, and RxFCb [ T1] is an RxFCb value obtained at a time T1.
The method for acquiring packet loss numbers of each layer between mpls network nodes provided by the present invention may further have a feature that, when the LMM message content received by the first MEP node is a management message, the OPCODE field in the LMM message is analyzed and the sending counter or the receiving counter of the corresponding service layer LSP is started for calculation.
The method for acquiring packet loss numbers of each layer between mpls network nodes provided by the present invention may further have a characteristic that, when the LMM message content received by the first MEP node is a management message, the method analyzes the OPCODE field in the LMM message and starts the sending counter or the receiving counter of the corresponding service layer PW for calculation.
The method for acquiring packet loss numbers of each layer between mpls network nodes provided by the present invention may further have a characteristic that, when the LMM message content received by the first MEP node is a management message, the method analyzes the OPCODE field in the LMM message and starts the sending counter or the receiving counter of the corresponding service layer logical port for calculation.
The method for acquiring the number of lost packets of each level between the nodes of the mpls network provided by the invention can also have the characteristic that the difference value between T1 and T2 is greater than or equal to 1 minute.
The invention has the following functions and effects: according to the method for acquiring the packet loss number of each layer among the mpls network nodes, because the same LMM and LMR data frame is used for testing the packet loss number of the data transmission of the TMC, TMP and TMS layers, in the process of transmitting the data transmission from the first MEP node to the second MEP node at one time, the method comprises the following steps of: the numerical values of TxFCf, RxFCf, TxFCb and RxFCb can be calculated to obtain the packet loss number of TMC, TMP and TMS three-layer data transmission in one LMM and LMR message sending and receiving process through a specific formula, and the method is simple in process, easy to implement and high in accuracy.
Drawings
FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present invention;
fig. 2 is a schematic step diagram of a method for obtaining packet loss numbers of each level between mpls network nodes according to an embodiment of the present invention;
fig. 3 is a schematic flow diagram of the LMM and LMR sending and receiving between the first MEP node and the second MEP node of the TMP layer;
fig. 4 is a schematic flow diagram of sending and receiving LMMs and LMRs between a first MEP node and a second MEP node of a TMC layer; and
fig. 5 is a schematic flow diagram of sending and receiving LMMs and LMRs between a first MEP node and a second MEP node on a TMS layer.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples.
The meanings of the acronyms mentioned in this example illustrate:
MPLS, Multi-Protocol Label Switching (MPLS), is a system for fast packet Switching and routing that provides network data traffic with the capabilities of destination, routing address, forwarding and Switching. More particularly, it has mechanisms for managing various different forms of communication flow.
MEP, Message Exchange Pattern.
LM, Loss Measurement, packet Loss Measurement.
TMC/TMP/TMS is English abbreviation of T-MPLS Channel, T-MPLS Path and T-MPLS Section, and Chinese is T-MPLS network vertical layering, namely a circuit layer (TMC: T-MPLS Channel), a Path layer (TMP: T-MPLS Path) and a segment layer (TMS: T-MPLS Section).
OAM, Operation Administration and Maintenance, operating Maintenance management protocol.
PTN, Packet Transport Network.
LMM, Loss Measure Message.
LMR, Loss Measure Response, Loss Measure recovery.
PDU, protocol Development Units, protocol data Unit.
NNI, Network to Network Interface, Network node Interface.
TP-OAM, MPLS-TP OAM is MPLS-TP (Multi-Protocol Label Switching Transport Profile, Multi-Protocol Label Switching Transport application) which carries out hierarchical management control on the original OAM and carries out hierarchical OAM, namely MPLS-TP operation management maintenance.
The OPCODE field, the most basic unit of program execution, namely the OPCODE.
LSP, Label Switching Path.
FPGA, Field-Programmable Gate Array, or Field Programmable Gate Array.
GAL, general Array Logic.
PW, Pseudo-Wire, pseudowire.
SPU, Synergistic Processing Unit, coprocessor.
Fig. 1 is a schematic view of an application scenario in an embodiment of the present invention.
The application scenario of the present invention is shown in fig. 1, and the method of the present invention is applied to a communication network composed of two or more MEP nodes to calculate packet loss data between a Device a and a Device B on a line in the network, and further calculate a packet loss rate of data transmission between two devices.
The LM is divided into a double-end LM mode and a single-end LM mode, and the method is an optimized measurement method based on an LM message (one type of OAM message) with three layers of double-end TMC/TMP/TMS to accurately measure the packet loss rate of each layer in the PTN network and meet the requirement of consistency
The LM has two kinds of OAM PDUs, namely LMM and LMR.
For the implementation of LM, the overview is as follows:
(1) the LM messages are not embodied in the chip custom headers. The chip directly analyzes the message format and directly prints the counter in the message static load designated field.
(2) Counters for TMC, TMP and TMS layers are all put into the message on the NNI side.
(3) Convention for the own station counter: all TP-OAM messages transmitted and received by the station are not counted in respective layer counters.
To sum up, the method for obtaining packet loss numbers of each layer between nodes of a mpls network in this embodiment is used to obtain packet loss numbers of TMP, TMC, and TMS layers in a packet transfer process between two MEP nodes in the mpls network, send and receive LMM packets and LMR packets of the TMP, TMC, and TMS layers between a first MEP node and a second MEP node, and obtain TxFCf, RxFCf, TxFCb, and RxFCb values in the TMP, TMC, and TMS layers respectively from the LMM packets and LMR packets sent and received to calculate the packet loss numbers.
In particular, according to the formula
The remote packet loss is | TxFCf [ T2] -TxFCf [ T1] | - | RxFCf [ T2] -RxFCf [ T1] |,
the number of near-end lost packets is | TxFCb [ T2] -TxFCb [ T1] | - | RxFCb [ T2] -RxFCb [ T1] |,
calculating the far-end packet loss number and the near-end packet loss number of the TMC, TMP and TMS layers,
wherein, TxFCf [ T2] is a TxFCf value obtained at a time T2, TxFCf [ T1] is a TxFCf value obtained at a time T1, RxFCf [ T2] is an RxFCf value obtained at a time T2, RxFCf [ T1] is an RxFCf value obtained at a time T1, TxFCb [ T2] is a TxFCb value obtained at a time T2, TxFCb [ T1] is a TxFCb value obtained at a time T1, RxFCb [ T2] is an RxFCb value obtained at a time T2, and RxFCb [ T1] is an RxFCb value obtained at a time T1.
Specifically, the TxFCf [ T2], TxFCf [ T1], RxFCf [ T2], RxFCf [ T1], TxFCb [ T2], TxFCb [ T1], RxFCb [ T2], and RxFCb [ T1] values corresponding to the three layers of the TMP, TMC, and TMS layers in the above formula are obtained through the following count values of the LMM packet and the corresponding fields in the LMR message graph in the transmission and reception processes of the first MEP node and the second MEP node, that is, the method for obtaining the number of packets lost in each layer between the nodes of the mpls network in this embodiment specifically includes the following steps S1 and S2.
Fig. 2 is a schematic step diagram of a method for obtaining the number of packets lost in each tier among mpls network nodes in the embodiment of the present invention.
Step S1, sending and receiving the LMM message and the LMR message of the TMP, TMC, and TMS layers between the first MEP node and the second MEP node, and obtaining TxFCf, RxFCf, TxFCb, and RxFCb values in the TMP, TMC, and TMS layers from the sent and received LMM message and LMR message, respectively. The specific step comprises the following three parallel sub-steps S1-1, S1-2 and S1-3.
And step S1-1, transmitting and receiving the LMM message and the LMR message between the first MEP node and the second MEP node, wherein chip self-defined message heads of the LMM message, the LMR message and the OAM message on the TMP layer have the same encapsulation, and TxFCf, RxFCf, TxFCb and RxFCb values of the TMP layer at the time of T1 and T2 of the LMM message and the LMR message are obtained.
Specifically, for the TMP layer:
when the sent OAM message is an LMM message, taking the sending counter value of the service layer LSP of the first MEP node as the value of TxFCf; when the second MEP node detects that the received OAM message is an LMM message, taking the receiving counter value of the service layer LSP of the second MEP node as an RxFCf value; when the sent OAM message is an LMR message, taking the sending counter value of the service layer LSP of the first MEP node as the value of TxFCb; and when the second MEP node detects that the received OAM message is an LMR message, taking the receiving counter value of the service plane LSP of the second MEP node as the RxFCb value. When the LMM message content received by the first MEP node is a management message, the OPCODE field in the LMM message is analyzed, and a sending counter or a receiving counter of a corresponding service layer LSP is started for calculation.
That is to say, in the interaction process of the first MEP node and the second MEP node performing LMM and LMR transmission and reception, the specific process includes LMM transmission, LMM reception, LMR transmission, and LMR reception.
Fig. 3 is a schematic flow diagram of the LMM and LMR transmitting and receiving between the first MEP node and the second MEP node of the TMP layer.
And LMM sending:
(1) and the message sent to the chip by the FPGA is encapsulated consistently with the chip custom message header of other TMP layer OAMs. The fields of 'TxFCf', 'Reserved for RxFCf in LMR' and 'Reserved for TxFCb in LMR' in the LMM message are set to zero. The consistent packaging is to make the messages the same as the FPGA messages in the existing MEP node device, so that the messages can be smoothly sent and transmitted, and the packaged ready-made message format has small change to the system, is convenient to debug and is not easy to make mistakes. The fields of 'TxFCf', 'Reserved for RxFCf in LMR' and 'Reserved for TxFCb in LMR' in the LMM message are set to zero in order to start a new cycle packet counting, and the obtained counting values are filled into the fields to ensure the accuracy of the counting process during the subsequent counting. The TxFCf is a 32-bit counter, and the value thereof is the service packet transmission counter value at the LMM transmission time, "Reserved for RxFCf in LMR" and "Reserved for TxFCb in LMR" indicate the standby value of these 4 bytes, and is generally regarded as 0 by default.
(2) After receiving the message with the D-Type of 1, the chip further analyzes the message to an OPCODE field. When the OPCODE is 0x2B, the transmission counter value of the service plane LSP is filled in the "TxFCf" field to obtain the count value of the corresponding TxFCf field. D-type ═ 1 means that the OAM management message processing process is entered, means that the received message is not a service message but a management message, and this fact needs to enter a special OAM state machine for subsequent processing of the relevant flow. When the field value of the OPCODE is 0x2B (0x represents a 16-ary system), that is, 43, the OAM message sent by the site is represented as an LMM message, where 0x2B is a signal flag used to indicate that the message is an LMM message.
(3) And sending a counter by the LSP collected by the LMM. Not to be taken into account by itself.
(4) And finishing the LMM sending.
LMM receives:
(1) the chip receives the LMM message from the line. The OAM frame of the TMP layer is recognized by LSP + GAL + ACH, and the OPCODE field is further parsed. And when the OPCODE is 0x2B, filling a receiving counter of the LSP corresponding to the service into a 'Reserved for RxFCf in LMR' field of the LMM message to obtain a count value of the RxFCf field. Similarly, when the field value of the OPCODE is 0x2B or 43, it indicates that the OAM message received by the site is an LMM message, where 0x2B is a signal flag for marking the message as an LMM message
(2) And transmitting the message to the FPGA according to a standard TMP OAM message format.
(3) The LMM collects the LSP receiving counter and does not count itself in the LSP receiving counter.
(4) And completing the LMM receiving process.
And LMR sending:
(1) the FPGA directly copies the 'TxFCf' and 'Reserved for RxFCf in LMR' fields of the LMM into corresponding bytes of the LMR (position stealing is not needed, and direct adoption is achieved).
(2) And the LMR message sent to the chip by the FPGA is encapsulated consistently with the custom message header of other TMP layer OAM frame chips.
(3) After receiving the message with the D-Type of 1, the chip further analyzes the message to an OPCODE field. When the OPCODE is 0x2A, the transmission counter value of the service plane LSP is filled in the "TxFCb" field to obtain the calculated value of the corresponding TxFCb field. D-type ═ 1 means that the OAM management message processing process is entered, means that the received message is not a service message but a management message, and this fact needs to enter a special OAM state machine for subsequent processing of the relevant flow. When the field value of the OPCODE is 0x2A, that is, 42, the OAM message sent by the site is denoted as an LMR message, where 0x2A is a signal flag used to mark the message as an LMR message.
(4) After the LMR collects the LSP and sends the counter, the LMR does not count the LMR into the counter.
(5) And finishing the LMR sending.
The LMR receives:
(1) the chip receives an LMR message from the line. The OAM frame of the TMP layer is recognized by LSP + GAL + ACH, and the OPCODE field is further parsed. When the OPCODE is 0x2A, filling a receiving counter of the LSP corresponding to the service into four bytes after "TxFCb" of the LMR message, which is called as "RxFCb" as the counter field, and obtaining a count value of the RxFCb field.
(2) Transmitting to FPGA according to standard TMP OAM message format
(3) After the LMR collects the LSP receiving counter, the LMR does not count the LMR into the LSP receiving counter
(4) And the FPGA analyzes the count values (TxFCf, RxFCf, TxFCb and RxFCb) of the four counters in the LMR message and reads the count values.
(5) The count values of the TxFCf, RxFCf, TxFCb, and RxFCb fields in the FPGA register are read twice at time T1 and time T2. The time interval between two times is greater than or equal to 1 minute.
(6) And finishing the LMR receiving process.
And step S1-2, the LMM message and the LMR message are sent and received between the first MEP node and the second MEP node, the chip self-defined message heads of the LMM message, the LMR message and the OAM message of the TMC layer have the same encapsulation, and TxFCf, RxFCf, TxFCb and RxFCb values of the TMC layer of the LMM message and the LMR message at the time of T1 and T2 are obtained.
Specifically, for the TMC layer, when the sent OAM message is an LMM message, the value of the sending counter of the service plane PW of the first MEP node is used as the value of TxFCf; when the second MEP node detects that the received OAM message is an LMM message, taking the receiving counter value of the service layer PW of the second MEP node as an RxFCf value; when the sent OAM message is an LMR message, taking the sending counter value of the service layer PW of the first MEP node as the value of TxFCb; and when the second MEP node detects that the received OAM message is an LMR message, taking the receiving counter value of the service layer PW of the second MEP node as the RxFCb value. When the content of the LMM message received by the first MEP node is a management message, the OPCODE field in the LMM message is analyzed, and a sending counter or a receiving counter of the corresponding service layer PW is started to perform calculation.
That is to say, in the interaction process of the first MEP node and the second MEP node performing LMM and LMR transmission and reception, the specific process includes LMM transmission, LMM reception, LMR transmission, and LMR reception.
Fig. 4 is a schematic flow diagram of the sending and receiving processes of the LMM and the LMR between the first MEP node and the second MEP node in the TMC layer.
The process flow is substantially identical to that of the TMP layer.
And LMM sending:
(1) and the message sent to the chip by the FPGA is encapsulated consistently with the chip custom message header of other TMC layer OAMs. The fields of 'TxFCf', 'Reserved for RxFCf in LMR' and 'Reserved for TxFCb in LMR' in the LMM message are set to zero. The consistent packaging is to make the messages the same as the FPGA messages in the existing MEP node device, so that the messages can be smoothly sent and transmitted, and the packaged ready-made message format has small change to the system, is convenient to debug and is not easy to make mistakes. The fields of 'TxFCf', 'Reserved for RxFCf in LMR' and 'Reserved for TxFCb in LMR' in the LMM message are set to zero in order to start a new cycle packet counting, and the obtained counting values are filled into the fields to ensure the accuracy of the counting process during the subsequent counting. The TxFCf is a 32-bit counter, and the value thereof is the service packet transmission counter value at the LMM transmission time, "Reserved for RxFCf in LMR" and "Reserved for TxFCb in LMR" indicate the standby value of these 4 bytes, and is generally regarded as 0 by default.
(2) After receiving the message with the D-Type of 4, the ingress disk chip further parses the message into the OPCODE field. When the OPCODE is 0x2B, the front-end chip needs to be informed to count the counter into the message. The fact that D-type is 4 means that an OAM management packet processing process is entered, means that a received OAM management packet is not a service packet but a management packet, and this fact needs to enter a special OAM state machine for subsequent processing of a related flow. When the field value of the OPCODE is 0x2B (0x represents a 16-ary system), that is, 43, the OAM message sent by the site is represented as an LMM message, where 0x2B is a signal flag used to indicate that the message is an LMM message.
(3) When the outgoing disc (front end) chip receives the message with D-Type 4, it further resolves to the OPCODE field. When the OPCODE is equal to 0x2B, the transmission counter value of the service plane PW is filled in the "TxFCf" field, and the count value of the corresponding TxFCf field is obtained.
(4) After the LMM finishes collecting NHI and sends the counter, the LMM does not count the LMM.
(5) And finishing the LMM sending.
LMM receives:
(1) the chip receives the LMM message from the line. And identifying that the OAM frame is a TMC layer OAM frame through the LSP + PW + ACH, and further analyzing the OPCODE field. And when the OPCODE is 0x2B, filling a receiving counter corresponding to the PW in a 'Reserved for RxFCf in LMR' field of the LMM message to obtain a count value of the RxFCf field. Similarly, when the field value of the OPCODE is 0x2B or 43, it indicates that the OAM message received by the station is an LMM message, where 0x2B is a signal flag used to mark the message as an LMM message.
(2) And transmitting the message to the distributed forwarding chip according to the standard TMC OAM message format, and reaching the back end SPUA through the forwarding plane, wherein the back end distributed forwarding chip is directly uploaded to the FPGA.
(3) And after the LMM collects the PW receiving counter, the counter is automatically increased by one.
(4) LMM reception flow is completed
And LMR sending:
(1) the FPGA directly copies the 'TxFCf' and 'Reserved for RxFCf in LMR' of the LMM into corresponding bytes of the LMR (position moving is not needed, and direct adoption is achieved).
(2) And the LMR message sent to the chip by the FPGA is encapsulated consistently with the custom message header of other TMC layer OAM frame chips.
(3) The message passes through the forwarding plane to reach the front-end SPU.
(4) After receiving the message with the D-Type of 4, the front-end chip further parses the message into an OPCODE field. When the OPCODE is 0x2A, the transmission counter value of the service plane PW is filled in the "TxFCb" field, and the calculated value of the corresponding TxFCb field is obtained. The fact that D-type is 4 means that an OAM management packet processing process is entered, means that a received OAM management packet is not a service packet but a management packet, and this fact needs to enter a special OAM state machine for subsequent processing of a related flow. When the field value of the OPCODE is 0x2A, that is, 42, the OAM message sent by the site is denoted as an LMR message, where 0x2A is a signal flag used to mark the message as an LMR message.
(5) After the LMR collects the PW and sends the counter, the LMR does not count the counter.
(6) And finishing the LMR sending.
The LMR receives:
(1) the front-end chip receives an LMR message from a line. And identifying that the OAM frame is a TMC layer OAM frame through the LSP + PW + ACH, and further analyzing the OPCODE field. When the OPCODE is 0x2A, filling a receiving counter corresponding to the PW in four bytes after "TxFCb" of the LMR message, which is called as "RxFCb" in the field of the counter, and obtaining a count value of the RxFCb field.
(2) And the message passes through a forwarding plane according to the standard TMCAM message format and is sent to a back-end FPGA by a back-end distributed forwarding chip.
(3) After the LMR collects the PW receiving counter, the LMR does not count the PW receiving counter into the LMR
(4) And the rear-end FPGA analyzes the count values (TxFCf, RxFCf, TxFCb and RxFCb) of the four counters in the LMR message and reads the count values.
(5) The count values of the TxFCf, RxFCf, TxFCb, and RxFCb fields in the FPGA register are read twice at time T1 and time T2. The time interval between two times is greater than or equal to 1 minute.
(6) And finishing the LMR receiving process.
And step S1-3, transmitting and receiving the LMM message and the LMR message between the first MEP node and the second MEP node, wherein the chip self-defined message heads of the LMM message, the LMR message and the OAM message on the TMS layer have the same encapsulation, and the TxFCf, RxFCf, TxFCb and RxFCb values of the TMS layer of the LMM message and the LMR message at the time of T1 and T2 are obtained.
Specifically, for the TMS layer, when the sent OAM message is an LMM message, the value of a sending counter of a logical port of the service plane of the first MEP node is used as the value of TxFCf; when the second MEP node detects that the received OAM message is an LMM message, taking the receiving counter value of the logic port of the service layer of the second MEP node as an RxFCf value; when the sent OAM message is an LMR message, taking the sending counter value of the logic port of the service layer of the first MEP node as the value of the TxFCb; and when the second MEP node detects that the received OAM message is an LMR message, taking the receiving counter value of the logic port of the service layer of the second MEP node as the RxFCb value. When the LMM message content received by the first MEP node is a management message, the OPCODE field in the LMM message is analyzed, and a sending counter or a receiving counter of a corresponding service layer logic port is started for calculation.
That is to say, in the interaction process of the first MEP node and the second MEP node performing LMM and LMR transmission and reception, the specific process includes LMM transmission, LMM reception, LMR transmission, and LMR reception.
Fig. 5 is a schematic flow diagram of sending and receiving LMMs and LMRs between a first MEP node and a second MEP node on a TMS layer.
The process flow is substantially identical to that of the TMP layer.
And LMM sending:
(1) and the message sent to the chip by the FPGA is encapsulated consistently with the chip custom message header of other TMP layer OAMs. The fields of 'TxFCf', 'Reserved for RxFCf in LMR' and 'Reserved for TxFCb in LMR' in the LMM message are set to zero. The consistent packaging is to make the messages the same as the FPGA messages in the existing MEP node device, so that the messages can be smoothly sent and transmitted, and the packaged ready-made message format has small change to the system, is convenient to debug and is not easy to make mistakes. The fields of 'TxFCf', 'Reserved for RxFCf in LMR' and 'Reserved for TxFCb in LMR' in the LMM message are set to zero in order to start a new cycle packet counting, and the obtained counting values are filled into the fields to ensure the accuracy of the counting process during the subsequent counting. The TxFCf is a 32-bit counter, and the value thereof is the service packet transmission counter value at the LMM transmission time, "Reserved for RxFCf in LMR" and "Reserved for TxFCb in LMR" indicate the standby value of these 4 bytes, and is generally regarded as 0 by default.
(2) After receiving the message with the D-Type of 3, the chip further analyzes the message to an OPCODE field. When OPCODE is 0x2B, the transmit counter value of the service plane logical port is filled in the "TxFCf" field. In the TMS layer, a D-type of 1 means that an OAM management packet processing procedure is entered, means that a received OAM management packet is not a service packet but a management packet, and this fact needs to enter a dedicated OAM state machine for subsequent processing of a related flow. When the field value of the OPCODE is 0x2B (0x represents a 16-ary system), that is, 43, the OAM message sent by the site is represented as an LMM message, where 0x2B is a signal flag used to indicate that the message is an LMM message.
(3) After the LMM finishes collecting and sending the counter, the LMM does not count the LMM into the transmission counter
(4) LMM sending is finished
LMM receives:
(1) the chip receives the LMM message from the line. The TMS layer OAM frame is identified by GAL + ACH and the OPCODE field is further parsed. And when the OPCODE is 0x2B, filling a receiving counter of the logic interface corresponding to the service into a 'Reserved for RxFCf in LMR' field of the LMM message to obtain a count value of the RxFCf field. Similarly, when the field value of the OPCODE is 0x2B or 43, it indicates that the OAM message received by the station is an LMM message, where 0x2B is a signal flag used to mark the message as an LMM message.
(2) And transmitting the message to the FPGA according to the standard TMS OAM message format.
(3) After the LMM finishes collecting the receiving counter, the LMM does not count the LMM into the receiving counter.
(4) And completing the LMM receiving process.
And LMR sending:
(1) the FPGA directly copies the 'TxFCf' and 'Reserved for RxFCf in LMR' of the LMM into corresponding bytes of the LMR (position moving is not needed, and direct adoption is achieved).
(2) And the LMR message sent to the chip by the FPGA is encapsulated consistently with the custom message header of other TMS layer OAM frame chips.
(3) After receiving the message with the D-Type of 3, the chip further analyzes the message to an OPCODE field. When the OPCODE is 0x2A, the transmission counter value of the service plane logical port is filled in the "TxFCb" field, and the calculated value of the corresponding TxFCb field is obtained. In the TMS layer, a D-type of 3 means that an OAM management packet processing procedure is entered, means that a received OAM management packet is not a service packet but a management packet, and this fact needs to enter a dedicated OAM state machine for subsequent processing of a related flow. When the field value of the OPCODE is 0x2A, that is, 42, the OAM message sent by the site is denoted as an LMR message, where 0x2A is a signal flag used to mark the message as an LMR message.
(4) After the LMR finishes collecting and sending the counter, the LMR does not count the LMR into the counter.
(5) And finishing the LMR sending.
The LMR receives:
(1) the chip receives an LMR message from the line. The TMS layer OAM frame is identified by GAL + ACH and the OPCODE field is further parsed. When the OPCODE is 0x2A, filling a receiving counter of the logical interface corresponding to the service into four bytes after "TxFCb" of the LMR message, which is called as "RxFCb" as the counter field, and obtaining a count value of the RxFCb field.
(2) And transmitting the message to the FPGA according to the standard TMS OAM message format.
(3) After the LMR collects the LSP receiving counter, the LMR does not count the LMR into the LSP receiving counter.
(4) And the FPGA analyzes the count values (TxFCf, RxFCf, TxFCb and RxFCb) of the four counters in the LMR message and reads the count values.
(5) The count values of the TxFCf, RxFCf, TxFCb, and RxFCb fields in the FPGA register are read twice at time T1 and time T2. The time interval between two times is greater than or equal to 1 minute.
(6) And finishing the LMR receiving process.
Step S2, according to the formula
The remote packet loss is | TxFCf [ T2] -TxFCf [ T1] | - | RxFCf [ T2] -RxFCf [ T1] |,
the number of near-end lost packets is | TxFCb [ T2] -TxFCb [ T1] | - | RxFCb [ T2] -RxFCb [ T1] |,
and calculating the far-end packet loss number and the near-end packet loss number of the TMC, TMP and TMS layers.
Wherein, TxFCf [ T2] is a TxFCf value obtained at a time T2, TxFCf [ T1] is a TxFCf value obtained at a time T1, RxFCf [ T2] is an RxFCf value obtained at a time T2, RxFCf [ T1] is an RxFCf value obtained at a time T1, TxFCb [ T2] is a TxFCb value obtained at a time T2, TxFCb [ T1] is a TxFCb value obtained at a time T1, RxFCb [ T2] is an RxFCb value obtained at a time T2, and RxFCb [ T1] is an RxFCb value obtained at a time T1.
Specifically, the TxFCf [ T2], TxFCf [ T1], RxFCf [ T2], RxFCf [ T1], TxFCb [ T2], TxFCb [ T1], RxFCb [ T2], and RxFCb [ T1] values corresponding to the three layers of the TMP, TMC, and TMS layers in the above formula are obtained through the LMM message and the count values of the corresponding fields in the LMR message graph in the transmission and reception processes of the first MEP node and the second MEP node.
In summary, the inventive idea of the method according to the above description of step S1 and step S2 is:
firstly, LM carries out single-end measurement as required, and after the function is started, the LM carries a local end sending service message number statistic TxFCf to send an LMM OAM message to an opposite end maintenance end point;
then, after receiving the LMM OAM message, the receiving end modifies the message into an LMR OAM message, and adds the receiving service message number statistic RxFCf of the local end and the sending service message number statistic TxFCb of the local end to return the message to the sending end;
and finally, after receiving the LMR OAM message, the sending end calculates the packet loss number according to the statistics of the TxFCf, the RxFCf, the TxFCb and the receiving service message number of the local end, and further calculates the packet loss rate and the like.
The specific processes in the receiving and transmitting processes of each layer are described in detail above according to the TMP, TMC, and TMS layers, and it is noted that for convenience of description, the TMP, TMC, and TMS layers are separately and sequentially described, but actually, the transmitting and receiving processes are performed at the same time and are not sequentially described.
The function and effect of the embodiment are as follows: according to the method for acquiring packet loss numbers of each layer among mpls network nodes in this embodiment, because the same LMM and LMR data frame is used for testing the packet loss numbers of the three layers of TMC, TMP and TMS, in the process of transmitting the packet loss numbers from the first MEP node to the second MEP node at one time, by acquiring specific fields in LMM and LMR messages at different times: the numerical values of TxFCf, RxFCf, TxFCb and RxFCb can be calculated to obtain the packet loss number of TMC, TMP and TMS three-layer data transmission in one LMM and LMR message sending and receiving process through a specific formula, and the method is simple in process, easy to implement and high in accuracy.
Further, in the embodiment, under the condition that chip resources are limited, the packet loss number of each layer channel of the MPLS-TP can be rapidly calculated, the packet loss rate can be further calculated, and the real-time working condition of each layer service channel can be analyzed by comparing the consistency of each packet loss rate.

Claims (6)

1. A method for obtaining packet loss number between nodes of mpls network is used for obtaining packet loss number of TMP, TMC, TMS layer in data packet transmission process between two MEP nodes in mpls network, and is characterized in that sending and receiving of LMM message and LMR message of TMP, TMC, TMS layer are carried out between a first MEP node and a second MEP node, and TxFCf, RxFCf, TxFCb and RxFCb value in TMP, TMC, TMS layer are respectively obtained in the sent and received LMM message and LMR message to carry out calculation of packet loss number;
sending and receiving an LMM message and an LMR message between a first MEP node and a second MEP node, wherein chip custom message headers of the LMM message, the LMR message and an OAM message of a TMP layer have the same encapsulation, and TxFCf, RxFCf, TxFCb and RxFCb values of the TMP layer of the LMM message and the LMR message at T1 and T2 are obtained;
the method comprises the steps that LMM messages and LMR messages are sent and received between a first MEP node and a second MEP node, chip custom message headers of the LMM messages, the LMR messages and OAM messages of a TMC layer are packaged in the same mode, and TxFCf, RxFCf, TxFCb and RxFCb values of the TMC layer at T1 and T2 of the LMM messages and the LMR messages are obtained;
sending and receiving an LMM message and an LMR message between a first MEP node and a second MEP node, wherein chip custom message headers of the LMM message, the LMR message and an OAM message of a TMS layer have the same encapsulation, and TxFCf, RxFCf, TxFCb and RxFCb values of the TMS layer of the LMM message and the LMR message at T1 and T2 are obtained;
wherein the content of the first and second substances,
for TMP layer
When the sent OAM message is an LMM message, taking the sending counter value of the service layer LSP of the first MEP node as the value of TxFCf;
when the second MEP node detects that the received OAM message is an LMM message, taking the receiving counter value of the service layer LSP of the second MEP node as an RxFCf value;
when the sent OAM message is an LMR message, taking the sending counter value of the service layer LSP of the first MEP node as the value of TxFCb;
when the second MEP node detects that the received OAM message is an LMR message, taking the receiving counter value of the service layer LSP of the second MEP node as the RxFCb value;
for TMC layer
When the sent OAM message is an LMM message, taking the sending counter value of the service layer PW of the first MEP node as the value of TxFCf;
when the second MEP node detects that the received OAM message is an LMM message, taking the receiving counter value of the service layer PW of the second MEP node as an RxFCf value;
when the sent OAM message is an LMR message, taking the sending counter value of the service layer PW of the first MEP node as the value of TxFCb;
when the second MEP node detects that the received OAM message is an LMR message, taking the receiving counter value of the service layer PW of the second MEP node as the RxFCb value;
for TMS layer
When the sent OAM message is an LMM message, taking the sending counter value of the logic port of the service layer of the first MEP node as the value of TxFCf;
when the second MEP node detects that the received OAM message is an LMM message, taking the receiving counter value of the logic port of the service layer of the second MEP node as an RxFCf value;
when the sent OAM message is an LMR message, taking the sending counter value of the logic port of the service layer of the first MEP node as the value of the TxFCb;
and when the second MEP node detects that the received OAM message is an LMR message, taking the receiving counter value of the logic port of the service layer of the second MEP node as the RxFCb value.
2. The method of claim 1, wherein the method for obtaining the number of lost packets between mpls network nodes comprises:
according to the formula:
the remote packet loss is | TxFCf [ T2] -TxFCf [ T1] | - | RxFCf [ T2] -RxFCf [ T1] |,
the number of near-end lost packets is | TxFCb [ T2] -TxFCb [ T1] | - | RxFCb [ T2] -RxFCb [ T1] |,
calculating the far-end packet loss number and the near-end packet loss number of the TMC, TMP and TMS layers,
wherein, TxFCf [ T2] is a TxFCf value obtained at a time T2, TxFCf [ T1] is a TxFCf value obtained at a time T1, RxFCf [ T2] is an RxFCf value obtained at a time T2, RxFCf [ T1] is an RxFCf value obtained at a time T1, TxFCb [ T2] is a TxFCb value obtained at a time T2, TxFCb [ T1] is a TxFCb value obtained at a time T1, RxFCb [ T2] is an RxFCb value obtained at a time T2, and RxFCb [ T1] is an RxFCb value obtained at a time T1.
3. The method of claim 1, wherein the method for obtaining the number of lost packets between mpls network nodes comprises:
when the LMM message content received by the first MEP node is a management message, the OPCODE field in the LMM message is analyzed, and a sending counter or a receiving counter of a corresponding service layer LSP is started for calculation.
4. The method of claim 1, wherein the method for obtaining the number of lost packets between mpls network nodes comprises:
when the LMM message content received by the first MEP node is a management message, the OPCODE field in the LMM message is analyzed, and a sending counter or a receiving counter of the corresponding service layer PW is started to perform calculation.
5. The method of claim 1, wherein the method for obtaining the number of lost packets between mpls network nodes comprises:
when the LMM message content received by the first MEP node is a management message, the OPCODE field in the LMM message is analyzed, and a sending counter or a receiving counter of a corresponding service layer logic port is started for calculation.
6. The method of claim 1, wherein the method for obtaining the number of lost packets between mpls network nodes comprises:
wherein the difference between T1 and T2 is greater than or equal to 1 minute.
CN201910253140.2A 2019-03-29 2019-03-29 method for acquiring packet loss number between mpls network nodes Active CN109981414B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910253140.2A CN109981414B (en) 2019-03-29 2019-03-29 method for acquiring packet loss number between mpls network nodes

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910253140.2A CN109981414B (en) 2019-03-29 2019-03-29 method for acquiring packet loss number between mpls network nodes

Publications (2)

Publication Number Publication Date
CN109981414A CN109981414A (en) 2019-07-05
CN109981414B true CN109981414B (en) 2021-08-24

Family

ID=67081922

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910253140.2A Active CN109981414B (en) 2019-03-29 2019-03-29 method for acquiring packet loss number between mpls network nodes

Country Status (1)

Country Link
CN (1) CN109981414B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021051418A1 (en) * 2019-09-21 2021-03-25 Huawei Technologies Co., Ltd. Methods and network nodes for reliability measurement

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102984018A (en) * 2011-09-02 2013-03-20 华为技术有限公司 Method, device and system for Ethernet packet loss measurement

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7983163B2 (en) * 2008-12-11 2011-07-19 International Business Machines Corporation System and method for implementing adaptive load sharing to balance network traffic
CN102857385B (en) * 2011-06-30 2018-01-16 中兴通讯股份有限公司 Packet loss detection method and system in a kind of Packet Transport Network
CN104486153B (en) * 2014-12-12 2018-03-30 国家电网公司 A kind of transformer station process layer network transmission performance monitoring method based on FPGA
CN106411625A (en) * 2015-07-27 2017-02-15 中兴通讯股份有限公司 Link message packet loss measurement method and system, target node and initiator node
CN106789437B (en) * 2016-12-29 2020-07-28 瑞斯康达科技发展股份有限公司 Message processing method, forwarding method, related device and packet loss rate measuring method

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102984018A (en) * 2011-09-02 2013-03-20 华为技术有限公司 Method, device and system for Ethernet packet loss measurement

Also Published As

Publication number Publication date
CN109981414A (en) 2019-07-05

Similar Documents

Publication Publication Date Title
US8520530B2 (en) Method and apparatus for providing availability metrics for measurement and managment of ethernet services
CN100583784C (en) Method for monitoring frame loss rate in multi protocol label exchange network
US8953456B2 (en) Ethernet OAM performance management
CN101536411B (en) Ethernet OAM at intrmediate nodes in a PBT network
KR101459252B1 (en) Traceroute_delay diagnostic command
CN106375158B (en) A kind of method for detecting packet loss, the network equipment and system
US20050099955A1 (en) Ethernet OAM fault isolation
CA2422258A1 (en) Ethernet route trace
CN105391592B (en) A kind of methods, devices and systems Packet Transport Network business detecting and measured
US20050099949A1 (en) Ethernet OAM domains and ethernet OAM frame format
US20050099951A1 (en) Ethernet OAM fault detection and verification
EP3022874B1 (en) Triangle loopback
CN105991338B (en) Network O&M management method and device
CN106789430B (en) A kind of point-to-point link fault detection method
WO2016177120A1 (en) Measurement method and system for packet loss of link packet, target node and initiating-end node
US20150036510A1 (en) Method and device for measuring ethernet performance
CN100550786C (en) In data network operation and maintenance agreement to the method for performance monitoring of frame transmission
CN107425995A (en) Bidirectional measurement control method, send business device and receive business device
CN109981414B (en) method for acquiring packet loss number between mpls network nodes
US20230318970A1 (en) Packet Processing Method and Apparatus
CN113328901B (en) Message out-of-order detection method, device and system
CN114697202B (en) Detection method and device
CN102752169B (en) Transmitting, monitoring method and device
EP4084414A1 (en) Detection configuration and processing methods and systems, control and communication devices, and storage medium
CN114157595B (en) Communication system, data processing method and related equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant