WO2018095095A1 - 建立分离路径的方法和装置 - Google Patents

建立分离路径的方法和装置 Download PDF

Info

Publication number
WO2018095095A1
WO2018095095A1 PCT/CN2017/099449 CN2017099449W WO2018095095A1 WO 2018095095 A1 WO2018095095 A1 WO 2018095095A1 CN 2017099449 W CN2017099449 W CN 2017099449W WO 2018095095 A1 WO2018095095 A1 WO 2018095095A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
path
network
intra
cross
Prior art date
Application number
PCT/CN2017/099449
Other languages
English (en)
French (fr)
Inventor
刘凯
胡永健
赵耀
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018095095A1 publication Critical patent/WO2018095095A1/zh

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/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/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • 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/12—Shortest path evaluation
    • H04L45/128—Shortest path evaluation for finding disjoint paths
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]

Definitions

  • the present application relates to the field of communications and, more particularly, to a method and apparatus for calculating a split path.
  • Telecommunications networks are usually composed of a large number of network devices, and the networking scale is very large. Therefore, a telecommunication network constructed by using MultiProtocol Label Switching (MPLS) technology usually divides the network into multiple autonomous domains according to a certain scale.
  • An autonomous domain is a collection of Label Switching Router (LSR) devices.
  • LSR Label Switching Router
  • An LSR device in an autonomous domain runs in a single distributed protocol instance or is managed by a centralized control unit.
  • LSP Label Switch Path
  • the sequential calculation method does not consider the protection path when calculating the working path. Calculating the protection path after the calculation of the working path is completed may result in the failure to calculate the path (also called the topology trap) separated from the node and link of the working path in one domain, resulting in the calculation of the entire cross-domain separation path. .
  • the present application provides a method and apparatus for establishing a separation path, which can solve the problem of calculating a topology trap when a cross-domain separation path is calculated.
  • the present application provides a method of establishing a split path, implemented in a communication system including at least two network domains, the communication system including a high layer controller and at least two lower layer controllers.
  • the mapping between the at least two lower layer controllers and the at least two network domains is a one-to-one correspondence.
  • the method includes the higher layer controller determining a sequence of domains of the at least two network domains that need to pass from the source node to the destination node.
  • Each network domain includes a source boundary node and a sink boundary node.
  • the higher layer controller determines the set of separated path groups within the domain that each network domain in the domain sequence has.
  • the set of split path groups within the domain includes at least one split path group within the domain.
  • the separated path group in each of the intra-separated path groups includes two separate paths within the domain, one of the separated paths in the two domains serves as the intra-domain working path and the other path serves as the intra-domain protection path.
  • each network domain has at least one separated path group in the domain.
  • the high-level controller determines a set of cross-domain separated path groups according to the set of separated path groups in each domain of the domain sequence.
  • the set of cross-domain path groups includes at least one cross-domain separation path group.
  • Each cross-domain separation path group includes one intra-domain separation path group for each network domain.
  • Each cross-domain split path group includes two cross-domain split paths, one of the two cross-domain split paths acts as a cross-domain work path and the other path acts as a cross-domain protection path.
  • a domain sequence is a sequence consisting of multiple domains ordered. Starting from the network domain where the source node is located, each network domain in the domain sequence is sequentially passed, and finally the network domain where the destination node is located is reached. In fact, the source node is the node in the first domain of the domain sequence, and the destination node is the node in the last domain of the domain sequence.
  • the intra-domain separation path group of the network domain when the intra-domain separation path group of the network domain is established, only the boundary node of the network domain is considered.
  • the separation path between nodes inside the network domain can be calculated by the prior art.
  • the prior art has matured for calculating a separate path between nodes within a network domain. This embodiment of the present application does not describe this in detail.
  • the high-level controller when establishing a cross-domain separation path, the high-level controller first determines a domain separation path group of each network domain in the network domain that needs to pass from the source node to the destination node, and sequentially processes the network domain in the domain domain.
  • the separated path groups in the domain are combined to obtain a cross-domain separation path group. Since the separated path group in each domain includes two intra-domain paths, one acts as the intra-domain working path and the other acts as the intra-domain protection path. In other words, the establishment of an intra-domain working path also takes into account the establishment of an intra-domain protection path.
  • each of the inter-domain separation path groups determined according to the intra-domain separation path group includes two inter-domain separation paths, one of which serves as a cross-domain working path and the other path serves as an inter-domain protection path. It can be seen from the process of establishing a cross-domain separation path in the embodiment of the present application that the cross-domain working path and the cross-domain protection path are simultaneously established. Therefore, when the split path is sequentially calculated in the prior art, the cross-domain protection path is established first, and the cross-domain protection path is first established, which may result in the problem that the cross-domain protection path cannot be calculated after the cross-domain working path is completed. .
  • the first network domain in the at least two network domains includes one source boundary node and multiple sink boundary nodes.
  • the first lower layer controller is included in the at least two lower layer controllers.
  • the first lower layer controller is a lower layer controller corresponding to the first network domain.
  • determining, by the upper-layer controller, the set of the separated path groups in the domain that is included in the domain sequence includes: receiving, by the upper-layer controller, the first indication information sent by the first lower-layer controller, and according to the first indication information Instructing to determine a set of separate path groups within the domain of the first network domain.
  • the intra-domain separated path group set of the first network domain includes at least one intra-domain separated path group of the first network domain, and the intra-domain separated path group of the first network domain is a first low-level controller that sets multiple sink boundaries of the first network domain After the nodes are combined to obtain at least one sink boundary node group, the source boundary node of the first network domain and the at least one sink boundary node group are combined one by one.
  • the first network domain herein may be any one of the at least two network domains.
  • the at least two network domains may include one or more first network domains. That is, if the topology of the boundary node of the partial network domain in the at least two network domains is one of the source boundary node and the sink boundary node is multiple, the methods provided in this embodiment may be used to construct the network. A separate path group for the domain.
  • the second network domain in the at least two network domains includes multiple source borders Node and multiple sink boundary nodes.
  • the at least two lower layer controllers include a second lower layer controller.
  • the second lower layer controller is a lower layer controller corresponding to the second network domain.
  • the high-level controller determines the set of the intra-domain separation path group that is included in each of the network domains included in the domain sequence, and the method includes: the high-level controller receives the second indication information sent by the second lower-layer controller, and according to the second indication information, Instructing to determine a set of separate path groups within the domain of the second network domain.
  • the intra-domain separated path group set of the second network domain includes at least one intra-domain separated path group of the second network domain, and the intra-domain separated path group of the second network domain is a second lower layer controller that sets multiple source end boundaries of the second network domain
  • the nodes are combined to obtain at least one source boundary node group, and the plurality of sink boundary nodes of the second network domain are combined to obtain at least one sink boundary node group, and the at least one source boundary is obtained.
  • the node group is combined with the at least one sink boundary node group one by one.
  • the second network domain herein may be any one of the at least two network domains.
  • the at least two network domains may include one or more second network domains. That is, if the topology of the boundary nodes of the plurality of network domains in the at least two network domains is that the source boundary node is multiple and the sink boundary node is multiple, the method provided in this embodiment may be used to construct A separate path group for these network domains.
  • the third network domain in the at least two network domains includes multiple source boundary nodes and one sink boundary node.
  • a third lower layer controller is included in the at least two lower layer controllers.
  • the third lower layer controller is a lower layer controller corresponding to the third network domain.
  • determining, by the high-level controller, the set of the separated path groups in each domain of the domain sequence includes: receiving, by the upper-layer controller, third indication information sent by the third lower-layer controller, and determining, according to the indication of the third indication information, A set of separated path groups within the domain of the third network domain.
  • the intra-domain separated path group set of the third network domain includes at least one intra-domain separated path group of the third network domain, and the intra-domain separated path group of the third network domain is a third lower-layer controller that uses multiple sources of the third network domain.
  • the boundary nodes are combined by two to obtain at least one source-end boundary node group, and then the sink-side boundary node of the third network domain is combined with the at least one source-end boundary node group one by one.
  • first and second in the embodiments of the present application are only for distinguishing different objects, for example, in order to distinguish different network domains, lower layer controllers, and the like. Therefore, the above first network domain, second network domain and third network domain are only three possible topologies as one network domain. That is to say, any one of the network domains in the communication system may be the topology of the first network domain, or the topology of the second network domain, or may be the topology of the third network domain. Based on different topologies, the process of the low-level controller to determine the separation of path groups within the domain is slightly different. For details, see the instructions in the manual.
  • the method further includes: the high-level controller calculates a path cost of each of the cross-domain separated path groups in the set of the cross-domain separated path groups, and determines the cross-domain separated path group with the smallest path cost as The target splits the path group across domains.
  • path cost can also be referred to as path cost.
  • the high-level controller may arbitrarily select a cross-domain separation path group from the cross-domain separation path group set as the target cross-domain separation path group, and use one path with a smaller path cost in the target cross-domain separation path group as the cross-domain. Work path, and another path with a higher path cost as a cross-domain protection path.
  • the high-level controller may also determine the cross-domain separation path group with the smallest path cost in the cross-domain separation path group set as the target cross-domain separation path group. At this time, the target cross-domain separation path group is globally optimal.
  • the high-level controller calculates the path cost of each cross-domain separated path group, and the packet
  • the high-level controller obtains the path cost of the separated path group in each domain of each domain in the domain sequence, where the path cost of the separated path group in each domain of each domain is corresponding to each network domain.
  • the low-level controller is calculated according to the preset working path and the weight of the protection path; the high-level controller calculates the cross-domain separated path group according to the path cost of each separated path group and the preset inter-domain link weight. Path cost.
  • the present application provides a method of establishing a split path, performed in a communication system including at least two network domains.
  • the communication system includes a high layer controller and at least two lower layer controllers.
  • the mapping between the at least two lower layer controllers and the at least two network domains is a one-to-one correspondence.
  • the at least two lower layer controllers include a first lower layer controller corresponding to the first network domain.
  • the first network domain is any one of the at least two network domains.
  • the method includes the first lower layer controller determining a set of separate path groups within the domain of the first network domain.
  • the set of split path groups within the domain includes at least one split path group within the domain.
  • the separated path group in each of the at least one intra-domain separation path group includes two intra-domain separation paths.
  • the first lower layer controller sends, to the upper layer controller, indication information for instructing the upper controller to determine the set of the separated path groups in the domain of the first network domain, so that the upper controller separates the path group set according to the domain of the first network domain and the at least A set of intra-domain separated path groups of other network domains except the first network domain in the two network domains, and a set of cross-domain separated path groups is determined.
  • the cross-domain separation path group set includes at least one cross-domain separation path group.
  • Each cross-domain split path group includes two cross-domain split paths, one of the two cross-domain split paths acts as a cross-domain work path and the other path acts as a cross-domain protection path.
  • the high-level controller when establishing a cross-domain separation path, first determines a domain separation path group of each network domain in the network domain that needs to pass from the source node to the destination node, and sequentially processes the network domain in the domain domain.
  • the separated path groups in the domain are combined to obtain a cross-domain separation path group.
  • the intra-domain separation path group of these network domains is determined by the low-level controller to indicate the high-level controller.
  • the intra-domain separation path group including the two paths is always calculated, and one of the two paths is used as the working path in the domain.
  • the other one acts as a protection path within the domain. That is, the intra-domain working path and the intra-domain protection path are calculated simultaneously.
  • each of the inter-domain separation path groups determined by the high-level controller according to the intra-domain separation path group of each network domain also includes two cross-domain paths, and one of the paths is used as the inter-domain working path and the other path is taken as the other path.
  • Cross-domain protection path It can be seen that the cross-domain working path and the cross-domain protection path are established at the same time, so that the cross-domain working path can be calculated by first establishing the cross-domain working path and then establishing the cross-domain protection path. Once completed, the problem of topology traps for cross-domain protection paths cannot be calculated.
  • the first network domain includes a source boundary node and a plurality of sink boundary nodes. And determining, by the first lower layer controller, the set of the separated path groups in the domain of the first network domain, including: the first lower layer controller combining the plurality of sink boundary nodes of the first network domain to obtain at least one sink boundary node The first lower layer controller combines the source boundary node and the plurality of sink boundary node groups one by one to obtain at least one intra-domain separated path group of the first network domain.
  • the first network domain includes multiple source boundary nodes and multiple sink boundary nodes. And determining, by the first lower layer controller, the at least one intra-domain separation path group of the first network domain, including: the first lower layer controller combining the plurality of source end boundary nodes of the first network domain to obtain at least one source side Defining a node group, and combining the plurality of sink boundary nodes of the first network domain to obtain at least one sink boundary node group; the first lower layer controller is configured by the at least one source boundary node group and the at least one sink The end boundary node groups are combined one by one to obtain at least one intra-domain separation path group of the first network domain.
  • the first network domain includes multiple source boundary nodes and one sink boundary node
  • the first lower layer controller determines at least one intra-domain separation path group of the first network domain, including: a low-level controller combines multiple source-side boundary nodes of the first network domain to obtain at least one source-end boundary node group; the first lower-layer controller associates one sink-end boundary node of the first network domain with the at least one The source boundary node groups are combined one by one to obtain at least one intra-domain separation path group of the first network domain.
  • the method before the first lower layer controller sends the indication information to the upper layer controller, the method further includes: the first lower layer controller calculating a path cost of the separated path group in the at least one domain of the first network domain, The indication information is further used to indicate, by the high-layer controller, a path cost of the separated path group in the at least one domain according to the first network domain, and each of the at least two network domains except the first network domain.
  • the path cost of the separated path group in at least one domain of the network domain, and the cross-domain separation path group with the smallest path cost is determined as the target cross-domain separated path group.
  • the first low-level controller calculates a path cost of the separated path group in the at least one domain of the first network domain, and specifically includes: the weight of the first low-level controller according to the preset working path and the protection path, Calculating a path cost of the separated path group in each of the separated path groups in the at least one intra-domain of the first network domain.
  • the first lower layer controller calculates the path cost of the separated path within each domain of the first network domain and indicates the result of the calculated path cost to the higher layer controller. Therefore, the high-level controller can combine the path cost of the separated path group in at least one domain of each network domain, and combine the cross-domain separation path group with the smallest path cost, and use the cross-domain separation path group with the minimum path cost as the target cross-domain. Separate path groups. At this time, the target cross-domain separation path group is globally optimal. Thus, path overhead can be saved and costs can be reduced.
  • the present application provides an apparatus for establishing a cross-domain separation path for performing the method of the first aspect or any possible implementation of the first aspect.
  • the apparatus comprises means for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • the present application provides an apparatus for establishing a cross-domain separation path for performing the method in any of the possible implementations of the second aspect or the second aspect.
  • the apparatus comprises means for performing the method of any of the second aspect or any of the possible implementations of the second aspect.
  • the application provides a network device, the network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program from the memory.
  • the processor performs the method of any of the above-described first aspects or any of the possible implementations of the first aspect.
  • the application provides a network device, the network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program from the memory.
  • the processor performs the method of any of the above-described second aspect or any of the possible implementations of the second aspect when the program is executed.
  • the present application provides a communication system comprising the apparatus of the third aspect and the apparatus of the fourth aspect.
  • the present application provides a communication system, including the network device of the fifth aspect and the network device of the sixth aspect.
  • the present application provides a computer readable medium for storing a computer program, the computer
  • the program includes instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • the present application provides a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the second aspect or the second aspect of the second aspect.
  • the high-level controller when establishing a cross-domain separation path, the high-level controller first determines a domain separation path group of each network domain in the network domain that needs to pass from the source node to the destination node, and sequentially processes the network domain in the domain domain.
  • the separated path groups in the domain are combined to obtain a cross-domain separation path group. Since the separated path group in each domain includes two intra-domain paths, one acts as the intra-domain working path and the other acts as the intra-domain protection path. Therefore, each of the inter-domain separation path groups determined according to the intra-domain separation path group includes two inter-domain separation paths, one of which serves as a cross-domain working path and the other path serves as an inter-domain protection path.
  • the cross-domain working path and the cross-domain protection path are established at the same time, so that the cross-domain working path can be calculated by first establishing the cross-domain working path and then establishing the cross-domain protection path. Once completed, the problem of topology traps for cross-domain protection paths cannot be calculated.
  • FIG. 1 shows an architectural diagram of a tiered deployed MPLS network in the prior art.
  • FIG. 2 shows a working LSP path and a protection LSP path following path separation in the prior art.
  • Figure 3 is a schematic diagram of a network topology.
  • FIG. 4 is a schematic flowchart of a method for establishing a cross-domain separation path according to an embodiment of the present application.
  • Figure 5 is an example of a topology of a path separation group within an intra-domain.
  • Figure 6 is an example of a topology of a path separation group within an intra-domain.
  • FIG. 7 is a centralized control network structure suitable for hierarchical deployment in the embodiment of the present application.
  • FIG. 8 is a schematic diagram of an apparatus 400 for establishing a separation path according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of an apparatus 500 for establishing a separation path according to another embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of an apparatus 600 for establishing a separation path according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of an apparatus 700 for establishing a separation path according to another embodiment of the present application.
  • Multi-Protocol Label Switching is a technology that uses tags for data forwarding.
  • MPLS Multi-Protocol Label Switching
  • LSP Label Switch Path
  • MPLS networks typically include both distributed control MPLS networks and centralized control MPLS networks.
  • a telecommunications network is usually composed of a large number of network devices. Whether distributed or centralized, the network size supported by a single example is limited. Therefore, a telecommunication network constructed by using MPLS technology usually divides the network into multiple autonomous domains according to a certain scale.
  • An autonomous domain is a collection of LSR devices.
  • An LSR device in a domain runs in a single distributed protocol instance or is managed by a centralized control unit. In the case where the network is divided into multiple autonomous domains, one LSP connection usually needs to run through multiple MPLS autonomous domains.
  • FIG. 1 shows an architectural diagram of a tiered deployed MPLS network in the prior art.
  • a single domain controller such as controller A and controller B in FIG. 1 directly interacts with an LSR in an MPLS network to implement centralized control of a single domain.
  • the high-level controller (such as controller AB in Figure 1) interacts with the low-level single-domain controller to complete coordinated control of multiple domains.
  • controller A and controller B in Figure 1 are Lever 0 layers, and high-level controller AB is Lever 1 layer.
  • the telecommunication network built with MPLS technology has very high requirements for service reliability. In the case of equipment and fiber failure, the service needs to be quickly protected and restored. The general recovery time is required to be within 50ms.
  • path separation means that the working path and the protection path pass through different nodes and links.
  • FIG. 2 shows a working LSP path and a protection LSP path following the path separation principle in the prior art.
  • the networking topology includes two network domains (for example, domain A and domain B).
  • the working LSP and the protection LSP run through domain A and domain B, respectively.
  • the working LSP and the protection LSP are respectively distributed on different links, and the nodes on the link do not overlap.
  • a sequential path computation method is proposed in the prior art to calculate a working path and a protection path that follow the path separation principle.
  • the main idea of the sequential path calculation method is to first establish a working LSP path. Then, in the case of excluding the working LSP path, a protection LSP path separated from the working LSP path is established.
  • the specific establishment process is as follows:
  • the method for establishing a single LSP path is mature.
  • the calculation and establishment of the LSP path can be realized through hierarchical calculation and coordination between the centralized control units of the hierarchical deployment.
  • the sequential calculation method establishes the first path (for example, the working path), the requirement of the second path (for example, the protection path) is not considered. Therefore, in many network topologies, the sequential calculation method cannot guarantee the calculation of the working LSP path and the protection LSP path that follow the path separation. Or, after the working LSP path is calculated, the protected LSP path cannot be calculated.
  • Figure 3 is a schematic diagram of a network topology.
  • node A and node Z are a source node and a destination node (or, respectively, a sink node).
  • the calculated optimal working path is A-B-F-H-J-Z.
  • the method for establishing a cross-domain separation path is applied to a centralized control mode network, including but not limited to an MPLS network.
  • the method for calculating the cross-domain separation path in the embodiment of the present application may also be used to calculate a cross-domain separation path, for example, a Synchronous Digital Hierarchy (SDH) VC connection and an optical transmission network.
  • SDH Synchronous Digital Hierarchy
  • Optical channel data unit connection in (Optical Transport Network, OTN), wavelength connection in WDN, and the like Optical Transport Network, OTN
  • the separation path (including the intra-domain separation path and the cross-domain separation path described later) in the embodiment of the present application is different from the separation path mentioned in the prior art.
  • the two cross-domain separation paths established according to the embodiment of the present application ie, The cross-domain working path and the cross-domain protection path do not pass through the same node, that is, the two cross-domain separation paths are strictly separated.
  • the two cross-domain separation paths established according to the embodiment of the present application pass through the same node (ie, two A cross-domain separation path passes through only one source boundary node or only one sink boundary node of the network domain. Therefore, in the embodiment of the present application, when at least two network domains that need to pass from the source node to the destination node have a source end boundary node of only a part of the network domain, only one or a sink boundary node is only one, the upper layer control The cross-domain separation path ultimately established by the device is not strictly separated.
  • the method for establishing a cross-domain separation path does not have any limitation on the topology of the multi-domain network. That is to say, regardless of the actual topology of the multi-domain network, according to the embodiment of the present application, two separate paths across domains can be calculated. Although, under certain topologies, the two calculated cross-domain separation paths are not strictly separated (ie, may pass through the same node). However, the performance of the algorithm is improved compared to the prior art in which it is not possible to calculate a cross-domain separation path.
  • FIG. 4 is a schematic flowchart of a method 200 for establishing a separation path according to an embodiment of the present application. It should be understood that the method 200 can be performed by a higher level controller in a centralized control network. More specifically, it can be executed by a processor configured in a higher layer controller. As shown in FIG. 4, the method mainly includes steps 210-230.
  • the high-level controller determines a domain sequence formed by the network domain that the source node needs to pass to reach the destination node.
  • the domain sequence includes at least two network domains, where each network domain includes a source boundary node and a sink boundary node.
  • the domain sequence herein is a sequence consisting of multiple domains ordered. Starting from the network domain where the source node is located, each network domain in the domain sequence is sequentially passed, and finally the network domain where the destination node is located is reached. In fact, the source node is the node in the first domain of the domain sequence, and the destination node is the node in the last domain of the domain sequence.
  • the domain sequence may be preset. In other words, which network domain needs to go from the source node to the destination node, which can be specified by the user.
  • the domain sequence may also be generated by the high-level controller automatically performing calculation according to the cross-domain topology relationship.
  • connection relationship between the network domains can be specified (or preset) by the user.
  • connection relationship between the network domains can also be automatically discovered by the higher layer controller based on a protocol between the network domains.
  • the high-level controller determines a set of intra-domain separated path groups included in each network domain included in the domain sequence, where the separated path group set includes at least one intra-domain separated path group, and each separated path group includes two separate paths within the domain.
  • One of the separated paths in the two domains serves as an intra-domain working path and the other path serves as an intra-domain protection path, wherein each network domain has at least one separated path group.
  • the high-level controller may determine, by using the indication information that is sent by the lower-layer controller corresponding to each network domain to indicate the intra-domain separated path group set of each network domain, to determine each network domain included in the domain sequence.
  • a collection of separated path groups within a domain may be determined, by using the indication information that is sent by the lower-layer controller corresponding to each network domain to indicate the intra-domain separated path group set of each network domain, to determine each network domain included in the domain sequence.
  • the intra-domain separated path group of each network domain is calculated by the lower layer controller corresponding to the network domain.
  • the specific calculation method is different according to the topology structure of the network domain boundary node.
  • the topological sub-sections of the network domain boundary nodes can be three cases (for convenience of explanation, the following are respectively referred to as Case 1, Case 2, and Case 3).
  • the separated path group in each domain contains two separate paths within the domain (hereinafter referred to as path 1 and path 2 respectively), and the source end boundary nodes of the separated paths in the two domains are the same and the sink boundary nodes are different. .
  • the first network domain in the at least two network domains includes a source boundary node and a plurality of sink boundary nodes, where the at least two lower layer controllers include a first lower layer controller,
  • the first lower layer controller is a lower layer controller corresponding to the first network domain,
  • the high-level controller determines the set of the separated path groups in the domain that each of the network domains included in the domain sequence has, including:
  • the high-level controller receives the first indication information sent by the first lower-layer controller, and determines, according to the indication of the first indication information, the intra-domain separation path group set of the first network domain, where the intra-domain separation path group set of the first network domain includes the first Separating a path group in at least one domain of the network, the intra-domain separation path group of the first network domain is a first low-level controller combining two plurality of sink boundary nodes of the first network domain to obtain a plurality of sink boundary node groups And combining the source boundary node of the first network domain and the plurality of sink boundary node groups one by one.
  • the lower layer controller corresponding to the network domain ie, the first lower layer controller
  • the sink boundary nodes are first combined to form a multi-pair border node group, and then the source boundary node and all the "sink-end boundary node groups" are combined to obtain multiple pairs of the network domain. Separate path groups within the domain.
  • the low-level controller after the low-level controller calculates the at least one intra-domain separated path group of the corresponding network domain, the low-level controller sends the indication information indicating the intra-domain separated path group set of the corresponding network domain to the high-layer controller.
  • the set of separated path groups in the domain includes at least one of the intra-domain separated path groups of the corresponding network domain. That is, the lower layer controller may not inform the upper layer server of all the intra-domain separation groups of the corresponding corresponding network domains.
  • Figure 5 is an example of a topology of a split path group.
  • node A is the source boundary node of domain A
  • nodes B1, B2, and B3 are the sink boundary nodes of domain A.
  • the topology shown in FIG. 5 is generally used for a service access domain
  • node A is an LSP access node
  • nodes B1, B2, and B3 are cross-domain nodes.
  • the lower layer controller corresponding to the domain A first combines the nodes B1, B2, and B3 to form three types of sink boundary node groups (B1, B2), (B1, B3), and (B2, B3). Then combine the source boundary node with the three sink boundary node groups to form [A-(B1, B2)], [A-(B1, B3)], [A-(B2, B3)].
  • sink boundary node groups B1, B2), (B1, B3), and (B2, B3).
  • the separated path group in each domain also contains two separate paths within the domain. Different from Case 1, the source boundary nodes of the paths in the two domains are different, and the boundary nodes of the sink are different.
  • the second network domain in the at least two network domains includes multiple source boundary nodes and multiple sink boundary nodes
  • the at least two lower layer controllers include a second lower layer controller.
  • the second lower layer controller is a lower layer controller corresponding to the second network domain
  • the high-level controller determines the set of the separated path groups in the domain that each of the network domains included in the domain sequence has, including:
  • the high-level controller receives the second indication information sent by the second lower-layer controller, and determines, according to the indication of the second indication information, the intra-domain separation path group set of the second network domain, where the intra-domain separation path group set of the second network domain includes the second Separating the path group in at least one domain of the network domain, and separating the path group in the domain of the second network domain, the second lower layer controller combining the plurality of source boundary nodes of the second network domain to obtain at least one source boundary node group And combining the plurality of sink boundary nodes of the second network domain to obtain at least one sink boundary node group, and performing the at least one source boundary node group and the at least one sink boundary node group one by one Combined.
  • the lower layer controller corresponding to the network domain calculates the path group in the domain of the network domain, and the lower layer The controller (ie, the second lower layer controller) first combines the source boundary nodes in pairs to form at least one source boundary node group (ie, a combination of source boundary nodes). At the same time, the lower layer controller combines the sink boundary nodes in pairs to form at least one sink boundary node group (ie, a combination of sink boundary nodes). Finally, the lower layer controller combines the at least one source boundary node group and the at least one sink boundary node group to obtain at least one intra-domain separation path group of the network domain.
  • Figure 6 is an example of another topology of a split path group.
  • nodes C1, C2, and C3 are source boundary nodes of domain B
  • nodes D1, D2, and D3 are sink boundary nodes of domain B.
  • the lower layer controller corresponding to the domain B first combines the source boundary nodes C1, C2, and C3 to obtain the source boundary node groups, which are (C1, C2), (C1, C3), and (C2, C3), respectively.
  • D1, D2, and D3 are combined to obtain a set of sink boundary nodes, which are (D1, D2), (D1, D3), (D2, D3).
  • the lower layer controller corresponding to the domain B combines the source boundary node group and the sink boundary node group to obtain the domain separated path group of the domain B.
  • n is an integer greater than or equal to 2
  • m is an integer greater than or equal to 2.
  • the number of separated path groups in the domain B obtained is:
  • the process of the lower layer controller calculating the intra-domain separation path of the corresponding network domain is similar to that of case 1. That is, the low-level controller first combines the plurality of source-end boundary nodes to obtain at least one source-end boundary node group, and then combines the sink-side boundary node and the source-end boundary node group one by one to obtain at least one intra-domain separation path. group.
  • Each low-level controller calculates at least one intra-domain separated path group of the corresponding network domain according to the topology of the corresponding network domain boundary node according to the method in the foregoing three cases, and sends the separated path group to the high-level controller after the calculation is completed.
  • the indication information is used to indicate to the high layer controller the separated path group in the at least one domain.
  • the high-level controller receives the indication information sent by each lower-layer controller, and determines, according to the indication of the indication information, a set of intra-domain separation path groups of each network domain corresponding to each lower-layer controller, within the domain of each network domain.
  • the set of split path groups includes at least one intra-path split path group of the network domain.
  • the higher layer controller obtains at least one intra-domain separated path group for each of the network domains in the domain sequence.
  • the manner in which the lower layer controller transmits the indication information to the higher layer controller is not particularly limited.
  • the low-level controller can send a Simple Network Management Protocol (SNMP) message, a Socket protocol message, and a Transmission Control Protocol (TCP) protocol message to the high-level controller to the upper-layer controller.
  • SNMP Simple Network Management Protocol
  • TCP Transmission Control Protocol
  • the higher layer controller sends indication information indicating the separated path group in the domain.
  • the lower layer controller carries the indication information in an SNMP message.
  • the indication information may indicate two identification sequences. Each identification sequence consists of at least two device identifications. Each device identifier in each identifier sequence is used to identify a device, and the device identifiers in each identifier sequence respectively identify devices (or nodes) in which the separated paths in the domain pass sequentially.
  • the indication information also includes interface information between the devices.
  • the high-level controller receives the SNMP message sent by the low-level controller, and obtains the indication information from the SNMP message. Based on the indication information, the high-level controller can determine the sequence according to the sequence of the device identification in each identification sequence and the interface information between the devices. A separate path group within the domain that the network domain has.
  • the high-level controller determines, according to the intra-domain separated path group set that each network domain included in the domain sequence has, a cross-domain separated path group set, where the cross-domain separated path group set includes at least one cross-domain separated path group, and each The cross-domain separated path group includes one intra-domain separated path group of each network domain, and each cross-domain separated path group includes two inter-domain separated paths, and one of the two inter-domain separated paths serves as a cross-domain working path and The other path acts as a cross-domain protection path.
  • the cross-domain working path and the cross-domain protection path are two paths that are separated from each other and sequentially run through each of the domain sequences. According to the calculation of step 220, a separate path group in each domain is obtained.
  • an intra-domain separated path group is selected from a plurality of intra-domain separated path groups of each network domain to be combined to obtain a cross-domain separated path group set, where the cross-domain separated path group set includes multiple crosses. Domain separation path group.
  • the intra-domain separated path group included in each of the combined cross-domain separated path groups corresponds to the network domain in the domain sequence, and the separated path group in each domain is separated in at least one domain of the corresponding network domain.
  • One of the path groups is easy to understand that the intra-domain separated path group included in each of the combined cross-domain separated path groups corresponds to the network domain in the domain sequence, and the separated path group in each domain is separated in at least one domain of the corresponding network domain.
  • the high-level controller when establishing the cross-domain separation path, the high-level controller first determines the intra-domain separation path group of each network domain in the network domain that needs to pass from the source node to the destination node. Then, the intra-domain separated path groups of these network domains are combined in order to obtain a cross-domain separated path group. Since the separated path group in each domain includes two intra-domain paths, one acts as the intra-domain working path and the other acts as the intra-domain protection path. In other words, the establishment of an intra-domain working path also takes into account the establishment of an intra-domain protection path.
  • each of the inter-domain separation path groups determined according to the intra-domain separation path group includes two inter-domain separation paths, one of which serves as a cross-domain working path and the other path serves as an inter-domain protection path.
  • the cross-domain working path and the cross-domain protection path are simultaneously established, so that the cross-domain working path is first established when the separate path is calculated in the prior art. After the cross-domain protection path is calculated, the problem of the topology trap of the cross-domain protection path cannot be calculated.
  • the method further includes:
  • the high-level controller calculates the path cost of each cross-domain separated path group in the set of cross-domain separated path groups, and determines the cross-domain separated path group with the smallest path cost as the target cross-domain separated path group.
  • the high-level controller determines (or calculates) a cross-domain separation group set, and the cross-domain separation path group set includes at least one cross-domain separation path group, each of which The cross-domain separation path group actually includes two cross-domain separation paths. Therefore, one cross-domain separated path group may be arbitrarily selected from the at least two cross-domain separated path groups determined in step 230, and one cross-domain working path in the selected cross-domain separated path group is used as the cross-domain working path, and A cross-domain path acts as a cross-domain protection path.
  • the cross-domain separated path group with the smallest path cost is selected from the cross-domain separated path group set as the target cross-domain separated path group according to the path cost.
  • one cross-domain path with a smaller path cost in the target cross-domain separated path group may be used as the cross-domain working path, and another cross-domain path with a larger path cost as the cross-domain protection path.
  • the high-level controller acquires each domain of each network domain in the domain sequence.
  • the path cost of the separated path group wherein the path cost of the separated path group in each domain of each network domain is calculated according to the weight of the preset working path and the protection path of the lower layer controller corresponding to each network domain. ;
  • the high-level controller calculates the path cost of each cross-domain separated path group according to the path cost of each separated path group and the preset inter-domain link weight.
  • the lower layer controller sends the indication information for indicating the separated path group in the domain to the upper layer controller, and the lower layer controller may send the SNMP protocol message, the Socket protocol message, and the TCP protocol message to the upper layer controller. Report the path cost of the separated path group in the domain to the upper controller.
  • the SNMP protocol message, the Socket protocol message, or the TCP protocol message carries information indicating a path cost of the intra-domain separation path group of the network domain corresponding to the lower layer controller.
  • the indication information includes information of multiple path costs.
  • the low-level controller can report the path cost of the separated path group in all the domains to the upper-layer controller, and can also report the path cost of the separated path group in the partial-domain with less path cost to the higher-layer controller.
  • the high-level controller when determining the target cross-domain separation path group, the high-level controller combines the path cost of the separated path group in each domain of the network domain, the path cost of the pre-domain separated path group, and the inter-domain link. The weight of the cost is calculated.
  • the calculation of the path cost of the lower layer controller for the separated path groups [C1-D1, C2-D2] in the domain may roughly include the following process:
  • Cost[C1-D1] (1) Calculate the path cost of the node C1 to the node D1, which is hereinafter referred to as Cost[C1-D1].
  • Cost[C2-D2] Calculate the path cost of the node C2 to the node D2, which is hereinafter referred to as Cost[C2-D2].
  • one path with a small path cost is determined as the working path in the domain, and the other path with a large path cost is determined as the intra-domain. Protection path.
  • the path cost of the separated path group in the domain the path cost of the working path in the domain ⁇ the path cost weight of the working path in the domain k + the path cost of the protected path in the domain ⁇ the path cost weight j of the protected path in the domain.
  • path cost weight of the working path in the domain and the path cost weight of the protection path in the domain may be specified by the user (or preset).
  • the path cost of the cross-domain separation path is calculated based on the path cost of the separate path in the domain of each network domain determined by each lower layer controller.
  • the path cost weight of the inter-domain link and the weight of the network domain can be specified (or preset) by the user.
  • the method for calculating the cross-domain separation path in the embodiment of the present application is applicable to a hierarchically deployed centralized control network system, and is used to establish two label switched paths (LSPs) separated by multiple network domains. .
  • LSPs label switched paths
  • the method for establishing a cross-domain separation path can ensure that the established cross-domain separation path is globally optimal.
  • FIG. 7 is a hierarchically controlled centralized network system suitable for use in embodiments of the present application.
  • the network system is deployed in two layers, denoted as Layer 1 and Layer 0 (L1 and L0, respectively, as shown in the figure).
  • the controller A is a high-level controller
  • the controller B, the controller C, the controller D, and the controller E are low-level controllers.
  • Controller B, controller C, controller D, and controller manage and control domain 1, domain 2, domain 3, and domain 4, respectively.
  • the low-level controller and the high-level controller realize the cooperative management and control of the entire network system through interaction.
  • the lower layer controller (controller B, controller C, controller D, and controller E as shown in the figure) generates routing information within the respective domains.
  • the high-level controller forms the relationship between the inter-domain boundary nodes in a manually specified manner to generate cross-domain routing information.
  • the cross-domain abstract topology includes a connection relationship between domain boundary nodes, wherein the cross-domain boundary point connection relationship may be specified by a user, or may be automatically discovered by a high-level controller based on a protocol between network domains.
  • the controller A sends a request message to the lower layer controller according to the domain that the LSP passes and the boundary node of the domain and the neighboring domain, and the request message is used to request the lower layer controller to calculate the intra-domain separated path group of the corresponding network domain.
  • the low layer controller receives the request message sent by the high layer controller, and determines at least one intra-path separation path group of the corresponding network domain.
  • each lower layer controller calculates a path cost of all intra-domain separated path groups of respective corresponding network domains. After the calculation is completed, the high-level controller A is sent information including the working channel cost of the path separation group in the domain, the protection channel cost, and the path cost of the path separation group in the domain.
  • the high-level controller A After the high-level controller A receives the indication information sent by each lower-layer controller for indicating the path cost of the at least one intra-path separation path group of each corresponding network domain, according to the indication of the indication information and the cross-domain boundary section
  • the connection relationship of the points is combined to obtain multiple cross-domain separated path groups (that is, the end-to-end separated LSP path group), that is, a cross-domain separated path group set is obtained.
  • the higher layer controller then calculates the path cost for each cross-domain separation path group.
  • the high-level controller may arbitrarily select a cross-domain separation path group from the cross-domain separation path group set as the target cross-domain separation path group, and use one path with a smaller path cost in the target cross-domain separation path group as the cross-domain. Work path, and another path with a higher path cost as a cross-domain protection path.
  • the high-level controller A selects the cross-domain separated path group with the smallest path cost as the target cross-domain path separation group by comparing the path costs of all the cross-domain separated path groups.
  • the target cross-domain separation path group is globally optimal.
  • the high-level controller A delivers the intra-domain path in the selected optimal cross-domain separation path group to the corresponding lower-layer controller, and the low-level controller completes the establishment of the cross-domain separation path.
  • the layer-by-layer abstraction referred to herein refers to the topology of the network managed by the lower layer controller, and abstracts the high-level controller into a network topology abstraction including only inter-domain nodes.
  • the L0 layer controller abstracts the L0 layer network into a domain boundary point connection relationship to the L1 layer control unit.
  • the L1 layer controller abstracts the L1 layer network into a domain boundary point connection relationship to the L2 layer controller and the like.
  • the method for establishing a separate path in the embodiment of the present application can solve the problem of calculating the cross-domain protection path and then establishing the cross-domain protection path by calculating the cross-domain protection path in the existing solution by simultaneously calculating the cross-domain working path and the cross-domain protection path.
  • a cross-domain protection path that may be caused by a problem that cannot be calculated for a topology trap.
  • the high-level controller determines the cross-domain separation path group with the smallest path cost among the plurality of cross-domain separation path groups calculated as the target cross-domain separation path group.
  • the target cross-domain separation path group is actually globally optimal, and therefore, the problem that the global separation path calculated in the prior art is not optimal can be solved.
  • FIG. 8 shows a schematic diagram of an apparatus 400 for establishing a separation path in accordance with an embodiment of the present application.
  • the device 400 is configured in a communication system including at least two lower layer controllers, where the communication system includes at least two network domains, and the mapping relationship between the at least two lower layer controllers and the at least two network domains is one by one correspond.
  • the device 400 includes:
  • the first processing unit 410 is configured to determine a domain sequence consisting of the at least two network domains that need to pass from the source node to the destination node, where each network domain includes a source boundary node and a sink boundary node;
  • the second processing unit 440 is configured to determine an intra-domain separated path group set that each network domain in the domain sequence has, where the separated path group set includes at least one intra-domain separated path group, and the separated path group in each domain includes two intra-domain separations. a path, one of the separated paths in the two domains serves as an intra-domain working path and the other path serves as an intra-domain protection path, wherein each network domain has at least one separated path group;
  • the second processing unit 440 is further configured to: according to the intra-domain separated path group set of each network domain in the domain sequence And determining a cross-domain separated path group set, where the cross-domain path group set includes at least one cross-domain separated path group, each cross-domain separated path group includes one intra-domain separated path group of each network domain, and each cross-domain separation A path group includes two inter-domain separation paths, one of which is a cross-domain working path and the other path is a cross-domain protection path.
  • the device 400 further includes a transmitting unit 420 and a receiving unit 430.
  • the first network domain in the at least two network domains includes a source boundary node and a plurality of sink boundary nodes, where the at least two lower layer controllers include a first lower layer controller,
  • the first lower layer controller is a lower layer controller corresponding to the first network domain,
  • the receiving unit 430 is configured to receive first indication information that is sent by the first lower layer controller
  • the second processing unit 440 is specifically configured to determine, according to the indication of the first indication information, a set of intra-domain separated path groups of the first network domain, where the intra-domain separated path group set of the first network domain includes at least one domain of the first network domain. Separating the path group, the intra-domain separation path group of the first network domain is: the first lower-layer controller combines the plurality of sink-side boundary nodes of the first network domain to obtain at least one sink-end boundary node group, and then the first network domain The source boundary node is combined with the at least one sink boundary node group one by one.
  • the second network domain in the at least two network domains includes multiple source border nodes and multiple sink border nodes
  • the at least two lower layer controllers include a second lower layer controller.
  • the second lower layer controller is a lower layer controller corresponding to the second network domain
  • the receiving unit 430 is further configured to receive second indication information sent by the second lower layer controller
  • the second processing unit 440 is specifically configured to determine, according to the indication of the second indication information, the intra-domain separation path group set of the second network domain, where the intra-domain separation path group set of the second network domain includes at least one domain of the second network domain.
  • the intra-domain separation path group of the second network domain is a second lower-layer controller combining the plurality of source-side boundary nodes of the second network domain to obtain at least one source-end boundary node group, and the second network
  • the plurality of sink boundary nodes of the domain are combined by two to two, and after at least one sink boundary node group is obtained, the at least one source border node group and the at least one sink boundary node group are combined one by one.
  • the second processing unit 440 is further configured to calculate a path cost of each cross-domain separated path group included in the cross-domain separated path combination set, and separate the cross-domain separation with the minimum path cost.
  • the path group is determined to be a target cross-domain separation path group.
  • the second processing unit 440 is specifically configured to:
  • the weight of the preset working path and the protection path are calculated;
  • the path cost of each cross-domain separated path group is calculated according to the path cost of each separated path group and the preset inter-domain link weight.
  • FIG. 9 shows a schematic diagram of an apparatus 500 for establishing a separation path in accordance with an embodiment of the present application.
  • the device 500 is configured in a communication system including at least two network domains, where the communication system includes a high-level controller and at least two lower-layer controllers, and the at least two lower-layer controllers and the at least two network domains Mapping to one-to-one correspondence, the The device 500 corresponding to the first network domain is included in at least two lower layer controllers, and the first network domain is any one of the at least two network domains.
  • the apparatus 500 includes:
  • the processing unit 510 is configured to determine an intra-domain separated path group set of the first network domain, where the separated path group set includes at least one intra-domain separated path group, and the separated path group group in each of the at least one intra-domain separated path group includes two A separate path within the domain, one of the separated paths in the two domains serves as the working path within the domain and the other path serves as the intra-domain protection path;
  • the sending unit 520 is configured to send, to the high-layer controller, indication information for instructing the high-layer controller to determine the intra-domain separated path group set of the first network domain, so that the high-layer controller separates the path group set according to the domain of the first network domain and the Determining a set of inter-domain separated path groups in the at least two network domains of the network domain other than the first network domain, the cross-domain separation path group set including at least one cross-domain separation path group, each The cross-domain split path group includes two cross-domain split paths, one of the two cross-domain split paths acts as a cross-domain work path and the other path acts as a cross-domain protection path.
  • the apparatus 500 further includes a receiving unit 530.
  • the first network domain includes a source boundary node and a plurality of sink boundary nodes
  • the processing unit 510 is specifically configured to:
  • the first network domain includes multiple source border nodes and multiple sink border nodes
  • the processing unit 510 is specifically configured to:
  • processing unit 510 is further configured to:
  • the indication information is further used to indicate that the high-layer controller determines a path cost of the separated path group in the at least one domain of the first network domain, so that the high-layer controller is configured according to the first a path cost of the separated path group in at least one domain of the network domain and a path cost of at least one intra-path separated path group of each of the at least two network domains except the first network domain
  • the cross-domain separation path group with the smallest path cost is determined as the target cross-domain separation path group.
  • the processing unit is configured to calculate, according to the preset working path and the weight of the protection path, a path cost of the separated path group in each of the separated path groups in the at least one domain of the first network domain.
  • FIG. 10 is a schematic structural diagram of an apparatus 600 for establishing a separation path according to an embodiment of the present application.
  • the device 600 includes a memory 610, a processor 620, and a communication interface 630.
  • the memory 610, the processor The 620 and communication interface 630 are interconnected by a communication bus 640.
  • Memory 610 is used to store applications, code or instructions that perform the inventive arrangements.
  • the processor 620 is configured to execute applications, code or instructions stored in the memory 610 to perform the method 200 of establishing a separate path and the corresponding processes and/or operations performed by the higher layer controller in various embodiments. For the sake of brevity, it will not be repeated here.
  • the apparatus 400 for establishing a separation path provided in FIG. 8 can be implemented by the apparatus 600 for establishing a separation path as shown in FIG.
  • the first processing unit 410 and the second processing unit 440 in FIG. 8 may be implemented by the processor 620 in FIG. 10, and the transmitting unit 420 and the receiving unit 430 may be provided by one or more communication interfaces 630 shown in FIG. achieve.
  • FIG. 11 is a schematic structural diagram of an apparatus 700 for establishing a separation path according to an embodiment of the present application.
  • device 700 includes a memory 710, a processor 720, and a communication interface 730.
  • the memory 610, the processor 620, and the communication interface 730 are connected to each other through a communication bus 740.
  • Memory 710 is used to store applications, code or instructions that perform the inventive arrangements.
  • the processor 720 is configured to execute an application, code or instruction stored in the memory 710 to complete the method 200 of establishing a separate path and the corresponding flow executed by a lower layer controller (eg, a first lower layer controller) in each embodiment and/or Or operation. For the sake of brevity, it will not be repeated here.
  • a lower layer controller eg, a first lower layer controller
  • the apparatus 500 for establishing a separation path provided in FIG. 9 can be implemented by the apparatus 700 for establishing a separation path as shown in FIG.
  • processing unit 510 in FIG. 9 may be implemented by processor 720 in FIG. 11, and transmitting unit 520 and receiving unit 530 may be implemented by one or more communication interfaces 730 in FIG.
  • the processor shown in Figures 10 and 11 can be a central processing unit (CPU), microprocessor, application specific integration An application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the memory shown in FIGS. 10 and 11 may be read-only memory (ROM) or may store static information and Other types of static storage devices, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or electrically erasable programmable read-only memory (Electrically Erasable Programmable Read) -Only Memory, EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage A medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of an instruction or data structure and that can be accessed by a computer, but is not limited thereto.
  • the memory may be present independently and coupled to the processor via a communication bus (e.g., communication bus 640 in FIG. 10 and communication bus 740 in FIG. 11).
  • the memory may be present independently and coupled to the processor via a communication bus (e.g
  • the communication bus may include a power bus, a control bus, and a status signal bus in addition to the data bus.
  • various buses are labeled as communication buses in the figures.
  • the communication interface may be a wired interface, such as a Fiber Distributed Data Interface (FDDI), a Gigabit Ethernet (GE) interface, or the like. This embodiment of the present application does not specifically limit this.
  • FDDI Fiber Distributed Data Interface
  • GE Gigabit Ethernet
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.

Landscapes

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

Abstract

本申请实施例公开了一种建立分离路径的方法和装置，能够解决顺序计算跨域分离路径时的拓扑陷阱问题。该方法包括：高层控制器确定从源节点到达目的节点需要经过的至少两个网络域组成的域序列；高层控制器确定域序列中每个网络域具有的域内分离路径组集合，域内分离路径组集合包括至少一个域内分离路径组，每个域内分离路径组包括两条域内分离路径，该两条域内分离路径中的一条路径为域内工作路径且另一条路径为域内保护路径；高层控制器根据域序列中每个网络域具有的域内分离路径组集合，确定至少一个跨域分离路径组，每个跨域分离路径组包括两条跨域分离路径，该两条跨域分离路径中的一条路径作为跨域工作路径且另一条路径作为跨域保护路径。

Description

建立分离路径的方法和装置
本申请要求2016年11月25日提交中国专利局、申请号为201611064236.7、申请名称为“建立分离路径的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种计算分离路径的方法和装置。
背景技术
电信网络通常由海量的网络设备组成，组网规模非常大。因此，采用多协议标签交换(MultiProtocol Label Switching，MPLS)技术构建的电信网络，通常都会按照一定的规模将网络划分为多个自治域。自治域是一组标签交换路由器(Label Switching Router，LSR)设备组成的集合。一个自治域内的LSR设备运行在一个单一的分布式协议实例中或者由一个集中控制单元进行管理。在网络划分为多个自治域的情况下，一条标签交换路径(Label switch Path，LSP)连接通常需要贯穿多个MPLS的自治域。
在MPLS多域组网模型中，在业务的可靠性要求非常高，或者设备、光纤等发生故障的情况下，业务需要得到快速的保护恢复。为此，通常在MPLS网络中会部署工作和保护两条路径在承载同一个业务。当工作路径发生故障的情况下，所承载的业务能快速切换到保护路径上。为了保障这种恢复路径的选择，工作路径和保护路径需要遵循路径分离原则，即将工作路径和保护路径尽量分布到不同节点、不同链路上。为了建立遵循路径分离原则的两条路径，现有技术中提出了一种顺序计算的方法。顺序计算的主要思想是先建立一条工作路径，然后在排除工作路径的情况下再建立一条路径分离的保护路径。
但是，顺序计算方法在计算工作路径时并没有考虑保护路径。在工作路径计算完成后再计算保护路径，可能会导致在一个域内，无法计算出与工作路径的节点、链路分离的路径(也称为拓扑陷阱)，从而导致整个跨域分离路径的计算失败。
发明内容
本申请提供一种建立分离路径的方法和装置，能够解决计算跨域分离路径时拓扑陷阱的问题。
第一方面，本申请提供了一种建立分离路径的方法，在包括至少两个网络域的通信***中执行，该通信***包括高层控制器和至少两个低层控制器。该至少两个低层控制器与该至少两个网络域之间的映射为一一对应。该方法包括：高层控制器确定从源节点到达目的节点需要经过的该至少两个网络域所组成的域序列。每个网络域包括源端边界节点和宿端边界节点。高层控制器确定域序列中每个网络域所具有的域内分离路径组集合。该域内分离路径组集合包括至少一个域内分离路径组。该至少一个域 内分离路径组中的每个域内分离路径组包括两条域内分离路径，该两条域内分离路径中的一条路径作为域内工作路径且另一条路径作为域内保护路径。其中，每个网络域有至少一个域内分离路径组。高层控制器根据域序列中每个网络域所具有的域内分离路径组集合，确定一个跨域分离路径组集合。该跨域路径组集合包括至少一个跨域分离路径组。每个跨域分离路径组包括每个网络域的一个域内分离路径组。每个跨域分离路径组包括两条跨域分离路径，该两条跨域分离路径中的一条路径作为跨域工作路径且另一条路径作为跨域保护路径。
应理解，域序列是一个由多个域有序组成的序列。从源节点所在的网络域出发，依次经过域序列中的每个网络域，最后会到达目的节点所在的网络域。实际上，源节点为该域序列中第一个网络域中的节点，目的节点为该域序列中最后一个网络域中的节点。
需要说明的是，在本申请实施例中，建立网络域的域内分离路径组时，仅考虑了网络域的边界节点。网络域内部的节点之间的分离路径可以通过现有技术计算得到。现有技术对于计算网络域内部节点之间的分离路径的方法已经很成熟。本申请实施例对此不作详述。
在本申请实施例中，高层控制器在建立跨域分离路径时，首先确定从源节点到达目的节点需要经过的网络域中每个网络域的域内分离路径组，再依序对这些网络域的域内分离路径组进行组合，得到跨域分离路径组。由于每个域内分离路径组中包括两条域内路径，一条作为域内工作路径，另一条作为域内保护路径。换句话说，建立域内工作路径时也考虑到域内保护路径的建立。从而，根据域内分离路径组确定的每个跨域分离路径组中包括两条跨域分离路径，其中一条路径作为跨域工作路径且另一条路径作为跨域保护路径。从本申请实施例建立跨域分离路径的过程可以看出，跨域工作路径和跨域保护路径是同时建立的。因而能够避免现有技术中顺序计算分离路径时，由于先建立跨域工作路径再建立跨域保护路径，可能导致跨域工作路径计算完成后，无法计算得出跨域保护路径的拓扑陷阱的问题。
在一种可能的实现方式中，该至少两个网络域中的第一网络域包括一个源端边界节点以及多个宿端边界节点。该至少两个低层控制器中包括第一低层控制器。第一低层控制器为第一网络域对应的低层控制器。以及，高层控制器确定域序列中包括的每个网络域所具有的域内分离路径组集合，具体包括：高层控制器接收第一低层控制器发送的第一指示信息，并根据第一指示信息的指示确定第一网络域的域内分离路径组集合。该第一网络域的域内分离路径组集合包括第一网络域的至少一个域内分离路径组，第一网络域的域内分离路径组是第一低层控制器将第一网络域的多个宿端边界节点两两进行组合得到至少一个宿端边界节点组后，将第一网络域的源端边界节点与该至少一个宿端边界节点组一一进行组合得到的。
应理解，这里的第一网络域可以为该至少两个网络域中的任意一个网络域。并且，该至少两个网络域中可以包括一个或多个第一网络域。即，如果该至少两个网络域中有部分网络域的边界节点的拓扑结构满足源端边界节点为一个且宿端边界节点为多个，则可以采用本实施例中提供的方法来构建这些网络域的分离路径组。
在一种可能的实现方式中，该至少两个网络域中的第二网络域包括多个源端边界 节点以及多个宿端边界节点。该至少两个低层控制器包括第二低层控制器。第二低层控制器为与第二网络域对应的低层控制器。以及，高层控制器确定域序列中包括的每个网络域所具有的域内分离路径组集合，具体包括：高层控制器接收第二低层控制器发送的第二指示信息，并根据第二指示信息的指示确定第二网络域的域内分离路径组集合。该第二网络域的域内分离路径组集合包括第二网络域的至少一个域内分离路径组，第二网络域的域内分离路径组是第二低层控制器将第二网络域的多个源端边界节点两两进行组合，得到至少一个源端边界节点组，并将第二网络域的多个宿端边界节点两两进行组合，得到至少一个宿端边界节点组后，将该至少一个源端边界节点组与该至少一个宿端边界节点组一一进行组合得到的。
与第一网络域类似，这里的第二网络域可以为该至少两个网络域中的任意一个网络域。并且，该至少两个网络域中可以包括一个或多个第二网络域。即，如果该至少两个网络域中有多个网络域的边界节点的拓扑结构满足源端边界节点为多个且宿端边界节点为多个，则可以采用本实施例中提供的方法来构建这些网络域的分离路径组。
在一种可能的实现方式中，该至少两个网络域中的第三网络域包括多个源端边界节点和一个宿端边界节点。该至少两个低层控制器中包括第三低层控制器。第三低层控制器为与第三网络域对应的低层控制器。以及，高层控制器确定域序列中每个网络域所具有的域内分离路径组集合，具体包括：高层控制器接收第三低层控制器发送的第三指示信息，并根据第三指示信息的指示确定第三网络域的域内分离路径组集合。该第三网络域的域内分离路径组集合中包括第三网络域的至少一个域内分离路径组，第三网络域的域内分离路径组是第三低层控制器将第三网络域的多个源端边界节点两两进行组合，得到至少一个源端边界节点组后，将第三网络域的宿端边界节点与该至少一个源端边界节点组一一进行组合得到的。
应理解，本申请实施例的中编号“第一”、“第二”仅仅为了区分不同的对象，例如，为了区分不同的网络域、低层控制器等。因此，上述第一网络域、第二网络域和第三网络域仅是作为一个网络域的三种可能的拓扑结构。即就是说，通信***中的任意一个网络域可能为第一网络域的拓扑结构，也可能为第二网络域的拓扑结构，或者，还可以为第三网络域的拓扑结构。基于不同的拓扑结构，低层控制器确定域内分离路径组时的过程略有不同。具体过程参见说明书中的说明。
在一种可能的实现方式中，该方法还包括：高层控制器计算该跨域分离路径组集合中每个跨域分离路径组的路径代价，并将路径代价最小的跨域分离路径组确定为目标跨域分离路径组。
一般地，路径代价也可称为路径开销(path cost)。
应理解，高层控制器可以从跨域分离路径组集合中任意选择一个跨域分离路径组作为目标跨域分离路径组，并将目标跨域分离路径组中路径代价较小的一条路径作为跨域工作路径，而将路径代价较大的另一条路径作为跨域保护路径。
本申请实施例在选择目标跨域分离路径组时，高层控制器也可以将跨域分离路径组集合中路径代价最小的跨域分离路径组确定为目标跨域分离路径组。此时的目标跨域分离路径组为全局最优。
在一种可能的实现方式中，高层控制器计算每个跨域分离路径组的路径代价，包 括：高层控制器获取域序列中每个网络域所具有的每个域内分离路径组的路径代价，其中，每个网络域的每个域内分离路径组的路径代价是与每个网络域所对应的低层控制器根据预设的工作路径和保护路径的权重计算得到的；高层控制器根据每个分离路径组的路径代价和预设的域间链路权重，计算每个跨域分离路径组的路径代价。
第二方面，本申请提供了一种建立分离路径的方法，在包括至少两个网络域的通信***中执行。该通信***中包括高层控制器和至少两个低层控制器。该至少两个低层控制器与该至少两个网络域之间的映射为一一对应。该至少两个低层控制器中包括与第一网络域对应的第一低层控制器。第一网络域为该至少两个网络域中的任意一个网络域。该方法包括：第一低层控制器确定第一网络域的域内分离路径组集合。该域内分离路径组集合包括至少一个域内分离路径组。该至少一个域内分离路径组中的每个域内分离路径组中包括两条域内分离路径。该两条域内分离路径中的一条路径作为域内工作路径且另一条路径作为域内保护路径。第一低层控制器向高层控制器发送用于指示高层控制器确定第一网络域的域内分离路径组集合的指示信息，以便于高层控制器根据第一网络域的域内分离路径组集合和该至少两个网络域中除第一网络域之外的其它网络域的域内分离路径组集合，确定一个跨域分离路径组集合。该跨域分离路径组集合中包括至少一个跨域分离路径组。每个跨域分离路径组包括两条跨域分离路径，该两条跨域分离路径中的一条路径作为跨域工作路径且另一条路径作为跨域保护路径。
在本申请实施例中，高层控制器在建立跨域分离路径时，首先确定从源节点到达目的节点需要经过的网络域中每个网络域的域内分离路径组，再依序对这些网络域的域内分离路径组进行组合，得到跨域分离路径组。而这些网络域的域内分离路径组是由低层控制器计算确定后指示高层控制器的。
低层控制器确定一个网络域(该低层控制器对应的网络域)的域内分离路径时，总是计算得到包括两条路径的域内分离路径组，这两条路径中的一条路径作为域内的工作路径而另一条作为域内的保护路径。即，域内工作路径和域内保护路径是同时计算得到的。
因此，高层控制器根据每个网络域的域内分离路径组确定得到的每个跨域分离路径组中也同样包括两条跨域路径，并将其中一条路径作为跨域工作路径且另一条路径作为跨域保护路径。可见，跨域工作路径和跨域保护路径是同时建立的，因而能够避免现有技术中顺序计算分离路径时，由于先建立跨域工作路径再建立跨域保护路径，可能导致跨域工作路径计算完成后，无法计算得出跨域保护路径的拓扑陷阱的问题。
在一种可能的实现方式中，第一网络域包括一个源端边界节点以及多个宿端边界节点。以及，第一低层控制器确定第一网络域的域内分离路径组集合，包括：第一低层控制器将第一网络域的多个宿端边界节点两两进行组合，得到至少一个宿端边界节点组；第一低层控制器将源端边界节点与该多个宿端边界节点组一一进行组合，得到第一网络域的至少一个域内分离路径组。
在一种可能的实现方式中，第一网络域包括多个源端边界节点以及多个宿端边界节点。以及，第一低层控制器确定第一网络域的至少一个域内分离路径组，包括：第一低层控制器将第一网络域的多个源端边界节点两两进行组合，得到至少一个源端边 界节点组，并将第一网络域的多个宿端边界节点两两进行组合，得到至少一个宿端边界节点组；第一低层控制器将该至少一个源端边界节点组与该至少一个宿端边界节点组一一进行组合，得到第一网络域的至少一个域内分离路径组。
在一种可能的实现方式中，第一网络域包括多个源端边界节点以及一个宿端边界节点，以及，第一低层控制器确定第一网络域的至少一个域内分离路径组，包括：第一低层控制器将第一网络域的多个源端边界节点两两进行组合，得到至少一个源端边界节点组；第一低层控制器将第一网络域的一个宿端边界节点与该至少一个源端边界节点组一一进行组合，得到第一网络域的至少一个域内分离路径组。
在一种可能的实现方式中，在第一低层控制器向高层控制器发送指示信息以前，该方法还包括：第一低层控制器计算第一网络域的至少一个域内分离路径组的路径代价，其中，该指示信息还用于指示高层控制器根据第一网络域的该至少一个域内分离路径组的路径代价和该至少两个网络域中除第一网络域之外的其它网络域的每个网络域所具有的至少一个域内分离路径组的路径代价，将路径代价最小的跨域分离路径组确定为目标跨域分离路径组。
在一种可能的实现方式中，第一低层控制器计算第一网络域的至少一个域内分离路径组的路径代价，具体包括：第一低层控制器根据预设的工作路径和保护路径的权重，计算该第一网络域的至少一个域内分离路径组中每个域内分离路径组的路径代价。
应理解，第一低层控制器计算第一网络域的每个域内分离路径的路径代价，并将计算得到的路径代价的结果指示给高层控制器。从而，高层控制器可以基于每个网络域的至少一个域内分离路径组的路径代价，组合得到路径代价最小的跨域分离路径组，并将该路径代价最小的跨域分离路径组作为目标跨域分离路径组。此时的目标跨域分离路径组为全局最优。因而，可以节省路径开销，降低成本。
第三方面，本申请提供了一种建立跨域分离路径的装置，用于执行第一方面或第一方面的任意可能的实现方式中的方法。具体地，该装置包括执行第一方面或第一方面的任意可能的实现方式中的方法的单元。
第四方面，本申请提供了一种建立跨域分离路径的装置，用于执行第二方面或第二方面的任意可能的实现方式中的方法。具体地，该装置包括执行第二方面或第二方面的任意可能的实现方式中的方法的单元。
第五方面，本申请提供了一种网络设备，该网络设备包括处理器和存储器。存储器用于存储计算机程序，处理器用于从存储器中调用并运行计算机程序。当程序被运行时，该处理器执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第六方面，本申请提供了一种网络设备，该网络设备包括处理器和存储器。存储器用于存储计算机程序，处理器用于从存储器中调用并运行计算机程序。当程序被运行时，该处理器执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第七方面，本申请提供了一种通信***，包括第三方面所述的装置以及第四方面所述的装置。
第八方面，本申请提供了一种通信***，包括第五方面所述的网络设备以及第六方面所述的网络设备。
第九方面，本申请提供了一种计算机可读介质，用于存储计算机程序，该计算机 程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第十方面，本申请提供了一种计算机可读介质，用于存储计算机程序，该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
在本申请实施例中，高层控制器在建立跨域分离路径时，首先确定从源节点到达目的节点需要经过的网络域中每个网络域的域内分离路径组，再依序对这些网络域的域内分离路径组进行组合，得到跨域分离路径组。由于每个域内分离路径组中包括两条域内路径，一条作为域内工作路径，另一条作为域内保护路径。从而，根据域内分离路径组确定的每个跨域分离路径组中包括两条跨域分离路径，其中一条路径作为跨域工作路径且另一条路径作为跨域保护路径。即，跨域工作路径和跨域保护路径是同时建立的，因而能够避免现有技术中顺序计算分离路径时，由于先建立跨域工作路径再建立跨域保护路径，可能导致跨域工作路径计算完成后，无法计算得出跨域保护路径的拓扑陷阱的问题。
附图说明
图1示出了现有技术中分层部署的MPLS网络的架构图。
图2示出了现有技术中遵循路径分离的工作LSP路径和保护LSP路径。
图3为一种网络拓扑结构的示意图。
图4是本申请实施例提供的建立跨域分离路径的方法的示意性流程图。
图5为域内路径分离组的一种拓扑结构的示例。
图6为域内路径分离组的一种拓扑结构的示例。
图7为适用于本申请实施例的一种分层部署的集中控制式网络结构。
图8为本申请一实施例的建立分离路径的装置400的示意图。
图9为本申请另一实施例的建立分离路径的装置500的示意图。
图10为本申请一实施例的建立分离路径的设备600的示意性结构图。
图11为本申请另一实施例的建立分离路径的设备700的示意性结构图。
具体实施方式
下面结合附图，对本申请实施例的技术方案进行说明。
首先，对本申请实施例涉及的相关概念进行简单介绍。
多协议标签交换(Multi-Protocol Label Switching，MPLS)是利用标记进行数据转发的技术。当分组报文进入网络时，要为其分配固定长度的短标记，并将标记与分组报文封装在一起。在整个转发过程中，交换节点仅根据标记进行转发。在MPLS网络中，数据传输发生在标签交换路径(Label switch Path，LSP)上，LSP是每一个沿着从源端到宿端的路径上的节点的标签序列。
MPLS网络通常包括分布式控制MPLS网络和和集中式控制MPLS网络两种。电信网络通常由海量的网络设备组成，无论是分布式还是集中式，单个示例所能支持的组网规模都是有限的。所以采用MPLS技术构建的电信网络，通常会按照一定的规模将网络划分为多个自治域。自治域是一组LSR设备的集合。一个域内的LSR设备运行在一个单一的分布式协议实例中，或者由一个集中控制单元进行管理。在网络分为多个自治域的情况下，一条LSP连接通常需要贯穿多个MPLS的自治域。
由于多域组网方式的存在，需要有多个域的协同机制，以确保能创建和管理跨多个域的业务连接，现有技术中大多通过分层部署的控制单元来实现。
图1示出了现有技术中分层部署的MPLS网络的架构图。如图1所示，单域控制器(如图1中的控制器A和控制器B)直接和MPLS网络中的LSR交互，实现对单个域的集中控制。高层控制器(如图1中的控制器AB)和低层的单域控制器进行交互，完成对多个域的协同控制。
应理解，控制器可以分多层进行部署。图1所示的两层部署架构仅作为示例性的说明。例如，图1中的控制器A和控制器B为Lever 0层，高层控制器AB为Lever 1层。
采用MPLS技术构建的电信网络，对业务的可靠性要求非常高。在设备、光纤故障的情况下，业务需要得到快速的保护恢复。一般的恢复时间都要求在50ms以内。
现有技术中，为了满足业务快速恢复的需求，通常在MPLS网络中部署工作路径和保护路径两条LSP来承载同一业务。并采用相应的操作、管理和维护(operation,administration and maintenance，OAM)机制来检测LSP的故障。例如，双向转发检测(Bidirectional Forwarding Detection，BFD)、多协议标签交换传输子集(Multiprotocol Label Switching transport profile，MPLS-TP)等。当工作发生故障的情况下，工作LSP路径上承载的业务能够快速地切换到保护LSP路径上。
为了保证这种保护恢复机制有效运作，在保护和工作LSP路径的选择上需要遵循路径分离的原则。现有技术中的路径分离，是指工作路径和保护路径所经过的节点和链路完全不同。
图2示出了现有技术中遵循路径分离原则的工作LSP路径和保护LSP路径。如图2所示，组网拓扑中包括2个网络域(例如，域A和域B)。其中，工作LSP和保护LSP分别贯穿域A和域B。但是，工作LSP和保护LSP分别分布在不同的链路上，且链路上的节点没有重合。
基于这样的路径分离的概念，现有技术中提出了一种顺序路径计算(Sequential path computation)方法来计算遵循路径分离原则的工作路径和保护路径。顺序路径计算方法的主要思想是：先建立一条工作LSP路径。然后，在排除工作LSP路径的情况下再建立一条与工作LSP路径分离的保护LSP路径。具体的建立过程如下：
(1)计算一条跨域的工作路径。
(2)在路由信息表中排除已有的工作路径(包括排除工作路径上的节点、链路)，重新建立一条保护路径。
在跨域MPLS组网的情况下，单条LSP路径的建立方法已经很成熟。可以通过分层部署的集中式控制单元之间的分层计算和协同，实现LSP路径的计算和建立。
但是，由于顺序计算方法在建立第一条路径(例如，工作路径)的时候，没有考虑第二条路径(比如，保护路径)的要求。因此，在很多网络拓扑结构下，顺序计算方法不能保证计算出遵循路径分离的工作LSP路径和保护LSP路径。或者，在计算出工作LSP路径后，无法计算出保护LSP路径。
图3为一种网络拓扑结构的示意图。如图3所示，节点A和节点Z分别为源节点和目的节点(或者，称为宿节点)。计算从节点A到节点Z的两条分离路径时，如果 按照顺序计算方法，计算出的最优工作路径为A-B-F-H-J-Z。在计算保护路径时，排除工作路径后，将无法找到与工作路径完全分离的保护路径。
但是，从图3中可以看出，在实际的网络拓扑上，是存在分离的业务路径的。例如，A-C-E-F-H-J-Z和A-B-D-G-I-Z。
可见，现有技术提出的顺序计算方法存在一定的缺陷，在计算第一条路径时不考虑第二条路径，可能会导致无法计算出遵循路径分离的工作路径和保护路径。
下文结合图4至图7，对本申请实施例的建立跨域分离路径的方法进行详细说明。
首先，需要说明的是，本申请实施例提供的建立跨域分离路径的方法应用于集中控制方式的网络中，包括但不限于MPLS网络。在其它采用连接技术的网络中，也可以使用本申请实施例的计算跨域分离路径的方法计算跨域的分离路径，例如，同步数字序列(Synchronous Digital Hierarchy，SDH)的VC连接、光传送网(Optical Transport Network，OTN)中的光信道数据单元连接、WDN中的波长连接等。
需要说明的是，本申请实施例中所说的分离路径(包括后文所说的域内分离路径和跨域分离路径)与前文现有技术中所说的分离路径有所不同。在本申请实施例中，当多域网络所包括的每个网络域的源端边界节点和宿端边界节点均为多个时，根据本申请实施例建立的两条跨域分离路径(即，跨域工作路径和跨域保护路径)不会经过同一个节点，即两条跨域分离路径严格分离。而当多域网络中某个网络域仅有一个源端边界节点或仅有一个宿端边界节点时，根据本申请实施例建立的两条跨域分离路径则会经过同一个节点(即，两条跨域分离路径均会经过该网络域仅有的一个源端边界节点或仅有的一个宿端边界节点)。由此可见，在本申请实施例中，从源节点到达目的节点需要经过的至少两个网络域中有部分网络域的源端边界节点仅为一个或宿端边界节点仅为一个时，高层控制器最终建立的跨域分离路径并不是严格分离的。
由此可以理解的是，根据本申请实施例的建立跨域分离路径的方法，对于多域网络的拓扑结构没有任何限制。即就是说，无论多域网络的实际拓扑结构是怎样的，根据本申请实施例都可以计算出两条跨域的分离路径。虽然，在某些拓扑结构下，计算出的两条跨域分离路径并不是严格分离(即，可能经过相同的节点)。但是相对于现有技术中在这种情况下无法计算出跨域分离路径相比，算法的性能得到改善。并且，在工作路径发生故障时，若故障的节点并不是该工作路径和保护路径共同经过的节点，那么，保护路径并不会受到工作路径故障的影响，从而能够实现业务从工作路径切换到保护路径，以起到快速恢复业务的作用。
图4是本申请实施例提供的建立分离路径的方法200的示意性流程图。应理解，方法200可以由集中控制式网络中的高层控制器执行。更具体地，可以由配置在高层控制器中的处理器执行。如图4所示，该方法主要包括步骤210-230。
210、高层控制器确定从源节点到达目的节点需要经过的网络域所组成的域序列，该域序列中包括至少两个网络域，每个网络域包括源端边界节点和宿端边界节点。
应理解，这里的域序列是一个由多个域有序组成的序列。从源节点所在的网络域出发，依次经过域序列中的每个网络域，最后会到达目的节点所在的网络域。实际上，源节点为该域序列中第一个网络域中的节点，目的节点为该域序列中最后一个网络域中的节点。
在本申请实施例中，域序列可以预先设定。或者说，从源节点到达目的节点需要经过哪些网络域，可以由用户指定。
可选地，域序列还可以由高层控制器根据跨域拓扑关系自动进行计算而生成。
另外，网络域之间的连接关系可以由用户指定(或者说，预设)。或者，网络域之间的连接关系也可以由高层控制器基于网络域之间的协议自动发现。
220、高层控制器确定域序列中包括的每个网络域所具有的域内分离路径组集合，该域内分离路径组集合包括至少一个域内分离路径组，每个域内分离路径组包括两条域内分离路径，该两条域内分离路径中的一条路径作为域内工作路径且另一条路径作为域内保护路径，其中，每个网络域有至少一个分离路径组。
具体地，高层控制器可以通过接收每个网络域对应的低层控制器发送的用于指示每个网络域的域内分离路径组集合的指示信息，确定该域序列中所包括的每个网络域的域内分离路径组集合。
在申请实施例中，每个网络域的域内分离路径组是由该网络域对应的低层控制器计算得到的。每个低层控制器在计算所对应的网络域的域内分离路径组时，根据网络域边界节点拓扑结构的不同，具体的计算方法也不同。
实际上，网络域边界节点的拓扑分可为三种情况(为了便于说明，以下分别记作情况1、情况2和情况3)。
情况1、一个源端边界节点、多个宿端边界节点
在情况1的拓扑结构下，每个域内分离路径组包含两条域内分离路径(以下分别记作路径1和路径2)，这两条域内分离路径的源端边界节点相同且宿端边界节点不同。
可选地，作为一个实施例，该至少两个网络域中的第一网络域包括一个源端边界节点以及多个宿端边界节点，该至少两个低层控制器中包括第一低层控制器，第一低层控制器为第一网络域对应的低层控制器，
以及，高层控制器确定域序列中包括的每个网络域所具有的域内分离路径组集合，包括：
高层控制器接收第一低层控制器发送的第一指示信息，并根据第一指示信息的指示确定第一网络域的域内分离路径组集合，该第一网络域的域内分离路径组集合包括第一网络的至少一个域内分离路径组，该第一网络域的域内分离路径组是第一低层控制器将第一网络域的多个宿端边界节点两两进行组合得到多个宿端边界节点组后，将第一网络域的源端边界节点与该多个宿端边界节点组一一进行组合得到的。
具体地，如果域序列中某个网络域的源端边界节点为一个且宿端边界节点为多个，该网络域对应的低层控制器(即，第一低层控制器)在计算该网络域的域内分离路径组时，首先将宿端边界节点两两组合，形成多对宿端边界节点组，再将源端边界节点和所有“宿端边界节点组”进行组合，得到该网络域的多对域内分离路径组。
可选地，低层控制器计算得到所对应的网络域的至少一个域内分离路径组后，向高层控制器发送用于指示所对应的网络域的域内分离路径组集合的指示信息。其中，该域内分离路径组集合包括所对应的网络域的域内分离路径组中的至少一个。即，低层控制器可以不用将计算出的所对应的网络域的全部域内分离组告知高层服务器。
图5为分离路径组的一种拓扑结构的示例。如图5所示，节点A为域A的源端边界节点，节点B1、B2、B3为域A的宿端边界节点。图5中所示的拓扑结构通常用于业务接入域，节点A为LSP接入节点，节点B1、B2、B3为跨域节点。
根据前文所述，域A对应的低层控制器首先将节点B1、B2、B3两两组合，形成(B1，B2)、(B1，B3)、(B2，B3)三种宿端边界节点组。再将源端边界节点与这三种宿端边界节点组分别进行组合，最终形成[A-(B1,B2)]、[A-(B1,B3)]、[A-(B2,B3)]三个域内分离路径组。即，生成域A的三个域内分离路径组。
情况2、多个源端边界节点、多个宿端边界节点
在情况2的拓扑结构下，每个域内分离路径组也包含两条域内分离路径，不同于情况1的是，这两条域内路径的源端边界节点不同，宿端边界节点也不同。
可选地，作为一个实施例，该至少两个网络域中的第二网络域包括多个源端边界节点以及多个宿端边界节点，该至少两个低层控制器中包括第二低层控制器，该第二低层控制器为该第二网络域对应的低层控制器，
以及，高层控制器确定域序列中包括的每个网络域所具有的域内分离路径组集合，包括：
高层控制器接收第二低层控制器发送的第二指示信息，并根据第二指示信息的指示确定第二网络域的域内分离路径组集合，该第二网络域的域内分离路径组集合包括第二网络域的至少一个域内分离路径组，第二网络域的域内分离路径组是第二低层控制器将第二网络域的多个源端边界节点两两进行组合，得到至少一个源端边界节点组，并将第二网络域的多个宿端边界节点两两进行组合，得到至少一个宿端边界节点组后，将该至少一个源端边界节点组与该至少一个宿端边界节点组一一进行组合得到的。
具体地，如果域序列中某个网络域的源端边界节点为多个且宿端边界节点为多个时，该网络域对应的低层控制器在计算该网络域的域内分离路径组时，低层控制器(即，第二低层控制器)首先将源端边界节点两两组合，形成至少一个源端边界节点组(即，源端边界节点的组合)。同时低层控制器将宿端边界节点两两组合，形成至少一个宿端边界节点组(即，宿端边界节点的组合)。最后低层控制器将该至少一个源端边界节点组和该至少一个宿端边界节点组两两组合，得到该网络域的至少一个域内分离路径组。
图6为分离路径组的另一种拓扑结构的示例。如图6所示，节点C1、C2、C3为域B的源端边界节点，节点D1、D2、D3为域B的宿端边界节点。域B对应的低层控制器首先将源端边界节点C1、C2、C3两两进行组合，得到源端边界节点组，分别为(C1,C2)、(C1,C3)、(C2、C3)。同时，将D1、D2、D3两两进行组合，得到宿端边界节点组，分别为(D1,D2)、(D1,D3)、(D2,D3)。最后，域B对应的低层控制器将源端边界节点组和宿端边界节点组两两再进行组合，得到域B的域内分离路径组。
可以理解的是，若一个网络域有n个源端边界节点、m个宿端边界节点，那么，生成的该域的域内分离路径组的数量为：
Figure PCTCN2017099449-appb-000001
其中，n为大于等于2的整数，m为大于等于2的整数。
以图6所示的域边界拓扑结构为例，得到的域B的域内分离路径组的数量为：
Figure PCTCN2017099449-appb-000002
分别为：
[C1-D1、C2-D2]、[C1-D2、C2-D1]
[C1-D1、C2-D3]、[C1-D3、C2-D1]
[C1-D2、C2-D3]、[C1-D3、C2-D2]
[C1-D1、C3-D2]、[C1-D2、C3-D1]
[C1-D1、C3-D3]、[C1-D3、C3-D1]
[C1-D2、C3-D3]、[C1-D3、C3-D2]
[C2-D1、C3-D2]、[C2-D2、C3-D1]
[C2-D1、C3-D3]、[C2-D3、C3-D1]
[C2-D2、C3-D3]、[C2-D3、C3-D2]。
情况3、多个源端边界节点、一个宿端边界节点
应理解，在情况3下，低层控制器计算所对应的网络域的域内分离路径的过程与情况1类似。即，低层控制器首先将多个源端边界节点两两组合，得到至少一个源端边界节点组，再将宿端边界节点与该源端边界节点组一一组合，从而得到至少一个域内分离路径组。
每个低层控制器根据所对应的网络域边界节点的拓扑结构，按照上述三种情况中的方法，计算所对应的网络域的至少一个域内分离路径组，并在计算完成后向高层控制器发送指示信息，该指示信息用于向高层控制器指示该至少一个域内分离路径组。
相对应地，高层控制器接收每个低层控制器发送的指示信息，并根据指示信息的指示确定每个低层控制器所对应的每个网络域的域内分离路径组集合，每个网络域的域内分离路径组集合包括该网络域的至少一个域内分离路径组。从而，高层控制器得到域序列中每个网络域的至少一个域内分离路径组。
这里，对低层控制器向高层控制器发送指示信息的方式不作特别限定。例如，低层控制器可以通过向高层控制器向高层控制器发送简单网络管理协议(Simple Network Management Protocol，SNMP)消息、Socket协议消息和传输控制协议(Transmission Control Protocol，TCP)协议消息的方式，向高层控制器发送用于指示域内分离路径组的指示信息。
以SNMP消息为例，低层控制器在SNMP消息中携带该指示信息。具体地，该指示信息可以指示两个标识序列。每个标识序列由至少两个设备标识组成。其中，每个标识序列中的每个设备标识用于标识一个设备，并且，每个标识序列中的设备标识分别标识域内分离路径依序经过的设备(或者说，节点)。另外，该指示信息中还包括这些设备之间的接口信息。
高层控制器接收低层控制器发送的SNMP消息，从SNMP消息中获取该指示信息，基于该指示信息，高层控制器根据每个标识序列中设备标识的顺序以及设备之间的接口信息，能够确定该网络域所具有的域内分离路径组。
需要说明的是，在本申请实施例中，计算网络域内的域内分离路径组时，仅考虑 了网络域的边界节点(包括源端边界节点和宿端边界节点)，而没有考虑网络域内部的节点。实际上，现有技术中计算网络域内部节点的分离路径的方法已经非常成熟，本申请实施例对此不作详述。
230、高层控制器根据域序列中包括的每个网络域所具有的域内分离路径组集合，确定一个跨域分离路径组集合，该跨域分离路径组集合包括至少一个跨域分离路径组，每个跨域分离路径组包括每个网络域的一个域内分离路径组，每个跨域分离路径组包括两条跨域分离路径，该两条跨域分离路径中的一条路径作为跨域工作路径且另一条路径作为跨域保护路径。
根据前文所述，跨域工作路径和跨域保护路径是两条彼此分离且依次贯穿域序列中每个网络域的路径。根据步骤220的计算，得到了每个域内的分离路径组。
具体地，在步骤230中，从每个网络域的多个域内分离路径组中选择一个域内分离路径组进行组合，得到一个跨域分离路径组集合，该跨域分离路径组集合包括多个跨域分离路径组。
容易理解的是，组合出的每个跨域分离路径组中包括的域内分离路径组与域序列中的网络域一一对应，每个域内分离路径组为所对应的网络域的至少一个域内分离路径组中的一个。
根据上述计算过程可以看出，在本申请实施例中，高层控制器在建立跨域分离路径时，首先确定从源节点到达目的节点需要经过的网络域中每个网络域的域内分离路径组，再依序对这些网络域的域内分离路径组进行组合，得到跨域分离路径组。由于每个域内分离路径组中包括两条域内路径，一条作为域内工作路径，另一条作为域内保护路径。换句话说，建立域内工作路径时也考虑到域内保护路径的建立。从而，根据域内分离路径组确定的每个跨域分离路径组中包括两条跨域分离路径，其中一条路径作为跨域工作路径且另一条路径作为跨域保护路径。从本申请实施例建立跨域分离路径的过程可以看出，跨域工作路径和跨域保护路径是同时建立的，因而能够避免现有技术中顺序计算分离路径时，由于先建立跨域工作路径再建立跨域保护路径，可能导致跨域工作路径计算完成后，无法计算得出跨域保护路径的拓扑陷阱的问题。
可选地，作为一个实施例，该方法还包括：
高层控制器计算该跨域分离路径组集合中每个跨域分离路径组的路径代价，并将路径代价最小的跨域分离路径组确定为目标跨域分离路径组。
容易理解的是，根据上述步骤210-230，高层控制器确定(或者说，计算得到)了一个跨域分离组集合，而跨域分离路径组集合中包括至少一个跨域分离路径组，每个跨域分离路径组中实际上都包括两条跨域分离路径。因此，可以从步骤230中确定的至少两个跨域分离路径组中任意选择一个跨域分离路径组，并将所选择的跨域分离路径组中的一条跨域路径作为跨域工作路径，另外一条跨域路径作为跨域保护路径。
在本实施例中，可以根据路径代价，从该跨域分离路径组集合中选择路径代价最小的跨域分离路径组作为目标跨域分离路径组。
进一步地，可以将目标跨域分离路径组中路径代价较小的一条跨域路径作为跨域工作路径，而将路径代价较大的另一条跨域路径作为跨域保护路径。
可选地，作为一个实施例，高层控制器获取域序列中每个网络域所具有的每个域 内分离路径组的路径代价，其中，每个网络域的每个域内分离路径组的路径代价是与每个网络域所对应的低层控制器根据预设的工作路径和保护路径的权重计算得到的；
高层控制器根据每个分离路径组的路径代价和预设的域间链路权重，计算每个跨域分离路径组的路径代价。
具体地，与前文所述的低层控制器向高层控制器发送用于指示域内分离路径组的指示信息类似，低层控制器可以通过向高层控制器发送SNMP协议消息、Socket协议消息和TCP协议消息来向高层控制器上报域内分离路径组的路径代价。例如，在SNMP协议消息、Socket协议消息或TCP协议消息中携带用于指示该低层控制器所对应的网路域的域内分离路径组的路径代价的信息。
容易想到的是，当一个网络域的域内分离路径组有多个时，该指示信息中包括多个路径代价的信息。显然，低层控制器可以将全部域内分离路径组的路径代价上报至高层控制器，也可以选择路径代价较小的部分域内分离路径组的路径代价上报给高层控制器。
在本申请实施例中，高层控制器在确定目标跨域分离路径组时，是结合每个网络域的域内分离路径组的路径代价、预设的域内分离路径组的路径代价与域间链路代价的权重计算得到的。
低层控制器对于域内分离路径组[C1-D1、C2-D2]的路径代价的计算大致可以包括如下过程：
(1)计算节点C1到节点D1的路径代价，以下记作Cost[C1-D1]。
(2)计算节点C2到节点D2的路径代价，以下记作Cost[C2-D2]。
计算出域内分离路径组[C1-D1、C2-D2]中的两条分离路径的路径代价后，将路径代价小的一条路径确定为域内工作路径，将路径代价大的另一条路径确定为域内保护路径。
(3)计算该域内分离路径组的路径代价。
具体地，域内分离路径组的路径代价＝域内工作路径的路径代价×域内工作路径的路径代价权重k+域内保护路径的路径代价×域内保护路径的路径代价权重j。
需要说明的是，这里的域内工作路径的路径代价权重和域内保护路径的路径代价权重可以由用户指定(或者说，预设)。
(4)计算跨域分离路径的路径代价。
跨域分离路径的路径代价是高层控制器在各个低层控制器确定的各个网络域的域内分离路径的路径代价的基础上计算得到的。
具体地，高层控制器可以按照如下方式计算跨域分离路径组的路径代价。即，跨域分离路径的路径代价＝域内分离路径组#1的路径代价×网络域#1的权重+域内分离路径组#2的路径代价×网络域#2的权重+……+(网络域#1与网络域#2的域间链路的路径代价)×(网络域#1与网络域#2的域间链路的路径代价权重)+(网络域#2与网络域#3的域间链路的路径代价)×(网络域#2与网络域#3的域间链路的路径代价权重)+……。
类似地，域间链路的路径代价权重和网络域的权重可以由用户指定(或者说，预设)。
按照上述步骤计算得到所有端到端(即，源节点到目的节点)跨域分离路径的路径代价后，通过比较，将路径代价最小的跨域分离路径组确定为最优(即，目标)跨域分离路径组。
最后，建立该最优跨域分离路径组，完成跨域分离路径的建立。
如前文所述，本申请实施例的计算跨域分离路径的方法适用于分层部署的集中控制网络***，用于跨多个网络域的情况下建立路径分离的两条标签交换路径(LSP)。通过各层之间的交互，可以解决现有技术中建立跨域分离路径时拓扑陷阱的问题。
进一步地，根据本申请实施例的建立跨域分离路径的方法，可以保证建立出的跨域分离路径全局最优。
下面结合图7所示的分层部署的集中控制网络***，对本申请实施例进行举例说明。
图7为适用于本申请实施例的一种分层部署的集中控制式网络***。如图7所示，网络***分两层部署，分别记作层1和层0(分别如图中所示的L1和L0)。其中，控制器A为高层控制器，控制器B、控制器C、控制器D和控制器E为低层控制器。控制器B、控制器C、控制器D、控制器分别对域1、域2、域3和域4进行管理和控制。低层控制器和高层控制器之间通过交互实现对整个网路***的协同管理和控制。
301、生成路由信息。
具体地，低层控制器(如图中所示的控制器B、控制器C、控制器D和控制器E)生成各自域内的路由信息。高层控制器通过人工指定的方式形成域间边界节点的联系关系，生成跨域的路由信息。
302、确定域序列。
当高层控制器(即，控制器A)接收到跨域业务建立请求后，根据本层的跨域抽象拓扑，计算从源节点到目的节点依次需要经过的网络域的有序组合，得到一个域序列。跨域抽象拓扑包含域边界节点之间的连接关系，其中，跨域边界点连接关系可以由用户进行指定，或者，也可以由高层控制器基于网络域之间的协议自动发现。
303、生成各个网络域的域内分离路径组。
控制器A根据LSP经过的域和该域与相邻域的边界节点，向低层控制器发送请求消息，该请求消息用于请求低层控制器计算各自对应的网络域的域内分离路径组。
低层控制器接收高层控制器发送的请求消息，确定所对应的网络域的至少一个域内分离路径组。
低层控制器确定域内分离路径组的具体过程可以参见前文所述的情况1和情况2，此处不再赘述。
304、计算各个域的域内分离路径组的路径代价。
具体地，各个低层控制器计算各自对应的网络域的所有域内分离路径组的路径代价。计算完成后，向高层控制器A发送包含域内路径分离组的工作通道代价、保护通道代价、域内路径分离组的路径代价的信息。
305、确定跨域分离路径组的路径代价。
高层控制器A接收到每个低层控制器发送的用于指示所对应的每个网络域的至少一个域内分离路径组的路径代价的指示信息后，根据该指示信息的指示和跨域边界节 点的连接关系，组合得到多个跨域分离路径组(即，端到端分离LSP路径组)，即得到一个跨域分离路径组集合。然后高层控制器计算每个跨域分离路径组的路径代价。
类似地，具体的计算过程可以参考前文。这里不再赘述。
306、确定最优跨域分离路径组。
应理解，高层控制器可以从跨域分离路径组集合中任意选择一个跨域分离路径组作为目标跨域分离路径组，并将目标跨域分离路径组中路径代价较小的一条路径作为跨域工作路径，而将路径代价较大的另一条路径作为跨域保护路径。
可选地，高层控制器A通过比较所有跨域分离路径组的路径代价，选择出路径代价最小的跨域分离路径组作为目标跨域路径分离组。此时的目标跨域分离路径组为全局最优。
307、建立最优跨域分离路径组。
高层控制器A将选择出的最优跨域分离路径组中的域内路径下发到对应的低层控制器，由低层控制器完成跨域分离路径的建立。
需要说明的是，本申请实施例仅以采用两层控制器的情况作为示例，在部署有多层控制器的情况下，通过逐层抽象，也可以采用本申请实施例的计算跨域路径的方法。
应理解，这里所说的逐层抽象是指低层控制器所管理的网络的拓扑，对高层控制器抽象为仅包含域间节点的网络拓扑抽象。例如，L0层控制器将L0层网络抽象为域边界点连接关系给L1层控制单元。L1层控制器将L1层网络抽象为域边界点连接关系给L2层控制器等。
本申请实施例的建立分离路径的方法，通过同时计算跨域工作路径和跨域保护路径，可解决现有方案中计算跨域分离路径时，先建立跨域保护路径再建立跨域保护路径而可能导致的跨域保护路径无法计算得到的拓扑陷阱的问题。
更进一步地，本申请实施例在选择目标跨域分离路径组时，高层控制器将计算得到的多个跨域分离路径组中路径代价最小的跨域分离路径组确定为目标跨域分离路径组，此时，目标跨域分离路径组实际上是全局最优的，因此，能够解决现有技术中计算出的全局分离路径非最优的问题。
以上结合图4至图7对本申请实施例的建立分离路径的方法进行了详细说明。以下结合图8至图，对本申请实施例的建立分离路径的装置进行说明。
图8示出了本申请实施例的建立分离路径的装置400的示意图。其中，装置400配置在包括至少两个低层控制器的通信***中，该通信***包括至少两个网络域，该至少两个低层控制器与该至少两个网络域之间的映射关系为一一对应。如图8所示，装置400包括：
第一处理单元410，用于确定从源节点到达目的节点需要经过的所述至少两个网络域所组成的域序列，每个网络域包括源端边界节点和宿端边界节点；
第二处理单元440用于，确定域序列中每个网络域所具有的域内分离路径组集合，该域内分离路径组集合包括至少一个域内分离路径组，每个域内分离路径组包括两条域内分离路径，该两条域内分离路径中的一条路径作为域内工作路径且另一条路径作为域内保护路径，其中，每个网络域有至少一个分离路径组；
第二处理单元440还用于，根据域序列中每个网络域所具有的域内分离路径组集 合，确定一个跨域分离路径组集合，该跨域路径组集合包括至少一个跨域分离路径组，每个跨域分离路径组包括每个网络域的一个域内分离路径组，每个跨域分离路径组包括两条跨域分离路径，该两条跨域分离路径中的一条路径作为跨域工作路径且另一条路径作为跨域保护路径。
具体地，装置400还包括发送单元420和接收单元430。
可选地，作为一个实施例，该至少两个网络域中的第一网络域包括一个源端边界节点以及多个宿端边界节点，该至少两个低层控制器中包括第一低层控制器，第一低层控制器为第一网络域对应的低层控制器，
所述接收单元430，用于接收第一低层控制器发送的第一指示信息；
以及，第二处理单元440具体用于根据第一指示信息的指示，确定第一网络域的域内分离路径组集合，该第一网络域的域内分离路径组集合包括第一网络域的至少一个域内分离路径组，第一网络域的域内分离路径组是第一低层控制器将第一网络域的多个宿端边界节点两两进行组合得到至少一个宿端边界节点组后，将第一网络域的源端边界节点与该至少一个宿端边界节点组一一进行组合得到的。
可选地，作为一个实施例，该至少两个网络域中的第二网络域包括多个源端边界节点以及多个宿端边界节点，该至少两个低层控制器包括第二低层控制器，第二低层控制器为与第二网络域对应的低层控制器，
所述接收单元430，还用于接收第二低层控制器发送的第二指示信息；
以及，第二处理单元440具体用于根据第二指示信息的指示，确定第二网络域的域内分离路径组集合，该第二网络域的域内分离路径组集合包括第二网络域的至少一个域内分离路径组，第二网络域的域内分离路径组是第二低层控制器将第二网络域的多个源端边界节点两两进行组合，得到至少一个源端边界节点组，并将第二网络域的多个宿端边界节点两两进行组合，得到至少一个宿端边界节点组后，将该至少一个源端边界节点组与该至少一个宿端边界节点组一一进行组合得到的。
可选地，作为一个实施例，所述第二处理单元440还用于计算该跨域分离路径组合集合中包括的每个跨域分离路径组的路径代价，并将路径代价最小的跨域分离路径组确定为目标跨域分离路径组。
可选地，作为一个实施例，第二处理单元440具体用于：
获取域序列中每个网络域所具有的每个域内分离路径组的路径代价，其中，每个网络域的每个域内分离路径组的路径代价是与每个网络域所对应的低层控制器根据预设的工作路径和保护路径的权重计算得到的；
根据每个分离路径组的路径代价和预设的域间链路权重，计算每个跨域分离路径组的路径代价。
根据本申请实施例的装置400中的各单元和上述其它操作或功能分别为了实现本申请实施例的建立分离路径的方法200中由高层控制器执行的相应流程。为了简洁，此处不再赘述。
图9示出了本申请实施例的建立分离路径的装置500的示意图。其中，装置500配置在包括至少两个网络域的通信***中，该通信***中包括高层控制器和至少两个低层控制器，该至少两个低层控制器与该至少两个网络域之间的映射为一一对应，该 至少两个低层控制器中包括与第一网络域对应的装置500，第一网络域为该至少两个网络域中的任意一个网络域。如图9所示，装置500包括：
处理单元510，用于确定第一网络域的域内分离路径组集合，该域内分离路径组集合包括至少一个域内分离路径组，该至少一个域内分离路径组中的每个域内分离路径组包括两条域内分离路径，该两条域内分离路径中的一条路径作为域内工作路径且另一条路径作为域内保护路径；
发送单元520，用于向高层控制器发送用于指示高层控制器确定第一网络域的域内分离路径组集合的指示信息，以便于高层控制器根据第一网络域的域内分离路径组集合和该至少两个网络域中除第一网络域之外的其它网络域的域内分离路径组集合，确定一个跨域分离路径组集合，该跨域分离路径组集合包括至少一个跨域分离路径组，每个跨域分离路径组包括两条跨域分离路径，该两条跨域分离路径中的一条路径作为跨域工作路径且另一条路径作为跨域保护路径。
具体地，装置500还包括接收单元530。
可选地，作为一个实施例，第一网络域包括一个源端边界节点以及多个宿端边界节点，以及，处理单元510具体用于：
将所述第一网络域的所述多个宿端边界节点两两进行组合，得到至少一个宿端边界节点组；
将第一网络域的所述源端边界节点与该至少一个宿端边界节点组一一进行组合，得到第一网络域的至少一个域内分离路径组。
可选地，作为一个实施例，第一网络域包括多个源端边界节点以及多个宿端边界节点，以及，处理单元510具体用于：
将第一网络域的所述多个源端边界节点两两进行组合，得到至少一个源端边界节点组，并将第一网络域的多个宿端边界节点两两进行组合，得到至少一个宿端边界节点组；
将该至少一个源端边界节点组与该至少一个宿端边界节点组一一进行组合，得到第一网络域的至少一个域内分离路径组。
可选地，作为一个实施例，处理单元510还用于：
计算第一网络域的至少一个域内分离路径组的路径代价，该指示信息还用于指示高层控制器确定第一网络域的至少一个域内分离路径组的路径代价，以便于高层控制器根据第一网络域的至少一个域内分离路径组的路径代价和该至少两个网络域中除第一网络域之外的其它网络域的每个网络域所具有的至少一个域内分离路径组的路径代价，将路径代价最小的跨域分离路径组确定为目标跨域分离路径组。
可选地，作为一个实施例，处理单元具体用于根据预设的工作路径和保护路径的权重，计算第一网络域的至少一个域内分离路径组中每个域内分离路径组的路径代价。
根据本申请实施例的装置500中的各单元和上述其它操作或功能分别为了实现本申请实施例的建立分离路径的方法200中由低层控制器(例如，第一低层控制器)执行的相应流程。为了简洁，此处不再赘述。
图10为本申请实施例的建立分离路径的设备600的示意性结构图。如图10所示，设备600包括：存储器610、处理器620和通信接口630。其中，存储器610、处理器 620和通信接口630通过通信总线640相互连接。
存储器610用于存储执行本发明方案的应用程序、代码或指令。处理器620用于执行存储器610中存储的应用程序、代码或指令，以完成建立分离路径的方法200以及各实施例中由高层控制器执行的相应流程和/或操作。为了简洁，此处不再赘述。
应理解，图8中提供的建立分离路径的装置400，可以通过图10中所示的建立分离路径的设备600来实现。例如，图8中的第一处理单元410以及第二处理单元440可以由图10中的处理器620实现，发送单元420和接收单元430可以由图10中所示的一个或多个通信接口630实现。
图11为本申请实施例的建立分离路径的设备700的示意性结构图。如图11所示，设备700包括：存储器710、处理器720和通信接口730。其中，存储器610、处理器620和通信接口730通过通信总线740相互连接。
存储器710用于存储执行本发明方案的应用程序、代码或指令。处理器720用于执行存储器710中存储的应用程序、代码或指令，以完成建立分离路径的方法200以及各实施例中由低层控制器(例如，第一低层控制器)执行的相应流程和/或操作。为了简洁，此处不再赘述。
同样的，图9中提供的建立分离路径的装置500，可以通过图11中所示的建立分离路径的设备700来实现。例如，图9中的处理单元510可以由图11中的处理器720实现，发送单元520和接收单元530可以由图11中的一个或多个通信接口730实现。
图10和图11中所示的处理器(例如，图10中所示的处理器620和图11中所示的处理器720)可以为中央处理器(CPU)、微处理器、特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
图10和图11中所示的存储器(例如，图10中所示的存储器610和图11中所示的存储器710)可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信总线(例如，图10中的通信总线640和图11中的通信总线740)与处理器相连接。存储器也可以和处理器集成在一起。
通信总线除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。为了清楚说明起见，在图中将各种总线都标为通信总线。
通信接口可以是有线接口，例如光纤分布式数据接口(Fiber Distributed Data Interface，简称FDDI)、千兆以太网(Gigabit Ethernet，简称GE)接口等，也可以是无线接口。本申请实施例对此不作特别限定。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺 序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (10)

  1. 一种建立分离路径的方法，其特征在于，在包括至少两个网络域的通信***中执行，所述通信***包括高层控制器和至少两个低层控制器，所述至少两个低层控制器与所述至少两个网络域之间的映射为一一对应，所述方法包括：
    所述高层控制器确定从源节点到达目的节点需要经过的所述至少两个网络域所组成的域序列，每个网络域包括源端边界节点和宿端边界节点；
    所述高层控制器确定所述域序列中每个网络域所具有的域内分离路径组集合，所述域内分离路径组集合包括至少一个域内分离路径组，每个域内分离路径组包括两条域内分离路径，所述两条域内分离路径中的一条路径作为域内工作路径且另一条路径作为域内保护路径，其中，所述每个网络域有至少一个所述域内分离路径组；
    所述高层控制器根据所述域序列中每个网络域所具有的域内分离路径组集合，确定一个跨域分离路径组集合，所述跨域路径组集合包括至少一个跨域分离路径组，每个所述跨域分离路径组包括所述每个网络域的一个域内分离路径组，每个所述跨域分离路径组包括两条跨域分离路径，所述两条跨域分离路径中的一条路径作为跨域工作路径且另一条路径作为跨域保护路径。
  2. 根据权利要求1所述的方法，其特征在于，所述至少两个网络域中的第一网络域包括一个源端边界节点以及多个宿端边界节点，所述至少两个低层控制器中包括第一低层控制器，所述第一低层控制器为所述第一网络域对应的低层控制器，
    以及，所述高层控制器确定所述域序列中包括的每个网络域所具有的域内分离路径组集合，具体包括：
    所述高层控制器接收所述第一低层控制器发送的第一指示信息，并根据所述第一指示信息的指示确定所述第一网络域的域内分离路径组集合，所述第一网络域的域内分离路径组集合包括所述第一网络域的至少一个域内分离路径组，所述第一网络域的域内分离路径组是所述第一低层控制器将所述第一网络域的所述多个宿端边界节点两两进行组合得到至少一个宿端边界节点组后，将所述第一网络域的源端边界节点与所述至少一个宿端边界节点组一一进行组合得到的。
  3. 根据权利要求1或2所述的方法，其特征在于，所述至少两个网络域中的第二网络域包括多个源端边界节点以及多个宿端边界节点，所述至少两个低层控制器包括第二低层控制器，所述第二低层控制器为与所述第二网络域对应的低层控制器，
    以及，所述高层控制器确定所述域序列中包括的每个网络域所具有的域内分离路径组集合，具体包括：
    所述高层控制器接收所述第二低层控制器发送的第二指示信息，并根据所述第二指示信息的指示确定所述第二网络域的域内分离路径组集合，所述第二网络域的域内分离路径组集合包括所述第二网络域的至少一个域内分离路径组，所述第二网络域的域内分离路径组是所述第二低层控制器将所述第二网络域的所述多个源端边界节点两两进行组合，得到至少一个源端边界节点组，并将所述第二网络域的所述多个宿端边界节点两两进行组合，得到至少一个宿端边界节点组后，将所述至少一个源端边界节点组与所述至少一个宿端边界节点组一一进行组合得到的。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    所述高层控制器计算所述跨域分离路径组合集合中包括的每个跨域分离路径组的路径代价，并将路径代价最小的跨域分离路径组确定为目标跨域分离路径组。
  5. 根据权利要求4所述的方法，其特征在于，所述高层控制器计算所述每个跨域分离路径组的路径代价，具体包括：
    所述高层控制器获取所述域序列中每个网络域所具有的每个域内分离路径组的路径代价，其中，所述每个网络域的每个域内分离路径组的路径代价是与所述每个网络域所对应的低层控制器根据预设的工作路径和保护路径的权重计算得到的；
    所述高层控制器根据所述每个分离路径组的路径代价和预设的域间链路权重，计算所述每个跨域分离路径组的路径代价。
  6. 一种建立分离路径的装置，其特征在于，配置在包括至少两个网络域的通信***中，所述通信***包括至少两个低层控制器，所述至少两个低层控制器与所述至少两个网络域之间的映射关系为一一对应，所述装置包括：
    第一处理单元，用于确定从源节点到达目的节点需要经过的所述至少两个网络域所组成的域序列，每个网络域包括源端边界节点和宿端边界节点；
    第二处理单元，用于确定所述域序列中每个网络域所具有的域内分离路径组集合，所述域内分离路径组集合包括至少一个域内分离路径组，每个所述域内分离路径组包括两条域内分离路径，所述两条域内分离路径中的一条路径作为域内工作路径且另一条路径作为域内保护路径，其中，每个网络域有至少一个分离路径组；
    所述第二处理单元，还用于根据所述域序列中每个网络域所具有的域内分离路径组集合，确定一个跨域分离路径组集合，所述跨域路径组集合包括至少一个跨域分离路径组，每个所述跨域分离路径组包括所述每个网络域的一个域内分离路径组，每个所述跨域分离路径组包括两条跨域分离路径，所述两条跨域分离路径中的一条路径作为跨域工作路径且另一条路径作为跨域保护路径。
  7. 根据权利要求6所述的装置，其特征在于，所述至少两个网络域中的第一网络域包括一个源端边界节点以及多个宿端边界节点，所述至少两个低层控制器中包括第一低层控制器，所述第一低层控制器为所述第一网络域对应的低层控制器，所述装置还包括接收单元，所述接收单元用于接收所述第一低层控制器发送的第一指示信息；
    所述第二处理单元具体用于根据所述第一指示信息的指示，确定所述第一网络域的域内分离路径组集合，所述第一网络域的域内分离路径组集合包括所述第一网络域的至少一个域内分离路径组，所述第一网络域的域内分离路径组是所述第一低层控制器将所述第一网络域的所述多个宿端边界节点两两进行组合得到至少一个宿端边界节点组后，将所述第一网络域的源端边界节点与所述至少一个宿端边界节点组一一进行组合得到的。
  8. 根据权利要求6所述的装置，其特征在于，所述至少两个网络域中的第二网络域包括多个源端边界节点以及多个宿端边界节点，所述至少两个低层控制器包括第二低层控制器，所述第二低层控制器为与所述第二网络域对应的低层控制器，所述装置还包括接收单元，所述接收单元用于接收所述第二低层控制器发送的第二指示信息；
    所述第二处理单元具体用于根据所述第二指示信息的指示，确定所述第二网络域的域内分离路径组集合，所述第二网络域的域内分离路径组集合中包括所述第二网络 域的至少一个域内分离路径组，所述第二网络域的域内分离路径组是所述第二低层控制器将所述第二网络域的所述多个源端边界节点两两进行组合，得到至少一个源端边界节点组，并将所述第二网络域的所述多个宿端边界节点两两进行组合，得到至少一个宿端边界节点组后，将所述至少一个源端边界节点组与所述至少一个宿端边界节点组一一进行组合得到的。
  9. 根据权利要求6至8中任一项所述的装置，其特征在于，所述第二处理单元还用于计算所述跨域分离路径组合集合中包括的每个跨域分离路径组的路径代价，并将路径代价最小的跨域分离路径组确定为目标跨域分离路径组。
  10. 根据权利要求9所述的装置，其特征在于，所述第二处理单元具体用于：
    获取所述域序列中每个网络域所具有的每个域内分离路径组的路径代价，其中，所述每个网络域的每个域内分离路径组的路径代价是与所述每个网络域所对应的低层控制器根据预设的工作路径和保护路径的权重计算得到的；
    根据所述每个分离路径组的路径代价和预设的域间链路权重，计算所述每个跨域分离路径组的路径代价。
PCT/CN2017/099449 2016-11-25 2017-08-29 建立分离路径的方法和装置 WO2018095095A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611064236.7 2016-11-25
CN201611064236.7A CN108111409A (zh) 2016-11-25 2016-11-25 建立分离路径的方法和装置

Publications (1)

Publication Number Publication Date
WO2018095095A1 true WO2018095095A1 (zh) 2018-05-31

Family

ID=62194698

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/099449 WO2018095095A1 (zh) 2016-11-25 2017-08-29 建立分离路径的方法和装置

Country Status (2)

Country Link
CN (1) CN108111409A (zh)
WO (1) WO2018095095A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI710231B (zh) * 2020-02-27 2020-11-11 中華電信股份有限公司 可橫跨多個集中式控制平面的路徑品質回報方法
CN114448863A (zh) * 2022-01-06 2022-05-06 武汉烽火技术服务有限公司 一种寻找跨域路径的计算方法和装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109525910B (zh) * 2019-01-04 2021-06-08 国网四川省电力公司经济技术研究院 一种最小环的电力***保护otn网络双路径规划方法
CN114650254B (zh) * 2021-12-10 2023-10-20 中国联合网络通信集团有限公司 一种确定业务路径的方法、装置以及计算机可读存储介质
CN115242432B (zh) * 2022-06-13 2023-05-16 中国电子科技集团公司第三十研究所 一种跨域时间同步装置及方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102201993A (zh) * 2011-05-25 2011-09-28 电子科技大学 一种跨域工作路径及其保护路径的计算方法
US8750127B2 (en) * 2010-03-31 2014-06-10 Fujitsu Limited Systems and methods for multi-domain routing
CN105227461A (zh) * 2014-06-26 2016-01-06 中兴通讯股份有限公司 获取跨域分离路径的方法、路径计算单元

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8750127B2 (en) * 2010-03-31 2014-06-10 Fujitsu Limited Systems and methods for multi-domain routing
CN102201993A (zh) * 2011-05-25 2011-09-28 电子科技大学 一种跨域工作路径及其保护路径的计算方法
CN105227461A (zh) * 2014-06-26 2016-01-06 中兴通讯股份有限公司 获取跨域分离路径的方法、路径计算单元

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI710231B (zh) * 2020-02-27 2020-11-11 中華電信股份有限公司 可橫跨多個集中式控制平面的路徑品質回報方法
CN114448863A (zh) * 2022-01-06 2022-05-06 武汉烽火技术服务有限公司 一种寻找跨域路径的计算方法和装置

Also Published As

Publication number Publication date
CN108111409A (zh) 2018-06-01

Similar Documents

Publication Publication Date Title
WO2018095095A1 (zh) 建立分离路径的方法和装置
US10148517B2 (en) Systems and methods for topology discovery and application in a border gateway protocol based data center
TWI586131B (zh) 使用標籤分配協定之多重協定標籤交換技術快速重路由（ｌｄｐ－ｆｒｒ）
CN111698152B (zh) 一种故障保护方法、节点及存储介质
US9369371B2 (en) Method and system for path monitoring using segment routing
CN105453491B (zh) 扩展远程lfa快速重新路由
US8842522B2 (en) Incremental deployment of MRT based IPFRR
US11240145B2 (en) Shared risk representation in networks for troubleshooting, assignment, and propagation across layers
US8456982B2 (en) System and method for fast network restoration
US20140036729A1 (en) Label distribution and route installation in a loop-free routing topology using routing arcs
US11356356B2 (en) Permitted network risks in diverse route determinations
KR20150121241A (ko) Ip/mpls 고속 재루트 방법 및 장치
EP3065350A1 (en) Link discovery method, system and device
CN105471599B (zh) 一种保护倒换方法及网络设备
KR102157711B1 (ko) 통신 네트워크에서 장애 복구 방법
JPWO2015045466A1 (ja) 通信制御装置、通信制御システム、通信制御方法及び通信制御プログラム
CN104702431B (zh) 一种虚拟专用网双断保护的方法及装置
CN108462637A (zh) 一种路由回切方法、控制器及***
CN107294875A (zh) 用于sdn网络的带外控制***、及控制面通信方法
EP3160095A1 (en) Method and device for processing mpls load sharing
WO2011147298A1 (zh) 三层vpn路由重置方法和装置
CN106161065B (zh) 路径的保护倒换处理方法、装置、***及转发设备
WO2016101492A1 (zh) 一种业务转发表的设置方法及装置
US9007892B2 (en) Apparatus and method to find partially disjoint routes for dual fiber-cuts
LI et al. Toward software defined AS-level fast rerouting

Legal Events

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

Ref document number: 17874294

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17874294

Country of ref document: EP

Kind code of ref document: A1