CN113812119B - Network node for performance measurement - Google Patents
Network node for performance measurement Download PDFInfo
- Publication number
- CN113812119B CN113812119B CN201980096092.9A CN201980096092A CN113812119B CN 113812119 B CN113812119 B CN 113812119B CN 201980096092 A CN201980096092 A CN 201980096092A CN 113812119 B CN113812119 B CN 113812119B
- Authority
- CN
- China
- Prior art keywords
- performance
- network node
- packet
- performance indicator
- indicator field
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0852—Delays
-
- 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/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- 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
-
- 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/16—Threshold monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/16—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence
-
- 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/10—Active monitoring, e.g. heartbeat, ping or trace-route
- H04L43/106—Active monitoring, e.g. heartbeat, ping or trace-route using time related information in packets, e.g. by adding timestamps
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present invention relates to the field of computer networks and performance measurement in such networks. The performance measurement is performed by the network node via a header having a constant size. Accordingly, the present invention provides a network node for performance measurement, wherein the network node is configured to obtain a message comprising a performance measurement header having a performance indicator field of a fixed length; updating the performance indicator field based on performance measurements performed in the network node without changing a length of the performance indicator field; and forwarding the packet to a network node.
Description
Technical Field
The present invention relates to computer networking technology and performance measurement in such networks. In particular, the present invention relates to a network node for performance measurement by means of a constant size header.
Background
Performance measurement and network telemetry are key capabilities of communication networks. Monitoring network performance is important for the detection of faults, network congestion or anomalies. Furthermore, performance measurement and telemetry are key functions of autonomous networks, which have been a rapidly growing domain in the past few years.
Performance measurements typically require overhead on network resources because the measurements and telemetry require at least one of: a dedicated packet is used to measure the network, or information related to the measurement is piggybacked on a data packet (in-band network telemetry (INT) and in-band operation management and maintenance (IOAM) are two examples of this method). In multi-hop measurement, when measuring multiple nodes on a network path, a method is generally used in which each hop on the network path pushes measurement-related data onto a data packet.
The problem with this approach is that the amount of overhead on each data packet increases as the number of hops of the network path increases, thus creating significant overhead on paths with a large number of hops.
Disclosure of Invention
In view of the above, embodiments of the present invention aim to improve conventional performance measurement solutions.
The present invention aims to provide a measurement solution for multi-hop measurements with low measurement overhead. The measurement overhead may specifically not depend on the number of hops.
This object is achieved by the 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 present invention provides a network node for network performance measurement, wherein the network node is configured to obtain a packet, the packet being transmitted in the network and comprising a performance measurement header having a performance indicator field of a fixed length; updating the performance indicator field based on performance measurements performed in the network node without changing a length of the performance indicator field; and forwarding the packet to a next hop of the network node.
This ensures that the overhead allocated to the performance measurement remains unchanged.
In particular, the network node for performance measurement may also be referred to as a transit node or a forwarding node. However, the network node may also be referred to as an ingress node or an egress node.
In particular, the network 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 performance indicator field may comprise a value representing performance on the path. In particular, the performance indicator field may be updated by each node on the path to reflect the updated performance.
In particular, the value of the performance indicator field may relate to the latency of the current packet in the current network node (i.e. the network node used for performance measurement). In particular, the value of the performance indicator field may relate to the fill level of the queue currently enqueued by the packet.
In an implementation manner of the first aspect, the network node is further configured to update the performance index field based on a current value of the performance index field and based on a performance index of the packet measured by the network node, or based on a current value of the performance index field and based on a performance index of the network node.
This is advantageous because the performance measurements can be taken taking into account both the state of the packets in the network node and the state of the network node itself.
In particular, the performance indicator of the network node may be a current state of a queue of the network node.
In yet another implementation form of the first aspect, the network node is further configured to update the performance indicator field based on a present value applied to the performance indicator field and/or a result of at least one function applied to a performance indicator of the packet measured by the network node.
This ensures that a function can be used that provides an output value of the same size as the corresponding input value.
In particular, the function may be an identity function, a scale function, a moving average function, a weighted moving average function or an exponentially weighted moving average function.
In yet another implementation form of the first aspect, the network node updating the performance indicator field based on the performance measurements performed in the network node without changing the length of the performance indicator field comprises the length of the performance indicator field after updating being the same as the length of the performance indicator field before updating.
In particular, a predefined number of bits may be allocated for the fixed length of the performance indicator field. In particular, updating the performance indicator field without changing the length of the performance indicator field means that the number of bits allocated to the performance indicator field after updating is the same as the number of bits allocated to the performance indicator field before updating.
In yet another implementation form of the first aspect, the performance measurement header further comprises a sequence number field and/or a timestamp field.
This ensures that more information is available for performance measurement.
In yet another implementation form of the first aspect, the network node is further configured to provide the performance measurement header to an evaluation device.
This ensures that an external evaluation device, which may be referred to as a detection device, can be used in combination with the network node.
This may be done in particular for the current packet in the network node before and/or after updating the performance indicator field.
In particular, the network node may be configured to provide the performance measurement header to the evaluation device together with the message.
In particular, the network node may be configured to provide the performance measurement header to the evaluation device together with the truncated portion of the packet.
In a further implementation form of the first aspect, the network node is further configured to remove the performance measurement header from the packet and forward the packet without the performance measurement header.
This ensures that the network node can be used to implement the egress node that terminates the performance measurement.
In particular, the message may be forwarded to a destination indicated in the message.
In yet another implementation manner of the first aspect, the network node is further configured to receive the packet without the performance measurement header, and add the performance measurement header to the received packet to obtain the packet including the performance measurement header.
This ensures that the network node can be used to implement an ingress node that turns on performance measurements.
In yet another implementation form of the first aspect, the network node is further configured to evaluate a performance of the packet based on the performance measurement header.
This ensures that the network node can also implement the functionality of the evaluation device (which may be referred to as the detection device) itself.
In particular, the evaluation of the performance of the network packet may include comparing the value of the performance indicator field to a predefined threshold.
In particular, the evaluation of the performance of the network packet may include comparing a current value of the performance indicator field with at least one previous value of the performance indicator field.
In particular, comparing the current value of the performance indicator field with at least one previous value of the performance indicator field includes, for example, applying dynamic classification based on a machine learning domain.
In particular, after the performance of the network packet is evaluated, the evaluation result is provided to the management device.
In a further implementation manner of the first aspect, the performance measurement header further includes a sequence number field and/or a time stamp field, and the network node is further configured to evaluate the performance of the packet according to the sequence number field and/or the time stamp field.
This ensures that the evaluation can also be based on the sequence number field and/or the timestamp field.
In particular, the evaluation device may be further configured to detect packet loss based on the sequence number field.
A second aspect of the present invention provides a method for performance measurement of a network, wherein the method comprises the steps of: a network node obtaining a message, wherein the message is transmitted in the network and comprises a performance measurement header having a fixed length performance indicator field; the network node updating the performance indicator field based on performance measurements performed in the network node without changing a length of the performance indicator field; and the network node forwards the packet to a next hop of the network node.
In an implementation manner of the second aspect, the method further includes the network node updating the performance indicator field based on the present value of the performance indicator field and based on the performance indicator of the packet measured by the network node, or based on the present value of the performance indicator field and based on the performance indicator of the network node.
In a further implementation form of the second aspect, the method further comprises the network node updating the performance indicator field based on a present value applied to the performance indicator field and/or a result of at least one function applied to a performance indicator of the packet measured by the network node.
In yet another implementation of the second aspect, the network node updating the performance indicator field based on the performance measurements performed in the network node without changing the length of the performance indicator field comprises the length of the performance indicator field after the updating being the same as the length of the performance indicator field before the updating.
In yet another implementation form of the second aspect, the performance measurement header further comprises a sequence number field and/or a timestamp field.
In a further implementation form of the second aspect, the method further comprises the network node providing the performance measurement header to an evaluation device.
In yet another implementation of the second aspect, the method further comprises the network node removing the performance measurement header from the packet and forwarding the packet without the performance measurement header.
In a further implementation manner of the second aspect, the method further includes the network node receiving the packet without the performance measurement header, and adding the performance measurement header to the received packet to obtain the packet including the performance measurement header.
In yet another implementation form of the second aspect, the method further comprises the network node evaluating performance of the packet based on the performance measurement header.
In yet another implementation form of the second aspect, the performance measurement header further includes a sequence number field and/or a timestamp field, and the method further comprises the network node evaluating the performance of the packet according to the sequence number field and/or the timestamp field.
The second aspect and its implementations comprise the same advantages as the first aspect and its respective implementations.
In summary, embodiments of the present invention provide a solution for in-band measurements that allows multi-hop measurements, but uses constant length performance data. In this case, "in-band measurement" refers to a measurement method of piggybacking performance-related data onto a data message. The fixed length data is carried along with the data packets on their paths and may be updated by the intermediate network devices to reflect their performance. A detection module may be used at the end of the path to detect performance degradation.
It should be noted that all devices, elements, units and methods described herein may be implemented in software or hardware elements or any combination thereof. All steps performed by the various entities described in the present application and the functions described to be performed by the various entities are intended to indicate that the respective entities are adapted or arranged to perform the respective steps and functions. Although in the following description of specific embodiments specific functions or steps performed by an external entity are not reflected in the description of specific elements of the entity performing the specific steps or functions, it should be clear to a person skilled in the art that these methods and functions may be implemented in respective hardware or software elements or any combination thereof.
Drawings
The aspects of the invention described above and the forms of its implementation are explained in the following description of specific embodiments in conjunction with the accompanying drawings, in which:
fig. 1 is a schematic diagram of a network node for performance measurement according to an embodiment of the present invention;
fig. 2 shows a schematic diagram of a network node for performance measurement according to an embodiment of the present invention in more detail;
FIG. 3 illustrates an example of operation provided by the present invention;
FIG. 4 is a diagram illustrating a message provided by the present invention;
FIG. 5 is a diagram illustrating a plurality of messages provided by the present invention;
fig. 6 shows a schematic diagram of a method provided by an embodiment of the invention.
Detailed Description
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 performance measurements in a network.
For performance measurement, the network node 100 obtains a packet 101. The message 101 comprises a performance measurement header 102 and a fixed length performance indicator field 103. That is, the length of the performance indicator field 103 does not change throughout the processing of the performance measurement to which it applies. The packet 101 may be obtained from other network nodes prior in the path of the packet 101. The other network node has for example added the performance measurement header 102 and the fixed length performance indicator field 103 to the packet 101. Thus, the network node may also be referred to as an ingress node.
The network node 100 then updates the performance indicator field 103 based on the performance measurements 104 performed in the network node 100 without changing the length of the performance indicator field 103. This means that the length of the performance indicator field 103 is the same before and after the update. In particular, the bit size of the indicator field 103 is not changed by the update, i.e. before and after the update is the same. Thereby obtaining a constant header size and avoiding an increase in overhead.
The network node 100 then forwards the packet 101 to another network node, e.g., along the expected path of the packet 101. In the further network node, further processing may be applied to the packet 101 (e.g. the performance measurement may be terminated at the node). Thus, the node may also be referred to as an egress node. When the network node 100 forwards the packet 101 from an ingress node to an egress node, the network node 100 may also be referred to as a transit node.
The message 101 may generally be any type of network message. In particular, the message 101 may be a data message, i.e. a message sent from a source host to a destination host. In particular, the packet 101 may be a control packet sent between network devices.
Fig. 2 shows a schematic diagram of a network node 100 according to 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 features and functions thereof.
As shown in fig. 2, the network node 100 may optionally update the performance indicator field 103 based on the current value of the performance indicator field 103 and the performance indicator 201 of the packet 101 measured by the network node 100. That is, the network node 100 may read the current value of the performance indicator field 103, may obtain the performance indicator 201 (e.g., delay value) of the packet 101, and may then calculate a new value of the performance indicator field 103 that replaces the old value. The new value may be the same length as the old value, i.e. the new value may comprise the same number of bits as the old value.
Additionally or alternatively, the network node 100 may update the performance indicator field 103 based on the present value of the performance indicator field 103 and based on the performance indicator 202 of the network node 100. That is, the network node 100 may read the current value of the performance indicator field 103, may obtain the performance indicator 202 of the network node 100 (e.g., a delay value such as a fill level of a packet queue), and may then calculate a new value of the performance indicator field 103 that replaces the old value. The new value may be the same length as the old value, i.e. the new value may comprise the same number of bits as the old value.
Further optionally, the network node 100 may update the performance indicator field 103 based on a present value applied to the performance indicator field 103 and a result of at least one function applied to the performance indicator 201 or the performance indicator 202. In particular, the function ensures that the length of the performance indicator field 103 remains unchanged.
The network node 100 may specifically implement an update algorithm, and according to the update algorithm, a node on a path (i.e., a transit node, and optionally, an ingress node or an egress node) may update the performance indicator field 103. The performance indicator field 103 may be updated from OldValue to NewValue according to the following algorithm: newValue = f (OldValue) + g (m), where m is the value of the performance indicator 201 or the performance indicator 202, and f () and g () are two functions used in the process.
One example of a possible performance indicator 201 is the latency of the current packet in the current device. One example of a possible performance indicator 202 is the fill level of the queue currently queuing packets.
For example, the performance indicator 201 may be the accumulated delay over the path, i.e. the sum of the delays of the network nodes 100 over the path. At this time, the update algorithm of each hop is as follows: newValue = OldValue + CurrentHopLatency, wherein: f (x) = x and g (x) = x.
However, f (x) or g (x) may be any one of an identity function, a scale function, a moving average function, a weighted moving average function, or an exponentially weighted moving average function. Further examples of functions f (x) and g (x) are:
identity function:
f(x)＝x，g(x)＝x
in this case, the performance indicator is simply the sum of the indicator values of the hops of the message 101.
Right-shifted by 4 bits:
f(x)＝x，g(x)＝x>>4
this allows scaling the performance index value to 2^4=16 hops.
Exponentially weighted moving average function:
f(x)＝x–x>>5，g(x)＝x>>5
NewValue＝(1–2^–5)*OldValue+2^–5*NewValue
as shown in fig. 2, the performance measurement header 102 may optionally include a sequence number field 203 and/or a timestamp field 204. The sequence number field 203 and/or the timestamp field 204 may assist in performance measurement and evaluation, as described below.
Further optionally, the network node 100 may provide the performance measurement header 102 to an evaluation device. That is, the network node may directly forward the information required for the performance measurement to the evaluation device without another device having to do so.
In other words, the network node 100 also allows hop-by-hop derivation. That is, each network node 100 on the path, upon receiving the packet 101 with the performance measurement header 102, may export a detailed set of performance related fields to the detection module and/or may append a sequence number field 203 or a timestamp field 204 to the performance measurement header 102. The detection module may then use the detailed performance information for further performance analysis. The sequence number field 203 or the timestamp field 204 may be used to correlate information in the same packet 101 received from different network nodes 100.
Further optionally, the network node 100 may remove the performance measurement header 102 from the packet 101 and forward the packet 101 without the performance measurement header 102. That is, the packet 101 may be forwarded to its intended destination without the performance measurement header 102.
In other words, the network node 100 may also perform the function of an egress node, removing performance data from the packet and forwarding the packet to its destination. That is, the egress node may also optionally update the performance indicator field and export the performance data to the detection module.
Further optionally, the network node 100 may receive the packet 101 without the performance measurement header 102, and add the performance measurement header 102 to the received packet 101, to obtain the packet 101 including the performance measurement header 102.
In other words, the network node 100 may also fulfill the function of an ingress node that prepares the packet 101 for performance measurement by adding the performance measurement header 102 to the received packet 101 that does not already contain the performance measurement header 102. In other words, the ingress node may push the following performance data into all or a subset of the packets 101 forwarded through it: a performance measurement header 102, a performance indicator field 103 (which is updated hop-by-hop, is a value that represents performance on the path, and may be updated by each node on the path to reflect the updated performance), a sequence number field (specifically assigned by the ingress node and not altered by other subsequent nodes), a timestamp field.
Further optionally, the network node 100 may evaluate the performance of the packet 101 based on the performance measurement header 102. That is, the network node 100 may also implement the functionality of the evaluation module (which may also be referred to as the detection module) without the need for another device. In other words, the detection module may be used to detect performance problems or performance degradation. This module may be an external node or an internal module in said network node 100.
The detection module may be configured to detect packet loss by comparing the sequence number of the current packet with a previous sequence number. If there is no packet loss, the sequence number difference should be 1 (i.e. the difference is the number of packet loss plus 1). The detection module may detect a performance degradation by processing the performance indicator field 103 using a detection function. The detection function may be one of the following: compare the performance indicator field 103 to a configurable threshold value indicating a problem; or compare the current value to a previous value and apply dynamic classification (e.g., using machine learning).
Once packet loss or performance degradation (or both) is detected, the detection module may report to a user or a management system, or may trigger fine-grained measurements to detect the location of a problem, such as IOAM, or may take corrective action, such as reconfiguring a network path.
Furthermore, since the performance measurement header 102 may comprise a sequence number field 203 and/or a timestamp field 204, the network node 100 may optionally also evaluate the performance of the packet 101 based on the sequence number field 203 and/or the timestamp field 204. The sequence number field 203 and/or the timestamp field 204 are not necessarily included in the performance measurement header 102. However, they may be separate parts of the performance data (i.e. separate fields in the performance data) together with the header.
Fig. 3 shows an example scenario for running several instances of network node 100. In fig. 3, the network node 100A implements a transit node, the network node 100B implements an ingress node, the network node 100C implements an egress node, and the network node 100D implements a detection module.
As shown in fig. 3, performance measurements are made between the ingress node 100B and the egress node 100C. The ingress node 100B is the first node on the path participating in the measurement and the egress node 100C is the last node on the path participating in the measurement. The ingress node 100C may push measurement data into the packet 101. The egress node 100C may remove the measurement data pushed by the ingress node 100B and forward the data packet to the destination. Transit nodes 100A are nodes on the path that can push additional data or update existing data (although only one transit node 100A is shown, there may be multiple transit nodes 100A on the path). The detection module 100D is a module for detecting performance degradation. It may run on a remote server or may run locally, e.g. as a module within one of the nodes 100A, 100B, 100C. The network device of fig. 3 may be a switch, router, middlebox, NIC, or any device that forwards messages. Although only the egress node 100C is shown as being capable of providing information to the detection module 100D, any other node along the path (e.g., the ingress node 100B or the transit node 100A) may also provide information to the detection module 100D.
Fig. 4 shows a message 101 with performance data comprising a performance measurement header 102 and a performance indicator field 103. The performance data shown in fig. 4 also contains an optional sequence number field 203 and an optional timestamp field 204.
Figure 5 shows a message containing performance data pushed by an ingress node (containing, among other things, the performance measurement header 102). As shown in the second line of said, the data can be pushed together with the tunnel header (e.g. VXLAN-GPE) or as an extension of the existing header in said message, e.g. an IPv6 extension header, as shown in the third line. The first row shows a normal message without the performance data.
Fig. 6 illustrates a method 600 provided by an embodiment of the invention. The method 600 is for performance measurement, comprising the steps of: the network node 100 obtains 601 a message 101, wherein the message 101 comprises a performance measurement header 102 having a fixed length of a performance indicator field 103. The method further comprises the steps of: the network node 100 updates 602 the performance indicator field 103 based on performance measurements 104 performed in the network node 100 without changing the length of the performance indicator field 103. The method further comprises the steps of: the network node 100 forwards 603 the packet 101 to the network node.
The main difference between the present invention and the existing field scheme is that the present invention provides multi-hop in-band measurement data, and simultaneously keeps the message overhead constant, independent of the number of hops in the network. The invention allows the use of a generic hop-by-hop update function such that multi-hop information is represented by fixed length fields. Furthermore, the invention employs an innovative combination of two components, while maintaining a constant overhead:
single-hop measurement data (sequence number or timestamp) and multi-hop measurement data (performance indicator). The invention also provides a detection module which can be used as a trigger for fine-grained measurement with higher cost. The measurement data according to the invention may for example be extended to contain more types of information while maintaining a fixed length. Another possible implementation of the invention is to use only multi-hop measurement data and not single-hop measurement data (sequence numbers or time stamps).
The invention has been described in connection with various embodiments and implementations as examples. Other variations will be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the disclosure, and the independent claims. In the claims and the description the wording "comprising" does not exclude other elements or steps and "a" or "an" does not exclude a plurality. A single element or other unit may fulfill the functions of several entities or items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
Claims (10)
1. A network node (100) for performance measurement, the network node (100) being configured to:
obtaining a message (101), wherein the message (101) comprises a performance measurement header (102) having a fixed length of a performance indicator field (103);
updating the performance indicator field (103) based on a present value applied to the performance indicator field (103) and/or a result of at least one function applied to a performance indicator (201) of the packet (101) measured by the network node (100) and/or a performance indicator (202) of the network node (100) without changing a length of the performance indicator field (103); and
forwarding the packet (101) to a next hop of the network node (100).
2. The network node (100) according to the preceding claim 1, wherein the network node (100) updating the performance indicator field (103) based on the performance measurements (104) performed in the network node (100) without changing the length of the performance indicator field (103) comprises the length of the performance indicator field (103) after updating being the same as the length of the performance indicator field (103) before updating.
3. The network node (100) according to any of the preceding claims 1 or 2, wherein the performance measurement header (102) further comprises a sequence number field (203) and/or a timestamp field (204).
4. The network node (100) according to claim 1 or 2, further configured to provide the performance measurement header (102) to an evaluation device.
5. The network node (100) according to claim 1 or 2, further configured to remove the performance measurement header (102) from the packet (101) and forward the packet (101) without the performance measurement header (102).
6. The network node (100) according to claim 1 or 2, further configured to:
-receiving said message (101) without said performance measurement header (102); and
adding the performance measurement header (102) to the received message (101) to obtain the message (101) containing the performance measurement header (102).
7. The network node (100) according to claim 1 or 2, configured to evaluate the performance of the packet (101) based on the performance measurement header (102).
8. The network node (100) according to claim 7, wherein the performance measurement header (102) further comprises a sequence number field (203) and/or a timestamp field (204), and wherein the network node (100) is further configured to evaluate the performance of the packet (101) based on the sequence number field (203) and/or the timestamp field (204).
9. A method (600) for performance measurement of a network, the method (600) comprising the steps of:
a network node (100) obtaining (601) a message (101), wherein the message (101) is transmitted in the network and comprises a performance measurement header (102) having a fixed length of a performance indicator field (103);
the network node (100) updating the performance indicator field (103) based on a present value applied to the performance indicator field (103) and/or a result of at least one function applied to a performance indicator (201) of the packet (101) measured by the network node (100) and/or a performance indicator (202) of the network node (100) without changing a length of the performance indicator field (103); and
the network node (100) forwards (603) the packet (101) to a next hop of the network node.
10. A computer-readable storage medium comprising computer program code instructions executable by a computer,
for performing the method of claim 9 when the computer program code instructions are run on a computer.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2019/107129 WO2021051419A1 (en) | 2019-09-21 | 2019-09-21 | Network node for performance measurement |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113812119A CN113812119A (en) | 2021-12-17 |
| CN113812119B true CN113812119B (en) | 2023-04-18 |
Family
ID=74883104
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201980096092.9A Active CN113812119B (en) | 2019-09-21 | 2019-09-21 | Network node for performance measurement |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113812119B (en) |
| WO (1) | WO2021051419A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116781499A (en) * | 2022-03-11 | 2023-09-19 | 华为技术有限公司 | Network performance measurement method, system and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7376122B2 (en) * | 2004-02-23 | 2008-05-20 | Microsoft Corporation | System and method for link quality source routing |
| US20080159287A1 (en) * | 2006-12-29 | 2008-07-03 | Lucent Technologies Inc. | EFFICIENT PERFORMANCE MONITORING USING IPv6 CAPABILITIES |
| CN106789730B (en) * | 2016-12-29 | 2020-02-11 | 杭州迪普科技股份有限公司 | Method and device for processing fragment message |
| EP3665866B1 (en) * | 2017-08-08 | 2022-11-16 | Telefonaktiebolaget LM Ericsson (publ) | Scalable network path tracing |
| CN109981457B (en) * | 2017-12-27 | 2021-09-07 | 华为技术有限公司 | Message processing method, network node and system |
-
2019
- 2019-09-21 WO PCT/CN2019/107129 patent/WO2021051419A1/en active Application Filing
- 2019-09-21 CN CN201980096092.9A patent/CN113812119B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021051419A1 (en) | 2021-03-25 |
| CN113812119A (en) | 2021-12-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11575559B1 (en) | Monitoring and detecting causes of failures of network paths | |
| KR102569305B1 (en) | Data message detection method, device and system | |
| EP3188412B1 (en) | Method, apparatus, and system for implementing delay measurement | |
| JP5646090B2 (en) | Traceroute_delay diagnostic command | |
| EP2245801B1 (en) | Network characterisation | |
| US20050232227A1 (en) | Method and apparatus for characterizing an end-to-end path of a packet-based network | |
| US9104543B1 (en) | Determining locations of network failures | |
| EP3369213B1 (en) | Performance measurement in a packet-switched communication network | |
| US10659327B2 (en) | Network traffic analysis | |
| US11133980B2 (en) | Detecting sources of computer network failures | |
| EP3188413B1 (en) | Method, apparatus, and system for implementing packet loss detection | |
| EP3474499A1 (en) | Network performance detection method and apparatus | |
| EP3529952B1 (en) | Performance measurement in a packet-switched communication network | |
| JP4311675B2 (en) | Quality degradation isolation method and apparatus | |
| CN113812119B (en) | Network node for performance measurement | |
| US6850530B1 (en) | Methods and apparatus for providing and obtaining resource usage information | |
| EP2957069B1 (en) | Method and network entity for evaluating a link between a first network node and a second network node | |
| US10666548B2 (en) | Method for intelligent multi-hop overlay routing | |
| US20170064489A1 (en) | Network system, method for determining communication quality, and analysis apparatus | |
| US20230009602A1 (en) | Path Assurance in Shared Transport | |
| US10462032B2 (en) | Probing a network | |
| JP2005277834A (en) | Apparatus, program, and system for estimating network congestion location | |
| CN114073053A (en) | Network node for supporting performance evaluation through performance bitmap | |
| Popescu et al. | Measurement of one-way transit time in IP routers | |
| JP2006013876A (en) | Traffic matrix generating apparatus and computer program thereof, and communication apparatus and computer program thereof |
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 |