CN117376200A - Service flow packet loss detection method, terminal equipment and storage medium - Google Patents
Service flow packet loss detection method, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN117376200A CN117376200A CN202210767944.6A CN202210767944A CN117376200A CN 117376200 A CN117376200 A CN 117376200A CN 202210767944 A CN202210767944 A CN 202210767944A CN 117376200 A CN117376200 A CN 117376200A
- Authority
- CN
- China
- Prior art keywords
- packet loss
- service flow
- flow identifier
- identifier
- target
- 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.)
- Pending
Links
- 238000001514 detection method Methods 0.000 title claims abstract description 104
- 238000013507 mapping Methods 0.000 claims abstract description 117
- 238000000034 method Methods 0.000 claims abstract description 53
- 230000005540 biological transmission Effects 0.000 claims description 45
- 230000006870 function Effects 0.000 claims description 21
- 238000004590 computer program Methods 0.000 claims description 12
- 238000005538 encapsulation Methods 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims 1
- 238000007726 management method Methods 0.000 description 23
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000008439 repair process Effects 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 238000005070 sampling Methods 0.000 description 3
- 125000004122 cyclic group Chemical group 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 208000033748 Device issues Diseases 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000000691 measurement method Methods 0.000 description 1
- 238000010295 mobile communication 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
- 230000006855 networking Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 239000004065 semiconductor Substances 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
Landscapes
- Engineering & Computer Science (AREA)
- Environmental & Geological Engineering (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a service flow packet loss detection method, terminal equipment and a storage medium. The method comprises the following steps: responding to a packet loss detection starting instruction issued by network management equipment, and acquiring a packet loss service flow identifier carried by at least one packet loss service flow; the packet loss detection starting instruction comprises: at least one service flow identifier to be detected; the packet loss service flow is a service flow with a service flow identifier comprising any service flow identifier to be detected and packet loss; and respectively acquiring the packet loss type mapped by each packet loss service flow identifier by inquiring the packet loss classification mapping table.
Description
Technical Field
The present invention relates to communications technologies, and in particular, to a method for detecting packet loss of a service flow, a terminal device, and a storage medium.
Background
In-band Operation, administration and Maintenance (IOAM) is a real traffic flow-based flow-following measurement technology, and is implemented by sampling traffic flow In real time and at high speed, adding IOAM information into sampled data, and then actively sending the sampled data to an analyzer for analysis, so as to realize real-time sensing and detection of network Operation state.
Compared with the traditional detection technology, the IOAM has the advantages of real-time monitoring, real-time health condition of the network and the like, and is more beneficial to the maintenance of a daily network; terminal equipment which can quickly sense the packet loss of the service flow in the service transmission path, but cannot accurately detect the specific reason of the packet loss of the service flow.
Disclosure of Invention
The application mainly aims to provide a service flow packet loss detection method, terminal equipment and storage medium, and aims to accurately detect the packet loss type of service flow packet loss so as to quickly repair packet loss faults and ensure the accuracy of service flow transmission.
In order to achieve the above objective, the present application provides a method for detecting packet loss of a service flow, which is applied to a target terminal device, where the target terminal device is a terminal device that packet loss occurs in a service flow to be detected in a service transmission path; the method comprises the following steps:
responding to a packet loss detection starting instruction issued by network management equipment, and acquiring a packet loss service flow identifier carried by at least one packet loss service flow; the packet loss detection starting instruction comprises: at least one service flow identifier to be detected; the packet loss service flow is a service flow with a service flow identifier comprising any service flow identifier to be detected and packet loss;
Respectively obtaining the packet loss type mapped by each packet loss service flow identifier by inquiring a packet loss classification mapping table;
and counting the packet loss quantity of the service flow to be detected transmitted by the target terminal equipment on each packet loss type.
In order to achieve the above object, the present application further provides a terminal device, including: the system comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor realizes the service flow packet loss detection method when executing the program.
In order to achieve the above object, the present application further provides a storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the above-mentioned method for detecting packet loss of a service flow.
With respect to the above examples and other aspects of the present application and their implementation, further description is provided in the accompanying description, detailed description and claims.
Drawings
Fig. 1 is a schematic structural diagram of a packet transport network for IOAM-based traffic packet loss detection according to an embodiment;
fig. 2 is a flowchart of a method for detecting packet loss of a service flow according to an embodiment;
fig. 3 is a schematic diagram of a method for detecting packet loss of an execution service flow of a target terminal device according to an embodiment;
Fig. 4 is a flowchart of a method for detecting packet loss of a service flow according to an embodiment;
fig. 5 is a schematic structural diagram of a transmission device according to an embodiment;
fig. 6 is a schematic hardware structure of a terminal device according to an embodiment.
Detailed Description
For the purposes of making the objects, technical solutions and advantages of the present application more apparent, embodiments of the present application will be described in detail hereinafter with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be arbitrarily combined with each other.
The steps illustrated in the flowchart of the figures may be performed in a computer system, such as a set of computer-executable instructions. Also, while a logical order is depicted in the flowchart, in some cases, the steps depicted or described may be performed in a different order than presented herein.
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
In the following description, suffixes such as "module", "component", or "unit" for representing elements are used only for facilitating the description of the present application, and have no specific meaning in themselves. Thus, "module," "component," or "unit" may be used in combination.
In-band Operation, administration and Maintenance (IOAM) is a real traffic flow-based flow-following measurement technique, and is implemented by sampling traffic flows In real time and at high speed, adding IOAM information into sampled data, and then actively sending the sampled data to an analyzer for analysis, so as to realize real-time sensing and detection of network Operation states. In the equipment of the engineering practical application networking environment, the traditional service flow packet loss detection method based on the IOAM can detect the service flow transmission condition of a service transmission path in real time by configuring the IOAM, can find whether the service data corresponding to a certain opening IOAM is normal or not in real time, and can locate the terminal equipment (namely the target terminal equipment) where the service flow in the service transmission path loses packets if the service flow transmission is abnormal, thereby facilitating the fault repair of the target terminal equipment where the packet loss occurs.
Fig. 1 is a schematic structural diagram of a packet transport network (Packet Transport Network, PTN) for IOAM-based traffic packet loss detection according to an embodiment. The PTN includes: the network management device 11, the service stream sending device 12, the plurality of terminal devices 13 and the service stream receiving device 14, wherein each terminal device 13 is a transmission node in the service transmission path. The network management equipment is respectively connected with the service flow sending equipment 12, each terminal equipment 13 and the service flow receiving equipment 14 and is used for carrying out information interaction with each terminal equipment 13 so as to realize control of the terminal equipment and sampling of the service flow; the traffic stream transmitting device 12 is arranged to generate traffic streams and the traffic stream receiving device 14 is arranged to receive traffic streams. The normal traffic flow transmission procedure in PTN is: the service flow sending device 12 sends the service flow to the service flow receiving device 14 through the terminal device of each transmission node in the preset service transmission path, specifically, the service flow flows in from the ingress port of the terminal device corresponding to the current transmission node, flows out through the egress port of the terminal device, and is sent to the ingress port of the terminal device corresponding to the next transmission node.
In the process of detecting packet loss of a service flow based on the IOAM, an identifier corresponding to the service flow to be detected (i.e. a service flow ID to be detected) is configured on the network management device 11, and a hop-by-hop detection function of the IOAM of the gateway device is started, and in the process that the service flow is sent from the service flow sending device 12 to the service flow receiving device 14 through the terminal device of each transmission node in the preset service transmission path, the service flow generated by the service flow sending device and the service flow received by the service flow receiving device are counted, whether packet loss occurs in the service flow is detected, and if packet loss occurs, the target terminal device of packet loss in the service flow can be positioned according to the service flow of an inlet port flow and the service flow of an outlet port of each terminal device. However, the conventional method for detecting packet loss of service flow based on IOAM can only locate the target terminal device of the service flow with packet loss, but there is no method for detecting the specific reason of packet loss, which definitely reduces the efficiency of fault repair.
Fig. 2 is a flowchart of a method for detecting packet loss of a service flow, as shown in fig. 2, where the method for detecting packet loss of a service flow provided in this embodiment may be applied to a target terminal device, where the target terminal device is a terminal device that is to detect packet loss of a service flow in a service transmission path, and the method includes the following steps:
Step 210: responding to a packet loss detection starting instruction issued by network management equipment, and acquiring a packet loss service flow identifier carried by at least one packet loss service flow; the packet loss detection starting instruction comprises: at least one service flow identifier to be detected; the packet loss service flow is a service flow whose service flow identifier contains any one of the service flow identifiers to be detected and which has packet loss.
All the service flows including the service flow identifier to be detected are the service flows to be detected, and the service flows to be detected can be understood as the service flows to be detected. In the transmission process of the transmission path, the service flow to be detected may have packet loss phenomenon; the service flow to be detected, in which packet loss occurs in the transmission path, is a packet loss service flow, i.e. the service flow to be detected includes: packet-lost traffic and/or non-packet-lost traffic. The type of the traffic to be detected is not particularly limited here, and may be, for example, a two-layer virtual private network L2VPN traffic or a three-layer virtual private network L3VPN traffic.
The target terminal device may be understood as a terminal device in which a packet loss occurs in a service flow to be detected in a service transmission path, and the target terminal device may be a terminal device corresponding to a first transmission node, any intermediate transmission node, or a last transmission node of the service transmission path.
The packet loss detection start instruction may be understood as an instruction for instructing the target terminal device to start the packet loss detection function, and the packet loss detection start instruction is not limited herein. The packet loss detection start instruction may include at least one service flow identifier to be detected. The packet loss detection starting instruction can be issued to the target terminal device after the network management device executes the IOAM hop-by-hop detection function to determine the target terminal device.
Specifically, the manner in which the user selects the service flow to be detected may be: and configuring one or more to-be-detected service flow identifiers in the network management equipment, and taking all the service flows containing the to-be-detected service flow identifiers in the service flow identifiers as to-be-detected service flows.
Because all the service flows including the service flow identifier to be detected are the service flows to be detected, and the packet loss service flow is the service flow to be detected, the method for determining the packet loss service flow can be as follows: and determining the service flow which contains any service flow identifier to be detected and has packet loss as the packet loss service flow.
Specifically, the target terminal device receives a packet loss detection instruction issued by the network management device, and responds to the packet loss detection instruction to start a packet loss detection function. After the packet loss detection function is started, the target terminal equipment determines the to-be-detected service flow transmitted by the target terminal equipment based on the to-be-detected service flow identifier in the packet loss detection starting instruction, and acquires the packet loss service flow identifier carried by each packet loss service flow according to one or more packet loss service flows of which the to-be-detected service flows are lost in the determination of the inflow flow of the inlet port and the outflow flow of the outlet port of the target terminal equipment.
In the service transmission path, the service flow to be detected is transmitted from the service flow sending device to the service flow receiving device through the terminal devices corresponding to the transmission nodes. The service flow to be detected may have packet loss on any one of the terminal devices, that is, the target terminal device where the packet loss of the service flow occurs may include at least one of the following: the first terminal device, the middle terminal device and the last terminal device in the service transmission path. Generally, in a service flow transmission process, a service flow is transmitted to a first terminal device in a service transmission path, the first terminal device encapsulates the service flow and then transmits the service flow to a next intermediate terminal device, the next intermediate terminal device continues to transmit the encapsulated service flow, and finally, the service flow is transmitted to a last terminal device, and the last terminal device decapsulates the encapsulated service flow. The method for acquiring the packet loss service flow identifier carried by the packet loss service flow is different for the encapsulated service flow and the non-encapsulated (or non-encapsulated) packet loss service flow. Based on the above, the method for the target terminal device to acquire the packet loss service flow identifier carried by at least one packet loss service flow includes:
step S211: and acquiring the packet loss service flow identifier carried by the first packet loss service flow based on the first acquisition mode.
Specifically, if the target terminal device is the first terminal device in the service transmission path, the packet loss service flow may be an unpackaged service flow; if the target terminal device is the last terminal device in the service transmission path, the packet loss service flow may be a decapsulated packet loss service flow after decapsulating the encapsulated service flow. Therefore, for the first packet loss service flow (i.e. the unpackaged packet loss service flow or the unpackaged packet loss service flow) transmitted by the target terminal device, the first mode is adopted to acquire the packet loss service flow identifier carried by the first packet loss service flow.
Step S212: acquiring a packet loss service flow identifier carried by a second packet loss service flow based on a second acquisition mode; and the second packet loss service flow is the packet loss service flow which has completed encapsulation.
Specifically, the terminal device is the first terminal device in the service transmission path, and at this time, the packet loss service flow may be not only an unpackaged service flow, but also a service flow that has already been packaged; if the target terminal equipment is the middle terminal equipment in the service transmission path, the packet loss service flow is the encapsulated service flow; if the target terminal device is the last terminal device in the service transmission path, the packet loss service flow may be the unpacked packet loss service flow after the unpacked service flow is unpacked, or the packet loss service flow which has been unpacked and has not been unpacked. Therefore, for the second packet loss service flow (i.e. the encapsulated packet loss service flow) transmitted by the target terminal device, the second mode is adopted to acquire the packet loss service flow identifier carried by the second packet loss service flow.
Optionally, the first obtaining manner includes: directly acquiring a packet loss service flow identifier carried by a packet loss service flow transmitted by target terminal equipment;
the second acquisition mode comprises the following steps: analyzing the second packet loss service flow transmitted by the target terminal equipment, and searching whether the analyzed second packet loss service flow contains an IOAM data guide tag or not; if the IOAM data guide label is included, determining a preset byte after analyzing a data message in the second packet loss service flow as a packet loss service flow identifier corresponding to the second packet loss service flow.
Specifically, for an unpackaged or unpackaged first packet loss service flow transmitted by the target terminal device, the target terminal device may directly obtain a packet loss service flow identifier carried in the first packet loss service flow. For the second packet loss service flow transmitted by the target terminal device, because the second packet loss service flow is the packet loss service flow for completing encapsulation, the target terminal device cannot directly obtain the packet loss service flow identifier carried in the second packet loss service flow, analyzes the encapsulated second packet loss service flow, and searches whether the analyzed packet loss service flow contains the IOAM data guide tag layer by layer. If so, the hop-by-hop detection function of the network management equipment is represented, so that whether the service flow transmitted by the terminal equipment is lost or not can be detected, and a preset byte after the data message in the parsed lost service flow is obtained, namely, a lost service flow identifier corresponding to the second lost service flow.
Optionally, the second packet loss traffic is a packet loss traffic based on multiprotocol label switching MPLS encapsulation.
Specifically, the MPLS label adopted by the packet loss service flow encapsulated by the MPLS label is nested between the 2-layer mac layer and the three ip layers layer by layer in a label format of 4 bytes, and the step of obtaining the second packet loss service flow identifier corresponding to the second packet loss service flow in a second manner by taking the second packet loss service flow encapsulated by the MPLS label as an example is that: analyzing the second packet loss service flow transmitted by the target terminal equipment, identifying the mac layer of the analyzed second packet loss service flow, carrying out layer-by-layer cyclic searching by taking 4 bytes as a unit, searching whether the analyzed second packet loss service flow contains an IOAM data guide label or not before the cyclic searching to the label stack is low, and ending the packet loss detection process if the analyzed second packet loss service flow does not contain the IOAM data guide label; if the IOAM data guiding label is found, the 4 bytes after the data message are used as the packet loss service flow identification corresponding to the second packet loss service flow.
Step 220: and respectively acquiring the packet loss type mapped by each packet loss service flow identifier by inquiring the packet loss classification mapping table.
The packet loss classification mapping table is used for storing packet loss types of packet loss of the service flow corresponding to the packet loss service flow identifier, and the packet loss types can be understood as types of packet loss reasons. For example, the packet loss reason is classified into a plurality of packet loss types according to a certain classification rule, for example, the packet loss type may include a plurality of parent types, and each parent type may further include a plurality of child types.
Specifically, the packet loss classification mapping table may be created and stored in the target terminal device during the hop-by-hop detection of the IOAM of the gateway device. Inquiring a packet loss classification mapping table based on the packet loss service flow identification to obtain the packet loss type mapped by the packet loss service flow identification
For example, the manner of creating the packet loss classification mapping table may be: in the hop-by-hop detection process based on the IOAM, if the to-be-detected service flow transmitted by the target terminal equipment is found to have packet loss, the gateway equipment determines the packet loss reason of each packet loss service flow based on the error position of the packet loss service flow when the service transmission program is executed and the packet loss reason corresponding to the pre-configured program error position, and classifies the packet loss reason to obtain the packet loss type. And then, creating a packet loss classification mapping table in the target terminal equipment, and storing the mapping relation between the packet loss service flow identification and the packet loss type into the packet loss classification mapping table. The mapping relationship between the packet loss service flow identifier and the packet loss type can be a direct mapping relationship or an indirect mapping relationship; the direct mapping relation refers to that the packet loss service flow identifier is directly mapped to the packet loss type, and the indirect mapping relation refers to that the packet loss service flow identifier is mapped to the intermediate quantity and is mapped to the packet loss type through the intermediate quantity.
Fig. 3 is a schematic diagram of a method for detecting packet loss of an execution service flow of a target terminal device according to an embodiment. As shown in fig. 3, in the embodiment of the present application, as a main device for executing a service flow packet loss detection method provided in the foregoing embodiment, a target terminal device may include a plurality of modules, where each module executes different steps respectively. The target terminal device may include at least: an acquisition module 31 and a query module 32; the acquiring module 31 may be configured in an upper data sensing layer, and the querying module 32 may be configured in a lower data processing chip. The acquiring module 31 and the query module 32 can interact in a lookup table manner, and the acquiring module 31 sends the acquired packet loss service flow information (which may include the packet loss service flow identifier and the outgoing port identifier) to the query module 32 through the mapping table, so that the query module 32 acquires the packet loss service flow information. Based on this, fig. 4 is a flowchart of a method for detecting packet loss of a service flow according to an embodiment. The method comprises the following steps: responding to a packet loss detection starting instruction issued by network management equipment, acquiring a packet loss service flow identifier carried by at least one packet loss service flow, and executing the following steps: the step of generating packet loss classification information items corresponding to the packet loss service flow identifiers can be further executed before the packet loss type mapped by each packet loss service flow identifier is respectively obtained by inquiring the packet loss classification mapping table. As shown in fig. 4, the method comprises the steps of:
Step 410: responding to a packet loss detection starting instruction issued by network management equipment, and acquiring a packet loss service flow identifier carried by at least one packet loss service flow; the packet loss detection starting instruction comprises: at least one service flow identifier to be detected; the packet loss service flow is a service flow with a service flow identifier containing any service flow identifier to be detected and packet loss occurs.
The acquisition module 31 may include a response unit and an acquisition unit, step 410: the responding to the packet loss detection starting instruction issued by the network management equipment can specifically comprise:
step 411: and reading a packet loss detection starting mark in a packet loss detection table item, wherein the packet loss detection starting mark is set as a target value when receiving the packet loss detection starting instruction.
Specifically, the network management device issues a packet loss detection starting instruction to the target terminal device so as to start the packet loss detection function of the query module of the target terminal device. When receiving a packet loss detection starting instruction issued by the network management equipment, the response unit of the acquisition module of the target terminal equipment sets a packet loss detection starting mark in a packet loss detection table entry stored in a memory as a target value (e.g. 1). An acquisition unit of the acquisition module reads a packet loss detection starting mark in a packet loss detection table item in real time,
Step 412: and if the packet loss detection starting mark is the target value, starting a packet loss detection function to acquire a packet loss service flow identifier carried by at least one packet loss service flow.
Specifically, if the packet loss detection starting flag is not the target value (e.g. 0), the packet loss detection instruction issued by the network management equipment is not received; if the packet loss detection starting mark is the target value, the target terminal equipment receives the issued packet loss detection starting instruction, the packet loss detection function of the query module of the target terminal equipment is started, and the packet loss service flow identifier carried by the packet loss service flow is acquired.
Step 420: and acquiring the mapping relation between the packet loss service flow identifier and the outgoing port identifier.
The outgoing port identifier may be understood as an identifier of an outgoing port of the packet loss service flow in the target terminal device.
Specifically, after sensing a response packet loss detection starting instruction and acquiring a packet loss service flow identifier carried by a packet loss service flow, an acquisition module of the target terminal equipment acquires an outgoing port identifier of the packet loss service flow in the target terminal equipment based on the packet loss service flow identifier, and determines a mapping relationship between the packet loss service flow identifier and the outgoing port identifier.
Step 430: and generating a packet loss service information mapping table based on the mapping relation between the packet loss service flow identifier and the outgoing port identifier.
The packet loss service information mapping table is used for storing the mapping relation between the packet loss service flow identifier and the corresponding outgoing port identifier.
Specifically, after acquiring the packet loss service flow identifier and the outgoing port identifier corresponding to the packet loss service flow identifier, the acquisition module of the target terminal equipment determines a mapping relationship between the packet loss service flow identifier and the outgoing port identifier, and stores the mapping relationship in the packet loss service information mapping table.
In addition, the target terminal device further includes a storage module 33 configured on the underlying data processing chip, and may be configured to store a packet loss service information mapping table, so as to facilitate subsequent query of the packet loss service information mapping table stored in the memory according to the packet loss service flow identifier to obtain an outgoing port identifier, and indicate a next transmission direction of the service flow.
In the service transmission process of the PTN network, the bit number of the service flow identifier carried by the service flow is usually relatively large, for example, up to 2 20 And in the process that the query module performs the packet loss classification mapping table by querying, the bit is larger in occupied hardware storage resource and lower in query efficiency in the process of respectively acquiring the packet loss type mapped by each packet loss service flow identifier. In order to solve the above problem, the step of generating the packet loss service information mapping table by the query module specifically includes:
Step 431: and acquiring a mapping relation between the packet loss service flow identifier and the target service flow identifier, wherein the bit number of the target service flow identifier is smaller than that of the packet loss service flow identifier.
The target service flow identifier is an identifier with the bit number smaller than that of the packet loss service flow identifier. The bit book of the target traffic flow identification may be set based on actual requirements or hardware capabilities.
The packet loss classification mapping table is queried by mapping the packet loss service flow identifier into a target service flow identifier with compressed bit number and adopting the target service flow identifier with smaller bit number.
Step 432: and generating a packet loss service information mapping table based on the mapping relation between the packet loss service flow identifier and the target service flow identifier and the mapping relation between the packet loss service flow identifier and the outgoing port identifier.
Specifically, the target service flow identifier is required to replace the packet loss service flow identifier to query a packet loss classification mapping table, and the mapping relationship between the target service flow identifier and the outgoing port identifier is required to be determined based on the mapping relationship between the packet loss service flow identifier and the target service flow identifier and the mapping relationship between the packet loss service flow identifier and the outgoing port identifier; and generating a packet loss service information mapping table according to the mapping relation between the target service flow identifier and the outbound port identifier, so that the corresponding outbound port identifier can be obtained by inquiring the packet loss service information mapping table based on the target service flow identifier with fewer bits mapped by the packet loss service flow identifier, the hardware storage resources occupied in the inquiring process can be reduced, and the inquiring efficiency is improved.
Step 440: and scanning the mapping relation in the packet loss service information mapping table, and generating packet loss classification information items corresponding to the service flow identifiers to be detected based on the updated mapping relation.
The packet loss classification information item may be understood as an information item for guiding packet loss classification, each to-be-detected service flow identifier corresponds to one packet loss classification information item, and the packet loss classification information item includes: and the service flow identifier to be detected is corresponding to the relevant information of the packet loss service flow.
Optionally, the packet loss classification information entry may include: an information entry index, at least one target traffic flow identifier, and an outbound port identifier corresponding to each target traffic flow identifier.
Wherein, an information item index is allocated to the packet loss classification information item corresponding to each packet loss service flow identifier, and the packet loss classification information item may further include: the method comprises at least one target service flow identifier of a service representation to be detected and an outbound port identifier corresponding to each target service flow identifier.
Specifically, the query module of the target terminal device may scan the mapping relationship in the packet loss service information mapping table based on a preset scan period, obtain an updated mapping relationship when the mapping relationship is updated, and generate packet loss classification information entries corresponding to the service flow identifiers to be detected based on the updated mapping relationship.
For example, if a plurality of to-be-detected service flow identifiers are configured, at least one packet loss service flow identifier containing any to-be-detected service flow identifier exists, that is, each to-be-detected service flow identifier corresponds to at least one packet loss service flow, a packet loss classification information item with an information item index is generated based on the target service flow identifier and the outgoing port identifier of each packet loss service flow.
Step 450: and respectively acquiring the packet loss type mapped by each packet loss service flow identifier by inquiring the packet loss classification mapping table.
In this embodiment, the packet loss classification mapping table includes: the mapping relation between the packet loss classification index and the packet loss type; the packet loss classification index is carried in the packet loss service flow corresponding to the target service flow identifier, and is generated when the network management equipment executes the IOAM hop-by-hop detection function.
The packet loss type may reflect a type to which a packet loss cause of the packet loss service flow belongs, and the packet loss type may include a plurality of major classes and/or a plurality of minor classes, where each major class may be divided into a plurality of minor classes, and the packet loss type is not limited herein.
Specifically, when the network management device executes the IOAM hop-by-hop detection function to determine the packet loss service flow, the packet loss classification index may be determined based on an error position of the packet loss service flow when executing the service transmission program, where the packet loss classification index is carried in the packet loss service flow and may reflect a packet loss cause of the packet loss service flow, and a mapping relationship between the packet loss classification index and the packet loss type is determined according to a type to which the preconfigured packet loss cause belongs. Thereby creating a packet loss classification mapping table based on the mapping relation between the packet loss classification index and the packet loss type.
Optionally, the mapping relationship between the packet loss classification index and the packet loss type includes: mapping relation between packet loss classification index and subtype of packet loss reason; and a mapping relationship between the subtype of the packet loss cause (i.e., the subclass) and the parent type of the packet loss cause (i.e., the major class).
Illustratively, table 1 is a mapping relationship table of packet loss classification index and packet loss type.
TABLE 1
Accordingly, step 450 may include:
step 451: and acquiring a target service flow identifier corresponding to each information item index.
Specifically, for the packet loss classification information item corresponding to each information item index, respectively obtaining the packet loss type mapped by each packet loss service flow identifier in the packet loss classification information item by querying the packet loss classification mapping table. In the process of inquiring the packet loss classification mapping table, the target service flow identifier with fewer bits is adopted to replace the packet loss service flow identifier, so that the target service flow identifier contained in the packet loss classification information item corresponding to each information item index needs to be acquired.
It should be noted that, for the packet loss classification information item corresponding to each information item index, the packet loss type mapped by each packet loss service flow identifier in the packet loss classification information item may be obtained by respectively querying the packet loss classification mapping table, which is not limited in this embodiment.
Step 452: and for each target service flow identifier, obtaining the packet loss type mapped by the packet loss classification index corresponding to each target service flow identifier by inquiring the packet loss classification mapping table.
Specifically, query information (i.e., each target service flow identifier) is input into the packet loss classification mapping table, a packet loss classification index corresponding to the target service flow identifier and a packet loss type mapped by the packet loss classification index are determined through the packet loss classification mapping table, and a query result fed back by the packet loss classification mapping table (i.e., the packet loss type mapped by each target service flow identifier, where the packet loss type may include a parent type and a subtype).
Step 453: and determining the packet loss type mapped by each packet loss service flow identifier based on the mapping relation between the packet loss service flow identifier and the target service flow identifier and the packet loss type mapped by each target service flow identifier.
Specifically, the packet loss type mapped by the target service flow identifier is determined as the packet loss type mapped by the packet loss service flow identifier.
In addition, the storage module 33 is further configured to store the packet loss type mapped by each packet loss service flow identifier.
In this embodiment of the present application, after determining the packet loss type to which the packet loss cause of each packet loss service flow corresponding to each packet loss service flow identifier on the target terminal device belongs, in order to quickly repair the packet loss fault, ensure accuracy of service flow transmission, as shown in fig. 4, step 450 may be further executed: after acquiring the packet loss type mapped by each packet loss service flow identifier by querying a packet loss classification mapping table, step 460 is executed: and counting the number of the lost packets of the lost packet service flow transmitted by the target terminal equipment on each lost packet type.
Specifically, by counting the number of packet loss of the packet loss service flow transmitted by the target terminal device on each packet loss type, the probability of occurrence of packet loss of the packet loss service flow transmitted by the terminal device on each packet loss type can be determined, the packet loss faults corresponding to the packet loss type with high probability of occurrence of packet loss are processed preferentially, and the influence of the packet loss faults on service transmission is reduced as much as possible.
Specifically, step 460: counting the packet loss quantity of the packet loss service flow transmitted by the target terminal equipment on each packet loss type, comprising the following steps:
step 461: for each information item index, determining a packet loss service flow identifier mapped by a target service flow identifier corresponding to the information item index;
step 462: and counting the number of the packet loss service flow corresponding to each information item index on each packet loss type according to the packet loss type mapped by each packet loss service flow identifier.
Specifically, the method includes the specific steps of counting the number of packet losses of the packet loss service flows corresponding to each information item index on each packet loss type, and counting the number of packet losses of the packet loss service flows corresponding to one information item index on each packet loss type, where the specific steps include: firstly, determining a packet loss service flow identifier mapped by a target service flow identifier corresponding to the information item index, then sequentially obtaining the packet loss type mapped by each packet loss service flow identifier, and counting the packet loss quantity of the packet loss service flow corresponding to each information item index on each packet loss type.
On the basis of the above embodiment, as shown in fig. 3, the target terminal device may further include: the counting module 34 is configured on the underlying data processing chip, and the counting module 34 includes: and the counters are respectively corresponding to the packet loss types corresponding to the information item indexes and are used for counting the packet loss quantity of the packet loss service flow corresponding to the information item indexes on each packet loss type.
The packet loss quantity of the packet loss service flows of which the service flow identifications contain different service flow identifications to be detected on each packet loss type is counted respectively, the specific reasons of packet loss of the different service flows to be detected on the target terminal equipment can be further compared, more information is provided for repairing the packet loss faults, and the recovery efficiency of the packet loss faults is improved.
On the basis of the above embodiment, as shown in fig. 3, the target terminal device may further include: a reporting module 35 configured on the underlying data processing chip; and a display module 36 disposed in an upper data sensing layer;
in execution step 460: after counting the number of packet loss of the packet loss service flow transmitted by the target terminal device on each packet loss type, the following steps may be executed:
analyzing the packet loss reasons corresponding to the packet loss types through the reporting module 35; generating a service flow packet loss detection report according to the packet loss quantity of the packet loss service flow transmitted by the target terminal equipment on each packet loss type and the packet loss reason corresponding to the packet loss type; and sending a service stream packet loss detection report to the network management equipment.
And generating alarm information based on the service stream packet loss detection report by the reporting module 35, and sending the service stream packet loss detection report and the alarm information to the display module.
The traffic stream packet loss detection report and the alarm information are displayed by the display module 36.
The service flow packet loss detection report is used for reflecting information such as positions, reasons, quantity and the like of packet loss of the service flow, so that the removal of packet loss faults is facilitated; the alarm information is used for prompting the packet loss and the packet loss reason of the service flow. The embodiment does not limit the form and the specific content of the service flow packet loss detection report, and the form and the specific content of the alarm information.
The embodiment of the application also provides a device for detecting the packet loss of the service flow. Fig. 5 is a schematic structural diagram of a transmission device according to an embodiment. As shown in fig. 5, the service flow packet loss detection apparatus may be configured in a terminal device, and includes:
the identifier obtaining module 510 is used for responding to a packet loss detection starting instruction issued by the network management equipment and obtaining a packet loss service flow identifier carried by at least one packet loss service flow; the packet loss detection starting instruction comprises: at least one service flow identifier to be detected; the packet loss service flow is a service flow with a service flow identifier comprising any service flow identifier to be detected and packet loss;
The type obtaining module 520 obtains the packet loss type mapped by each packet loss service flow identifier by querying a packet loss classification mapping table.
Optionally, after the network management device executes the IOAM hop-by-hop detection function to determine the target terminal device, the packet loss detection start instruction is issued to the target terminal device.
Optionally, the identifier obtaining module 510 includes:
the first identifier acquisition unit acquires a packet loss service flow identifier carried by the first packet loss service flow based on a first acquisition mode; the first packet loss service flow is an unpackaged packet loss service flow or an unpackaged packet loss service flow;
and/or;
the second identifier acquisition unit acquires the identifier of the packet loss service flow carried by the second packet loss service flow based on a second acquisition mode; and the second packet loss service flow is the packet loss service flow which has completed encapsulation.
Optionally, the second packet loss service flow is a packet loss service flow based on multiprotocol label switching MPLS encapsulation.
Optionally, the first obtaining manner includes: directly acquiring a packet loss service flow identifier carried by a packet loss service flow transmitted by the target terminal equipment;
the second acquisition mode includes: analyzing the second packet loss service flow transmitted by the target terminal equipment, and searching whether the analyzed second packet loss service flow contains an IOAM data guide tag or not; and if the IOAM data guide label is included, determining a preset byte after the data message in the parsed second packet loss service flow as a packet loss service flow identifier corresponding to the second packet loss service flow.
Optionally, the method further comprises:
the mapping relation acquisition module acquires the mapping relation between the packet loss service flow identifiers and the outgoing port identifiers after acquiring at least one packet loss service flow identifier and before respectively acquiring the packet loss type mapped by each packet loss service flow identifier by inquiring a packet loss classification mapping table;
the mapping table generation module is used for generating a packet loss service information mapping table based on the mapping relation between the packet loss service flow identifier and the outbound port identifier;
and the information item generating module scans the mapping relation in the packet loss service information mapping table and generates packet loss classification information items corresponding to the service flow identifiers to be detected based on the updated mapping relation.
Optionally, the mapping table generating module includes:
acquiring a mapping relation between the packet loss service flow identifier and the target service flow identifier; the bit number of the target service flow identifier is smaller than that of the packet loss service flow identifier;
and generating a packet loss service information mapping table based on the mapping relation between the packet loss service flow identifier and the target service flow identifier and the mapping relation between the packet loss service flow identifier and the outbound port identifier.
Optionally, the packet loss classification information entry includes: an information entry index, at least one target service flow identifier and an outbound port identifier corresponding to each target service flow identifier. Optionally, the packet loss classification mapping table includes: the mapping relation between the packet loss classification index and the packet loss type; the packet loss classification index is carried in the packet loss service flow corresponding to the target service flow identifier and is generated when the network management equipment executes the IOAM hop-by-hop detection function;
accordingly, the type obtaining module 520 includes:
an identifier obtaining unit for obtaining a target service flow identifier corresponding to each information item index;
a type mapping unit, for each target service flow identifier, obtaining a packet loss type mapped by a packet loss classification index corresponding to each target service flow identifier by querying the packet loss classification mapping table;
and the type determining unit is used for determining the packet loss type mapped by each packet loss service flow identifier based on the mapping relation between the packet loss service flow identifier and the target service flow identifier and the packet loss type mapped by each target service flow identifier.
Optionally, the mapping relationship between the packet loss classification index and the packet loss type includes:
The mapping relation between the packet loss classification index and the subtype of the packet loss reason; and the mapping relation between the sub type of the packet loss reason and the father type of the packet loss reason.
Optionally, the method further comprises:
and the statistics module is used for counting the packet loss quantity of the packet loss service flows transmitted by the target terminal equipment on each packet loss type after respectively acquiring the packet loss type mapped by each packet loss service flow identifier by inquiring the packet loss classification mapping table.
Optionally, the statistics module includes:
for each information item index, determining a packet loss service flow identifier mapped by a target service flow identifier corresponding to the information item index;
and counting the number of the packet loss service flow corresponding to each information item index on each packet loss type according to the packet loss type mapped by each packet loss service flow identifier.
Optionally, the method further comprises: after counting the number of packet losses of the packet loss service flow transmitted by the target terminal device on each packet loss type,
the analysis module analyzes the packet loss reasons corresponding to the packet loss types;
the report generation module is used for generating a service flow packet loss detection report according to the packet loss quantity of the packet loss service flow transmitted by the target terminal equipment on each packet loss type and the packet loss reason corresponding to the packet loss type;
And the report sending module is used for sending the service stream packet loss detection report to the network management equipment.
Optionally, the identifier obtaining module 510 is specifically configured to:
reading a packet loss detection starting mark in a packet loss detection table item, wherein the packet loss detection starting mark is set as a target value when receiving the packet loss detection starting instruction;
and if the packet loss detection starting mark is the target value, starting a packet loss detection function to acquire a packet loss service flow identifier carried by at least one packet loss service flow.
Optionally, the service flow to be detected includes:
two-layer virtual private network L2VPN traffic or three-layer virtual private network L3VPN traffic.
The service flow packet loss detection device provided in this embodiment and the service flow packet loss detection method provided in the foregoing embodiments belong to the same inventive concept, technical details which are not described in detail in this embodiment can be seen in any of the foregoing embodiments, and this embodiment has the same advantages as those of executing the service flow packet loss detection method.
The embodiment of the present application further provides a terminal device, and fig. 6 is a schematic hardware structure of the terminal device provided by an embodiment, as shown in fig. 6, where the terminal device provided by the present application includes a memory 620, a processor 610, and a computer program stored in the memory and capable of running on the processor, and the processor 610 implements the above-mentioned method for detecting packet loss of a service flow when executing the program.
The terminal device may also include a memory 620; the number of processors 610 in the terminal device may be one or more, one processor 610 being taken as an example in fig. 6; memory 520 is used to store one or more programs; the one or more programs are executed by the one or more processors 610, so that the one or more processors 610 implement the traffic stream packet loss detection method as described in the embodiments of the present application.
The terminal device further includes: communication device 630, input device 640, and output device 650.
The processor 510, memory 520, communication means 530, input means 540 and output means 550 in the terminal device may be connected by a bus or other means, for example by a bus connection in fig. 6.
The input means 640 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the terminal device. The output 650 may include a display device such as a display screen.
The communication device 630 may include a receiver and a transmitter. The communication means 630 is arranged to perform information transceiving communication according to control of the processor 610.
The memory 620, which is a computer readable storage medium, may be configured to store a software program, a computer executable program, and modules, as described in the embodiments of the present application, corresponding to program instructions/modules (e.g., the identifier obtaining module 510 and the type obtaining module 520 in the traffic packet loss detection device) of the traffic packet loss detection method. Memory 620 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, at least one application program required for a function; the storage data area may store data created according to the use of the terminal device, etc. In addition, memory 620 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some examples, memory 620 may further include memory located remotely from processor 610, which may be connected to the terminal device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The embodiment of the application also provides a storage medium, and the storage medium stores a computer program, and the computer program realizes the method for detecting the packet loss of the service flow in any one of the embodiments of the application when being executed by a processor.
Optionally, the method for detecting packet loss of the service flow is applied to target terminal equipment, wherein the target terminal equipment is terminal equipment for detecting packet loss of the service flow to be detected in a service transmission path; the method comprises the following steps: responding to a packet loss detection starting instruction issued by network management equipment, and acquiring a packet loss service flow identifier carried by at least one packet loss service flow; the packet loss detection starting instruction comprises: at least one service flow identifier to be detected; the packet loss service flow is a service flow with a service flow identifier comprising any service flow identifier to be detected and packet loss; and respectively acquiring the packet loss type mapped by each packet loss service flow identifier by inquiring a packet loss classification mapping table.
Any combination of one or more computer readable media may be employed as the computer storage media of the embodiments herein. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium may be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access Memory (Random Access Memory, RAM), a Read-Only Memory (ROM), an erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), a flash Memory, an optical fiber, a portable CD-ROM, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. A computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to: electromagnetic signals, optical signals, or any suitable combination of the preceding. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, radio Frequency (RF), and the like, or any suitable combination of the foregoing.
Computer program code for carrying out operations of the present application may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application.
It will be appreciated by those skilled in the art that the term user terminal encompasses any suitable type of wireless user equipment, such as a mobile telephone, a portable data processing device, a portable web browser or a car mobile station.
In general, the various embodiments of the application may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
Embodiments of the present application may be implemented by a data processor of a mobile device executing computer program instructions, e.g. in a processor entity, either in hardware, or in a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (Instruction Set Architecture, ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages.
The block diagrams of any logic flow in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on a memory. The Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), optical Memory devices and systems (digital versatile Disk (Digital Video Disc, DVD) or Compact Disk (CD)), etc., the computer readable medium may comprise a non-transitory storage medium.
By way of exemplary and non-limiting example, a detailed description of exemplary embodiments of the present application has been provided above. Various modifications and adaptations to the above embodiments may become apparent to those skilled in the art without departing from the scope of the present application, as considered in conjunction with the accompanying drawings and claims. Accordingly, the proper scope of the present application is to be determined according to the claims.
Claims (17)
1. The method for detecting the packet loss of the service flow is characterized by being applied to target terminal equipment, wherein the target terminal equipment is terminal equipment for detecting the packet loss of the service flow to be detected in a service transmission path; the method comprises the following steps:
responding to a packet loss detection starting instruction issued by network management equipment, and acquiring a packet loss service flow identifier carried by at least one packet loss service flow; the packet loss detection starting instruction comprises: at least one service flow identifier to be detected; the packet loss service flow is a service flow with a service flow identifier comprising any service flow identifier to be detected and packet loss;
and respectively acquiring the packet loss type mapped by each packet loss service flow identifier by inquiring a packet loss classification mapping table.
2. The method according to claim 1, wherein the packet loss detection initiation instruction is issued to the target terminal device after the network management device performs an IOAM hop-by-hop detection function to determine the target terminal device.
3. The method of claim 1, wherein obtaining the packet loss service flow identifier carried by the at least one packet loss service flow comprises:
acquiring a packet loss service flow identifier carried by a first packet loss service flow based on a first acquisition mode; the first packet loss service flow is an unpackaged packet loss service flow or an unpackaged packet loss service flow;
and/or;
acquiring a packet loss service flow identifier carried by a second packet loss service flow based on a second acquisition mode; and the second packet loss service flow is the packet loss service flow which has completed encapsulation.
4. The method of claim 3, wherein the second packet-loss traffic flow is a packet-loss traffic flow based on multiprotocol label switching, MPLS, encapsulation.
5. The method of claim 4, wherein the first obtaining means comprises: directly acquiring a packet loss service flow identifier carried by a packet loss service flow transmitted by the target terminal equipment;
the second acquisition mode includes: analyzing the second packet loss service flow transmitted by the target terminal equipment, and searching whether the analyzed second packet loss service flow contains an IOAM data guide tag or not; and if the IOAM data guide label is included, determining a preset byte after the data message in the parsed second packet loss service flow as a packet loss service flow identifier corresponding to the second packet loss service flow.
6. The method according to claim 1, wherein after acquiring at least one packet loss service flow identifier and before acquiring the packet loss type mapped by each packet loss service flow identifier by querying a packet loss classification mapping table, further comprising:
acquiring the mapping relation between the packet loss service flow identifier and the outgoing port identifier;
generating a packet loss service information mapping table based on the mapping relation between the packet loss service flow identifier and the outbound port identifier;
and scanning the mapping relation in the packet loss service information mapping table, and generating packet loss classification information items corresponding to the service flow identifiers to be detected based on the updated mapping relation.
7. The method of claim 6, wherein generating a packet loss service information mapping table based on the packet loss service flow identification and the outgoing port identification comprises:
acquiring a mapping relation between the packet loss service flow identifier and the target service flow identifier; the bit number of the target service flow identifier is smaller than that of the packet loss service flow identifier;
and generating a packet loss service information mapping table based on the mapping relation between the packet loss service flow identifier and the target service flow identifier and the mapping relation between the packet loss service flow identifier and the outbound port identifier.
8. The method of claim 7, wherein the packet loss classification information entry comprises: an information entry index, at least one target service flow identifier and an outbound port identifier corresponding to each target service flow identifier.
9. The method of claim 8, wherein the packet loss classification mapping table comprises: the mapping relation between the packet loss classification index and the packet loss type; the packet loss classification index is carried in the packet loss service flow corresponding to the target service flow identifier and is generated when the network management equipment executes the IOAM hop-by-hop detection function;
correspondingly, by querying a packet loss classification mapping table, the packet loss type mapped by each packet loss service flow identifier is respectively obtained, which comprises the following steps:
acquiring a target service flow identifier corresponding to each information item index;
for each target service flow identifier, obtaining the packet loss type mapped by the packet loss classification index corresponding to each target service flow identifier by inquiring the packet loss classification mapping table;
and determining the packet loss type mapped by each packet loss service flow identifier based on the mapping relation between the packet loss service flow identifier and the target service flow identifier and the packet loss type mapped by each target service flow identifier.
10. The method of claim 9, wherein the mapping between the packet loss classification index and the packet loss type comprises:
the mapping relation between the packet loss classification index and the subtype of the packet loss reason; and the mapping relation between the sub type of the packet loss reason and the father type of the packet loss reason.
11. The method according to any one of claims 9-10, further comprising, after obtaining the packet loss type mapped by each packet loss service flow identifier by querying a packet loss classification mapping table, respectively:
and counting the packet loss quantity of the packet loss service flow transmitted by the target terminal equipment on each packet loss type.
12. The method according to claim 11, wherein counting the number of dropped packets of the dropped packet traffic stream transmitted by the target terminal device on each of the dropped packet types includes:
for each information item index, determining a packet loss service flow identifier mapped by a target service flow identifier corresponding to the information item index;
and counting the number of the packet loss service flow corresponding to each information item index on each packet loss type according to the packet loss type mapped by each packet loss service flow identifier.
13. The method according to claim 11, further comprising, after counting the number of packet losses of each of the packet loss types for the packet loss service flows transmitted by the target terminal device:
analyzing the packet loss reasons corresponding to the packet loss types;
generating a service flow packet loss detection report according to the packet loss quantity of the packet loss service flow transmitted by the target terminal equipment on each packet loss type and the packet loss reason corresponding to the packet loss type;
and sending the service stream packet loss detection report to the network management equipment.
14. The method of claim 1, wherein responding to the packet loss detection start command issued by the network management device comprises:
reading a packet loss detection starting mark in a packet loss detection table item, wherein the packet loss detection starting mark is set as a target value when receiving the packet loss detection starting instruction;
and if the packet loss detection starting mark is the target value, starting a packet loss detection function to acquire a packet loss service flow identifier carried by at least one packet loss service flow.
15. The method of claim 1, wherein the traffic flow to be detected comprises:
two-layer virtual private network L2VPN traffic or three-layer virtual private network L3VPN traffic.
16. A terminal device, comprising:
a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the traffic stream packet loss detection method according to any of claims 1-15 when the program is executed.
17. A storage medium having stored thereon a computer program, which when executed by a processor implements a traffic stream packet loss detection method according to any of claims 1-15.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210767944.6A CN117376200A (en) | 2022-06-30 | 2022-06-30 | Service flow packet loss detection method, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210767944.6A CN117376200A (en) | 2022-06-30 | 2022-06-30 | Service flow packet loss detection method, terminal equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117376200A true CN117376200A (en) | 2024-01-09 |
Family
ID=89397053
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210767944.6A Pending CN117376200A (en) | 2022-06-30 | 2022-06-30 | Service flow packet loss detection method, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117376200A (en) |
-
2022
- 2022-06-30 CN CN202210767944.6A patent/CN117376200A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11228515B2 (en) | Data packet detection method, device, and system | |
| US10484206B2 (en) | Path detection method in VxLAN, controller, and network device | |
| EP3082293B1 (en) | Switching device and packet loss method therefor | |
| WO2017206841A1 (en) | Method and device for determining quality of service of network apparatus | |
| WO2018054397A1 (en) | Service function chain detection path method and device | |
| CN105684382A (en) | Packet control method, switch and controller | |
| CN105024985A (en) | Message processing method and apparatus | |
| CN112866075A (en) | In-band network telemetering method, system and related device for Overlay network | |
| CN112039796B (en) | Data packet transmission method and device, storage medium and electronic equipment | |
| US20230261962A1 (en) | Method for Detecting Multicast Service Flow and Related Apparatus | |
| US11336545B2 (en) | Network device measurements employing white boxes | |
| CN112737871B (en) | Link fault detection method and device, computer equipment and storage medium | |
| CN113709043B (en) | Path tracking method and device | |
| EP3905599A1 (en) | Statistic information generation device, statistic information generation method, and program | |
| US20130042020A1 (en) | Quick Network Path Discovery | |
| CN111490907B (en) | Method and device for determining VXLAN network performance parameters | |
| US20220094613A1 (en) | Message sampling method, decapsulation method, node, system and storage medium | |
| CN117376200A (en) | Service flow packet loss detection method, terminal equipment and storage medium | |
| CN108616453B (en) | Method, device and system for network equipment | |
| CN113726657A (en) | Message forwarding method, device, system, equipment and storage medium | |
| CN116527592A (en) | Application layer stream following detection method and device based on APN (access point) and related equipment | |
| CN112543142B (en) | Method and device for realizing RSTP ring network protocol based on FPGA | |
| CN114866488A (en) | Information flow identification method, network chip and network equipment | |
| CN115225545B (en) | Message transmission method and device | |
| US11770312B2 (en) | Service detection method and apparatus, device, and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |