WO2023050817A1 - 确定报文传输路径故障的方法以及装置 - Google Patents

确定报文传输路径故障的方法以及装置 Download PDF

Info

Publication number
WO2023050817A1
WO2023050817A1 PCT/CN2022/091516 CN2022091516W WO2023050817A1 WO 2023050817 A1 WO2023050817 A1 WO 2023050817A1 CN 2022091516 W CN2022091516 W CN 2022091516W WO 2023050817 A1 WO2023050817 A1 WO 2023050817A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
target
transmission path
node
port
Prior art date
Application number
PCT/CN2022/091516
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 WO2023050817A1 publication Critical patent/WO2023050817A1/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/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults

Definitions

  • the present application relates to the technical field of communications, and in particular to a method, device, electronic device and storage medium for determining a message transmission path failure.
  • Embodiments of the present application provide a method, device, electronic device, and storage medium for determining a packet transmission path failure, which can accurately locate a location of a failure in a network at least to a certain extent.
  • the embodiment of the present application provides a method for determining a message transmission path failure, the method including: determining the transmission path of the target message; obtaining the target identifier corresponding to the target message; according to the target identifier, Determining the statistical quantity of target packets corresponding to each node port passed by the transmission path; determining the location of the failure in the transmission path according to the node port meeting the first condition, the first condition being that the node port corresponds to The statistical number of target packets is less than the preset number threshold.
  • the embodiment of the present application provides a device for determining a message transmission path failure
  • the device includes: a path determination module, configured to determine the transmission path of the target message; a sending module, configured to send a message to the transmission path The starting node of the sending message modification request, so that the target message is modified according to the message modification request by the starting node, so that the target message carries a target identifier; the statistics module is used to modify the target message according to the The target identifier is used to determine the statistical quantity of target packets corresponding to each node port passed by the transmission path; the fault determination module is used to determine the location of the fault in the transmission path according to the node port meeting the first condition, The first condition is that the statistical number of target packets corresponding to the node port is smaller than a preset number threshold.
  • an embodiment of the present application provides an electronic device, including: a memory for storing a program; a processor for executing the program stored in the memory, and when the processor executes the program stored in the memory, The processor is configured to execute: the method for determining a message transmission path failure as provided in the first aspect above.
  • the embodiment of the present application provides a storage medium storing computer-executable instructions, and the computer-executable instructions are used to execute: the method for determining a packet transmission path failure provided in the first aspect above.
  • FIG. 1 is a schematic diagram of an application scenario of a method for determining a message transmission path failure provided in an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a method for determining a message transmission path failure provided by an embodiment of the present application
  • FIG. 3 is a schematic flowchart of step S230 in the method for determining a message transmission path failure in FIG. 2;
  • FIG. 4 is a schematic structural diagram of a physical device in the physical layer provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a device for determining a message transmission path failure provided by an embodiment of the present application
  • FIG. 6 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • the embodiment of the present application provides a method, device, electronic equipment, and storage medium for determining a message transmission path failure, which can accurately locate the specific location of the failure in the network, and determine the specific transmission link and equipment where the network failure occurs .
  • FIG. 1 is a schematic diagram of an application scenario of a method for determining a packet transmission path failure provided by an embodiment of the present application.
  • the application scenario of the method for determining a packet transmission path failure provided by the embodiment of the present application includes a virtualized network, which adopts a three-layer networking architecture, including a physical layer, a virtual layer, and an application layer.
  • the physical layer includes a router 100, an EOR (End of Row) switch 110, a TOR (Top of Rack) switch 120 and a host 130.
  • EOR End of Row
  • TOR Top of Rack
  • the virtual layer includes a virtual switch 140 and a virtual machine 150, the virtual machine 150 is deployed in the host 130, and the physical port of the host 130 and the virtual machine port of the virtual machine 150 can be managed through the virtual switch 140.
  • the application layer includes various types of network elements 160, and there are various virtual machines 150 responsible for different functions in the network elements 160.
  • a network element 160 may contain multiple virtual machines 150, different virtual machines 150 may be deployed on the same host 130, or may be deployed on different hosts 130, one host 130 may be connected to multiple TOR switches 120, one The TOR switch 120 can also link a plurality of EOR switches 110 . Therefore, there are multiple optional message transmission paths between the sending device and the receiving device. It can be understood that the above-mentioned sending device refers to a specific sending location, such as a network element, a module in a network element, a service, a microservice, or software.
  • Fig. 2 is a schematic flowchart of a method for determining a packet transmission path failure provided by an embodiment of the present application.
  • the method for determining the message transmission path failure provided by the embodiment of the present application includes the following steps:
  • Step S210 determining the transmission path of the target message.
  • the transmission path of the target message includes virtual nodes and physical nodes, wherein the virtual nodes include virtual machines, and the physical nodes include at least one of the following: host, TOR switch, EOR Switches and routers; the node ports that the transmission path passes through include virtual machine ports, host inbound ports, host outbound ports, TOR switch inbound ports, TOR switch outbound ports, EOR switch inbound ports, EOR switch outbound ports, and router inbound ports and the outgoing port of the router.
  • the transmission path of the target message from the sending device to the receiving device is different, and the nodes and node ports included in the transmission path are also different.
  • the transmission path of the target message includes node: virtual machine, and node port: virtual machine port, or the target message sent from the sending device , passing through the virtual machine and the host, reaching the TOR switch and returning to the receiving device, that is, the transmission path of the target message includes nodes: virtual machine, host and TOR switch, and node ports: virtual machine port, host inbound port, host outbound port , the inbound port of the TOR switch and the outbound port of the TOR switch.
  • the target message can also be returned to the receiving device at the EOR switch or router, which will not be repeated here.
  • determining the transmission path of the target message includes obtaining message information of the target message, and the message information includes at least one of the following: message location characteristics, message service characteristics, and message Internet interconnection Protocol (Internet Protocol, IP) feature; according to the message information, determine the transmission path of the target message.
  • message information includes at least one of the following: message location characteristics, message service characteristics, and message Internet interconnection Protocol (Internet Protocol, IP) feature; according to the message information, determine the transmission path of the target message.
  • IP Internet interconnection Protocol
  • the message location feature includes sending device, receiving device, etc. It should be noted that the above sending device refers to the specific location where the message is sent, such as a network element, a module in a network element, a service, a microservice or software etc.
  • the packet service characteristics include user, service type, and so on.
  • the packet IP features include source-destination address, source-destination port, protocol type, virtual routing forwarding (Virtual Routing Forwarding, VRF), etc.
  • determining the transmission path of the target message according to the message information may include: determining the transmission path of the target message at different sending locations according to the characteristics of the message location; or, determining the transmission path of the target message according to the message service feature, to determine the transmission path of a specific service message; or, according to the IP feature of the message, to determine the transmission path of the target message from the sending device to the receiving device; it can also be based on the location characteristics of the message and the service characteristics of the message and packet IP features to determine the transmission path of the target packet from the sending device to the receiving device.
  • transmission paths containing different information for different target messages can be determined, which will not be listed here. It should be understood that the transmission path determined here includes information about nodes and node ports on the transmission path.
  • the embodiment of the present application may further include the following steps:
  • each node in the network includes nodes in the physical layer, virtual layer and application layer in the above-mentioned virtualized three-layer network, that is to say, the optional transmission link includes the physical layer, virtual layer and the link of the application layer three-layer network.
  • message position feature position determines the virtual machine that interacts with the outside world in the message sending device, and then determine the connection between the application layer and the virtual layer .
  • the virtual machine that interacts with the outside world in the message sending device determine the host where the virtual machine is located, and then determine the connection between the virtual layer and the physical layer. In this way, links among the three-layer networking of the physical layer, the virtual layer, and the application layer can be determined.
  • FIG. 4 is a schematic structural diagram of physical devices in the physical layer provided by the embodiment of the present application.
  • router 200, EOR switch 210, TOR The switch 220 and the host 230, open the link layer discovery protocol (Link Layer Discovery Protocol, LLDP), and notify each other of their own device identification number (Chassis Identity document, Chassis ID) and device port identification number (Port Identity document, Port ID),
  • Link Layer Discovery Protocol LLDP
  • the adjacency relationship of each device can be stored as follows:
  • the router 200 stores the adjacency relationship of its adjacent EOR switch 210;
  • the EOR switch 210 stores the adjacency relationship of its adjacent TOR switch 220 and router 200;
  • the TOR switch 220 stores the adjacency relationship of its adjacent host 230 and EOR switch 210;
  • the host 230 stores the adjacency relationship of the TOR switch 220 to which it adjoins.
  • confirming the optional transmission link between the host and the TOR switch may be: obtain the Chassis ID of the peer device of the host and the Port ID of the peer port, and compare the acquired Chassis ID Compare with the Chassis IDs of all TOR switches in the physical layer. After matching, compare the obtained Port ID with the Port IDs of all ports of the matched TOR switch. If they are the same, the two ports have a link.
  • confirming the optional transmission link between the TOR switch and the EOR switch may be: obtaining the Chassis ID of the peer device of the TOR switch and the Port ID of the peer port, and comparing the acquired Compare the Chassis ID with the Chassis IDs of all EOR switches in the physical layer. After matching, compare the obtained Port ID with the Port IDs of all ports of the matched EOR switch. If they are the same, the two ports have a link Link.
  • the above steps are also applicable and will not be repeated here. Thereby, links between physical devices within the physical layer can be determined.
  • the link between the sending device and the receiving device will change, the virtual machine in the network element of the application layer can be migrated to a different host, and the link between the host, TOR switch, EOR switch and router will change Therefore, the link between the sending device and the receiving device is uncertain.
  • the message transmission path fault detection is performed again, the adjacency relationship of each node in the network will be obtained again, and the adjacency relationship of each node will be re-determined An optional transmission link in a network.
  • determining the link between physical devices in the physical layer may also be, when the instruction interface is opened between the physical devices, by obtaining the configured device configuration information and message information, to find out the outgoing interface of each physical device and the next link. One hop of information finally forms the transmission path of the message between physical devices.
  • determining the transmission path of the message according to the message information includes: determining the transmission path of the target message from optional transmission links according to the message information.
  • the optional transmission link includes all transmission paths of the physical layer, virtual layer and application layer, and the target message is sent from the sending device, which can be transmitted between the host and the TOR switch. , EOR switch or router returns to the receiving device, therefore, the actual transmission path of the target message may not completely include all nodes and node ports on the optional transmission path.
  • Step S220 acquiring a target identifier corresponding to the target packet.
  • the target identifier can be set in the data field of the target message or in the identification field of the target message.
  • Step S230 determine the statistical quantity of target packets corresponding to each node port passed by the transmission path.
  • the number of messages of the target message corresponding to the target identifier is counted.
  • the node ports that the transmission path passes through can be virtual machine ports, host inbound ports, host outbound ports, TOR switch inbound ports, TOR switch outbound ports, and EOR switch inbound ports. port, EOR switch outbound port, router inbound port, and router outbound port.
  • the node ports that the target message passes through include the virtual machine port, the host inbound port, the host outbound port, and the TOR switch inbound port.
  • the and the outgoing port of the TOR switch so determine the statistical quantity of target packets corresponding to the target identifier at the virtual machine port, the incoming port of the host, the outgoing port of the host, the incoming port of the TOR switch, and the outgoing port of the TOR switch.
  • the target identifier is set in the Differentiated Services Code Point (DSCP) field of the target message to determine the statistical quantity of the target message corresponding to each node port passed by the transmission path, as shown in FIG. 3 ,include:
  • DSCP Differentiated Services Code Point
  • Step S310 for each node port that the transmission path passes through, respectively obtain the message received by the node port;
  • Step S320 when the DSCP field in the message received by the node port is a preset field value, determine the message as the target message;
  • Step S330 counting the number of target packets received by the node port to obtain the statistical number of target packets corresponding to the node port.
  • the node ports that the transmission path of the target message passes through include virtual machine ports, host inbound ports, host outbound ports, TOR switch inbound ports, and TOR switch outbound ports.
  • the DSCP field in the received message is a preset field value, and the message is determined as the target message, and then, the number of target messages received by the above-mentioned node port is counted, and the target message corresponding to the above-mentioned node port is obtained total number.
  • DSCP uses 6 bits in the TOS identification byte of the service category in the IP header of each datagram to divide the service category and distinguish the priority of the service.
  • the DSCP value ranges from 0 to 63 . Modify the DSCP value of the message to mark the message to identify the target message. At the same time, because the DSCP itself is a part of the message header, modifying the DSCP value of the message will not increase the length of the target message or increase the length of the target message. The data information carried by the target packet will not be affected.
  • modifying the data field or other identification fields of the target message so that the target message carries the target identifier can also serve to identify the target message, which is not specifically limited in this embodiment of the present application.
  • the above steps of the method are also applicable to determine the statistical quantity of the target message corresponding to each node port passed by the transmission path, and will not be repeated here.
  • the last two bits of the DSCP field of the target packet both have a fixed value of 1.
  • the last two bits of the DSCP field are fixed at 1.
  • the last two bits refer to the 2 bits in the DSCP field other than the 6 bits used to divide the service category, specifically the last two lowest bits of the DSCP field, such as setting the DSCP field 101111B, that is, the DSCP value is 47, or set the DSCP field to 110111B, that is, the DSCP value is 55.
  • it may further include: sending a message modification request to the initial node passed by the transmission path , so that the initiating node modifies the target message according to the message modification request, so that the target message carries the target identifier.
  • the statistical quantity of target packets corresponding to each node port passed by the transmission path may be determined.
  • the starting node passed by the transmission path may be a node in the physical layer, virtual layer, and application layer of the virtualized three-layer network as described above.
  • the initiating node modifies the target message according to the message modification request, which may be to modify the data field of the target message so that the target message carries the target identifier, or to modify the target message The field is modified so that the target packet carries the target identifier, which is not specifically limited in this embodiment of the present application.
  • Step S240 determine the location of the fault in the transmission path according to the node port meeting the first condition, the first condition is that the statistical number of target packets corresponding to the node port is less than a preset number threshold.
  • the statistical quantity of target packets corresponding to the node port determines whether the corresponding statistical quantity of target packets is less than the preset quantity threshold, determine the location of the fault in the transmission path, that is, determine the occurrence Specific transmission links and equipment for network failures.
  • the above preset quantity threshold is the total number of target packets carrying target identifiers.
  • the preset quantity threshold is that the initial node that the transmission path passes through requests for modification of the target packets.
  • the total number of target packets carrying the target identifier after modifying the DSCP field of the packet that is, the total number of target packets whose DSCP is set to a specific value.
  • the target packet is sent from the sending device, arrives at the EOR switch and returns to the receiving device as an example for illustration.
  • the node ports that the transmission path of the target message passes through include a virtual machine port, a host inbound port, a host outbound port, a TOR switch inbound port, a TOR switch outbound port, an EOR switch inbound port, and an EOR switch outbound port.
  • the routine meeting determines the statistical quantity of the target packets of the above node ports, and then determines the location of the transmission failure in the transmission path, including the following situations:
  • the number of target packets carrying the target ID is 1200, that is, the preset threshold is 1200, the statistics of the target packets of the virtual machine port are 1200, and the statistics of the target packets of the inbound port of the host are 1200.
  • the statistical number of target packets of the outgoing port is 1100, and the statistical number of target packets of other node ports are all 1100, so it can be determined that the location of the fault in the transmission path is the host device in the physical layer.
  • the location of the fault in the transmission path is the link from the host to the TOR switch in the physical layer .
  • the location of the fault in the transmission path is the link from the application layer to the virtual layer.
  • the statistical quantity of the target message corresponding to each node port passed by the transmission path is determined, and according to the corresponding The relationship between the statistical quantity of target packets and the preset quantity threshold, that is, whether the corresponding target packet statistical quantity is less than the preset quantity threshold, locate the location of the fault in the transmission path, that is, determine the location of the network fault Specific transmission links and equipment. In this way, the time affected by the network failure is reduced, and the loss caused by the failure is reduced.
  • FIG. 5 is a schematic structural diagram of an apparatus 300 for determining a packet transmission path failure provided by an embodiment of the present application.
  • the device 300 for determining a message transmission path failure provided by the embodiment of the present application includes:
  • Path determination module 310 configured to determine the transmission path of the target message
  • the sending module 320 is configured to send a message modification request to the initial node in the transmission path, so that the target message is modified by the initial node according to the message modification request, so that the target message carries a target identifier;
  • a statistical module 330 configured to determine the statistical quantity of target packets corresponding to each node port passed by the transmission path according to the target identifier
  • the failure determination module 340 is configured to determine the location of the failure in the transmission path according to the node port meeting the first condition, the first condition being that the statistical number of target packets corresponding to the node port is less than a preset number threshold.
  • the transmission path of the target message is determined by the path determination module, and then the sending module sends a message modification request to the initial node in the transmission path, so that the initial node can modify the target message according to the message modification request.
  • Modify so that the target message carries the target identifier
  • the statistical module determines the target message corresponding to each node port that the transmission path passes through according to the target identifier on the modified target message Statistical quantity.
  • the fault determination module locates faults in the network according to the relationship between the statistical quantity of target packets corresponding to the node port and the preset quantity threshold, that is, whether the corresponding target packet statistical quantity is less than the preset quantity threshold. s position.
  • FIG. 6 shows an electronic device 400 provided by an embodiment of the present application. As shown in FIG. 6, the electronic device 400 includes but is not limited to:
  • Memory 420 used to store programs
  • the processor 410 is configured to execute the program stored in the memory 420.
  • the processor 410 executes the program stored in the memory 420, the processor 410 is configured to execute the above-mentioned method for determining a message transmission path failure.
  • the processor 410 and the memory 420 may be connected through a bus or in other ways.
  • the memory 420 can be used to store non-transitory software programs and non-transitory computer-executable programs, such as the method for determining message transmission path failure described in any embodiment of the present application.
  • the processor 410 executes the non-transitory software programs and instructions stored in the memory 420, so as to implement the above-mentioned method for determining a message transmission path failure.
  • the memory 420 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store and execute the above-mentioned method for determining a message transmission path failure.
  • the memory 420 may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices.
  • the memory 420 may include memories located remotely relative to the processor 410, and these remote memories may be connected to the processor 410 through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the non-transitory software programs and instructions required to implement the above-mentioned method for determining a message transmission path failure are stored in the memory 420, and when executed by one or more processors 410, the determination message described in any embodiment of the present application is executed.
  • the method for transmission path failure for example, executes the method steps S210 to S240 described in FIG. 2 and the method steps S310 to S330 described in FIG. 3 .
  • the embodiment of the present application also provides a storage medium, which stores computer-executable instructions, and the computer-executable instructions are used to execute the above-mentioned method for determining a packet transmission path failure.
  • the storage medium stores computer-executable instructions, and the computer-executable instructions are executed by one or more control processors, for example, executed by one or more processors 410 of the above-mentioned electronic device 400, so that The above-mentioned one or more processors 410 execute the method for determining a packet transmission path failure provided by any embodiment of the present application, for example, execute the method steps S210 to S240 described in FIG. 2 and the method steps S310 to S330 described in FIG. 3 .
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware, or in the form of hardware plus software functional units.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer.
  • communication media typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种确定报文传输路径故障的方法以及装置，所述方法包括确定目标报文的传输路径(S210)；获取所述目标报文对应的目标标识(S220)；根据所述目标标识，确定所述传输路径经过的每个节点端口分别对应的目标报文统计数量(S230)；根据符合第一条件的节点端口确定所述传输路径中发生故障的位置，所述第一条件为所述节点端口对应的目标报文统计数量小于预设的数量阈值(S240)。

Description

确定报文传输路径故障的方法以及装置
相关申请的交叉引用
本申请基于申请号为202111162061.4、申请日为2021年9月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及通信技术领域，特别是涉及一种确定报文传输路径故障的方法、装置、电子设备以及存储介质。
背景技术
在本领域一些情形中，判断网络故障、丢包等情况，都是端到端的，比如只能判断出源节点到宿节点之间是否出现网络故障、丢包等情况，无法快速、准确的定位网络中发生故障的位置，延长了受网络故障影响的时间，对运营商产生不可估计的损失。
发明内容
本申请实施例提供了一种确定报文传输路径故障的方法、装置、电子设备以及存储介质，能够至少在一定程度上实现准确定位网络中发生故障的位置。
第一方面，本申请实施例提供一种确定报文传输路径故障的方法，所述方法包括：确定目标报文的传输路径；获取所述目标报文对应的目标标识；根据所述目标标识，确定所述传输路径经过的每个节点端口分别对应的目标报文统计数量；根据符合第一条件的节点端口确定所述传输路径中发生故障的位置，所述第一条件为所述节点端口对应的目标报文统计数量小于预设的数量阈值。
第二方面，本申请实施例提供一种确定报文传输路径故障的装置，所述装置包括：路径确定模块，用于确定目标报文的传输路径；发送模块，用于向所述传输路径中的起始节点发送报文修改请求，以通过所述起始节点根据所述报文修改请求对所述目标报文进行修改，使得所述目标报文携带有目标标识；统计模块，用于根据所述目标标识，确定所述传输路径经过的每个节点端口分别对应的目标报文统计数量；故障确定模块，用于根据符合第一条件的节点端口确定所述传输路径中发生故障的位置，所述第一条件为所述节点端口对应的目标报文统计数量小于预设的数量阈值。
第三方面，本申请实施例提供一种电子设备，包括：存储器，用于存储程序；处理器，用于执行所述存储器存储的程序，当所述处理器执行所述存储器存储的程序时，所述处理器用于执行：如上第一方面提供的确定报文传输路径故障的方法。
第四方面，本申请实施例提供一种存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行：如上第一方面提供的确定报文传输路径故障的方法。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1是本申请实施例提供的确定报文传输路径故障的方法的应用场景示意图；
图2是本申请实施例提供的一种确定报文传输路径故障的方法的流程示意图；
图3是图2的确定报文传输路径故障的方法中步骤S230的具体流程示意图；
图4是本申请实施例提供的物理层中物理设备的结构示意图；
图5是本申请实施例提供的一种确定报文传输路径故障的装置的结构示意图；
图6是本申请实施例提供的一种电子设备的结构示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
此外，下面所描述的本申请各个实施方式中所涉及到的技术特征只要彼此之间未构成冲突就可以相互组合。
随着虚拟化技术的发展，产生了三层组网：物理层、虚层和应用层。虚拟化三层组网虽然很好的解决了运营商对网络的特殊要求，但其业务故障的定位和恢复相较于传统网络更复杂，纯人工的方式已经满足不了故障快速定位和恢复的需求，其主要原因是物理层、虚层和应用层分层构建，虚拟化网络功能共享资源池，跨层诊断和分析异常困难。
在本领域一些情形中，判断网络故障、丢包等情况，都是端到端的，比如只能判断出源节点到宿节点之间是否出现网络故障、丢包等情况，无法快速的判断网络故障发生在哪一层、哪一段链路、哪一个设备，延长了受网络故障影响的时间，对运营商产生不可估计的损失。
基于此，本申请实施例提供了一种确定报文传输路径故障的方法、装置、电子设备以及存储介质，能够准确定位网络中发生故障的具体位置，确定发生网络故障的具体传输链路和设备。
为了方便本领域技术人员理解本申请实施例，下面先对本申请实施例提供的虚拟化三层组网的架构进行说明。
图1是本申请实施例提供的确定报文传输路径故障的方法的应用场景示意图。参见图1，本申请实施例提供的确定报文传输路径故障的方法的应用场景包括虚拟化网络，该虚拟化网络采用三层组网架构，包括有物理层、虚拟层和应用层。
在上述虚拟化网络中，物理层包括有路由器100、EOR(End of Row)交换机110、TOR(Top of Rack)交换机120和主机130。
在上述虚拟化网络中，虚拟层包括有虚拟交换机140和虚拟机150，虚拟机150部署在主机130内，通过虚拟交换机140能够对主机130的物理端口和虚拟机150的虚拟机端口进行管理。
在上述虚拟化网络中，应用层包括有各种类型的网元160，网元160内有各种负责不同功能的虚拟机150。
一个网元160内可以包含有多个虚拟机150，不同的虚拟机150可以部署在同一个主机130上，也可以部署在不用的主机130上，一个主机130可以链接多个TOR交换机120，一个TOR交换机120也可以链接多个EOR交换机110。因此，发送设备和接收设备之间有多条可选的报文传输路径。可以理解的是，上述发送设备指的是具体发送的位置，比如网元、网元内模块、服务、微服务或软件等。
图2是本申请实施例提供的一种确定报文传输路径故障的方法的流程示意图。参见图2，本申请实施例提供的确定报文传输路径故障的方法包括以下步骤：
步骤S210，确定目标报文的传输路径。
在一些实施例中，基于上述虚拟化三层组网，目标报文的传输路径包括虚拟节点和物理节点，其中，虚拟节点包括虚拟机，物理节点包括以下至少之一：主机、TOR交换机、EOR交换机和路由器；传输路径经过的节点端口包括虚拟机端口、主机入向端口、主机出向端口、TOR交换机入向端口、TOR交换机出向端口、EOR交换机入向端口、EOR交换机出向端口、路由器入向端口和路由器出向端口。
可以理解的是，基于上述虚拟化三层组网，目标报文从发送设备到接收设备之间的传输路径是不同的，传输路径所包括的节点以及节点端口也是不同的，比如，从发送设备发出的目标报文，经过虚拟机，到达主机就返回接收设备，也就是目标报文的传输路径包括节点：虚拟机，以及节点端口：虚拟机端口，又或者，从发送设备发出的目标报文，经过虚拟机和主机，到达TOR交换机就返回接收设备，也就是目标报文的传输路径包括节点：虚拟机、主机和TOR交换机，以及节点端口：虚拟机端口、主机入向端口、主机出向端口、TOR交换机入向端口和TOR交换机出向端口，此外，目标报文还可以于EOR交换机或路由器处返回接收设备，在此不再赘述。
在一些实施例中，确定目标报文的传输路径，包括获取所述目标报文的报文信息，报文信息包括以下至少之一：报文位置特征、报文业务特征和报文网际互连协议(Internet Protocol，IP)特征；根据报文信息，确定目标报文的传输路径。
在一些示例中，报文位置特征包括，发送设备、接收设备等，需要说明的是，上述发送设备指的是具体发送报文的位置，比如网元、网元内模块、服务、微服务或软件等。
在一些示例中，报文业务特征包括，用户、业务类型等。
在一些示例中，报文IP特征包括，源目的地址、源目的端口、协议类型、虚拟路由转发(Virtual Routing Forwarding，VRF)等。
需要说明的是，在上述实施例中，根据报文信息，确定目标报文的传输路径可以包括：根据报文位置特征，确定不同发送位置的目标报文的传输路径；或者，根据报文业务特征，确定特定的业务报文的传输路径；又或者，根据报文IP特征，确定目标报文从发送设备到接收设备之间的传输路径；还可以是根据报文位置特征、报文业务特征和报文IP特征中的任意组合来确定目标报文从发送设备到接收设备之间的传输路径。根据不同的报文信息，可以确 定不同目标报文的包含不同信息的传输路径，在此不一一列举。应能理解，这里确定的传输路径包含了传输路径上的节点以及节点端口信息。
本申请实施例在所述根据所述报文信息，确定所述目标报文的传输路径之前，还可以包括以下步骤：
获取网络中每个节点的邻接关系，并根据每个节点的邻接关系确定网络中的可选传输链路。
可以理解的是，网络中的每个节点包括有如上述虚拟化三层组网中物理层、虚拟层和应用层中的节点，也就是说，可选传输链路是包括了物理层、虚拟层和应用层三层组网的链路。
在一个具体的实施例中，根据报文位置特征位置、报文业务信息和报文IP特征，确定报文发送设备内和外界进行交互的虚拟机，继而确定应用层和虚拟层之间的联系。根据报文发送设备内和外界进行交互的虚拟机，确定虚拟机所在的主机，便可以确定虚层和物理层之间的联系。由此，可以确定物理层、虚拟层和应用层三层组网之间的链路。
在另一个具体的实施例中，基于上述虚拟化三层组网，参考图4，图4是本申请实施例提供的物理层中物理设备的结构示意图，图中路由器200、EOR交换机210、TOR交换机220和主机230、开启链路层发现协议(Link Layer Discovery Protocol，LLDP)，相互通知自身的设备识别号(Chassis Identity document，Chassis ID)和设备端口识别号(Port Identity document，Port ID)，各设备的邻接关系可以存储如下：
路由器200存储与其邻接的EOR交换机210的邻接关系；
EOR交换机210存储与其邻接的TOR交换机220和路由器200的邻接关系；
TOR交换机220存储与其邻接的主机230和EOR交换机210的邻接关系；
主机230存储与其邻接的TOR交换机220的邻接关系。
需要说明的是，在上述实施例中，确认主机与TOR交换机之间的可选传输链路可以是：获取主机的对端设备的Chassis ID以及对端端口的Port ID，对比获取到的Chassis ID与物理层中所有TOR交换机的Chassis ID进行比较，匹配上以后，再对比获取到的Port ID与匹配上的TOR交换机的所有端口的Port ID，若相同，即这两个端口有链路链接。
需要说明的是，在上述实施例中，确认TOR交换机和EOR交换机之间的可选传输链路可以是：获取TOR交换机的对端设备的Chassis ID以及对端端口的Port ID，对比获取到的Chassis ID与物理层中所有EOR交换机的Chassis ID进行比较，匹配上以后，再对比获取到的Port ID与匹配上的EOR交换机的所有端口的Port ID，若相同，即这两个端口有链路链接。此外，确认EOR交换机和路由器之间的可选传输链路，同样适用以上步骤，在此不再赘述。由此，可以确定物理层内的物理设备之间的链路。
可以理解的是，发送设备到接收设备之间的链路会发生变化，应用层的网元内的虚拟机可以迁移到不同主机上，主机、TOR交换机、EOR交换机和路由器之间的链接是变化的，因此发送设备和接收设备之间的链路是不确定的，当再次进行报文传输路径故障检测时，将再次获取网络中每个节点的邻接关系，根据每个节点的邻接关系重新确定网络中的可选传输链路。
应了解，确定物理层内的物理设备之间的链路还可以是，当物理设备间开放了指令接口，通过获取配置好的设备配置信息和报文信息，查找各物理设备的出接口以及下一跳信息，最终形成报文在物理设备之间的传输路径。
本申请实施例中根据报文信息，确定报文的传输路径包括：根据报文信息，从可选传输链路中确定目标报文的传输路径。
需要说明的是，基于上述虚拟化三层组网，可选传输链路是包含了物理层、虚拟层和应用层的所有传输路径，而目标报文从发送设备发出，可以于主机、TOR交换机、EOR交换机或路由器返回接收设备，因此，目标报文的实际传输路径可以不完全包括可选传输路径上的所有节点以及节点端口。
步骤S220，获取所述目标报文对应的目标标识。需要说明的是，目标标识可以设置在目标报文的数据字段中，也可以设置在目标报文的标识字段中。
步骤S230，根据目标标识，确定传输路径经过的每个节点端口分别对应的目标报文统计数量。
根据设置在目标报文中的目标标识，在传输路径经过的每个节点端口，统计对应目标标识的目标报文的报文数量。
可以理解的是，基于上述虚拟化三层组网，传输路径经过的节点端口可以是虚拟机端口、主机入向端口、主机出向端口、TOR交换机入向端口、TOR交换机出向端口、EOR交换机入向端口、EOR交换机出向端口、路由器入向端口和路由器出向端口。比如，当目标报文从发送设备发出，到达TOR交换机便返回接收设备，该目标报文的传输路径经过的节点端口就有虚拟机端口、主机入向端口、主机出向端口、TOR交换机入向端口和TOR交换机出向端口，于是，确定在虚拟机端口、主机入向端口、主机出向端口、TOR交换机入向端口和TOR交换机出向端口处的对应目标标识的目标报文统计数量。
在一些实施例中，目标标识设置在目标报文的差分服务代码点(Differentiated Services Code Point，DSCP)字段中，确定传输路径经过的每个节点端口分别对应的目标报文统计数量，参照图3，包括：
步骤S310，对于传输路径经过的每个节点端口，分别获取节点端口接收到的报文；
步骤S320，当节点端口接收到的报文中的DSCP字段为预设的字段值，将报文确定为目标报文；
步骤S330，统计节点端口接收到的目标报文的数量，得到节点端口对应的目标报文统计数量。
基于上述虚拟化三层组网，以目标报文从发送设备发出，到达TOR交换机便返回接收设备为例进行说明。该目标报文的传输路径经过的节点端口有虚拟机端口、主机入向端口、主机出向端口、TOR交换机入向端口和TOR交换机出向端口，于是，分别获取上述节点端口接收到的报文，当接收到的报文中的DSCP字段为预设的字段值，将该报文确定为目标报文，接着，统计上述节点端口接收到的目标报文的数量，得到上述节点端口对应的目标报文统计数量。
需要说明的是，DSCP在每个数据报IP头部的服务类别TOS标识字节中，使用其中6个比特位，来划分服务类别，区分服务的优先级，其中DSCP值的范围为0至63。修改报文的DSCP值对报文进行标记，起到识别目标报文的作用，同时，因为DSCP本身就是报文头部的一部分，修改报文的DSCP值即不会增加目标报文的长度也不会影响目标报文携带的数据信息。
应了解，修改目标报文的数据字段或其他标识字段，使得目标报文携带有目标标识，同样可以起到识别目标报文的作用，本申请实施例不对此进行具体限定。当目标标识设置在目 标报文的数据字段或其他标识字段中，确定传输路径经过的每个节点端口分别对应的目标报文统计数量同样适用以上方法步骤，此处不再赘述。
在一些实施例中，目标报文的DSCP字段的最后两个比特位均为固定值1。
修改目标报文的DSCP值对报文进行标记，从而达到识别目标报文的目的。为了更准确地识别目标报文，避免与常用的DSCP值冲突，在修改目标报文时，DSCP字段的最后两个比特位均为固定值1。
需要说明的是，最后两个比特位指DSCP字段中除用于划分服务类别的6个比特位之外的2个比特位，具体为DSCP字段后两个最低位的比特位，比如设置DSCP字段为101111B，也就是DSCP值为47，又或者设置DSCP字段为110111B，也就是DSCP值为55。
本申请实施例在确定报文的传输路径之后，在确定传输路径经过的每个节点端口分别对应的目标报文统计数量之前，还可以包括：向传输路径经过的起始节点发送报文修改请求，以通过起始节点根据报文修改请求对目标报文进行修改，使得目标报文携带有目标标识。
在确定报文的传输路径之后，向传输路径经过的起始节点发送报文修改请求，以通过起始节点根据报文修改请求对目标报文进行修改，使得目标报文携带有目标标识，继而可以确定传输路径经过的每个节点端口分别对应的目标报文统计数量。
可以理解的是，传输路径经过的起始节点可以是如上述虚拟化三层组网的物理层、虚拟层和应用层中的节点。在一些示例中，起始节点根据报文修改请求对目标报文进行修改，可以是对目标报文的数据字段进行修改，使得目标报文携带有目标标识，又或者，对目标报文的标识字段进行修改，使得目标报文携带有目标标识，本申请实施例不对此进行具体限定。
步骤S240，根据符合第一条件的节点端口确定传输路径中发生故障的位置，第一条件为节点端口对应的目标报文统计数量小于预设的数量阈值。
根据节点端口对应的目标报文统计数量和预设的数量阈值之间的关系，即对应的目标报文统计数量是否小于预设的数量阈值，确定传输路径中发生故障的位置，也就是确定发生网络故障的具体传输链路和设备。
可以理解的是，上述预设的数量阈值是携带目标标识的目标报文总数，在一个具体实施例中，预设的数量阈值是传输路径经过的起始节点根据报文修改请求，对目标报文的DSCP字段进行修改并发出的携带有目标标识的目标报文总数，也就是DSCP被设置成特定值的目标报文总数。
基于上述虚拟化三层组网，以目标报文从发送设备发出，到达EOR交换机便返回接收设备为例进行说明。该目标报文的传输路径经过的节点端口有虚拟机端口、主机入向端口、主机出向端口、TOR交换机入向端口、TOR交换机出向端口、EOR交换机入向端口和EOR交换机出向端口，本申请实施例会确定上述节点端口的目标报文统计数量，之后确定传输路径中发送故障的位置，包括有如下情况：
若携带有目标标识的目标报文的数量为1200，也就是预设的数量阈值为1200，虚拟机端口的目标报文统计数量为1200，主机入向端口的目标报文统计数量为1200，主机出向端口的目标报文统计数量为1100，其他节点端口的目标报文统计数量都为1100，那么可以确定传输路径中发生故障的位置是物理层中的主机设备。
又比如，若携带有目标标识的目标报文的数量为1400，也就是预设的数量阈值为1400，虚拟机端口的目标报文统计数量为1400，主机出向端口的目标报文统计数量为1400，TOR交 换机入向端口的目标报文统计数量为1300，其他节点端口的目标报文统计数量都为1300，那么可以确定传输路径中发生故障的位置是物理层中主机到TOR交换机的链路上。
再比如，若携带有目标标识的目标报文的数量为1600，也就是预设的数量阈值为1600，虚拟机端口的目标报文统计数量为1500，其他节点端口的目标报文统计数量都为1500，那么可以确定传输路径中发生故障的位置是应用层到虚层的链路上。
当传输路径中发生故障是在虚拟化三层组网的其他位置上，同样适用以上方法步骤，此处不再赘述。
需说明的是，在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述或记载的部分，可以参见其它实施例的相关描述。
本申请实施例，通过确定目标报文的传输路径和获取目标报文对应的目标标识，根据该目标标识，确定传输路径经过的每个节点端口分别对应的目标报文统计数量，根据节点端口对应的目标报文统计数量和预设的数量阈值之间的关系，即对应的目标报文统计数量是否小于预设的数量阈值，定位出传输路径中发生故障的位置，也就是确定发生网络故障的具体传输链路和设备。如此，减小网络故障影响的时间，降低故障造成的损失。
图5是本申请实施例提供的一种确定报文传输路径故障的装置300的结构示意图。参见图5，本申请实施例提供的确定报文传输路径故障的装置300包括：
路径确定模块310，用于确定目标报文的传输路径；
发送模块320，用于向传输路径中的起始节点发送报文修改请求，以通过起始节点根据报文修改请求对目标报文进行修改，使得目标报文携带有目标标识；
统计模块330，用于根据目标标识，确定传输路径经过的每个节点端口分别对应的目标报文统计数量；
故障确定模块340，用于根据符合第一条件的节点端口确定传输路径中发生故障的位置，第一条件为节点端口对应的目标报文统计数量小于预设的数量阈值。
需要说明的是，上述模块之间的信息交互、执行过程等内容，由于与本申请方法实施例基于同一构思，其具体功能及带来的技术效果，具体可参见方法实施例部分，此处不再赘述。
本申请实施例，通过路径确定模块确定目标报文的传输路径，之后由发送模块向传输路径中的起始节点发送报文修改请求，以通过起始节点根据报文修改请求对目标报文进行修改，使得目标报文携带有目标标识，统计模块在起始节点修改目标报文后，根据修改后的目标报文上的目标标识，确定传输路径经过的每个节点端口分别对应的目标报文统计数量，最后，故障确定模块根据节点端口对应的目标报文统计数量和预设的数量阈值之间的关系，即对应的目标报文统计数量是否小于预设的数量阈值，定位网络中发生故障的位置。
图6示出了本申请实施例提供的一种电子设备400。如图6所示，该电子设备400包括但不限于：
存储器420，用于存储程序；
处理器410，用于执行存储器420存储的程序，当处理器410执行存储器420存储的程序时，处理器410用于执行上述的确定报文传输路径故障的方法。
处理器410和存储器420可以通过总线或者其他方式连接。
存储器420作为一种非暂态计算机可读存储介质，可用于存储非暂态软件程序以及非暂态性计算机可执行程序，如本申请任意实施例描述的确定报文传输路径故障的方法。处理器 410通过运行存储在存储器420中的非暂态软件程序以及指令，从而实现上述的确定报文传输路径故障的方法。
存储器420可以包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需要的应用程序；存储数据区可存储执行上述的确定报文传输路径故障的方法。此外，存储器420可以包括高速随机存取存储器，还可以包括非暂态存储器，比如至少一个磁盘存储器件、闪存器件、或其他非暂态固态存储器件。在一些实施方式中，存储器420可包括相对于处理器410远程设置的存储器，这些远程存储器可以通过网络连接至该处理器410。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
实现上述的确定报文传输路径故障的方法所需的非暂态软件程序以及指令存储在存储器420中，当被一个或者多个处理器410执行时，执行本申请任意实施例描述的确定报文传输路径故障的方法，例如，执行图2中描述的方法步骤S210至S240和图3中描述的方法步骤S310至S330。
本申请实施例还提供了一种存储介质，存储有计算机可执行指令，计算机可执行指令用于执行上述的确定报文传输路径故障的方法。
在一实施例中，该存储介质存储有计算机可执行指令，该计算机可执行指令被一个或多个控制处理器执行，比如，被上述电子设备400的一个或多个处理器410执行，可使得上述一个或多个处理器410执行本申请任意实施例提供的确定报文传输路径故障的方法，例如，执行图2中描述的方法步骤S210至S240和图3中描述的方法步骤S310至S330。
以上所描述的实施例仅仅是示意性的，其中作为分离部件说明的单元可以是或者也可以不是物理上分开的，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包括计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上是对本申请的较佳实施进行了具体说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不违背本申请方案的。共享条件下还可作出种种等同的变形或替换，这些等同的变形或替换均包括在本申请权利要求所限定的范围内。

Claims (10)

  1. 一种确定报文传输路径故障的方法，包括：
    确定目标报文的传输路径；
    获取所述目标报文对应的目标标识；
    根据所述目标标识，确定所述传输路径经过的每个节点端口分别对应的目标报文统计数量；
    根据符合第一条件的节点端口确定所述传输路径中发生故障的位置，所述第一条件为所述节点端口对应的目标报文统计数量小于预设的数量阈值。
  2. 根据权利要求1所述的方法，其中，所述目标标识设置在所述目标报文的DSCP字段中；
    所述确定所述传输路径经过的每个节点端口分别对应的目标报文统计数量，包括：
    对于所述传输路径经过的每个节点端口，分别获取所述节点端口接收到的报文；
    当所述节点端口接收到的所述报文中的DSCP字段为预设的字段值，将所述报文确定为目标报文；
    统计所述节点端口接收到的目标报文的数量，得到所述节点端口对应的目标报文统计数量。
  3. 根据权利要求2所述的方法，其中，所述目标报文的DSCP字段的最后两个比特位均为固定值1。
  4. 根据权利要求1所述的方法，其中，所述确定目标报文的传输路径，包括：
    获取所述目标报文的报文信息，所述报文信息包括以下至少之一：报文位置特征、报文业务特征和报文I P特征；
    根据所述报文信息，确定所述目标报文的传输路径。
  5. 根据权利要求4所述的方法，其中，在所述根据所述报文信息，确定所述目标报文的传输路径之前，所述方法还包括：
    获取网络中每个节点的邻接关系，并根据每个节点的邻接关系确定所述网络中的可选传输链路；
    所述根据所述报文信息，确定所述报文的传输路径，包括：
    根据所述报文信息，从所述可选传输链路中确定所述目标报文的传输路径。
  6. 根据权利要求1所述的方法，其中，所述传输路径包括虚拟节点和物理节点，其中，所述虚拟节点包括虚拟机，所述物理节点包括以下至少之一：主机、TOR交换机、EOR交换机和路由器；
    所述传输路径经过的节点端口包括虚拟机端口、主机入向端口、主机出向端口、TOR交换机入向端口、TOR交换机出向端口、EOR交换机入向端口、EOR交换机出向端口、路由器入向端口和路由器出向端口。
  7. 根据权利要求1所述的方法，其中，在所述确定报文的传输路径之后，在所述确定所述传输路径经过的每个节点端口分别对应的目标报文统计数量之前，所述方法还包括：
    向所述传输路径经过的起始节点发送报文修改请求，以通过所述起始节点根据所述报文修改请求对所述目标报文进行修改，使得所述目标报文携带有目标标识。
  8. 一种确定报文传输路径故障的装置，包括：
    路径确定模块，用于确定目标报文的传输路径；
    发送模块，用于向所述传输路径中的起始节点发送报文修改请求，以通过所述起始节点根据所述报文修改请求对所述目标报文进行修改，使得所述目标报文携带有目标标识；
    统计模块，用于根据所述目标标识，确定所述传输路径经过的每个节点端口分别对应的目标报文统计数量；
    故障确定模块，用于根据符合第一条件的节点端口确定所述传输路径中发生故障的位置，所述第一条件为所述节点端口对应的目标报文统计数量小于预设的数量阈值。
  9. 一种电子设备，包括：
    存储器，用于存储程序；
    处理器，用于执行所述存储器存储的程序，当所述处理器执行所述存储器存储的程序时，所述处理器用于执行：如权利要求1至7中任一项所述的方法。
  10. 一种存储介质，存储有计算机可执行指令，其中，所述计算机可执行指令用于执行：如权利要求1至7中任一项所述的方法。
PCT/CN2022/091516 2021-09-30 2022-05-07 确定报文传输路径故障的方法以及装置 WO2023050817A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111162061.4 2021-09-30
CN202111162061.4A CN115913910A (zh) 2021-09-30 2021-09-30 确定报文传输路径故障的方法以及装置

Publications (1)

Publication Number Publication Date
WO2023050817A1 true WO2023050817A1 (zh) 2023-04-06

Family

ID=85729496

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/091516 WO2023050817A1 (zh) 2021-09-30 2022-05-07 确定报文传输路径故障的方法以及装置

Country Status (2)

Country Link
CN (1) CN115913910A (zh)
WO (1) WO2023050817A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070014232A1 (en) * 2005-06-13 2007-01-18 Fujitsu Limited Apparatus and method for detecting network failure
CN101848474A (zh) * 2010-05-07 2010-09-29 华为技术有限公司 通讯链路监控方法及装置
CN105743711A (zh) * 2016-04-13 2016-07-06 华为技术有限公司 一种网络路径的故障检测方法、装置及网络设备
CN106301821A (zh) * 2015-05-15 2017-01-04 中兴通讯股份有限公司 一种隧道丢包检测方法、装置及网络通信设备
CN108400900A (zh) * 2017-02-06 2018-08-14 中兴通讯股份有限公司 报文检测、配置、转发、统计方法及设备、控制器和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070014232A1 (en) * 2005-06-13 2007-01-18 Fujitsu Limited Apparatus and method for detecting network failure
CN101848474A (zh) * 2010-05-07 2010-09-29 华为技术有限公司 通讯链路监控方法及装置
CN106301821A (zh) * 2015-05-15 2017-01-04 中兴通讯股份有限公司 一种隧道丢包检测方法、装置及网络通信设备
CN105743711A (zh) * 2016-04-13 2016-07-06 华为技术有限公司 一种网络路径的故障检测方法、装置及网络设备
CN108400900A (zh) * 2017-02-06 2018-08-14 中兴通讯股份有限公司 报文检测、配置、转发、统计方法及设备、控制器和系统

Also Published As

Publication number Publication date
CN115913910A (zh) 2023-04-04

Similar Documents

Publication Publication Date Title
EP3808040B1 (en) Apparatus and method to trace packets in a packet processing pipeline of a software defined networking switch
CN108702326B (zh) 检测sdn控制平面循环的方法、设备和非暂时性机器可读介质
EP3665866B1 (en) Scalable network path tracing
CN108353006B (zh) 用于测试和剖析网络服务功能的非侵入式方法
CN109076018B (zh) 利用is-is协议实现分段路由网络中网元的方法和设备
US9699064B2 (en) Method and an apparatus for network state re-construction in software defined networking
US9479409B2 (en) Passive reachability measurement for inline service chaining
US9742657B2 (en) Method and system for resynchronization of forwarding states in a network forwarding device
US8374164B2 (en) Detection of specific BFD path failures
US10148573B2 (en) Packet processing method, node, and system
US20210144091A1 (en) Method and system for tracing packets in software defined networks
KR102066978B1 (ko) 차별화된 서비스 코드 포인트(dscp) 및 명시적 혼잡 통지(ecn)를 모니터링하기 위한 데이터 플레인을 위한 방법 및 장치
WO2016027220A1 (en) Forwarding packet fragments using l4-l7 headers without reassembly in a software-defined networking (sdn) system
US12095660B2 (en) Method for multi-segment flow specifications
CN108604997B (zh) 用于对差异化服务编码点(dscp)和显式拥塞通知(ecn)的监视进行配置的控制平面的方法和设备
EP3586482B1 (en) Mechanism to detect data plane loops in an openflow network
US9973578B2 (en) Real time caching efficient check in a content centric networking (CCN)
WO2018150223A1 (en) A method and system for identification of traffic flows causing network congestion in centralized control plane networks
CN111614505B (zh) 报文处理的方法和网关设备
EP2466796A1 (en) User access method, system and access server, access device
WO2023050817A1 (zh) 确定报文传输路径故障的方法以及装置
WO2023011200A1 (zh) 信息验证方法及装置、存储介质和电子装置
WO2023236544A1 (zh) 切片信息的验证方法及装置
WO2023231438A1 (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: 22874215

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: 22874215

Country of ref document: EP

Kind code of ref document: A1