WO2021093692A1 - 网络质量检测方法、装置、服务器和计算机可读介质 - Google Patents

网络质量检测方法、装置、服务器和计算机可读介质 Download PDF

Info

Publication number
WO2021093692A1
WO2021093692A1 PCT/CN2020/127327 CN2020127327W WO2021093692A1 WO 2021093692 A1 WO2021093692 A1 WO 2021093692A1 CN 2020127327 W CN2020127327 W CN 2020127327W WO 2021093692 A1 WO2021093692 A1 WO 2021093692A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
path
network
service flow
detection
Prior art date
Application number
PCT/CN2020/127327
Other languages
English (en)
French (fr)
Inventor
涂继强
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2021093692A1 publication Critical patent/WO2021093692A1/zh

Links

Images

Classifications

    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5058—Service discovery by the service manager
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/02—Capturing of monitoring data
    • H04L43/026—Capturing of monitoring data using flow identification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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
    • 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
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/50—Testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/14—Routing performance; Theoretical aspects
    • 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/12—Discovery or management of network topologies
    • 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/22—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]

Definitions

  • This application relates to the field of computer network technology, and in particular to a network quality detection method, device, server, and computer-readable medium.
  • the disadvantage is that it cannot guarantee that the simulated message is consistent with the real service path, and cannot be applied to service scenarios such as active-standby switching, Equal-Cost Multipath Routing (Equal-Cost Multipath Routing), etc., and cannot fully reflect the SLA (Service Level Agreement). ), especially silent failures such as a small amount of packet loss cannot be captured.
  • the performance data collection cycle of the traditional out-of-band OAM detection method is minute or sub-minute.
  • the bearer network can only passively respond to complaints from surrounding departments after service failure or quality degradation, and cannot fully reflect network quality in real time.
  • traditional out-of-band OAM detection methods are unable to detect hop by hop, and the problem is difficult to accurately determine the boundary. It often requires multiple teams to coordinate positioning, and the positioning cycle is several days or even weeks.
  • In-band OAM refers to directly encapsulating the OAM information and data that needs to be carried in a user data message, which can be sent together with the data message, without the need for additional control messages to send OAM data.
  • In-band OAM can implement a variety of network fault detection functions, such as packet path consistency detection, POT (Proof of Transit) verification, SLA detection, and so on.
  • the edge node in the in-band OAM domain embeds the in-band OAM data in the data message, so this node is also called the in-band OAM encapsulation node.
  • the edge node in the in-band OAM domain removes the OAM data message, so the node again It is called the in-band OAM decapsulation node.
  • In-band OAM network quality detection objects can be SR (Segment Routing)-TP (Transport Profile)/TE (Traffic Engineering) tunnel, SR-BE (Best Effort, best effort segment) Routing) tunnel, or IP (Internet Protocol, Internet Protocol address) service flow carried.
  • SR Segment Routing
  • TP Transmission Profile
  • TE Traffic Engineering
  • SR-BE Best Effort, best effort segment Routing
  • IP Internet Protocol, Internet Protocol address
  • Existing in-band network quality detection solutions include: MPLS-TP-OAM, CFM (Connectivity Fault Management), TWAMP (Tow-Way Active Measurement Protocol, two-way active measurement protocol), etc.
  • the above detection scheme has obvious shortcomings: the configuration of the detection implementation process is complicated, the operation and maintenance cost is high, and the detection of the whole service path is not well supported, and more importantly, the detection result does not reflect the real service path.
  • the embodiments of the present application provide a network quality detection method, device, server, and computer-readable medium.
  • An embodiment of the present application provides a network quality detection method, the method includes: determining a suspected path of a service flow used for detection according to a preset static routing database; and sending to a network element device on the suspected path to indicate detection
  • the subscription command of the service flow, and receiving the data sent by the network element device, the data is the performance data in response to the subscription command; according to the data, the static routing database, and the suspected path, the data is determined
  • the real path of the service flow; and the network quality of the real path is detected according to the data and a preset index threshold.
  • An embodiment of the present application also provides a network quality detection device, including: a first determining module, a sending module, a receiving module, a second determining module, and a detecting module; the first determining module is used for, according to a preset static routing database Determine the suspected path of the service flow used for detection; the sending module is configured to send a subscription command for instructing the detection of the service flow to the network element device on the suspected path; the receiving module is configured to receive all The data sent by the network element device, the data is performance data in response to the subscription command; the second determining module is configured to determine the service according to the data, the static routing database, and the suspected path The real path of the flow; the detection module is used to detect the network quality of the real path according to the data and a preset index threshold.
  • An embodiment of the present application further provides a server, which includes: one or more processors and a storage device; wherein, one or more programs are stored on the storage device, and when the above-mentioned one or more programs are used by the above-mentioned one or more When the processor is executed, the above one or more processors implement the network quality detection method provided in the foregoing embodiments.
  • the embodiments of the present application also provide a computer-readable medium on which a computer program is stored, wherein the computer program implements the network quality detection method provided in the foregoing embodiments when the computer program is executed.
  • FIG. 1 is a flowchart of a network quality detection method provided by an embodiment of this application
  • Figure 2 is a flow chart of data preprocessing provided by an embodiment of the application
  • FIG. 3 is a flowchart of determining a true path provided by an embodiment of the application
  • FIG. 4 is an example of data preprocessing provided by an embodiment of the application.
  • FIG. 5 is an example of a hop-by-hop detection type provided by an embodiment of the application.
  • FIG. 6 is a flowchart of a network quality detection method provided by another embodiment of this application.
  • FIG. 7 is a schematic diagram showing real paths and faults provided by an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of a network quality detection device provided by another embodiment of this application.
  • FIG. 9 is a schematic structural diagram of a network quality detection device provided by another embodiment of this application.
  • FIG. 10 is a schematic structural diagram of a network quality detection device provided by still another embodiment of this application.
  • FIG. 11 is a schematic structural diagram of a network quality detection device provided by another embodiment of this application.
  • An embodiment of the present application provides a network quality detection method, which can be applied but not limited to 5G (5th-Generation, fifth-generation mobile communication technology) network quality detection.
  • the method is applied to a system including a network quality detection device (such as a management and control server), a data collection server, and a number of network element devices for carrying service flows.
  • a network quality detection device such as a management and control server
  • a data collection server such as a management and control server
  • a number of network element devices for carrying service flows In the initialization phase, perform the following operations: 1. Configure general detection parameters.
  • General detection parameters can include compression format, reporting channel, reporting protocol, etc., for example, compression format can be GPB, GPB-KV, etc., reporting channel can be DCN (Data Communication Network, data communication network) channel, the reporting protocol can be UDP (User Datagram Protocol, user datagram protocol), gRPC (Remote Procedure Call, remote procedure call) protocol; 2. Select the detection object (that is, the one used for detection) Service flow) and configure the detection task parameters.
  • the detection task parameters can include tunnel parameters, detection types, and the subscription, dyeing, encapsulation, and decapsulation command parameters related to the detection task, etc.; use L3VPN (Virtual Private Network, virtual private network) IP Take a service flow as an example.
  • Its detection task parameters can include service flow identification, detection type, source network element, service access point, source IP (both IPV4/IPV6 are supported), source port, protocol number, sink IP, sink port, DSCP (Differentiated Services Code Point) priority, delay priority, reporting cycle, etc.
  • the method includes the following steps:
  • Step 11 Determine the suspected path of the service flow used for detection according to the preset static routing database.
  • the network quality detection device queries the static routing database to identify all possible routing information, PE (Provider Edge) equipment and P (Provider, core) equipment of the service flow used for detection, and based on the routing information , PE equipment and P equipment determine the suspected path of the service flow.
  • PE Provider Edge
  • P Provider, core
  • the same service flow can have different paths at different times, but the service flow has a unique path at the same time.
  • the possible paths of the service flow at different times are summarized to form a suspect Path collection.
  • Step 12 Send a subscription command for instructing to detect the service flow to the network element device on the suspected path.
  • the network quality detection device first determines the network element equipment on each suspected path, and the network element equipment includes PE equipment and P equipment. Then respectively send a subscription command to the determined network element equipment, and then send a detection task to detect the service flow.
  • the subscription command carries the general detection parameters and the parameters of the detection task.
  • the network quality detection device sends a subscription command to the data collection server, and the data collection server sends the subscription command to the network element devices on each suspected path.
  • Step 13 Receive data sent by each network element device.
  • the data sent by the network element device is the performance data in response to the subscription command, which may include the number of packets lost, the packet loss rate, time delay, jitter, and so on.
  • the network element device can use the Telemetry protocol to report the performance data of the device (that is, single point performance data) to the data collection server in real time, and the data collection server reports the performance data reported by each network element device to the network quality detection device.
  • the network quality detection device parses the data according to the encoding and compression format to obtain necessary information (including FlowID, timestamp, counting information, etc.). It should be noted that, in order to ensure the correctness of data analysis, it is necessary to ensure the time synchronization of each network element device and the integrity of the data reported by each network element device.
  • Step 14 Determine the true path of the service flow based on the data, the static routing database and the suspected path.
  • the data sent by each network element device is real-time data, and the service flow has a unique path at the same time, the only real path of the service flow at a certain time can be determined according to the data.
  • the specific implementation method of determining the real path of the service flow according to the data, the static routing database and the suspected path will be described in detail later in conjunction with FIG. 4.
  • Step 15 Detect the network quality of the real path according to the data and the preset index threshold.
  • the indicator threshold may be set in units of service flow, that is, a series of related performance indicator thresholds are set for each service flow.
  • the threshold may also be set according to the service type, that is, for each service type, a set of Series-related performance index thresholds.
  • the network quality detection device compares the data reported by each network element device on the real path with the corresponding index threshold. If the data meets the corresponding performance index conditions, the performance index is considered qualified; if the data does not meet the corresponding index If the performance index conditions, the node or link is considered to be faulty.
  • the suspected path of the service flow used for detection is determined according to the preset static routing database
  • the subscription command is sent to the network element device on the suspected path
  • the network is received.
  • the data sent by the meta-device in response to the subscription command determines the real path of the service flow according to the static routing database and the suspected path of the data, and detects the network quality on the real path according to the data and the preset index threshold.
  • This application uses the in-band flow-following detection method to reflect the true SLA, which can provide end-to-end and hop-by-hop SLA detection capabilities, and can perceive network performance indicators in real time to achieve rapid and accurate delineation of network failures; by segmenting equipment performance data
  • Real-time integration with the routing database to achieve true path restoration can effectively solve the problem of difficulty in true path restoration in business scenarios such as active/standby path switching, ECMP, and eX2.
  • the scheme of the present application has simple configuration, low operation and maintenance costs, and is easy to implement.
  • the static routing database and the suspected path i.e. step 14
  • the received data is preprocessed.
  • the data includes at least a service flow identifier (FlowID) and a timestamp.
  • FlowID service flow identifier
  • the data preprocessing process may include the following steps:
  • Step 13' mark the first label for the data according to the service flow identifier.
  • the network quality detection device marks each data with the same service flow identification with the same first label.
  • the first label may be the service flow identification.
  • the service flow identification is uniformly allocated by the network quality detection device to ensure that it is globally unique in the detection domain. .
  • Step 14' Determine the reporting period of the data according to the time stamp, and mark the data with a second label according to the reporting period.
  • the network quality detection apparatus marks each data with the same reporting period with the same second label, and the second label may be the reporting period sequence number (Blocknum).
  • the data preprocessing process may also include the following steps: dividing the data into network element data, link data, and end-to-end data. It should be noted that the order of execution of this step, step 13' and step 14' is not limited, and can also be executed simultaneously.
  • determining the true path of the service flow (that is, step 14) according to the data, the static routing database, and the suspected path includes:
  • Step 141 According to the network element identification and port information and the static routing database, the network element data, link data, and end-to-end data are matched, and the first path of the service flow is formed according to the matching result.
  • the network quality detection device uses the directed graph topology search algorithm to match the network element data, link data, and end-to-end data according to the network element identification, port information, and static routing database to form multiple pieces of service flow.
  • the first path. Specifically, the matching result can be marked on the route of the suspected path until all the suspected paths in the suspected path set are marked.
  • Step 142 According to the flow direction of the service flow, sequentially mark the third label on the data on the first path.
  • the network quality detection device determines whether the link between the first and last PE devices of the first path is connected, that is, it determines the link between the first PE device and the P device, respectively. Whether the link between the adjacent P devices and the link between the P device and the tail PE device are connected, and a path that connects all the above three kinds of links is selected from the first path.
  • Step 143 It is judged whether the first path connected by each link is one of the suspected paths, if yes, step 144 is executed, otherwise, the flow is ended.
  • the network quality detection device determines whether the first path connected by each link is one of the suspected paths. If so, it means that the first path is the true path of the service flow; if the first path is not suspected One of the paths indicates that there may be a problem with the collected data, resulting in an error in the real path, then this process is ended.
  • Step 144 Use the first path as the real path of the service flow.
  • each data includes a first label, a second label, and a third label.
  • the first label is the service flow identifier (FlowID)
  • the second label is the reporting period number (Blocknum)
  • the third label is the service.
  • the first node NE1 and the fourth node NE4 are PE devices
  • the second node NE2 and the third node NE3 are P devices
  • the ingress of the service flow is port 1 of the first node NE1
  • the egress is port 8 of the fourth node NE4.
  • the real path of the service flow whose service flow identifier is 8 is shown by the arrow in Fig. 4, namely, NE1 ⁇ NE2 ⁇ NE3 ⁇ NE4.
  • the detection types of detection tasks include end-to-end detection and hop-by-hop detection.
  • the sending the subscription command to the network element device on the suspected path includes the following steps: determining the network element device on the suspected path for receiving the subscription command according to the detection type of the service flow, and Send a subscription command to the determined network element device.
  • the network element equipment includes the network side edge (PE) equipment
  • the detection type is the hop-by-hop detection type
  • the network element equipment includes the network side edge (PE) equipment and the core (P )equipment.
  • the network quality detection device reports to the nodes respectively A, B, C, and D send subscription commands. That is to say, for the end-to-end detection type, the detection task is only issued to the ingress and egress equipment of the service flow (ie PE equipment), not to the intermediate device (ie P device); for the hop-by-hop detection type, then The subscription command must be issued to the ingress and egress equipment (ie PE equipment) of the service flow, and also to the intermediate equipment (ie P equipment).
  • the detection type of each detection task can be initially configured as an end-to-end detection type, that is, the default configuration is an end-to-end detection type. It should be noted that, for reinsurance scenarios, hop-by-hop detection can be started from the beginning.
  • the detection type of the detection task can also be automatically modified. That is, the network quality detection method may further include the following steps: if a network failure is detected under the end-to-end detection type, the detection type is switched to the hop-by-hop detection type, and the transmission is sent to the PE device and the P device on the suspected path Used to indicate the subscription command to detect the service flow.
  • the network quality detection device detects a network failure in the end-to-end detection mode, and can automatically switch to the hop-by-hop detection mode without interrupting services and detection tasks, thereby improving detection quality and detection efficiency.
  • the The network quality detection method may also include the following steps:
  • Step 15' generate a network topology diagram of the service flow according to the real path, and mark and display the real path on the network topology diagram.
  • the network quality detection device In this step, the network quality detection device generates a network topology diagram about the current real path of the service flow. Taking the real path of the service flow as NE1 ⁇ NE2 ⁇ NE3 as an example, it can be presented to the user as shown in Figure 7. Figure 7 shows the path through The software simulates the display interface of the network topology diagram produced, in which the real path can be represented by a solid arrow. It should be noted that the network quality detection device may also mark the suspected path on the network topology map, and the suspected path may be represented by a dotted line.
  • step 15' is executed after step 16 as an example for description.
  • the method further includes:
  • step 16' if a network failure is detected, the failure is displayed on the real path of the network topology diagram.
  • the performance data at a certain moment can be selected, and the real path of the service flow at that moment can be displayed in the form of a directed topology diagram, as well as the performance data indicators of each link in the real path, which can be displayed in red according to the pre-configured indicator threshold.
  • Limited data so that faults can be delimited quickly, efficiently, and intuitively.
  • the end-to-end (NE1 node to NE3 node) delay performance data indicates that the connection appears in red, indicating that the end-to-end delay index has exceeded the limit.
  • this application visually displays the real path of the business at a certain moment in the form of network topology, and can display node failures and link failures, as well as the performance of each service flow from the inbound interface to the outbound interface.
  • Data indicators when performance data exceeds the limit, identify the over-limit data and the link where it is located, so that fault delimitation can be done quickly and intuitively.
  • the network quality detection method may also display data in various forms.
  • the data display forms can include the following:
  • the network quality detection device After receiving the data reported by each network element device, the network quality detection device refreshes the data in the form of a table, and displays the data that exceeds the limit in red according to the pre-configured index threshold.
  • the network quality detection device selects the network element data, link data and end-to-end data at a certain moment, and displays the change trend of real-time data in the form of a graph.
  • the data that exceeds the limit can be displayed in red according to the pre-configured indicator threshold. And can display peaks, valleys and threshold lines.
  • the network quality detection device selects the network element data, link data, and end-to-end data at a certain moment, and displays the change trend of the data in a specified time period in the form of a graph, which can be displayed in red according to the pre-configured indicator threshold Data beyond the limit, and can display peaks, valleys and indicator threshold lines.
  • This application uses in-band detection technology to detect network quality, which can display performance data changes in milliseconds in real time, which is a qualitative leap from traditional network quality detection methods; this application has both end-to-end detection and hop-by-hop detection capabilities.
  • the fault can be quickly and intuitively delimited by combining charts, trend charts and topological paths.
  • This application combines segment-by-segment performance data with the routing database in real time, and uses a directed graph topology search algorithm to achieve true path restoration, which can effectively solve the problem of difficulty in true path restoration in business scenarios such as active/standby path switching, ECMP, and eX2.
  • an embodiment of the present application also provides a network quality detection device.
  • the network quality detection device includes: a first determining module 1, a sending module 2, a receiving module 3, and a second determining module 4 and detection module 5.
  • the first determining module 1 is configured to determine the suspected path of the service flow used for detection according to a preset static routing database.
  • the sending module 2 is configured to send a subscription command for instructing to detect the service flow to the network element device on the suspected path.
  • the receiving module 3 is configured to receive data sent by the network element device, where the data is performance data in response to the subscription command.
  • the second determining module 4 is configured to determine the true path of the service flow according to the data, the static routing database and the suspected path.
  • the detection module 5 is configured to detect the network quality of the real path according to the data and a preset index threshold.
  • the data includes at least a service flow identifier and a timestamp
  • the network quality detection apparatus further includes a data processing module 6, and the data processing module 6 is configured to receive data sent by each of the network element devices in the receiving module 3.
  • the second determining module 4 determines the true path of the service flow according to the data, the static routing database and the suspected path, it marks the data with a first label according to the service flow identifier, where The first label of each data identified by the same service flow is the same; and, the reporting period of the data is determined according to the timestamp, and the second label is marked for the data according to the reporting period, wherein each data with the same reporting period The second label is the same.
  • the data further includes network element identification and port information
  • the data processing module 6 is further configured to: after the receiving module 3 receives the data sent by each of the network element devices, the second determining module 4 Before the data, the static routing database, and the suspected path determine the true path of the service flow, the data is divided into network element data, link data, and end-to-end data.
  • the second determining module 4 is configured to match the network element data, the link data, and the end-to-end data according to the network element identification and port information and the static routing database, and form the service according to the matching result
  • the data processing module 6 is further configured to sequentially mark the data on the first path with a third label according to the flow direction of the service flow.
  • the sending module 2 is configured to determine the network element device used to receive the subscription command on the suspected path according to the detection type of the service flow, and send the subscription command to the determined network element device;
  • the detection type is an end-to-end detection type
  • the network element device includes a network-side edge device
  • the detection type is a hop-by-hop detection type
  • the network element device includes a network-side edge device and a core device.
  • the detection type is initially configured as an end-to-end detection type.
  • the network quality detection device further includes a type switching module 7, and the type switching module 7 is used to: When a network failure is detected under the detection type, the detection type is switched to a hop-by-hop detection type, and the sending module is instructed to send the subscription command to the network-side edge device and the core device on the suspected path.
  • the network quality detection device further includes a display module 8, and the display module 8 is configured to generate a network topology diagram of the service flow according to the real path, and display it in the network topology diagram.
  • the real path is marked and displayed; when the detection module detects a network failure, the failure is displayed on the real path of the network topology diagram.
  • An embodiment of the present application also provides a server, which includes: one or more processors and a storage device; wherein, one or more programs are stored on the storage device, and when the above-mentioned one or more programs are used by the above-mentioned one or more When executed by each processor, the above-mentioned one or more processors implement the network quality detection method provided in the foregoing embodiments.
  • the embodiments of the present application also provide a computer-readable medium on which a computer program is stored, wherein the computer program implements the network quality detection method provided in the foregoing embodiments when the computer program is executed.
  • the functional modules/units in the device can be implemented as software, firmware, hardware, and appropriate combinations thereof.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may consist of several physical components.
  • the components are executed cooperatively.
  • Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit .
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium).
  • the term computer storage medium includes volatile and non-volatile data implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or Any other medium used to store desired information and that can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供一种网络质量检测方法，根据预设的静态路由数据库确定用于检测的业务流的疑似路径，向疑似路径上的网元设备发送订阅命令，并接收网元设备发送的响应订阅命令的数据，根据该数据、静态路由数据库和疑似路径确定业务流的真实路径，并根据该数据和预设的指标阈值，在真实路径上检测网络质量。本申请实施例还提供一种网络质量检测装置、服务器和计算机可读介质。

Description

网络质量检测方法、装置、服务器和计算机可读介质
相关申请的交叉引用
本申请基于申请号为201911102257.7、申请日为2019年11月12日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请涉及计算机网络技术领域，具体涉及一种网络质量检测方法、装置、服务器和计算机可读介质。
背景技术
随着5G通信网络的到来，垂直行业对网络指标要求更为苛刻，给承载网运维带来了巨大挑战。传统网络OAM(Operations，Administration，and Maintenance，操作管理维护)检测技术均为带外(Out-Of-Band)检测技术，采用在模拟业务路径上发送模拟业务报文的方式间接检测网络质量，例如，对MPLS-TP(Multi Protocol Label Switching-Transport Profi le，多协议标签交换传送应用)进行OAM、TWAMP(Two-Way Active Measurement Protocol，双向主动测量协议)等。其缺点是无法保证模拟报文与真实业务路径一致，无法应用于主备倒换、ECMP(Equal-Cost Multipath Routing，等价路由)等业务场景，不能完全真实反应SLA(Service Level Agreement,网络业务质量)，特别是无法捕获少量丢包这类静默故障。另外，传统的带外OAM检测方 法性能数据采集周期为分钟级或亚分钟级，承载网只能等业务发生故障或质量劣化之后才能被动响应周边部门投诉定位，无法完全实时反映网络质量。而且，传统带外OAM检测方法因无法逐跳检测，问题难以精确定界，经常需要多团队协同定位，定位周期长达数天甚至数周。
带内OAM是指直接将需要携带的OAM信息和数据封装在用户数据报文中，可以随数据报文一起发送，而不需要额外的控制报文发送OAM数据。带内OAM可以实现多种网络故障检测功能，例如，包路径一致性检测、POT(Proof of Transit,传输路径)验证、SLA检测等。带内OAM域的边缘节点将带内OAM数据嵌入在数据报文中，所以该节点又称为带内OAM封装节点，带内OAM域的边缘节点将OAM数据报文移除，因此该节点又称为带内OAM解封装节点。带内OAM网络质量检测对象可以是SR(Segment Routing，分段路由)-TP(Transport Profile，传输应用)/TE(Traffic Engineering，流量工程)隧道、SR-BE(Best Effort,尽力而为的段路由)隧道，或承载的IP(Internet Protocol，互联网协议地址)业务流。现有的带内网络质量检测方案包括：MPLS-TP-OAM、CFM(Connectivity Fault Management，连接故障管理)、TWAMP(Tow-Way Active Measurement Protocol，双向主动测量协议)等。上述检测方案存在明显的不足：检测实现过程配置复杂、操作维护成本高，且并不能很好地支持全业务路径逐段检测，更重要的是检测的结果反映的并不是真实的业务路径。
发明内容
本申请实施例提供一种网络质量检测方法、装置、服务器和计算机可读介质。
本申请实施例提供一种网络质量检测方法，所述方法包括：根据预设的静态路由数据库确定用于检测的业务流的疑似路径；向所述疑似路 径上的网元设备发送用于指示检测所述业务流的订阅命令，并接收所述网元设备发送的数据，所述数据为响应所述订阅命令的性能数据；根据所述数据、所述静态路由数据库和所述疑似路径，确定所述业务流的真实路径；根据所述数据和预设的指标阈值，检测所述真实路径的网络质量。
本申请实施例还提供一种网络质量检测装置，包括：第一确定模块、发送模块、接收模块、第二确定模块和检测模块；所述第一确定模块用于，根据预设的静态路由数据库确定用于检测的业务流的疑似路径；所述发送模块用于，向所述疑似路径上的网元设备发送用于指示检测所述业务流的订阅命令；所述接收模块用于，接收所述网元设备发送的数据，所述数据为响应所述订阅命令的性能数据；所述第二确定模块用于，根据所述数据、所述静态路由数据库和所述疑似路径，确定所述业务流的真实路径；所述检测模块用于，根据所述数据和预设的指标阈值，检测所述真实路径的网络质量。
本申请实施例还提供一种服务器，该服务器包括：一个或多个处理器以及存储装置；其中，存储装置上存储有一个或多个程序，当上述一个或多个程序被上述一个或多个处理器执行时，使得上述一个或多个处理器实现如前述各实施例所提供的网络质量检测方法。
本申请实施例还提供了一种计算机可读介质，其上存储有计算机程序，其中，该计算机程序被执行时实现如前述各实施例所提供的网络质量检测方法。
附图说明
图1为本申请一实施例提供的网络质量检测方法的流程图；
图2为本申请实施例提供的数据预处理的流程图；
图3为本申请实施例提供的确定真实路径的流程图；
图4为本申请实施例提供的数据预处理的示例；
图5为本申请实施例提供的逐跳检测类型示例；
图6为本申请又一实施例提供的网络质量检测方法的流程图；
图7为本申请实施例提供的显示真实路径及故障的示意图；
图8为本申请另一实施例提供的网络质量检测装置结构示意图；
图9为本申请又一实施例提供的网络质量检测装置结构示意图；
图10为本申请再一实施例提供的网络质量检测装置结构示意图；
图11为本申请另一实施例提供的网络质量检测装置结构示意图。
具体实施方式
在下文中将参考附图更充分地描述示例实施例，但是所述示例实施例可以以不同形式来体现且不应当被解释为限于本文阐述的实施例。反之，提供这些实施例的目的在于使本申请透彻和完整，并将使本领域技术人员充分理解本申请的范围。
如本文所使用的，术语“和/或”包括一个或多个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述特定实施例，且不意欲限制本申请。如本文所使用的，单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。还将理解的是，当本说明书中使用术语“包括”和/或“由……制成”时，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加一个或多个其他特征、整体、步骤、操作、元件、组件和/或其群组。
本文所述实施例可借助本申请的理想示意图而参考平面图和/或截面图进行描述。因此，可根据制造技术和/或容限来修改示例图示。因此，实施例不限于附图中所示的实施例，而是包括基于制造工艺而形成的配置的修改。因此，附图中例示的区具有示意性属性，并且图中所示 区的形状例示了元件的区的具体形状，但并不旨在是限制性的。
除非另外限定，否则本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本申请的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本文明确如此限定。
本申请的一个实施例提供一种网络质量检测方法，所述方法可以应用但不限于对5G(5th-Generation，第五代移动通信技术)网络质量进行检测。所述方法应用于包括网络质量检测装置(例如管控服务器)、数据采集服务器和若干用于承载业务流的网元设备的系统中。在初始化阶段，执行以下操作：1、配置通用的检测参数，通用的检测参数可以包括压缩格式、上报通道、上报协议等，例如，压缩格式可以为GPB、GPB-KV等，上报通道可以为DCN(Data Communication Network，数据通信网络)通道，上报协议可以为UDP(User Datagram Protocol，用户数据报协议)、gRPC(Remote Procedure Call，远程过程调用)协议；2、选择检测对象(即用于检测的业务流)并配置检测任务参数，检测任务参数可以包括隧道参数、检测类型及与检测任务相关的订阅、染色、封装、解封装命令参数等；以L3VPN(Virtual Private Network，虚拟专用网)的IP业务流为例，其检测任务参数可以包括业务流标识、检测类型、源网元、业务接入点、源IP(IPV4/IPV6都支持)、源端口、协议号、宿IP、宿端口、DSCP(Differentiated Services Code Point，差分服务代码点)优先级、时延优先级、上报周期等。
以下结合图1，对本实施例的网络质量检测方法进行详细说明。如图1所示，所述方法包括以下步骤：
步骤11，根据预设的静态路由数据库确定用于检测的业务流的疑似路径。
在本步骤中，网络质量检测装置查询静态路由数据库，识别用于检测的业务流所有可能的路由信息、PE(Provider Edge，网络侧边缘) 设备及P(Provider，核心)设备，并根据路由信息、PE设备和P设备确定该业务流的疑似路径。在本申请实施例中，同一个业务流在不同时刻可以有不同路径，但是在同一时刻该业务流具有唯一的路径，在本步骤中，将该业务流在不同时刻可能的路径汇总，形成疑似路径集合。
步骤12，向疑似路径上的网元设备发送用于指示检测所述业务流的订阅命令。
在本步骤中，网络质量检测装置首先确定各疑似路径上的网元设备，网元设备包括PE设备和P设备。然后分别向确定出的网元设备发送订阅命令，以下发检测所述业务流的检测任务。订阅命令中携带有通用检测参数和该检测任务的参数。具体的，网络质量检测装置向数据采集服务器发送订阅命令，由数据采集服务器将订阅命令分别发送给各疑似路径上的网元设备。
步骤13，接收各网元设备发送的数据。
网元设备发送的数据为响应订阅命令的性能数据，可以包括丢包数、丢包率、时延、抖动等。网元设备可以利用Telemetry协议向数据采集服务器实时上报本设备的性能数据(即单点性能数据)，数据采集服务器将各网元设备上报的性能数据上报给网络质量检测装置。网络质量检测装置根据编码及压缩格式解析该数据获取必要的信息(包括FlowID、时间戳、计数信息等)。需要说明的是，为了保证数据解析的正确性，必须保证各网元设备的时间同步，以及各网元设备上报的数据完整。
步骤14，根据数据、静态路由数据库和疑似路径，确定业务流的真实路径。
由于各网元设备发送的数据为实时数据，而相同时刻业务流具有唯一的路径，因此，根据所述数据可以确定出某一时刻下该业务流的唯一的真实路径。根据数据、静态路由数据库和疑似路径确定业务流的真实路径的具体实现方式，后续结合附图4再详细说明。
步骤15，根据数据和预设的指标阈值，检测真实路径的网络质量。
所述指标阈值可以是以业务流为单位设置的，即针对每个业务流设置一系列相关的性能指标阈值，所述阈值也可以是根据业务类型设置的，即针对每种业务类型，设置一系列相关的性能指标阈值。
在本步骤中，网络质量检测装置将真实路径上各网元设备上报的数据与相应的指标阈值相比较，若数据满足相应的性能指标条件，则认为该性能指标合格；若数据不满足相应的性能指标条件，则认为该节点或链路故障。
通过步骤11-15可以看出，在本申请的实施例中，根据预设的静态路由数据库确定用于检测的业务流的疑似路径，向疑似路径上的网元设备发送订阅命令，并接收网元设备发送的响应订阅命令的数据，根据该数据静态路由数据库和疑似路径确定业务流的真实路径，并根据该数据和预设的指标阈值，在真实路径上检测网络质量。本申请利用带内随流检测方式反映真实的SLA，能够提供端到端和逐跳SLA检测能力，可实时感知网络性能指标，实现快速、精准定界网络故障；通过将逐段的设备性能数据和路由数据库实时结合实现真实路径还原，可以有效解决主备路径倒换、ECMP及eX2等业务场景下的真实路径还原困难的问题。本申请的方案配置简单、操作维护成本低，易于实现。
在本申请另一实施例中，在接收各网元设备发送的数据(即步骤13)之后，根据数据、静态路由数据库和疑似路径确定业务流的真实路径(即步骤14)之前，还可以对接收到的数据进行预处理。所述数据至少包括业务流标识(FlowID)和时间戳，如图2所示，数据预处理过程可以包括以下步骤：
步骤13’，根据业务流标识为数据标记第一标签。
在本步骤中，网络质量检测装置将具有相同业务流标识的各数据标记相同的第一标签，第一标签可以为业务流标识，业务流标识由网络质量检测装置统一分配，保证检测域内全局唯一。
步骤14’，根据时间戳确定数据的上报周期，并根据上报周期为数据标记第二标签。
在本步骤中，网络质量检测装置将具有相同上报周期的各数据标记相同的第二标签，第二标签可以为上报周期序号(Blocknum)。
进一步的，数据预处理过程还可以包括以下步骤：将数据划分为网元数据、链路数据和端对端数据。需要说明的是，本步骤与步骤13’、步骤14’的执行顺序不限，也可以同步执行。
在本申请的一些实施例中，如图3所示，根据数据、静态路由数据库和疑似路径，确定业务流的真实路径(即步骤14)，包括：
步骤141，根据网元标识和端口信息和所述静态路由数据库，匹配网元数据、链路数据和端对端数据，并根据匹配结果形成业务流的第一路径。
在本步骤中，网络质量检测装置利用有向图拓扑搜索算法，根据网元标识、端口信息和静态路由数据库，匹配网元数据、链路数据和端对端数据，以形成业务流的多条第一路径。具体的，可以将匹配结果在疑似路径的路由上进行标注，直到疑似路径集合中所有的疑似路径均被标注。
步骤142，按照业务流的流向,对第一路径上的数据顺序标记第三标签。
在本步骤中，针对每条第一路径，网络质量检测装置判断该第一路径的首、尾PE设备之间的链路是否连通，即分别判断首PE设备与P设备之间的链路、相邻P设备间的链路以及P设备与尾PE设备间的链路是否连通，并从第一路径中选择出上述三种链路均连通的路径。
步骤143，判断各段链路均连通的第一路径是否为疑似路径之一，若是，则执行步骤144，否则，结束本流程。
在本步骤中，网络质量检测装置判断各段链路均连通的第一路径是否为疑似路径中的一条，若是，说明该第一路径即为业务流的真实路径；若该第一路径不是疑似路径中的一条，说明采集到的数据可能存在问题，导致真实路径有误，则结束本流程。
步骤144，将所述第一路径作为业务流的真实路径。
如图4所示，每个数据均包括第一标签、第二标签和第三标签，第一标签为业务流标识(FlowID)，第二标签为上报周期编号(Blocknum)，第三标签为业务流序列号(SequenceID)。第一节点NE1和第四节点NE4为PE设备，第二节点NE2和第三节点NE3为P设备，该业务流的入口为第一节点NE1的端口1，出口为第四节点NE4的端口8，业务流标识为8的业务流的真实路径如图4中箭头所示，即NE1→NE2→NE3→NE4。
需要说明的是，在完成业务流的真实路径还原后，还需将相关数据入库保存。
检测任务的检测类型包括端到端检测和逐跳检测。在一些实施例中，所述向疑似路径上的网元设备发送订阅命令(即步骤12)，包括以下步骤：根据业务流的检测类型确定疑似路径上用于接收订阅命令的网元设备，并向确定出的网元设备发送订阅命令。其中，当检测类型为端到端检测类型时，网元设备包括网络侧边缘(PE)设备；当检测类型为逐跳检测类型时，网元设备包括网络侧边缘(PE)设备和核心(P)设备。如图5所示，检测域内有2个PE设备(即节点A和D)，以及2个P设备(即节点B和C)，针对逐跳检测类型的检测任务，网络质量检测装置分别向节点A、B、C、D发送订阅命令。也就是说，针对端到端检测类型，检测任务只下发给业务流的入口和出口设备(即PE设备)，不会下发给中间设备(即P设备)；针对逐跳检测类型，则订阅命令既要下发给业务流的入口和出口设备(即PE设备)，也要下发给中间设备(即P设备)。
各检测任务的检测类型可以初始配置为端到端检测类型，即默认配置为端到端检测类型。需要说明的是，对于重保场景，可以一开始就启动逐跳检测。
在本申请一些实施例中，还可以自动对检测任务的检测类型进行修改。即所述网络质量检测方法还可以包括以下步骤：若在端到端检测类 型下检测出网络存在故障，则将检测类型切换为逐跳检测类型，并向疑似路径上的PE设备和P设备发送用于指示检测该业务流的订阅命令。也就是说，网络质量检测装置在端到端检测模式下检测出网络存在故障，可以在不中断业务和检测任务的前提下自动切换到逐跳检测模式，提升检测质量和检测效率。
进一步的，为了实现直观的对故障进行定界，在一些实施例中，如图6所示，在根据数据、静态路由数据库和疑似路径确定业务流的真实路径(即步骤15)之后，所述网络质量检测方法还可以包括以下步骤：
步骤15’，根据真实路径生成业务流的网络拓扑图，并在网络拓扑图上标记并显示真实路径。
在本步骤中，网络质量检测装置生成关于业务流当前真实路径的网络拓扑图，以业务流的真实路径为NE1→NE2→NE3为例，可以按照图7所示呈现给用户，图7为经过软件模拟生产的网络拓扑图的显示界面，其中，真实路径可以通过实线箭头表示。需要说明的是，网络质量检测装置也可以在网络拓扑图上标记疑似路径，疑似路径可以通过虚线表示。
需要说明的是，本步骤与步骤16的执行顺序不限，也可以同步执行，在本实施例中，以在步骤16之后执行步骤15’为例进行说明。
进一步的，如图6所示，在根据数据和预设的指标阈值，检测真实路径的网络质量(即步骤15)之后，所述方法还包括：
步骤16’，若检测出网络故障，则在网络拓扑图的真实路径上显示故障。
可以选择某一时刻的性能数据，用有向拓扑图的形式展示业务流在该时刻的真实路径，以及真实路径中各段链路的性能数据指标，可以根据事先配置的指标阈值用红色显示越限的数据，这样就可以快速、高效、直观地定界故障。如图7所示，端到端(NE1节点到NE3节点)的时延性能数据示意连线出现红色，表示端到端的时延指标越限了。在拓扑图上看到尾节点NE3及上一个节点NE2之间链路的时延数据示意连线也是 红色，而其它的节点和链路的颜色都是正常的，这样就可以快速、直观地确定出是尾节点NE3前一个节点NE2的某端口到尾节点NE3的某端口之间的时延过大造成了整个业务流的时延指标过大。
本申请通过选择实时性能数据，以络拓扑的形式直观展示业务在某个时刻的真实路径，并能够展示节点故障和链路故障，以及展示每个业务流从入接口到出接口之间的性能数据指标，在有性能数据越限时标识出该越限数据以及所在链路，这样就可以快速、直观地做到故障定界。而且，通过持续观察和对比，可以方便、直观地观察到业务路径是否发生变化，从而确定业务路径是否发生了主备倒换。
进一步的，在本申请一些实施例中，在步骤13之后，所述网络质量检测方法还可以以各种形式展示数据。具体的，数据展示形式可以包括以下几种：
1、实时图表展示。网络质量检测装置接收到各网元设备上报的数据后以表格的形式刷新数据，并根据事先配置的指标阈值用红色显示越限的数据。
2、实时趋势图展示。网络质量检测装置选择某一时刻的网元数据、链路数据和端对端数据，通过曲线图的形式关联展示实时数据的变化趋势，可以根据事先配置的指标阈值用红色显示越限的数据，并可以展示峰值、谷值和阈值线。
3、历史趋势图展示。网络质量检测装置选择某一时刻的网元数据、链路数据和端对端数据，通过曲线图的形式关联展示某个指定时间段内数据的变化趋势，可以根据事先配置的指标阈值用红色显示越限的数据，并可以展示峰值、谷值和指标阈值线。
当检测出网络故障时，为了做进一步分析，可以进一步查看相关数据的历史趋势图，这样可以确定该数据在历史时间段内是否持续越限，还是在该时刻突发性的指标越限。
本申请采用带内检测技术检测网络质量，可以毫秒级实时展示性能数据的变化，相对于传统的网络质量检测方法有了质的飞跃；本申请同 时具有端到端检测和逐跳检测的能力，可以结合图表、趋势图和拓扑路径的方式快速、直观的对故障进行定界。本申请将逐段性能数据和路由数据库实时结合，利用有向图拓扑搜索算法实现真实路径还原，可以有效解决主备路径倒换、ECMP及eX2等业务场景下的真实路径还原困难的问题。
基于相同的技术构思，本申请实施例还提供一种网络质量检测装置，如图9所示，该网络质量检测装置包括：第一确定模块1、发送模块2、接收模块3、第二确定模块4和检测模块5。
第一确定模块1用于，根据预设的静态路由数据库确定用于检测的业务流的疑似路径。
发送模块2用于，向所述疑似路径上的网元设备发送用于指示检测所述业务流的订阅命令。
接收模块3用于，接收所述网元设备发送的数据，所述数据为响应所述订阅命令的性能数据。
第二确定模块4用于，根据所述数据、所述静态路由数据库和所述疑似路径，确定所述业务流的真实路径。
检测模块5用于，根据所述数据和预设的指标阈值，检测所述真实路径的网络质量。
在一些实施例中，所述数据至少包括业务流标识和时间戳，所述网络质量检测装置还包括数据处理模块6，数据处理模块6用于，在接收模块3接收各所述网元设备发送的数据之后、第二确定模块4根据所述数据、所述静态路由数据库和所述疑似路径确定所述业务流的真实路径之前，根据业务流标识为所述数据标记第一标签，其中，具有相同业务流标识的各数据的第一标签相同；以及，根据时间戳确定所述数据的上报周期，并根据所述上报周期为所述数据标记第二标签，其中，具有相同上报周期的各数据的第二标签相同。
在一些实施例中，所述数据还包括网元标识和端口信息，数据处理 模块6还用于，在接收模块3接收各所述网元设备发送的数据之后、第二确定模块4根据所述数据、所述静态路由数据库和所述疑似路径确定所述业务流的真实路径之前，将所述数据划分为网元数据、链路数据和端对端数据。
第二确定模块4用于，根据网元标识和端口信息和所述静态路由数据库，匹配所述网元数据、所述链路数据和所述端对端数据，并根据匹配结果形成所述业务流的第一路径；当所述第一的各段链路均连通且所述第一路径为所述疑似路径之一时，将所述第一路径作为所述业务流的真实路径。
数据处理模块6还用于，按照所述业务流的流向,对所述第一路径上的数据顺序标记第三标签。
在一些实施例中，发送模块2用于，根据所述业务流的检测类型确定所述疑似路径上用于接收订阅命令的网元设备，并向确定出的网元设备发送所述订阅命令；当所述检测类型为端到端检测类型时，所述网元设备包括网络侧边缘设备；当所述检测类型为逐跳检测类型时，所述网元设备包括网络侧边缘设备和核心设备。
在一些实施例中，所述检测类型初始配置为端到端检测类型，如图10所示，所述网络质量检测装置还包括类型切换模块7，类型切换模块7用于，当在端到端检测类型下检测出网络存在故障时，将所述检测类型切换为逐跳检测类型，并指示所述发送模块向所述疑似路径上的网络侧边缘设备和核心设备发送所述订阅命令。
在一些实施例中，如图11所示，网络质量检测装置还包括显示模块8，显示模块8用于，根据所述真实路径生成所述业务流的网络拓扑图，并在所述网络拓扑图上标记并显示所述真实路径；当所述检测模块检测出网络故障时，在所述网络拓扑图的所述真实路径上显示所述故障。
本申请实施例还提供了一种服务器，该服务器包括：一个或多个处理器以及存储装置；其中，存储装置上存储有一个或多个程序，当上述一个或多个程序被上述一个或多个处理器执行时，使得上述一个或多个 处理器实现如前述各实施例所提供的网络质量检测方法。
本申请实施例还提供了一种计算机可读介质，其上存储有计算机程序，其中，该计算机程序被执行时实现如前述各实施例所提供的网络质量检测方法。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
本文已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则可单独使用与特定实施例相结合描述的特征、特性和/或元素，或可与其他实施例相结合描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本发明的范围的 情况下，可进行各种形式和细节上的改变。

Claims (10)

  1. 一种网络质量检测方法，所述方法包括：
    根据预设的静态路由数据库确定用于检测的业务流的疑似路径；
    向所述疑似路径上的网元设备发送用于指示检测所述业务流的订阅命令，并接收所述网元设备发送的数据，所述数据为响应所述订阅命令的性能数据；
    根据所述数据、所述静态路由数据库和所述疑似路径，确定所述业务流的真实路径；
    根据所述数据和预设的指标阈值，检测所述真实路径的网络质量。
  2. 如权利要求1所述的方法，其中，所述数据至少包括业务流标识和时间戳，在接收各所述网元设备发送的数据之后、根据所述数据、所述静态路由数据库和所述疑似路径，确定所述业务流的真实路径之前，所述方法还包括：
    根据业务流标识为所述数据标记第一标签，其中，具有相同业务流标识的各数据的第一标签相同；
    根据时间戳确定所述数据的上报周期，并根据所述上报周期为所述数据标记第二标签，其中，具有相同上报周期的各数据的第二标签相同。
  3. 如权利要求2所述的方法，其中，所述数据还包括网元标识和端口信息，在接收各所述网元设备发送的数据之后、根据所述数据、所述静态路由数据库和所述疑似路径，确定所述业务流的真实路径之前，所述方法还包括：将所述数据划分为网元数据、链路数据和端对端数据；
    所述根据所述数据、所述静态路由数据库和所述疑似路径，确定所述业务流的真实路径，包括：
    根据网元标识、端口信息和所述静态路由数据库，匹配所述网元数据、所述链路数据和所述端对端数据，并根据匹配结果形成所述业务流的第一路径；
    按照所述业务流的流向,对所述第一路径上的数据顺序标记第三标签；
    响应于所述第一路径的各段链路均连通且所述第一路径为所述疑似路径之一，将所述第一路径作为所述业务流的真实路径。
  4. 如权利要求1所述的方法，其中，向所述疑似路径上的网元设备发送用于指示检测所述业务流的订阅命令，包括：
    根据所述业务流的检测类型确定所述疑似路径上用于接收所述订阅命令的网元设备，并向确定出的网元设备发送所述订阅命令；当所述检测类型为端到端检测类型时，所述网元设备包括网络侧边缘设备；或者，当所述检测类型为逐跳检测类型时，所述网元设备包括网络侧边缘设备和核心设备。
  5. 如权利要求4所述的方法，其中，所述检测类型初始配置为端到端检测类型；所述方法还包括：
    若在端到端检测类型下检测出网络存在故障，则将所述检测类型切换为逐跳检测类型，并向所述疑似路径上的网络侧边缘设备和核心设备发送所述订阅命令。
  6. 如权利要求1-5任一项所述的方法，其中，在所述根据所述数据、所述静态路由数据库和所述疑似路径，确定所述业务流的真实路径之后，所述方法还包括：根据所述真实路径生成所述业务流的网络拓扑图，并在所述网络拓扑图上标记并显示所述真实路径；
    在所述根据所述数据和预设的指标阈值，检测所述真实路径的网络质量之后，所述方法还包括：若检测出网络故障，则在所述网络拓扑图的所述真实路径上显示所述故障。
  7. 一种网络质量检测装置，包括：第一确定模块、发送模块、接收模块、第二确定模块和检测模块；
    所述第一确定模块用于，根据预设的静态路由数据库确定用于检测的业务流的疑似路径；
    所述发送模块用于，向所述疑似路径上的网元设备发送用于指示检测所述业务流的订阅命令；
    所述接收模块用于，接收所述网元设备发送的数据，所述数据为响应所述订阅命令的性能数据；
    所述第二确定模块用于，根据所述数据、所述静态路由数据库和所述疑似路径，确定所述业务流的真实路径；
    所述检测模块用于，根据所述数据和预设的指标阈值，检测所述真实路径的网络质量。
  8. 如权利要求7所述的网络质量检测装置，其中，所述发送模块用于，根据所述业务流的检测类型确定所述疑似路径上用于接收订阅命令的网元设备，并向确定出的网元设备发送所述订阅命令；当所述检测类型为端到端检测类型时，所述网元设备包括网络侧边缘设备；或者，当所述检测类型为逐跳检测类型时，所述网元设备包括网络侧边缘设备和核心设备。
  9. 一种服务器，包括：
    一个或多个处理器；
    存储装置，其上存储有一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如权利要求1-6任一项所述的网络质量检测方法。
  10. 一种计算机可读介质，其上存储有计算机程序，其中，所述程序被执行时实现如权利要求1-6任一项所述的网络质量检测方法。
PCT/CN2020/127327 2019-11-12 2020-11-07 网络质量检测方法、装置、服务器和计算机可读介质 WO2021093692A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911102257.7A CN112866043B (zh) 2019-11-12 2019-11-12 网络质量检测方法、装置、服务器和计算机可读介质
CN201911102257.7 2019-11-12

Publications (1)

Publication Number Publication Date
WO2021093692A1 true WO2021093692A1 (zh) 2021-05-20

Family

ID=75911777

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/127327 WO2021093692A1 (zh) 2019-11-12 2020-11-07 网络质量检测方法、装置、服务器和计算机可读介质

Country Status (2)

Country Link
CN (1) CN112866043B (zh)
WO (1) WO2021093692A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114584485A (zh) * 2022-01-30 2022-06-03 阿里巴巴（中国）有限公司 检测边缘网络质量的方法、装置、设备和计算机可读存储介质
CN115174449A (zh) * 2022-05-30 2022-10-11 杭州初灵信息技术股份有限公司 一种传递随流检测信息的方法、系统、装置和存储介质
CN115277491A (zh) * 2022-06-15 2022-11-01 中国联合网络通信集团有限公司 异常数据的确定方法、装置及计算机可读存储介质
CN115580568A (zh) * 2022-11-16 2023-01-06 北京连星科技有限公司 基于IPv6流标签实现网络服务质量保障的方法及系统
WO2023241520A1 (zh) * 2022-06-15 2023-12-21 华为技术有限公司 随流检测方法、装置、设备、系统及存储介质
WO2024088064A1 (zh) * 2022-10-28 2024-05-02 中兴通讯股份有限公司 带内操作维护管理oam测量方法及系统

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113644998B (zh) * 2021-08-23 2023-06-09 烽火通信科技股份有限公司 一种5g网络的ioam时延测量方法和装置
CN113810229B (zh) * 2021-09-16 2023-12-05 烽火通信科技股份有限公司 一种基于时序调度的ioam质量性能数据分析方法和装置
CN114189908B (zh) * 2021-12-17 2024-06-04 中国联合网络通信集团有限公司 通信方法、装置、设备及存储介质
CN114679369B (zh) * 2022-05-10 2023-09-19 中国联合网络通信集团有限公司 数据处理方法、装置、设备、系统及存储介质
WO2023241122A1 (zh) * 2022-06-17 2023-12-21 华为云计算技术有限公司 一种网络链路故障诊断方法以及装置
CN116996392B (zh) * 2023-09-27 2023-12-29 山东省计算中心（国家超级计算济南中心） 一种基于加权有向图算法的流量路径重构方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6363053B1 (en) * 1999-02-08 2002-03-26 3Com Corporation Method and apparatus for measurement-based conformance testing of service level agreements in networks
CN105490962A (zh) * 2015-12-04 2016-04-13 哈尔滨工程大学 一种基于OpenFlow网络的QoS管理方法
US20180234342A1 (en) * 2017-02-16 2018-08-16 Timur Voloshin Method and program product for electronic communication based on user action
CN108449267A (zh) * 2018-03-15 2018-08-24 东北大学 一种基于链路质量估计的可靠路由算法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009246500A (ja) * 2008-03-28 2009-10-22 Fujitsu Ltd Ｉｐネットワークにおけるルートシミュレーション方法及びルートシミュレーションシステム
JP5413238B2 (ja) * 2010-02-24 2014-02-12 富士通株式会社 ルータ、管理装置およびルーティング制御プログラム
WO2014089772A1 (zh) * 2012-12-12 2014-06-19 华为技术有限公司 链路检测方法及装置
WO2015120601A1 (zh) * 2014-02-13 2015-08-20 华为技术有限公司 移动通信网络检测方法和装置
US9853882B2 (en) * 2014-07-23 2017-12-26 Cisco Technology, Inc. Dynamic path switchover decision override based on flow characteristics
WO2016045098A1 (zh) * 2014-09-26 2016-03-31 华为技术有限公司 交换机、控制器、系统及链路质量检测方法
CN107294849B (zh) * 2016-04-13 2022-05-13 中兴通讯股份有限公司 业务路径的建立方法、装置及系统
CN110120878B (zh) * 2018-02-05 2020-10-23 华为技术有限公司 获取链路质量的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6363053B1 (en) * 1999-02-08 2002-03-26 3Com Corporation Method and apparatus for measurement-based conformance testing of service level agreements in networks
CN105490962A (zh) * 2015-12-04 2016-04-13 哈尔滨工程大学 一种基于OpenFlow网络的QoS管理方法
US20180234342A1 (en) * 2017-02-16 2018-08-16 Timur Voloshin Method and program product for electronic communication based on user action
CN108449267A (zh) * 2018-03-15 2018-08-24 东北大学 一种基于链路质量估计的可靠路由算法

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114584485A (zh) * 2022-01-30 2022-06-03 阿里巴巴（中国）有限公司 检测边缘网络质量的方法、装置、设备和计算机可读存储介质
CN114584485B (zh) * 2022-01-30 2023-10-31 阿里巴巴（中国）有限公司 检测边缘网络质量的方法、装置、设备和计算机可读存储介质
CN115174449A (zh) * 2022-05-30 2022-10-11 杭州初灵信息技术股份有限公司 一种传递随流检测信息的方法、系统、装置和存储介质
CN115174449B (zh) * 2022-05-30 2024-03-26 杭州初灵信息技术股份有限公司 一种传递随流检测信息的方法、系统、装置和存储介质
CN115277491A (zh) * 2022-06-15 2022-11-01 中国联合网络通信集团有限公司 异常数据的确定方法、装置及计算机可读存储介质
CN115277491B (zh) * 2022-06-15 2023-06-06 中国联合网络通信集团有限公司 异常数据的确定方法、装置及计算机可读存储介质
WO2023241520A1 (zh) * 2022-06-15 2023-12-21 华为技术有限公司 随流检测方法、装置、设备、系统及存储介质
WO2024088064A1 (zh) * 2022-10-28 2024-05-02 中兴通讯股份有限公司 带内操作维护管理oam测量方法及系统
CN115580568A (zh) * 2022-11-16 2023-01-06 北京连星科技有限公司 基于IPv6流标签实现网络服务质量保障的方法及系统
CN115580568B (zh) * 2022-11-16 2023-03-24 北京连星科技有限公司 基于IPv6流标签实现网络服务质量保障的方法及系统

Also Published As

Publication number Publication date
CN112866043A (zh) 2021-05-28
CN112866043B (zh) 2024-06-18

Similar Documents

Publication Publication Date Title
WO2021093692A1 (zh) 网络质量检测方法、装置、服务器和计算机可读介质
WO2021093574A1 (zh) 网络质量检测方法、装置、网元设备、计算机设备和计算机可读介质
CN113079091B (zh) 一种主动随流检测的方法、网络设备以及通信系统
US8774045B2 (en) Packet loss detecting method and apparatus, and router
US8850324B2 (en) Visualization of changes and trends over time in performance data over a network path
CN107465565B (zh) 链路测试方法和装置及系统
US9489279B2 (en) Visualization of performance data over a network path
EP2884697B1 (en) Measuring method, device and system for network packet loss
EP2903214B1 (en) Measuring method, device and system for network packet loss
US20230006906A1 (en) In-situ flow detection method and apparatus
US20070064611A1 (en) Method for monitoring packet loss ratio
CN106487605B (zh) 丢包率检测方法及装置
US20090268622A1 (en) Route Tracing Program Configured to Detect Particular Network Element Making Type of Service Modification
US20140293798A1 (en) Mpls-tp network and link trace method thereof
US20150036510A1 (en) Method and device for measuring ethernet performance
US20160337212A1 (en) Uplink Performance Management
CN113328901B (zh) 报文乱序检测方法、装置及系统
CN105634935A (zh) 一种服务层信号失效检测装置及方法
CN105812198B (zh) 桥接网络端到端的监测方法和装置
WO2012142753A1 (zh) Ip承载网性能监控的方法及设备
US11582156B2 (en) Traffic detection method, apparatus, and system
WO2019001101A1 (zh) 路由路径分析方法及设备
CN114697202B (zh) 一种检测方法及装置
EP2854339A1 (en) Transmission monitoring method and device
CN114430355A (zh) 路径确定方法及装置、计算机存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20887758

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20887758

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 01/03/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20887758

Country of ref document: EP

Kind code of ref document: A1