Method for counting packet loss and node equipment
By adding a non-first packet counter and iFIT header encapsulation to the header node, the packet loss detection error caused by fragmented packets is resolved, achieving more accurate network packet loss statistics and improving detection accuracy and user experience.
Patent Information
- Application Number
- CN202511393546.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-26
- Publication Date
- 2025-11-18
AI Technical Summary
In complex network environments, there are errors in the statistical packet loss detection of fragmented and non-fragmented packets, resulting in the inaccurate identification of the actual packet loss situation in the network.
By adding a non-first fragment counter at the head node to count the total number of fragmented packets, and performing matching and judgment at the tail node, the packets are encapsulated using the iFIT header to ensure that the number of packets from the head node to the tail node matches the actual number of fragmented packets sent, and to determine whether there is packet loss.
It accurately identifies packet loss in fragmented packets, avoids statistical errors caused by fragmented packets, provides more accurate network packet loss detection results, and improves user experience.
Smart Images
Figure CN120979987A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present specification relates to the technical field of communication, and particularly relates to a method for counting packet loss and a node device. BACKGROUND
[0002] Flow detection is to use normal forwarding traffic, insert control information in the specified traffic, process it through the forwarding device, report the collected information to the controller, detect and identify the subtle anomalies in the network, accurately detect the performance information such as delay, packet loss and jitter of each service, make the network quality SLA real-time visible, and achieve rapid fault delimiting and positioning.
[0003] Flow detection needs to be completed by network devices and controllers, and the whole detection system includes the following roles:
[0004] Ingress: responsible for screening the target traffic, adding specific detection data structure to the target flow, collecting the statistical data of the target flow and reporting it to the controller.
[0005] Transmit: according to whether the packet contains the detection data structure, it is judged whether it is a detection target flow, for the detection target flow, according to the measurement type carried in the detection data structure, it is decided whether the statistical data of the target flow needs to be collected and reported to the controller.
[0006] Egress: according to whether the packet contains the detection data structure, it is judged whether it is a detection target flow, for the detection target flow, the statistical data of the target flow is collected and reported to the controller, and the detection data structure in the packet is removed.
[0007] Controller: responsible for collecting the statistical data sent by the ingress, transmit and egress, and completing the data aggregation and calculation.
[0008] According to the detection requirements of different application scenarios, flow detection can be divided into end-to-end measurement and point-by-point measurement.
[0009] First, end-to-end measurement, as shown in Figure 1 When the user wants to measure the packet loss and delay performance of the whole network, the end-to-end measurement type can be selected. End-to-end measurement measures whether there is packet loss and delay parameter between the device that enters the network (traffic entrance) and the device that leaves the network (traffic exit).
[0010] Second, point-by-point measurement, as shown in Figure 2As shown, when users want to accurately locate the packet loss and latency performance of each network node, they can choose the segmented measurement type. When the measurement results show that there is packet loss or latency that does not meet business requirements in the end-to-end statistical scenario, the network between the end and end can be divided into multiple smaller measurement segments to measure whether there is packet loss or latency between every two network elements, and further locate the network element that affects network performance.
[0011] The main applications of flow-based detection are packet loss detection and latency detection. The principles of packet loss and latency detection are as follows, with latency detection employing a dual-labeling method, that is, using both L and D labels simultaneously to complete latency detection.
[0012] Packet loss detection:
[0013] Ingress node: The L-marker is used to alternately color the marker field of the detected flow according to a certain period, while the number of colored packets in this period is counted and the measurement data is reported to the controller.
[0014] Intermediate Nodes: For point-to-point measurements, intermediate nodes are required to count the number of characteristic service flow colored packets in the current period, following the same period as the ingress nodes, and report the measurement data to the controller. For end-to-end measurements, intermediate nodes forward packets normally without needing to perform flow-based detection processing on characteristic service flows.
[0015] Outgoing node: Based on the same period as the incoming node, count the number of characteristic service flow colored packets in this period and report the measurement data to the controller.
[0016] The controller calculates the packet loss count for service flow i in period i based on the information reported by the ingress and egress nodes: PacketLoss[i] = Tx[i] – Rx[i]
[0017] Latency detection:
[0018] Ingress node: In each measurement cycle, delay coloring is applied to one of the packets in the detected service flow within this cycle, the ingress timestamp t1 of the packet is recorded, and the measurement data is reported to the controller.
[0019] Intermediate Nodes: For point-to-point measurements, intermediate nodes are required to record the egress timestamp t2 of the delay-colored packets of the detected service flows in each cycle and report the measurement data to the controller. For end-to-end measurements, intermediate nodes forward packets normally and do not need to perform flow-based detection processing on the characteristic service flows.
[0020] Outgoing node: According to the same period as the incoming node, record the outgoing timestamp t2 of the delayed coloring message of the detected service flow in each period, and report the measurement data to the controller.
[0021] The controller calculates the one-way delay of the service flow cycle i based on the information reported by the ingress and egress nodes: Delay[i] = t2 - t1.
[0022] Similarly, the one-way latency information of the reverse path of the detection business flow can be obtained.
[0023] In the scenario where the detected business flow has a bidirectional same path, the controller can calculate the bidirectional delay of the business flow period i based on the information reported by the ingress and egress nodes: Delay[i] = forward business flow one-way delay + reverse business flow one-way delay.
[0024] In complex network environments, there are both fragmented and unfragmented packets. This can lead to a situation where something seems wrong but actually works. Unfragmented packets are lost, but fragmented packets are overcounted by the end device. If both are exactly the same, the analyzer may not see any packet loss, even though packet loss has actually occurred in the network. Summary of the Invention
[0025] To overcome the problems existing in related technologies, this specification provides a method and node device for statistical packet loss.
[0026] According to a first aspect of the embodiments of this specification, a method for statistically analyzing packet loss is provided, the method comprising:
[0027] The first sum is obtained based on the number of messages received by the head node and the number of intermediate fragments and the number of tail fragments when the received messages are fragmented.
[0028] Determine if the number of messages sent by the tail node matches the first number;
[0029] If a match is found, it indicates that there was no packet loss from the head node to the tail node; if no match is found, it indicates that there was packet loss from the head node to the tail node.
[0030] The method further includes:
[0031] Add a non-first chip counter to the head node;
[0032] The first value is obtained by summing the number of fragmented packets belonging to the middle fragment and the tail fragment using the non-first fragment counter.
[0033] The step of obtaining the first sum based on the number of messages received by the head node and the number of intermediate fragments and the number of tail fragments in the fragmentation of the received messages includes:
[0034] The first sum is obtained by summing the first value and the number of received messages.
[0035] The step of determining whether the number of messages sent by the tail node matches the first sum includes:
[0036] The header node encapsulates an iFIT header for each fragmented message;
[0037] The tail node obtains the sum of the number of packets carrying the iFIT header;
[0038] The sum of the message counts is matched with the first sum.
[0039] The method further includes:
[0040] The matching results are sent to the management device so that the administrator can determine whether packet loss exists based on the matching results.
[0041] As can be seen from the above embodiments, by calculating the first sum by the head node, the first sum can be matched with the number of messages sent by the tail node, and the matching result can be used to determine whether there is packet loss.
[0042] According to a second aspect of the embodiments of this specification, a node device is provided, the node device comprising:
[0043] The acquisition module is used to obtain a first sum based on the number of packets received by the head node and the number of intermediate fragments and the number of tail fragments after fragmenting the received packets, wherein the first sum is the sum of the number of received packets, the number of intermediate fragments and the number of tail fragments;
[0044] The judgment module is used to determine whether the number of messages sent by the tail node matches the first number;
[0045] The processing module is used to determine that there is no packet loss from the head node to the tail node if a match is found; otherwise, it determines that there is packet loss from the head node to the tail node.
[0046] The node device further includes:
[0047] The configuration module is used to add a non-first chip counter to the header node;
[0048] The acquisition module is used to obtain a first value by counting the sum of the number of fragment packets belonging to the middle fragment and the tail fragment through the non-first fragment counter.
[0049] Specifically, the acquisition module is used to obtain a first sum based on the first value and the sum of the number of received messages.
[0050] The configuration module is further configured to encapsulate an iFIT header for each fragmented packet.
[0051] The acquisition module is also used to acquire the sum of the number of packets carrying the iFIT header;
[0052] The processing module is also used to match the sum of the message counts with the first sum.
[0053] The processing module is also used to send the matching results to the management device so that the administrator can determine whether there is packet loss based on the matching results.
[0054] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this specification. Attached Figure Description
[0055] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this specification and, together with the description, serve to explain the principles of this specification.
[0056] Figure 1 This is a schematic diagram of the architecture of a transmission network illustrated in this specification according to an exemplary embodiment.
[0057] Figure 2 This is a schematic diagram of the architecture of a transmission network illustrated in this specification according to an exemplary embodiment.
[0058] Figure 3 This is a schematic diagram of the architecture of a transmission network illustrated in this specification according to an exemplary embodiment.
[0059] Figure 4 This is a schematic flowchart illustrating a method for statistical packet loss based on an exemplary embodiment. Detailed Implementation
[0060] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.
[0061] The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of this specification. The singular forms “a,” “the,” and “the” as used in this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.
[0062] It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."
[0063] like Figure 3 As shown, user A sends a large packet to user B. This packet is split into 3 pieces on device A. It is then forwarded normally on devices B and C. User B will receive the 3 pieces of the packet and then reassemble them.
[0064] In this scenario, after enabling iFIT probing, device A's ingress packet count is 1 fragment, and its egress packet count is 3 fragments; devices B and C both have 3 fragments counted at both their ingress and egress. Clearly, according to the previously described principle of iFIT packet loss statistics, device C's egress is greater than device A's ingress, causing an anomaly in the packet loss statistics (Ingress-Egress). In complex network environments, there are both fragmented and non-fragmented packets. This can lead to a situation where a seemingly correct but actually incorrect packet loss occurs: non-fragmented packets are lost, but fragmented packets are overcounted at the tail device. If both counts are exactly the same, the analyzer may perceive no packet loss, even though actual packet loss has occurred in the network.
[0065] To address the aforementioned technical problems, embodiments of this disclosure provide a method for statistically analyzing packet loss, such as... Figure 4 As shown, the method includes:
[0066] S401 obtains a first sum based on the number of messages received by the head node and the number of intermediate fragments and the number of tail fragments when the received messages are fragmented, wherein the first sum is the sum of the number of received messages, the number of intermediate fragments and the number of tail fragments.
[0067] S402 determines whether the number of messages sent by the tail node matches the first sum;
[0068] If S403 matches, it determines that there is no packet loss from the head node to the tail node; if it does not match, it determines that there is packet loss from the head node to the tail node.
[0069] In this embodiment, a non-first fragment counter can be added to each probe stream at the head node. This non-first fragment counter is used to record the total number of intermediate fragments and tail fragments generated after the large packet is fragmented.
[0070] like Figure 3As shown, node device A acts as the head node and receives messages from user A. When the message is a large packet, node device A can fragment the large packet into large packet 1, large packet 2, and large packet 3. In other words, node device A splits a message into three packets. At this time, the non-head packet counter will count large packet 2 and large packet 3, which is 2.
[0071] Since node device A counts to 1 when it receives a large packet sent by user A through Ingress, and after node device A splits the large packet into large packet 1, packet 2, and large packet 3, the non-first packet counter will count to 2. Therefore, the first sum of the packets sent by node device A to user A is 3.
[0072] In this embodiment, when node device A reports the Ingress statistics count to the analyzer, it will also report the count results of non-first chip counters to the analyzer. That is, in the example above, node device A will report the first and number 3 to the analyzer.
[0073] In this embodiment, after the head node device fragments the packet, it needs to insert an iFIT encapsulation header into each fragmented packet. Subsequently, when performing iFIT statistics on each node device, it is no longer necessary to pay attention to whether the packet is fragmented. As long as the packet has an iFIT encapsulation header, it will be counted, thereby avoiding the consumption of corresponding computing power.
[0074] For example, when the tail node device performs iFIT statistics, if it counts that there are 3 iFIT encapsulation headers in the outgoing direction, it can be known that 3 slice packets were sent in the outgoing direction. At the same time, the tail node device can send the count of the sent slice packets counted by the outgoing interface to the analyzer. When the analyzer determines that the first sum of the packets sent by node device A is 3 and the number of slice packets sent by the tail node device is also 3, it can be determined that there is no loss of slice packets during the transmission process.
[0075] In another example, if it is determined that the number of slice packets sent reported by the tail node device is less than the first sum reported by node device A, then it can be determined that there is a slice packet loss during transmission.
[0076] In this embodiment, the analyzer can report the matching results to the management device, and the administrator can use the management device to determine whether there is packet loss in the transmission network.
[0077] In practical implementation, the non-first fragment counter is called Fragment. When the analyzer calculates network packet loss, if the non-first fragment count (Fragment) on the head node device is not 0, it indicates that fragmented packets exist on the head node device. When calculating with Egress, the result is "(Ingress + Fragment) - Egress", where Ingress is the number of packets received by the head node device from the user, Fragment is the count of the non-first fragment counter, Ingress + Fragment is the first sum, and Egress is the number of fragmented packets output by the tail node device. When (Ingress + Fragment) - Egress is 0, it can be determined that there is no packet loss during transmission; when (Ingress + Fragment) - Egress is greater than 0, it can be determined that packet loss exists during transmission. Simultaneously, the analyzer can independently display to the user the actual number of packets received by the head device (Ingress) and the number of newly added packets due to fragmentation (Fragment), avoiding confusion when users use other methods to count packets.
[0078] As can be seen from the above embodiments, the technical solution provided in this embodiment can solve the defect that iFIT statistics may be inaccurate when there are fragmented packets in the network, and bring a better user experience.
[0079] Based on the above method embodiments, this disclosure also provides a node device, the node device comprising:
[0080] The acquisition module is used to obtain a first sum based on the number of packets received by the head node and the number of intermediate fragments and the number of tail fragments after fragmenting the received packets, wherein the first sum is the sum of the number of received packets, the number of intermediate fragments and the number of tail fragments;
[0081] The judgment module is used to determine whether the number of messages sent by the tail node matches the first number;
[0082] The processing module is used to determine that there is no packet loss from the head node to the tail node if a match is found; otherwise, it determines that there is packet loss from the head node to the tail node.
[0083] The node device further includes:
[0084] The configuration module is used to add a non-first chip counter to the header node;
[0085] The acquisition module is used to obtain a first value by counting the sum of the number of fragment packets belonging to the middle fragment and the tail fragment through the non-first fragment counter.
[0086] Specifically, the acquisition module is used to obtain a first sum based on the first value and the sum of the number of received messages.
[0087] The configuration module is further configured to encapsulate an iFIT header for each fragmented packet.
[0088] The acquisition module is also used to acquire the sum of the number of packets carrying the iFIT header;
[0089] The processing module is also used to match the sum of the message counts with the first sum.
[0090] The processing module is also used to send the matching results to the management device so that the administrator can determine whether there is packet loss based on the matching results.
[0091] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without creative effort.
[0092] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.
[0093] Other embodiments of this specification will readily occur to those skilled in the art upon consideration of the specification and practice of the invention claimed herein. This specification is intended to cover any variations, uses, or adaptations that follow the general principles of this specification and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this specification are indicated by the following claims.
[0094] It should be understood that this specification is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this specification is limited only by the appended claims.
[0095] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.
Claims
1. A method for statistically analyzing packet loss, characterized in that, The method includes: The first sum is obtained based on the number of messages received by the head node and the number of intermediate fragments and the number of tail fragments when the received messages are fragmented. Determine if the number of messages sent by the tail node matches the first number; If a match is found, it indicates that there was no packet loss from the head node to the tail node; if no match is found, it indicates that there was packet loss from the head node to the tail node.
2. The method according to claim 1, characterized in that, The method further includes: Add a non-first chip counter to the head node; The first value is obtained by summing the number of fragmented packets belonging to the middle fragment and the tail fragment using the non-first fragment counter.
3. The method according to claim 2, characterized in that, The step of obtaining the first sum based on the number of messages received by the header node and the number of intermediate fragments and the number of tail fragments in the fragmentation of the received messages includes: The first sum is obtained by summing the first value and the number of received messages.
4. The method according to claim 1, characterized in that, The step of determining whether the number of messages sent by the tail node matches the first sum includes: The header node encapsulates an iFIT header for each fragmented message; The tail node obtains the sum of the number of packets carrying the iFIT header; The sum of the message counts is matched with the first sum.
5. The method according to claim 1, characterized in that, The method further includes: The matching results are sent to the management device so that the administrator can determine whether there is packet loss based on the matching results.
6. A node device, characterized in that, The node device includes: The acquisition module is used to obtain a first sum based on the number of packets received by the head node and the number of intermediate fragments and the number of tail fragments after fragmenting the received packets, wherein the first sum is the sum of the number of received packets, the number of intermediate fragments and the number of tail fragments; The judgment module is used to determine whether the number of messages sent by the tail node matches the first number; The processing module is used to determine that there is no packet loss from the head node to the tail node if a match is found; otherwise, it determines that there is packet loss from the head node to the tail node.
7. The node device according to claim 6, characterized in that, The node device further includes: The configuration module is used to add a non-first chip counter to the header node; The acquisition module is used to obtain a first value by counting the sum of the number of fragmented packets belonging to the middle fragment and the tail fragment through the non-first fragment counter.
8. The node device according to claim 7, characterized in that, The acquisition module is specifically used to obtain a first sum based on the first value and the sum of the number of received messages.
9. The node device according to claim 6, characterized in that, The configuration module is also used to encapsulate an iFIT header for each fragmented packet; The acquisition module is also used to acquire the sum of the number of packets carrying the iFIT header; The processing module is also used to match the sum of the message counts with the first sum.
10. The node device according to claim 6, characterized in that, The processing module is also used to send the matching results to the management device so that the administrator can determine whether there is packet loss based on the matching results.