EP1502396A1 - Procede pour accepter des circuits equivalents dans des reseaux mpls - Google Patents

Procede pour accepter des circuits equivalents dans des reseaux mpls

Info

Publication number
EP1502396A1
EP1502396A1 EP03729874A EP03729874A EP1502396A1 EP 1502396 A1 EP1502396 A1 EP 1502396A1 EP 03729874 A EP03729874 A EP 03729874A EP 03729874 A EP03729874 A EP 03729874A EP 1502396 A1 EP1502396 A1 EP 1502396A1
Authority
EP
European Patent Office
Prior art keywords
mpls
packets
oam
connection
lav
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP03729874A
Other languages
German (de)
English (en)
Inventor
Joachim Klink
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siemens AG
Original Assignee
Siemens AG
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 Siemens AG filed Critical Siemens AG
Publication of EP1502396A1 publication Critical patent/EP1502396A1/fr
Withdrawn legal-status Critical Current

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
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • 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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing
    • 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/5619—Network Node Interface, e.g. tandem connections, transit switching
    • 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/5625—Operations, administration and maintenance [OAM]
    • H04L2012/5627—Fault tolerance and recovery
    • 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

Definitions

  • the invention relates to a method according to the preamble of claim 1.
  • the OAM functionality (Operation and Maintenance) is to be regarded as an essential part of the operation of public communication networks. It supports the quality of the network performance while reducing the operating costs of the network. It makes a significant contribution, particularly with regard to the quality of service of the information transmitted (QoS).
  • QoS quality of service of the information transmitted
  • OAM functionality of the operator of a co can - munikationsnetzes always obtained knowledge about 'whether the guaranteed quality of service for a connection (Service Level Agreement) is complied with. For this, the operator must know the availability of existing connections (connection "up ⁇ or" down *) as well as the time delay in the transmission of the information (delay, delay variation), the - possibly averaged - deviation from the otherwise usual distance between each two information transmissions (delay jitter), or the number of information not even allowed to be transmitted (blocking rate, error performance).
  • MPLS networks are currently proposed for the transmission of information on the Internet.
  • MPLS networks Multiprotocol Packet Label Switching
  • information is transmitted using MPLS packets.
  • MPLS packets have a variable length, each with a header and an information part.
  • the header is used to record connection information, while the information section is useful for recording useful information.
  • IP packets are used as useful information.
  • the connection information contained in the header is designed as an MPLS connection number. However, this is only valid in the MPLS network. If an IP packet from an Internet network thus penetrates the MPLS network (FIG. 1), this is preceded by the header that is valid in the MPLS network. This contains all connection information that specifies the path of the MPLS packet in the MPLS network. Leave that
  • MPLS packet the MPLS network, the head part is removed again and the IP packet in the subsequent internet network is routed further in accordance with the IP protocol.
  • MPLS packets are transmitted unidirectionally.
  • Fig. 1 it is assumed as an example that information such. B. can be supplied from a subscriber TLN1 to a subscriber TLN2.
  • the sending subscriber TLN1 is connected to the Internet network IP, through which the information is passed according to an Internet protocol, such as the IP protocol. This protocol is not a connection-oriented protocol.
  • the Internet network IP has a plurality of routers R, which can be meshed with one another.
  • the receiving subscriber TLN2 is connected to a further Internet network IP.
  • An MPLS network is inserted between the two Internet networks IP, through which information in the form of MPLS packets is switched through in a connection-oriented manner. This network also has a plurality of routers meshed with one another.
  • LSR label switched routers
  • QoS quality of service
  • the knowledge of failure situations (signal case situation) of connections in the network plays an important role for the network operator, since he can carry out corresponding equivalent circuits for the user in accordance with this information.
  • the prior art makes no contribution to solving this problem.
  • the invention has for its object to show a way, how information about failure situations in MPLS networks can be provided with little effort and appropriate equivalent switching measures can be initiated.
  • the invention is achieved on the basis of the features specified in the preamble of claim 1 by the characterizing features.
  • An advantage of the invention is in particular the provision of specially designed MPLS-OAM packets which are inserted into the traffic flow of user data packets.
  • MPLS-OAM packets which are inserted into the traffic flow of user data packets.
  • a further identifier is required.
  • the packages defined in this way monitor the continuity of connections and the transmission quality (performance monitoring) of an MPLS connection (MPLS Label Switched Path).
  • MPLS-OAM functionality is now used to support MPLS equivalent switching measures. This procedure is easy to use, especially where very fast changeover times are not required.
  • a simple express protocol is defined for faster switching times.
  • FIG 1 shows the basic conditions in an MPLS network
  • Figure 2 shows an end-to-end connection between two participants
  • Figure 3 shows the relationships in the packet header and in the information part of an MPLS-OAM packet
  • FIG. 2 shows a connection (label switched path, LSP) between two subscribers TLN1, TLN2.
  • LSP label switched path
  • This connection is made via a plurality of nodes N1 ... N4, as a result of which a plurality of connection sections (label switched hop) are defined.
  • the nodes N1 ... N4 should be designed as routers LSR of an MPLS network.
  • an information flow arises between the subscriber TLN1 and the subscriber TLN2, which is formed from a plurality of MPLS packets carrying the useful data.
  • MPLS-OAM packets can be inserted into this MPLS packet flow (inband LSP).
  • connections are defined via which only MPLS-OAM packets are routed (outband LSP).
  • in-band MPLS-OAM packets are useful for logging LSP connections on an individual basis. However, in some cases it may be more advantageous to define an out-of-band MPLS-OAM packet flow. An example of this is the MPLS group equivalent circuit.
  • MPLS-OAM packets In order to distinguish MPLS-OAM packets from MPLS packets carrying user data, the MPLS-OAM packets are marked.
  • the special marking mechanisms are shown in FIG. 3 and will be described in more detail later.
  • the sequence of several MPLS-OAM packets defines an MPLS-OAM packet flow. Basically 3 different types of an MPLS-OAM packet flow exist simultaneously for a connection LSP:
  • End-to-end MPLS-OAM packet flow It is used in particular when OAM communication takes place between a source and a sink of an LSP connection. It is formed from MPLS-OAM packets, which are inserted in the source of the connection LSP in the user data stream and are taken out again at the sink. The MPLS-OAM packets can be recorded and monitored along the connection LSP to the connection point CP without interfering with the transmission process (passive monitoring).
  • the MPLS-OAM packet flow of type A is distinguished from the end-to-end defined MPLS-OAM packet flow. It is used in particular when OAM communication takes place between the nodes which delimit a connection section (segment) of type A (FIG. 2).
  • One or more Type A MPLS-OAM segments can be defined in the LSP connection, but they cannot be nested nor can they overlap with other Type A segments.
  • the MPLS-OAM packet flow of type B is distinguished from the two types of packet flow mentioned above. It is used in particular when OAM communication takes place between the nodes which delimit a type B connection section (FIG. 2).
  • One or more Type B MPLS OAM segments can be defined in the LSP connection, but they cannot be nested nor can they overlap with other Type B segments.
  • an MPLS-OAM packet flow (end-to-end, type A, type B) is formed from MPLS-OAM packets, which are inserted into the user data stream at the beginning of a segment and at the end of the MPLS-OAM packet flow
  • connection point CP in the connection LSP including the sources and sinks of the connection can be configured as an MPLS-OAM source or an MPLS-OAM sink, the MPLS-OAM packets originating from an MPLS-OAM source preferably as “upstream” * are to be configured.
  • the end points (source, sink) of the associated MPLS-OAM segment must be defined.
  • the definition of source and sink for an MPLS-OAM segment is not necessarily fixed for the duration of the connection. This means that the relevant segment can be reconfigured, for example, using fields in the signaling protocol.
  • the segmented MPLS-OAM packet flow (type A or type B) can be nested within an end-to-end MPLS-OAM packet flow.
  • the connection points CP can be the source / sink of a segment flow (type A or type B) as well as the end-to-end MPLS-OAM packet flow.
  • the MPLS-OAM packet flow (segment flow) of type A is functionally independent of that of type B in terms of inserting, removing and processing the MPLS-OAM packets.
  • a connection point CP can therefore be the source and sink of an OAM segment flow of type A and type B at the same time.
  • type A segments can overlap with type B segments. Both segments can and will operate independently of one another therefore do not influence each other in any way. In MPLS replacement circuits, however, overlapping can lead to problems.
  • the differentiation between MPLS-OAM packets and MPLS packets carrying user data can be carried out by using one of the EXP bits in the MPLS packet header.
  • this procedure offers a very simple possibility of differentiation.
  • This bit can be checked in the sink of an MPLS-O ⁇ M segment or at the connection points CP in order to filter out MPLS-OAM packets before further evaluations are carried out.
  • one of the MPLS connection numbers (MPLS label values) No. 4 to No. 15 in the header of the MPLS packet can be used as an identifier.
  • These MPLS connection numbers have been reserved by IANA.
  • the next identifier in the stack of the assigned connection LSP must indicate what the inband OAM functionality is carried out for.
  • This approach is somewhat more complex to implement, since the hardware in the OAM sink and the connection points CP requires two MPLS stack inputs for each MPLS-OAM packet.
  • the processing must be done in real time, i.e. in the connection points CP the OAM packets must be reinserted into the flow if the sequence order is adhered to. This is imperative to ensure correct performance monitoring results in the OAM sink.
  • MPLS-OAM-LAV packets are defined to monitor (verify) the availability (availability) of an MPLS connection LSP (hereinafter referred to as MPLS-LAV function).
  • connection LSP This enables the availability of an LSP connection to be determined on an end-to-end basis or on a segmented basis.
  • an MPLS-OAM-LAV packet provided for this purpose is inserted periodically per time interval (e.g. per second) and periodically per time interval (e.g. per second) monitored at the sink for its arrival. If after a predefined time (e.g. several seconds) and possibly multiple checks (e.g. 2 to 3 times) no MPLS-OAM-LAV packet has been received at the sink, the connection LSP is declared not available (LSP ⁇ down * or "unavailable ⁇ ). In the case of the unavailable connection LSP, the arrival of the MPLS-OAM-LAV packet is still checked periodically at the sink, and if it is received again at the sink after a predefined time (of several seconds), the connection becomes available again explained.
  • the MPLS-LAV function can be activated simultaneously on an end-to-end basis or segmented basis for each LSP connection on any interface CP or network element. Activation and deactivation is possible via signaling procedures as well as via manual configuration via network management. The activation can take place at any time, either during the connection establishment or afterwards.
  • a segment is monitored, it is first necessary to define the limits of the segment in question within the assigned LSP connection. This is usually done by first determining the source and sink.
  • the MPLS-LAV function can then be activated in the following. However, it must be inactive if the limits of a segment are to be changed or the segment is to be deleted, which is possible at any time.
  • the advantage of the MPLS-LAV function is that you can check whether the agreed (Service Level Agreement) Quality of Service parameters of the LSP connection in question have been complied with.
  • the availability status is an indication of the occurrence of a connection failure (signal fail situation).
  • a signal "Signal Fail” is activated. If the connection is available, this signal is deactivated. With the aid of this signal, substitute switching requests (MPLS Protection Switching) or alarms can then be initiated. Furthermore, the location of the underlying network fault can be determined.
  • a further, purely passive monitoring function can be provided as an additional function to the monitoring function (MPLS-LAV function).
  • the MPLS-OAM-LAV packets are only read during the monitoring process but not changed (non-intrusive). They can be determined at each of the connection points CP along the MPLS-OAM-LAV traffic flow on an end-to-end basis or segment basis by processing the content of the MPLS-OAM-LAV packets passing the connection point CP without characteristic quantities such as B. the content of the packages is changed.
  • Monitoring takes place in addition to e.g. end-to-end monitoring, d. H. in this case, individual connection sections of the entire connection are checked.
  • Passive monitoring includes the same functionality as described for the MPLS-LAV function.
  • the advantage of the passive monitoring function can be seen in the fault localization. This can be used to implement a step-by-step method which can be used to determine which parts of the connection LSP are interrupted. The Ver- deterioration in transmission quality (signal degrade) can also be determined.
  • the MPLS-LAV function also forms the basis for monitoring the transmission quality (performance monitoring).
  • the function that monitors the transmission quality (hereinafter referred to as the PM function) is to be regarded as a subfunction for the MPLS-LAV function.
  • the PM function is used to monitor the transmission quality of a connection on an end-to-end basis or segment basis.
  • the number of MPLS-LAV packets that are lost per time interval during transmission plays a role as large as the number of packets that were incorrectly inserted. For example, a time interval of 1 second can be used as the time interval (one-second interval).
  • the MPLS-OAM-LAV packet contains a special field for receiving a packet counter.
  • the monitoring of the transmission quality is now carried out by first counting the number of MPLS packets transmitted in the source that carry useful data and are transmitted per second for the LSP connection in question.
  • the value determined in this way is now transmitted to the sink, where it is compared with the status of a further counter, in which the number of MPLS packets carrying user data that have arrived in the sink is recorded. By comparing the two values, the number of packets lost during transmission or the number of incorrectly inserted packets can be determined.
  • the PM function can only be activated when the (associated) MPLS-LAV function is active. If this is the case for a specific LSP connection, the PM function can be active or inactive as required. Activation and deactivation the PM function is possible via signaling procedures as well as alternatively via manual configuration.
  • the PM function is used to determine whether the negotiated (Service Level Agreement), guaranteed quality of service (QoS) of the assigned LSP connection has also been observed. These include e.g. B. the requirements regarding error performance. It can also be determined whether the throughput guaranteed for the connection has actually been maintained by the network.
  • QoS quality of service
  • the PM function can also be used to determine the deterioration of a signal (signal degrade) for a connection LSP.
  • MPLS protection switching can be initiated as a result.
  • an alarm can also be generated, which is supplied to the network operator, for example.
  • MPLS traffic engineering can be provided to determine overload situations in the network.
  • a free-running counter in the source counts the number of MPLS packets carrying user data that are sent for the corresponding LSP connection.
  • MPLS packets carrying user data are understood to mean all the packets which are not marked as OAM packets.
  • the counter can be designed as a 16-bit counter (free running, modulo 65536). Every time an MPLS-LAV packet is inserted into the MPLS-LAV traffic flow of the LSP connection in question (eg per second), the current value of the counter is written into the corresponding field of the MPLS-LAV packet.
  • the difference between two consecutive counter readings corresponds to the number of MPLS packets carrying user data that have been transmitted between two MPLS-OAM-LAV packets sent one after the other.
  • another, free-running counter in the sink counts the number of MPLS packets carrying the user data (LSP for this connection).
  • This counter is also designed as a 16 bit counter (free running, modulo 65536). Every time an MPLS-OAM-LAV packet is received for the LSP connection in question (e.g. per second), the following calculations are carried out in real-time processing (ie within the transmission time of an MPLS packet carrying useful data):
  • the difference between the current meter reading (after determining the number of MPLS packets carrying the useful data that have arrived) and the meter reading that it had when evaluating the last MPLS-OAM-LAV packet is formed.
  • the result corresponds to the number of MPLS packets carrying user data that have arrived for this LSP connection within the one-second interval.
  • the counter reading also transmitted in the MPLS-OAM-LAV packet is then read in a second calculation step, and subtracted from the value of the counter reading also transmitted of the previously arrived MPLS-OAM-LAV packet.
  • the result corresponds to the number of MPLS packets carrying user data that were sent in the source within the one-second interval for this connection LSP.
  • the difference between the two calculations corresponds to the number of packets that were lost within the last one-second interval for the LSP connection in question (assuming that more packets were sent than received). This result is saved for this time interval. If more packets have arrived than were sent, it is assumed that packets have been inserted LSP incorrectly somewhere during the transmission in this connection. A free-running one-second counter in the sink then handles the further processing. If the status of the associated LSP connection is "down * or" unavailable *, the activation of the PM function is suppressed until the status of this connection is again "up * or" available *.
  • the transmission quality of the connection or of the partial section of the connection can also be monitored in any network devices located between the source and the sink.
  • the information about the transmission quality of the MPLS connection in any MPLS network devices located between the source and the sink it is possible to locate the underlying network error as part of diagnostic measures.
  • the OAM functionality just described is also used to support MPLS protection switching devices.
  • the basic functionality of an MPLS protection switching device is described in the German patent application with the official file number 19646016.6.
  • MPLS group replacement circuits Group Protection Switching
  • Switching times are necessary, as in the case of SDH / SONET networks.
  • an extended MPLS-OAM functionality is required.
  • the support on the part of the MPLS-OAM functionality is also required in order to determine a deterioration in the transmission quality (signal degrade situation) on an assigned connection LSP and to send the relevant information to the sink of the section to be protected, where that Switching to a replacement route (protection switching) can be initiated.
  • control information causing the changeover is stored in the form of a K1 / K2 byte.
  • the MPLS-LAV function determines failure situations (signal fail) on an assigned LSP connection.
  • an MPLS-OAM-LAV traffic flow (on an end-to-end basis or segment basis) is configured for the current LSP operating route and another for the LSP replacement route.
  • the failure of the signal (signal fail) can then be determined in the OAM sink and the switchover processes can be initiated as a result.
  • an MPLS-OAM function is defined for fast triggering of the equivalent circuit when failure situations occur (FSFT function, Fast Signal Fail Trigger Function).
  • the functionality is the same as for the MPLS-LAV function except for the fact that a OAM packet is inserted in the source every 10 ms (instead of once per sec). Accordingly, the evaluation in the sink is based on a 10 ms counter instead of a 1 sec counter. As a result, the failure of a signal in the sink is determined after a maximum time of 30 ms after the interruption occurred. Further processing can then be initiated immediately.
  • the purely passive monitoring function non intrusive monitoring function
  • an OAM traffic flow (on an end-to-end basis or segment basis) for a control connection on the operating route (working entity) and another for a control connection on the replacement route (protection Entity) can be configured.
  • the failure of a signal is then determined on these control connections, whereupon the equivalent switching measures are initiated for the entire group.
  • the FSFT function can also (if required) be used for individual MPLS equivalent circuits in order to achieve reduced equivalent switching times.
  • both the MPLS-LAV traffic flow and the MPLS-OAM-FSFT traffic flow are configured simultaneously for the assigned LSP connection, both on the active operating route (working entity) and on the replacement route (protection entity).
  • the replacement circuit is then initiated in failure situations not on the basis of the monitoring of the MPLS-LAV traffic flow but rather on the basis of the fast MPLS-LAV-FSFT traffic flow.
  • the deterioration in the transmission quality of a signal can be determined using the PM function (performance monitoring). For this, an MPLS Configure LAV traffic flow (on an end-to-end basis or segment basis) for the active operating route as well as for the alternative route of the LSP connection. The deterioration in the transmission quality can then be determined in the OAM sink, whereupon MPLS equivalent switching measures are initiated.
  • This functionality is used to determine the deterioration in the transmission quality in individual MPLS replacement switch configurations.
  • the MPLS group replacement circuit is not described further here, but the functionality in this case is much more complex and also makes use of the performance monitoring subfunction of the MPLS-LAV function.
  • the first function is called the normal transfer function and the second is called the accelerated transfer function on:
  • this functionality can also be used for the evaluation of the equivalent switching protocol.
  • Information relating to the equivalent circuit is stored in the equivalent switching protocol and is transmitted between the source and sink of the section to be protected.
  • the Kl / K2 bytes of the equivalent switching protocol are then transmitted in the payload of the MPLS-OAM-LAV packets.
  • the corresponding format is shown in Figure 3.
  • the current K1 / K2 byte send status is inserted into the MPLS-OAM-LAV packet at source m per second. If the K1 / K2 transmission status changes, this change will be transmitted in the next MPLS-OAM-LAV packet.
  • the MPLS-OAM-LAV packet is taken from the traffic flow.
  • the received K1 / K2 bytes in the payload are then made available to the MPLS equivalent switching function for further processing.
  • the relatively slow mechanism of the normal transfer function cannot be accepted for MPLS group equivalent switching configurations where fast equivalent switching is required.
  • an MPLS-OAM replacement switching protocol express message (accelerated transmission function) is defined, which includes an expansion of the OAM-LAV functionality.
  • an MPLS-OAM spare switching protocol express message is transmitted immediately instead of waiting for the next MPLS-OAM-LAV packet (per second lx).
  • the OAM format of this packet is shown in Figure 3.
  • the spare switch protocol information is extracted from the OAM packet and supplied to the MPLS spare switch functionality. Immediate initiation of processing in the sink can be achieved, for example, by checking an incoming OAM packet to determine whether the function type is suitable for a spare switch express message. This is the case if it has the value ⁇ 0010 ".
  • the accelerated transfer function should be activated at the same time as the fast FSFT function in order to achieve fast substitute switching for MPLS group substitute switch configurations.
  • both mechanisms can also be used for MPLS replacement switch configurations on an individual basis.

Landscapes

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

Abstract

La présente invention concerne un procédé pour accepter des mesures de circuit équivalent dans des réseaux MPLS à l'aide de moyens simples. Ce procédé consiste à définir une fonctionnalité MPLS-OAM permettant de surveiller la continuité et la qualité de transmission (performance monitoring) d'une liaison MPLS (MPLS Label Switched Path). Cette fonctionnalité MPLS-OAM permet d'accepter des mesures de circuit équivalent MPLS. Il est notamment facile de mettre en oeuvre ce procédé dans les cas où aucune durée de transfert très rapide n'est nécessaire. Un protocole express simple est défini de manière supplémentaire pour des durées de transfert plus rapides.
EP03729874A 2002-05-08 2003-05-08 Procede pour accepter des circuits equivalents dans des reseaux mpls Withdrawn EP1502396A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE10220619 2002-05-08
DE10220619 2002-05-08
PCT/DE2003/001480 WO2003096631A1 (fr) 2002-05-08 2003-05-08 Procede pour accepter des circuits equivalents dans des reseaux mpls

Publications (1)

Publication Number Publication Date
EP1502396A1 true EP1502396A1 (fr) 2005-02-02

Family

ID=29413720

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03729874A Withdrawn EP1502396A1 (fr) 2002-05-08 2003-05-08 Procede pour accepter des circuits equivalents dans des reseaux mpls

Country Status (3)

Country Link
US (1) US20060165089A1 (fr)
EP (1) EP1502396A1 (fr)
WO (1) WO2003096631A1 (fr)

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7236490B2 (en) 2000-11-17 2007-06-26 Foundry Networks, Inc. Backplane interface adapter
US7596139B2 (en) 2000-11-17 2009-09-29 Foundry Networks, Inc. Backplane interface adapter with error control and redundant fabric
US20120155466A1 (en) 2002-05-06 2012-06-21 Ian Edward Davis Method and apparatus for efficiently processing data packets in a computer network
US7266117B1 (en) 2002-05-06 2007-09-04 Foundry Networks, Inc. System architecture for very fast ethernet blade
US7187687B1 (en) 2002-05-06 2007-03-06 Foundry Networks, Inc. Pipeline method and system for switching packets
US7468975B1 (en) 2002-05-06 2008-12-23 Foundry Networks, Inc. Flexible method for processing data packets in a network routing system for enhanced efficiency and monitoring capability
US6901072B1 (en) 2003-05-15 2005-05-31 Foundry Networks, Inc. System and method for high speed packet transmission implementing dual transmit and receive pipelines
US7817659B2 (en) 2004-03-26 2010-10-19 Foundry Networks, Llc Method and apparatus for aggregating input data streams
US8730961B1 (en) 2004-04-26 2014-05-20 Foundry Networks, Llc System and method for optimizing router lookup
US7657703B1 (en) 2004-10-29 2010-02-02 Foundry Networks, Inc. Double density content addressable memory (CAM) lookup scheme
CN100583784C (zh) * 2005-03-30 2010-01-20 华为技术有限公司 在多协议标签交换网络中监测丢包率的方法
US7898944B2 (en) * 2005-12-14 2011-03-01 Cisco Technology, Inc. Smart mechanism for multi-client bidirectional optical channel protection scheme
US8448162B2 (en) 2005-12-28 2013-05-21 Foundry Networks, Llc Hitless software upgrades
US7903654B2 (en) 2006-08-22 2011-03-08 Foundry Networks, Llc System and method for ECMP load sharing
US8238255B2 (en) 2006-11-22 2012-08-07 Foundry Networks, Llc Recovering from failures without impact on data traffic in a shared bus architecture
US20090279441A1 (en) 2007-01-11 2009-11-12 Foundry Networks, Inc. Techniques for transmitting failure detection protocol packets
US8037399B2 (en) 2007-07-18 2011-10-11 Foundry Networks, Llc Techniques for segmented CRC design in high speed networks
US8271859B2 (en) 2007-07-18 2012-09-18 Foundry Networks Llc Segmented CRC design in high speed networks
US7895425B2 (en) * 2007-08-03 2011-02-22 Cisco Technology, Inc. Operation, administration and maintenance (OAM) in a service insertion architecture (SIA)
US8509236B2 (en) 2007-09-26 2013-08-13 Foundry Networks, Llc Techniques for selecting paths and/or trunk ports for forwarding traffic flows
US8374095B2 (en) * 2009-03-23 2013-02-12 Cisco Technology, Inc. Connection verification for MPLS label switched paths and pseudowires
US8090901B2 (en) 2009-05-14 2012-01-03 Brocade Communications Systems, Inc. TCAM management approach that minimize movements
US8599850B2 (en) 2009-09-21 2013-12-03 Brocade Communications Systems, Inc. Provisioning single or multistage networks using ethernet service instances (ESIs)
WO2015097318A1 (fr) * 2013-12-26 2015-07-02 Telefonica, S.A Procédé et système pour restaurer les détériorations de la qualité de service dans des réseaux de mpls

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5838924A (en) * 1996-08-06 1998-11-17 Lucent Technologies Inc Asynchronous transfer mode (ATM) connection protection switching apparatus and method
US6654923B1 (en) * 1999-09-09 2003-11-25 Nortel Networks Limited ATM group protection switching method and apparatus
CA2310872A1 (fr) * 1999-12-22 2001-06-22 Nortel Networks Corporation Commutation de protection automatique au moyen de la redondance au niveau liaison en soutien a la commutation d'etiquettes multi-protocole
EP1126742A1 (fr) * 2000-02-15 2001-08-22 Siemens Aktiengesellschaft Méthode de commutation de protection des dispositifs de transmission dans des réseaux MPLS
US8199649B2 (en) * 2001-03-28 2012-06-12 Alcatel Lucent Method and apparatus for rerouting a connection in a data communication network based on a user connection monitoring function

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
WO2003096631A1 (fr) 2003-11-20
US20060165089A1 (en) 2006-07-27

Similar Documents

Publication Publication Date Title
EP1502396A1 (fr) Procede pour accepter des circuits equivalents dans des reseaux mpls
EP1500236B1 (fr) Procede pour surveiller la qualite de transmission de liaisons dans des reseaux mpls
WO2003094443A1 (fr) Procede pour controler la disponibilite de liaisons dans des reseaux mpls
DE69934852T2 (de) IP-Paketkommunikationsvorrichtung
DE60217279T2 (de) Vorrichtung und Verfahren zur Übertragung im Fehlerfall von OAM paketen zwischen ATM und geschalteten Netzwerken
DE69523898T2 (de) Kommunikationsnetzwerk mit einer kanalumschaltungsschutzanordnung
DE69634611T2 (de) Selbstheilendes netzwerk
DE60319502T2 (de) Verfahren zur Wiedererstellung von Transportnetzwerken
WO1999046908A1 (fr) Reseau local, notamment reseau ethernet, ayant des proprietes de redondance et un gestionnaire de redondance
DE69830951T2 (de) Anordnung und Verfahren zum effizienten Koordinieren der Reservenumschaltung
EP1430665A2 (fr) Procede et dispositif d'adaptation de chemins a commutation d'etiquettes dans des reseaux paquets
EP2634973A1 (fr) Appareil de communication pour un réseau de communication industriel fonctionnant de manière redondante et procédé de fonctionnement d'un appareil de communication
DE10219153A1 (de) Verfahren zur Überprüfung der Durchgängigkeit von Verbindungen in MPLS-Netzen
DE19826387A1 (de) Überwachungsschaltung für ein Datenübertragungsnetz
DE10118295A1 (de) Optischer Crossconnect
DE602004001231T2 (de) Verfahren zur Wiederherstellung von Zusatzverkehr unterstützenden Transportnetzwerken
EP1130853A1 (fr) Dispositif de circuit pour la commutation de substitution d' installations de transmission dans des architectures d' anneau avec des paquets de MPLS
EP1262084B1 (fr) Procede de commutation de remplacement de dispositifs de transmission dans les reseaux mpls
DE102005055854A1 (de) Vorrichtungen und Verfahren zum Erzeugen von Paketen und Taktsignalen für ein Paketnetzwerk
WO2003081850A1 (fr) Procede de fonctionnement et de surveillance de reseaux mpls
EP1130852A1 (fr) Procédé de commutation de substitution d' installations de transmission dans des architectures d' anneau avec des paquets de MPLS
EP3629550A1 (fr) Procédé de transmission de données dans un réseau de communication industrielle et dispositif de communication couplée
DE60018779T2 (de) Signalisierung von fehlern in nachrichtenübertragungsnetzwerken
DE102005007062B4 (de) Verfahren zum Übermitteln von Signalisierungsdaten zwischen Peripherieeinrichtungen eines Vermittlungssystems
EP1256257A1 (fr) Procede de commutation de remplacement de dispositifs de transmission dans les reseaux mpls

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20040405

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20051216