Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
• • 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/52—Multiprotocol routers

Definitions

• the present invention relates to the management of communications networks and, in particular, to the selection for packet switch router use within a system intranet of a traffic tailored routing method and bearer type.
• communications networks have been designed as tightly coupled systems wherein one traffic type, one cell switch routing method, and one switch interconnecting bearer type are linked together to define and provide communications service through the network.
• a communications network being designed to primarily handle voice traffic may utilize a completely different selection of routing method and bearer type than a network being designed to primarily handle data
• the routing method selected for use on that bearer type is typically chosen to complement the carried traffic type on that specific bearer.
• Packet switch routing nodes are interconnected to form a system intranet communications network. These interconnections between the packet switch routers are made through the use of a plurality of different types of bearers. Furthermore, each packet switch router supports the use of a plurality of routing methods over the available bearer types.
• a system intranet transport controller monitors intranet performance indicators relating to handling the carried traffic and characterizes the current state of system intranet health. Based on this evaluation of system intranet health, the system intranet transport controller selects the particular type(s) of bearer(s) to be interface supported at each packet switch router, and also selects the particular routing method(s) to be utilized by each packet switch router, to best match traffic needs.
• FIGURE 1 is a block diagram of a client/server environment wireless communications network in accordance with the present invention
• FIGURE 2 is a flow diagram of the routing method/bearer traffic tailored selection process of the present invention.
• FIGURE 1 wherein there is shown a block diagram of a client/server environment wireless communications network in accordance with the present invention, and also to FIGURE 2 wherein there is shown a flow diagram of the routing method/bearer traffic tailored selection process of the present invention.
• the clients 10 comprise a plurality of base stations 12 that support subscriber communications over an air interface 14 with a plurality of mobile stations 16.
• the server 18 comprises a mobile switching center
• gateway operations 24 for interfacing the network to the Internet or an intranet
• service provision 26 for supporting subscriber access to services such as, for example, voice mail, intelligent networking (IN), and the like.
• Interconnecting the clients 10 to the server 18 is a core network 30 comprised of a plurality of edge routers 32 supporting connections to the base stations 12 and the mobile switching center 20, and a plurality of packet switch routers 34 that are interconnected 36 in at least an almost fully-meshed network configuration to provide a system intranet 38. Some of the packet switch routers 34 within the intranet support connections to the edge routers 32.
• the interconnection 36 between packet switch routers within the system intranet 38 on a physical layer (OSI layer 1) is made through interfaces 40 to a selected one or ones of an available plurality of bearer types.
• bearer or “bearer type” refers to a means by which packet based communications in a bidirectional symmetric, bidirectional asymmetric or unidirectional fashion are established using a channel connection (either virtual or material).
• a first portion (perhaps all) of pairs of packet switch routers 34 within the system intranet may be interconnected through their interfaces 40 using a first bearer type such as a T1/T3 link, while a second portion (some the same as the first portion) of pairs of packet switch routers may be interconnected through their interfaces using a second bearer type such as a fiber optic link.
• first and second types of bearers may be any suitable packet switch router interconnecting bearer types (other examples include: unshielded twisted pair, SONET and the like).
• Each packet switch router 34 is further capable of implementing one or more different routing methods (at OSI layer 3) such as: open shortest path first (OSPF), border gateway protocol (BGP), private network-to- network interface (PNNI), interior gateway routing protocol (IGRP), routing info protocol (RIP), and the like (including their variants), for use in routing packets over the selected available bearers.
• OSPF open shortest path first
• BGP border gateway protocol
• PNNI private network-to- network interface
• IGRP interior gateway routing protocol
• RIP routing info protocol
• the network further includes a system intranet transport controller 50 (perhaps implemented in the form of an expert system) that operates to select routing method(s) and bearer(s) based on (and to accommodate) not only traffic needs within the system intranet but also network operator preferences.
• a system intranet transport controller 50 (perhaps implemented in the form of an expert system) that operates to select routing method(s) and bearer(s) based on (and to accommodate) not only traffic needs within the system intranet but also network operator preferences.
• the transport controller 50 might implemented in the form of an expert system that operates to select routing method(s) and bearer(s) based on (and to accommodate) not only traffic needs within the system intranet but also network operator preferences.
• performance control functionality 52 that constantly monitors network (and perhaps more particularly system intranet) performance indicators such as throughput, utilization, end-to-end delay, packet delay variation, insertion delay, label space usage, and the like, that are indicative of traffic need. These indicators are, generally speaking, derived by the functionality 52 from performance related data supplied thereto by the packet switch routers 34 in the normal course of their operation (step 100). From the derived performance indicators, the functionality 52 then characterizes the current (and predicted future) state of system intranet health (step 102), perhaps through the use of an evaluator algorithm. The generated characterization of system intranet health may take the form of an overall system intranet performance index.
• the index may be derived as follows:
• the edge routers of the network periodically send, for example, an update of their label space usage (in terms of percent), insertion delay (in terms of seconds) and cumulative throughput (in terms of bits per second) on a per label switched path basis.
• this information is provided through the use of "heartbeat" messages (background signaling).
• the performance control functionality takes a sample of these indicators on a periodic basis (such as once every thirty seconds) and applies the following exemplary algorithm to determine the index: a 1 *
• the process implemented by the performance control functionality 52 first collects from the packet switch routers certain sampled statistics concerning, for example, throughput, end-to-end delay and utilization. Next, these sampled statistics are processed through a parser and then the evaluator algorithm to identify whether the system intranet is operating well. Lastly, a conclusion is reached based on that operating condition identification of an index (or other suitable measure) reflecting the operating status of the physical network. This index is generated on a regular basis, and is then processed (as will be described in more detail below) to correct, over the long-term, the physical set up (i.e., routing method and bearer type) of the system intranet to be more closely tailored to traffic needs.
• index or other suitable measure reflecting the operating status of the physical network. This index is generated on a regular basis, and is then processed (as will be described in more detail below) to correct, over the long-term, the physical set up (i.e., routing method and bearer type) of the system intranet to be more closely tailored to traffic needs.
• the transport controller 50 further includes a control signal routing functionality 54 that operates to choose for the system intranet, and more particularly for each of the individual packet switch routers 34, the particular one or ones of the supported plurality of routing methods to be used (step 104). This selection is made by the functionality 54 based on an evaluation of the characterization of system intranet health (e.g., the derived overall system intranet performance index) and network operator routing method preferences. For example, given an index of +12 (as determined above), an operator preference for RIP and the availability of IGRP and RIP, an exemplary rule system could give priority to the operator's RIP preference since the index of +12 is favorable. Conversely, given an index of -20 (as determined above), an operator preference for RIP and the availability of IGRP and RIP, that exemplary rule system would yield IGRP since its impact on routing updates is less than the impact caused by RIP.
• a control signal routing functionality 54 that operates to choose for the system intranet, and more particularly for each of the individual packet switch routers 34, the particular one
• the system intranet transport controller 50 Responsive to a selection made by the functionality 54, the system intranet transport controller 50 issues the requisite control signals and messages to the packet switch routers 34, and the routers respond by making the appropriate selection.
• the system intranet transport controller 50 still further includes a content transport functionality 56 that operates to choose, for each packet switch router 34, the best bearer or combination of bearers, selected from the plurality of interface 40 supported bearers, for use in physically interconnecting each pair of packet switch routers for communication (step 106). This selection is made by the functionality 56 based on an evaluation of the characterization of system intranet health (e.g., the derived overall system intranet performance index as set forth above), the selected routing method and network operator bearer preferences in accordance with certain configuration rules.
• the characterization of system intranet health e.g., the derived overall system intranet performance index as set forth above
• the bearers UTP, SONET, Tl and fiber may be available with the routing protocols of IGRP, OSPF and RIP.
• the configuration rules would dictate a change because RIP/T1 performance is unstable (as indicated by the index at 0). Most likely this is due to many routing updates performed in RIP and the quiescent bit rate of Tl that forces retransmissions of those routing updates.
• the configuration rules in this instance may select OSPF for the routing protocol and a fiber bearer for the long term in order to regain stability.
• the system intranet transport controller 50 issues the requisite control signals and messages to the packet switch routers 34, and the routers respond by enabling the appropriate OSI layer 1 interfaces 40 to establish interconnections within the system intranet using the specified bearer or combination of bearers.
• system intranet transport controller 50 is illustrated as a discrete node within the network, it will, of course, be understood that such need not be the case.
• a preferred embodiment of the present invention implements the system intranet transport controller 50 as a software/hardware module that resides in various different physical nodes within the network (or system intranet).
• the transport controller may reside in both types of the edge and packet switched routers.
• Expert systems contain a knowledge base and an inference engine.
• the knowledge base contains the specific domain knowledge (or facts), and the inference engine controls the reasoning process and user interface.
• the expert system implements the actions of steps 104 and 106 wherein the routing methods and bearers are selected and then configured at certain ones of the packet switch routers 34. Configuration of such an expert system to make optimization decisions is well within the capabilities of one skilled in the arts of artificial intelligence and expert system design.
• the inference engine is capable of selecting both routing method and bearer type for the network in order to provide an optimized configuration for current traffic needs.

Landscapes

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

Applications Claiming Priority (3)

Publications (1)

Family

ID=23758430

Family Applications (1)

Country Status (7)

Families Citing this family (5)

Family Cites Families (4)

• 2000
  • 2000-10-24 TW TW089122310A patent/TW522679B/zh not_active IP Right Cessation
  • 2000-10-27 WO PCT/SE2000/002111 patent/WO2001037508A2/en active Application Filing
  • 2000-10-27 EP EP00978150A patent/EP1230762A2/en not_active Withdrawn
  • 2000-10-27 CA CA002400999A patent/CA2400999A1/en not_active Abandoned
  • 2000-10-27 KR KR1020027006218A patent/KR20020067517A/ko active IP Right Grant
  • 2000-10-27 CN CNB008159270A patent/CN1163026C/zh not_active Expired - Fee Related
  • 2000-10-27 AU AU15636/01A patent/AU1563601A/en not_active Abandoned

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events