CN114073049B - Method and network node for reliability measurement - Google Patents
Method and network node for reliability measurement Download PDFInfo
- Publication number
- CN114073049B CN114073049B CN201980096090.XA CN201980096090A CN114073049B CN 114073049 B CN114073049 B CN 114073049B CN 201980096090 A CN201980096090 A CN 201980096090A CN 114073049 B CN114073049 B CN 114073049B
- Authority
- CN
- China
- Prior art keywords
- message
- network node
- count information
- node
- network
- 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
Links
- 238000005259 measurement Methods 0.000 title claims abstract description 167
- 238000000034 method Methods 0.000 title claims description 62
- 238000011156 evaluation Methods 0.000 claims description 42
- 235000008694 Humulus lupulus Nutrition 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 5
- 238000003860 storage Methods 0.000 claims description 3
- 238000001514 detection method Methods 0.000 abstract description 14
- 238000010586 diagram Methods 0.000 description 19
- 230000006870 function Effects 0.000 description 10
- 150000001875 compounds Chemical class 0.000 description 3
- 239000000203 mixture Substances 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 239000004615 ingredient Substances 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000000691 measurement method Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- 238000011065 in-situ storage Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
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
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/02—Capturing of monitoring data
- H04L43/026—Capturing of monitoring data using flow identification
-
- 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/12—Shortest path evaluation
- H04L45/123—Evaluation of link metrics
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/55—Prevention, detection or correction of errors
- H04L49/555—Error detection
Abstract
The present invention relates to the field of computer networks. More particularly, the present invention relates to packet loss detection in such networks. The present invention provides a network node for reliability measurement of a network. The network node is used for acquiring a message, wherein the message relates to a stream being transmitted in a network and comprises a reliability measurement field; acquiring message counting information of the network node, wherein the message counting information represents the number of messages of the flow forwarded by the network node; inserting the message count information of the network node into the reliability measurement field; and forwarding the message to a next hop of the network node.
Description
Technical Field
The present invention relates to the field of computer networks. More particularly, the present invention relates to packet loss detection in such networks. A network node is provided that allows in-band packet loss measurements to be made over multiple hops. The invention also relates to an evaluation device, an ingress node and an egress node assisting the network node.
Background
Performance measurement and network telemetry are key capabilities of a communication network. One of the most important aspects of performance monitoring is packet loss measurement, i.e., the ability to detect and measure the number of network device packets lost. In particular, it is particularly important to be able to detect the exact location of a packet loss (a particular network device or node).
Existing packet loss measurement solutions employ a point-to-point approach such that the number of lost packets is measured between two particular devices or endpoints in the network. The problem faced by this solution is that it is difficult to determine the exact location of the packet loss.
Disclosure of Invention
In view of the above, embodiments of the present invention aim to improve conventional packet loss measurement solutions.
The aim is to allow the measurement of packet losses on the network path hop by hop, in particular to allow the detection of the location of the packet losses.
This object is achieved by embodiments of the invention as described in the appended independent claims. Advantageous implementations of embodiments of the invention are further defined in the dependent claims.
A first aspect of the invention provides a network node for reliability measurement of a network. The network node is used for acquiring a message, wherein the message relates to a stream being transmitted in a network and comprises a reliability measurement field; acquiring message counting information of the network node, wherein the message counting information represents the number of messages of the flow forwarded by the network node; inserting the message count information of the network node into the reliability measurement field; and forwarding the message to a next hop of the network node.
This is advantageous in that the message comprises a reliability measurement field for which message count information of the network node is acquired and inserted. The reliability measure field allows determining the location of the packet loss in the network.
In particular, the network node for packet loss measurement may also be referred to as a transit node or a forwarding node.
In particular, the forwarding node may be a switch, a router, a middlebox, a network interface controller, a NIC, or any device capable of sending, receiving, and/or forwarding messages.
In particular, the reliability measure field is a field that includes an entry with reliability information (i.e., message count information) for each node on the network path. In particular, the reliability measure field may be updated by each node on the path.
In particular, the message count information comprises a count value of a total number of messages of a generic flow forwarded by the network node.
In particular, the next hop of the network node is the network node to which the message is forwarded.
In an implementation manner of the first aspect, the message is obtained from a last hop of the network node.
In particular, the last hop of the network node is a network node that forwards the message to the network node for reliability measurements.
In a further implementation manner of the first aspect, the obtained packet count information further includes a first identifier, where the first identifier is obtained by adding 1 to an identifier of the packet count information of the network node of the previous hop.
This is advantageous because it allows determining the location of a packet loss in the network based on the above identification.
In particular, the packet count information in the packet acquired by the network node already has an identifier of the packet count information of the network node of the previous hop.
In particular, the identity is greater than a maximum identity of message count information contained in the reliability measurement field of the acquired message.
In particular, the identification is an integer. In particular, the identifier of the acquired message count information is greater than the maximum identifier of the message count information existing in the acquired message by a value of 1.
In particular, the stream includes a set of messages having a common characteristic.
In particular, the features include at least one of: source IP, destination IP, source port, destination port, protocol type, multicast group, broadcast domain.
In a further implementation form of the first aspect, the network node is further configured to provide the acquired message count information to an evaluation node.
A second aspect of the invention provides a network node for preparing a message for a reliability measurement of a network. The network node is used for acquiring a message from a source node; adding a reliability measurement field in the message, wherein the reliability measurement field comprises initial message counting information; and forwarding the message to a network node for reliability measurement.
This is advantageous because it enables the determination of the location of packet losses in the network.
In particular, the network node for preparing the message for the performance measurement may also be referred to as an ingress node.
In particular, the ingress node may be a switch, a router, a middlebox, a network interface controller, a NIC, or any device capable of sending, receiving, and/or forwarding messages.
In an implementation manner of the second aspect, the initial message count information further includes a second identifier, the second identifier specifying a sequence number of the network node for preparing a message for a reliability measure between hops in the network.
This is advantageous because it enables to determine the location of the packet loss in the network based on said second identity.
In particular, the second identifier is, for example, 0 or 1. In particular, the second identity indicates the start of a network path of measurement reliability.
In particular, the second identity of the network node for preparing a message for a reliability measurement is a first identity of the network node for a reliability measurement.
A third aspect of the invention provides a network node for performing reliability measurements of a network. The network node is used for acquiring a message from the network node to perform reliability measurement, wherein the message comprises a reliability measurement field which comprises message counting information of one or more network nodes through which the message passes in the network; removing the reliability measurement field from the message; providing the reliability measure field to an evaluation node; and forwarding the message to a destination node.
This is advantageous because it enables the determination of the location of packet losses in the network.
In particular, the network node for performing performance measurements may also be referred to as an egress node.
In particular, the egress node may be a switch, a router, a middlebox, a network interface controller, a NIC, or any device capable of sending, receiving, and/or forwarding messages.
In particular, the network node is configured to provide the reliability measure field together with the message to the evaluation node.
In particular, the network node is configured to provide the reliability measure field together with the truncated portion of the message to the evaluation node.
In particular, the message is forwarded to a destination indicated in the message.
In an implementation manner of the third aspect, the acquired packet count information further includes an identification of the acquired packet count information.
This is advantageous because it enables the determination of the location of a packet loss in the network based on the above identification.
In particular, the identifier of the acquired message count information corresponds to the first identifier or the second identifier.
A fourth aspect of the invention provides an evaluation node for reliability measurement of flows in a network. The evaluation node is configured to: obtaining a first reliability measurement field related to a first message and a second reliability measurement field related to a second message from an egress network node, wherein the first reliability measurement field comprises first message count information, and the second reliability measurement field comprises second message count information; and evaluating reliability of the flow based on the first and second message count information.
This is beneficial because it determines the location of packet loss in the network.
In particular, the egress network node is the network node for performing reliability measurements.
In an implementation manner of the fourth aspect, the identifier of the second packet count information is the same as the identifier of the first packet count information, and the evaluation node is further configured to detect packet loss based on a difference between the count value of the second packet count information and the count value of the first packet count information.
This is advantageous because it enables the determination of the location of a packet loss in the network based on the above identification.
In particular, the second message is immediately subsequent to the first message.
In particular, the node to which the second message count information entry relates is immediately next to the node to which the first message count information entry relates. Both nodes are located on a common network path.
Specifically, if the difference between the count value of the second packet count information table item and the count value of the first packet count information table item is greater than 1, packet loss is detected.
A fifth aspect of the invention provides a method for reliability measurement. The method comprises the following steps: the method comprises the steps that a network node obtains a message, wherein the message relates to a stream being transmitted in a network and comprises a reliability measurement field; the network node obtains message counting information of the network node, wherein the message counting information represents the message quantity of the flow forwarded by the network node; the network node inserts the message count information of the network node into the reliability measurement field; and the network node forwards the message to the next hop of the forwarding network node.
In particular, the message is obtained from a network node for preparing the message for reliability measurement. In particular, the message is forwarded to a network node for performing reliability measurements.
In an implementation manner of the fifth aspect, the message is obtained from a last hop of the network node.
In a further implementation manner of the fifth aspect, the obtained packet count information further includes a first identifier, where the first identifier is obtained by adding 1 to an identifier of the packet count information of the network node of the previous hop.
In a further implementation manner of the fifth aspect, the network node provides the acquired message count information to an evaluation node.
The fifth aspect and its implementation include the same advantages as the first aspect and its separate implementation.
A sixth aspect of the invention provides a method for preparing a message for reliability measurement. The method comprises the following steps: the network node acquires a message from a source node; the network node adds a reliability measurement field in the message, wherein the reliability measurement field comprises initial message counting information; and the network node forwards the message to a network node for reliability measurement.
In particular, the message is forwarded to a network node for reliability measurement. In particular, the network node for reliability measurement obtains the message count information and adds the message count information as an entry to the reliability measurement field.
In an implementation manner of the sixth aspect, the initial message count information further includes a second identifier, where the second identifier specifies a sequence number of the network node for preparing a message for reliability measurement between hops in the network.
The sixth aspect and its implementation include the same advantages as the second aspect and its separate implementation.
A seventh aspect of the invention provides a method for performing reliability measurements. The method comprises the following steps: the network node acquires a message from the network node, wherein the message comprises a reliability measurement field which comprises message counting information of one or more network nodes through which the message passes in a network; the network node removing the reliability measurement field from the message; the network node providing the reliability measurement field to an evaluation node; and the network node forwards the message to a destination node.
In particular, the message is obtained from a network node for reliability measurement. In particular, the network node for reliability measurement obtains the message count information and adds the message count information as an entry to the reliability measurement field.
In an implementation manner of the seventh aspect, the acquired packet count information further includes an identification of the acquired packet count information.
The seventh aspect and its implementation include the same advantages as the third aspect and its separate implementation.
An eighth aspect of the invention provides a method for reliability measurement of flows in a network. The method comprises the following steps: the method comprises the steps that an evaluation node obtains a first reliability measurement field related to a first message and a second reliability measurement field related to a second message from an exit network node, wherein the first reliability measurement field comprises first message counting information, and the second reliability measurement field comprises second message counting information; and the evaluation node evaluates the reliability of the flow based on the first and second message count information.
In particular, the message is obtained from a network node for performing reliability measurements.
In an implementation manner of the eighth aspect, the identifier of the second packet count information is the same as the identifier of the first packet count information, and the evaluation node is further configured to detect packet loss based on a difference between the count value of the second packet count information and the count value of the first packet count information.
The eighth aspect and its implementation include the same advantages as the fourth aspect and its separate implementation.
A ninth aspect of the invention proposes a computer program product comprising computer readable code instructions. When run in a computer, the computer readable code instructions will cause the computer to perform the method of the fifth, sixth, seventh or eighth aspect of the invention.
A tenth aspect of the invention proposes a computer readable storage medium comprising computer program code instructions executable by a computer. When run in a computer, the computer program code instructions will perform the method according to the fifth, sixth, seventh or eighth aspect of the invention. The computer readable storage medium includes one or more of the following: read-Only Memory (ROM), programmable ROM (PROM), erasable Programmable ROM (EPROM), flash Memory, electrically Erasable Programmable ROM (Electrically EPROM, EEPROM), and hard disk drive.
An eleventh aspect of the invention proposes an apparatus for reliability measurement of a network, comprising a processor and a memory. The memory stores instructions that cause the processor to perform the method according to the fifth aspect of the invention.
A twelfth aspect of the invention proposes an apparatus for reliability measurement of a network, comprising a processor and a memory. The memory stores instructions that cause the processor to perform the method according to the sixth aspect of the invention.
A thirteenth aspect of the invention proposes an apparatus for reliability measurement of a network, comprising a processor and a memory. The memory stores instructions that cause the processor to perform the method according to the seventh aspect of the invention.
A fourteenth aspect of the invention proposes an apparatus for reliability measurement of a network, comprising a processor and a memory. The memory stores instructions that cause the processor to perform the method according to the eighth aspect of the invention.
In summary, the embodiment of the invention provides a solution for packet loss measurement, so as to measure the number of packet loss of each hop on a network path of a given service flow. The measurement solution may require each network device on the network path to maintain a message counter for a given traffic flow being measured. Each device may push the value of its counter into the header of the data packet as it traverses the network path. At the end of the path, the counters of all network devices on the path may be used to analyze the evaluation scheme of the counters. These hop-by-hop counters then allow measurement of the number of messages lost in each hop since the previously received message.
It should be noted that all the devices, elements, units and methods described in the present application may be implemented in software or hardware elements or any combination thereof. All steps performed by the various entities described in this application and the functions described to be performed by the various entities are intended to indicate that the various entities are adapted to or for performing the respective steps and functions. Although in the following description of specific embodiments, specific functions or steps performed by external entities are not reflected in the description of specific elements of the entity performing the specific steps or functions, it should be clear to a skilled person that the methods and functions may be implemented in respective hardware or software elements or any combination thereof.
Drawings
The aspects of the application and the manner of attaining them will be elucidated with reference to the embodiments described hereinafter, taken in conjunction with the accompanying drawings, wherein:
fig. 1 shows a schematic diagram of a network node for reliability measurement according to an embodiment of the present application;
FIG. 2 shows a schematic diagram of a network node for reliability measurement provided by an embodiment of the present application in more detail;
fig. 3 is a schematic diagram of a network node for preparing a message for reliability measurement according to an embodiment of the present application;
FIG. 4 illustrates in more detail a schematic diagram of a network node for preparing a message for reliability measurement provided by an embodiment of the present application;
fig. 5 shows a schematic diagram of a network node for performing reliability measurements according to an embodiment of the present application;
FIG. 6 illustrates in more detail a schematic diagram of a network node for performing reliability measurements provided by an embodiment of the present application;
FIG. 7 is a schematic diagram of an evaluation node for reliability measurement according to an embodiment of the present application;
FIG. 8 illustrates a schematic diagram of an evaluation node for reliability measurement provided by an embodiment of the present application in more detail;
FIG. 9 shows an example of operation provided by the present application;
FIG. 10 is a schematic diagram of a message provided by the present application;
FIG. 11 is a schematic diagram of a plurality of messages provided by the present application;
FIG. 12 shows a schematic diagram of a method provided by an embodiment of the present application;
FIG. 13 shows a schematic diagram of a method provided by an embodiment of the present application;
FIG. 14 shows a schematic diagram of a method provided by an embodiment of the present application; and
fig. 15 shows a schematic diagram of a method provided by an embodiment of the present application.
Detailed Description
Illustrative embodiments of a method and apparatus for managing data for a plurality of files within one or more file systems are described herein with reference to the accompanying drawings. While this description provides detailed examples of possible implementations, it should be noted that the details are intended to be examples and in no way limit the scope of the application.
In addition, one embodiment/example may refer to other embodiments/examples. For example, any description including, but not limited to, terms, elements, processes, explanations, and/or technical advantages mentioned in one embodiment/example apply to other embodiments/examples.
Fig. 1 shows a schematic diagram of a network node 100 according to an embodiment of the present invention. The network node 100 is used for reliability measurements of a network, in particular for packet loss detection in a network.
To this end, the network node 100 is adapted to obtain a message 101, which relates to a particular flow forwarded in the network. The acquired message 101 includes a reliability measurement field 102. The reliability measure field 102 may be inserted into the message, for example, by a previous node in the path, such as an ingress node, which will be described below.
The network node 100 is further configured to obtain message count information 103 of the network node 100. The message count information 103 indicates the number of messages of the flow forwarded by the network node 100. That is, the network node 100 counts the number of forwarding messages associated with the flow.
The message count information 103 (i.e. the message count number) of the network node 100 is then inserted into the reliability measurement field 102. The message 101 is then forwarded to the next hop of the network node 100. The next hop of the network node 100 may be, for example, a later network node in the network path of the flow. The last hop of the flow to be monitored may be, for example, an egress node, which will also be described below.
Fig. 2 shows a schematic diagram of a network node 100 provided by an embodiment of the present invention in more detail. The network node 100 of fig. 2 is based on the network node 100 of fig. 1 and thus comprises all its features and functions.
As shown in fig. 2, the network node 100 may also obtain the first identifier 201 when obtaining the packet count information 103. The first identifier may be regarded as an index value or simply as the number of the message count information 103. To obtain the first identity 201, the network node 100 looks up other identities related to the previous several nodes in the path of the message 101 in the reliability measurement field 102 (i.e. looks up other index numbers of the message count information 103 in the reliability measurement field 102). Then adding 1 to the found maximum identity gives the value of said first identity 201.
Alternatively, the network node 100 may also directly provide the acquired packet count information 103 to an evaluation node (to be described later) to evaluate the reliability of the network.
Fig. 3 shows a network node 300 according to an embodiment of the invention. The network node 300 is arranged to prepare a message 301 for a reliability measurement.
The network node 300 may also be referred to as an ingress node. The network node 300 obtains a message 301 from a source node. The network node 300 then adds a reliability measure field 302 in the message 301. The reliability measure field 302 includes initial message count information 303. The initial message count information is, for example, the message count information 303 counted by the network node 300. The message 301 is then forwarded to a network node 100 for reliability measurements. The message 301 forwarded to the network node 100 is the message 101 obtained by the network node 100 in fig. 1.
In other words, the ingress node pushes the following measurement related data into all or a subset of the data messages forwarded through it: a measurement related header (e.g. the reliability measurement field 302), a counter (e.g. the initial message count information 303), in particular a message counter representing the number of messages belonging to the current traffic flow. For each message traversing the network node 100, the counter is incremented. Optionally, the measurement related data further comprises other measurement related fields.
Fig. 4 shows a schematic diagram of a network node 300 provided by an embodiment of the invention in more detail. The network node 300 of fig. 4 is based on the network node 300 of fig. 3 and thus comprises all its features and functions.
As shown in fig. 4, the initial packet count information 303 may further include a second identifier 401. In particular, the second identifier 401 of fig. 4 is the first identifier 201 of fig. 2. The second identifier 401 may be regarded as an initial counter index of the initial message count information 303. That is, if the initial counter index (i.e., the second identification 401) is 1, the next hop on the path may add the message count information 103 entry in the reliability measurement field 102 with the first identification 201 (i.e., count index) of 2. The next node on the path adds a message count information 103 entry with a first identification 201 (i.e., its count index) of 3, and so on.
Fig. 5 shows a network node 500 according to an embodiment of the invention. The network node 500 is used to perform reliability measurements.
To this end, the network node 500 obtains a message 501 from the network node 100. In particular, the acquired message 501 is the message 101 forwarded by the network node 100 in fig. 1. The message 501 includes a reliability measurement field 502 with message count information 503 for one or more network nodes forwarding the message in the network. These fields and information also relate to the corresponding entities of fig. 1.
To complete the reliability measurement, the network node 500 removes the reliability measurement field 502 from the message and provides the reliability measurement field 502 to an evaluation node 700, which will be described below. The message 501 is then forwarded to the destination node. That is, the messages in the figures are sent from the source node to the destination node (i.e., along a particular network path). Reliability measurements are made between the ingress node 300 and the egress node 500 (the measurement path partially overlaps with the particular network path described above).
In other words, the egress node performs the following operations: exporting the measurement data to a detection module, removing the measurement data from the message, and forwarding the message to its destination. The egress node may optionally also push a counter into the measurement data, i.e. may perform the function of the network node 100 (also called transit node).
Fig. 6 shows a schematic diagram of a network node 500 provided by an embodiment of the invention in more detail. The network node 500 of fig. 6 is based on the network node 500 of fig. 5 and thus comprises all its features and functions.
As shown in fig. 6, the packet count information 503 acquired by the network node 500 also includes an identifier 601. The identity 601 is the identity 201 of the network node 100 of fig. 2.
Fig. 7 shows an evaluation node 700 according to an embodiment of the invention. The evaluation node 700 is configured for reliability measurement, for determining and measuring packet loss on a network path of a message of the flow.
To this end, the evaluation node 700 obtains a first reliability measurement field 701. This field relates to a message forwarded by the network node 100, for example. The evaluation node 700 also obtains a second reliability measure field 702, which is e.g. associated with the message. The message is forwarded, for example, by other instances of the network node 100. The first and second reliability measurement fields 701, 702 are provided in particular by the egress node, i.e. by the network node 500.
The first reliability measurement field 701 includes first message count information 703, and the second reliability measurement field 702 includes second message count information 704. Then, the evaluation node 700 evaluates the reliability of the flow to which the packet belongs based on the first packet count information 703 and the second packet count information 704.
The evaluation module 700 may also be referred to as a detection module for detecting and locating packet loss. The detection module may be an external node or an internal module in the egress node. The detection module may be configured to detect packet loss per hop by comparing a counter value of an mth hop on the path with a counter value of the same hop m in a previous packet. If there is no packet loss, the difference should be 1. The difference is the packet loss number plus 1. By repeating this process for each hop on the path, the detection module can calculate the number of dropped packets in each hop on the path.
Upon detection of a packet loss, the detection module may report to a user or management system, or may trigger fine-grained measurements to detect the location of a problem, such as in-band operations management maintenance (in situ operations, administration and maintenance, IOAM for short), or may take corrective action, such as reconfiguring network paths.
Fig. 8 shows a schematic diagram of an evaluation node 700 provided by an embodiment of the invention in more detail. The evaluation node 700 of fig. 8 is based on the evaluation node 700 of fig. 7 and thus comprises all its features and functions.
As shown in fig. 8, the first packet count information 703 and the second packet count information 704 may each include an identifier 801 and 802, respectively. In the evaluation, the identifier 801 of the second packet count information 704 is the same as the identifier 802 of the first packet count information 703. That is, the message count information obtained at a particular node is compared for two different messages. For example, if the values of the identifications 801 and 802 are both "3", a third hop between the ingress node and the egress node is observed.
In particular, packet loss is detected based on a difference between the count value of the second packet count information 704 and the count value of the first packet count information 703.
For example, if the difference between the second packet count information 704 and the first packet count information 703 of two adjacent packets of the same flow is greater than "1" at the third hop between the ingress node and the egress node, packet loss occurs.
Fig. 9 shows an example scenario in which the network node 100 for reliability measurements, the network node 300 for preparing a message 301 for reliability measurements, the network node 500 for completing reliability measurements and the evaluation node 700 for reliability measurements are run.
As shown in fig. 9, performance measurements are performed between a network node 300 (which may also be referred to as an ingress node) for preparing a message 301 for reliability measurements and a network node 500 (which may also be referred to as an egress node) for completing reliability measurements. The ingress node is the first node on the path to participate in the measurement method and the egress node is the last node on the path to participate in the measurement method.
The present invention generally operates through messages, and in particular through data messages and/or control messages. The data message is a message sent from a source host to a destination host, as opposed to a control message sent between network devices.
The ingress node may push the counter (i.e. the initial message count information 303) and possibly other measurement data into the data message.
The egress node may remove the measurement data pushed by the ingress node and forward the data message to its destination.
A transit node (e.g., the network node 100 for reliability measurement) is a node on the path that can push additional data or update existing data (i.e., the message count information 103).
The detection module (which may also be referred to as evaluation node 700) is a module for detecting performance degradation. It may run on a remote server or locally as a module inside the egress node.
The network device capable of implementing the above node may be a switch, a router, a middlebox, a NIC, or any device that forwards messages.
Although not shown in fig. 9, alternatively, each node on the path may derive the message count information to the detection module when receiving a message with a reliability measurement field. The detection module may receive the message count information from each device and may compare it with the message count information of the same stream previously received from the same device. So that packet loss can be determined.
Although there is only one network device 100 on the path between the ingress node 300 and the egress node 500, there may be multiple instances of such network devices 100 on multiple nodes of the path.
In other words, the present invention provides a counter update procedure according to which each network node 100 updates the counter of each traffic flow. However, it is also possible for the ingress or egress node to implement this update flow. The corresponding counter is incremented for each message traversing the traffic flow and belonging to the measured flow.
In order to classify the message into the service flow, the invention also realizes a classification method. A flow consists of a set of messages that have common characteristics, such as source and destination IP addresses, source and destination ports, or protocols. The invention also implements a classification method that determines which traffic flow is currently being measured (which may be a subset of the existing flows in the network).
By implementing the solution shown in fig. 9, the present invention provides a hop-by-hop packet loss measurement using a single in-band measurement for each traffic flow. In contrast, prior art solutions require that a packet loss measurement procedure be invoked for each hop on the path in order to provide the same information about the packet loss location. The present invention employs an innovative combination of a hop-by-hop stream-by-stream counter with existing In-band telemetry methods (IOAM or In-band network telemetry (In-band Network Telemetry, abbreviated INT)).
Fig. 10 shows a message 101 with a reliability measurement field 102 (i.e. "measurement data" in fig. 2). The reliability measure field 102 specifically includes a number of entries of message count information 103 (i.e., entries labeled "counter"). All entries are obtained at different instances of the network node 100. Each entry includes an index number identifying 201, i.e., a counter. In other words, fig. 10 shows a counter of a push message.
Fig. 11 shows the reliability measurement field 102 (i.e., "measurement data") pushed by the ingress node. As shown in the second row of the figure, the data may be pushed with a tunnel header (e.g., VXLAN-GPE) or as an extension of an existing header in the message, e.g., an IPv6 extension header, as shown in the third row. The first line shows a regular message without the reliability measure field 102.
Fig. 12 illustrates a method 1200 provided by an embodiment of the invention. The method 1200 is for reliability measurement, comprising the step of the network node 100 obtaining 1201 a message 101, said message 101 relating to a flow being transmitted in the network and comprising a reliability measurement field 102. The method 1200 further comprises the step of the network node 100 obtaining 1202 message count information 103 of the network node 100, the message count information 103 representing the number of messages of the flow forwarded by the network node 100. The method 1200 further comprises the step of the network node 100 inserting 1203 the message count information 103 of the network node 100 into the reliability measurement field 102. The method 1200 further comprises the step of the network node 100 forwarding 1204 the message 101 to a next hop of the forwarding network node 100.
Fig. 13 illustrates a method 1300 provided by an embodiment of the present invention. The method 1300 is for preparing a message 301 for reliability measurement, comprising the step of the network node 300 obtaining 1301 the message 301 from a source node. The method 1300 further comprises the step of the network node 300 adding 1302 the reliability measure field 302 to the message 301, the reliability measure field 302 comprising initial message count information 303. The method 1300 further comprises the step of the network node 300 forwarding 1303 the message 301 to a network node 300 for reliability measurements.
Fig. 14 illustrates a method 1400 provided by an embodiment of the present invention. The method 1400 is for performing reliability measurements and comprises the step of the network node 500 obtaining 1401 a message 501 from the network node 100, the message 501 comprising a reliability measurement field 502 comprising message count information 503 of one or more network nodes through which the message passes in the network. The method 1400 further comprises the step of the network node 500 removing 1402 the reliability measure field 502 from the message. The method 1400 further comprises the step of the network node 500 providing 1403 the reliability measure field 502 to an evaluation node 700. The method 1400 further comprises the step of the network node 500 forwarding 1404 the message 501 to a destination node.
Fig. 15 illustrates a method 1500 provided by an embodiment of the present invention. The method 1500 is used for reliability measurement of flows in a network, and includes the following steps: the evaluation node 700 obtains 1501 from the egress network node 500 a first reliability measurement field 701 associated with a first message, the first reliability measurement field 701 comprising first message count information 703, and a second reliability measurement field 702 associated with a second message, the second reliability measurement field 702 comprising second message count information 704. The method 1400 further comprises the step of the evaluation node 700 evaluating 1502 the reliability of the flow based on the first message count information 703 and the second message count information 704.
Other systems, methods, features and advantages of the invention will be or will become apparent to one with skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, methods, features and advantages be included within this description, be within the scope of the invention, and be protected by the accompanying claims.
The description of the various embodiments of the present invention is intended for purposes of illustration only and is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles of the embodiments, the practical application, or the technological advancement of the art, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein, as opposed to commercially available technologies.
It is expected that during the life of a patent growing from this disclosure many relevant keys will be developed and the scope of the term "key" is intended to include all such new technologies a priori.
The terms "comprising," including, "" having, "and variations thereof mean" including but not limited to. This term includes the term "consisting of … …" as well as "consisting essentially of … …".
The phrase "consisting essentially of … …" means that a composition or method may include additional ingredients and/or steps, provided that the additional ingredients and/or steps do not materially alter the basic and novel characteristics of the composition or method as required.
As used herein, the singular forms "a", "an" and "the" include plural referents unless the context clearly dictates otherwise. For example, the term "compound" or "at least one compound" may comprise a plurality of compounds, including mixtures thereof.
The word "exemplary" is used herein to mean "serving as an example, instance, or illustration. Any "exemplary" embodiment is not necessarily to be construed as preferred or advantageous over other embodiments, and/or as an exclusion of any combination of features from other embodiments.
The word "optionally" as used herein means "provided in some embodiments and not provided in other embodiments. Any particular embodiment of the application may incorporate a number of "optional" features unless those features are contradictory.
Throughout this disclosure, various embodiments of the application may be presented in a range format. It should be understood that the description of the range format is merely for convenience and brevity and should not be construed as a fixed limitation on the scope of the present application. Accordingly, the description of a range should be considered to have specifically disclosed all possible sub-ranges as well as individual values within the range. For example, descriptions of ranges, e.g., from 1 to 6, should be considered to have specifically disclosed sub-ranges, e.g., from 1 to 3, from 1 to 4, from 1 to 5, from 2 to 4, from 2 to 6, from 3 to 6, etc., as well as individual numbers within the ranges, e.g., 1, 2, 3, 4, 5, and 6. This applies regardless of the width of the range.
When a range of numbers is referred to herein, it is intended to encompass any of the recited numbers (fractional or integer) within the range indicated. The phrases "within a first indicated number and a second indicated number" and "from the first indicated number to the second indicated number" and are used interchangeably herein to refer to the inclusion of both the first and second indicated numbers and all fractions and integers therebetween.
It is appreciated that certain features of the application, which are, for brevity, described in the context of a single embodiment, may also be provided in combination in a single embodiment. Conversely, various features of the application which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable sub-combination or as any suitable alternative embodiment of the application. Certain features described in the context of various embodiments are not to be considered essential features of those embodiments unless the embodiments are not described as being without these elements.
All publications, patents and patent specifications mentioned in this specification are herein incorporated in their entirety by reference into the specification, and each individual publication, patent or patent specification is also specifically and individually indicated to be incorporated herein. Furthermore, citation or identification of any reference to the application shall not be construed as an admission that such reference is available as prior art to the present application. With respect to the use of section titles, the section titles should not be construed as necessarily limiting.
Claims (11)
1. A network node (100) for reliability measurement of a network, the network node (100) being adapted to:
-obtaining a message (101), the message (101) relating to a stream being transmitted in a network and comprising a reliability measurement field (102);
acquiring message count information (103) of the network node (100), wherein the message count information (103) represents the number of messages of a flow forwarded by the network node (100);
inserting the message count information (103) of the network node (100) into the reliability measurement field (102); and
forwarding the message (101) to a next hop of the network node (100);
the acquired message count information (103) further comprises a first identifier (201), wherein the first identifier (201) is obtained by adding 1 to the identifier of the message count information of the network node of the last hop of the network node (100); the message counting information (103) is used for detecting packet loss.
2. The network node (100) according to claim 1, wherein the message (101) is obtained from a last hop of the network node (100).
3. The network node (100) according to any of the preceding claims, further being configured to provide the message count information (103) to an evaluation node.
4. A network node (300) for preparing a message (301) for a reliability measurement of a network, the network node (300) being adapted to:
obtaining a message from a source node (301);
adding a reliability measurement field (302) in the message (301), wherein the reliability measurement field (302) comprises initial message count information (303); and
forwarding the message (301) to a network node (100) for reliability measurement;
the initial message count information (303) further comprises a second identity (401), the second identity (401) specifying a sequence number of the network node (300) between hops in the network for preparing a message for a reliability measure; the initial message count information (303) is used for detecting packet loss.
5. A network node (500) for performing reliability measurements of a network, the network node (500) being adapted to:
obtaining a message (501) from a network node (100) for reliability measurement, the message (501) comprising a reliability measurement field (502) comprising message count information (503) of one or more network nodes through which the message passes in the network;
Removing the reliability measurement field from the message (502);
providing the reliability measure field (502) to an evaluation node (700); and
forwarding the message (501) to a destination node;
the acquired message count information (503) further includes an identifier (601) of the acquired message count information (503), where the identifier (601) is obtained by adding 1 to an identifier of the message count information of a network node of a previous hop of the network node (100); the message count information (503) is used for detecting packet loss.
6. An evaluation node (700) for reliability measurement of flows in a network, characterized in that the evaluation node (700) is adapted to:
obtaining a first reliability measurement field (701) related to a first message and a second reliability measurement field (702) related to a second message from an egress network node (500), the first reliability measurement field (701) comprising first message count information (703), the second reliability measurement field (702) comprising second message count information (704); and
evaluating the reliability of the flow based on the first message count information (703) and the second message count information (704);
The identity (801) of the second message count information (704) is the same as the identity (802) of the first message count information (703);
the evaluation node (700) is further configured to detect packet loss based on a difference between a count value of the second packet count information (704) and a count value of the first packet count information (703).
7. A method (1200) for reliability measurement, the method (1200) comprising:
a network node (100) obtaining (1201) a message (101), the message (101) relating to a flow being transmitted in a network and comprising a reliability measurement field (102);
the network node (100) obtains (1202) message count information (103) of the network node (100), the message count information (103) representing a number of messages of a flow forwarded by the network node (100);
-the network node (100) inserting (1203) the message count information (103) of the network node (100) into the reliability measurement field (102); and
-the network node (100) forwarding (1204) the message (101) to a next hop of the network node (100);
the acquired message count information (103) further comprises a first identifier (201), wherein the first identifier (201) is obtained by adding 1 to the identifier of the message count information of the network node of the last hop of the network node (100); the message counting information (103) is used for detecting packet loss.
8. A method (1300) for preparing a message (301) for reliability measurement, the method (1300) comprising:
the network node (300) obtains (1301) a message (301) from a source node;
-the network node (300) adding (1302) a reliability measurement field (302) in the message (301), the reliability measurement field (302) comprising initial message count information (303); and
the network node (300) forwards (1303) the message (301) to a network node (300) for reliability measurement;
the initial message count information (303) further comprises a second identity (401), the second identity (401) specifying a sequence number of the network node (300) between hops in the network for preparing a message for a reliability measure; the initial message count information (303) is used for detecting packet loss.
9. A method (1400) for performing reliability measurements, the method (1400) comprising:
the network node (500) obtains (1401) a message (501) from the network node (100), the message (501) comprising a reliability measurement field (502) comprising message count information (503) of one or more network nodes through which the message passes in the network;
-the network node (500) removing (1402) the reliability measure field (502) from the message;
-the network node (500) providing (1403) the reliability measure field (502) to an evaluation node (700); and
-the network node (500) forwarding (1404) the message (501) to a destination node;
the acquired message count information (503) further includes an identifier (601) of the acquired message count information (503), where the identifier (601) is obtained by adding 1 to an identifier of the message count information of a network node of a previous hop of the network node (100); the message count information (503) is used for detecting packet loss.
10. A method (1500) for reliability measurement of flows in a network, the method (1500) comprising:
the evaluation node (700) obtains (1501) from the egress network node (500) a first reliability measurement field (701) associated with a first message and a second reliability measurement field (702) associated with a second message, the first reliability measurement field (701) comprising first message count information (703) and the second reliability measurement field (702) comprising second message count information (704); and
-the evaluation node (700) evaluating (1502) the reliability of the flow based on the first (703) and second (704) message count information;
the identity (801) of the second message count information (704) is the same as the identity (802) of the first message count information (703);
the evaluation node (700) also detects packet loss based on a difference between a count value of the second message count information (704) and a count value of the first message count information (703).
11. A computer readable storage medium comprising computer program code instructions executable by a computer for performing the method of any of claims 7-10 when the computer program code instructions are run on a computer.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2019/107128 WO2021051418A1 (en) | 2019-09-21 | 2019-09-21 | Methods and network nodes for reliability measurement |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114073049A CN114073049A (en) | 2022-02-18 |
| CN114073049B true CN114073049B (en) | 2023-11-17 |
Family
ID=74883097
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201980096090.XA Active CN114073049B (en) | 2019-09-21 | 2019-09-21 | Method and network node for reliability measurement |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114073049B (en) |
| WO (1) | WO2021051418A1 (en) |
Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6377550B1 (en) * | 1997-10-28 | 2002-04-23 | Texas Instruments Incorporated | Nested measurement period switch algorithm for flow control of available bit rate ATM communications |
| US6381216B1 (en) * | 1997-10-28 | 2002-04-30 | Texas Instruments Incorporated | Simplified switch algorithm for flow control of available bit rate ATM communications |
| KR20040074236A (en) * | 2003-02-17 | 2004-08-25 | 삼성전자주식회사 | Hop calculating methdo of mobile ip in ip network |
| CN1881908A (en) * | 2005-06-13 | 2006-12-20 | 华为技术有限公司 | Method for measuring MPLS network performance parameter |
| KR20070099172A (en) * | 2006-04-03 | 2007-10-09 | 엘지전자 주식회사 | Method of allocating and searching relay station region in mobile communications system |
| CN101699786A (en) * | 2009-10-15 | 2010-04-28 | 华为技术有限公司 | Method, device and system for detecting packet loss |
| CN101729303A (en) * | 2008-10-25 | 2010-06-09 | 华为技术有限公司 | Method and device for measuring network performance parameter |
| CN101789900A (en) * | 2009-11-19 | 2010-07-28 | 福建星网锐捷网络有限公司 | Multicast forwarding route query method, intermediate node and management node |
| CN102301651A (en) * | 2009-05-15 | 2011-12-28 | 华为技术有限公司 | method, device and system for measuring network performance |
| CN102904775A (en) * | 2012-09-29 | 2013-01-30 | 华为技术有限公司 | Method, apparatus and system for measuring network packet loss |
| CN102946330A (en) * | 2012-09-29 | 2013-02-27 | 华为技术有限公司 | Method, device and system for network packet loss measurement |
| US8489860B1 (en) * | 1997-12-22 | 2013-07-16 | Texas Instruments Incorporated | Mobile electronic device having a host processor system capable of dynamically canging tasks performed by a coprocessor in the device |
| CN103684923A (en) * | 2013-12-24 | 2014-03-26 | 华为技术有限公司 | Method for measuring packet loss and network device |
| CN105743711A (en) * | 2016-04-13 | 2016-07-06 | 华为技术有限公司 | Fault detection method and device for network path and network equipment |
| US9397913B1 (en) * | 2014-03-28 | 2016-07-19 | Juniper Networks, Inc. | Packet loss measurement in a distributed data plane |
| CN105830393A (en) * | 2013-12-17 | 2016-08-03 | 意大利电信股份公司 | Time measurement in a packet-switched communication network |
| CN106375158A (en) * | 2016-10-25 | 2017-02-01 | 华为技术有限公司 | Packet loss detection method, network device and system |
| CN106936655A (en) * | 2015-12-30 | 2017-07-07 | 阿里巴巴集团控股有限公司 | Chain circuit detecting method, device and the network equipment, controller |
| CN108259208A (en) * | 2016-12-29 | 2018-07-06 | 华为技术有限公司 | A kind of method and apparatus of detection messages dyeing bit swiping |
| CN109547288A (en) * | 2018-11-29 | 2019-03-29 | 中国科学院信息工程研究所 | A kind of unrelated forwarding Network Programmable flow measuring method of agreement |
| CN109981414A (en) * | 2019-03-29 | 2019-07-05 | 烽火通信科技股份有限公司 | The acquisition methods of number of dropped packets between mpls network node |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1209861A1 (en) * | 2000-11-22 | 2002-05-29 | Telefonaktiebolaget L M Ericsson (Publ) | Monitoring traffic in packet networks |
| US7457868B1 (en) * | 2003-12-30 | 2008-11-25 | Emc Corporation | Methods and apparatus for measuring network performance |
| US8725607B2 (en) * | 2004-01-30 | 2014-05-13 | The Clearing House Payments Company LLC | Electronic payment clearing and check image exchange systems and methods |
| WO2007044038A2 (en) * | 2004-12-13 | 2007-04-19 | Telcordia Technologies, Inc. | Lightweight packet-drop detection for ad hoc networks |
| US8271634B2 (en) * | 2009-04-30 | 2012-09-18 | Alcatel Lucent | Buffer system for managing service measurement requests |
| US8989020B2 (en) * | 2009-12-03 | 2015-03-24 | Verizon Patent And Licensing Inc. | Bidirectional forwarding detection (BFD) protocol extension for detecting random traffic dropping |
| CN106130825A (en) * | 2016-08-04 | 2016-11-16 | 华为技术有限公司 | A kind of data transmission quality detection method and device |
-
2019
- 2019-09-21 CN CN201980096090.XA patent/CN114073049B/en active Active
- 2019-09-21 WO PCT/CN2019/107128 patent/WO2021051418A1/en active Application Filing
Patent Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6377550B1 (en) * | 1997-10-28 | 2002-04-23 | Texas Instruments Incorporated | Nested measurement period switch algorithm for flow control of available bit rate ATM communications |
| US6381216B1 (en) * | 1997-10-28 | 2002-04-30 | Texas Instruments Incorporated | Simplified switch algorithm for flow control of available bit rate ATM communications |
| US8489860B1 (en) * | 1997-12-22 | 2013-07-16 | Texas Instruments Incorporated | Mobile electronic device having a host processor system capable of dynamically canging tasks performed by a coprocessor in the device |
| KR20040074236A (en) * | 2003-02-17 | 2004-08-25 | 삼성전자주식회사 | Hop calculating methdo of mobile ip in ip network |
| CN1881908A (en) * | 2005-06-13 | 2006-12-20 | 华为技术有限公司 | Method for measuring MPLS network performance parameter |
| KR20070099172A (en) * | 2006-04-03 | 2007-10-09 | 엘지전자 주식회사 | Method of allocating and searching relay station region in mobile communications system |
| CN101729303A (en) * | 2008-10-25 | 2010-06-09 | 华为技术有限公司 | Method and device for measuring network performance parameter |
| CN102301651A (en) * | 2009-05-15 | 2011-12-28 | 华为技术有限公司 | method, device and system for measuring network performance |
| CN101699786A (en) * | 2009-10-15 | 2010-04-28 | 华为技术有限公司 | Method, device and system for detecting packet loss |
| CN101789900A (en) * | 2009-11-19 | 2010-07-28 | 福建星网锐捷网络有限公司 | Multicast forwarding route query method, intermediate node and management node |
| CN102946330A (en) * | 2012-09-29 | 2013-02-27 | 华为技术有限公司 | Method, device and system for network packet loss measurement |
| CN102904775A (en) * | 2012-09-29 | 2013-01-30 | 华为技术有限公司 | Method, apparatus and system for measuring network packet loss |
| CN105830393A (en) * | 2013-12-17 | 2016-08-03 | 意大利电信股份公司 | Time measurement in a packet-switched communication network |
| CN103684923A (en) * | 2013-12-24 | 2014-03-26 | 华为技术有限公司 | Method for measuring packet loss and network device |
| US9397913B1 (en) * | 2014-03-28 | 2016-07-19 | Juniper Networks, Inc. | Packet loss measurement in a distributed data plane |
| CN106936655A (en) * | 2015-12-30 | 2017-07-07 | 阿里巴巴集团控股有限公司 | Chain circuit detecting method, device and the network equipment, controller |
| CN105743711A (en) * | 2016-04-13 | 2016-07-06 | 华为技术有限公司 | Fault detection method and device for network path and network equipment |
| CN106375158A (en) * | 2016-10-25 | 2017-02-01 | 华为技术有限公司 | Packet loss detection method, network device and system |
| CN108259208A (en) * | 2016-12-29 | 2018-07-06 | 华为技术有限公司 | A kind of method and apparatus of detection messages dyeing bit swiping |
| CN109547288A (en) * | 2018-11-29 | 2019-03-29 | 中国科学院信息工程研究所 | A kind of unrelated forwarding Network Programmable flow measuring method of agreement |
| CN109981414A (en) * | 2019-03-29 | 2019-07-05 | 烽火通信科技股份有限公司 | The acquisition methods of number of dropped packets between mpls network node |
Non-Patent Citations (2)
| Title |
|---|
| Grid-based directed diffusion for wireless sensor networks;毕嘉娜;;High Technology Letters(第04期);全文 * |
| 基于LabVIEW和C语言的1553B串行通讯系统;赵昶宇;于平;李东景;;光机电信息(第06期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114073049A (en) | 2022-02-18 |
| WO2021051418A1 (en) | 2021-03-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10063440B2 (en) | Method and system for measuring packet loss | |
| US8054744B1 (en) | Methods and apparatus for flow classification and flow measurement | |
| US6363056B1 (en) | Low overhead continuous monitoring of network performance | |
| EP2884697B1 (en) | Measuring method, device and system for network packet loss | |
| US8270305B2 (en) | Node device, node system, and method and program for changing statistic information management table used for the node device | |
| US10129115B2 (en) | Method and system for network monitoring using signature packets | |
| US20070064611A1 (en) | Method for monitoring packet loss ratio | |
| US20050281259A1 (en) | Method of generating a monitoring datagram | |
| CN108370333B (en) | System, method and node for performance measurement in a segmented routing network | |
| US8165019B2 (en) | Indirect measurement methodology to infer routing changes using statistics of flow arrival processes | |
| US11082316B2 (en) | Performance measurement in a packet-switched communication network | |
| EP2016712B1 (en) | Nat and proxy device detection | |
| EP3101844B1 (en) | Packet loss detection method, apparatus, and system | |
| CN108259208B (en) | Method and equipment for detecting message dye bit conflict | |
| CN105991338A (en) | Network operation and maintenance management method and device | |
| CN114430386A (en) | Method and related device for detecting multicast service flow | |
| US11165671B2 (en) | Performance measurement in a packet-switched communication network | |
| CN114073049B (en) | Method and network node for reliability measurement | |
| CN110266726A (en) | A kind of method and device identifying DDOS attack data flow | |
| CN113810295A (en) | Path detection method, device and system | |
| CN114465897A (en) | Method, device and system for monitoring data packets in service flow | |
| US11784895B2 (en) | Performance measurement in a packet-switched communication network | |
| JP2004032377A (en) | Method and system for estimating bottle neck and computer readable recording medium recorded with program of that method | |
| WO2021051419A1 (en) | Network node for performance measurement | |
| JP2005110038A (en) | Congestion detecting device, and method for detecting congestion of tcp traffic, and program |
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 |