EP2797259B1 - Verfahren zur erstellung eines ringnetzwerketikettschaltwegs, zugehörige vorrichtung und kommunikationssystem - Google Patents

Verfahren zur erstellung eines ringnetzwerketikettschaltwegs, zugehörige vorrichtung und kommunikationssystem Download PDF

Info

Publication number
EP2797259B1
EP2797259B1 EP13738884.9A EP13738884A EP2797259B1 EP 2797259 B1 EP2797259 B1 EP 2797259B1 EP 13738884 A EP13738884 A EP 13738884A EP 2797259 B1 EP2797259 B1 EP 2797259B1
Authority
EP
European Patent Office
Prior art keywords
node
path
label switched
switched path
label
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.)
Active
Application number
EP13738884.9A
Other languages
English (en)
French (fr)
Other versions
EP2797259A1 (de
EP2797259A4 (de
Inventor
Guoyi Chen
Lianshu Zheng
Jie Dong
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP2797259A1 publication Critical patent/EP2797259A1/de
Publication of EP2797259A4 publication Critical patent/EP2797259A4/de
Application granted granted Critical
Publication of EP2797259B1 publication Critical patent/EP2797259B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/12—Discovery or management of network topologies
    • 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/42—Loop networks
    • H04L12/437—Ring fault isolation or reconfiguration
    • 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/40—Bus networks
    • H04L12/40006—Architecture of a communication node
    • H04L12/40013—Details regarding a bus controller
    • 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/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • 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/4637—Interconnected ring systems
    • 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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method for creating a ring network label switched path, a related device, and a communications system.
  • Network availability is a critical indicator for operators.
  • the network availability directly affects the fulfillment of the service level agreement (SLA, Service Level Agreement) by the operators.
  • SLA Service Level Agreement
  • a ring network protection mechanism is an important means for ensuring high network availability.
  • P2P Point to Point
  • LSP Label Switch Path
  • a master point to point LSP and a backup point to point LSP are created between each two nodes in an existing access ring network.
  • LSP protection switching mainly adopts a Wrapping or Steering manner.
  • US2012/281705 A1 discloses a method for protection switching in a multi-protocol label switching (MPLS) ring network with a protection label switch path that is shared by multiple working label switch paths.
  • MPLS multi-protocol label switching
  • Embodiments of the present invention provide a method for creating a ring network label switched path, a device, and a communications system, so as to reduce the number of created ring network label switched paths and maintenance complexity.
  • an embodiment of the present invention provides a method for creating a ring network label switched path, including:
  • an embodiment of the present invention further provides a network node, including:
  • an embodiment of the present invention further provides a communications system, including: the network node according to the foregoing embodiment.
  • a first node receives a first Path message used for creating a first label switched path from a second node; allocates a first label to the first label switched path; sends a first Resv message carrying the first label to the second node; and when the first node receives a second Path message used for creating a second label switched path from the second node and determines that a destination node of the second label switched path is the same as that of the first label switched path, and the first node, the second node, and the destination node are located in a same ring network, allocates the first label to the second label switched path; and sends, to the second node, a second Resv message carrying the first label allocated to the second label switched path.
  • a node in a ring network allocates a same path label to identical path segments of LSPs passing through the node and having a same destination node, so as to merge identical path segments of LSPs having a same destination node on the ring network to some extent, which helps greatly reduce the number of LSPs to be created and maintained by each node on the ring network, and further reduces the LSP control overhead.
  • Embodiments of the present invention provide a method for creating a ring network LSP, a related device, and a communications system, so as to reduce the number of created ring network label switched paths and the maintenance complexity.
  • a control plane is a control network running in a network, a corresponding control channel is provided by the network, and a multi-protocol label switching (MPLS, Multi-Protocol Label Switching) protocol family runs on the control plane.
  • MPLS protocol family includes a routing protocol, a signaling protocol, and so on, where the routing protocol is mainly responsible for collecting network topology information (including node and link information, and the like) and calculating a path that a connection passes through; and the signaling protocol is mainly responsible for creating a network connection according to a calculated path.
  • a MPLS resource reservation protocol-traffic engineering (RSVP-TE, Resource reSerVation Protocol-Traffic Engineering) is adopted.
  • RSVP-TE Resource reservation protocol-traffic engineering
  • a message and an object mentioned in the embodiments of the present invention may be a message and an object in the MPLS RSVP-TE.
  • a direction for transferring service data from a first node to a last node is referred to as a Downstream direction, and may also be referred to as a forward direction, that is, a direction in which a path request (Path) message is sent; whereas, a direction for transferring a resource reservation (Resv) message corresponding to the Path message from the last node to the first node is referred to as an Upstream direction, and may also be referred to as a reverse direction, that is, a direction in which a Resv message is sent.
  • the Path message is a message type defined in the RSVP-TE.
  • a Path message may be sent from a source node (the first node) to a destination node (the last node) along a calculated path, so as to instruct all nodes along the path to create a connection.
  • the Resv message is also a message type defined in the RSVP-TE.
  • a Resv message may be sent from the last node to the source node.
  • An LSP connection may be created by using a Resv message along with a Path message.
  • a direction in which a Path message is received is referred to as a forward incoming direction
  • a direction in which a Path message is sent is referred to as a forward outgoing direction
  • a direction in which a Resv message is received is referred to as a reverse incoming direction
  • a direction in which a Resv message is sent is referred to as a reverse outgoing direction.
  • a node between the first node and the last node may be referred to as an intermediate node. The number of the intermediate nodes may be 0, 1, or more.
  • a node which sends a Path message may be referred to as an upstream node and a node which receives a Path message is a downstream node.
  • a node which sends a Resv message may be referred to as a downstream node and a node which receives a Resv message is an upstream node. It can be understood that an upstream node and a downstream node are relative. Certainly, the first node may be referred to as an upstream node of all the other nodes and the last node may be referred to as a downstream node of all the other nodes.
  • FIG. 1-b shows a ring network topology structure.
  • a node A, a node B, a node C, node D, a node E, and a node F are located in a same ring network.
  • the solution of the embodiments of the present invention is mainly applied to creation of a ring network LSP.
  • a ring node mentioned in the following embodiments of the present invention is a shortened form for a node located in a ring network.
  • the method may include: collecting, by a third node, network topology information; when the third node determines, according to the collected network topology information, that the third node is located in a same ring network as a fourth node, calculating, by the third node, according to the collected network topology information, a shortest path to the fourth node and taking it as a primary path; calculating a shortest path to the fourth node which does not pass through a next hop node of the foregoing shortest path and taking it as a backup path; and sending, by the third node, a Path message to nodes on the primary path and the backup path, so as to trigger creation of a primary LSP and a secondary LSP from the third node to the fourth node.
  • a method for creating a ring network label switched path includes: 201: A third node collects network topology information.
  • each node on a ring network may implement advertisement and discovery of a ring network topology by using an interior gateway protocol (IGP, Interior Gateway Protocols) or another protocol, so that each node on the ring network may learn a ring network topology structure.
  • IGP Interior Gateway Protocol
  • a ring identifier may be configured for each node or an interface of each node on the ring network, where the Ring ID may identify a home ring of each node and an interface of each node (namely, a ring network to which each node and the interface of each node belong).
  • Each node may advertise a Ring ID of the interface of each node as a part of an interface parameter to another network node through a type-length-value (TLV, Type-Length-Value) field (or another field) of an extended IGP protocol message, thereby enabling another node (for example, a router) in the network to learn which interfaces of which nodes in the network are located in a same ring network (Ring IDs of interfaces of nodes located in the same ring network are the same).
  • TLV Type-Length-Value
  • the third node may collect network topology information.
  • the network topology information includes: a ring identifier that is advertised by at least another one node in the same ring network where the third node is located, and is corresponding to the at least another one node or at least one interface of the at least another one node.
  • the third node may also advertise the ring identifier corresponding to the third node or at least one interface of the third node, so that another node collects network topology information.
  • the third node may calculate, according to the collected network topology information, a shortest path to the fourth node and use it as a primary path; and calculate a shortest path to the fourth node which does not pass through a next hop node of the foregoing shortest path and use it as a backup path.
  • Nodes that the primary path and the backup path from the third node to the fourth node pass through are all located in the same ring network.
  • the third node sends a Path message to downstream nodes on the primary path and the backup path to trigger creation of a primary LSP and a secondary LSP from the third node to the fourth node.
  • the third node may carry an indication of allowing LSP merging in a Path message that is sent to a downstream node on the primary path (and/or the backup path) to the fourth node, so as to indicate that an LSP that the Path message triggers to create allows being merged (merge), according to which the downstream node on the primary path (and/or the backup path) from the third node to the fourth node may learn that merging processing is allowed for identical path segments (where, all nodes on the identical path segments are also nodes on the same ring network) between the LSP that the Path message triggers to create and an LSP that another node on the same ring network triggers to create and having a same destination node (that is, both the destination nodes are the fourth node).
  • the indication of allowing LSP merging may include, for example, a ring identifier (Ring ID), so as to indicate that the LSP is initiated by a node on a ring network.
  • Ring ID ring identifier
  • the Path message may also not carry an indication of allowing LSP merging.
  • another node on the ring network may be considered by default that merging processing is allowed for identical path segments between the LSP that the Path message triggers to create and an LSP that another node on the ring network triggers to create and having the same destination node.
  • another node on the ring network may also directly allow, by default, merging processing on identical path segments between the LSP that the Path message triggers to create and an LSP that another node triggers to create and having the same destination node.
  • the third node and another node located in the same ring network as the third node similarly may trigger, based on the foregoing mechanism, to create a primary LSP and a secondary LSP to another node on the ring network.
  • the third node and another node located in the same ring network as the third node similarly may also trigger, based on the foregoing mechanism, to create a primary LSP to another node on the ring network, but do not trigger to create a secondary LSP.
  • the method may include: receiving, by a first node, a first Path message used for creating a first label switched path from a second node; allocating, by the first node, a first label to the first label switched path; sending, by the first node, a first Resv message carrying the first label to the second node; and when the first node receives a second Path message used for creating a second label switched path from the second node and determines that a destination node of the second label switched path is the same as that of the first label switched path, and the first node, the second node, and the destination node are located in a same ring network, allocating, by the first node, the first label to the second label switched path; and sending, to the second node, a second Resv message carrying the first label allocated to the second label switched path.
  • another method for creating a ring network label switched path includes: 301: A first node receives a first Path message used for creating a first label switched path from a second node.
  • the second node may be a source node of the first label switched path. Certainly, the second node may also be an intermediate node of the first label switched path.
  • the first node may be a destination node of the first label switched path. Certainly, the first node may also be an intermediate node of the first label switched path.
  • each node on a ring network may implement advertisement and discovery of a ring network topology by using an interior gateway protocol (IGP) or another protocol, so that each node on the ring network may learn a ring network topology structure.
  • IGP interior gateway protocol
  • a ring identifier may be configured for each node or an interface of each node on the ring network, where the Ring ID may identify a home ring of each node and an interface of each node (namely, a ring network to which each node and the interface of each node belong).
  • Each node may advertise a Ring ID of the interface of each node as a part of an interface parameter to another network node through a type-length-value (TLV) field (or another field) of an extended IGP protocol message, thereby enabling another node (for example, a router) in the network to learn which interfaces of which nodes in the network are located in a same ring network (Ring IDs of interfaces of nodes located in the same ring network are the same).
  • TLV type-length-value
  • the first node may also advertise a Ring ID corresponding to the first node or at least one interface of the first node; and/or the first node may collect network topology information; the network topology information includes: a Ring ID that is advertised by at least another one node in the same ring network where the first node is located and is corresponding to the at least another one node or at least one interface of the at least another one node.
  • the first node allocates a first label to the first label switched path.
  • the first node sends a first Resv message carrying the first label to the second node.
  • the first node may also reserve a corresponding resource for the first label switched path.
  • the first Resv message may carry description information of the resource that the first node reserves for the first label switched path.
  • the first Resv message may also not carry description information of the resource that the first node reserves for the first label switched path, and after receiving the first Resv message corresponding to the first label switched path, the second node may take it by default that the required resource is already reserved for the first label switched path by the first node. The second node subsequently may send a service flow to the first node based on the first label carried in the first Resv message.
  • the first node When the first node receives a second Path message used for creating a second label switched path from the second node and determines that a destination node of the second label switched path is the same as that of the first label switched path, and the first node, the second node, and the destination node are located in the same ring network, the first node allocates the first label to the second label switched path; and sends, to the second node, a second Resv message carrying the first label allocated to the second label switched path by the first node.
  • the first node when the first node receives a second Path message used for creating a second label switched path from the second node and determines that a destination node of the second label switched path is the same as that of the first label switched path, and the first node, the second node, and the destination node are located in the same ring network, it indicates that the second label switched path and the first label switched path have identical path segments (herein, the identical path segments include a path segment from the second node to the destination node). Therefore, a node on the identical path segments may process the second label switched path and the first label switched path.
  • the first node is a node on the identical path segments.
  • a label allocated by the first node to the second label switched path is the same as a label allocated by the first node to the first label switched path (referred to as a first label).
  • a label allocated by the first node to the first label switched path referred to as a first label.
  • the first node may also reserve a corresponding resource for the second label switched path.
  • the second Resv message may carry description information of the resource that the first node reserves for the second label switched path.
  • the second Resv message may also not carry description information of the resource that the first node reserves for the second label switched path, and after receiving the second Resv message corresponding to the second label switched path, the second node may take it by default that the required resource is already reserved for the second label switched path by the first node.
  • the second node subsequently may send a service flow (the service flow may be initially sent by the source node of the first label switched path, and may also be initially sent by the source node of the second label switched path) to the first node based on the first label.
  • description information of a certain object mentioned in the embodiments of the present invention may be the object itself, or may also be any other information that can indicate the object.
  • the first Path message may carry a ring identifier of a ring network where a source node corresponding to the first label switched path is located.
  • the second Path message may carry a ring identifier of a ring network where a source node corresponding to the second label switched path is located.
  • the ring identifier of the ring network where the source node corresponding to the first label switched path is located is the same as the ring identifier of the ring network where the source node corresponding to the second label switched path is located, which indicates that the source node corresponding to the first label switched path and the source node corresponding to the second label switched path are located in the same ring network.
  • the first node after the first node receives a first Path message from the second node and used for creating a first label switched path, the first node creates a Path state information block for the first label switched path.
  • the first node After the first node receives a second Path message used for creating a second label switched path from the second node, the first node creates a Path state information block for the second label switched path, and may merge the Path state information blocks created for the first label switched path and the second label switched path (herein, the merging the Path state information, for example, may include retaining different information and de-duplicate identical information in the Path state information block corresponding to the first label switched path and the Path state information block corresponding to the second label switched path, so as to further obtain a merged Path state information block).
  • generating a Path state information block corresponding to an LSP and then merging Path state information blocks does not necessarily refer to first generating an actually existing data structure of a Path state information block, but may form, by using some indication information, a Path state information block that is flexible in a form, and the form of the indication information may be varied.
  • the first node when the first node is an intermediate node on the first label switched path (herein, because the destination node of the first label switched path is the same as that of the second label switched path, the first node is also an intermediate node of the second label switched path), after receiving a first Path message from the second node and used for creating the first label switched path, the first node may send, to a downstream node of the first label switched path, a Path message used for creating the first label switched path. The first node may send the received first Path message to the downstream node, or may also perform format conversion or protocol conversion on the received first Path message, or add/delete/modify carried information and then send it to the downstream node.
  • the first node When the first node receives, from the downstream node of the first label switch path, a third Resv message corresponding to the first label switched path, the first node creates a Resv state information block for the first label switched path.
  • the first node may send, to a downstream node of the second label switched path, a Path message used for creating the first label switched path (similarly, the first node may transparently transmit the received second Path message to a downstream node, or, the first node may also perform format conversion or protocol conversion on the received second Path message, or add/delete/modify carried information and then send it to a downstream node).
  • the first node may create a Resv state information block for the second label switched path and merge the Resv state information blocks created for the first label switched path and the second label switched path. Similar to the merging of Path state information, the merging of Resv state information, for example, may include retaining different information and de-duplicate identical information in the Resv state information block corresponding to the first label switched path and the Resv state information block corresponding to the second label switched path, so as to obtain a merged Resv state information block. By merging the Resv state information blocks, the LSP state information volume, the number of Resv state information blocks, and the like to be maintained by the first node can be reduced relatively.
  • the first node when the first node is the destination node of the first label switched path (herein, because the first label switched path and the second label switched path have the same destination node, the first node is also the destination node of the second label switched path), after receiving a first Path message from the second node and used for creating the first label switched path, the first node sends a first Resv message carrying the first label to the second node.
  • the first node may also create a Resv state information block for the first label switched path.
  • the first node After the first node receives a second Path message from the second node and used for creating the second label switched path, the first node sends a second Resv message carrying the first label to the second node.
  • the first node may also create a Resv state information block for the second label switched path.
  • the first node may merge the Resv state information blocks created for the first label switched path and the second label switched path. Similar to the merging of Path state information, the merging of Resv state information, for example, may include retaining different information and de-duplicate identical information in the Resv state information block corresponding to the first label switched path and the Resv state information block corresponding to the second label switched path, so as to obtain a merged Resv state information block.
  • the first node when the first node is an intermediate node of the second label switched path, after the first node receives a second Path message from the second node and used for creating the second label switched path, the first node may determine whether the total resource requirement of the first label switched path and the second label switched path is equal to the resource requirement of the first label switched path (for example, no bandwidth resource requirement is specified for the second label switched path). If the total resource requirement of the first label switched path and the second label switched path is equal to the resource requirement of the first label switched path (that is, no bandwidth resource requirement is specified for the second label switched path), the first node may also not send, to a downstream node of the second label switched path, a Path message for creating the second label switched path.
  • the first node and another node on the ring network where the first node is located may also merge identical path segments of LSPs passing through the node and having the same destination address based on the foregoing LSP merging mechanism.
  • a node on an LSP may also merge identical path segments of LSPs passing through the node and having the same destination address by using a similar mechanism.
  • a certain ring network includes N nodes. If each node is used as a destination node by another node on the ring network to establish two LSPs, namely, a primary LSP and a secondary LSP, after LSP merging processing is performed, only a total of 2 N LSPs are required to implement uplink or downlink communication and communication between any nodes on the ring.
  • the first node receives a first Path message from the second node and used for creating a first label switched path; allocates a first label to the first label switched path; sends a first Resv message carrying the first label to the second node; and if a second Path message used for creating a second label switched path from the second node is received and it is determined that a destination node of the second label switched path is the same as that of the first label switched path, and the first node, the second node, and the destination node are located in the same ring network, allocates the first label to the second label switched path and sends a second Resv message carrying the first label to the second node.
  • a node in a ring network allocates a same path label to identical path segments of LSPs passing through the node and having a same destination node, so as to merge identical path segments of LSPs having a same destination node on the ring network, which helps greatly reduce the number of LSPs to be created and maintained by each node on the ring network, and further reduces the LSP control overhead.
  • the first node may merge Path messages and/or Resv messages corresponding to identical path segments and used for state refreshing, and then send the messages (for example, the first node may merge Path messages and/or Resv messages corresponding to the first LSP and the second LSP and used for state refreshing, and then send the messages).
  • the first node may generate, based on the merged Path state information block, a Path message (where the Path message may carry description information of source nodes (multiple) and a destination node (one) of all the LSPs with identical path segments merged, and is used for refreshing the state of the merged LSPs) used for state refreshing and send the Path message to a downstream node.
  • the first node may also generate, based on the merged Resv state information block, a Resv message (where the Resv message may carry description information of source nodes (multiple) and a destination node (one) of all the LSPs with identical path segments merged, and is used for refreshing the state of the merged LSPs) used for state refreshing, and send the Resv message to an upstream node.
  • a Resv message (where the Resv message may carry description information of source nodes (multiple) and a destination node (one) of all the LSPs with identical path segments merged, and is used for refreshing the state of the merged LSPs) used for state refreshing, and send the Resv message to an upstream node.
  • the Resv message may carry description information of source nodes (multiple) and a destination node (one) of all the LSPs with identical path segments merged, and is used for refreshing the state of the merged LSPs
  • the Resv message may carry description information of source nodes (multiple) and a destination
  • the following describes in detail by taking a specific application scenario as an example.
  • the following describes by taking a method for creating a ring network label switched path LSP in a ring network shown in FIG. 1-b as an example.
  • Another method for creating a ring network LSP may include: 401: Each node advertises and collects network topology information.
  • each node on a ring network may implement advertisement and discovery of a ring network topology by using an interior gateway protocols (IGP) or another protocol, so that each node on the ring network may learn a ring network topology structure.
  • IGP interior gateway protocols
  • a ring identifier may be configured for an interface of each node, where the Ring ID may identify a home ring of each node and an interface of each node (namely, a ring network to which each node and the interface of each node belong).
  • Each node may advertise a Ring ID of the interface of each node as a part of an interface parameter to another network node through a type-length-value (TLV) field (or another field) of an extended IGP protocol message, thereby enabling another node (for example, a router) in the network to learn which interfaces of which nodes in the network are located in a same ring network (Ring IDs are the same).
  • TLV type-length-value
  • each node calculates a shortest path to another node and takes it as a primary path; and calculates a shortest path to the another node which does not pass through a next hop node of the foregoing shortest path and takes it as a backup path.
  • a node C initiates creation of primary and backup paths to a node A as an example.
  • the node C may determine, according to the collected network topology information, that the node C is located in the same ring network as nodes A, B, D, E, and F. Therefore, according to the collected network topology information, the node C may utilize a constraint shortest path first (CSPF, Constraint Shortest Path First) protocol and another routing calculating protocol to calculates a shortest path (C-B-A) to the node A and takes it as a primary path, and to calculate a shortest path to the node A which does not pass through a next hop node (the node B) of the foregoing shortest path and takes it as a backup path (C-D-E-F-A). Certainly, the node C may also determine the primary and backup paths to the node A (and to all the other nodes) in another other existing manner.
  • CSPF Constraint Shortest Path First
  • the node C sends a Path message to a node on the primary path from the node C to the node A, so as to trigger to create a primary LSP from the node C to the node A; and the node C sends a Path message to a node on the backup path from the node C to the node A, so as to trigger to create a secondary LSP from the node C to the node A.
  • the node C sends the Path message to nodes along the primary path (C-B-A), so as to trigger to create the primary LSP (for example, referred to as an LSP-ca1) from the node C to the node A.
  • the Path message may carry an indication of allowing LSP merging, so as to indicate that an LSP that the Path message triggers to create allows to be merged (merge), according to which other nodes may learn that merging is allowed for identical path segments between the LSP-cal that the Path message triggers to create and an LSP that another node triggers to create and having the same destination node.
  • the indication of allowing LSP merging may include, for example, a ring identifier (Ring ID), so as to indicate that the LSP is initiated by a node on a ring network.
  • Ring ID ring identifier
  • the Path message may also not carry an indication of allowing LSP merging.
  • another node on the ring network may be considered by default that merging processing is allowed for identical path segments between the LSP that the Path message triggers to create and an LSP that another node on the ring network triggers to create and having the same destination node.
  • another node on the ring network may also directly allow, by default, merging processing on identical path segments between the LSP that the Path message triggers to create and an LSP that another node triggers to create and having the same destination node.
  • the node C sends the Path message to nodes along the backup path, so as to trigger to create the secondary LSP (referred to as an LSP-ca2) from the node C to the node A.
  • the Path message may also carry an indication of allowing LSP merging (for example, a Ring ID).
  • the Path message may further carry information such as a session object (SESSION object), a sender template object (SENDER_TEMPLATE object), and a session attribute object (SESSION_ATTRIBUTE object).
  • SESSION object a session object
  • SENDER_TEMPLATE object a sender template object
  • SESSION_ATTRIBUTE object a session attribute object
  • Information carried in the Path message initiated by the node C may mainly describe the last node (the node A) and the first node (the node C) of the LSP-ca1 created under triggering, an LSP-ca1 identifier, a corresponding tunnel (Tunnel) identifier, an LSP-ca1 attribute (for example, required bandwidth), and so on.
  • the node C may also create a Path state information block (Path State Block) locally.
  • the node C may create Path State Blocks for the primary path and the backup path to the node A, respectively (the primary path and the backup path are in opposite directions).
  • the Path State Block created for the LSP-ca1 may store the description information of the last node (the node A) and the first node (the node C) of the LSP-ca1, the LSP-ca1 identifier, and the corresponding Tunnel identifier carried in the corresponding Path message.
  • the Path State Block may further store the description information of the LSP-ca1 attribute (for example, required bandwidth).
  • Path State Block created by the node C for the LSP-ca2 may store description information of the last node (the node A) and the first node (the node C) of the LSP-ca2, an LSP-ca2 identifier, and a corresponding Tunnel identifier carried in the corresponding Path message.
  • the Path State Block may further store description information of an LSP-ca2 attribute (for example, required bandwidth).
  • a node through which the Path message passes creates a Path state information block for an LSP passing through the node.
  • the node B When the Path message sent by the node C for triggering to create the LSP-ca1 of the path C-B-A reaches the node B, the node B creates a Path State Block locally for the LSP-ca1 (C-B-A).
  • the Path message used for creating the LSP-ca1 is continuously sent to the downstream node A.
  • the node A is a ring egress node (Egress), namely, the last node of the LSP-ca1.
  • the Path State Block created locally by the node B for the LSP-ca1 may store description information of the last node (the node A) and the first node (the node C) of the LSP-cal, an LSP-ca1 identifier, and a corresponding Tunnel identifier carried in the corresponding Path message.
  • the Path State Block may further store description information of an LSP-ca1 attribute (for example, required bandwidth).
  • the Path message sent by the node C for triggering to create the LSP-ca2 of the path C-D-E-F-A reaches other nodes (the nodes D, E, and F) along the path
  • the nodes D, E, and F create Path State Blocks for the LSP-ca2 locally and continuously send, to a downstream node, the Path message for creating the LSP-ca1.
  • the Path State Blocks created locally by the nodes D, E, and F for the LSP-ca2 may store description information of the last node (the node A) and the first node (the node C) of the LSP-ca2, an LSP-ca1 identifier, and a corresponding Tunnel identifier carried in the corresponding Path message.
  • the Path State Blocks may further store description information of an LSP-ca2 attribute (for example, required bandwidth).
  • the node A After receiving the Path message used for creating the LSP-ca1, the node A creates a Path State Block for the LSP-ca1 locally.
  • the Path State Block may store description information of the last node (the node A) and the first node (the node C) of the LSP-ca1, an LSP-ca1 identifier, and a corresponding Tunnel identifier.
  • the Path State Block may further store description information of an LSP-ca1 attribute (for example, required bandwidth).
  • the node A is the last node of the LSP-ca1.
  • the node A allocates a label to the LSP-ca1 and reserve a resource (for example, reserve required bandwidth), sends a Resv message in a direction opposite to that of a corresponding Path message, and creates a Resv state information block (Reservation State Block) locally.
  • the Reservation State Block includes description information of a label allocated by the node A to the LSP-ca1.
  • the node A returns a Resv message to the node B.
  • the Resv message carries the description information of the label allocated by the node A to the LSP-ca1, and may further carry the description information of the resource reserved by the node A for the LSP-ca1 (certainly, the description information of the resource reserved by the node A for the LSP-ca1 may not be carried, and the B, after receiving the Resv message, takes it by default that the required resource is already reserved by the node A).
  • the node B receives the Resv message and then creates a Resv state information block (Reservation State Block) locally.
  • the Reservation State Block may include description information of the label allocated by the node A to the LSP-ca1 and a next hop node (namely, the node A), and may further include description information of the resource reserved by the node A for the LSP-ca1.
  • the node B allocates a label to and reserves a resource for the LSP-cal, returns a Resv message to the node C.
  • the Resv message includes description information of the label allocated by the node B to the LSP-ca1.
  • the node C receives the Resv message and then creates a Reservation State Block.
  • the Reservation State Block includes the description information of the label allocated by the node B to the LSP-ca1 and a next hop node (namely, the node B), and may further include description information of the resource reserved by the node B for the LSP-ca1.
  • the node A After receiving the Path message used for creating the LSP-ca2, the node A creates a Path State Block for the LSP-ca2 locally.
  • the Path State Block may store description information of the last node (the node A) and the first node (the node C) of the LSP-ca2, an LSP-ca2 identifier, and a corresponding Tunnel identifier.
  • the Path State Block may further store description information of an LSP-ca2 attribute (for example, required bandwidth).
  • the node A is the last node of the LSP-ca2.
  • the node A allocates a label to and reserves a resource for the LSP-ca2, and sends a Resv message in a direction opposite to that of the Path message.
  • the node A returns a Resv message to an upstream node F.
  • the Resv message carries information of the label allocated by the node A to the LSP-ca2.
  • the node F receives the Resv message and then creates locally a Resv state information block, which includes the description information of the label allocated by the node A to the LSP-ca2 carried in the Resv message, and further includes description information of a next hop node (namely, the node A) and the resource reserved by the node A for the LSP-ca2.
  • the node F further locally allocates a label to and reserves a resource for the LSP-ca2, and returns a Resv message to a node E.
  • the Resv message includes description information of the label allocated by the node F to the LSP-ca2.
  • an upstream node for example, the node E and a node D, of the node F receives the Resv message, and then similarly creates a Resv state information block locally in the foregoing manner.
  • the Resv state information block may include the description information of the label of the LSP-ca2, and may further include description information of a next hop node and a resource reserved by the next hop node for the LSP-ca2.
  • the node E and the node D further locally allocate a label to and reserve a resource for the LSP-ca2.
  • the node D returns a Resv message to an upstream node C (the first node).
  • the Resv message includes description information of the label allocated by a downstream node of the first node to the LSP-ca2.
  • the node C receives the Resv message from the node D and creates a Resv state information block. So far, creation of the LSP-ca2 (C-D-E-F-A) is complete.
  • another node may also calculate a primary path and a backup path to another node according to collected network topology information and based on the foregoing example mechanism.
  • the node D calculates a shortest path to another node and takes it as a primary path; and calculates a shortest path to the another node which does not pass through a next hop node of the foregoing shortest path and takes it as a backup path.
  • the node D may determine, according to the collected network topology information, that the node D is located in the same ring network as nodes A, B, C, E, and F. Therefore, according to the collected network topology information, the node D may utilize a CSPF protocol and another routing calculating protocol to calculate a shortest path (for example, D-C-B-A) from the node D to the node A and takes it as a primary path, and to calculate a shortest path to the node A which does not pass through a next hop node (namely, the node C) of the foregoing shortest path and takes it as a backup path (namely, D-E-F-A). Certainly, the node D may also determine the primary and backup paths to the node A (and to all the other nodes) in another existing manner.
  • a CSPF protocol and another routing calculating protocol to calculate a shortest path (for example, D-C-B-A) from the node D to the node A and takes it as a primary path
  • the node D sends a Path message to a node on the primary path from the node D to the node A, so as to trigger to create a primary LSP from the node D to the node A; and the node D sends a Path message to a node on the backup path from the node D to the node A, so as to trigger to create a secondary LSP from the node D to the node A.
  • the node D sends a Path message to nodes along the primary path, so as to trigger to create a primary LSP (for example, referred to as an LSP-da1) from the node D to the node A.
  • the Path message may carry an indication of allowing LSP merging (for example, including a Ring ID), so as to indicate that an LSP that the Path message triggers to create allows to be merged, according to which other nodes may learn that merging is allowed for the LSP that the Path message triggers to create and another LSP that another node triggers to create (certainly, the Path message may also not carry an indication of allowing LSP merging, and the other nodes take it by default that merging is allowed for identical path segments between the LSP that the Path message triggers to create and an LSP created by another node and having the same destination node).
  • the node D sends the Path message to nodes along the backup path, so as to trigger to create the secondary LSP (for example, referred to as an LSP-da2) from the node D to the node A.
  • the Path message may also carry an indication of allowing LSP merging (for example, including a Ring ID).
  • a node through which the Path message passes creates a Path state information block for the corresponding LSP from the node D to the node A and passing through the node; and a node through which the Resv message passes creates a Resv state information block for the corresponding LSP from the node D to the node A and passing through the node.
  • the node C may create locally a Path state information block for the LSP-da1.
  • the node C discovers, according to information carried in the Path message, that the LSP-da1 and the LSP-ca1 (C-B-A) have the same last node and downstream path.
  • the node C may merge the Path state information block corresponding to the LSP-da1 (D-C-B-A) and the Path state information block corresponding to the LSP-ca1 (C-B-A), store description information of the first nodes, the last nodes, and the LSP attributes of the two LSPs. With regard to identical description information corresponding to the two LSPs, only one copy is stored (namely, de-duplication).
  • the node C may not send, to a downstream node, a Path message for creating the LSP-da1.
  • the node C may directly allocate a label to the LSP-da1 and then directly returns a Resv message to the upstream node D (the first node).
  • the Resv message carries description information of the label allocated by the node C to the LSP-da1.
  • the node C may continuously send, to the downstream node, the corresponding Path message for creating the LSP-da1 (D-C-B-A), so as to update the resource requirement.
  • the downstream node B receives the Path message, locally creates a Path state information block for the LSP-da1, and according to a processing manner for merging Path state information blocks similar to that of the node C, performs merging on the Path state information block corresponding to the local LSP-da1 and the Path state information block corresponding to the previously created LSP-ca1 (C-B-A) and stores description information of the first nodes, the last nodes, and the LSP attributes of the two LSPs. With regard to identical description information corresponding to the two LSPs, only one copy is stored.
  • the node B discovers, according to the information carried in the Path message, that the total resource requirement on the downstream path of the LSP-da1 and the created and merged LSP (which is the LSP-ca1) changes (for example, becoming higher, for example, the total required bandwidth becomes higher), compared with the resource requirement of the created and merged LSP (which is the LSP-ca1), the node B may continuously send, to the downstream node A, the corresponding Path message for creating the LSP-da1 (D-C-B-A), so as to update the resource requirement.
  • the node B may continuously send, to the downstream node A, the corresponding Path message for creating the LSP-da1 (D-C-B-A), so as to update the resource requirement.
  • the node A receives the Path message for triggering to create the LSP-da1 and then locally creates a Path State Block for the LSP-da1.
  • the node A may merge the Path state information block corresponding to the local LSP-da1 (D-C-B-A) and the Path state information block corresponding to the previously created LSP-ca1 (C-B-A), and store description information of the first nodes, the last nodes, and the LSP attributes of the two LSPs. With regard to identical description information of the corresponding two LSPs, only one copy is stored.
  • the node A is the last node of the LSP-da1.
  • the node A allocates a label to and reserves a resource for the LSP-da1 (the node A takes the label allocated to the LSP-cal as a label allocated to the LSP-da1, that is, the node A allocates a same path label to the LSP-da1 and the LSP-ca1).
  • the node A locally creates a Resv state information block corresponding to the LSP-da1 and may merge the Resv state information block corresponding to the locally created LSP-da1 and the Resv state information block corresponding to the LSP-ca1.
  • the node A sends a Resv message in a direction opposite to that of the corresponding Path message.
  • the node A returns a Resv message to the node B, carrying description information of the label allocated by the node A to the LSP-da1 (equivalent to the label allocated by the node A to the LSP-ca1).
  • the node B receives the Resv message and then allocates a label to and reserves a resource for the LSP-da1 (the node B takes the label allocated to the LSP-ca1 as a label allocated to the LSP-dal, that is, the node B allocates the same label to the LSP-da1 and the LSP-ca1).
  • the node B locally creates a Resv state information block for the corresponding LSP-da1 and merges the Resv state information block corresponding to the locally created LSP-da1 and the Resv state information block corresponding to the LSP-ca1.
  • the merged Resv state information block may include description information of the label (which is also the label of the LSP-ca1) allocated by the downstream node to the LSP-da1, the next hop node (the node A), and the resource reserved for the LSP-ca1.
  • the node B returns a Resv message to the node C.
  • the Resv message includes information of a label allocated by the node B to the LSP-da1 (the same as the label of the LSP-ca1).
  • the node C receives the Resv message and allocates a label and a resource to the LSP-da1.
  • the node C locally creates a Resv state information block corresponding to the LSP-da1 and merges the Resv state information block corresponding to the local LSP-da1 and the Resv state information block corresponding to the LSP-ca1.
  • the merged Resv state information block includes description information of the label allocated by the downstream node to the LSP-da1 (the same as the label by the downstream node to the LSP-ca1), the next hop node (the node B), and the resource reserved for the LSP-ca1.
  • the node C returns a Resv message to the node D.
  • the Resv message includes information of the label allocated by the node C to the LSP-da1.
  • the node D receives the Resv message.
  • the node D locally creates a Resv state information block corresponding to the LSP-da1. So far, creation of the LSP-da1 (C-B-A) is complete.
  • the node C, the node B, and the node A may also merge the Path messages and/or the Resv messages used for state refreshing and corresponding to identical path segments and then send the messages (for example, the node C, the node B, and the node A may merge the Path messages and/or the Resv messages used for state refreshing and corresponding to the LSP-da1 and the LSP-ca1, and then send the messages).
  • the node C may generate, based on the merged Path state information block, a Path message used for state refreshing and send the message to the downstream node (where the Path message may carry description information of source nodes (two) and a destination node of all the LSPs with identical path segments merged, and is used for refreshing the state of the merged LSPs).
  • the node C, the node B, and the node A may also generate, based on the merged Resv state information block, a Resv message used for state refreshing and send the message to the upstream node (where the Resv message carries description information of source nodes (two) and a destination node of all the LSPs with identical path segments merged), so as to refresh the state of the merged LSPs.
  • all the nodes passed through by the LSPs may also merge the Path/Resv state information blocks only and still send Path/Resv messages used for state refreshing to each LSP separately.
  • the node A receives the Path message sent for triggering to create the LSP-da2 and then sends a Resv message in a direction opposite to that of the Path message.
  • the Resv message passes through the node F and the node E to the node D, so as to further complete creation of the LSP-da2.
  • the node A, the node F, the node E, and the node D merge the corresponding Resv state information blocks and merge the corresponding Path state information blocks of the LSP-da2 and the LSP-ca2, and allocate the same path labels to identical path segments, respectively, and details are not repeatedly described herein.
  • the node B and the node F may perform merging processing on local state information blocks in a similar manner. It can be understood that all LSPs on the ring network from all nodes to the node A through the node B are finally merged at the node B, and all LSPs from all nodes to the node A through the node F are merged at the node F. Similar to the processing of the node B, another node on the ring network may also perform merging on identical path segments of all LSPs which pass through the node to the same last node and have the same downstream path.
  • another node may also calculate a primary path and a backup path to another node according to collected network topology information and based on the foregoing example mechanism.
  • each node on the ring network is used as the destination node, and each node only creates two Ring LSPs. Therefore, assuming that a ring including N nodes, only a total of 2N (primary + secondary; N is the number of nodes on the ring network) Ring LSPs are required to implement uplink or downlink communication, or communication between any nodes on the ring network.
  • the traffic is switched by the node E to the secondary Ring LSP (L2) which takes the node A as the egress node, and directly flows out of the ring when reaching the node A (the traffic path is E-D-C-B-A).
  • L2 the secondary Ring LSP
  • the traffic needs to first bypass the node A to reach the node F which senses the fault and then switched back to the primary path of F-A (the traffic path is E-D-C-B-A-F-A), namely, traffic bypasses between the node A and the node F.
  • the node E may advertise the fault to the node D.
  • the subsequent traffic is forwarded from the node D and along the secondary Ring LSP (L2) which takes the node A as the last node, which prevents the traffic from bypassing between D and E.
  • L2 secondary Ring LSP
  • the node E After the fault is rectified, the node E advertises it to the node D, and the subsequent traffic from the node D maybe continuously forwarded along the primary Ring LSP (L1).
  • a node in a ring network allocates a same path label to identical path segments of LSPs passing through the node and having a same destination node, so as to merge identical path segments of LSPs having a same destination node on the ring network, which helps greatly reduce the number of LSPs to be created and maintained by each node on the ring network, and further reduces the LSP control overhead.
  • the forging method embodiments are described as a combination of a series of actions.
  • a person skilled in the art should be aware that the present invention is not limited by the sequence of the described actions. According to the present invention, some steps may be implemented in another sequence or be simultaneously performed. Additionally, a person skilled in the art may also be aware that, the embodiments described in the specification all belong to preferable embodiments, in which an action and a module involved are not necessarily essential to the present invention.
  • the following provides a related apparatus for implementing the foregoing solutions.
  • an embodiment of the present invention provides a network node 600, which may include: a receiving module 610, a label allocating module 620, and a sending module 630.
  • the receiving module 610 is configured to receive a first Path message used for creating a first label switched path from a second node.
  • the label allocating module 620 is configured to allocate a first label to the first label switched path.
  • the sending module 630 is configured to send a first Resv message carrying the first label to the second node.
  • the label allocating module 620 is further configured to: when the receiving module 610 receives a second Path message used for creating a second label switched path from the second node and determines that a destination node of the second label switched path is the same as that of the first label switched path, and the network node 600, the second node, and the destination node are located in a same ring network, allocate the first label to the second label switched path.
  • the sending module 630 is further configured to send, to the second node, a second Resv message carrying the first label allocated to the second label switched path by the label allocating module 620.
  • the network node 600 may further include: a Path state information block creating module 640 and a first information block merging module 650.
  • the Path state information block creating module 640 is configured to: after the receiving module 610 receives the first Path message from the second node and used for creating the first label switched path, create a Path state information block for the first label switched path; and after the receiving module 610 receives the second Path message from the second node and used for creating the second label switched path, create a Path state information block for the second label switched path.
  • the first information block merging module 650 is configured to merge the Path state information blocks created for the first label switched path and the second label switched path by the Path state information block creating module 640.
  • the sending module 630 is further configured to: after the receiving module receives the first Path message from the second node and used for creating the first label switched path, send, to a downstream node of the first label switched path, a Path message used for creating the first label switched path.
  • the network node 600 may further include: a Resv state information block creating module 660 and a second information block merging module 670.
  • the Resv state information block creating module 660 is configured to: when the receiving module 610 receives, from the downstream node of the first label switch path, a third Resv message corresponding to the first label switched path, create a Resv state information block for the first label switched path.
  • the sending module 630 is further configured to: after the receiving module 610 receives the second Path message from the second node and used for creating the second label switched path, send, to a downstream node of the second label switched path, a Path message for creating the second label switched path.
  • the Resv state information block creating module 660 is configured to: when the receiving module 610 receives, from the downstream node of the second label switch path, a fourth Resv message corresponding to the second label switched path, create a Resv state information block for the second label switched path.
  • the second information block merging module 670 is configured to merge the Resv state information blocks created for the first label switched path and the second label switched path by the Resv state information block creating module 660.
  • the network node 600 when the network node 600 is an intermediate node of the second label switched path, the network node 600 further includes: a determining module 680, configured to: after the receiving module 610 receives the second Path message from the second node and used for creating the second label switched path, determine whether a resource requirement of the second label switched path is not designated, and if the resource requirement of the second label switched path is not designated, skip sending the second Path message to a downstream node of the second label switched path.
  • a determining module 680 configured to: after the receiving module 610 receives the second Path message from the second node and used for creating the second label switched path, determine whether a resource requirement of the second label switched path is not designated, and if the resource requirement of the second label switched path is not designated, skip sending the second Path message to a downstream node of the second label switched path.
  • the network node 600 may further include: an advertising module 691 and/or a topology collecting module 692.
  • the advertising module 691 is configured to advertise a ring identifier corresponding to the network node or at least one interface of the network node.
  • the topology collecting module 692 is configured to collect network topology information, where the network topology information includes: a ring identifier that is advertised by at least another one node in a same ring network where the network node is located and is corresponding to the at least another one node or at least one interface of the at least another one node.
  • the network node 600 may merge Path messages and/or Resv messages corresponding to identical path segments and used for state refreshing, and then send the messages (for example, the network node 600 may merge Path messages and/or Resv messages corresponding to the first LSP and the second LSP and used for state refreshing, and then send the messages).
  • the sending module 630 may be further configured to generate, based on the merged Path state information block, a Path message (where the Path message may carry description information of source nodes (multiple) and a destination node (one) of all the LSPs with identical path segments merged, and is used for refreshing the state of the merged LSPs) used for state refreshing and send the Path message to a downstream node.
  • the sending module 630 may be further configured to generate, based on the merged Resv state information block, a Resv message (where the Resv message may carry description information of source nodes (multiple) and a destination node (one) of all the LSPs with identical path segments merged, and is used for refreshing the state of the merged LSPs) used for state refreshing, and send the Resv message to an upstream node.
  • a Resv message (where the Resv message may carry description information of source nodes (multiple) and a destination node (one) of all the LSPs with identical path segments merged, and is used for refreshing the state of the merged LSPs) used for state refreshing, and send the Resv message to an upstream node.
  • the number of messages exchanged between all the nodes along the LSPs can be greatly reduced.
  • all the nodes passed through by the LSPs may also merge the Path/Resv state information blocks only and still send Path/Resv messages used for state refreshing to each LSP separately.
  • the network node 600 in this embodiment may be a node in the ring network in the foregoing method embodiments.
  • the network node 600 may be, for example, the first node in the method embodiments, or may be the node B in the method embodiments, or may be a node combining capabilities of all the nodes in the method embodiments, where the functions of all the functional modules can be specifically implemented according to the method in the method embodiments.
  • the specific implementation process reference may be made to the related description in the method embodiments, and details are not repeatedly described herein.
  • An embodiment of the present invention further provides a communications system, including: a second node and a network node 600, where the second node and the network node 600 are connected in a communicable manner.
  • a first node receives a first Path message used for creating a first label switched path from a second node; allocates a first label to the first label switched path; sends a first Resv message carrying the first label to the second node; and when the first node receives a second Path message used for creating a second label switched path from the second node and determines that a destination node of the second label switched path is the same as that of the first label switched path, and the first node, the second node, and the destination node are located in a same ring network, allocates the first label to the second label switched path; and sends, to the second node, a second Resv message carrying the first label allocated to the second label switched path.
  • a node in a ring network allocates a same path label to identical path segments of LSPs passing through the node and having a same destination node, so as to merge identical path segments of LSPs having a same destination node on the ring network, which helps greatly reduce the number of LSPs to be created and maintained by each node on the ring network, and further reduces the LSP control overhead.
  • a node in the ring network merges Path state information blocks and Resv state information blocks created for identical path segments of LSPs passing through the node and having a same destination node, thereby facilitating a drop in the number of state information blocks to be maintained, and reducing control complexity.
  • a node on an LSP may send a Path/Resv message used for state refreshing based on a merged Path/Resv state information block. That is to say, the periodical state information refreshing after an LSP is created may be performed for merged LSPs other than for each independent LSP, which helps greatly reduce the number of Path/Resv messages exchanged between nodes on the LSPs.
  • the program may be stored in a computer readable storage medium.
  • the storage medium may include: a read-only memory, a random access memory, a magnetic disk, or an optical disc.

Landscapes

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

Claims (14)

  1. Verfahren zum Erzeugen eines etikettenvermittelten Pfades in einem Ringnetz, umfassend:
    Empfangen (301) einer ersten Path-Nachricht, die zum Erzeugen eines ersten etikettenvermittelten Pfades verwendet wird, von einem zweiten Knoten durch einen ersten Knoten,
    Zuweisen (302) eines ersten Etiketts zu dem ersten etikettenvermittelten Pfad durch den ersten Knoten,
    Senden (303) einer ersten Resv-Nachricht, die das erste Etikett mitführt, an den zweiten Knoten durch den ersten Knoten und
    wenn der erste Knoten eine zweite Path-Nachricht empfängt, die verwendet wird, um einen zweiten etikettenvermittelten Pfad von dem zweiten Knoten zu erzeugen, und bestimmt, dass ein Zielknoten des zweiten etikettenvermittelten Pfades gleich dem des ersten etikettenvermittelten Pfades ist, und sich der erste Knoten, der zweite Knoten und der Zielknoten in einem gleichen Ringnetz befinden, Zuweisen (304) des ersten Etiketts zu dem zweiten etikettenvermittelten Pfad durch den ersten Knoten und Senden einer zweiten Resv-Nachricht, die das erste Etikett mitführt, das dem zweiten etikettenvermittelten Pfad zugewiesen ist, an den zweiten Knoten.
  2. Verfahren nach Anspruch 1, wobei
    die erste Path-Nachricht eine Ringkennung eines Ringnetzes mitführt, in dem sich ein Quellknoten befindet, der dem ersten etikettenvermittelten Pfad entspricht, die zweite Path-Nachricht eine Ringkennung des Ringnetzes mitführt, in dem sich ein Quellknoten befindet, der dem zweiten etikettenvermittelten Pfad entspricht, und die Ringkennung des Ringnetzes, in dem sich der Quellknoten befindet, der dem ersten etikettenvermittelten Pfad entspricht, gleich der Ringkennung des Ringnetzes ist, in dem sich der Quellknoten befindet, der dem zweiten etikettenvermittelten Pfad entspricht.
  3. Verfahren nach Anspruch 1, wobei:
    das Verfahren nach dem Empfangen einer Path-Nachricht, die zum Erzeugen eines ersten etikettenvermittelten Pfades verwendet wird, von einem zweiten Knoten durch einen ersten Knoten ferner umfasst: Erzeugen eines Path-Zustandsinformationsblocks für den ersten etikettenvermittelten Pfad durch den ersten Knoten und
    das Verfahren nach dem Empfangen einer zweiten Path-Nachricht, die zum Erzeugen eines zweiten etikettenvermittelten Pfades verwendet wird, von dem zweiten Knoten durch den ersten Knoten ferner umfasst: Erzeugen eines Path-Zustandsinformationsblocks für den zweiten etikettenvermittelten Pfad durch den ersten Knoten und Verschmelzen der Path-Zustandsinformationsblöcke, die für den ersten etikettenvermittelten Pfad und den zweiten etikettenvermittelten Pfad erzeugt wurden.
  4. Verfahren nach Anspruch 3, ferner umfassend:
    Erzeugen einer Path-Nachricht, die zum Aktualisieren des Pfadzustandes verwendet wird, gemäß den verschmolzenen Path-Zustandsinformationsblöcken durch den ersten Knoten und Senden der Path-Nachricht.
  5. Verfahren nach einem der Ansprüche 1 bis 4, wobei
    das Verfahren nach dem Empfangen einer ersten Path-Nachricht, die zum Erzeugen eines ersten etikettenvermittelten Pfades verwendet wird, von einem zweiten Knoten durch einen ersten Knoten ferner umfasst: Senden einer Path-Nachricht, die zum Erzeugen des ersten etikettenvermittelten Pfades verwendet wird, durch den ersten Knoten an einen prozessabwärtigen Knoten des ersten etikettenvermittelten Pfades und, wenn der erste Knoten von dem prozessabwärtigen Knoten des ersten etikettenvermittelten Pfades eine dritte Resv-Nachricht empfängt, die dem ersten etikettenvermittelten Pfad entspricht, Erzeugen eines Resv-Zustandsinformationsblocks für den ersten etikettenvermittelten Pfad durch den ersten Knoten und
    das Verfahren nach dem Empfangen einer zweiten Path-Nachricht, die zum Erzeugen eines zweiten etikettenvermittelten Pfades verwendet wird, von dem zweiten Knoten durch den ersten Knoten ferner umfasst: Senden einer Path-Nachricht, die zum Erzeugen des zweiten etikettenvermittelten Pfades verwendet wird, durch den ersten Knoten an einen prozessabwärtigen Knoten des zweiten etikettenvermittelten Pfades und, wenn der erste Knoten von dem prozessabwärtigen Knoten des zweiten etikettenvermittelten Pfades eine vierte Resv-Nachricht empfängt, die dem zweiten etikettenvermittelten Pfad entspricht, Erzeugen eines Resv-Zustandsinformationsblocks für den zweiten etikettenvermittelten Pfad durch den ersten Knoten und Verschmelzen der Resv-Zustandsinformationsblöcke, die für den ersten etikettenvermittelten Pfad und den zweiten etikettenvermittelten Pfad erzeugt wurden.
  6. Verfahren nach Anspruch 5, ferner umfassend:
    Erzeugen einer Resv-Nachricht, die zum Aktualisieren des Pfadzustandes verwendet wird, gemäß den verschmolzenen Path-Zustandsinformationsblöcken durch den ersten Knoten und Senden der Path-Nachricht.
  7. Verfahren nach einem der Ansprüche 1 bis 4, wobei
    wenn der erste Knoten ein Zwischenknoten des zweiten etikettenvermittelten Pfades ist,
    das Verfahren nach dem Empfangen einer zweiten Path-Nachricht, die zum Erzeugen eines zweiten etikettenvermittelten Pfades verwendet wird, von dem zweiten Knoten durch den ersten Knoten ferner umfasst:
    Bestimmen, ob keine Ressourcenanforderung des zweiten etikettenvermittelten Pfades ausgewiesen ist, durch den ersten Knoten und wenn keine Ressourcenanforderung des zweiten etikettenvermittelten Pfades ausgewiesen ist, Überspringen des Sendens der zweiten Path-Nachricht an einen prozessabwärtigen Knoten des zweiten etikettenvermittelten Pfades durch den ersten Knoten.
  8. Verfahren nach einem der Ansprüche 1 bis 4, umfassend:
    Bekanntgeben einer Ringkennung, die dem ersten Knoten oder mindestens einer Schnittstelle des ersten Knotens entspricht, durch den ersten Knoten und/oder
    Erfassen von Netztopologieinformationen durch den ersten Knoten,
    wobei die Netztopologieinformationen umfassen: eine Ringkennung, die durch mindestens einen anderen Knoten in einem gleichen Ringnetz bekanntgegeben wird, in dem sich der erste Knoten befindet, und die dem mindestens einen anderen Knoten oder mindestens einer Schnittstelle des mindestens einen anderen Knotens entspricht.
  9. Netzknoten (600), umfassend:
    ein Empfangsmodul (610), das dafür konfiguriert ist, eine erste Path-Nachricht, die zum Erzeugen eines ersten etikettenvermittelten Pfades verwendet wird, von einem zweiten Knoten zu empfangen,
    ein Etikettenzuweisungsmodul (620), das dafür konfiguriert ist, dem ersten etikettenvermittelten Pfad ein erstes Etikett zuzuweisen, und
    ein Sendemodul (630), das dafür konfiguriert ist, eine erste Resv-Nachricht, die das erste Etikett mitführt, an den zweiten Knoten zu senden, wobei das Etikettenzuweisungsmodul (620) ferner für Folgendes konfiguriert ist: wenn das Empfangsmodul (610) eine zweite Path-Nachricht empfängt, die verwendet wird, um einen zweiten etikettenvermittelten Pfad von dem zweiten Knoten zu erzeugen, und bestimmt, dass ein Zielknoten des zweiten etikettenvermittelten Pfades gleich dem des ersten etikettenvermittelten Pfades ist, und sich der Netzknoten, der zweite Knoten und der Zielknoten in einem gleichen Ringnetz befinden, das erste Etikett dem zweiten etikettenvermittelten Pfad zuzuweisen und
    das Sendemodul (630) ferner dafür konfiguriert ist, eine zweite Resv-Nachricht, die das erste Etikett mitführt, das dem zweiten etikettenvermittelten Pfad durch das Etikettenzuweisungsmodul (620) zugewiesen wird, an den zweiten Knoten zu senden.
  10. Netzknoten nach Anspruch 9, wobei
    der Netzknoten ferner umfasst:
    ein Path-Zustandsinformationsblock-Erzeugungsmodul, das für Folgendes konfiguriert ist: nach dem Empfangen der ersten Path-Nachricht, die zum Erzeugen des ersten etikettenvermittelten Pfades verwendet wird, von dem zweiten Knoten durch das Empfangsmodul (610) einen Path-Zustandsinformationsblocks für den ersten etikettenvermittelten Pfad zu erzeugen und nach dem Empfangen der zweiten Path-Nachricht, die zum Erzeugen des zweiten etikettenvermittelten Pfades verwendet wird, von dem zweiten Knoten durch das Empfangsmodul einen Path-Zustandsinformationsblock für den zweiten etikettenvermittelten Pfad zu erzeugen und
    ein erstes Informationsblock-Verschmelzungsmodul, das dafür konfiguriert ist, die Path-Zustandsinformationsblöcke, die für den ersten etikettenvermittelten Pfad und den zweiten etikettenvermittelten Pfad durch das Path-Zustandsinformationsblock-Erzeugungsmodul erzeugt wurden, zu verschmelzen.
  11. Netzknoten nach Anspruch 9, wobei
    das Sendemodul (630) ferner für Folgendes konfiguriert ist: nach dem Empfangen der ersten Path-Nachricht, die zum Erzeugen des ersten etikettenvermittelten Pfades verwendet wird, von dem zweiten Knoten durch das Empfangsmodul (610), eine Path-Nachricht zum Erzeugen des ersten etikettenvermittelten Pfades an einen prozessabwärtigen Knoten des ersten etikettenvermittelten Pfades zu senden, wobei der Netzknoten ferner umfasst:
    ein Resv-Zustandsinformationsblock-Erzeugungsmodul, das für Folgendes konfiguriert ist: wenn das Empfangsmodul (610) von dem prozessabwärtigen Knoten des ersten etikettenvermittelten Pfades eine dritte Resv-Nachricht empfängt, die dem ersten etikettenvermittelten Pfad entspricht, einen Resv-Zustandsinformationsblock für den ersten etikettenvermittelten Pfad zu erzeugen,
    das Sendemodul (630) ferner für Folgendes konfiguriert ist: nach dem Empfangen der zweiten Path-Nachricht, die zum Erzeugen des zweiten etikettenvermittelten Pfades verwendet wird, von dem zweiten Knoten durch das Empfangsmodul eine Path-Nachricht zum Erzeugen des zweiten etikettenvermittelten Pfades an einen prozessabwärtigen Knoten des zweiten etikettenvermittelten Pfades zu senden,
    das Resv-Zustandsinformationsblock-Erzeugungsmodul ferner für Folgendes konfiguriert ist: wenn das Empfangsmodul (610) von dem prozessabwärtigen Knoten des zweiten etikettenvermittelten Pfades eine vierte Resv-Nachricht empfängt, die dem zweiten etikettenvermittelten Pfad entspricht, einen Resv-Zustandsinformationsblock für den zweiten etikettenvermittelten Pfad zu erzeugen, und
    der Netzknoten ferner umfasst:
    ein zweites Informationsblock-Verschmelzungsmodul, das dafür konfiguriert ist, die Resv-Zustandsinformationsblöcke zu verschmelzen, die durch das Resv-Zustandsinformationsblock-Erzeugungsmodul für den ersten etikettenvermittelten Pfad und den zweiten etikettenvermittelten Pfad erzeugt wurden.
  12. Netzknoten nach Anspruch 9 oder 10 wobei
    wenn der Netzknoten ein Zwischenknoten des zweiten etikettenvermittelten Pfades ist,
    der Netzknoten ferner umfasst:
    ein Bestimmungsmodul, das für Folgendes konfiguriert ist: nach dem Empfangen der zweiten Path-Nachricht, die zum Erzeugen des zweiten etikettenvermittelten Pfades verwendet wird, von dem zweiten Knoten durch das Empfangsmodul (610) zu bestimmen, ob keine Ressourcenanforderung des zweiten etikettenvermittelten Pfades ausgewiesen ist, und wenn keine Ressourcenanforderung des zweiten etikettenvermittelten Pfades ausgewiesen ist, das Senden der zweiten Path-Nachricht an einen prozessabwärtigen Knoten des zweiten etikettenvermittelten Pfades zu überspringen.
  13. Netzknoten nach Anspruch 9 oder 10, wobei
    der Netzknoten ferner umfasst:
    ein Bekanntgabemodul, das dafür konfiguriert ist, eine Ringkennung bekanntzugeben, die dem Netzknoten oder mindestens einer Schnittstelle des Netzknotens entspricht,
    und/oder
    ein Topologieerfassungsmodul, das dafür konfiguriert ist, Netztopologieinformationen zu erfassen, wobei die Netztopologieinformationen umfassen: eine Ringkennung, die durch mindestens einen anderen Knoten in einem gleichen Ringnetz bekanntgegeben wird, in dem sich der Netzknoten befindet und das dem mindesten einen anderen Knoten oder mindestens einer Schnittstelle des mindestens einen anderen Knotens entspricht.
  14. Kommunikationssystem, umfassend:
    den Netzknoten nach einem der Ansprüche 9 bis 13.
EP13738884.9A 2012-01-17 2013-01-05 Verfahren zur erstellung eines ringnetzwerketikettschaltwegs, zugehörige vorrichtung und kommunikationssystem Active EP2797259B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210013863.3A CN103209088B (zh) 2012-01-17 2012-01-17 环网标签交换路径创建方法及相关设备和通信系统
PCT/CN2013/070058 WO2013107298A1 (zh) 2012-01-17 2013-01-05 环网标签交换路径创建方法及相关设备和通信系统

Publications (3)

Publication Number Publication Date
EP2797259A1 EP2797259A1 (de) 2014-10-29
EP2797259A4 EP2797259A4 (de) 2014-12-31
EP2797259B1 true EP2797259B1 (de) 2021-04-07

Family

ID=48756180

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13738884.9A Active EP2797259B1 (de) 2012-01-17 2013-01-05 Verfahren zur erstellung eines ringnetzwerketikettschaltwegs, zugehörige vorrichtung und kommunikationssystem

Country Status (6)

Country Link
US (1) US9350620B2 (de)
EP (1) EP2797259B1 (de)
JP (1) JP5759637B2 (de)
KR (1) KR101605052B1 (de)
CN (1) CN103209088B (de)
WO (1) WO2013107298A1 (de)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106982161B (zh) * 2012-11-22 2020-07-24 华为技术有限公司 环网保护中标签保持和删除的方法及设备
US9438473B2 (en) * 2014-06-30 2016-09-06 Juniper Networks, Inc. Auto-discovery and convergent multi-protocol label switching rings
US10218611B2 (en) 2014-06-30 2019-02-26 Juniper Networks, Inc. Label distribution protocol (LDP) signaled multi-protocol label switching rings
US9729455B2 (en) 2014-06-30 2017-08-08 Juniper Networks, Inc. Multi-protocol label switching rings
US9692693B2 (en) 2014-06-30 2017-06-27 Juniper Networks, Inc. Bandwidth control for ring-based multi-protocol label switched paths
US9313663B2 (en) * 2014-08-21 2016-04-12 Futurewei Technologies, Inc. Automatic division of internet protocol radio access networks to interior gateway protocol areas
CN105991434B (zh) * 2015-02-05 2019-12-06 华为技术有限公司 一种环网中mpls报文转发的方法及网络节点
US9843508B2 (en) 2015-03-06 2017-12-12 Juniper Networks, Inc. RSVP make-before-break label reuse
CN106330701B (zh) * 2015-07-01 2020-09-25 深圳市中兴通讯技术服务有限责任公司 环形组网的快速重路由方法及装置
CN107634869B (zh) * 2016-07-18 2022-07-15 中兴通讯股份有限公司 一种Hello消息处理方法及装置
CN108345621B (zh) * 2017-01-24 2022-03-08 腾讯科技（深圳）有限公司 一种数据对账方法、系统及数据系统
US10341228B1 (en) * 2017-03-29 2019-07-02 Juniper Networks, Inc. RSVP make-before-break label reuse
CN109428865B (zh) * 2017-08-30 2021-12-07 中兴通讯股份有限公司 一种切换标签交换路径更新权限的方法及相关设备
US11233748B1 (en) 2018-08-30 2022-01-25 Juniper Networks, Inc. Bandwidth management for resource reservation label switched path of a ring network
CN115866071A (zh) * 2023-02-28 2023-03-28 中信云网有限公司 初始设备属性信息的上报路径确定方法及装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7298700B1 (en) * 2001-05-24 2007-11-20 At&T Corp. Method for unidirectional and bidirectional label switched path setup in a label switched network
JP4522955B2 (ja) * 2006-02-09 2010-08-11 日本電信電話株式会社 マルチキャストポイントツーポイント（ｍｐ２ｐ）マルチプロトコルラベルスイッチング（ｍｐｌｓ）トラヒックエンジニアリング（ｔｅ）通信システム
US7742482B1 (en) * 2006-06-30 2010-06-22 Juniper Networks, Inc. Upstream label assignment for the resource reservation protocol with traffic engineering
CN1921453B (zh) * 2006-09-25 2011-06-01 杭州华三通信技术有限公司 Mpls有序方式下lsp中间节点标签分配方法及装置
CN101877892B (zh) * 2009-04-29 2012-11-07 华为技术有限公司 节点关联通道能力的协商方法及节点设备
CN101599862B (zh) * 2009-06-30 2011-09-21 中兴通讯股份有限公司 传送多协议标签交换环网保护维护实体组配置方法和装置
JP2011124897A (ja) * 2009-12-14 2011-06-23 Fujitsu Ltd ネットワーク管理装置および異常箇所特定方法
US20120008632A1 (en) * 2010-07-12 2012-01-12 Telefonaktiebolaget L M Ericsson Sharing Resource Reservations Among Different Sessions In RSVP-TE
CN102143043B (zh) * 2010-07-14 2014-11-05 华为技术有限公司 一种建立标签交换路径的方法和装置
CN102035714B (zh) * 2010-12-17 2016-03-30 中兴通讯股份有限公司 一种相交相切环网保护方法及系统
CN102158396B (zh) * 2011-02-15 2015-01-07 中兴通讯股份有限公司 一种节点分配标签的方法及装置
CN102201985B (zh) * 2011-05-06 2014-02-05 杭州华三通信技术有限公司 多协议标签交换传送技术环保护倒换方法及节点

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
JP2015504284A (ja) 2015-02-05
EP2797259A1 (de) 2014-10-29
CN103209088B (zh) 2016-12-28
JP5759637B2 (ja) 2015-08-05
CN103209088A (zh) 2013-07-17
EP2797259A4 (de) 2014-12-31
WO2013107298A1 (zh) 2013-07-25
US9350620B2 (en) 2016-05-24
KR20140116196A (ko) 2014-10-01
US20140348028A1 (en) 2014-11-27
KR101605052B1 (ko) 2016-03-21

Similar Documents

Publication Publication Date Title
EP2797259B1 (de) Verfahren zur erstellung eines ringnetzwerketikettschaltwegs, zugehörige vorrichtung und kommunikationssystem
US10250459B2 (en) Bandwidth on-demand services in multiple layer networks
US10432514B2 (en) Multiprotocol label switching traffic engineering tunnel establishing method and device
EP3751801B1 (de) Grenz-gateway-protokoll zur kommunikation zwischen softwaredefinierten netzwerksteuergeräten
US7602702B1 (en) Fast reroute of traffic associated with a point to multi-point network tunnel
US9954773B2 (en) Label switching path establishment method, data forwarding method, and device
CN101160914B (zh) 一种基于多协议标签交换流量工程隧道的数据报文传输系统
US9210037B2 (en) Method, apparatus and system for interconnected ring protection
JP5543596B2 (ja) マルチレイヤネットワークにおいてフォワーディング隣接のプロパティの継承方法及び相応のマルチレイヤネットワーク
JP4509885B2 (ja) シグナリング装置
US9246838B1 (en) Label switched path setup using fast reroute bypass tunnel
CN104429030A (zh) 用信号告知双向分组te隧道的合作路由和非合作路由lsp
WO2011157130A2 (zh) 路径建立方法和装置
CN102957614A (zh) 一种动态路由的实现方法和装置
CN102201970A (zh) 一种对关联双向lsp进行路由优化的方法及系统
JP6377738B2 (ja) Ｒｓｖｐ−ｔｅシグナリングを処理するための方法及びシステム
CN102136945A (zh) Lsp保护的建立方法和节点
Xia Research on signaling mechanism based on convergence network
CN109729006B (zh) 一种报文处理方法和装置、计算机可读存储介质
JP2006080682A (ja) ポイントツーマルチポイントＭＰＬＳ（Ｍｕｌｔｉ−ＰｒｏｔｏｃｏｌＬａｂｅｌＳｗｉｔｃｈｉｎｇ）通信方法及びシステム

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: 20140724

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

A4 Supplementary search report drawn up and despatched

Effective date: 20141201

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/723 20130101ALI20141125BHEP

Ipc: H04L 12/437 20060101ALI20141125BHEP

Ipc: H04L 12/24 20060101AFI20141125BHEP

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: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20190208

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20201103

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1381100

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210415

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602013076729

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20210407

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1381100

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210407

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

Ref country code: HR

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: 20210407

Ref country code: BG

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: 20210707

Ref country code: AT

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: 20210407

Ref country code: LT

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: 20210407

Ref country code: NL

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: 20210407

Ref country code: FI

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: 20210407

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602013076729

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012240000

Ipc: H04L0041000000

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

Ref country code: GR

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: 20210708

Ref country code: IS

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: 20210807

Ref country code: LV

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: 20210407

Ref country code: RS

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: 20210407

Ref country code: SE

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: 20210407

Ref country code: PT

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: 20210809

Ref country code: NO

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: 20210707

Ref country code: PL

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: 20210407

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: 20210407

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602013076729

Country of ref document: DE

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

Ref country code: DK

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: 20210407

Ref country code: CZ

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: 20210407

Ref country code: EE

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: 20210407

Ref country code: SK

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: 20210407

Ref country code: SM

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: 20210407

Ref country code: RO

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: 20210407

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: 20220110

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

Ref country code: IS

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: 20210807

Ref country code: AL

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: 20210407

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: 20210407

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

Ref country code: MC

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: 20210407

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20220131

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

Ref country code: LU

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

Effective date: 20220105

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

Ref country code: BE

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

Effective date: 20220131

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

Ref country code: LI

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

Effective date: 20220131

Ref country code: CH

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

Effective date: 20220131

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

Ref country code: IE

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

Effective date: 20220105

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

Ref country code: GB

Payment date: 20221201

Year of fee payment: 11

Ref country code: FR

Payment date: 20221208

Year of fee payment: 11

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

Ref country code: DE

Payment date: 20221130

Year of fee payment: 11

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

Ref country code: HU

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

Effective date: 20130105

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

Ref country code: MK

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: 20210407

Ref country code: CY

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: 20210407