EP1478129B1 - Réseau de transport supportant des tunnels pour fournir un transport de données basé sur le service - Google Patents

Réseau de transport supportant des tunnels pour fournir un transport de données basé sur le service Download PDF

Info

Publication number
EP1478129B1
EP1478129B1 EP04300235A EP04300235A EP1478129B1 EP 1478129 B1 EP1478129 B1 EP 1478129B1 EP 04300235 A EP04300235 A EP 04300235A EP 04300235 A EP04300235 A EP 04300235A EP 1478129 B1 EP1478129 B1 EP 1478129B1
Authority
EP
European Patent Office
Prior art keywords
service
transport
distribution point
recited
packet
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.)
Expired - Fee Related
Application number
EP04300235A
Other languages
German (de)
English (en)
Other versions
EP1478129A3 (fr
EP1478129A2 (fr
Inventor
Joe Regan
Sunil Khankekar
Marcelo Mourier
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.)
Nokia of America Corp
Original Assignee
Alcatel IP Networks Inc
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 Alcatel IP Networks Inc filed Critical Alcatel IP Networks Inc
Publication of EP1478129A2 publication Critical patent/EP1478129A2/fr
Publication of EP1478129A3 publication Critical patent/EP1478129A3/fr
Application granted granted Critical
Publication of EP1478129B1 publication Critical patent/EP1478129B1/fr
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/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
    • 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]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers

Definitions

  • the present invention relates generally to computer networks. More specifically, using network transport tunnels to provide service-based data transport is disclosed.
  • Transport tunnels are employed in communications, networks, and networking equipment (e.g., routers, switches, hubs, etc.) to route data between endpoints.
  • transport tunnels may be used to forward packets through a network that does not support the particular packet protocol in use.
  • a transport tunnel may be used to forward a non-IP packet across an IP network, multicast packets across a unicast network, etc.
  • Services may be bound to a transport tunnel, but use a cross-connect or binding that is individually connected between a service and a transport tunnel.
  • a cross-connect or binding that is individually connected between a service and a transport tunnel.
  • each individual service and cross connect must be individually modified. This limits the ability of networks to efficiently implement and operate services across core networks, leading to significant time and expense in both managing the transport tunnels as well as the services that connect to them. Further, it inhibits the implementation for networks where a service vendor may be providing numerous services across a multitude of core networks or transport tunnels.
  • a solution is needed that enables capabilities for providing service-based data communication using transport tunnels that does not require that each individual service be reconfigured every time a transport tunnel is added, changed, or removed and that allows services to be added, changed, or removed without requiring that those provisioning such services have detailed information about the transport tunnels and how the tunnels are configured.
  • EP 1202501 discloses a hierarchical bandwidth management model for multiservice networks that provides management at a transport level and at a service/application level.
  • MPLS Multiprotocol Label Switching
  • a method of hierarchical bandwidth management in a multiservice network supporting various quality of service levels e.g. EF, AF1, AF2, BE
  • a number of applications e.g. ATM, MPLS, IP, FR
  • the method includes the steps of: establishing a transport connection tunnel (e.g. an E-Label Switched Path(LSP)) between pairs of the edge nodes in the network; and managing bandwidth of the transport connection tunnel among the quality of service levels and the applications.
  • LSP E-Label Switched Path
  • US 2003/028650 discloses a network interface unit for use intermediate a LAN and a public or private network, or a combination of both, for establishing secure links to a VPN gateway.
  • Login by a LAN client with the network interface unit addressing, authentication, and other configuration operations achieved using a web page-based GUI are applied in establishing tunnels from LAN clients to desired VPN destinations.
  • Illustrative network interface units include a DHCP server and provide encryption-decryption and encapsulation-decapsulation of data packets for communication with VPN nodes.
  • Configuration and connection of a client are further enhanced by a built-in DNS server and other functional servers to provide a high degree of autonomy in establishing connections to a desired VPN gateway via an ISP or other public and/or private network links to.
  • US 2002/116501 discloses a method for establishing a service tunnel for private internet protocol services over a connectionless network.
  • the private internet protocol services are transported over the service tunnel in accordance with selected respective private internet protocol services.
  • the invention can be implemented in numerous ways, including as a process, an apparatus, a system, a composition of matter, a computer readable medium such as a computer readable storage medium or a computer network wherein program instructions are sent over optical or electronic communication links.
  • these implementations, or any other form that the invention may take, may be referred to as techniques.
  • the order of the steps of disclosed processes may be altered within the scope of the invention.
  • SDP service-based distribution point
  • PEs provider edge routers
  • LERs label edge routers
  • CE customer edge routers
  • end destinations e.g., MAC addresses
  • the transport tunnels associated with SDPs may be established using protocols such as MPLS, MPLS-Traffic Engineering (MPLS-TE), IP, or other types of generic routing (e.g., GRE) protocols.
  • MPLS-TE MPLS-Traffic Engineering
  • IP IP
  • GRE generic routing
  • label-switched paths may be associated (as individual paths or sub-paths) with SDPs.
  • a service or set of services may be mapped or bound to one or more SDPs.
  • Packets associated with a service may be transported via a transport tunnel associated with an SDP to which the service is bound.
  • an SDP Regardless of the core network protocol in use, an SDP enables improved service control, monitoring, configuration, and other capabilities.
  • Figure 1 illustrates a system for binding services directly to individual label switched paths.
  • Services 102-106 send data to provider edge (PE) router A via LSP A 112 using cross connects (CC) 108, 116, and 120, respectively.
  • Service 102-106 send data to PE router B via LSP B 114 using cross connects 110, 118, and 122, respectively.
  • Each service 102-106 is individually configured with an independent cross connect for each LSP. Fewer or more cross connects and services may be implemented, but where multiple services are employed, management, monitoring, and control may become increasingly complicated. For example, a change to LSP 112 would require that each of cross connects 108, 116, and 120 be reconfigured to reflect the change.
  • FIG 2A illustrates an exemplary system 200 in which transport tunnels bound to service-based distribution points (SDPs) are used to provide service-based transport of network traffic.
  • Services 1-3 labeled 202-206, in Figure 2A , are bound by SDP mapping module 208 to one or more of SDPs 210-216. While the SDP mapping module 208 is shown as a single box in Figure 2A , in some embodiments it may be implemented as a set of individual cross-connects binding each service to one or more of SDPs 210-216.
  • SDPs 210-216 may be implemented having one or more transport tunnels (e.g., LSPs) associated with each SDP.
  • the transport tunnels may be static or dynamic.
  • each SDP comprises a distribution point for a single destination (egress) PE router.
  • Each SDP may have multiple services bound or mapped to it by the SDP mapping module 208.
  • an ingress PE router may have more than one SDP associated with the same destination (egress) PE, but each service may be bound or mapped only to one SDP for each destination to which the service may be configured to send data.
  • LSPs are one example of a type of transport tunnel that may be associated with an SDP for transporting service packets across an MPLS core network. With other types of core networks or networks that may use different core routing protocols, other types of paths may be used.
  • each SDP 210-216 may be treated as a distribution point having one or more associated transport tunnels that connect a near-endpoint with a far-endpoint/destination, to which one or more services may be mapped in order to enable the service(s) to send service packets (or service data in some other form) to the destination associated with the SDP.
  • the services 202-206 can be configured independently of the transport tunnels, and vice versa, thereby simplifying the provisioning and/or reconfiguration of each.
  • an LSP in SDP 1 (210) were added, removed, or changed, the information about the LSP would only have to be modified once, in the SDP.
  • the services 202-206 which are in the system 200 bound by the SDP mapping module 208 to the SDP and not directly to the transport tunnels associated with the SDP, would not require any change.
  • services could be added, removed, or changed without requiring that multiple cross connects to a plurality of LSPs (or other transport paths) be modified.
  • an SDP has several attributes for providing service-based data communication capabilities.
  • these attributes include an address (e.g., IP address) for a far-end destination (e.g., PE or other egress equipment or node) that represents an endpoint to which network traffic associated with the service may be sent for further delivery to a customer destination associated with the service, the type of encapsulation used to transport data to the destination (e.g., GRE, MPLS, L2TP, etc.), a path used to reach a far-end destination (where applicable, e.g., MPLS), and the maximum transmission unit (MTU) for the path.
  • IP address e.g., IP address
  • a far-end destination e.g., PE or other egress equipment or node
  • MTU maximum transmission unit
  • An SDP provides control capabilities using these attributes that determine how service packets (i.e., packets transported to implement a specific service such as a virtual leased line (VLL) or other type of service provided by a vendor or service provider, etc.) are transported and handled on an end-to-end basis throughout the network.
  • An SDP may be used to transport packets associated with a single service or multiple services. By grouping multiple LSPs or paths into a single transport tunnel (SDP), services packets may be load shared among the LSPs comprising the SDP. That is, packets may be distributed among several paths for routing to an end service destination, instead of sending packets for a particular service across a single path.
  • a protocol may also be used for dynamically monitoring the end-to-end operational state of an SDP, providing the capability to determine whether the operational state of an SDP has changed and, if so, what services may be affected.
  • a "keep alive" protocol may be implemented that provides for specific header values or information that, upon de-multiplexing, may be used for operation, administrative, and maintenance (OAM) functions.
  • FIG. 2B illustrates an exemplary service-based distribution point including associated transport tunnels.
  • SDP 230 is shown having several LSPs 232-240 (assuming MPLS is in use) associated with it. In other examples where MPLS may not be in use, transport tunnels other than LSPs may be used.
  • LSPs 232-240 transport service packets between a near-end (ingress) router and one or more far-end (egress) routers associated with the SDP.
  • SDPs are represented graphically as tunnels comprising one or more component transport tunnels, such as LSPs, to convey the concept that SDPs provide a way to transport data, via the transport tunnels associated with them, to a destination associated with the SDP.
  • the SDPs do not in fact represent transport mechanisms separate from or layered on top of the transport tunnels associated with them, and instead serve as a distribution point configured to cause data packets associated with services bound to the SDP to be transported to a destination associated with the SDP via a transport tunnel (e.g., LSP) associated with the SDP.
  • LSP transport tunnel
  • FIG. 3 illustrates an exemplary system 300 having unidirectional transport tunnels interconnecting endpoints across a network.
  • This illustration shows a more detailed example of a system where SDPs may be used to provide service-based transport of data across a network or series of networks.
  • Edge service routers (ESRs) 302 and 304 are connected across network 306.
  • network 306 is illustrated as being an IP/MPLS core network. In other embodiments, other types of core network may be used.
  • CEs 308-310 send packets received from ESRs 302 and 304, respectively, to the final customer destinations to which they are addressed, such as MAC addresses within their respective customer networks.
  • CEs 308 and 310 also received from associated customer nodes packets to be transported using VLL Service 123 and deliver such packets to ESRs 302 and 304, respectively, for transport.
  • Unidirectional transport tunnels 312 and 314 provide the transport mechanism for service packet transmission and are associated with the SDPs illustrated in this example.
  • transport tunnel 312 comprises an LSP associated with SDP 324 and transport tunnel 314 comprises an LSP associated with SDP 326.
  • a service such as VLL may be implemented using bidirectional service access points 316-318.
  • other types of service e.g., VPLS, may be provided.
  • Service packets are exchanged between service access points 316-318 and transported over unidirectional transport tunnels 312 and 314.
  • virtual circuit (VC) labels 320 and 322 are applied to the service packets originating from service access points 316 and 318, respectively.
  • SDPs 324-326 forward the service packets with the appended VC labels 320-322 across unidirectional transport tunnels 312 and 314 to ESRs 302-304.
  • de-multiplexers 328 and 330 Upon receipt of the service packets with the prepended VC labels, de-multiplexers 328 and 330 identify the service packets as destined for service access points 316 or 318, based on VC labels 320-322, and route them accordingly.
  • a customer packet associated with VLL Service 123 that is sent by a source associated with CE 308 to a destination associated with CE 310 would be sent by CE 308 to ESR 302.
  • ESR 302 would receive the packet and associate the packet with VLL Service 123 (e.g., based on the port on which it was received, encapsulation used, a label or other identifying information included in the packet, etc.).
  • the service access point 316 forwards the packet to SDP 324 (either directly in the embodiment shown or via an SDP mapping module, not shown in Figure 3 but described above in connection with Figure 2A , e.g., in an embodiment in which multiple services may use the same SDP) for transport to egress ESR 304.
  • the SDP 324 encapsulates the packet for transport to ESR 304 via unidirectional transport tunnel 312, including by appending a VC label 320 that identifies the packet as being associated with Service 123.
  • SDP 324 selects a tunnel to be used to transport the packet to ESR 304.
  • the SDP 324 may be configured to bind a service to a particular LSP, e.g., a VLL service such as VLL Service 123, so that all traffic for the service is sent via the same LSP.
  • the SDP may map packets to an LSP for transport by associating the packet with a "conversation" (i.e., a related set of packets being exchanged between two endpoints) and select an LSP associated with that conversation (e.g., to prevent packets from being delivered out of order, as might happen if different packets associated with a conversation were sent via different paths.)
  • a "conversation" i.e., a related set of packets being exchanged between two endpoints
  • an LSP associated with that conversation e.g., to prevent packets from being delivered out of order, as might happen if different packets associated with a conversation were sent via different paths.
  • the destination MAC address may be used to identify the LSP to be used to transport the packet.
  • demultiplexer 330 identifies the packet as being as associated with Service 123, e.g., based on the presence of VC label 320, and delivers the original (payload) packet to service access point 318 for processing. Service access point 318 then delivers the packet to CE 310.
  • Figure 4 illustrates an exemplary service packet format for service-based transport.
  • the following packet format is an example of a type of service packet that may used to implement SDPs. Alternative formats may be used and are not limited to the illustrated embodiment.
  • IP/GRE encapsulation of an MPLS packet is used to transport packets through the core network.
  • service packet 400 includes several components 402-412.
  • Encapsulated service packet 400 comprises a media and encapsulation dependent header 402 for specifying handling of service packet 400 within the core network.
  • a media and encapsulation dependent trailer 404 may also be appended to service packet 400.
  • media and encapsulation dependent trailer 404 may not be used. Additional headers are also included to enable the separation and handling of service packet 400.
  • service packet 400 may be transported through an IP core network.
  • An IP/generic routing encapsulation (GRE) header 406 may be used for transporting service packet 400 over an IP-based network.
  • IP/GRE header 406 comprises an IP header in which the GRE protocol is specified.
  • GRE Header 408 is added to provide generic routing encapsulation for forwarding service packet 400.
  • GRE header 408 indicates MPLS as the protocol type of the IP/GRE encapsulated packet.
  • IP/GRE header 406 and GRE header 408 are used to transmit service packet 400 between edge service routers (e.g., provider edge devices configured to provide service-based transport services as described herein).
  • Service header 410 may also be used to identify the specific service that service packet 400 is intended to use.
  • a specific service may be identified using a VC label or other type of label.
  • Martini encapsulation is used.
  • Service packet data 412 constitutes the payload or portion of data intended to be delivered via the service. In other embodiments, other protocols and/or packet formats may be used.
  • FIG. 5 illustrates a service packet format for service-based distribution, in accordance with an alternative embodiment.
  • MPLS encapsulation is used to transport packets through the core network
  • Service packet 500 includes media and encapsulation dependent header 502 and, if necessary, media and encapsulation dependent trailer 504.
  • MPLS tunnel shim header 506 provides forwarding and handling information to routers and nodes within the MPLS core.
  • Service header 508 identifies service packet 500 for a particular service.
  • VC labels and service identification labels may be included within service header 508.
  • service packet data 510 provides the payload or primary data being transported between end destinations implementing a service.
  • Figures 4 and 5 illustrate examples of types of encapsulation techniques that may be used to transport packets between SERs.
  • each service within a tunnel may be uniquely identified using a service identification label (e.g., Service ID) or other form of label.
  • a service encapsulation within a tunnel provides service separation and capabilities to infer service handling on a packet-by-packet basis.
  • Martini encapsulation may be used to provide a common encapsulation method for both IP/GRE and MPLS SDPs, as illustrated in Figures 4 and 5 .
  • a Martini-encapsulated service header may be implemented as an additional label in an MPLS shim header. In other embodiments other forms of encapsulation besides Martini encapsulation may be used.
  • FIG. 6 illustrates an exemplary overall process for establishing a service-based distribution point.
  • the process shown is an example of an overall process for implementing an SDP and binding a service to it.
  • a transport tunnel e.g., LSP
  • LSP transport tunnel
  • one or more transport tunnels may be associated with an SDP.
  • the transport tunnel associated with the SDP must have as its far end destination the destination (egress) PE router (or other node or equipment) associated with the SDP.
  • a service is associated with the SDP (604). Once a transport tunnel has been associated with the SDP and a service bound to the SDP, packets associated with the service may be sent via the transport tunnel to the destination associated with the SDP.
  • FIG. 7A illustrates a process for operational service determination, in accordance with an embodiment.
  • Operational service determination may include checking configuration, testing connectivity, dynamic monitoring of the end-to-end operational state of an SDP, troubleshoot an inoperable SDP, or round trip testing.
  • OAM messaging may be used to implement operational service determination.
  • a service verify message is sent to the far-end ESR to verify that the desired service is available, properly configured, operational, and connectivity (e.g., MTU) is determined (704). It is determined whether a reply message is received (706). If a reply message is received, then the reply message is checked for data or information about the configuration of the far-end ESR with respect to the service being verified (708). If a reply message is not received, then an error message is sent to an administrator (710) and the service is kept in a non-operational state (712).
  • MTU connectivity
  • Figure 7B illustrates a process for determining a service configuration, in accordance with an embodiment.
  • the process of Figure 7B is used to implement step 708 of the process shown in Figure 7A .
  • a reply message (e.g., echo request reply message for OAM functions, etc.) is received (720).
  • the reply message is checked to determine the service configuration of the far-end destination (e.g., SER) (722). It is determined whether there is an inconsistency between the far-end ESR and near-end SER, in terms of service configuration (724).
  • SER service configuration of the far-end destination
  • the service is placed into an operational state (726). If an inconsistency between the far-end ESR service configuration and the near-end ESR service configuration is found, then an error message is sent to the network/system administrator (728) and the service is kept in a non-operational state (730).
  • FIG 8 illustrates a process for service packet handling using a service-based distribution point, in accordance with an embodiment.
  • a packet to be sent to a far-end destination such as an ESR or end service (e.g., VLL Service 123 - Figure 3 ) is received (802).
  • the received packet is associated with a service (803).
  • the packet is associated with a service based on information supplied by and/or associated with a service access point from which the packet was received.
  • the transport tunnel e.g., LSP
  • LSP transport tunnel
  • the encapsulation may include a media and encapsulation dependent header (e.g., DLC header) and/or a trailer, depending upon the media and encapsulation method used, as described above in connection with Figures 4 and 5 .
  • the service may be mapped to a particular transport tunnel (e.g., an LSP) or a tunnel assoc iated with the SDP may be selected based on such considerations as load sharing, an exchange of data with which the packet is associated (e.g., a session or "conversation" between two nodes), and/or the destination address (e.g., destination MAC address) of the packet.
  • a service header that may include a VC label to identify the packet as being associated with a particular service is applied (806).
  • Martini encapsulation or other encapsulation techniques may be used to add the service header.
  • the packet is forwarded to the far-end ESR via the tunnel identified in step 804 (808).
  • the service header is used to identify how the packet should be handled..
  • the egress ESR associates the packet with a service, e.g., based on a VC label associated with the service, and forwards the packet to a service access point associated with the service for further processing and delivery.
  • Figure 9 illustrates a process used in an embodiment to automatically remap a service to an alternate SDP in the event an SDP becomes unavailable.
  • An indication is received that an SDP has become unavailable (902).
  • the indication received in step 902 is generated as a result of a continuing or periodic process of verifying the tunnel and/or service connectivity and configuration, using a process such as described above in connection with Figures 7A and 7B . It is determined whether an alternate SDP to the destination(s) associated with the SDP that has become unavailable is available (904).
  • an alert is generated (908) and the process ends (912). If it is determined that an alternate SDP is available (906), the service(s) associated with the SDP that has become unavailable are remapped automatically to the alternate SDP (910), after which the process of Figure 9 ends (912).
  • a process similar to that shown in Figure 9 may be used within an SDP to remap a service, e.g., a VLL service, to an alternate transport tunnel (e.g., LSP) in the event of failure of a transport tunnel to which the SDP has bound a particular service.

Landscapes

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

Claims (29)

  1. Procédé pour transporter des données à travers un réseau (306) comprenant :
    association (602) d'une pluralité de tunnels de transport à un point de distribution de service (210-216) ;
    mappage (604) d'un service (202-206) au point de distribution de service (210-216) ; et
    utilisation d'un tunnel sélectionné parmi la pluralité de tunnels de transport pour transporter les données associées au service (202-206) ;
    un ou plusieurs paquets de service étant associés à chaque service, chaque paquet comprenant un en-tête de service incluant un identifiant qui associe ledit paquet avec son service correspondant, et le service (202-206) n'étant pas lié directement au tunnel sélectionné parmi la pluralité de tunnels de transport de sorte que le service (202-206) et le tunnel sélectionné parmi la pluralité de tunnels de transport peuvent être approvisionnés et modifiés indépendamment l'un de l'autre, caractérisé en ce que ledit service (202-206) est mappé au point de distribution de service (210-216) par un module de mappage de point de distribution de service (208) configuré pour mapper chacun parmi un ou plusieurs services à un ou plusieurs points de distribution de service correspondants, et en ce que le point de distribution de service (210-216) est configuré pour recevoir (802) un paquet associé au service (202-206) et pour sélectionner le tunnel de transport pour transporter le paquet en se basant sur ladite association du tunnel de transport sélectionné avec le point de distribution de service (210-216).
  2. Procédé selon la revendication 1, comprenant en outre la réalisation d'une détermination opérationnelle du service et du tunnel de transport.
  3. Procédé selon la revendication 2, dans lequel la réalisation d'une détermination opérationnelle comprend en outre la vérification du tunnel de transport.
  4. Procédé selon la revendication 2, dans lequel la réalisation d'une détermination opérationnelle comprend en outre l'envoi (704) d'un message à un point terminal.
  5. Procédé selon la revendication 2, dans lequel la réalisation d'une détermination opérationnelle comprend en outre la réception (720) d'un message de réponse en réponse à un message envoyé à un point terminal.
  6. Procédé selon la revendication 2, dans lequel la réalisation d'une détermination opérationnelle comprend en outre la vérification (722) que le service est bien configuré au niveau d'une destination distante associée au point de distribution de service (210-216).
  7. Procédé selon la revendication 1, dans lequel le tunnel de transport comprend un chemin de commutation d'étiquettes (LSP).
  8. Procédé selon la revendication 1, dans lequel le point de distribution de service (210-216) comprend un premier point de distribution de service (210-216) associé à une destination distante et le procédé inclut en outre :
    réception (902) d'une indication selon laquelle le premier point de distribution de service (210-216) est devenu indisponible ; et
    re-mappage automatique (910) du service vers un deuxième point de distribution de service (210-216) associé à la destination distante.
  9. Procédé selon la revendication 8, comprenant en outre la détermination si le deuxième point de distribution de service associé à la première destination distante est disponible.
  10. Procédé selon la revendication 1, dans lequel l'utilisation du tunnel de transport pour transporter les données associées au service comprend :
    réception (802) d'un paquet associé au service (202-206) ;
    encapsulation (806) du paquet avec un en-tête de service (410, 508) ; et
    transmission (808) du paquet vers une destination distante associée au point de distribution de service (210-216) par le biais du tunnel de transport.
  11. Procédé selon la revendication 10, dans lequel l'en-tête de service (508) comprend un identifiant associé au service (202-206).
  12. Procédé selon la revendication 11, dans lequel l'identifiant associé au service comprend une étiquette de circuit virtuelle associée au service (202-206).
  13. Procédé selon la revendication 10, dans lequel l'en-tête de service (508) est utilisé à la destination distante pour associer le paquet au service (202-206).
  14. Procédé selon la revendication 1, dans lequel le réseau (306) comprend une combinaison de deux composants de réseau ou plus.
  15. Procédé selon la revendication 1, dans lequel le réseau (306) comprend un réseau de protocole Internet (IP).
  16. Procédé selon la revendication 15, dans lequel le tunnel de transport comprend un tunnel IP/GRE.
  17. Procédé selon la revendication 1, dans lequel le réseau comprend un réseau MPLS.
  18. Procédé selon la revendication 17, dans lequel le tunnel de transport comprend un chemin de commutation d'étiquettes (LSP).
  19. Procédé selon la revendication 1, dans lequel le tunnel de transport comprend un premier tunnel de transport et le procédé comprend en outre l'association d'un ou de plusieurs tunnels de transport supplémentaires avec le point de distribution de service (210-216).
  20. Procédé selon la revendication 19, comprenant en outre la mise en oeuvre du partage de la charge entre les tunnels de transport associés au point de distribution de service (210-216).
  21. Procédé selon la revendication 20, comprenant en outre le mappage du service (202-206) à un tunnel sélectionné parmi les tunnels de transport associés au point de distribution de service (210-216).
  22. Procédé selon la revendication 1, dans lequel le service (202-206) comprend un premier service et le procédé comprend en outre le mappage d'un ou de plusieurs services supplémentaires au point de distribution de service (210-216).
  23. Procédé selon la revendication 1, dans lequel le point de distribution de service (210-216) comprend un premier point de distribution de service, le tunnel de transport comprend un premier tunnel de transport, le service (202-206) comprend un premier service et le procédé inclut en outre :
    association d'un deuxième tunnel de transport avec un deuxième point de distribution de service ;
    mappage d'un deuxième service au deuxième point de distribution de service ; et
    utilisation du deuxième tunnel de transport pour transporter les données associées au service.
  24. Procédé selon la revendication 1, dans lequel le point de distribution de service (210-216) comprend un parmi une pluralité de points de distribution de service, le tunnel de transport comprend un parmi une pluralité de tunnels de transport, le service (202-206) comprend un parmi une pluralité de services et le procédé inclut en outre :
    association de chacun de ladite pluralité de tunnels de transport avec l'un desdits points de distribution de service ;
    mappage de chacun de ladite pluralité de service à un ou plusieurs parmi ladite pluralité de points de distribution de service ; et
    transport des données associées à chacun parmi ladite pluralité de services en utilisant un tunnel de transport associé à un point de distribution de service auquel le service a été mappé.
  25. Système de transport de données comprenant :
    une interface d'entrée configurée pour recevoir un paquet associé à un service (202-206) ; et
    un processeur configuré pour associer une pluralité de tunnels de transport à un point de distribution de service (210-216), pour mapper ledit service (202-206) au point de distribution de service (210-216) et utiliser un tunnel sélectionné parmi la pluralité de tunnels de transport pour transporter les données associées au service (202-206) ;
    le service (202-206) n'étant pas lié directement au tunnel sélectionné parmi la pluralité de tunnels de transport de sorte que le service (202-206) et le tunnel sélectionné parmi la pluralité de tunnels de transport peuvent être approvisionnés et modifiés indépendamment l'un de l'autre, caractérisé en ce que ledit service (202-206) est mappé au point de distribution de service (210-216) par un module de mappage de point de distribution de service (208) configuré pour mapper chacun parmi un ou plusieurs services à un ou plusieurs points de distribution de service correspondants, et en ce que le point de distribution de service (210-216) est configuré pour recevoir ledit paquet associé au service (202-206) et pour sélectionner le tunnel de transport pour transporter le paquet en se basant sur ladite association du tunnel de transport sélectionné avec le point de distribution de service (210-216).
  26. Système de transport de données selon la revendication 25, dans lequel le processeur est en outre configuré pour encapsuler lesdites données associées au service (202-206) en utilisant un en-tête de service (410, 508) qui inclut un identifiant associé au service (202-206).
  27. Système de transport de données selon la revendication 25, dans lequel l'identifiant comprend une étiquette de circuit virtuelle.
  28. Système de transport de données selon la revendication 25, dans lequel le système de transport de données comprend un routeur.
  29. Produit de programme informatique pour transporter des données à travers un réseau (306), le produit de programme informatique étant intégré dans un support lisible par ordinateur et comprenant des instructions machine pour :
    associer (602) une pluralité de tunnels de transport à un point de distribution de service (210-216) ;
    mapper (604) un service (202-206) au point de distribution de service (210-216) ; et utiliser un tunnel sélectionné parmi la pluralité de tunnels de transport pour transporter les données associées au service (202-206) ;
    un ou plusieurs paquets de service étant associés à chaque service, chaque paquet comprenant un en-tête de service incluant un identifiant qui associe ledit paquet avec son service correspondant, et le service (202-206) n'étant pas lié directement au tunnel sélectionné parmi la pluralité de tunnels de transport de sorte que le service (202-206) et le tunnel sélectionné parmi la pluralité de tunnels de transport peuvent être approvisionnés et modifiés indépendamment l'un de l'autre, caractérisé en ce que ledit service (202-206) est mappé au point de distribution de service (210-216) par un module de mappage de point de distribution de service (208) configuré pour mapper chacun parmi un ou plusieurs services à un ou plusieurs points de distribution de service correspondants, et en ce que le point de distribution de service (210-216) est configuré pour recevoir (802) un paquet associé au service (202-206) et pour sélectionner le tunnel de transport pour transporter le paquet en se basant sur ladite association du tunnel de transport sélectionné avec le point de distribution de service (210-216).
EP04300235A 2003-04-28 2004-04-28 Réseau de transport supportant des tunnels pour fournir un transport de données basé sur le service Expired - Fee Related EP1478129B1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US46634003P 2003-04-28 2003-04-28
US466340P 2003-04-28
2003-07-18
US10/833,489 US8098649B2 (en) 2003-04-28 2004-04-27 Using network transport tunnels to provide service-based data transport

Publications (3)

Publication Number Publication Date
EP1478129A2 EP1478129A2 (fr) 2004-11-17
EP1478129A3 EP1478129A3 (fr) 2007-03-14
EP1478129B1 true EP1478129B1 (fr) 2011-02-23

Family

ID=33479250

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04300235A Expired - Fee Related EP1478129B1 (fr) 2003-04-28 2004-04-28 Réseau de transport supportant des tunnels pour fournir un transport de données basé sur le service

Country Status (3)

Country Link
US (1) US8098649B2 (fr)
EP (1) EP1478129B1 (fr)
DE (1) DE602004031477D1 (fr)

Families Citing this family (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7447207B2 (en) * 2003-10-27 2008-11-04 Hewlett-Packard Development Company, L.P. Method of and apparatus for transporting SCSI data over a network
US7558219B1 (en) 2004-08-30 2009-07-07 Juniper Networks, Inc. Multicast trees for virtual private local area network (LAN) service multicast
US7990965B1 (en) 2005-07-28 2011-08-02 Juniper Networks, Inc. Transmission of layer two (L2) multicast traffic over multi-protocol label switching networks
US9166807B2 (en) 2005-07-28 2015-10-20 Juniper Networks, Inc. Transmission of layer two (L2) multicast traffic over multi-protocol label switching networks
US7564803B1 (en) 2005-08-29 2009-07-21 Juniper Networks, Inc. Point to multi-point label switched paths with label distribution protocol
US7787380B1 (en) 2006-06-30 2010-08-31 Juniper Networks, Inc. Resource reservation protocol with traffic engineering point to multi-point label switched path hierarchy
US7742482B1 (en) 2006-06-30 2010-06-22 Juniper Networks, Inc. Upstream label assignment for the resource reservation protocol with traffic engineering
US7839862B1 (en) 2006-06-30 2010-11-23 Juniper Networks, Inc. Upstream label assignment for the label distribution protocol
US8531941B2 (en) * 2007-07-13 2013-09-10 Cisco Technology, Inc. Intra-domain and inter-domain bridging over MPLS using MAC distribution via border gateway protocol
US7873060B2 (en) 2008-10-18 2011-01-18 Fortinet, Inc. Accelerating data communication using tunnels
US8077726B1 (en) 2008-12-10 2011-12-13 Juniper Networks, Inc. Fast reroute for multiple label switched paths sharing a single interface
US8675494B2 (en) * 2009-12-04 2014-03-18 Brocade Communications Systems, Inc. Conflict identification in label switched services
US8520680B1 (en) 2010-03-26 2013-08-27 Juniper Networks, Inc. Address learning in a layer two bridging network
US8619788B1 (en) * 2010-06-14 2013-12-31 Juniper Networks, Inc. Performing scalable L2 wholesale services in computer networks
US9246838B1 (en) 2011-05-27 2016-01-26 Juniper Networks, Inc. Label switched path setup using fast reroute bypass tunnel
US8675664B1 (en) 2011-08-03 2014-03-18 Juniper Networks, Inc. Performing scalable L2 wholesale services in computer networks using customer VLAN-based forwarding and filtering
US8837479B1 (en) 2012-06-27 2014-09-16 Juniper Networks, Inc. Fast reroute between redundant multicast streams
US8997094B2 (en) * 2012-06-29 2015-03-31 Pulse Secure, Llc Migrating virtual machines between computing devices
US9331940B2 (en) 2012-08-28 2016-05-03 Alcatel Lucent System and method providing distributed virtual routing and switching (DVRS)
US9049148B1 (en) 2012-09-28 2015-06-02 Juniper Networks, Inc. Dynamic forwarding plane reconfiguration in a network device
CN104054305A (zh) * 2012-12-26 2014-09-17 华为技术有限公司 一种ip数据包的发送方法及标签交换路由器
US8953500B1 (en) 2013-03-29 2015-02-10 Juniper Networks, Inc. Branch node-initiated point to multi-point label switched path signaling with centralized path computation
CN103490972B (zh) * 2013-09-27 2016-06-22 迈普通信技术股份有限公司 多链路隧道报文传输方法及系统
US20150381445A1 (en) * 2014-06-30 2015-12-31 Alcatel-Lucent Canada, Inc. Retaining service configuration during test connection
US9806895B1 (en) 2015-02-27 2017-10-31 Juniper Networks, Inc. Fast reroute of redundant multicast streams
US10158565B2 (en) * 2016-08-26 2018-12-18 Cisco Technology, Inc. Network services across non-contiguous subnets of a label switched network separated by a non-label switched network
US10170304B1 (en) 2017-10-25 2019-01-01 Globalfoundries Inc. Self-aligned nanotube structures
JP6805194B2 (ja) * 2018-02-15 2020-12-23 日本電信電話株式会社 経路情報転送装置、経路情報転送方法および経路情報転送プログラム

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5878129A (en) * 1997-02-20 1999-03-02 Ameritech Corporation Method and system for distributing messages from a signal transfer point to a plurality of service control points
US6795445B1 (en) 2000-10-27 2004-09-21 Nortel Networks Limited Hierarchical bandwidth management in multiservice networks
US7225259B2 (en) * 2001-02-21 2007-05-29 Nokia Inc. Service tunnel over a connectionless network
US7139276B1 (en) * 2001-02-27 2006-11-21 Cisco Technology, Inc. Load sharing between L2TP tunnels
US20030115480A1 (en) * 2001-12-17 2003-06-19 Worldcom, Inc. System, method and apparatus that employ virtual private networks to resist IP QoS denial of service attacks
US7269157B2 (en) * 2001-04-10 2007-09-11 Internap Network Services Corporation System and method to assure network service levels with intelligent routing
JP4501310B2 (ja) * 2001-05-28 2010-07-14 株式会社日立製作所 パケット転送装置
US7152115B2 (en) * 2001-07-12 2006-12-19 Nortel Networks Limited Virtual private networks
US7827292B2 (en) * 2001-07-23 2010-11-02 At&T Intellectual Property Ii, L.P. Flexible automated connection to virtual private networks
US7184434B2 (en) * 2002-03-28 2007-02-27 Tropic Networks Inc. Label distribution protocol supporting multiple classes of service in a multi protocol label switching (MPLS) network, methods and MPLS network using thereof
US7269135B2 (en) * 2002-04-04 2007-09-11 Extreme Networks, Inc. Methods and systems for providing redundant connectivity across a network using a tunneling protocol
US7477657B1 (en) * 2002-05-08 2009-01-13 Juniper Networks, Inc. Aggregating end-to-end QoS signaled packet flows through label switched paths
US20040165600A1 (en) * 2003-02-21 2004-08-26 Alcatel Customer site bridged emulated LAN services via provider provisioned connections

Also Published As

Publication number Publication date
US20050013295A1 (en) 2005-01-20
US8098649B2 (en) 2012-01-17
EP1478129A3 (fr) 2007-03-14
EP1478129A2 (fr) 2004-11-17
DE602004031477D1 (de) 2011-04-07

Similar Documents

Publication Publication Date Title
EP1478129B1 (fr) Réseau de transport supportant des tunnels pour fournir un transport de données basé sur le service
US7486622B2 (en) OAM echo messaging to verify a service-based network distribution path
US7570648B2 (en) Enhanced H-VPLS service architecture using control word
US9225622B2 (en) OAM echo messaging to verify a service-based network distribution path
EP2367320B1 (fr) Communication de chemin de réseau et informations d'état dans des réseaux à rattachement multiple
US9166807B2 (en) Transmission of layer two (L2) multicast traffic over multi-protocol label switching networks
US8565235B2 (en) System and method for providing transparent LAN services
US7486674B2 (en) Data mirroring in a service
EP1693996B1 (fr) Découverte automatique des adresses d'homologues pseudo-wire dans des réseaux Ethernet
US20070140235A1 (en) Network visible inter-logical router links
US20080049621A1 (en) Connection-Oriented Communications Scheme For Connection-Less Communications Traffic
US20060146832A1 (en) Method and system for transporting data using pseudowire circuits over a bridged network
US7263106B2 (en) System and protocol for frame relay service over the internet
US20060126659A1 (en) Methods, apparatus and data structures for preserving address and service level information in a virtual private network
US20040202199A1 (en) Address resolution in IP interworking layer 2 point-to-point connections
JP2004328752A (ja) Ｏａｍ機能を可能にするアドレスの挿入
WO2009135392A1 (fr) Procédé, système et dispositif de commande de signalisation
EP1848160B1 (fr) Procédé et appareil de consolidation de trafic IP de gestion
JP6332544B1 (ja) ネットワーク管理装置、ネットワークシステム、方法、及びプログラム
US20030208525A1 (en) System and method for providing transparent lan services
JP2019103117A (ja) ネットワーク管理装置、方法、及びプログラム
WO2012084626A1 (fr) Procédé pour des communications entre domaines
WO2005018145A1 (fr) Systeme et procede de fourniture de services de reseau lan transparents
KR100730024B1 (ko) 지알이 터널을 기반 가상 사설 네트워크 및 지알이 터널을기반으로 하는 회선 다중화 방법

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

AK Designated contracting states

Kind code of ref document: A2

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

AX Request for extension of the european patent

Extension state: AL HR LT LV MK

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

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

AX Request for extension of the european patent

Extension state: AL HR LT LV MK

17P Request for examination filed

Effective date: 20070914

AKX Designation fees paid

Designated state(s): DE ES FR GB IT

17Q First examination report despatched

Effective date: 20080317

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE ES FR GB IT

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 602004031477

Country of ref document: DE

Date of ref document: 20110407

Kind code of ref document: P

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602004031477

Country of ref document: DE

Effective date: 20110407

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110603

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20111124

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602004031477

Country of ref document: DE

Effective date: 20111124

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110223

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

Owner name: ALCATEL-LUCENT USA INC., US

Effective date: 20130619

REG Reference to a national code

Ref country code: FR

Ref legal event code: GC

Effective date: 20140225

REG Reference to a national code

Ref country code: FR

Ref legal event code: RG

Effective date: 20141015

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 12

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20160421

Year of fee payment: 13

Ref country code: GB

Payment date: 20160421

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20160421

Year of fee payment: 13

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602004031477

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20170428

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20171229

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20171103

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170502

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170428