WO2005050933A1 - Surveillance de chemin point a point dans un reseau central en mode paquet - Google Patents

Surveillance de chemin point a point dans un reseau central en mode paquet Download PDF

Info

Publication number
WO2005050933A1
WO2005050933A1 PCT/US2004/036944 US2004036944W WO2005050933A1 WO 2005050933 A1 WO2005050933 A1 WO 2005050933A1 US 2004036944 W US2004036944 W US 2004036944W WO 2005050933 A1 WO2005050933 A1 WO 2005050933A1
Authority
WO
WIPO (PCT)
Prior art keywords
point
route
packet
gateway system
core network
Prior art date
Application number
PCT/US2004/036944
Other languages
English (en)
Inventor
Michael K. Bugenhagen
Original Assignee
Sprint Communications Company, L. P.
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 Sprint Communications Company, L. P. filed Critical Sprint Communications Company, L. P.
Publication of WO2005050933A1 publication Critical patent/WO2005050933A1/fr

Links

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H04L12/5601—Transfer mode dependent, e.g. ATM
    • H04L2012/5629—Admission control
    • H04L2012/5631—Resource management and allocation
    • H04L2012/5636—Monitoring or policing, e.g. compliance with allocated rate, corrective actions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H04L12/5601—Transfer mode dependent, e.g. ATM
    • H04L2012/5638—Services, e.g. multimedia, GOS, QOS
    • H04L2012/5665—Interaction of ATM with other protocols
    • H04L2012/5669—Multiprotocol over ATM [MPOA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • H04L43/0829—Packet loss
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0882—Utilisation of link capacity

Definitions

  • the invention is related to the field of communication systems, and in particular, to point-to-point route monitoring in a packet-based core network.
  • the core network for communication providers such as Sprint, AT&T, and MCI Worldcom
  • a core network is typically defined as a combination of high-capacity switches and transmission facilities which form the backbone of a carrier network.
  • Network designers have improved the capacity provided by the circuit-based core networks over the years to try to meet the high-speed demands.
  • Network designers have also conceptualized a packet-based core network to add to or replace the circuit-based core network.
  • the packet-based core network may further increase the capacity currently provided by the communication providers.
  • a circuit-based core network is comprised of switches that are connected by physical connections (i.e., T-l, DS-3, OC-1). The physical connections make up the bearer paths for the transport of voice and data.
  • the circuit-based core network also includes a signaling network for transporting SS7 signaling or another signaling protocol.
  • a circuit- based core network continually performs status checks on the physical connections to warn the switches of transport failures or faults, high volume call events, overloaded connections, and other conditions before calls are received into the switches.
  • the circuit-based core network uses alarming to proactively monitor the network.
  • Proactively monitoring the network means that the monitoring is continually or periodically performed and is not necessarily responsive to an incoming call or on a per-call basis.
  • the monitoring continually takes place based on a clock signal.
  • the circuit- based core network may use red and yellow alarming to monitor the network.
  • a near end switch Over a T-l line, a near end switch periodically transmits test bits over one or more channels of the T-l line to a far end switch. The test bits are not transmitted in response to an incoming call, but are transmitted periodically.
  • the near end switch also sets a timer. If the near end switch does not receive an acknowledgement from the far end switch within a particular time period, then the near end switch indicates an alarm.
  • the alarm may be a yellow alarm, which typically indicates if a piece of equipment has suffered a critical fault.
  • the near end switch may also indicate a red alarm if it detects a local failure, such as a condition where loss of synchronization exists for 2.5 seconds from the TDM transport protocol (i.e., T-l, DS-3, etc). Responsive to detecting a transport failure or other fault, the switch can apply the proper call treatment (i.e., a busy signal) for calls before the call is set up, which saves processing time in the switch. Because the circuit-based core network is periodically monitored and the status of the physical connections is fed back to the switches, the switches can better handle incoming calls instead of setting the calls up and then detecting failures of call setup.
  • the packet-based core networks that have been conceptualized utilize a fundamental packet protocol for communication, such as Internet Protocol (IP), Asynchronous Transfer Mode (ATM), Frame Relay, X.25, or another protocol.
  • IP Internet Protocol
  • ATM Asynchronous Transfer Mode
  • MPLS Multi-Protocol Label Switching
  • Packet networks generally route based on virtual connections, routes, paths, etc, instead of physical connections. For instance, in native IP, a file is broken up into multiple IP packets with each packet stamped with an IP address for a destination. As the packets are transmitted, each packet may take a different route through the network to the destination. There is not a particular physical connection assigned to transport the packets and there may not be a particular route provisioned through the network to transport the packets.
  • a packet switch For connectionless protocols like this, there is currently no effect way to proactively monitor routes through the network and provide information on the routes to the switches in the network.
  • a packet switch has to receive a call before the switch is able to determine the status of a route.
  • the packet switch determines the status of a route on a per-call basis.
  • a packet switch determines if the route is available to transport packets. If the route is available, then the packet switch transmits the packets over the route. If the route is not available, then the packet switch provides a call treatment (i.e., a busy signal) to the caller and terminates the call.
  • Some packet protocols provide a point-to-point route that is provisioned through the network, such as a Virtual Private Network (VPN). The point-to-point route through the network associates one node in the network to another node in the network.
  • VPN Virtual Private Network
  • LSP Labeled Switch Path
  • SVC Switched Virtual Circuit
  • PPTP Point-to-Point Tunneling Protocol
  • IP IP
  • Software exists that is able to monitor the state or capacity of point-to-point routes, such as Element Management Software (EMS) used to monitor VPNs.
  • EMS Element Management Software
  • NOC National Operations Center
  • the state information is not currently used to inform packet switches of problems before the packet switches receive calls.
  • the packet switch is not able to determine if there is a problem with a route before attempting to set up the call over the route.
  • the packet switch has to determine the status of a route on a call-by-call basis. This results in inefficient use of processing time in the packet switch.
  • Packet networks do not currently have proactive monitoring and feedback to more efficiently utilize the packet switches.
  • the invention helps solve the above problems by proactively monitoring a packet- based core network and providing feedback information on point-to-point routes in the packet-based core network.
  • a communication network that includes a packet-based core network, gateway systems, and a monitoring system.
  • the packet-based core network includes a plurality of edge routing systems.
  • a point-to-point route is used for communication between a first edge routing system and a second edge routing system.
  • a first gateway system is configured to provide an ingress point to the packet-based core network and connects to the first edge routing system.
  • a second gateway system is configured to provide an egress point from the packet-based core network and connects to the second edge routing system.
  • the monitoring system receives information on the point-to-point route from the packet-based core network.
  • the information on the point-to-point route may include a status or state of the route, degradation of the route, path loss on the route, available bandwidth on the route, etc.
  • the monitoring system processes the information on the point-to-point route, an identifier for the first gateway system, and an identifier for the second gateway system to generate feedback information.
  • the feedback information associates the information on the point-to-point route with the identifier for the first gateway system and the identifier for the second gateway system.
  • the identifier for the first and second gateway systems may comprise point codes, Carrier Identification Codes (CIC), port numbers, etc.
  • the monitoring system then transmits the feedback information to the first and second gateway systems.
  • the first and second gateway systems process the feedback information to handle future calls.
  • the first and second gateway systems may process the feedback information to update call routing tables. Because the monitoring system proactively monitors the point-to-point route and provides feedback information to the gateway systems, the gateway systems can better handle calls when they are received. Instead of having to determine the status of the point- to-point route on a call-by-call basis as is currently done, the gateway systems advantageously know the status of the point-to-point route at the time the calls are received.
  • a monitoring system in the communication network that includes an interface system and a computer system.
  • the interface system receives the information on the point-to-point route from the packet-based core network, and forwards the information on the point-to-point route to the computer system.
  • the computer system processes the information on the point-to-point route, the identifier for the first gateway system, and the identifier for the second gateway system to generate feedback information.
  • the feedback information associates the information on the point-to-point route with the identifier for the first gateway system and the identifier for the second gateway system.
  • the computer system then forwards the feedback information to the interface system.
  • the interface system transmits the feedback information to the gateway systems.
  • the invention may include other embodiments described below.
  • FIG. 1 illustrates a communication network having point-to-point route monitoring in an embodiment of the invention.
  • FIG. 2 is a flow chart illustrating a method of operation of the communication network in FIG. 1 in an embodiment of the invention.
  • FIG. 3 illustrates a monitoring system in an embodiment of the invention.
  • FIG. 4 illustrates a communication network having tunnel monitoring and feedback in an embodiment of the invention.
  • FIGS. 1-4 and the following description depict specific embodiments of the invention to teach those skilled in the art how to make and use the best mode of the invention.
  • some conventional aspects of the invention have been simplified or omitted.
  • Those skilled in the art will appreciate variations from these embodiments that fall within the scope of the invention.
  • Those skilled in the art will appreciate that the features described below can be combined in various ways to form multiple variations of the invention. As a result, the invention is not limited to the specific embodiments described below, but only by the claims and their equivalents.
  • FIG. 1 illustrates a communication network 100 having point-to-point route monitoring in an embodiment of the invention.
  • Communication network 100 includes a packet-based core network 102, gateway systems 104-105, and monitoring system 110.
  • Packet-based core network 102 includes a plurality of edge routing systems 121-122. Communication network 100 may include other devices or systems not shown for the sake of brevity.
  • Monitoring system 110 is coupled to gateway systems 104-105. Monitoring system 110 is also coupled to packet-based core network 102, in which it may communicate with multiple edge routing systems 121-122, other routing systems, switches, or other nodes within packet-based core network 102.
  • Gateway system 104 is coupled to edge routing system 121 and gateway system 105 is coupled to edge routing system 122.
  • point-to-point route 124 is used for communication between edge routing system 121 and edge routing system 122.
  • Packet-based core network 102 comprises any network that transports packets or cells for communication between nodes.
  • Packet-based core network 102 may use any packet-type protocol, such as Internet Protocol (IP), Asynchronous Transfer Mode (ATM), Frame Relay, or X.25. Packet-based core network 102 may include many other routing systems and point-to-point routes other than those shown in FIG. 1.
  • Gateway systems 104-105 comprise any systems, components, or devices that interwork calls from one format to another format. For instance, gateway systems 104-105 may interwork calls from a synchronous communication format to an asynchronous communication format, such as from Time Division Multiplex (TDM) communications to IP packets, or from TDM communications to ATM cells.
  • TDM Time Division Multiplex
  • gateway system 104 is configured to provide an ingress point to packet-based core network 102
  • gateway system 105 is configured to provide an egress point from packet-based core network 102.
  • gateway systems 104-105 may be configured to provide both ingress and egress points.
  • Edge routing systems 121-122 comprise any systems, components, or devices configured to route packets or cells within packet-based core network 102 and exchange packets with systems outside of packet-based core network 102. Examples of edge routing systems 121-122 include routers and packet switches .
  • Point-to-point route 124 includes any route through packet-based core network 102 that associates two points or nodes in packet-based core network 102.
  • Point-to-point route 124 may be a static or dynamic route between edge routing system 121 and edge routing system 122. Examples of point-to-point route 124 include a Virtual Private Network (VPN), a Labeled Switch Path (LSP) in Multi-Protocol Label Switching (MPLS), a
  • VPN Virtual Private Network
  • LSP Labeled Switch Path
  • MPLS Multi-Protocol Label Switching
  • FIG. 2 is a flow chart illustrating a method of operation of communication network
  • monitoring system 110 receives information on point-to-point route 124 from packet-based core network 102.
  • the information on point-to-point route 124 may include a status or state of the route, degradation of the route, path loss on the route, available bandwidth on the route, etc.
  • gateway systems 104-105 are set up to use point-to-point route 124.
  • monitoring system 110 processes the information on point-to-point route 124, an identifier for gateway system 104, and an identifier for gateway system 105 to generate feedback information in step 204.
  • the feedback information associates the information on point-to- point route 124 with the identifier for gateway system 104 and the identifier for gateway system 105.
  • the identifier for gateway systems 104-105 comprise any code, address, name, label, or other identifier that distinguishes gateway systems 104-105, such as point codes, Carrier Identification Codes (CIC), port numbers, etc.
  • Monitoring system 110 then transmits the feedback information to gateway systems 104-105 in step 206.
  • Gateway systems 104-105 process the feedback information to handle future calls in step 208.
  • gateway system 104 accesses the feedback information to determine if the call may be forwarded over route 124. If the call may be forwarded, then gateway system 104 forwards packets for the call to edge routing system 121 in a conventional manner. If the call may not be forwarded over route 124, then gateway system 104 handles the call differently.
  • Gateway system 104 may block the call, re-route the call, or otherwise handle the call. Gateway system 104 may also provide call treatment to the caller, such as providing a busy signal or a busy message. Alternatively, gateway system 104 may update routing tables based on the feedback information. Responsive to receiving a call, gateway system 104 may access updated routing tables to handle the call. Monitoring system 110 continually or periodically receives the information on point-to-point route 124 from packet-based core network 102, generates the feedback information, and transmits the feedback information to gateway systems 104-105. Monitoring system 110 may transmit the feedback information every few seconds.
  • monitoring system 410 may transmit the feedback information on point-to- point route 124 to gateway systems 104-105 responsive to detecting a change in state of point-to-point route 124. Because monitoring system 110 proactively monitors route 124 and provides feedback information to gateway systems 104-105, gateway systems 104-105 can better handle calls when they are received. Instead of having to determine the status of a route on packet-based core network 102 on a call-by-call basis, gateway systems 104-105 advantageously know the status at the time the calls are received. Consequently, gateway systems 104-105 do not have to waste processing time determining the status after the call is received.
  • FIG. 3 illustrates monitoring system 110 in an embodiment of the invention.
  • Monitoring system 110 includes an interface system 302 coupled to a computer system 304.
  • Computer system 304 could be comprised of a programmed general purpose computer, although those skilled in the art will appreciate that programmable or special purpose circuitry and equipment may be used.
  • Computer system 304 may use a client server architecture where operations are distributed among a server system and client devices.
  • Computer system 304 includes a processing system 310 and a storage system 312.
  • Processing system 310 could comprise a computer microprocessor, logic circuit, or some other processing device. Processing system 310 may be distributed among multiple processing devices.
  • Storage system 312 is configured to store control software 314. Some examples of storage system 312 are memory devices, tape, disks, integrated circuits, and servers. Storage system 312 may be distributed among multiple memory devices.
  • interface system 302 receives information on point-to-point route 124 from packet-based core network 102. Interface system 302 forwards the information on point-to-point route 124 to computer system 304. Responsive to the information on point- to-point route 124, processing system 310 executes control software 314 in storage system 312 to perform the following.
  • Processing system 310 processes the information on point-to- point route 124, an identifier for gateway system 104, and an identifier for gateway system 105 to generate feedback information.
  • the feedback information associates the information on point-to-point route 124 with the identifier for gateway system 104 and the identifier for gateway system 105.
  • the identifier for gateway systems 104- 105 comprise any code, address, name, label, or other identifier that distinguishes gateway systems 104-105, such as point codes, Carrier Identification Codes (CIC), port numbers, etc.
  • Processing system 310 then forwards the feedback information to interface system 302.
  • Interface system 302 transmits the feedback information to gateway systems 104- 1O5.
  • FIG. 3 also describes methods of operation of monitoring system 110.
  • FIG. 4 illustrates a communication network 400 having tunnel monitoring and feedback in an embodiment of the invention.
  • the monitoring and feedback in this embodiment may be referred to as layer 2 to layer 3 feedback.
  • 400 comprises a packet core network 402, gateway systems 4O4-406, TDM networks 407-
  • Packet core network 402 comprises edge routers 421-423 and router 424. Communication network 400 may include other devices or systems not shown for the sake of brevity.
  • Monitoring system 410 is coupled to gateway systems 404-406. Monitoring system 410 is also coupled to packet core network 402, in which monitoring system 410 may communicate with multiple edge routers 421-423, other routers 424, switches, or other nodes within packet core network 402.
  • Gateway system 404 is coupled to TDM network 407 and edge router 421.
  • Gateway system 405 is coupled to TDM network 408 and edge router 422.
  • Gateway system 406 is coupled to TDM network 409 and edge router 423.
  • edge routers 421-423 communicate with one another via tunnels.
  • Edge router 421 communicates with edge router 422 via tunnel 431.
  • Edge router 421 communicates with edge router 423 via tunnel 432.
  • Edge router 422 communicates with edge router 423 via tunnel 433.
  • Tunnels 431 -433 may be Layer 2 Tunneling Protocol
  • Packet core network 402 may also include a supplemental protocol, such as MPLS, wherein tunnels 431-433 maybe Labeled Switch Paths. Packet core network 402 uses packets for communication between routers 421-424. Packet core network 402 may include many other routers and packet switches than those shown in FIG. 4. Packet core network 402 comprises a carrier-class network used as a backbone for major communication providers, such as Sprint, AT&T, and MCI Worldcom.
  • Gateway systems 404-406 comprise any systems, components, or devices that interwork calls from Time Division Multiplex (TDM) communications to packets, such as IP packets, ATM cells, etc.
  • Gateway systems 404-406 are configured to provide an ingress/egress point to packet core network 402.
  • gateway systems 404-406 may include a signaling processor 440 and an interworking unit 442.
  • the signaling processor 440 is configured to receive signaling, such as SS7 signaling, from TDM network 407 for a call.
  • Signaling processor 440 processes the signaling to generate a control message that includes an identifier for routing the call over packet core network 402.
  • the identifier may be an address, such as an IP address.
  • Interworking unit 442 is configured to receive user communications from TDM network 407 for the call.
  • the user communications are in TDM format and comprise bearer communications for the call.
  • Interworking unit 442 also receives the control message from signaling processor 440.
  • Interworking unit 442 interworks the user communications, in TDM format, into packets.
  • Interworking unit 442 adds the identifier from the control message to the headers of the packets. Interworking unit 442 is then prepared to forward the packets to edge router 421.
  • Gateway systems 404-406 may have different configurations than that shown in gateway system 404 in other embodiments.
  • monitoring system 410 receives information on tunnels 431-433 from packet core network 402.
  • the information on tunnels 431-433 may include a status or state of tunnels 431-433, degradation of tunnels 431-433, path loss on tunnels 431-433, available bandwidth on tunnels 431-433, or any other transport information on tunnels 431-433.
  • Monitoring system 410 processes the information on tunnel 431 , a point code for gateway system 404, and a point code for gateway system 405 to generate feedback information for tunnel 431.
  • the feedback information for tunnel 431 associates the information on tunnel 431 with the point code for gateway system 404 and the point code for gateway system 405.
  • Monitoring system 410 also processes the information on tunnel 432, the point code for gateway system 404, and a point code for gateway system 406 to generate feedback information for tunnel 432.
  • the feedback information for tunnel 432 associates the information on tunnel 432 with the point code for gateway system 404 and the point code for gateway system 406.
  • Monitoring system 410 also processes the information on tunnel 433, the point code for gateway system 406, and the point code for gateway system 405 to generate feedback information for tunnel 433.
  • the feedback information for tunnel 433 associates the information on tunnel 433 with the point code for gateway system 406 and the point code for gateway system 405.
  • Monitoring system 410 transmits the feedback information for tunnel 431 to gateway systems 404-405.
  • Monitoring system 410 transmits the feedback information for tunnel 432 to gateway systems 404 and 406.
  • Monitoring system 410 transmits the feedback information for tunnel 433 to gateway systems 405-406. Monitoring system 410 may transmit the feedback information for tunnels 431-433 periodically, such as every few seconds. Monitoring system 410 may also transmit the feedback information for tunnels 431-433 responsive to detecting a change in state of a tunnel. For instance, if tunnel 431 is experiencing a transport problem or is congested, then monitoring system 410 may transmit feedback information to gateway systems 404-405 indicating the problem. Gateway systems 404-406 process the feedback information to handle future calls, such as voice calls, video calls, or data calls. Gateway systems 404-406 may update routing tables in response to receiving the feedback information to handle calls.
  • gateway system 404 receives a call
  • signaling processor 440 processes signaling for the call to determine how to route the call. Assume for this call that signaling processor 440 determines that the call is to be routed to gateway system 405 over tunnel 431. If there is a problem with tunnel 431, then signaling processor 440 will know this from the feedback information provided by monitoring system 410. Signaling processor 440 can then handle the call differently. Signaling processor 440 may block the call, re-route the call, or otherwise handle the call. Signaling processor 440 may also provide call treatment to the caller, such as providing a busy signal or a busy message. If there is no problem with tunnel 431, then signaling processor 440 generates a control message that includes an address for routing over tunnel 431. Signaling processor
  • Interworking unit 442 receives user communications from TDM network 407 for the call. Interworking unit 442 interworks the user communications, in TDM format, into packets having the address from the control message. Interworking unit 442 then forwards the packets to edge router 421.
  • Signaling processor 440 may still determine the Quality of Service (QoS) on tunnel 431 before the packets are forwarded over tunnel 431 using conventional methods ⁇ such as Resource Reservation Protocol (RSVP).
  • QoS Quality of Service
  • RSVP Resource Reservation Protocol
  • communication network 400 is able to provide proactive monitoring of tunnels 431-433 and notify gateway systems 404-406 of any problems. The monitoring resembles red and yellow alarming typically done in a circuit-based core network. Proactive monitoring may be of particular importance for a packet core network.
  • gateway systems 404-406 advantageously know the status of tunnels 431-433 at the time the calls are received. Consequently, gateway systems 404-406 do not have to waste processing time determining the status after the call is received.

Landscapes

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

Abstract

L'invention concerne un réseau de télécommunication (100) qui comprend un réseau central (102) en mode paquet, des systèmes passerelles (104-105) et un système de surveillance (110). Le réseau central (102) en mode paquet comprend une pluralité de systèmes de routage (121-122) périphériques, un chemin (124) point à point reliant un premier système de routage (121) périphérique à un deuxième système de routage (122) périphérique. Le système de surveillance (110) reçoit du réseau central (102) des données relatives au chemin (124) point à point. Le système de surveillance (110) traite les données relatives au chemin (124) point à point ainsi que des identificateurs des systèmes passerelles (104-105) afin de produire des données de rétroaction. Les données de rétroaction associent les données de chemin (124) aux identificateurs des systèmes passerelles (104-105). Le système de surveillance (110) transmet ensuite les données de rétroaction aux systèmes passerelles (104-105). Les systèmes passerelles (104-105) traitent les données de rétroaction en vue du traitement des futurs appels.
PCT/US2004/036944 2003-11-14 2004-11-05 Surveillance de chemin point a point dans un reseau central en mode paquet WO2005050933A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US71403203A 2003-11-14 2003-11-14
US10/714,032 2003-11-14

Publications (1)

Publication Number Publication Date
WO2005050933A1 true WO2005050933A1 (fr) 2005-06-02

Family

ID=34619877

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2004/036944 WO2005050933A1 (fr) 2003-11-14 2004-11-05 Surveillance de chemin point a point dans un reseau central en mode paquet

Country Status (1)

Country Link
WO (1) WO2005050933A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102005052188A1 (de) * 2005-10-26 2007-05-31 Deutsche Telekom Ag Dienstqualitätssicherung mit Hilfe zentral erfasster Dienstgüteparameter
CN102904769A (zh) * 2011-07-27 2013-01-30 广西鑫百纳电气有限公司 用于监控系统的测试方法以及测试设备
US9800433B2 (en) 2015-12-16 2017-10-24 At&T Intellectual Property I, L.P. Method and apparatus for providing a point-to-point connection over a network
AT521914A1 (de) * 2018-12-13 2020-06-15 Avl List Gmbh Kommunikationsmodul

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020143928A1 (en) * 2000-12-07 2002-10-03 Maltz David A. Method and system for collection and storage of traffic data in a computer network
US20030091049A1 (en) * 1996-03-08 2003-05-15 Hajime Abe Packet switching network, packet switching equipment and network management equipment

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030091049A1 (en) * 1996-03-08 2003-05-15 Hajime Abe Packet switching network, packet switching equipment and network management equipment
US20020143928A1 (en) * 2000-12-07 2002-10-03 Maltz David A. Method and system for collection and storage of traffic data in a computer network

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SERIES E:OVERALL NETWORK OPERATION: "E.164 Supplement 1:Alternatives for carrier selection and Network identification", March 1998, INTERNATIONAL TELECOMMUNICATION UNION, XP002319207 *
SERIES Q:SWITCHING AND SIGNALLING: "Q.713:Signalling connection control part formats and codes", March 2001, INTERNATIONAL TELECOMMUNICATION UNION, XP002319206 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102005052188A1 (de) * 2005-10-26 2007-05-31 Deutsche Telekom Ag Dienstqualitätssicherung mit Hilfe zentral erfasster Dienstgüteparameter
DE102005052188B4 (de) 2005-10-26 2019-01-10 Deutsche Telekom Ag Dienstqualitätssicherung mit Hilfe zentral erfasster Dienstgüteparameter
CN102904769A (zh) * 2011-07-27 2013-01-30 广西鑫百纳电气有限公司 用于监控系统的测试方法以及测试设备
US9800433B2 (en) 2015-12-16 2017-10-24 At&T Intellectual Property I, L.P. Method and apparatus for providing a point-to-point connection over a network
US10361885B2 (en) 2015-12-16 2019-07-23 At&T Intellectual Property I, L.P. Method and apparatus for providing a point-to-point connection over a network
US10887129B2 (en) 2015-12-16 2021-01-05 At&T Intellectual Property I, L.P. Method and apparatus for providing a point-to-point connection over a network
US11563602B2 (en) 2015-12-16 2023-01-24 At&T Intellectual Property I, L.P. Method and apparatus for providing a point-to-point connection over a network
AT521914A1 (de) * 2018-12-13 2020-06-15 Avl List Gmbh Kommunikationsmodul
AT521914B1 (de) * 2018-12-13 2020-10-15 Avl List Gmbh Kommunikationsmodul

Similar Documents

Publication Publication Date Title
US6532088B1 (en) System and method for packet level distributed routing in fiber optic rings
US6647428B1 (en) Architecture for transport of multiple services in connectionless packet-based communication networks
EP1748599B1 (fr) Réseau porteur d'anneaux et procédé de mise en oeuvre de porteur de services
EP0961518B1 (fr) Routage de connexions dans un réseau de communication digital dirigé par un operateur
US8854975B2 (en) Scaling OAM for point-to-point trunking
US7765306B2 (en) Technique for enabling bidirectional forwarding detection between edge devices in a computer network
EP1433287B1 (fr) Commutation de protection dans un reseau de communications utilisant une commutation d'etiquettes
WO2021185208A1 (fr) Procédé et appareil de traitement de paquet, dispositif, et support de stockage
US7796511B2 (en) Self-routed layer 4 packet network system and method
EP1777897B1 (fr) Procede d implementation de gestion et de protection par la division de domaine dans le reseau a commutation d etiquettes
US7796504B1 (en) Method for establishing an MPLS data network protection pathway
US7756125B2 (en) Method and arrangement for routing pseudo-wire encapsulated packets
US20080095045A1 (en) Method and Apparatus for Detecting MPLS Network Failures
WO2009035808A1 (fr) Systèmes et procédés pour une topologie ethernet de support à auto-rétablissement
Huynh et al. Resilience technologies in Ethernet
US20050238001A1 (en) Virtual ethernet mac switching
US7289431B2 (en) Packet transmission method
US9037746B2 (en) Pseudowire circuit emulation
WO2005050933A1 (fr) Surveillance de chemin point a point dans un reseau central en mode paquet
US8964525B1 (en) Methods and apparatus for enhancing fault management using inter-working between PPP and ethernet
Suhaimy et al. Analysis of MPLS-TP network for different applications
KR100684143B1 (ko) 단순화된 ｍｐｌｓ 메커니즘을 이용하여 다양한 ｌ2ｖｐｎ서비스를 제공하기 위한 방법 및 장치
CN115801552A (zh) 保护倒换方法及网络设备
Thunen SNA over Frame Relay
JP2000032058A (ja) 高効率パケットデ―タ伝送ネットワ―クおよびそれに用いられるインタフェ―ス

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DPEN Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101)
122 Ep: pct application non-entry in european phase