+

WO1998030040A2 - Procede et dispositif pour creer des itineraires preferentiels pour le retablissement d'un reseau - Google Patents

Procede et dispositif pour creer des itineraires preferentiels pour le retablissement d'un reseau Download PDF

Info

Publication number
WO1998030040A2
WO1998030040A2 PCT/US1997/023884 US9723884W WO9830040A2 WO 1998030040 A2 WO1998030040 A2 WO 1998030040A2 US 9723884 W US9723884 W US 9723884W WO 9830040 A2 WO9830040 A2 WO 9830040A2
Authority
WO
WIPO (PCT)
Prior art keywords
routes
route
network
node
nodes
Prior art date
Application number
PCT/US1997/023884
Other languages
English (en)
Other versions
WO1998030040A3 (fr
Inventor
William D. Croslin
Original Assignee
Mci Communications Corporation
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 Mci Communications Corporation filed Critical Mci Communications Corporation
Priority to AU56206/98A priority Critical patent/AU5620698A/en
Publication of WO1998030040A2 publication Critical patent/WO1998030040A2/fr
Publication of WO1998030040A3 publication Critical patent/WO1998030040A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0062—Provisions for network management
    • H04Q3/0075—Fault management techniques
    • H04Q3/0079—Fault management techniques involving restoration of networks, e.g. disaster recovery, self-healing networks

Definitions

  • the present invention relates to analyzing communication systems, including analyzing systems for restoration after a network suffers from an unplanned outage or break in a signal path.
  • fiber optic cables have increased bandwidth over known twisted pair or copper wire cables
  • fiber optic cables are used increasingly for connecting network stations and other network elements.
  • a greater number of stations or network elements can be connected over a fewer number of fiber optic cables, as opposed to prior cables.
  • telecommunications carriers simulate possible failures, determine restoral routes and develop a "pre-plan" by collecting large amounts of data reflecting the logical topology of the network, and then analyze this data.
  • the collected data is often retrieved from network engineering databases which reflect the logical construction of the network, such as indicating the connections and paths of all network traffic trunks.
  • An engineer or network analyst analyzes the collected data, compares the collected data to the geographic or physical layout location of the network, and then generates the pre-plans therefrom.
  • Telecommunications carriers typically simulate different failure scenarios in advance of any network outages. Based on the scenarios, the telecommunications carriers establish the pre-plans that can be used at various stations of the network to establish restoral routes to recover from the network outage. Since the number of possible failures in a network necessarily increases as the size of the network increases, a large number of pre-plans are required. Furthermore, since technological improvements allow network topologies to change relatively quickly and easily, and as a network grows, such networks are not static. As a result, pre-fabricated restoral plans or pre-plans must be continually reevaluated, and new pre-plans created.
  • Dynamic restoration methods formulate a restoral route dynamically, during the restoration process and when a failure is detected, so that the method employs the most accurate and recent network data available.
  • dynamic restoration methods require extensive and time- consuming analysis during the restoration process.
  • a restoral route must be quickly created. Not only must various restoral routes be located, but an optimal restoral route must be identified in terms of its cost to the network. Determining a low cost, and thus optimal, restoral route during a failure requires extensive analysis of the entire network topology data. As a result, when a network failure occurs, the processing time required for dynamic restoration methods cause the restoration process to take longer than is typically desired by most telecommunications carriers.
  • the present invention enhances network restoration processes by providing an automated method of creating preferred restoral routes for network restoration.
  • a method and apparatus under the present invention first analyzes topology data for the network. Under an exemplary embodiment, a maximum threshold of inter-node connections is then specified and all routes under the threshold are identified. A cost or other factors are preferably assigned to each individual link, and a total cost is determined for each route. The routes are preferably ranked according to their costs. Thereafter, a preferential route table is constructed for each node in the network which identifies every other node to which it is coupled. The resulting preferred route tables can be employed by various applications, such as in dynamic restoration systems to dynamically build a restoral route on a node-to-node basis following an outage in the network.
  • the present invention embodies a method for analyzing a network.
  • the network has a plurality of nodes interconnected by links.
  • the method includes the steps of: (a) identifying sets of routes within the network, wherein each route extends between two or more nodes along one or more links and wherein each set of routes includes one or more routes that extend from a starting end node to a selected end node selected from the plurality of nodes in the network; and (b) creating an organized set of data for at least some of the starting nodes in the plurality of nodes, wherein the organized set of data represent a first link in each set of routes from each of the starting nodes to an adjacent node.
  • Figure 1 is a block diagram of a portion of a network, including a network control center.
  • Figure 2 is a block diagram of an alternative portion of the network.
  • Figure 3 is an exemplary flowchart diagram of a method for creating preferred restoral routes under the present invention.
  • Figure 4 is an exemplary flow diagram of a subroutine performed by the method of Figure 3.
  • Figure 5 is an exemplary flowchart diagram of an alternative method for creating preferred restoral routes under the present invention.
  • Figure 6 is an exemplary flowchart diagram of a subroutine performed by the method of Figure 5.
  • a telecommunications network and in particular, a method and apparatus for analyzing the network, is described in detail herein.
  • numerous specific details are set forth such as network configurations, ordering and execution of steps under an analysis routine, etc., in order to provide a thorough understanding of the present invention.
  • One skilled in the relevant art will readily recognize that the present invention can be practiced without use of the specific details described herein, or with other data formats, specific steps in a routine, etc.
  • Well-known structures and steps are not shown or described in detail in order to avoid obscuring the present invention.
  • a telecommunications network 10 includes interconnected network stations or nodes AAA, BBB, CCC. DDD, EEE, and FFF, designated as stations 12-17, respectively.
  • each node can include digital cross connect (DXC) systems, multiplexing equipment, line termination equipment, and/or fiber transmission systems.
  • DXC system is a complex digital switch capable of automatically switching trunks based on external commands.
  • a "trunk.” as generally used herein, is a logical channel of communications capacity that traverses one or more nodes and one or more links between nodes (e.g., DS-0, DS-1, DS-3, etc.).
  • Line termination equipment and fiber transmission systems typically include light-to-electricity transducers and/or multiplexers, as is known in the art.
  • communications traffic is routed between the network nodes 12-17 along trunks, and between these and other network nodes of the larger network 10 of which the portion shown in Figure 1 forms a part thereof.
  • Each node typically has a unique address or other designator in the network 10.
  • each node 12-17 is connected by control circuits 19-24, respectively, to a network management or control center 30.
  • the control circuits 19-24 may each be an X.25 circuit, which is a known circuit for carrying control communications between the associated node and the network control center 30.
  • the network control center 30 includes a computer 32 and a terminal 34 for interacting with the computer 32 which provides an interface for human interaction.
  • the network control center 30 also includes a storage facility or device 36 for storing network and circuit routing data, topology data, pre-plans, etc. Several of such network control centers 30 can be distributed throughout the network 10.
  • the network control system 30 determines the location of the outage. Under the centralized restoration system of Figure 1, the network control system 30 performs failure locating routines, such as routines described in detail in the inventor's copending U.S. patent application entitled “Method and Apparatus for Centralized Network Restoration,” filed concurrently herewith.
  • the computer 32 in a centralized restoration system retrieves from the storage facility 36 information about the impacted circuits including the paths that they follow and the equipment they pass through at different nodes along the paths. Based on this data, the network control system 30 can dynamically restore telecommunications traffic on the network despite the outage.
  • the network control center 30 implements the alternative routes in the network 10 by establishing new connections via commands transmitted through the control circuits 19-24, or alternatively, depending upon the equipment employed at the nodes 12-17, by other means of transmission to effect or direct manual actions to be taken at the nodes. For example, spare high bandwidth DS-3 trunks typically exist throughout the network 10, which can be employed to restore an outage in the network.
  • the network 10 is most effectively restored when the nodes 12-17 employ DXC systems that can automatically switch from one trunk to another based on commands from the network control center 30. Referring to Figure 2, an exemplary network portion 80 of the network
  • a “link.” as generally used herein, is a physical connection between two nodes, representing any type and any capacity of communications between the nodes.
  • a single link usually consists of multiple trunks, and a single trunk consists of one or more links that span multiple nodes. In general most high capacity networks contain far more trunks than links.
  • the network portion 80 of Figure 2 is employed below as an example of a network portion analyzed by the present invention.
  • the nodes A-H represent "restoration" nodes of the telecommunications network 10. While the network 10 typically includes various nodes, such as nodes having multiplexing equipment (e.g. , "Ml 3 nodes"), digital repeater nodes, switch nodes, etc., only certain nodes in the network are employed for network restoration. For example, nodes having DXC systems are especially useful for network restoration. Thus, nodes having DXC systems in the exemplary embodiment are restoration nodes. Other nodes that are not useful for restoration, such as nodes containing only digital repeater equipment, are "intervening nodes," and are not shown in Figure 2.
  • Each node A-H is coupled to the links shown in Figure 2 by way of ports at the nodes.
  • ports 110, 111 and 112 of node A couple to nodes F, B and E through links 120, 121, 122, all respectively.
  • ports 1 13, 1 14 and 1 15 of node E couple to nodes G, D and A through links 123, 124 and 122, all respectively.
  • a routine 200 performed by the computer 32 in the network control center 30 identifies node interconnections to thereby derive a data table that represents the links of preferred restoral routes of the network 10 based on physical topology data.
  • the table can then be used for multiple applications, such as for dynamically building restoral routes by selecting individual links of preferred routes on a node-to-node basis.
  • a dynamic restoral method allows a restoration system to maintain the speed of pre-fabricated restoral plans (pre-plans), while maintaining the accuracy of up-to-date information employed by dynamic restoration methods.
  • the tables produced therefrom can be rapidly employed by a dynamic restoration system because the time-consuming task of analyzing the network has previously been performed before the failure occurred.
  • the present invention identifies every possible restoral route in the network, within specified limitations, between each pair of nodes in the network 10.
  • the routine 200 determines the cost of each route and ranks each route between each node pair based on the cost.
  • the routine 200 then builds tables for each node that identified the preferred restoral routes, ranked by cost, to every other node. As a result, for each node, there is a table for every other node in the network that identifies restoral routes to those nodes. However, rather than specifying the entire route, the tables specify the port at a given node that transmits to the next or adjacent node of the preferred restoral route. This allows a restoral route to be built dynamically on a node-by-node basis, thereby optimizing each link as the route is built.
  • the routine 200 can be performed on a single computer of virtually any type, preferably a computer which forms part of a network restoration system, such as the computer 32.
  • the routine 200 when employed with a dynamic restoration system, is preferably performed prior to a network failure, and on a periodic basis.
  • the tables produced therefrom are based on the then current physical network topology, which changes infrequently, typically less than daily.
  • the routine 200 is performed daily, it virtually ensures that the preferred restoral routes and tables created therefrom accurately reflect the network topology when a failure occurs.
  • Such extensive analysis of the network topology performed before an outage occurs minimizes the time required during the dynamic restoration process.
  • the computer 32 retrieves restoration node topology data, such as the physical topology data for the network 10 for DXC level nodes.
  • the physical network topology defines the network in terms of its interconnected nodes, as described herein.
  • the physical topology data is preferably automatically generated prior to performing the routine 200, such as under the inventor's copending U.S. patent application entitled “Method and Apparatus for Deriving and Representing Physical Network Topology,” filed November 26, 1996 (Assignee's docket number COS-96-022).
  • the computer 32 need only employ physical topology data that identifies restoration nodes in the network and restoral routes, in addition to primary traffic routes, extending between the nodes.
  • a partial list of links, based on node connections includes:
  • a "route,” as generally used herein, is a path of communications, consisting of one or more links, between a pair of end nodes with zero or more nodes therebetween. Each pair of nodes in the network is a pair of end nodes, although some pairs of nodes may not have any possible route therebetween.
  • a partial list of routes for the network portion 80 therefore includes: A-B-C-D-E
  • the computer 32 receives the physical topology data from the storage facility 36. Thereafter, under steps 204-216, the computer 32 analyzes or processes each individual trunk in the network 10 until all nodes have been analyzed.
  • a network analyst or engineer specifies a maximum number of inter-node connections or "hops" that can be taken by a route to be considered a practical restoration route.
  • a hop traverses a node, and is equivalent to a number of links. For example, a route that traverses nodes A-F-G-E includes three links therebetween, and thus takes three hops. The maximum number of hops selected by the network analyst helps eliminate restoral routes that are too costly.
  • the computer 32 identifies all physical routes between every node pair in the network 10 that are within the threshold specified under step 204.
  • the computer 32 can employ alternative or additional rules when identifying physical routes. For example, the computer 32 can eliminate any routes that include retracing a link or "backhaul."
  • An example of a backhaul is a route that traverses nodes A-B-F-B- C.
  • the backhaul from node F to node B can be possible because of multiple trunks on the link between nodes B and F, so that a route extends from node B to node F on one trunk, and then back to node B on another trunk. However, it is typically neither desirable nor useful for a restoral route to have backhaul. Additionally, or alternatively, the computer 32 can select only certain routes that form all or part of selected network configurations, such as routes having pass-through nodes, stranded network non-rings or rings, etc. A method of determining such network configurations is described in the inventor's U.S.
  • the computer 32 in step 206 processes the topology data retrieved in step 202 to identify every possible route among restoration nodes within the maximum hop threshold and/or other rules. For example, with the maximum hop threshold established at 4 and omitting backhaul, the computer 32 in step 206 identifies all routes between end nodes A and E as follows:
  • step 206 the computer 32 also determines all routes between every other node pair in the network.
  • the computer 32 determines and applies a cost to each individual link in the network.
  • the particular definition and determination of costs can vary in a given network, and should meet the needs of the restoration system. Examples of common factors used to determine costs include: capacity of a link, distance traversed by a link, equipment used at nodes or along the link, priority of traffic supported by the link, types of traffic supported by the link, and a number and type of intervening nodes along a link or route. Other factors, of course, can be employed. By employing all of these factors, the computer 32 associates a cost with each link in the network 10.
  • each link can support several trunks, where each trunk uses an individual port at each node.
  • a DXC level network such as a DXC 3/3 level network where DS-3 trunks entering and exiting the node are switched by the DXC system.
  • Multiple DS-3 trunks can traverse a single link, thereby causing the link to use multiple ports at each node.
  • each port can be associated with a different cost, even though the ports are associated with a single node and a single link. Consequently, computer 32 in step 208 applies a separate cost to each port.
  • the link 121 between nodes A and B supports 10 DS-3 trunks on a single optical fiber transmission system, then there will be 10 ports on each of the nodes A and B.
  • the link 121 is demultiplexed and input to 10 separate ports.
  • Each of such 10 DS-3 trunks can have equivalent priority and designation, and therefore have the same cost.
  • some of the 10 trunks on the link 121 can have a different priority or designation than the other trunks. Therefore, their costs will differ.
  • the computer 32 in step 208 assigns a separate cost to each of the 10 trunks in the link 121, as well as the other links in the network 10.
  • the computer 32 applies a total cost to each route identified in step 206.
  • the computer 32 sums the costs of each individual link traversed by the given route.
  • the cost of the route is therefore simply the sum of the costs of its constituent links. If multiple costs are associated with a link, due to multiple ports on that link as noted above, then multiple routes with its own costs are defined. For example, the route A-E-G-E will be identified or listed twice, and have two costs associated with the same route, if multiple costs are associated with links in this route.
  • the computer 32 ranks all of the identified routes in order of ascending costs. Therefore, the least costly route is ranked first, while the most costly route is ranked last. Other methods of ranking the routes can be performed.
  • the computer 32 builds a set of tables for each node in the network 10. Each node will thus have a table for every other node in the network. For example, the computer 32 under the subroutine 214 builds a set of tables for the node A that consists of a table for node B, a table for node C, and so on, through to a table for node H. Each table is a "preferred route table" that identifies the routes, in order of preference (ascending costs), from a given node (a first end node) to another end node. Each table preferably specifies only the port that supports each route to that end node. For example, if the given node currently analyzed is node A, and first and second preferred routes between the node A and the end node E are:
  • node A's table for routes to node E will specify first the port at node A that supports the link to node F for the first route (i.e., port 110), and second, the port that supports the link 122 to node E (i.e., port 112).
  • the process of building such preferred route tables is described below with respect to Figure 4.
  • Preferred routes differ from “absolute routes.”
  • An absolute route includes a complete node-to-node listing for the restoral route.
  • Preferred or preferential routes compress restoral route definitions to simply a port which directs a given node to an adjacent node on a restoral route.
  • the adjacent node may include a different preferred routing to the same end node.
  • dynamic restoration methods can optimize decisions at each node for a restoral route.
  • step 216 the routine 200 ends after the computer 32 has built all preferred route tables for each node, and stored such tables in the storage facility 36.
  • the storage facility 36 contains a set of tables for each node in the network 10.
  • Each set of tables identifies the preferred routes from a given end node to every other end node, with one table for each other end node. Therefore, considering only the network portion 80, the node A would include seven tables for routes to each of nodes B-H. The preferred route to each of such end nodes is identified by only the port at the given node to which the table belongs.
  • step 302 the computer 32 selects the first route from the list created under step 206 and ranked in step 212.
  • step 304 the computer 32 identifies the end node pairs for the selected route. For example, if the first route selected in step
  • the end node pair identified in step 304 is A/E.
  • step 306 the computer 32 processes through the entire list of routes and identifies all routes for the end node pair identified in step 304.
  • all routes for the end node pair A/E for the network portion 80 are included in Table 3, reprinted below:
  • the computer 32 in step 306 flags each identified route as processed. As a result, each of such routes identified under step 306 is not processed again under a further iteration of the subroutine 214.
  • step 308 the computer 32 ranks the routes identified under step 306 according to their associated costs. Such a ranking of the routes will typically be in the same order in which all the routes were ranked under step 212.
  • step 310 the computer 32 builds a table for the first end node in the preferred routes to the second end node that was identified in step 306.
  • the table specifies the ports that begin each route from the given node which begins the route.
  • the table for preferred routes from the node A to the node E will be as follows.
  • each port is only listed once in Table 4. Even though node A's link to node B begins the first three preferred routes in Table 3, port 1 1 1 is only listed once in the above table. As a result, if the link 121 to node B fails, then node A will use the next port in Table 4 (i.e., port 110), to establish a link with the node F under the fourth preferred route of Table 3. If multiple ports support a single link, then the computer 32 under step
  • step 310 lists each of these ports in order of preference. For example, if the link 121 between nodes A and B consists of three DS-3 level trunks, then each of these trunks is supported on node A by ports 220, 221 and 222 (not shown). As a result, the computer 32 in step 310 ranks these ports by ascending cost in step 208 as follows:
  • step 310 the computer 32 builds the table for node A as follows: 1. Port 222
  • step 312 the computer 32 constructs a table for the second end node to reflect the preferred routes to the first end node.
  • the table corresponds to node E for the routes to node A.
  • the preferred routes are identical, and in the same order, as those established under step 308.
  • the table specifies the ports at the second node that begin each of these routes.
  • the table for the ports that begin each route from node E to node A will be as follows:
  • port 1 14 begins each of the first through third preferred routes under Table 3 from node E to node A, if node D fails, then none of the first through third preferred routes will be used.
  • step 314 the computer 32 determines if any additional routes remain in the network 10. Such routes will be unflagged and not have been analyzed under the routine 200. If additional unflagged routes exist, then the computer 32 again performs the steps 302-314 until all routes in the network 10 have been processed. Thereafter, each node in the network 10 will have a table of preferred routes, listed by port, for every other node in the network.
  • an alternative embodiment of the routine 200 is shown as a routine 200'. The alternative embodiment is similar to the previously described routine 200, and all steps are similarly numbered when of similar operation. Only significant differences in operation are discussed in detail.
  • step 207 the computer 32 maps all routes identified under step 206 to end node pairs.
  • each of the routes identified under step 206 are listed by their end node pairs, rather than ranking the routes in terms of their costs as performed under step 212.
  • step 212 of the routine 200 is not performed under the alternative routine 200'.
  • the computer 32 under a subroutine 215 builds preferred route tables based on the listed node pairs determined under step 207.
  • the remaining steps of 202, 204, 206. 208, 210 and 216 under the alternative routine 200' are substantially similar to the steps described above.
  • the subroutine 215 is an alternative embodiment to the subroutine 214 of Figure 4.
  • the subroutine 215 builds preferred route tables from a route list in which each route is listed as a pair of end nodes, rather than by cost, as noted above.
  • the computer 32 still applies a cost to each of the routes under step 210.
  • step 502 the computer 32 selects the first node pair determined under step 207 of the routine 200'.
  • step 504 all routes for the selected node pair are identified and flagged as processed. As a result, the computer 32 under the subroutine 215 will not process those routes twice. Since all routes for a given node pair are already grouped under the routine 200', the computer 32 can readily perform step 504.
  • step 506 the computer 32 ranks the routes for the selected node pair by cost. Thereafter, under steps 508, 510 and 512. the computer 32 performs substantially the same operations as performed under steps 310, 312 and 314. respectively, for the subroutine 214.
  • the resulting route tables constructed by the computer 32 under the routines 200 and 200' specify, in preferred descending order based on ports, the preferred routes from one node to every other node in the network.
  • Each node in the network 10 will have one table for every other node in the network.
  • a "table" corresponds to any organized set of data.
  • the computer 32 can store the data (ports and their ranking for each node) in an appropriate database for use by other routines as described herein.
  • the tables reflect the preferred restoral routes of the network 10.
  • the resulting data can then be output and used in a variety of applications, such as applications that analyze the network 10 and require data reflecting preferred routes through the network.
  • applications that analyze the network 10 and require data reflecting preferred routes through the network.
  • the resulting data can be used to efficiently and quickly establish restoral routes within the network 10 following a failure, such as by employing the inventor's above-noted copending U.S. patent application.
  • Such U.S. patent application describes centralized network restoration.
  • the preferred node tables derived under the present invention can be employed with normalizing the network following a restoration, such as is described in the inventor's copending U.S. patent application entitled "Method and Apparatus for Automated Node-Based Normalization After Restoration," filed concurrently herewith.
  • the preferred route tables can be stored at the nodes themselves in appropriate storage facilities.
  • the DXC systems at the nodes in the network portion 80 of Figure 2 preferably include data storage and data processing equipment. Therefore, the data tables for node A can be stored in the data storage facility at node A. and so forth, for the remaining nodes in the network 10.
  • a distributed dynamic restoration method can be more readily performed such as that described in the co-inventor's copending U.S. patent application entitled "Method and Apparatus for Distributed Network Restoration Using Preferred Routes,” filed concurrently herewith.
  • a combined centralized and distributed restoration method can employ the resulting preferred route tables produced under the present invention, such as the inventor's copending U.S. patent application entitled "Method and Apparatus for Integrating a Centralized and Distributed Network Restoration System," filed concurrently herewith.
  • the granularity of the analysis performed under the routines 200 and 200' by the computer 32 can vary.
  • the present invention has generally been described above as analyzing only links with high bandwidth DS-3 trunks between DXC nodes.
  • the granularity of the analysis performed under the routines 200 and 200' can be increased so as to analyze lower bandwidth links, having, e.g., DS-1 trunks, to thereby recognize additional inter-node connections.
  • the physical topology of the network 10 changes infrequently, possibly once a year, as new links are established in the network.
  • Logical topology changes more frequently, such as the rerouting of a traffic trunk, but such rerouting generally does not impact the physical topology. Therefore, the computer 32 preferably performs the routine 200 or 200' regularly, such as on a daily basis. As a result, the chance of erroneously deriving preferred route tables from the physical topology of the network 10 is very small, despite frequent rerouting of traffic trunks, etc.
  • the present invention analyzes network topology data prior to a failure occurring within the network 10, and provides the results of such analysis in the form of preferred restoral route tables.
  • the system thereby has the accuracy of typical dynamic restoration processes with the speed of pre-fabricated restoration plans.
  • the present invention provides this benefit by creating restoral routes in order of preference, in which preference is generally determined by the cost of each route, but can include other factors.
  • the restoral routes are then represented in preferred route tables as single links from each node, based on ports at that node, so that the dynamic restoration system can dynamically build a restoral route using predetermined preferred links. While prior dynamic restoration systems require that the network topology data be analyzed at the time of restoration, and during a failure, the present invention allows the dynamic restoration system to build a restoral route by simply selecting a series of preferred links.
  • the present invention can receive network topology data based on communication links and nodes of any type and capacity from which the present invention generates preferred routing tables.
  • link is defined above as routing telecommunications traffic
  • the present invention can analyze any communication channel or path between two nodes and 0 or more intervening nodes and employ any topology data representing such channels or paths, as will be understood by those skilled in the relevant art.
  • node applies to any point receiving or transmitting signals, not necessarily a DXC system or other telecommunications equipment coupled between two trunks.

Landscapes

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

Abstract

Procédé et dispositif pour analyser un réseau de télécommunication et fournir des données dérivées d'une telle analyse. Ce procédé consiste en premier lieu à extraire des données topologiques pour le réseau, puis à spécifier un seuil maximum pour les connexions entre noeuds, et à identifier tous les itinéraires se situant en dessous de ce seuil. Un coût est attribué à chaque chaînon individuel et un coût total est défini pour chaque itinéraire. Une table pour les itinéraires préférentiels est ensuite établie pour chaque noeud du réseau, identifiant chacun des autres noeuds auquel le noeud est relié. Les tables résultantes pour les itinéraires préférentiels peuvent ainsi être employés par des systèmes de rétablissement dynamiques pour l'établissement dynamique noeud par noeud d'un itinéraire de rétablissement à la suite d'une interruption survenue dans le réseau.
PCT/US1997/023884 1996-12-31 1997-12-30 Procede et dispositif pour creer des itineraires preferentiels pour le retablissement d'un reseau WO1998030040A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU56206/98A AU5620698A (en) 1996-12-31 1997-12-30 Method and apparatus for creating preferred routes for network restoration

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US77787796A 1996-12-31 1996-12-31
US08/777,877 1996-12-31

Publications (2)

Publication Number Publication Date
WO1998030040A2 true WO1998030040A2 (fr) 1998-07-09
WO1998030040A3 WO1998030040A3 (fr) 1998-09-11

Family

ID=25111578

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1997/023884 WO1998030040A2 (fr) 1996-12-31 1997-12-30 Procede et dispositif pour creer des itineraires preferentiels pour le retablissement d'un reseau

Country Status (2)

Country Link
AU (1) AU5620698A (fr)
WO (1) WO1998030040A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001035289A1 (fr) * 1999-11-10 2001-05-17 Pricing Research Corporation Procede et systeme de gestion des recettes
US8571903B1 (en) 1998-07-02 2013-10-29 Google Inc. Pricing graph representation for sets of pricing solutions for travel planning system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1995010149A2 (fr) * 1993-10-07 1995-04-13 British Telecommunications Public Limited Company Modele de protection de reseau
US5459716A (en) * 1994-04-15 1995-10-17 Mci Communications Corporation Facility restoration for telecommunications networks
US5463615A (en) * 1994-07-07 1995-10-31 At&T Corp. Node failure restoration tool

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8571903B1 (en) 1998-07-02 2013-10-29 Google Inc. Pricing graph representation for sets of pricing solutions for travel planning system
WO2001035289A1 (fr) * 1999-11-10 2001-05-17 Pricing Research Corporation Procede et systeme de gestion des recettes

Also Published As

Publication number Publication date
AU5620698A (en) 1998-07-31
WO1998030040A3 (fr) 1998-09-11

Similar Documents

Publication Publication Date Title
US5881048A (en) Method and apparatus for determining maximum network failure spans forrestoration
US6075766A (en) Method and apparatus for identifying restoral routes in a network
US5995485A (en) Method and apparatus for isolating network failures by correlating paths issuing alarms with failure spans
US5991264A (en) Method and apparatus for isolating network failures by applying alarms to failure spans
WO1998024220A9 (fr) Procede et dispositif servant a isoler des pannes de reseau par mise en correlation de trajets emettant des alarmes avec des liaisons en derangement
US6047331A (en) Method and apparatus for automatic protection switching
US5459716A (en) Facility restoration for telecommunications networks
US5812524A (en) Deterministic selection of an optimal restoration route in a telecommunications network
US6018576A (en) Method and apparatus for automated node-based normalization after network restoration
US6728205B1 (en) Method and apparatus for automatic protection switching
US6564258B1 (en) Detection of network topology changes affecting trail routing consistency
US5942989A (en) Automatic path setting apparatus for a synchronous communication system
US6314092B1 (en) Routing in a communications network
US7668184B2 (en) Method and system for designing ring-based telecommunications networks
US5941992A (en) Distributed method and system for excluding components from a restoral route in a communications network
US5404451A (en) System for identifying candidate link, determining underutilized link, evaluating addition of candidate link and removing of underutilized link to reduce network cost
WO1998029997A9 (fr) Procede et dispositif pour la normalisation automatique en fonction des noeuds apres le retablissement d'un reseau
US6052796A (en) Method and system for augmenting communications network with spare capacity
US6754208B2 (en) Traffic spreading to reduce blocking in a groomed CLOS communication switch
US5883881A (en) Method for selecting preferred nodes for distributed network restoration
Wilson The quantitative impact of survivable network architectures on service availability
WO1998029999A9 (fr) Procede et systeme de selection de noeuds preferes permettant le retablissement d'un reseau reparti
US20030009598A1 (en) Method for designing demand-sensitive rings
WO1999000995A2 (fr) Procede et systeme de preconnexion d'un reseau de communications
WO1998030040A2 (fr) Procede et dispositif pour creer des itineraires preferentiels pour le retablissement d'un reseau

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AU CA JP MX

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载