WO2022078338A1 - 路径确定方法及装置、计算机存储介质 - Google Patents

路径确定方法及装置、计算机存储介质 Download PDF

Info

Publication number
WO2022078338A1
WO2022078338A1 PCT/CN2021/123326 CN2021123326W WO2022078338A1 WO 2022078338 A1 WO2022078338 A1 WO 2022078338A1 CN 2021123326 W CN2021123326 W CN 2021123326W WO 2022078338 A1 WO2022078338 A1 WO 2022078338A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
source
destination
network entity
target
Prior art date
Application number
PCT/CN2021/123326
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 华为技术有限公司
Priority to EP21879382.6A priority Critical patent/EP4216505A4/en
Publication of WO2022078338A1 publication Critical patent/WO2022078338A1/zh
Priority to US18/300,605 priority patent/US20230254244A1/en

Links

Images

Classifications

    • 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/44—Distributed routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/36—Creation of semantic tools, e.g. ontology or thesauri
    • G06F16/367—Ontology
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • 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
    • 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
    • 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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • 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/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L2012/4629—LAN interconnection over a backbone network, e.g. Internet, Frame Relay using multilayer switching, e.g. layer 3 switching
    • 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/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • 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

  • the present application relates to the field of network technologies, and in particular, to a method and device for determining a path, and a computer storage medium.
  • In-situ flow information telemetry is currently a common method used to determine the transmission path of services in the network.
  • the iFIT solution restores the real transmission path of services in the network by coloring the headers of service packets, and then performing packet-by-packet and hop-by-hop detection.
  • the present application provides a path determination method and device, and a computer storage medium, which can solve the problem of high application limitations of the current business path determination.
  • a path determination method includes: the analyzing device firstly determines the source network entity and the destination network entity on the knowledge graph of the target network.
  • the knowledge graph includes multiple knowledge graph triples, and each knowledge graph triple includes two network entities and a relationship between the two network entities.
  • the types of network entities are devices, interfaces, protocols or services. Then, the analysis device determines the transmission path from the source network entity to the destination network entity on the knowledge graph.
  • the knowledge graph of the network is composed of knowledge graph triples, other network entities that have a relationship with the network entity can be found through one network entity. Therefore, after obtaining the source network entity and the destination network entity on the knowledge graph, The transmission path from the source network entity to the destination network entity may be determined according to the relationship between the network entities. There is no need to rely on service packet transmission scenarios, and the path determination is more flexible. In addition, in this application, all transmission paths from the source network entity to the destination network entity can be found by searching the knowledge graph, which can be applied to more scenarios.
  • the network entities on the transmission path include physical entities and logical entities.
  • Physical entities include physical devices and/or physical interfaces.
  • Logical entities include one or more of logical devices, logical interfaces, protocols or services.
  • the currently determined transmission paths usually only include hardware such as physical devices and physical interfaces, while the transmission paths determined in this application include not only physical entities such as physical devices and/or physical interfaces, but also logical devices, logical interfaces, protocols and/or services.
  • the transmission path can reflect the protocols and services used for communication between the source device and the destination device.
  • the transmission path contains more information, which is convenient for later analysis of the network.
  • the implementation process of the analyzing device determining the source network entity on the knowledge graph of the target network includes: the analyzing device determining the source end device and the destination device accessing the target network.
  • the analyzing device determines the source network entity according to the source device, and determines the destination network entity according to the destination device.
  • the transmission path from the source network entity to the destination network entity is also the transmission path from the source device to the destination device.
  • the transmission path does not need to determine the transmission path between two devices depending on the service packet transmission scenario, and the flexibility of determining the path is high.
  • an implementation process for the analysis device to determine the source network entity according to the source device includes: the analysis device determines the source network entity according to access information of the source device, where the access information of the source device includes the identity of the source device. .
  • the source network entity is the source end device, or the source network entity is the first interface of the first network device in the target network.
  • the first interface of the first network device is used to connect the source device to the target network.
  • an implementation process for the analyzing device to determine the destination network entity according to the destination device includes: the analyzing device determines the destination network entity according to access information of the destination device, where the access information of the destination device includes the identifier of the destination device.
  • the destination network entity is the destination device, or the destination network entity is the second interface of the second network device in the target network.
  • the second interface of the second network device is used to connect the destination device to the target network.
  • the implementation process of the analyzing device determining the destination network entity according to the destination device includes: the analyzing device obtains the target VLAN corresponding to the DHCP service of the source device.
  • the analyzing device determines that the target network entity is the Layer 3 virtual interface corresponding to the target Layer 2 forwarding instance on the core network device in the target network.
  • the target Layer 2 forwarding instance is any Layer 2 forwarding instance except the VLAN instance.
  • the analysis device determines that the target network entity is the VLAN interface corresponding to the target VLAN on the core network device in the target network.
  • the source device is a wireless device.
  • the implementation process of the analysis device obtaining the target VLAN corresponding to the DHCP service of the source device includes: the analysis device according to the identification of the access point associated with the source device, the identification of the radio used by the source device, and the access point associated with the source device.
  • One or more of the service set identifiers of the point determine the service VLAN corresponding to the source device, and use the service VLAN corresponding to the source device as the target VLAN.
  • the implementation process of the analysis device determining the transmission path from the source network entity to the destination network entity on the knowledge graph includes: the analysis device determines the source network entity to the destination based on the knowledge graph according to the network passed by the source end device to the destination device.
  • the intermediate network entity passed by the network entity, and the network passed from the source device to the destination device includes the underlying network.
  • the analyzing device determines a transmission path according to the intermediate network entities that the source network entity passes through to the destination network entity, and the transmission path includes the source network entity, the destination network entity and the intermediate network entity.
  • the network passing from the source device to the destination device further includes an upper-layer network, and the upper-layer network is constructed on the lower layer network.
  • the upper layer network includes overlay networks and/or CAPWAP networks.
  • the access manner of the source device accessing the target network is wired access.
  • the analysis device determines that the source device and the destination device pass through the overlay network.
  • the target Layer 2 forwarding instance is any Layer 2 forwarding instance except the VLAN instance.
  • the analysis device determines that the transmission path from the source device to the destination device includes the underlying network entity and the overlay network entity. If the overlay network runs the VXLAN protocol, the analysis device determines that the packets between the source device and the destination device are forwarded through a VXLAN tunnel. When the source device and the destination device do not pass through the overlay network, the analysis device determines that the transmission path from the source device to the destination device only includes the underlying network entities.
  • the access manner of the source device accessing the target network is wireless access.
  • the analysis device determines that the source device and the destination device pass through the CAPWAP network.
  • the packet type between the source device and the destination device is a service packet
  • the service packet is forwarded directly, and the service VLAN corresponding to the service packet is bound to the target Layer 2 forwarding instance, and the analysis device determines The source device to the destination device goes through the overlay network.
  • the target Layer 2 forwarding instance is any Layer 2 forwarding instance except the VLAN instance.
  • the analysis device determines that the source device and the destination device pass through the CAPWAP network.
  • the analysis device determines that the management message between the source device and the destination device is forwarded by using a CAPWAP tunnel, and the transmission path of the management message includes the underlying network entity and the CAPWAP network entity.
  • the analysis device determines that the service message in the tunnel forwarding mode between the source device and the destination device is forwarded by the CAPWAP tunnel, and the transmission path of the service message includes the underlying network entity and the CAPWAP network entity.
  • the analysis device determines that the transmission path of the service packet includes the underlying network entity and the overlay network entity; The source device and the destination device do not pass through the overlay network, and the analysis device determines that the transmission path of the service packet only includes the underlying network entity. Whether service packets are forwarded through tunnel or tunnel depends on the specific configuration of the AP.
  • the analysis device determines the intermediate network entity from the source network entity to the destination network entity based on the knowledge graph according to the network from the source device to the destination device.
  • the implementation process includes: the analysis device determines the overlay network entity corresponding to the tunnel and the underlying network entity bearing the tunnel on the knowledge graph according to the tunnel endpoint of the tunnel passed by the source device to the destination device in the overlay network.
  • the implementation process of the analyzing device determining the source device and the destination device in the target network includes: the analyzing device determines the source device and the destination device in the target network according to an abnormal event generated in the target network.
  • the abnormal event includes the access information of the abnormal service and the service type of the abnormal service.
  • the access information of the abnormal service includes the access information of the source end device and/or the access information of the destination device that carries the abnormal service.
  • the analysis device can determine the source device and the destination device according to the abnormal events generated in the target network, and then generate the transmission path from the source device to the destination device based on the knowledge graph of the target network, which can determine the abnormal path in real time and improve the target network. fault location efficiency in .
  • the knowledge graph of the target network identifies an abnormal network entity that generates an abnormal event in the target network, and after the analysis device determines the transmission path from the source network entity to the destination network entity on the knowledge graph, it can also The abnormal network entity of the network determines the fault root cause of the abnormal service.
  • the analysis device can further determine the root cause of the faulty network entity on the transmission path according to the fault propagation rule, and then determine the fault root cause of the abnormal service, so as to realize end-to-end Fault root cause location.
  • the analysis device determines the transmission path on the knowledge graph of the target network according to the abnormal event generated in the target network, it can detect the fault in the target network that caused the abnormal event in real time, and the fault location efficiency is high.
  • the types of abnormal events include one or more of alarm logs, state change logs, and abnormal key performance indicators.
  • the analysis device may also generate a knowledge graph of the target network according to the network data of the target network.
  • the network data includes the networking topology of the target network and device information of multiple network devices in the target network.
  • Device information includes configuration information.
  • Device information may also include routing information and/or state information.
  • a path determination device in a second aspect, includes a plurality of functional modules, and the plurality of functional modules interact to implement the methods in the first aspect and the various embodiments thereof.
  • the multiple functional modules may be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules may be arbitrarily combined or divided based on specific implementations.
  • a path determination device including: a processor and a memory;
  • the memory for storing a computer program, the computer program including program instructions
  • the processor is configured to invoke the computer program to implement the path determination method in the first aspect and its various embodiments.
  • a computer storage medium is provided, and instructions are stored on the computer storage medium, and when the instructions are executed by a processor of a computer device, the path determination method in the first aspect and its various embodiments is implemented. .
  • a chip in a fifth aspect, includes programmable logic circuits and/or program instructions, and when the chip runs, the methods in the first aspect and the various embodiments thereof are implemented.
  • the knowledge graph of the network is composed of knowledge graph triples, other network entities that have a relationship with the network entity can be found through one network entity, so the source network entity and the destination network entity on the knowledge graph acquired by the analysis device are Afterwards, the transmission path from the source network entity to the destination network entity can be determined according to the relationship between the network entities.
  • the transmission path from the source network entity to the destination network entity is also the transmission path from the source device to the destination device.
  • all transmission paths from the source network entity to the destination network entity can be found by searching the knowledge graph, which can be applied to more scenarios. Further, since an abnormal network entity is identified on the transmission path determined by the analysis device, the analysis device can further determine the root cause of the failure network entity on the transmission path according to the fault propagation rule, and then determine the failure root cause of the abnormal service, so as to realize the end-to-end failure. Root cause location. In addition, after the analysis device determines the transmission path on the knowledge graph of the target network according to the abnormal event generated in the target network, it can detect the fault in the target network that caused the abnormal event in real time, and the fault location efficiency is high.
  • FIG. 1 is a schematic diagram of an application scenario involved in a path determination method provided by an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a communication network provided by an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a path determination method provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a knowledge graph provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of another knowledge graph provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a path determination device provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a first determination module provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of another path determination apparatus provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of another path determination device provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of still another path determination apparatus provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of still another path determination device provided by an embodiment of the present application.
  • FIG. 12 is a block diagram of an apparatus for determining a path provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of an application scenario involved in a path determination method provided by an embodiment of the present application.
  • the application scenario includes: an analysis device 101 and network devices 102A-102C (collectively referred to as network devices 102 ) in a communication network.
  • the number of network devices in FIG. 1 is only used for exemplary illustration, and not as a limitation on the communication network involved in the embodiments of the present application.
  • the analysis device 101 may be a server, or a server cluster composed of several servers, or a cloud computing service center.
  • the network device 102 may be a physical communication device such as a switch or a router, or may also be a virtual communication device such as a virtual switch or a virtual router.
  • the application scenario also includes a control device 103 .
  • the control device 103 is used to manage and control the network device 102 in the communication network.
  • the control device 103 may be a network controller, a network management device, a gateway or other devices with control capability.
  • the control device 103 may be one or more devices.
  • the analysis device 101 and the control device 103 are connected through a wired network or a wireless network.
  • the control device 103 and the network device 102 are connected through a wired network or a wireless network.
  • control device 103 stores the networking topology of the communication network managed by the control device 103 .
  • the control device 103 is also used to collect the device information of the network device 102 in the communication network and the abnormal events generated in the communication network, etc., and provide the analysis device 101 with the networking topology of the communication network, the device information of the network device 102 and the communication network. abnormal events, etc.
  • the device information of the network device 102 includes at least configuration information.
  • the configuration information of the network device specifically includes interface configuration information, protocol configuration information, and/or service configuration information, and the like.
  • the device information of the network device 102 may further include routing information and/or state information and the like.
  • the routing information of the network device specifically includes an Address Resolution Protocol (Address Resolution Protocol, ARP) table, a Media Access Control (Media Access Control, MAC) table, a routing table and/or a forwarding table.
  • the state information of the network device specifically includes protocol state information and/or tunnel state information, and the like.
  • the protocol status information includes open shortest path first (OSPF) protocol status information, Border Gateway Protocol (BGP) status information, and/or link layer discovery protocol (LLDP) ) status information, etc.
  • the tunnel status information includes the identity of the tunnel endpoint and the status of the tunnel.
  • the control device 103 may periodically collect device information of the network device 102 and abnormal events generated in the communication network.
  • the control device may use the remote terminal protocol (telnet for short), the simple network management protocol (SNMP) or the network telemetry (network telemetry) technology to collect the device information of the network device and the abnormal events generated in the communication network .
  • SNMP simple network management protocol
  • network telemetry network telemetry
  • the analysis device 101 may also be integrated with the control device 103 , that is, the analysis device 101 is directly connected to the network device 102 in the communication network, which is not limited in this embodiment of the present application.
  • the communication network provided by the embodiment of the present application may be a data center network (data center network, DCN), a metropolitan area network, a wide area network, or a campus network, etc.
  • the embodiment of the present application does not limit the type of the communication network.
  • the communication network includes an underlay network.
  • the underlying network may be a physical network composed of the Internet (internet), a multi-protocol label switching (MPLS) network, and/or a long term evolution (long term evolution, LTE) network, and the like.
  • the underlying network includes multiple network devices, and the multiple network devices are connected through physical links.
  • the communication network may further include an upper layer network constructed on the lower layer network, and the upper layer network may also be referred to as a logical network or a virtual network.
  • the upper layer network may include an overlay network and/or a control and provisioning of wireless access points (CAPWAP) network.
  • CAPWAP wireless access points
  • the overlay network can be implemented using generic routing encapsulation (GRE) protocol, virtual extensible local area network (VXLAN) protocol, dynamic smart virtual private network (DSVPN) technology and/or automatic Virtual private network (automatic virtual private network, Auto VPN) technology is a network constructed on the basis of the underlying network.
  • GRE generic routing encapsulation
  • VXLAN virtual extensible local area network
  • DVPN dynamic smart virtual private network
  • Auto VPN automatic Virtual private network
  • Auto VPN automatic Virtual private network
  • the overlay network includes tunnels (also called overlay tunnels), which are virtual or logical links. Each tunnel corresponds to one or more paths in the underlying network, where each path is usually composed of multiple physical links connected one after the other in the underlying network.
  • CAPWAP networks include CAPWAP tunnels.
  • a CAPWAP tunnel is usually established between an access point (AP) and an access controller (AC).
  • a CAPWAP tunnel is divided into a data channel and a control channel.
  • the data channel is used to transmit service packets (ie, user data packets), and the control channel is used to transmit management packets (also called control packets).
  • the communication network provided by the embodiments of the present application may adopt a two-layer network architecture or a three-layer network architecture.
  • the communication network includes a convergence layer and an access layer, which can also be called a two-layer network.
  • the convergence layer is the high-speed switching backbone of the communication network
  • the access layer is used to connect workstations to the communication network.
  • the communication network includes a core layer, an aggregation layer and an access layer.
  • the communication network can also be called a three-layer network.
  • the core layer is the high-speed switching backbone of the communication network, and the aggregation layer is used to provide aggregation connections (connection access layer and core layer), the access layer is used to connect the workstation to the communication network.
  • the workstation may include a terminal, an AP, a server, or a virtual machine (virtual machine, VM), and the like.
  • the terminal can be a mobile phone or a computer.
  • FIG. 2 is a schematic structural diagram of a communication network provided by an embodiment of the present application.
  • the communication network 20 includes a core layer network device 102a, aggregation layer network devices 102b1-102b2, and access layer network devices 102c1-102c2.
  • An AP 104 is connected to the access layer network device 102c1, the AP 104 is connected to the terminal 105a, and the access layer network device 102c2 is connected to a virtual machine 105b.
  • the access layer network device 102c1 has the interface GE1/0/0.1 and the interface GE1/1/0
  • the aggregation layer network device 102b1 has the interface GE1/2/0 and the interface GE1/3/0
  • the core layer network The device 102a has interfaces GE1/4/0, GE1/5/0, and GE1/6/0
  • the aggregation layer network device 102b2 has interfaces GE1/7/0 and GE1/8/0
  • the access layer network device 102c2 It has interface GE1/0/1.1 and interface GE1/9/0.
  • the interface GE1/0/0.1 on the access layer network device 102c1 and the interface GE1/0/1.1 on the access layer network device 102c2 are boundary interfaces.
  • the access layer network device 102c1 is connected to the AP 104 through the interface GE1/0/0.1, and the access layer network device 102c2 is connected to the virtual machine 105b through the interface GE1/0/1.1.
  • the interface GE1/1/0 of the access layer network device 102c1 is connected to the interface GE1/2/0 of the aggregation layer network device 102b1.
  • the interface GE1/3/0 of the aggregation layer network device 102b1 is connected to the interface GE1/4/0 of the core layer network device 102a.
  • the interface GE1/6/0 of the core layer network device 102a is connected to the interface GE1/7/0 of the aggregation layer network device 102b2.
  • the interface GE1/8/0 of the aggregation layer network device 102b2 is connected to the interface GE1/9/0 of the access layer network device 102c2.
  • FIG. 3 is a schematic flowchart of a path determination method provided by an embodiment of the present application. The method can be applied to the analysis device 101 in the application scenario shown in FIG. 1 . As shown in Figure 3, the method includes:
  • Step 301 acquiring the knowledge graph of the target network.
  • the knowledge graph includes multiple knowledge graph triples.
  • Each knowledge graph triplet includes two network entities and a relationship between the two network entities.
  • the types of network entities are devices, interfaces, protocols or services.
  • the network entity of type device can be represented by the name of the device, MAC address, hardware address, OSPF route (abbreviation: OsRouter, which can uniquely identify the network device at the OSPF layer) or other identifiers that can uniquely identify the device.
  • a network entity of type interface can be represented by the name of the interface.
  • a network entity of type protocol may be represented by an identifier of the protocol.
  • Knowledge graph triples are represented in the form of graphs. The knowledge graph triple is composed of two basic elements: point and edge. The point represents the network entity, and the edge represents the relationship between the two network entities. Among them, the edges in the knowledge graph triples can be directional or non-directional.
  • Edges in knowledge graph triples can also be used to represent specific relationships between two network entities, such as dependencies or peer-to-peer relationships. For example, when two network entities are in a peer-to-peer relationship, an undirected edge can be used to connect the two network entities; when two network entities are in a dependent relationship, a directional edge (such as an arrow) can be used ) connects the two network entities, and the direction of the edge is from the dependent network entity to the dependent network entity.
  • a directional edge such as an arrow
  • Each network entity has its own configuration, for example, an interface is configured with attributes such as an interface state, an interface name, an Internet Protocol (Internet Protocol, IP) address, and/or whether to join a VLAN. Relationships are established between network entities based on configurations and physical links.
  • the network device has an interface, that is, the interface depends on the network device; the interface of the network device can carry forwarding services, that is, the forwarding service depends on the interface; Layer 3 The forwarding service can carry VXLAN tunnels, traffic engineering (TE) tunnels, and BGP, that is, VXLAN tunnels, TE tunnels, and BGP rely on Layer 3 forwarding services; TE tunnels can carry VPN services, that is, Yes, VPN services rely on TE tunnels; and so on.
  • TE traffic engineering
  • the Layer 3 forwarding service can carry VXLAN tunnels, indicating that the interface carrying the Layer 3 forwarding service can be used as the endpoint of the VXLAN tunnel; the Layer 3 forwarding service can carry TE tunnels, indicating that the interface carrying the Layer 3 forwarding service can be used as a TE The endpoint of the tunnel; BGP can be carried on the Layer 3 forwarding service, indicating that the interface carrying the Layer 3 forwarding service can send and receive BGP-based protocol packets; the TE tunnel can carry VPN services, indicating that the interface carrying the TE tunnel can support VPN business.
  • the implementation process of step 301 includes: the analyzing device generates a knowledge graph of the target network according to the network data of the target network.
  • the network data includes the networking topology of the target network and device information of multiple network devices in the target network.
  • the device information of the network device includes configuration information.
  • the interface configuration information of the network device may include the IP address of the interface, the protocol type supported by the interface, the service type supported by the interface, and the like.
  • the protocol configuration information of the network device may include a protocol identifier, which is used to uniquely identify the protocol, and the protocol identifier may be represented by characters, letters, and/or numbers.
  • the service configuration information of the network device may include services used by the network device, such as a virtual private network (virtual private network, VPN) service and/or a Dynamic Host Configuration Protocol (Dynamic Host Configuration Protocol, DHCP) service, and the like.
  • the device information of the network device may also include state information and/or routing information of the network device, and the like.
  • the analysis device periodically acquires device information of network devices in the target network, and generates a knowledge graph of the target network.
  • the analysis device may also store the knowledge graph of the target network in the analysis device or in a storage device connected to the analysis device for subsequent use.
  • the knowledge graph of the target network can be used as a basis for determining fault propagation relationships between network entities, and/or as a basis for fault root cause reasoning, etc.
  • the analysis device can identify the abnormal network entity that generated the abnormal event on the knowledge graph corresponding to the period, and obtain the knowledge graph with the abnormal network entity identified, thereby improving the identification of the abnormal network entity. Acquisition efficiency of knowledge graphs with abnormal network entities.
  • the knowledge graph of the target network can also be generated by other devices according to the network data of the target network and sent to the analysis device. This embodiment of the present application does not limit this.
  • the target network includes two network devices, namely network device A and network device B.
  • Network device A has three interfaces, and the names of the three interfaces are 10GE1/0/1, 10GE1/0/2, and 10GE1/0/3, respectively.
  • Network device B has four interfaces, and the names of the four interfaces are 10GE3/0/1, 10GE3/0/2, 10GE3/0/3, and 10GE3/0/4.
  • Both network device A and network device B support the OSPF protocol.
  • the identifier of the OSPF protocol in network device A is represented by 10.89.46.25, including three routing IPs, namely 11.11.11.11, 11.11.11.12, and 11.11.11.13.
  • the identifier of the OSPF protocol in the network device B is represented by 10.89.49.37, including four routing IPs, namely 11.12.11.11, 11.12.11.12, 11.12.11.13, and 11.12.11.14.
  • the interface "10GE1/0/2" of network device A is connected to the interface "10GE3/0/2" of network device B, and the two interfaces communicate using the OSPF protocol.
  • the interface "10GE1/0" of network device A is The route IP used by /2" is 11.11.11.11, and the route IP used by the interface "10GE3/0/2” of network device B is 11.12.11.14. Based on the above network data, the knowledge graph shown in Figure 4 can be obtained.
  • abnormal network entities that generate abnormal events in the target network are identified on the knowledge graph of the target network.
  • the types of abnormal events include one or more of alarm logs, state change logs, and abnormal key performance indicators (key performance indicators, KPIs).
  • the alarm log includes the identifier of the abnormal network entity in the network device and the alarm type.
  • the state change log includes configuration file change information and/or routing table entry change information, etc.
  • the state change log may include information such as "deletion of access sub-interface" or "deletion of destination IP host route".
  • Abnormal KPIs are used to describe an abnormality in a certain indicator of a network entity.
  • the knowledge graph can be The network entity corresponding to the interface "10GE1/0/2" and the network entity corresponding to the routing IP "11.11.11.11” are identified as abnormal network entities.
  • the abnormal event entity can be connected to the abnormal network entity to identify the abnormality.
  • Abnormal event entities can be distinguished from network entities by special graphics or colors. For example, referring to FIG. 5, a triangle may be used to represent an abnormal event entity.
  • the abnormal event entity may also include the specific content of the abnormal event, so that the operation and maintenance personnel can quickly obtain abnormal objects and specific abnormal types in the target network based on the knowledge graph.
  • the network entities on the knowledge graph of the target network include physical entities and logical entities.
  • Physical entities include physical devices and/or physical interfaces.
  • Logical entities include one or more of logical devices, logical interfaces, protocols or services.
  • physical entities include physical devices and physical interfaces
  • physical devices include network device A and network device B
  • physical interfaces include 10GE1/0/1, 10GE1/0/2, and 10GE1 /0/3, 10GE3/0/1, 10GE3/0/2, 10GE3/0/3, and 10GE3/0/4.
  • Logical entities include protocols and logical interfaces. Protocols include OSPF 10.89.46.25 and OSPF 10.89.49.37. Logical interfaces are represented by assigned routing IP. Logical interfaces include 11.11.11.11, 11.11.11.12, 11.11.11.13, 11.12.11.11, and 11.12. .11.12, 11.12.11.13 and 11.12.11.14.
  • the knowledge graph of the target network may only include network entities corresponding to network devices in the target network, or the knowledge graph of the target network may include network entities corresponding to network devices in the target network and access targets A network entity corresponding to a terminal, AP, server, or virtual machine of a network.
  • Step 302 Determine the source network entity and the destination network entity on the knowledge graph of the target network.
  • the analysis device first determines the source end device and the destination device accessing the target network, then determines the source network entity according to the source end device, and determines the destination network entity according to the destination device.
  • the following describes the implementation process of the analysis device determining the source network entity according to the source device and determining the destination network entity according to the destination device.
  • the analysis device may determine the source network entity according to the access information of the source end device.
  • the access information of the source device includes the identifier of the source device.
  • the identifier of the source end device may be the MAC address or IP address of the source end device, or the like.
  • the source device when the source device is a wired device, for example, the source device is a server or a virtual machine, etc., the source device is wired to a network device in the target network to access the target network, and the source device is connected to the target
  • the network device of the network can report the access information of the source device to the analysis device.
  • the source device is a wireless device, for example, the source device is a mobile phone
  • the source device is associated with the AP
  • the AP is wired to the access layer network device in the target network to connect the source device to the target network.
  • the network device or the AC for managing the AP can report the access information of the source device to the analysis device.
  • the access information of the source device may also include interface information of the network device that accesses the source device to the target network and/or quintuple information and triplet information of the source device.
  • the access information of the source device may also include the identification of the AP associated with the source device, the identification of the radio used by the source device, or the service of the AP associated with the source device.
  • SSIDs service set identifiers
  • the source network entity may be a source end device, or the source network entity may be a first interface of a first network device in the target network, where the first interface of the first network device is used to connect the source end device to target network. If the knowledge graph of the target network includes a network entity corresponding to the source device and a network entity corresponding to the network device in the target network, the analysis device determines that the source network entity is the source device.
  • the analysis device determines that the source network entity is the interface of the network device connected to the source device in the target network;
  • the analysis device determines that the source network entity is an interface of a network device in the target network that is connected to the AP associated with the source device.
  • the analyzing device determines the destination network entity according to the destination device in the following two implementation manners:
  • the analyzing device may determine the destination network entity according to the access information of the destination device.
  • the access information of the destination device includes the identifier of the destination device.
  • the destination network entity may be a destination device, or the destination network entity may be a second interface of a second network device in the target network, where the second interface of the second network device is used to connect the destination device to the target network.
  • the manner in which the analysis device acquires the access information of the destination device and the implementation manner of determining the destination network entity according to the access information of the destination device may refer to the manner in which the analysis device acquires the access information of the source device and the method for determining the destination network entity according to the access information of the destination device.
  • the implementation manner of determining the source network entity by the incoming information is not repeated in this embodiment of the present application.
  • the destination device is a DHCP server or a DHCP relay device.
  • the analysis device can obtain the target VLAN corresponding to the DHCP service of the source device.
  • the target VLAN has a binding relationship with the target Layer 2 forwarding instance
  • the analyzing device determines that the target network entity is the Layer 3 virtual interface corresponding to the target Layer 2 forwarding instance on the core network device in the target network.
  • the target Layer 2 forwarding instance is any Layer 2 forwarding instance other than the VLAN instance, for example, the target Layer 2 forwarding instance is a bridge domain (bridge domain, BD) instance.
  • the analysis device determines that the target network entity is the VLAN interface corresponding to the target VLAN on the core network device in the target network.
  • the VLAN interface may also be called vlanif.
  • one or more forwarding instances are configured in the network device, and one forwarding instance corresponds to a set of locally valid routing information on the network device.
  • Each forwarding instance in the same network device works independently to implement route isolation.
  • the network device may include a Layer 2 forwarding instance (L2VPN instance) and/or a Layer 3 forwarding instance (L3VPN instance).
  • the Layer 2 forwarding instance corresponds to the Layer 2 routing information on the network device, such as the MAC table;
  • the Layer 3 forwarding instance corresponds to the Layer 3 routing information on the network device, such as the forwarding table.
  • a VLAN instance is a Layer 2 forwarding instance.
  • an L2VPN instance can also be called a BD instance (corresponding to a Layer 2 forwarding domain).
  • An L3VPN instance may also be referred to as a virtual routing forwarding (VRF) instance (corresponding to a Layer 3 forwarding domain).
  • VRF virtual routing forwarding
  • the target Layer 2 forwarding instance may be a BD instance
  • the Layer 3 virtual interface corresponding to the BD instance is a BD-based logical interface, which may be referred to as vbdif for short.
  • the target VLAN corresponding to the DHCP service of the source device has a binding relationship with the BD instance, it means that the DHCP packet of the source device is forwarded through the VXLAN tunnel, and the analysis device can find the corresponding BD instance on the core network device. Then the vbdif bound to the BD instance is used as the destination network entity. If the target VLAN corresponding to the DHCP service does not have a binding relationship with the BD instance, it means that the DHCP packets of the source device are not forwarded through the VXLAN tunnel. The analysis device can find the corresponding VLAN instance on the core network device, and then use the VLAN instance. The bound vlanif is used as the destination network entity.
  • the analysis device can also use the DHCP server or DHCP relay device connected to the vbdif or vlanif bound to the Layer 2 forwarding instance on the core network device as the DHCP server or DHCP relay device.
  • Destination network entity if the knowledge graph of the target network includes a DHCP server or a DHCP relay device, the analysis device can also use the DHCP server or DHCP relay device connected to the vbdif or vlanif bound to the Layer 2 forwarding instance on the core network device. Destination network entity.
  • the implementation process of the analyzing device acquiring the target VLAN corresponding to the DHCP service of the source-end device includes: One or more of the ID of the radio and the service set ID of the access point associated with the source device, determine the service VLAN corresponding to the source device, and use the service VLAN corresponding to the source device as the target VLAN.
  • the analysis device may determine the source device and the destination device in the target network according to abnormal events generated in the target network.
  • the abnormal event includes the access information of the abnormal service and the service type of the abnormal service.
  • the access information of the abnormal service includes the access information of the source end device and/or the access information of the destination device that carries the abnormal service.
  • the service types of abnormal services include DHCP services, associated services, authentication services, or audio and video services.
  • the association service and the authentication service respectively refer to the association and authentication between the terminal and the AP in the wireless local area network.
  • the abnormal event generated in the target network may be generated by the analysis device according to the log or alarm reported by the network device and/or the AP. Alternatively, abnormal events generated in the target network can also be externally input.
  • DHCP timeout exception event can be represented as follows:
  • the service type of the abnormal service included in the abnormal event is DHCP service, and the abnormal cause is DHCP timeout.
  • the MAC address of the source device is 6480-9915-cd9b
  • the radio ID used by the source device is 1
  • the AP associated with the source device is AP2
  • the SSID of the AP associated with the source device is 1x-135.
  • the source device is a terminal with a MAC address of 6480-9915-cd9b
  • the destination device is a DHCP server or a DHCP relay device.
  • the operation and maintenance personnel can also directly specify the source network entity and the destination network entity on the knowledge graph, or the operation and maintenance personnel can also input the access information of the source device to the analysis device for the analysis device to determine the source network.
  • the network entity and/or the operation and maintenance personnel input the access information of the destination device to the analysis device for the analysis device to determine the destination network entity.
  • This embodiment of the present application does not limit the manner in which the analysis device determines the source network entity and the destination network entity on the knowledge graph of the target network.
  • Step 303 Determine the transmission path from the source network entity to the destination network entity on the knowledge graph of the target network.
  • the transmission path from the source network entity to the destination network entity determined on the knowledge graph of the target network belongs to the knowledge graph of the target network, that is, the transmission path is a sub-graph of the knowledge graph of the target network.
  • the network entities on the transmission path include physical entities and logical entities. There may be one or more transmission paths from the source network entity to the destination network entity.
  • the currently determined transmission path usually only includes hardware such as physical devices and physical interfaces, while the transmission path determined in this embodiment of the present application includes not only physical entities such as physical devices and/or physical interfaces, but also logical devices (for example, logical switches BD, logical router VPN, etc.), logical interfaces (eg vlanif, vbdif, network virtualization edge (NVE), LoopBack, etc.), protocols (eg OSPF, BGP, etc.) and/or services (eg tunnel traffic, VXLAN tunnel, CAPWAP)
  • the transmission path can reflect the protocols and services used for communication between the source device and the destination device.
  • the transmission path contains more information, which is convenient for later analysis of the network.
  • the implementation process of step 303 includes: the analysis device determines the intermediate network entities that the source network entity passes through to the destination network entity based on the network passed by the source end device to the destination device, and the source end device to the destination network entity based on the knowledge graph of the target network.
  • the network traversed by the destination device includes the underlying network.
  • the analyzing device determines a transmission path according to the intermediate network entity that the source network entity passes through to the destination network entity, and the transmission path includes the source network entity, the destination network entity and the intermediate network entity. All intermediate network entities determined by the analysis device may be included on the transmission path.
  • the network traversed by the source device to the destination device also includes an upper-layer network.
  • the upper layer network includes overlay networks and/or CAPWAP networks.
  • the analysis device can determine the overlay network entity corresponding to the tunnel and The underlying network entity that carries this tunnel.
  • the overlay network entity refers to the corresponding network entity in the overlay network, such as BD instance or vbdif; the underlying network entity refers to the corresponding network entity in the underlying network, such as physical device, physical interface, OSPF or BGP, etc.
  • the source device is the terminal 105a
  • the destination device is a DHCP server (not shown in the figure) connected to the core layer network device 102a
  • the source device to the destination device passes through
  • the overlay network runs the VXLAN protocol.
  • the access layer network device 102c1 is configured with a VXLAN tunnel endpoint (VXLAN tunnel endpoint, VTEP) 1
  • the core layer network device 102a is configured with a VTEP2.
  • a VXLAN tunnel connection is established between the access layer network device 102c1 and the core layer network device 102a based on VTEP1 and VTEP2. Tunnels are unidirectional.
  • both the access layer network device 102c1 and the core layer network device 102a are configured with BD instances.
  • the identifier of the BD instance in the access layer network device 102c1 is 10, referred to as BD10 for short, the NVE connected to the BD10 in the access layer network device 102c1 is referred to as NVE1 for short; the identifier of the BD instance in the core layer network device 102a is 20, referred to as BD20,
  • the NVE connected to the BD20 in the core layer network device 102a is referred to as NVE2 for short.
  • the analysis device determines that the overlay network entities corresponding to the tunnel on the knowledge graph include BD10, NVE1, NVE2, and BD20, and the underlying network entities bearing the tunnel include the access layer network device 102c1, interface GE1/1/0, interface GE1/2/0 , the convergence layer network device 102b1, the interface GE1/3/0, the interface GE1/4/0, and the core layer network device 102a.
  • the analysis device can determine that the network entities that the terminal 105a passes through to the DHCP server include: the access layer network device 102c1, the interface GE1/1/0, the interface GE1/2/0, the aggregation layer network device 102b1, and the interface GE1/3/0 , interface GE1/4/0 and core layer network device 102a, and, BD10, NVE1, NVE2 and BD20.
  • the packets between the source device and the destination device can be transmitted in forwarding modes such as Layer 2 forwarding, Layer 3 forwarding, VXLAN tunnel forwarding, or CAPWAP tunnel forwarding, and the analysis device can be based on the specific configuration of the network device in the target network. to determine the forwarding mode.
  • the analysis device may determine the network through which the source device and the destination device pass based on the access mode of the source device accessing the target network, and further determine the forwarding mode of packets between the source device and the destination device.
  • the access mode for the source device to access the target network is wired access.
  • the analysis device determines that the source device and the destination device pass through the overlay network.
  • the analysis device determines that the source device and the destination device do not pass through the overlay network.
  • the target Layer 2 forwarding instance is any Layer 2 forwarding instance except the VLAN instance, such as a BD instance.
  • the analysis device determines that the transmission path from the source device to the destination device includes the underlying network entity and the overlay network entity. If the overlay network runs the VXLAN protocol, the analysis device determines that the packets between the source device and the destination device are forwarded through a VXLAN tunnel. When the source device and the destination device do not pass through the overlay network, the analysis device determines that the transmission path from the source device to the destination device only includes the underlying network entities.
  • the access mode of the source device accessing the target network is wireless access.
  • the analysis device determines that the source device and the destination device pass through the CAPWAP network.
  • the packet type between the source device and the destination device is a service packet
  • the service packet is forwarded directly and the service VLAN corresponding to the service packet is bound to the target Layer 2 forwarding instance.
  • the analysis device determines the source end.
  • the device to the destination device goes through the overlay network.
  • the target Layer 2 forwarding instance is any Layer 2 forwarding instance except the VLAN instance, such as a BD instance.
  • the analysis device determines that the source device and the destination device pass through the CAPWAP network.
  • direct forwarding may also be called local forwarding
  • tunnel forwarding may also be called centralized forwarding.
  • the service packets in direct forwarding mode do not pass through the CAPWAP tunnel, and the service packets in the tunnel forwarding mode pass through the CAPWAP tunnel.
  • the analysis device determines that the management packet between the source device and the destination device is forwarded by using the CAPWAP tunnel, and the transmission path of the management packet includes the underlying network entity and the CAPWAP network entity.
  • the analysis device determines that the service message in the tunnel forwarding mode between the source device and the destination device is forwarded by the CAPWAP tunnel, and the transmission path of the service message includes the underlying network entity and the CAPWAP network entity.
  • the analysis device determines that the transmission path of the service packet includes the underlying network entity and the overlay network entity; The source device and the destination device do not pass through the overlay network, and the analysis device determines that the transmission path of the service packet only includes the underlying network entity.
  • the CAPWAP network entity refers to a corresponding network entity in the CAPWAP network. Whether service packets are forwarded through tunnel or tunnel depends on the specific configuration of the AP.
  • the knowledge graph of the network is composed of knowledge graph triples, other network entities that have a relationship with the network entity can be found through one network entity, so the source network entity and the destination network entity on the knowledge graph are acquired. Afterwards, the transmission path from the source network entity to the destination network entity can be determined according to the relationship between the network entities.
  • the transmission path from the source network entity to the destination network entity is also the transmission path from the source device to the destination device.
  • the application embodiment does not need to depend on a service packet transmission scenario, and the path determination is more flexible.
  • all transmission paths from the source network entity to the destination network entity can be found by searching the knowledge graph, which can be applied to more scenarios, such as an equal-cost multi-path (ECMP) scenario ,and many more.
  • ECMP equal-cost multi-path
  • Step 304 when an abnormal network entity that generates an abnormal event in the target network is identified on the knowledge graph of the target network, after the analysis device determines the transmission path from the source network entity corresponding to the abnormal event to the destination network entity on the knowledge graph of the target network, Step 304 described below may also be performed.
  • Step 304 Determine the fault root cause of the abnormal service based on the abnormal network entity on the transmission path from the source network entity to the destination network entity.
  • the analysis device first determines the transmission path of the DHCP message on the knowledge graph of the target network based on the abnormal DHCP timeout event in step 302, and then performs inference based on the abnormal network entity with the abnormal event mounted on the transmission path, and obtains a conclusion.
  • OsRouter ID conflict causes wireless device DHCP timeout.
  • the analysis device can further determine the root cause of the faulty network entity on the transmission path according to the fault propagation rule, and then determine the fault root cause of the abnormal service. To locate the root cause of the fault.
  • the analysis device determines the transmission path on the knowledge graph of the target network according to the abnormal event generated in the target network, it can detect the fault in the target network that caused the abnormal event in real time, and the fault location efficiency is high.
  • the fault propagation rule can be obtained based on expert experience.
  • the network entities on the knowledge graph of the target network can mount various related abnormal events
  • other technologies such as iFIT or data plane verification (DPV)
  • iFIT iFIT
  • DUV data plane verification
  • the inference engine can locate more types of fault root causes, which is easy to expand.
  • the transmission path from the source network entity to the destination network entity can be determined according to the relationship between the network entities.
  • the transmission path from the source network entity to the destination network entity is also the transmission path from the source device to the destination device.
  • the application embodiment When determining a transmission path between two devices, the application embodiment does not need to depend on a service packet transmission scenario, and the path determination is more flexible.
  • all transmission paths from the source network entity to the destination network entity can be found by searching the knowledge graph, which can be applied to more scenarios, such as ECMP scenarios, and so on.
  • the analysis device can further determine the root cause fault network entity on the transmission path according to the fault propagation rule, and then determine the fault root cause of the abnormal service, so as to realize the end-to-end fault. Root cause location.
  • the analysis device determines the transmission path on the knowledge graph of the target network according to the abnormal event generated in the target network, it can detect the fault in the target network that caused the abnormal event in real time, and the fault location efficiency is high.
  • FIG. 6 is a schematic structural diagram of a path determination apparatus provided by an embodiment of the present application.
  • the apparatus may be the analysis device 101 in the application scenario shown in FIG. 1 .
  • the device 60 includes:
  • the first determination module 601 is used to determine the source network entity and the destination network entity on the knowledge graph of the target network, the knowledge graph includes a plurality of knowledge graph triples, and each knowledge graph triple includes two network entities and two The relationship between two network entities.
  • the type of network entity is equipment, interface, protocol or service.
  • the second determining module 602 is configured to determine the transmission path from the source network entity to the destination network entity on the knowledge graph.
  • the network entities on the transmission path include physical entities and logical entities
  • the physical entities include physical devices and/or physical interfaces
  • the logical entities include one or more of logical devices, logical interfaces, protocols or services.
  • the first determining module 601 is configured to: determine the source end device and the destination device accessing the target network; determine the source network entity according to the source end device, and determine the destination network entity according to the destination device.
  • the first determining module 601 is configured to: determine the source network entity according to the access information of the source device, where the access information of the source device includes the identifier of the source device.
  • the source network entity is a source end device, or the source network entity is a first interface of a first network device in the target network, and the first interface of the first network device is used to connect the source end device to the target network.
  • the first determining module 601 is configured to: determine the destination network entity according to the access information of the destination device, where the access information of the destination device includes the identifier of the destination device.
  • the destination network entity is a destination device, or the destination network entity is a second interface of a second network device in the target network, and the second interface of the second network device is used to connect the destination device to the target network.
  • the first determination module 601 includes:
  • Determining submodule 6012 is used to determine that the target network entity is a layer 3 virtual interface corresponding to the target layer 2 forwarding instance on the core network device in the target network when the target VLAN has a binding relationship with the target layer 2 forwarding instance, the target layer 2
  • the forwarding instance is any Layer 2 forwarding instance other than the VLAN instance; the determining submodule 6012 is also used to determine that the destination network entity is when the target VLAN does not have a binding relationship with other Layer 2 forwarding instances except the VLAN instance.
  • the source end device is a wireless device
  • the acquisition sub-module 6011 is configured to: according to the identification of the access point associated with the source end device, the identification of the radio used by the source end device, and the identification of the access point associated with the source end device.
  • the service VLAN corresponding to the source device is determined, and the service VLAN corresponding to the source device is used as the target VLAN.
  • the second determining module 602 is configured to: determine, according to the network passed from the source end device to the destination device, based on the knowledge graph, determine the intermediate network entity passed by the source network entity to the destination network entity, where the source end device goes to the destination device.
  • the network passed through includes the underlying network; the transmission path is determined according to the intermediate network entity passed through from the source network entity to the destination network entity, and the transmission path includes the source network entity, the destination network entity and the intermediate network entity.
  • the network from the source device to the destination device further includes an upper-layer network
  • the upper-layer network is constructed on the bottom-layer network
  • the upper-layer network includes an overlay network and/or a CAPWAP network.
  • the access mode for the source device to access the target network is wired access.
  • the device 60 further includes:
  • the third determining module 603 is configured to, when the interface of the network device connected to the source device in the target network has a binding relationship with the target layer-2 forwarding instance, determine that the source-end device and the destination device pass through the overlay network, and the target layer-2 forwarding instance is Any Layer 2 forwarding instance other than the VLAN instance.
  • the access mode of the source device accessing the target network is wireless access.
  • the device 60 further includes:
  • the fourth determining module 604 is configured to determine that the source device and the destination device pass through the CAPWAP network when the type of the message between the source device and the destination device is a management message; the fourth determining module 604 is also configured to be used when the source device The packet type between the device and the destination device is service packet, the service packet is forwarded directly, and the service VLAN corresponding to the service packet is bound to the target Layer 2 forwarding instance.
  • the target Layer 2 forwarding instance is any Layer 2 forwarding instance except the VLAN instance; the fourth determining module 604 is also used when the packet type between the source device and the destination device is a service packet and the service Packets are forwarded through tunnels to ensure that the source device and the destination device pass through the CAPWAP network.
  • the second determining module 602 is configured to: according to the tunnel endpoint of the tunnel traversed by the source end device to the destination device in the overlay network, in the knowledge graph The overlay network entity corresponding to the tunnel and the underlying network entity bearing the tunnel are determined above.
  • the first determining module 601 is configured to: determine the source device and the destination device in the target network according to an abnormal event generated in the target network, and the abnormal event includes the access information of the abnormal service and the service type of the abnormal service,
  • the access information of the abnormal service includes the access information of the source device carrying the abnormal service and/or the access information of the destination device.
  • abnormal network entities that generate abnormal events in the target network are identified on the knowledge graph.
  • the device 60 further includes:
  • the fifth determining module 605 is configured to determine the fault root cause of the abnormal service based on the abnormal network entity on the transmission path after determining the transmission path from the source network entity to the destination network entity on the knowledge graph.
  • the types of abnormal events include one or more of alarm logs, state change logs, and abnormal key performance indicators.
  • the apparatus 60 further includes:
  • the generating module 606 is configured to generate a knowledge graph according to network data of the target network, where the network data includes the networking topology of the target network and device information of multiple network devices in the target network, and the device information includes configuration information.
  • the path determination device since the knowledge graph of the network is composed of knowledge graph triples, other network entities that have a relationship with the network entity can be found through one network entity, so the analysis device After the source network entity and the destination network entity on the knowledge graph are passed through the first determination module, the transmission path from the source network entity to the destination network entity can be determined according to the relationship between the network entities through the second determination module.
  • the transmission path from the source network entity to the destination network entity is also the transmission path from the source device to the destination device.
  • the application embodiment When determining a transmission path between two devices, the application embodiment does not need to rely on a service packet transmission scenario, and the path determination is more flexible.
  • all transmission paths from the source network entity to the destination network entity can be found by searching the knowledge graph, which can be applied to more scenarios, such as ECMP scenarios, and so on.
  • the analysis device can further determine the root cause fault network entity on the transmission path according to the fault propagation rule, and then determine the fault root cause of the abnormal service, so as to realize the end-to-end fault. Root cause location.
  • the analysis device determines the transmission path on the knowledge graph of the target network according to the abnormal event generated in the target network, it can detect the fault in the target network that caused the abnormal event in real time, and the fault location efficiency is high.
  • FIG. 12 is a block diagram of an apparatus for determining a path provided by an embodiment of the present application.
  • the apparatus may be the analysis device 101 in the application scenario shown in FIG. 1 .
  • the apparatus 120 includes: a processor 1201 and a memory 1202 .
  • a memory 1202 for storing a computer program, the computer program including program instructions
  • the processor 1201 is configured to invoke the computer program to implement the path determination method described in the above method embodiments.
  • the apparatus 120 further includes a communication bus 1203 and a communication interface 1204 .
  • the processor 1201 includes one or more processing cores, and the processor 1201 executes various functional applications and data processing by running a computer program.
  • Memory 1202 may be used to store computer programs.
  • the memory may store the operating system and application program elements required for at least one function.
  • the operating system may be an operating system such as a real-time operating system (Real Time eXecutive, RTX), LINUX, UNIX, WINDOWS, or OS X.
  • the memory 1202 and the communication interface 1204 are respectively connected to the processor 1201 through the communication bus 1203 .
  • Embodiments of the present application further provide a computer storage medium, where instructions are stored on the computer storage medium, and when the instructions are executed by a processor of a computer device, the path determination method described in the above method embodiments is implemented.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Computational Linguistics (AREA)
  • Animal Behavior & Ethology (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种路径确定方法及装置、计算机存储介质，属于网络技术领域。分析设备先确定目标网络的知识图谱上的源网络实体和目的网络实体。该知识图谱中包括多个知识图谱三元组，每个知识图谱三元组包括两个网络实体以及所述两个网络实体之间的关系。网络实体的类型为设备、接口、协议或业务。然后，分析设备在知识图谱上确定源网络实体到目的网络实体的传输路径。本申请无需依赖于业务报文传输场景确定路径，确定路径的灵活性较高。

Description

路径确定方法及装置、计算机存储介质
本申请要求于2020年10月15日提交的申请号为202011103339.6、发明名称为“路径确定方法及装置、计算机存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及网络技术领域，特别涉及一种路径确定方法及装置、计算机存储介质。
背景技术
当前网络中经常会出现因网络环境、人为操作或设备缺陷等原因导致流量中断从而导致业务故障的问题。由于大部分业务(尤其是金融类业务和银行类业务等)对业务故障问题非常敏感，因此在业务故障后，需要及时进行故障定位，然后对故障设备采取相应隔离或恢复措施。而目前的故障定位通常基于故障业务在网络中的传输路径实现。
随流检测(in-situ flow information telemetry，iFIT)是目前用于确定业务在网络中的传输路径的常用手段。iFIT方案是通过对业务报文的报文头进行染色，然后进行逐包、逐跳检测来还原业务在网络中的真实传输路径的。
但是，采用iFIT方案来确定业务在网络中的传输路径，只能在网络中有真实的业务报文传输时才能实现，因此采用iFIT方案确定路径的应用局限性较高。
发明内容
本申请提供了一种路径确定方法及装置、计算机存储介质，可以解决目前确定业务路径的应用局限性较高的问题。
第一方面，提供了一种路径确定方法。该方法包括：分析设备先确定目标网络的知识图谱上的源网络实体和目的网络实体。该知识图谱中包括多个知识图谱三元组，每个知识图谱三元组包括两个网络实体以及所述两个网络实体之间的关系。网络实体的类型为设备、接口、协议或业务。然后，分析设备在知识图谱上确定源网络实体到目的网络实体的传输路径。
本申请中，由于网络的知识图谱由知识图谱三元组构成，通过一个网络实体能够找到与该网络实体具有关系的其它网络实体，因此在获取知识图谱上的源网络实体和目的网络实体后，可以根据网络实体之间的关系确定源网络实体到目的网络实体的传输路径。无需依赖于业务报文传输场景，确定路径的灵活性较高。另外，本申请中，通过搜索知识图谱可以找到源网络实体到目的网络实体的所有传输路径，可以应用于更多的场景。
可选地，传输路径上的网络实体包括物理实体和逻辑实体。物理实体包括物理设备和/或物理接口。逻辑实体包括逻辑设备、逻辑接口、协议或业务中的一种或多种。
目前确定的传输路径通常只包含物体设备和物理接口等硬件，而本申请确定的传输路径中既包括物理设备和/或物理接口等物理实体，还包括逻辑设备、逻辑接口、协议和/或业务等逻辑实体，该传输路径能够反映源端设备和目的设备通信所采用的协议和业务等，该传输路 径包含的信息更多，便于后期对网络进行分析。
可选地，分析设备确定目标网络的知识图谱上的源网络实体的实现过程，包括：分析设备确定接入目标网络的源端设备和目的设备。分析设备根据源端设备确定源网络实体，并根据目的设备确定目的网络实体。
本申请中，当源网络实体为源端设备对应的网络实体，目的网络实体为目的设备对应的网络实体时，源网络实体到目的网络实体的传输路径也即是源端设备到目的端设备的传输路径，无需依赖于业务报文传输场景确定两个设备之间的传输路径，确定路径的灵活性较高。
可选地，分析设备根据源端设备确定源网络实体的实现过程，包括：分析设备根据源端设备的接入信息确定源网络实体，该源端设备的接入信息中包括源端设备的标识。
可选地，源网络实体为源端设备，或者，源网络实体为目标网络中的第一网络设备的第一接口。第一网络设备的第一接口用于将源端设备接入目标网络。
在一种实现方式中，分析设备根据目的设备确定目的网络实体的实现过程，包括：分析设备根据目的设备的接入信息确定目的网络实体，该目的设备的接入信息中包括目的设备的标识。
可选地，目的网络实体为目的设备，或者，目的网络实体为目标网络中的第二网络设备的第二接口。第二网络设备的第二接口用于将目的设备接入目标网络。
在另一种实现方式中，分析设备根据目的设备确定目的网络实体的实现过程，包括：分析设备获取源端设备的DHCP业务对应的目标VLAN。当目标VLAN与目标二层转发实例具有绑定关系，分析设备确定目的网络实体为目标网络中的核心网络设备上与目标二层转发实例对应的三层虚拟接口。该目标二层转发实例为除VLAN实例以外的任一二层转发实例。当目标VLAN与除VLAN实例以外的其它二层转发实例均不具有绑定关系，分析设备确定目的网络实体为目标网络中的核心网络设备上与目标VLAN对应的VLAN接口。
可选地，源端设备为无线设备。分析设备获取源端设备的DHCP业务对应的目标VLAN的实现过程，包括：分析设备根据源端设备关联的接入点的标识、源端设备所使用的无线电的标识以及源端设备关联的接入点的服务集标识中的一个或多个，确定源端设备对应的业务VLAN，并将源端设备对应的业务VLAN作为目标VLAN。
可选地，分析设备在知识图谱上确定源网络实体到目的网络实体的传输路径的实现过程，包括：分析设备根据源端设备到目的设备所经过的网络，基于知识图谱确定源网络实体到目的网络实体所经过的中间网络实体，源端设备到目的设备所经过的网络包括底层网络。分析设备根据源网络实体到目的网络实体所经过的中间网络实体，确定传输路径，该传输路径上包括源网络实体、目的网络实体以及中间网络实体。
可选地，源端设备到目的设备所经过的网络还包括上层网络，上层网络构建于底层网络之上。上层网络包括覆盖网络和/或CAPWAP网络。
在一种可实现方式中，源端设备接入目标网络的接入方式为有线接入。当目标网络中与源端设备连接的网络设备的接口与目标二层转发实例具有绑定关系，分析设备确定源端设备到目的设备经过覆盖网络。目标二层转发实例为除VLAN实例以外的任一二层转发实例。
该实现方式中，当源端设备到目的设备经过覆盖网络，分析设备确定源端设备到目的设备的传输路径上包括底层网络实体和覆盖网络实体。若覆盖网络运行VXLAN协议，则分析设备确定源端设备与目的设备之间的报文采用VXLAN隧道转发。当源端设备到目的设备不 经过覆盖网络，分析设备确定源端设备到目的设备的传输路径上只包括底层网络实体。
在另一种可实现方式中，源端设备接入目标网络的接入方式为无线接入。当源端设备与目的设备之间的报文类型为管理报文，分析设备确定源端设备到目的设备经过CAPWAP网络。当源端设备与目的设备之间的报文类型为业务报文，该业务报文采用直接转发方式，且该业务报文对应的业务VLAN与目标二层转发实例具有绑定关系，分析设备确定源端设备到目的设备经过覆盖网络。该目标二层转发实例为除VLAN实例以外的任一二层转发实例。当源端设备与目的设备之间的报文类型为业务报文且该业务报文采用隧道转发方式，分析设备确定源端设备到目的设备经过CAPWAP网络。
该实现方式中，分析设备确定源端设备与目的设备之间的管理报文采用CAPWAP隧道转发，该管理报文的传输路径上包括底层网络实体和CAPWAP网络实体。分析设备确定源端设备与目的设备之间采用隧道转发方式的业务报文采用CAPWAP隧道转发，该业务报文的传输路径上包括底层网络实体和CAPWAP网络实体。若源端设备与目的设备之间的业务报文采用直接转发方式，当源端设备到目的设备经过覆盖网络，分析设备确定该业务报文的传输路径上包括底层网络实体和覆盖网络实体；当源端设备到目的设备不经过覆盖网络，分析设备确定该业务报文的传输路径上只包括底层网络实体。业务报文采用隧道转发方式还是隧道转发方式取决于AP的具体配置。
可选地，当源端设备到目的设备所经过的网络包括覆盖网络，分析设备根据源端设备到目的设备所经过的网络，基于知识图谱确定源网络实体到目的网络实体所经过的中间网络实体的实现过程，包括：分析设备根据源端设备到目的设备在覆盖网络中所经过的隧道的隧道端点，在知识图谱上确定隧道对应的覆盖网络实体以及承载该隧道的底层网络实体。
可选地，分析设备确定目标网络中的源端设备和目的设备的实现过程，包括：分析设备根据目标网络中产生的异常事件确定目标网络中的源端设备和目的设备。该异常事件中包括异常业务的接入信息和异常业务的业务类型。异常业务的接入信息包括承载该异常业务的源端设备的接入信息和/或目的设备的接入信息。
本申请中，分析设备可以根据目标网络中产生的异常事件确定源端设备和目的设备，然后基于目标网络的知识图谱生成源端设备到目的设备的传输路径，能够实时确定异常路径，提高目标网络中的故障定位效率。
可选地，目标网络的知识图谱上标识有目标网络中产生异常事件的异常网络实体，分析设备在该知识图谱上确定源网络实体到目的网络实体的传输路径之后，还可以基于该传输路径上的异常网络实体确定异常业务的故障根因。
本申请中，由于分析设备确定的传输路径上标识有异常网络实体，分析设备可以进一步根据故障传播规则确定传输路径上的根因故障网络实体，进而确定异常业务的故障根因，实现端到端的故障根因定位。另外，分析设备根据目标网络中产生的异常事件，在目标网络的知识图谱上确定传输路径后，能够实时检测导致该异常事件产生的目标网络中的故障，故障定位效率较高。
可选地，异常事件的类型包括告警日志、状态变化日志以及异常关键绩效指标中的一个或多个。
可选地，分析设备还可以根据目标网络的网络数据，生成目标网络的知识图谱。该网络数据包括目标网络的组网拓扑以及目标网络中多个网络设备的设备信息。设备信息包括配置 信息。设备信息还可以包括路由信息和/或状态信息。
第二方面，提供了一种路径确定装置。所述装置包括多个功能模块，所述多个功能模块相互作用，实现上述第一方面及其各实施方式中的方法。所述多个功能模块可以基于软件、硬件或软件和硬件的结合实现，且所述多个功能模块可以基于具体实现进行任意组合或分割。
第三方面，提供了一种路径确定装置，包括：处理器和存储器；
所述存储器，用于存储计算机程序，所述计算机程序包括程序指令；
所述处理器，用于调用所述计算机程序，实现如第一方面及其各实施方式中的路径确定方法。
第四方面，提供了一种计算机存储介质，所述计算机存储介质上存储有指令，当所述指令被计算机设备的处理器执行时，实现如第一方面及其各实施方式中的路径确定方法。
第五方面，提供了一种芯片，芯片包括可程序设计逻辑电路和/或程序指令，当芯片运行时，实现上述第一方面及其各实施方式中的方法。
本申请提供的技术方案带来的有益效果至少包括：
本申请中，由于网络的知识图谱由知识图谱三元组构成，通过一个网络实体能够找到与该网络实体具有关系的其它网络实体，因此分析设备在获取知识图谱上的源网络实体和目的网络实体后，可以根据网络实体之间的关系确定源网络实体到目的网络实体的传输路径。当源网络实体为源端设备对应的网络实体，目的网络实体为目的设备对应的网络实体，则源网络实体到目的网络实体的传输路径也即是源端设备到目的端设备的传输路径，本申请在确定两个设备之间的传输路径时，无需依赖于业务报文传输场景，确定路径的灵活性较高。另外，本申请中，通过搜索知识图谱可以找到源网络实体到目的网络实体的所有传输路径，可以应用于更多的场景。进一步地，由于分析设备确定的传输路径上标识有异常网络实体，分析设备可以进一步根据故障传播规则确定传输路径上的根因故障网络实体，进而确定异常业务的故障根因，实现端到端的故障根因定位。另外，分析设备根据目标网络中产生的异常事件，在目标网络的知识图谱上确定传输路径后，能够实时检测导致该异常事件产生的目标网络中的故障，故障定位效率较高。
附图说明
图1是本申请实施例提供的路径确定方法所涉及的应用场景示意图；
图2是本申请实施例提供的一种通信网络的结构示意图；
图3是本申请实施例提供的一种路径确定方法的流程示意图；
图4是本申请实施例提供的一种知识图谱的结构示意图；
图5是本申请实施例提供的另一种知识图谱的结构示意图；
图6是本申请实施例提供的一种路径确定装置的结构示意图；
图7是本申请实施例提供的一种第一确定模块的结构示意图；
图8是本申请实施例提供的另一种路径确定装置的结构示意图；
图9是本申请实施例提供的又一种路径确定装置的结构示意图；
图10是本申请实施例提供的再一种路径确定装置的结构示意图；
图11是本申请实施例提供的还一种路径确定装置的结构示意图；
图12是本申请实施例提供的一种路径确定装置的框图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
图1是本申请实施例提供的路径确定方法所涉及的应用场景示意图。如图1所示，该应用场景中包括：分析设备101以及通信网络中的网络设备102A-102C(统称为网络设备102)。图1中网络设备的数量仅用作示例性说明，不作为对本申请实施例涉及的通信网络的限制。
分析设备101可以是一台服务器，或者由若干台服务器组成的服务器集群，或者是一个云计算服务中心。网络设备102可以是交换机或路由器等实体通信设备，或者也可以是虚拟交换机或虚拟路由器等虚拟通信设备。
可选地，请继续参见图1，该应用场景中还包括控制设备103。该控制设备103用于管理和控制通信网络中的网络设备102。该控制设备103可以是网络控制器，网络管理设备，网关或其它具有控制能力的设备。控制设备103可以是一台或多台设备。分析设备101与控制设备103之间通过有线网络或无线网络连接。控制设备103与网络设备102之间通过有线网络或无线网络连接。
可选地，控制设备103中存储有该控制设备103管理的通信网络的组网拓扑。控制设备103还用于收集通信网络中的网络设备102的设备信息以及通信网络中产生的异常事件等，并向分析设备101提供通信网络的组网拓扑、网络设备102的设备信息以及通信网络中产生的异常事件等。
网络设备102的设备信息至少包括配置信息。网络设备的配置信息具体包括接口配置信息、协议配置信息和/或业务配置信息等。可选地，网络设备102的设备信息还可以包括路由信息和/或状态信息等。网络设备的路由信息具体包括地址解析协议(Address Resolution Protocol，ARP)表、媒体访问控制(Media Access Control，MAC)表、路由表和/或转发表。网络设备的状态信息具体包括协议状态信息和/或隧道状态信息等。其中，协议状态信息包括开放式最短路径优先(open shortest path first，OSPF)协议状态信息、边界网关协议(Border Gateway Protocol，BGP)状态信息和/或链路层发现协议(link layer discovery protocol，LLDP)状态信息等。隧道状态信息包括隧道端点的标识以及隧道的状态。
可选地，控制设备103可以周期性地采集网络设备102的设备信息以及通信网络中产生的异常事件。示例地，控制设备可以采用远程终端协议(简称：telnet)、简单网络管理协议(simple network management protocol，SNMP)或网络遥测(network telemetry)技术采集网络设备的设备信息以及通信网络中产生的异常事件。或者，当网络设备102的设备信息发生变更时，网络设备102主动向控制设备103上报变更后的设备信息；当通信网络发生故障时，网络设备102主动向控制设备103上报产生的异常事件。当然，在一些应用场景中，分析设备101也可以与控制设备103集成，即分析设备101与通信网络中的网络设备102直接连接，本申请实施例对此不做限定。
本申请实施例提供的通信网络可以是数据中心网络(data center network，DCN)、城域网络、广域网络或园区网络等，本申请实施例对通信网络的类型不做限定。该通信网络包括底层(underlay)网络。底层网络可以是由互联网(internet)、多协议标签交换(multi-protocol label switching，MPLS)网络和/或长期演进(long term evolution，LTE)网络等构成的物理网络。底层网络中包括多个网络设备，该多个网络设备之间通过物理链路连接。
可选地，通信网络还可以包括构建于底层网络之上的上层网络，上层网络也可称为逻辑网络或虚拟网络。上层网络可以包括覆盖(overlay)网络和/或无线接入点控制与配置(control and provisioning of wireless access points，CAPWAP)网络。
覆盖网络可以是采用通用路由封装(generic routing encapsulation，GRE)协议、虚拟扩展局域网(virtual extensible local area network，VXLAN)协议、动态智能虚拟专用网(dynamic smart virtual private network，DSVPN)技术和/或自动虚拟专用网(automatic virtual private network，Auto VPN)技术等在底层网络的基础上构建的网络。覆盖网络中包括隧道(也可称为overlay隧道)，该隧道为虚拟的或逻辑的链接。每个隧道对应于底层网络中的一条或多条路径，其中每条路径通常由底层网络中前后衔接的多条物理链路构成。
CAPWAP网络包括CAPWAP隧道。CAPWAP隧道通常建立在接入点(access point，AP)与接入控制器(access controller，AC)之间。CAPWAP隧道分为数据通道和控制通道，数据通道用于传输业务报文(即用户数据报文)，控制通道用于传输管理报文(也称为控制报文)。
本申请实施例提供的通信网络可以采用二层网络架构或三层网络架构。在二层网络架构下，通信网络包括汇聚层和接入层，该通信网络也可称为两层网络，汇聚层是通信网络的高速交换主干，接入层用于将工作站接入通信网络。在三层网络架构下，通信网络包括核心层、汇聚层和接入层，该通信网络也可称为三层网络，核心层是通信网络的高速交换主干，汇聚层用于提供汇聚连接(连接接入层和核心层)，接入层用于将工作站接入通信网络。其中，工作站可以是包括终端、AP、服务器或虚拟机(virtual machine，VM)等。终端可以是手机或电脑等。
示例地，图2是本申请实施例提供的一种通信网络的结构示意图。如图2所示，该通信网络20中包括核心层网络设备102a、汇聚层网络设备102b1-102b2以及接入层网络设备102c1-102c2。接入层网络设备102c1上连接有AP104，AP104与终端105a连接，接入层网络设备102c2上连接有虚拟机105b。
请继续参见图2，接入层网络设备102c1具有接口GE1/0/0.1和接口GE1/1/0，汇聚层网络设备102b1具有接口GE1/2/0和接口GE1/3/0，核心层网络设备102a具有接口GE1/4/0、接口GE1/5/0和接口GE1/6/0，汇聚层网络设备102b2具有接口GE1/7/0和接口GE1/8/0，接入层网络设备102c2具有接口GE1/0/1.1和接口GE1/9/0。其中，接入层网络设备102c1上的接口GE1/0/0.1和接入层网络设备102c2上的接口GE1/0/1.1为边界接口。接入层网络设备102c1通过接口GE1/0/0.1连接AP104，接入层网络设备102c2通过接口GE1/0/1.1连接虚拟机105b。接入层网络设备102c1的接口GE1/1/0与汇聚层网络设备102b1的接口GE1/2/0连接。汇聚层网络设备102b1的接口GE1/3/0与核心层网络设备102a的接口GE1/4/0连接。核心层网络设备102a的接口GE1/6/0与汇聚层网络设备102b2的接口GE1/7/0连接。汇聚层网络设备102b2的接口GE1/8/0与接入层网络设备102c2的接口GE1/9/0连接。
图3是本申请实施例提供的一种路径确定方法的流程示意图。该方法可以应用于如图1所示的应用场景中的分析设备101。如图3所示，该方法包括：
步骤301、获取目标网络的知识图谱。
该知识图谱中包括多个知识图谱三元组。每个知识图谱三元组包括两个网络实体以及该两个网络实体之间的关系。网络实体的类型为设备、接口、协议或业务。
可选地，类型为设备的网络实体可以采用设备的名称、MAC地址、硬件地址、OSPF路由(简称：OsRouter，可以在OSPF层唯一标识网络设备)或其它可唯一标识设备的标识符表示。类型为接口的网络实体可以采用接口的名称表示。类型为协议的网络实体可以采用协议的标识符表示。知识图谱三元组以图的形式表示。知识图谱三元组由点和边两个基本元素构成，点表示网络实体，边表示两个网络实体之间的关联关系。其中，知识图谱三元组中的边可以是有方向的，也可以是无方向的。知识图谱三元组中的边还可以用于表示两个网络实体之间的具体关系，例如依赖关系或对等关系等。示例地，当两个网络实体之间为对等关系时，可以采用无方向的边连接该两个网络实体；当两个网络实体之间为依赖关系时，可以采用有方向的边(例如箭头)连接该两个网络实体，该边的方向由依赖的网络实体指向被依赖的网络实体。
每个网络实体都有各自的配置，例如接口配置有接口状态、接口名称、互联网协议(Internet Protocol，IP)地址和/或是否加入VLAN等属性。网络实体之间根据配置以及物理链路建立关系。以下对网络实体之间的关系进行示例性说明：网络设备具有接口，也即是，接口依赖于网络设备；网络设备的接口上可以承载转发业务，也即是，转发业务依赖于接口；三层转发业务之上可以承载VXLAN隧道、流量工程(traffic engineering，TE)隧道以及BGP，也即是，VXLAN隧道、TE隧道以及BGP依赖于三层转发业务；TE隧道之上可以承载VPN业务，也即是，VPN业务依赖于TE隧道；等等。其中，三层转发业务之上可以承载VXLAN隧道，表示承载有三层转发业务的接口可作为VXLAN隧道的端点；三层转发业务之上可以承载TE隧道，表示承载有三层转发业务的接口可作为TE隧道的端点；三层转发业务之上可以承载BGP，表示承载有三层转发业务的接口可收发基于BGP的协议报文；TE隧道之上可以承载VPN业务，表示承载有TE隧道的接口可支持VPN业务。
可选地，步骤301的实现过程包括：分析设备根据目标网络的网络数据，生成目标网络的知识图谱。该网络数据包括目标网络的组网拓扑以及目标网络中多个网络设备的设备信息。网络设备的设备信息包括配置信息。网络设备的接口配置信息可以包括接口的IP地址、接口支持的协议类型以及接口支持的业务类型等。网络设备的协议配置信息可以包括协议的标识符，协议的标识符用于唯一标识该协议，协议的标识符可以采用字符、字母和/或数字等表示。网络设备的业务配置信息可以包括网络设备使用的业务，例如虚拟专用网络(virtual private network，VPN)业务和/或动态主机配置协议(Dynamic Host Configuration Protocol，DHCP)业务等。网络设备的设备信息还可以包括网络设备的状态信息和/或路由信息等。
可选地，分析设备周期性地获取目标网络中网络设备的设备信息，并生成目标网络的知识图谱。分析设备在生成目标网络的知识图谱后，还可以在该分析设备中或与该分析设备连接的存储设备中存储该目标网络的知识图谱，以便后续使用。例如目标网络的知识图谱可以作为确定网络实体间的故障传播关系的基础，和/或，作为故障根因推理的基础等。示例地，当目标网络在某个周期内发生故障时，分析设备可以在该周期对应的知识图谱上标识出产生 异常事件的异常网络实体，得到标识有异常网络实体的知识图谱，进而提高对标识有异常网络实体的知识图谱的获取效率。
当然，目标网络的知识图谱还可以由其它设备根据目标网络的网络数据生成后发送给分析设备。本申请实施例对此不做限定。
示例地，假设目标网络中包括两个网络设备，分别为网络设备A和网络设备B。网络设备A具有3个接口，该3个接口的名称分别为10GE1/0/1、10GE1/0/2和10GE1/0/3。网络设备B具有4个接口，该4个接口的名称分别为10GE3/0/1、10GE3/0/2、10GE3/0/3和10GE3/0/4。网络设备A和网络设备B均支持OSPF协议。网络设备A中OSPF协议的标识符采用10.89.46.25表示，包括3个路由IP，分别为11.11.11.11、11.11.11.12和11.11.11.13。网络设备B中OSPF协议的标识符采用10.89.49.37表示，包括4个路由IP，分别为11.12.11.11、11.12.11.12、11.12.11.13和11.12.11.14。网络设备A的接口“10GE1/0/2”与网络设备B的接口“10GE3/0/2”连接，且该两个接口之间采用OSPF协议通信，其中，网络设备A的接口“10GE1/0/2”采用的路由IP为11.11.11.11，网络设备B的接口“10GE3/0/2”采用的路由IP为11.12.11.14。则基于上述网络数据可以得到如图4所示的知识图谱。
可选地，目标网络的知识图谱上标识有目标网络中产生异常事件的异常网络实体。异常事件的类型包括告警日志、状态变化日志以及异常关键绩效指标(key performance indicator，KPI)中的一个或多个。告警日志中包括网络设备中异常网络实体的标识以及告警类型。状态变化日志中包括配置文件变化信息和/或路由表项变化信息等，例如状态变化日志中可以包括“接入子接口删除”或“目的IP主机路由删除”等信息。异常KPI用于描述某个网络实体的某种指标出现异常。
示例地，参考如图4所示的例子，假设网络设备A的接口“10GE1/0/2”发生故障，路由IP“11.11.11.11”不通，导致目标网络发生故障时，可以在知识图谱上将接口“10GE1/0/2”对应的网络实体和路由IP“11.11.11.11”对应的网络实体标识为异常网络实体，参见图5，可以通过在异常网络实体上连接异常事件实体，以标识出异常网络实体。异常事件实体可以采用特殊的图形或颜色等区别于网络实体。例如参见图5，可以采用三角形表示异常事件实体。或者，异常事件实体中也可以包括异常事件的具体内容，以便于运维人员基于知识图谱快速获取目标网络中的异常对象以及具体的异常类型。
可选地，目标网络的知识图谱上的网络实体包括物理实体和逻辑实体。物理实体包括物理设备和/或物理接口。逻辑实体包括逻辑设备、逻辑接口、协议或业务中的一种或多种。
示例地，在如图4所示的知识图谱中，物理实体包括物理设备和物理接口，物理设备包括网络设备A和网络设备B，物理接口包括10GE1/0/1、10GE1/0/2、10GE1/0/3、10GE3/0/1、10GE3/0/2、10GE3/0/3和10GE3/0/4。逻辑实体包括协议和逻辑接口，协议包括OSPF10.89.46.25和OSPF 10.89.49.37，逻辑接口采用分配的路由IP表示，逻辑接口包括11.11.11.11、11.11.11.12、11.11.11.13、11.12.11.11、11.12.11.12、11.12.11.13和11.12.11.14。
本申请实施例中，目标网络的知识图谱上可以仅包括目标网络中的网络设备对应的网络实体，或者，目标网络的知识图谱上可以包括目标网络中的网络设备对应的网络实体以及接入目标网络的终端、AP、服务器或虚拟机等对应的网络实体。
步骤302、确定目标网络的知识图谱上的源网络实体和目的网络实体。
可选地，分析设备先确定接入目标网络的源端设备和目的设备，再根据源端设备确定源 网络实体，并根据目的设备确定目的网络实体。以下分别对分析设备根据源端设备确定源网络实体以及根据目的设备确定目的网络实体的实现过程进行说明。
可选地，分析设备可以根据源端设备的接入信息确定源网络实体。该源端设备的接入信息中包括源端设备的标识。源端设备的标识可以是源端设备的MAC地址或IP地址等。
本申请实施例中，当源端设备为有线设备，例如源端设备为服务器或虚拟机等，源端设备与目标网络中的网络设备有线连接以接入目标网络，将源端设备接入目标网络的网络设备可以向分析设备上报该源端设备的接入信息。当源端设备为无线设备，例如源端设备为手机等，源端设备关联至AP，AP与目标网络中的接入层网络设备有线连接以将源端设备接入目标网络，该接入层网络设备或用于管理该AP的AC可以向分析设备上报该源端设备的接入信息。源端设备的接入信息还可以包括将该源端设备接入目标网络的网络设备的接口信息和/或源端设备的五元组信息、三元组信息等。当源端设备为无线设备时，该源端设备的接入信息还可以包括该源端设备关联的AP的标识、该源端设备所使用的无线电的标识或该源端设备关联的AP的服务集标识(service set identifier，SSID)中的一种或多种。
可选地，源网络实体可以是源端设备，或者，源网络实体可以是目标网络中的第一网络设备的第一接口，该第一网络设备的第一接口用于将源端设备接入目标网络。若目标网络的知识图谱上包括源端设备对应的网络实体以及目标网络中的网络设备对应的网络实体，分析设备确定源网络实体为该源端设备。若目标网络的知识图谱上仅包括目标网络中的网络设备对应的网络实体，当源端设备为有线设备，分析设备确定源网络实体为目标网络中与该源端设备连接的网络设备的接口；当源端设备为无线设备，分析设备确定源网络实体为目标网络中与该源端设备所关联的AP连接的网络设备的接口。
本申请实施例中，分析设备根据目的设备确定目的网络实体有以下两种实现方式：
在第一种实现方式中，分析设备可以根据目的设备的接入信息确定目的网络实体。该目的设备的接入信息中包括目的设备的标识。目的网络实体可以是目的设备，或者，目的网络实体可以是目标网络中的第二网络设备的第二接口，该第二网络设备的第二接口用于将目的设备接入目标网络。分析设备获取目的设备的接入信息的方式以及根据目的设备的接入信息确定目的网络实体的实现方式，可以分别参考上述分析设备获取源端设备的接入信息的方式以及根据源端设备的接入信息确定源网络实体的实现方式，本申请实施例在此不再赘述。
在第二种实现方式中，目的设备为DHCP服务器或DHCP中继设备。分析设备可以获取源端设备的DHCP业务对应的目标VLAN。当目标VLAN与目标二层转发实例具有绑定关系，分析设备确定目的网络实体为该目标网络中的核心网络设备上与目标二层转发实例对应的三层虚拟接口。该目标二层转发实例为除VLAN实例以外的任一二层转发实例，例如该目标二层转发实例为桥接域(bridge domain，BD)实例。当目标VLAN与除VLAN实例以外的其它二层转发实例均不具有绑定关系，分析设备确定目的网络实体为目标网络中的核心网络设备上与目标VLAN对应的VLAN接口。其中，VLAN接口也可称为vlanif。
可选地，网络设备中配置有一个或多个转发实例，一个转发实例对应该网络设备上本地有效的一组路由信息。同一网络设备中的各个转发实例独立工作，用于实现路由隔离。网络设备中可以包括二层转发实例(L2VPN实例)和/或三层转发实例(L3VPN实例)。二层转发实例对应该网络设备上的二层路由信息，例如MAC表；三层转发实例对应该网络设备上的三层路由信息，例如转发表。VLAN实例是一种二层转发实例。在VXLAN中，L2VPN实例 也可称为BD实例(对应二层转发域)。L3VPN实例也可称为虚拟路由转发(virtual routing forwarding，VRF)实例(对应三层转发域)。本申请实施例中，目标二层转发实例可以是BD实例，BD实例对应的三层虚拟接口为基于BD的逻辑接口，可简称为vbdif。
示例地，若源端设备的DHCP业务对应的目标VLAN与BD实例具有绑定关系，说明该源端设备的DHCP报文通过VXLAN隧道转发，分析设备可以在核心网络设备上找到对应的BD实例，然后将该BD实例绑定的vbdif作为目的网络实体。若DHCP业务对应的目标VLAN与BD实例不具有绑定关系，说明该源端设备的DHCP报文不通过VXLAN隧道转发，分析设备可以在核心网络设备上找到对应的VLAN实例，然后将该VLAN实例绑定的vlanif作为目的网络实体。当然，若目标网络的知识图谱上包括DHCP服务器或DHCP中继设备，分析设备也可以将与核心网络设备上的二层转发实例绑定的vbdif或vlanif所连接的DHCP服务器或DHCP中继设备作为目的网络实体。
可选地，当源端设备为无线设备，分析设备获取源端设备的DHCP业务对应的目标VLAN的实现过程，包括：分析设备根据源端设备关联的接入点的标识、源端设备所使用的无线电的标识以及源端设备关联的接入点的服务集标识中的一个或多个，确定该源端设备对应的业务VLAN，并将源端设备对应的业务VLAN作为目标VLAN。
可选地，分析设备可以根据目标网络中产生的异常事件确定目标网络中的源端设备和目的设备。该异常事件中包括异常业务的接入信息和异常业务的业务类型。异常业务的接入信息包括承载该异常业务的源端设备的接入信息和/或目的设备的接入信息。异常业务的业务类型包括DHCP业务、关联业务、认证业务或音视频业务等。其中，关联业务和认证业务分别指无线局域网中的终端与AP之间的关联和认证。目标网络中产生的异常事件可以由分析设备根据网络设备和/或AP上报的日志或告警等生成。或者，目标网络中产生的异常事件也可以由外部输入。
示例地，当目标网络中由于OsRouter ID冲突导致无线设备DHCP超时，AP和目标网络中的网络设备会上报无线设备的DHCP异常、OSPF异常等相关日志和告警，分析设备基于这些日志和告警可以生成DHCP超时异常事件。例如，该DHCP超时异常事件可以表示如下：
{“name”:“dhcp-timeout”
“ssid”:“1x-135”,“ap_name”:“AP2”,“sta_mac”:“6480-9915-cd9b”,“radio_id”:“1”}
该异常事件中包含的异常业务的业务类型为DHCP业务，异常原因为DHCP超时。源端设备的MAC地址为6480-9915-cd9b，源端设备所使用的无线电的标识为1，源端设备关联的AP为AP2，源端设备关联的AP的SSID为1x-135。基于该异常事件可知，源端设备为MAC地址为6480-9915-cd9b的终端，目的设备为DHCP服务器或DHCP中继设备。
本申请实施例中，也可以由运维人员直接指定知识图谱上的源网络实体和目的网络实体，或者，也可以由运维人员向分析设备输入源端设备的接入信息供分析设备确定源网络实体和/或由运维人员向分析设备输入目的设备的接入信息供分析设备确定目的网络实体。本申请实施例对分析设备确定目标网络的知识图谱上的源网络实体和目的网络实体的方式不做限定。
步骤303、在目标网络的知识图谱上确定源网络实体到目的网络实体的传输路径。
在目标网络的知识图谱上确定的源网络实体到目的网络实体的传输路径属于该目标网络的知识图谱，即该传输路径为目标网络的知识图谱的子图谱。该传输路径上的网络实体包括物理实体和逻辑实体。源网络实体到目的网络实体的传输路径可以有一条或多条。
目前确定的传输路径通常只包含物体设备和物理接口等硬件，而本申请实施例确定的传输路径中既包括物理设备和/或物理接口等物理实体，还包括逻辑设备(例如逻辑交换机BD、逻辑路由器VPN等)、逻辑接口(例如vlanif、vbdif、网络虚拟化边缘(network virtualization edge，NVE)、LoopBack等)、协议(例如OSPF、BGP等)和/或业务(例如隧道业务，VXLAN隧道、CAPWAP隧道等)等逻辑实体，该传输路径能够反映源端设备和目的设备通信所采用的协议和业务等，该传输路径包含的信息更多，便于后期对网络进行分析。
可选地，步骤303的实现过程包括：分析设备根据源端设备到目的设备所经过的网络，基于目标网络的知识图谱确定源网络实体到目的网络实体所经过的中间网络实体，源端设备到目的设备所经过的网络包括底层网络。然后，分析设备根据源网络实体到目的网络实体所经过的中间网络实体，确定传输路径，该传输路径上包括源网络实体、目的网络实体以及中间网络实体。该传输路径上可以包括分析设备确定的所有中间网络实体。
可选地，源端设备到目的设备所经过的网络还包括上层网络。上层网络包括覆盖网络和/或CAPWAP网络。当源端设备到目的设备所经过的网络包括覆盖网络，分析设备可以根据源端设备到目的设备在覆盖网络中所经过的隧道的隧道端点，在知识图谱上确定该隧道对应的覆盖网络实体以及承载该隧道的底层网络实体。其中，覆盖网络实体指覆盖网络中的对应的网络实体，例如BD实例或vbdif等；底层网络实体指底层网络中对应的网络实体，例如物理设备、物理接口、OSPF或BGP等。
示例地，请参考如图2所示的例子，假设源端设备为终端105a，目的设备为与核心层网络设备102a连接的DHCP服务器(图中未示出)，源端设备到目的设备所经过的覆盖网络运行VXLAN协议。接入层网络设备102c1中配置了VXLAN隧道端点(VXLAN tunnel endpoint，VTEP)1，核心层网络设备102a中配置了VTEP2。接入层网络设备102c1和核心层网络设备102a之间基于VTEP1和VTEP2建立了VXLAN隧道连接。隧道是单向的，通常两个网络设备之间会建立两条方向相反的隧道，以实现双向通信。假设接入层网络设备102c1和核心层网络设备102a中均配置了BD实例。接入层网络设备102c1中的BD实例的标识为10，简称BD10，接入层网络设备102c1中与BD10连接的NVE简称NVE1；核心层网络设备102a中的BD实例的标识为20，简称BD20，核心层网络设备102a中与BD20连接的NVE简称NVE2。分析设备确定知识图谱上该隧道对应的覆盖网络实体包括BD10、NVE1、NVE2和BD20，承载该隧道的底层网络实体包括接入层网络设备102c1、接口GE1/1/0、接口GE1/2/0、汇聚层网络设备102b1、接口GE1/3/0、接口GE1/4/0和核心层网络设备102a。即分析设备可以确定：终端105a到DHCP服务器经过的网络实体包括：接入层网络设备102c1、接口GE1/1/0、接口GE1/2/0、汇聚层网络设备102b1、接口GE1/3/0、接口GE1/4/0和核心层网络设备102a，以及，BD10、NVE1、NVE2和BD20。
可选地，源端设备与目的设备之间的报文可以采用二层转发、三层转发、VXLAN隧道转发或CAPWAP隧道转发等转发模式进行传输，分析设备可以根据目标网络中网络设备的具体配置来确定转发模式。本申请实施例中，分析设备可以基于源端设备接入目标网络的接入方式确定源端设备到目的设备所经过的网络，进一步确定源端设备与目的设备之间的报文的转发模式。
在本申请的一个可选实施例中，源端设备接入目标网络的接入方式为有线接入。当目标网络中与源端设备连接的网络设备的接口与目标二层转发实例具有绑定关系，分析设备确定 源端设备到目的设备经过覆盖网络。当目标网络中与源端设备连接的网络设备的接口与目标二层转发实例不具有绑定关系，分析设备确定源端设备到目的设备不经过覆盖网络。目标二层转发实例为除VLAN实例以外的任一二层转发实例，例如BD实例。
本实施例中，当源端设备到目的设备经过覆盖网络，分析设备确定源端设备到目的设备的传输路径上包括底层网络实体和覆盖网络实体。若覆盖网络运行VXLAN协议，则分析设备确定源端设备与目的设备之间的报文采用VXLAN隧道转发。当源端设备到目的设备不经过覆盖网络，分析设备确定源端设备到目的设备的传输路径上只包括底层网络实体。
在本申请的另一个可选实施例中，源端设备接入目标网络的接入方式为无线接入。当源端设备与目的设备之间的报文类型为管理报文，分析设备确定源端设备到目的设备经过CAPWAP网络。当源端设备与目的设备之间的报文类型为业务报文，该业务报文采用直接转发方式且业务报文对应的业务VLAN与目标二层转发实例具有绑定关系，分析设备确定源端设备到目的设备经过覆盖网络。目标二层转发实例为除VLAN实例以外的任一二层转发实例，例如BD实例。当源端设备与目的设备之间的报文类型为业务报文且该业务报文采用隧道转发方式，分析设备确定源端设备到目的设备经过CAPWAP网络。其中，直接转发也可称为本地转发，隧道转发也可称为集中转发。采用直接转发方式的业务报文不经过CAPWAP隧道，采用隧道转发方式的业务报文经过CAPWAP隧道。
本实施例中，分析设备确定源端设备与目的设备之间的管理报文采用CAPWAP隧道转发，该管理报文的传输路径上包括底层网络实体和CAPWAP网络实体。分析设备确定源端设备与目的设备之间采用隧道转发方式的业务报文采用CAPWAP隧道转发，该业务报文的传输路径上包括底层网络实体和CAPWAP网络实体。若源端设备与目的设备之间的业务报文采用直接转发方式，当源端设备到目的设备经过覆盖网络，分析设备确定该业务报文的传输路径上包括底层网络实体和覆盖网络实体；当源端设备到目的设备不经过覆盖网络，分析设备确定该业务报文的传输路径上只包括底层网络实体。其中，CAPWAP网络实体指CAPWAP网络中对应的网络实体。业务报文采用隧道转发方式还是隧道转发方式取决于AP的具体配置。
本申请实施例中，由于网络的知识图谱由知识图谱三元组构成，通过一个网络实体能够找到与该网络实体具有关系的其它网络实体，因此在获取知识图谱上的源网络实体和目的网络实体后，可以根据网络实体之间的关系确定源网络实体到目的网络实体的传输路径。当源网络实体为源端设备对应的网络实体，目的网络实体为目的设备对应的网络实体，则源网络实体到目的网络实体的传输路径也即是源端设备到目的端设备的传输路径，本申请实施例在确定两个设备之间的传输路径时，无需依赖于业务报文传输场景，确定路径的灵活性较高。另外，本申请实施例中，通过搜索知识图谱可以找到源网络实体到目的网络实体的所有传输路径，可以应用于更多的场景，例如等价多路径(equal-cost multi-path，ECMP)场景，等等。
可选地，当目标网络的知识图谱上标识有目标网络中产生异常事件的异常网络实体，分析设备在目标网络的知识图谱上确定异常事件对应的源网络实体到目的网络实体的传输路径之后，还可以执行下述步骤304。
步骤304、基于源网络实体到目的网络实体的传输路径上的异常网络实体确定异常业务的故障根因。
示例地，分析设备先基于步骤302中的DHCP超时异常事件在目标网络的知识图谱上确定DHCP报文的传输路径，然后基于该传输路径上挂载有异常事件的异常网络实体进行推理， 得到结论：OsRouter ID冲突导致无线设备DHCP超时。
本申请实施例中，由于分析设备确定的传输路径上标识有异常网络实体，分析设备可以进一步根据故障传播规则确定传输路径上的根因故障网络实体，进而确定异常业务的故障根因，实现端到端的故障根因定位。另外，分析设备根据目标网络中产生的异常事件，在目标网络的知识图谱上确定传输路径后，能够实时检测导致该异常事件产生的目标网络中的故障，故障定位效率较高。其中，故障传播规则可以基于专家经验得到。
另外，由于目标网络的知识图谱上的网络实体可以挂载各种相关异常事件，可以利用其它技术，例如iFIT或数据面验证(data plane verification，DPV)等生成质量异常事件和/或表项异常事件等，然后挂载在对应的网络实体上，分析设备生成传输路径后使用推理引擎能够定位更多类型的故障根因，易于扩展。
本申请实施例提供的路径确定方法的步骤先后顺序可以进行适当调整，步骤也可以根据情况进行相应增减。任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化的方法，都应涵盖在本申请的保护范围之内。
综上所述，在本申请实施例提供的路径确定方法中，由于网络的知识图谱由知识图谱三元组构成，通过一个网络实体能够找到与该网络实体具有关系的其它网络实体，因此分析设备在获取知识图谱上的源网络实体和目的网络实体后，可以根据网络实体之间的关系确定源网络实体到目的网络实体的传输路径。当源网络实体为源端设备对应的网络实体，目的网络实体为目的设备对应的网络实体，则源网络实体到目的网络实体的传输路径也即是源端设备到目的端设备的传输路径，本申请实施例在确定两个设备之间的传输路径时，无需依赖于业务报文传输场景，确定路径的灵活性较高。另外，本申请实施例中，通过搜索知识图谱可以找到源网络实体到目的网络实体的所有传输路径，可以应用于更多的场景，例如ECMP场景，等等。进一步地，由于分析设备确定的传输路径上标识有异常网络实体，分析设备可以进一步根据故障传播规则确定传输路径上的根因故障网络实体，进而确定异常业务的故障根因，实现端到端的故障根因定位。另外，分析设备根据目标网络中产生的异常事件，在目标网络的知识图谱上确定传输路径后，能够实时检测导致该异常事件产生的目标网络中的故障，故障定位效率较高。
图6是本申请实施例提供的一种路径确定装置的结构示意图。该装置可以是如图1所示的应用场景中的分析设备101。如图6所示，该装置60包括：
第一确定模块601，用于确定目标网络的知识图谱上的源网络实体和目的网络实体，知识图谱中包括多个知识图谱三元组，每个知识图谱三元组包括两个网络实体以及两个网络实体之间的关系，网络实体的类型为设备、接口、协议或业务。
第二确定模块602，用于在知识图谱上确定源网络实体到目的网络实体的传输路径。
可选地，传输路径上的网络实体包括物理实体和逻辑实体，物理实体包括物理设备和/或物理接口，逻辑实体包括逻辑设备、逻辑接口、协议或业务中的一种或多种。
可选地，第一确定模块601，用于：确定接入目标网络的源端设备和目的设备；根据源端设备确定源网络实体，并根据目的设备确定目的网络实体。
可选地，第一确定模块601，用于：根据源端设备的接入信息确定源网络实体，源端设备的接入信息中包括源端设备的标识。
可选地，源网络实体为源端设备，或者，源网络实体为目标网络中的第一网络设备的第一接口，第一网络设备的第一接口用于将源端设备接入目标网络。
可选地，第一确定模块601，用于：根据目的设备的接入信息确定目的网络实体，目的设备的接入信息中包括目的设备的标识。
可选地，目的网络实体为目的设备，或者，目的网络实体为目标网络中的第二网络设备的第二接口，第二网络设备的第二接口用于将目的设备接入目标网络。
可选地，如图7所示，第一确定模块601，包括：
获取子模块6011，用于获取源端设备的DHCP业务对应的目标VLAN；
确定子模块6012，用于当目标VLAN与目标二层转发实例具有绑定关系，确定目的网络实体为目标网络中的核心网络设备上与目标二层转发实例对应的三层虚拟接口，目标二层转发实例为除VLAN实例以外的任一二层转发实例；该确定子模块6012，还用于当目标VLAN与除VLAN实例以外的其它二层转发实例均不具有绑定关系，确定目的网络实体为目标网络中的核心网络设备上与目标VLAN对应的VLAN接口。
可选地，源端设备为无线设备，获取子模块6011，用于：根据源端设备关联的接入点的标识、源端设备所使用的无线电的标识以及源端设备关联的接入点的服务集标识中的一个或多个，确定源端设备对应的业务VLAN，并将源端设备对应的业务VLAN作为目标VLAN。
可选地，第二确定模块602，用于：根据源端设备到目的设备所经过的网络，基于知识图谱确定源网络实体到目的网络实体所经过的中间网络实体，源端设备到目的设备所经过的网络包括底层网络；根据源网络实体到目的网络实体所经过的中间网络实体，确定传输路径，传输路径上包括源网络实体、目的网络实体以及中间网络实体。
可选地，源端设备到目的设备所经过的网络还包括上层网络，上层网络构建于底层网络之上，上层网络包括覆盖网络和/或CAPWAP网络。
可选地，源端设备接入目标网络的接入方式为有线接入。如图8所示，装置60还包括：
第三确定模块603，用于当目标网络中与源端设备连接的网络设备的接口与目标二层转发实例具有绑定关系，确定源端设备到目的设备经过覆盖网络，目标二层转发实例为除VLAN实例以外的任一二层转发实例。
可选地，源端设备接入目标网络的接入方式为无线接入。如图9所示，装置60还包括：
第四确定模块604，用于当源端设备与目的设备之间的报文类型为管理报文，确定源端设备到目的设备经过CAPWAP网络；该第四确定模块604，还用于当源端设备与目的设备之间的报文类型为业务报文，业务报文采用直接转发方式，且业务报文对应的业务VLAN与目标二层转发实例具有绑定关系，确定源端设备到目的设备经过覆盖网络，目标二层转发实例为除VLAN实例以外的任一二层转发实例；该第四确定模块604，还用于当源端设备与目的设备之间的报文类型为业务报文且业务报文采用隧道转发方式，确定源端设备到目的设备经过CAPWAP网络。
可选地，当源端设备到目的设备所经过的网络包括覆盖网络，第二确定模块602，用于：根据源端设备到目的设备在覆盖网络中所经过的隧道的隧道端点，在知识图谱上确定隧道对应的覆盖网络实体以及承载隧道的底层网络实体。
可选地，第一确定模块601，用于：根据目标网络中产生的异常事件确定目标网络中的源端设备和目的设备，异常事件中包括异常业务的接入信息和异常业务的业务类型，异常业务 的接入信息包括承载异常业务的源端设备的接入信息和/或目的设备的接入信息。
可选地，知识图谱上标识有目标网络中产生异常事件的异常网络实体。如图10所示，装置60还包括：
第五确定模块605，用于在知识图谱上确定源网络实体到目的网络实体的传输路径之后，基于传输路径上的异常网络实体确定异常业务的故障根因。
可选地，异常事件的类型包括告警日志、状态变化日志以及异常关键绩效指标中的一个或多个。
可选地，如图11所示，装置60还包括：
生成模块606，用于根据目标网络的网络数据，生成知识图谱，网络数据包括目标网络的组网拓扑以及目标网络中多个网络设备的设备信息，设备信息包括配置信息。
综上所述，在本申请实施例提供的路径确定装置中，由于网络的知识图谱由知识图谱三元组构成，通过一个网络实体能够找到与该网络实体具有关系的其它网络实体，因此分析设备在通过第一确定模块知识图谱上的源网络实体和目的网络实体后，可以通过第二确定模块根据网络实体之间的关系确定源网络实体到目的网络实体的传输路径。当源网络实体为源端设备对应的网络实体，目的网络实体为目的设备对应的网络实体，则源网络实体到目的网络实体的传输路径也即是源端设备到目的端设备的传输路径，本申请实施例在确定两个设备之间的传输路径时，无需依赖于业务报文传输场景，确定路径的灵活性较高。另外，本申请实施例中，通过搜索知识图谱可以找到源网络实体到目的网络实体的所有传输路径，可以应用于更多的场景，例如ECMP场景，等等。进一步地，由于分析设备确定的传输路径上标识有异常网络实体，分析设备可以进一步根据故障传播规则确定传输路径上的根因故障网络实体，进而确定异常业务的故障根因，实现端到端的故障根因定位。另外，分析设备根据目标网络中产生的异常事件，在目标网络的知识图谱上确定传输路径后，能够实时检测导致该异常事件产生的目标网络中的故障，故障定位效率较高。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
图12是本申请实施例提供的一种路径确定装置的框图。该装置可以是如图1所示的应用场景中的分析设备101。如图12所示，该装置120包括：处理器1201和存储器1202。
存储器1202，用于存储计算机程序，所述计算机程序包括程序指令；
处理器1201，用于调用所述计算机程序，实现上述方法实施例所述的路径确定方法。
可选地，该装置120还包括通信总线1203和通信接口1204。
其中，处理器1201包括一个或者一个以上处理核心，处理器1201通过运行计算机程序，执行各种功能应用以及数据处理。
存储器1202可用于存储计算机程序。可选地，存储器可存储操作系统和至少一个功能所需的应用程序单元。操作系统可以是实时操作系统(Real Time eXecutive，RTX)、LINUX、UNIX、WINDOWS或OS X之类的操作系统。
通信接口1204可以为多个，通信接口1204用于与其它存储设备或网络设备进行通信。
存储器1202与通信接口1204分别通过通信总线1203与处理器1201连接。
本申请实施例还提供了一种计算机存储介质，所述计算机存储介质上存储有指令，当所述指令被计算机设备的处理器执行时，实现上述方法实施例所述的路径确定方法。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
在本申请实施例中，术语“第一”、“第二”和“第三”仅用于描述目的，而不能理解为指示或暗示相对重要性。
本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
以上所述仅为本申请的可选实施例，并不用以限制本申请，凡在本申请的构思和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (38)

  1. 一种路径确定方法，其特征在于，所述方法包括：
    确定目标网络的知识图谱上的源网络实体和目的网络实体，所述知识图谱中包括多个知识图谱三元组，每个所述知识图谱三元组包括两个网络实体以及所述两个网络实体之间的关系，所述网络实体的类型为设备、接口、协议或业务；
    在所述知识图谱上确定所述源网络实体到所述目的网络实体的传输路径。
  2. 根据权利要求1所述的方法，其特征在于，所述传输路径上的网络实体包括物理实体和逻辑实体，所述物理实体包括物理设备和/或物理接口，所述逻辑实体包括逻辑设备、逻辑接口、协议或业务中的一种或多种。
  3. 根据权利要求1或2所述的方法，其特征在于，所述确定目标网络的知识图谱上的源网络实体，包括：
    确定接入所述目标网络的源端设备和目的设备；
    根据所述源端设备确定所述源网络实体，并根据所述目的设备确定所述目的网络实体。
  4. 根据权利要求3所述的方法，其特征在于，所述根据所述源端设备确定所述源网络实体，包括：
    根据所述源端设备的接入信息确定所述源网络实体，所述源端设备的接入信息中包括所述源端设备的标识。
  5. 根据权利要求3或4所述的方法，其特征在于，所述源网络实体为所述源端设备，或者，所述源网络实体为所述目标网络中的第一网络设备的第一接口，所述第一网络设备的所述第一接口用于将所述源端设备接入所述目标网络。
  6. 根据权利要求3至5任一所述的方法，其特征在于，所述根据所述目的设备确定所述目的网络实体，包括：
    根据所述目的设备的接入信息确定所述目的网络实体，所述目的设备的接入信息中包括所述目的设备的标识。
  7. 根据权利要求3至6任一所述的方法，其特征在于，所述目的网络实体为所述目的设备，或者，所述目的网络实体为所述目标网络中的第二网络设备的第二接口，所述第二网络设备的所述第二接口用于将所述目的设备接入所述目标网络。
  8. 根据权利要求3至5任一所述的方法，其特征在于，所述根据所述目的设备确定所述目的网络实体，包括：
    获取所述源端设备的动态主机配置协议DHCP业务对应的目标虚拟局域网VLAN；
    当目标VLAN与目标二层转发实例具有绑定关系，确定所述目的网络实体为所述目标网络中的核心网络设备上与所述目标二层转发实例对应的三层虚拟接口，所述目标二层转发实例为除VLAN实例以外的任一二层转发实例；
    当目标VLAN与除VLAN实例以外的其它二层转发实例均不具有绑定关系，确定所述目的网络实体为所述目标网络中的核心网络设备上与所述目标VLAN对应的VLAN接口。
  9. 根据权利要求8所述的方法，其特征在于，所述源端设备为无线设备，所述获取所述源端设备的DHCP业务对应的目标虚拟局域网VLAN，包括：
    根据所述源端设备关联的接入点的标识、所述源端设备所使用的无线电的标识以及所述源端设备关联的接入点的服务集标识中的一个或多个，确定所述源端设备对应的业务VLAN，并将所述源端设备对应的业务VLAN作为所述目标VLAN。
  10. 根据权利要求3至9任一所述的方法，其特征在于，所述在所述知识图谱上确定所述源网络实体到所述目的网络实体的传输路径，包括：
    根据所述源端设备到所述目的设备所经过的网络，基于所述知识图谱确定所述源网络实体到所述目的网络实体所经过的中间网络实体，所述源端设备到所述目的设备所经过的网络包括底层网络；
    根据所述源网络实体到所述目的网络实体所经过的中间网络实体，确定所述传输路径，所述传输路径上包括所述源网络实体、所述目的网络实体以及所述中间网络实体。
  11. 根据权利要求10所述的方法，其特征在于，所述源端设备到所述目的设备所经过的网络还包括上层网络，所述上层网络构建于所述底层网络之上，所述上层网络包括覆盖网络和/或无线接入点控制与配置CAPWAP网络。
  12. 根据权利要求10或11所述的方法，其特征在于，所述源端设备接入所述目标网络的接入方式为有线接入，所述方法还包括：
    当所述目标网络中与所述源端设备连接的网络设备的接口与目标二层转发实例具有绑定关系，确定所述源端设备到所述目的设备经过覆盖网络，所述目标二层转发实例为除VLAN实例以外的任一二层转发实例。
  13. 根据权利要求10或11所述的方法，其特征在于，所述源端设备接入所述目标网络的接入方式为无线接入，所述方法还包括：
    当所述源端设备与所述目的设备之间的报文类型为管理报文，确定所述源端设备到所述目的设备经过CAPWAP网络；
    当所述源端设备与所述目的设备之间的报文类型为业务报文，所述业务报文采用直接转发方式，且所述业务报文对应的业务VLAN与目标二层转发实例具有绑定关系，确定所述源端设备到所述目的设备经过覆盖网络，所述目标二层转发实例为除VLAN实例以外的任一二层转发实例；
    当所述源端设备与所述目的设备之间的报文类型为业务报文且所述业务报文采用隧道转 发方式，确定所述源端设备到所述目的设备经过CAPWAP网络。
  14. 根据权利要求10至13任一所述的方法，其特征在于，当所述源端设备到所述目的设备所经过的网络包括覆盖网络，所述根据所述源端设备到所述目的设备所经过的网络，基于所述知识图谱确定所述源网络实体到所述目的网络实体所经过的中间网络实体，包括：
    根据所述源端设备到所述目的设备在所述覆盖网络中所经过的隧道的隧道端点，在所述知识图谱上确定所述隧道对应的覆盖网络实体以及承载所述隧道的底层网络实体。
  15. 根据权利要求3至14任一所述的方法，其特征在于，所述确定所述目标网络中的源端设备和目的设备，包括：
    根据所述目标网络中产生的异常事件确定所述目标网络中的源端设备和目的设备，所述异常事件中包括异常业务的接入信息和所述异常业务的业务类型，所述异常业务的接入信息包括承载所述异常业务的源端设备的接入信息和/或目的设备的接入信息。
  16. 根据权利要求15所述的方法，其特征在于，所述知识图谱上标识有所述目标网络中产生异常事件的异常网络实体，在所述知识图谱上确定所述源网络实体到所述目的网络实体的传输路径之后，所述方法还包括：
    基于所述传输路径上的异常网络实体确定所述异常业务的故障根因。
  17. 根据权利要求15或16所述的方法，其特征在于，所述异常事件的类型包括告警日志、状态变化日志以及异常关键绩效指标中的一个或多个。
  18. 根据权利要求1至17任一所述的方法，其特征在于，所述方法还包括：
    根据所述目标网络的网络数据，生成所述知识图谱，所述网络数据包括所述目标网络的组网拓扑以及所述目标网络中多个网络设备的设备信息，所述设备信息包括配置信息。
  19. 一种路径确定装置，其特征在于，所述装置包括：
    第一确定模块，用于确定目标网络的知识图谱上的源网络实体和目的网络实体，所述知识图谱中包括多个知识图谱三元组，每个所述知识图谱三元组包括两个网络实体以及所述两个网络实体之间的关系，所述网络实体的类型为设备、接口、协议或业务；
    第二确定模块，用于在所述知识图谱上确定所述源网络实体到所述目的网络实体的传输路径。
  20. 根据权利要求19所述的装置，其特征在于，所述传输路径上的网络实体包括物理实体和逻辑实体，所述物理实体包括物理设备和/或物理接口，所述逻辑实体包括逻辑设备、逻辑接口、协议或业务中的一种或多种。
  21. 根据权利要求19或20所述的装置，其特征在于，所述第一确定模块，用于：
    确定接入所述目标网络的源端设备和目的设备；
    根据所述源端设备确定所述源网络实体，并根据所述目的设备确定所述目的网络实体。
  22. 根据权利要求21所述的装置，其特征在于，所述第一确定模块，用于：
    根据所述源端设备的接入信息确定所述源网络实体，所述源端设备的接入信息中包括所述源端设备的标识。
  23. 根据权利要求21或22所述的装置，其特征在于，所述源网络实体为所述源端设备，或者，所述源网络实体为所述目标网络中的第一网络设备的第一接口，所述第一网络设备的所述第一接口用于将所述源端设备接入所述目标网络。
  24. 根据权利要求21至23任一所述的装置，其特征在于，所述第一确定模块，用于：
    根据所述目的设备的接入信息确定所述目的网络实体，所述目的设备的接入信息中包括所述目的设备的标识。
  25. 根据权利要求21至24任一所述的装置，其特征在于，所述目的网络实体为所述目的设备，或者，所述目的网络实体为所述目标网络中的第二网络设备的第二接口，所述第二网络设备的所述第二接口用于将所述目的设备接入所述目标网络。
  26. 根据权利要求21至23任一所述的装置，其特征在于，所述第一确定模块，包括：
    获取子模块，用于获取所述源端设备的动态主机配置协议DHCP业务对应的目标虚拟局域网VLAN；
    确定子模块，用于当目标VLAN与目标二层转发实例具有绑定关系，确定所述目的网络实体为所述目标网络中的核心网络设备上与所述目标二层转发实例对应的三层虚拟接口，所述目标二层转发实例为除VLAN实例以外的任一二层转发实例；
    所述确定子模块，还用于当目标VLAN与除VLAN实例以外的其它二层转发实例均不具有绑定关系，确定所述目的网络实体为所述目标网络中的核心网络设备上与所述目标VLAN对应的VLAN接口。
  27. 根据权利要求26所述的装置，其特征在于，所述源端设备为无线设备，所述获取子模块，用于：
    根据所述源端设备关联的接入点的标识、所述源端设备所使用的无线电的标识以及所述源端设备关联的接入点的服务集标识中的一个或多个，确定所述源端设备对应的业务VLAN，并将所述源端设备对应的业务VLAN作为所述目标VLAN。
  28. 根据权利要求21至27任一所述的装置，其特征在于，所述第二确定模块，用于：
    根据所述源端设备到所述目的设备所经过的网络，基于所述知识图谱确定所述源网络实体到所述目的网络实体所经过的中间网络实体，所述源端设备到所述目的设备所经过的网络包括底层网络；
    根据所述源网络实体到所述目的网络实体所经过的中间网络实体，确定所述传输路径， 所述传输路径上包括所述源网络实体、所述目的网络实体以及所述中间网络实体。
  29. 根据权利要求28所述的装置，其特征在于，所述源端设备到所述目的设备所经过的网络还包括上层网络，所述上层网络构建于所述底层网络之上，所述上层网络包括覆盖网络和/或无线接入点控制与配置CAPWAP网络。
  30. 根据权利要求28或29所述的装置，其特征在于，所述源端设备接入所述目标网络的接入方式为有线接入，所述装置还包括：
    第三确定模块，用于当所述目标网络中与所述源端设备连接的网络设备的接口与目标二层转发实例具有绑定关系，确定所述源端设备到所述目的设备经过覆盖网络，所述目标二层转发实例为除VLAN实例以外的任一二层转发实例。
  31. 根据权利要求28或29所述的装置，其特征在于，所述源端设备接入所述目标网络的接入方式为无线接入，所述装置还包括：
    第四确定模块，用于当所述源端设备与所述目的设备之间的报文类型为管理报文，确定所述源端设备到所述目的设备经过CAPWAP网络；
    所述第四确定模块，还用于当所述源端设备与所述目的设备之间的报文类型为业务报文，所述业务报文采用直接转发方式，且所述业务报文对应的业务VLAN与目标二层转发实例具有绑定关系，确定所述源端设备到所述目的设备经过覆盖网络，所述目标二层转发实例为除VLAN实例以外的任一二层转发实例；
    所述第四确定模块，还用于当所述源端设备与所述目的设备之间的报文类型为业务报文且所述业务报文采用隧道转发方式，确定所述源端设备到所述目的设备经过CAPWAP网络。
  32. 根据权利要求28至31任一所述的装置，其特征在于，当所述源端设备到所述目的设备所经过的网络包括覆盖网络，所述第二确定模块，用于：
    根据所述源端设备到所述目的设备在所述覆盖网络中所经过的隧道的隧道端点，在所述知识图谱上确定所述隧道对应的覆盖网络实体以及承载所述隧道的底层网络实体。
  33. 根据权利要求21至32任一所述的装置，其特征在于，所述第一确定模块，用于：
    根据所述目标网络中产生的异常事件确定所述目标网络中的源端设备和目的设备，所述异常事件中包括异常业务的接入信息和所述异常业务的业务类型，所述异常业务的接入信息包括承载所述异常业务的源端设备的接入信息和/或目的设备的接入信息。
  34. 根据权利要求33所述的装置，其特征在于，所述知识图谱上标识有所述目标网络中产生异常事件的异常网络实体，所述装置还包括：
    第五确定模块，用于在所述知识图谱上确定所述源网络实体到所述目的网络实体的传输路径之后，基于所述传输路径上的异常网络实体确定所述异常业务的故障根因。
  35. 根据权利要求33或34所述的装置，其特征在于，所述异常事件的类型包括告警日志、 状态变化日志以及异常关键绩效指标中的一个或多个。
  36. 根据权利要求19至35任一所述的装置，其特征在于，所述装置还包括：
    生成模块，用于根据所述目标网络的网络数据，生成所述知识图谱，所述网络数据包括所述目标网络的组网拓扑以及所述目标网络中多个网络设备的设备信息，所述设备信息包括配置信息。
  37. 一种路径确定装置，其特征在于，包括：处理器和存储器；
    所述存储器，用于存储计算机程序，所述计算机程序包括程序指令；
    所述处理器，用于调用所述计算机程序，实现如权利要求1至18任一所述的路径确定方法。
  38. 一种计算机存储介质，其特征在于，所述计算机存储介质上存储有指令，当所述指令被计算机设备的处理器执行时，实现如权利要求1至18任一所述的路径确定方法。
PCT/CN2021/123326 2020-10-15 2021-10-12 路径确定方法及装置、计算机存储介质 WO2022078338A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21879382.6A EP4216505A4 (en) 2020-10-15 2021-10-12 PATH DETERMINATION METHOD AND APPARATUS, AND COMPUTER STORAGE MEDIUM
US18/300,605 US20230254244A1 (en) 2020-10-15 2023-04-14 Path determining method and apparatus, and computer storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011103339.6 2020-10-15
CN202011103339.6A CN114430355A (zh) 2020-10-15 2020-10-15 路径确定方法及装置、计算机存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/300,605 Continuation US20230254244A1 (en) 2020-10-15 2023-04-14 Path determining method and apparatus, and computer storage medium

Publications (1)

Publication Number Publication Date
WO2022078338A1 true WO2022078338A1 (zh) 2022-04-21

Family

ID=81207723

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/123326 WO2022078338A1 (zh) 2020-10-15 2021-10-12 路径确定方法及装置、计算机存储介质

Country Status (4)

Country Link
US (1) US20230254244A1 (zh)
EP (1) EP4216505A4 (zh)
CN (1) CN114430355A (zh)
WO (1) WO2022078338A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115242885B (zh) * 2022-07-15 2023-10-13 天翼云科技有限公司 云数据中心系统、数据报文传输方法、设备和介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105871612A (zh) * 2016-03-31 2016-08-17 乐视控股（北京）有限公司 Cdn网络的拓扑结构生成器
CN107749803A (zh) * 2017-10-16 2018-03-02 浙江宇视科技有限公司 一种网络拓扑布局方法及装置
CN109347798A (zh) * 2018-09-12 2019-02-15 东软集团股份有限公司 网络安全知识图谱的生成方法、装置、设备及存储介质
CN109922075A (zh) * 2019-03-22 2019-06-21 中国南方电网有限责任公司 网络安全知识图谱构建方法和装置、计算机设备
CN110008288A (zh) * 2019-02-19 2019-07-12 武汉烽火技术服务有限公司 用于网络故障分析的知识图谱库的构建方法及其应用
US20190334778A1 (en) * 2016-11-30 2019-10-31 Nutanix, Inc. Generic access to heterogeneous virtualized entities

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9537749B2 (en) * 2012-06-06 2017-01-03 Tufin Software Technologies Ltd. Method of network connectivity analyses and system thereof
US9270597B2 (en) * 2012-07-10 2016-02-23 Futurewei Technologies, Inc. Representing bandwidth constraints in partially controlled environments

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105871612A (zh) * 2016-03-31 2016-08-17 乐视控股（北京）有限公司 Cdn网络的拓扑结构生成器
US20190334778A1 (en) * 2016-11-30 2019-10-31 Nutanix, Inc. Generic access to heterogeneous virtualized entities
CN107749803A (zh) * 2017-10-16 2018-03-02 浙江宇视科技有限公司 一种网络拓扑布局方法及装置
CN109347798A (zh) * 2018-09-12 2019-02-15 东软集团股份有限公司 网络安全知识图谱的生成方法、装置、设备及存储介质
CN110008288A (zh) * 2019-02-19 2019-07-12 武汉烽火技术服务有限公司 用于网络故障分析的知识图谱库的构建方法及其应用
CN109922075A (zh) * 2019-03-22 2019-06-21 中国南方电网有限责任公司 网络安全知识图谱构建方法和装置、计算机设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4216505A4

Also Published As

Publication number Publication date
US20230254244A1 (en) 2023-08-10
EP4216505A1 (en) 2023-07-26
CN114430355A (zh) 2022-05-03
EP4216505A4 (en) 2023-12-13

Similar Documents

Publication Publication Date Title
EP3188409B1 (en) Oam mechanisms for evpn active-active services
CN107852365B (zh) 用于动态vpn策略模型的方法和装置
EP3301861A1 (en) Evpn designated forwarder state propagation to customer edge devices using connectivity fault management
US11418955B2 (en) System and methods for transit path security assured network slices
EP3223461B1 (en) Communicating network path and status information in multi-homed networks
WO2021047011A1 (zh) 数据处理方法及装置、计算机存储介质
EP3675431A1 (en) Core isolation for logical tunnels stitching multi-homed evpn and l2 circuit
EP3935814B1 (en) Dynamic access network selection based on application orchestration information in an edge cloud system
CN112956158B (zh) 结构数据平面监视
WO2022083563A1 (zh) 链路检测方法、链路检测装置、终端设备和存储介质
WO2014180199A1 (zh) 网络建立的方法及控制设备
US20230254244A1 (en) Path determining method and apparatus, and computer storage medium
CN109495370B (zh) 一种基于vpls的报文传输方法及装置
CN110380966B (zh) 一种发现转发路径的方法及其相关设备
US11784874B2 (en) Bulk discovery of devices behind a network address translation device
CN109768929A (zh) 一种基于vpws的报文传输方法及装置
WO2022053007A1 (zh) 网络可达性验证方法及装置、计算机存储介质
US11943101B2 (en) Joint orchestration for private mobile network
US20240348505A1 (en) Network system, network packet processing method and apparatus, and storage medium
US20240031266A1 (en) Remote reachability checks in a distributed tunnel fabric
WO2020135888A1 (zh) 流量的传输方法及装置，物理拓扑结构
CN114257516A (zh) 网络可达性验证方法及装置、计算机存储介质

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021879382

Country of ref document: EP

Effective date: 20230419

NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 21879382

Country of ref document: EP

Kind code of ref document: A1