WO2010031283A1 - 一种检测链路标签状态的方法、设备与系统 - Google Patents

一种检测链路标签状态的方法、设备与系统 Download PDF

Info

Publication number
WO2010031283A1
WO2010031283A1 PCT/CN2009/073083 CN2009073083W WO2010031283A1 WO 2010031283 A1 WO2010031283 A1 WO 2010031283A1 CN 2009073083 W CN2009073083 W CN 2009073083W WO 2010031283 A1 WO2010031283 A1 WO 2010031283A1
Authority
WO
WIPO (PCT)
Prior art keywords
status
label
link
information
lsps
Prior art date
Application number
PCT/CN2009/073083
Other languages
English (en)
French (fr)
Inventor
孙俊
陈俊逊
段瑞
岳华名
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2010031283A1 publication Critical patent/WO2010031283A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, device, and system for detecting a link label status. Background technique
  • the routing protocol and the link management protocol are used, so that the network has the functions of network control topology and automatic discovery of resource topology.
  • LSP can be implemented. (Automatic new creation of the Label Swi tch Path, label switching path) and automatic recovery of the fault re-routing.
  • the LMP (Link Management Protocol) protocol mainly establishes and maintains a series of link management such as control channels, data link connectivity check, and link consistency check for the local interface.
  • 0SPF-TE Open Shortest Path First
  • the protocol mainly floods the information after the link check is passed to the entire network.
  • the LSP is newly created and rerouted.
  • the LSP path is calculated on the ingress node based on the obtained network resource topology information based on the traffic engineering path algorithm, and then distributed on each network element node along the LSP path through the signaling protocol. Labels, reserve resources, and establish cross-connections, where the distribution label is done by the Link Resource Manager (LRM).
  • LRM Link Resource Manager
  • the NE In the process of deleting an LSP, the NE cannot be successfully deleted due to abnormal reset of the NE.
  • the corresponding crossover on some NE nodes (usually the upstream node) has been deleted, and the corresponding link label resources have been released.
  • the corresponding crossover on the node (usually the downstream node) remains, and the corresponding link label resource is still occupied.
  • the status of the corresponding link label between the abnormal reset network element node and its neighboring node (usually the upstream node) is likely to be inconsistent.
  • an LSP with the A node as the ingress node and the F node as the egress node passes through the 8, C, D, and E nodes.
  • the D node has been reset and restarted, and the corresponding cross on the A, B, and C nodes has been Delete, and 0, E, and F remain.
  • the link between C and D has the inconsistency of the label status at both ends.
  • the label status is inconsistent, the corresponding link label will be unavailable, which will result in a waste of link label resources.
  • it may even have a serious impact on the LSP establishment process:
  • an LSP establishes signaling it first goes to the idle end network element node. This link label may be allocated. When the signaling goes to the other occupied network element node, a crossover failure will occur, causing the current setup process to fail. Even if the LSP is successfully established by adopting the Crankback mechanism or other special processing, the total time is extended. If the LSP is established for rerouting recovery, the impact will be more serious.
  • the prior art uses the 0SPF-TE protocol to flood the link label status information of the entire network within the entire network. Each node uses this information to periodically connect all links with neighboring nodes. The status of the labels on both ends is compared. If the status of the labels on both ends is inconsistent, the upstream node of the link uses the special identifier to identify the label as occupied, so that the LSP can be evaded when the label is allocated. If it is idle, the label status of the other end of the special identifier is changed to idle, so that the LSP can be reused when it is established.
  • each node in the networking needs to flood all the link label status information of the local node through the 0SPF-TE protocol, which greatly increases the amount of communication data.
  • the 0SPF-TE protocol flooding refresh may be untimely. In order to avoid false check, it is necessary to check multiple times to confirm, which results in untimely detection. Summary of the invention
  • the embodiment of the present invention provides a method for detecting the status of a link label, and compares the label status information of the two ends by using the extended LinkSum mary message, so that the label status of both ends of the link can be detected in time with a small amount of traffic. .
  • An embodiment of the present invention provides a method for detecting a link label status, which includes the following steps:
  • the LinkSu ⁇ ary message includes link label status information.
  • the status of the outgoing label information of all LSPs on the remote link and the status of the incoming label information are obtained, and the local link is The status of the outgoing label information of all LSPs is compared with the status of the incoming label information. The result is whether the status of the link labels at both ends is consistent.
  • an embodiment of the present invention further provides a node device, including:
  • a label status module configured to collect link label status information on the local link, and send the status information to the sending module and the comparing module;
  • a sending module configured to add link label status information on the local link to a LinkSu mmary message to send out;
  • a comparison module configured to receive a LinkSummary message sent by the remote link, and obtain link tag status information according to the L inkSummary message, compare link link status information sent by the remote link, and the local link The link label status information on the upper link, and the comparison result is sent to the result module;
  • a result module configured to send the comparison result.
  • an embodiment of the present invention further provides a system for detecting a link label status, including:
  • the first node is configured to collect link label status information on the local link, and add the information to the LinkSummary message to send the information.
  • a second node configured to receive the LinkSummary message, and according to the LinkSummary The message obtains the link label status information, and compares with the corresponding outgoing label status and the incoming label status on the local end link, and obtains and sends the comparison result.
  • FIG. 1 is a schematic diagram showing the state inconsistency of the labels at both ends in the prior art
  • FIG. 2 is a schematic flowchart of a method for detecting a link label state according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for detecting a link label status according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a LinkSummary message according to an embodiment of the present invention. Schematic diagram of the frame structure;
  • FIG. 5 is a schematic structural diagram of a node device according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a system for detecting a link label status according to an embodiment of the present invention. detailed description
  • FIG. 2 The specific method flow of the embodiment of the present invention is as shown in FIG. 2, and includes the following steps:
  • Step S201 Receive a LinkSummary message, where the LinkSummary message includes link label status information.
  • the LinkSummary message includes a status of the outbound label information of all LSPs on the remote link and a status of the inbound label information.
  • Step S202 obtaining, according to the LinkSummary message, all the LSPs on the remote link.
  • the status of the label information and the status of the incoming label information are compared with the status of the outgoing label information of all LSPs on the local link and the status of the incoming label information.
  • Step S203 A result of whether the link label states at both ends are consistent.
  • the B node is a peer node of the A node, and includes the following steps:
  • Step S301 The A node collects the inbound and outbound label information of all the LSPs that occupy the state at the local end of the link, puts the information into the LinkSummary message, and sends the LinkSummary message to the link peer node.
  • the Data-Link object in the LinkSummary message is extended by sub-objects.
  • the extended sub-object Label_ Status specifically includes:
  • Type frame The type used to represent the content of the child object.
  • Length frame Record the length of the byte occupied by this sub-object. The length must be a multiple of 4.
  • Status frame Indicates the status of the tag. 0x0000 indicates that the tag is idle; 0x0001 indicates that the tag is occupied.
  • Direction frame identifies the direction of the label, 0x0000 indicates that the direction is the inbound label; 0x0001 indicates that the direction is the outgoing label.
  • Label ID frame Records all tag IDs with the same status and direction, each tag ID occupies 4 bytes.
  • the LinkSummary message defined in the existing LMP protocol standard is used to perform TE link attributes. Consistency check function, TE link attribute consistency check The main check content is now: Check the ID (Link-Id) type of both ends of the TE link and the interface (Interface_Id) identifier of both ends of the data link. Types of.
  • Link-Id the ID of both ends of the TE link
  • Interface_Id the interface identifier of both ends of the data link. Types of.
  • the A node has three LSPs, and the labels are L1, L2, and L3.
  • the inbound label status of L1 is occupied, and the outgoing label status is idle.
  • the outgoing and incoming label status of L2 are occupied.
  • L3 outgoing and incoming labels The status is all idle.
  • the ijA node collects the outgoing and incoming label information of all the LSPs that occupy the state. It is found that the inbound label status of L1 and the outgoing and incoming label status of L2 are occupied. Then, according to the direction of outgoing and incoming labels, L1
  • the inbound and inbound labels of the inbound label and L2 are respectively placed in the two sub-objects Label-Status.
  • One of the Label-Status states is the occupied inbound label, and its Label_ID is L1, L2; the other Label-Status is placed in the occupied outgoing label, and its Label_ID is L2.
  • the LinkSummary message containing the tag status information is sent to the peer B node, and the A node may also periodically send the LinkSummary message containing the tag status information to the peer B node.
  • Step S302 The B node obtains the information of the outgoing and incoming labels at the A node according to the received LinkSummary message, and compares with all the outgoing and incoming label information on the local link.
  • the status of the remote label information that the B node does not receive by default is idle.
  • Step S303 If the status of the label corresponding to the two ends of the link is inconsistent, take corresponding measures: report the alarm as described above, clear the status of the remaining label, and so on.
  • Step S304 If the labels of the corresponding two ends of the link are in the same state, no processing is performed.
  • the A node may also collect only the inbound and outbound label information of all the LSPs whose status is idle on the local link, and the status of the remote label information that the B node will not receive by default.
  • the node A can also collect the outgoing and incoming label information of all the LSPs on the local link and send them to the Node B.
  • the technical solution of the embodiment of the present invention increases the link label status consistency check function by extending the LinkSummary message, so that the link can be timely and with a small amount of traffic. Check the label status of the end;
  • a node device includes a label status module, a comparison module, a sending module, and a result module:
  • a label status module configured to collect link label status information on the local link, and send the status information to the sending module and the comparing module;
  • a sending module configured to add the link label status information on the local link to the LinkSummary message and send the information
  • a comparison module configured to receive a LinkSummary message sent by the remote link, according to the
  • the LinkSummary message obtains the link label status information, compares the link label status information sent by the remote link, and the link label status information on the local link, and sends the comparison result to the result module.
  • a result module configured to send the comparison result.
  • the link label status information includes the outbound and inbound label information of all the LSPs that are occupied, or the outbound and inbound label information of all LSPs that are idle, or the status of the outgoing and incoming labels of all LSPs.
  • the status of the link label received by the comparison module is the outbound and inbound label information of all the LSPs that are occupied, the status of the outbound label information and the inbound label information of the LSP on the link that are not received by default are both Being idle;
  • the status of the link label received by the comparison module is the outbound and inbound label information of all the LSPs that are in the idle state, the status of the outbound label information and the inbound label information of the LSP that are not received by default are occupied. .
  • a third embodiment of the present invention includes: a first node, configured to collect link label status information on the local link, and add the information to the Li Sent out in the nkSu ⁇ ary message;
  • the second node is configured to receive the LinkSummary message, obtain the link label status information according to the LinkSummary message, and compare the corresponding label status and the inbound label status on the link of the local end, and obtain and send a comparison. result.
  • the link label status information includes the outbound and inbound label information of all the LSPs that are occupied, or the outbound and inbound label information of all LSPs that are idle, or the status of the outgoing and incoming labels of all LSPs.
  • the status of the outbound label information and the inbound label information of the LSP on the link that is not received by default when the status of the link label received by the second node is the outbound and inbound label information of the LSP. All are idle;
  • the link label status information received by the second node is the outbound and inbound label information of all the LSPs that are in the idle state
  • the status of the outbound label information and the inbound label information of the LSP that are not received by default are both Occupied.
  • the first node periodically sends the information.
  • the technical solution of the embodiment of the present invention has the following advantages: By extending the LinkSummary message, the link label status consistency check function is added, so that the label status of both ends of the link can be detected in time with a small amount of traffic. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

一种检测链路标签状态的方法、 设备与系统
本申请要求 2008年 9月 22日提交中国专利局、申请号为 200810216304. 6、 发明名称为 "一种检测链路标签状态的方法、 设备与系统" 的中国专利申请 的优先权, 其全部内容通过引用结合在本申请中。
技术领域 本发明实施例涉及通信领域, 尤其涉及一种检测链路标签状态的方法、 设备与系统。 背景技术
在 MPLS (Mul ti Protocol Label Swi tch , 多协议标签交换) 网络中使 用了路由协议和链路管理协议, 就使网络具有了网络控制拓扑和资源拓扑 自动发现的功能, 在此基础上可实现 LSP ( Label Swi tch Path, 标签交换 路径) 的自动新建和故障时重路由自动恢复。
LMP ( Link Management Protocol , 链路管理协议) 协议主要对本地接 口进行建立和维护相应的控制通道、 数据链路连通性校验和链路一致性校 验等一系列链路管理。 0SPF-TE ( Open Shortest Path First , 开放式最短 路径优先) 协议主要将链路校验通过后的信息洪泛到整个网络上。
LSP的新建和重路由恢复都是首先在入口节点上根据已获得的网络资 源拓扑信息采用基于流量工程的路径算法计算好 LSP路径,然后通过信令协 议沿着 LSP路径在各网元节点上分配标签、预留资源并建立交叉连接,其中 分配标签由本地链路资源管理器 (Link Resource Manager , LRM ) 完成。
正常情况下相临网元之间链路的标签状态应保持一致, 但在如下异常 情形下, 就会出现不一致的情况:
在删除某 LSP过程中由于某网元节点异常复位等原因不能成功删除,造 成一些网元节点 (通常是上游节点) 上相应交叉已被删除, 相应链路标签 资源已被释放; 但一些网元节点(通常是下游节点)上相应交叉仍然残留, 相应链路标签资源仍被占用。 在异常复位网元节点与其相邻的节点 (通常 是上游节点) 之间相应链路标签状态就很有可能会不一致。 如下图 1所示, 一条以 A节点为入口节点、 F节点为出口节点的 LSP中间经过8、 C、 D和 E节点, 其中 D节点曾复位重启, A、 B、 C节点上相应交叉已被删除, 而0、 E、 F仍残 留, C和 D之间链路即存在两端标签状态不一致情况。
标签状态不一致首先会造成相应链路标签不可用, 导致链路标签资源 浪费; 其次甚至有可能会对 LSP的建立过程造成严重影响: 当某 LSP建立信 令先走到空闲一端网元节点时有可能会分配使用此链路标签, 当信令走到 另外被占用一端网元节点时将发生建立交叉失败, 从而造成当前建立过程 失败。 即使通过采取 Crankback机制或其它特殊处理重新建立 LSP成功, 但 延长了总时间, 如果建立 LSP是为了重路由恢复, 则影响会更严重。
为了解决上述标签状态一致的问题,现有技术利用 0SPF-TE协议在整个 网络内部洪泛整个组网的链路标签状态信息, 每个节点利用此信息定期对 其与相邻节点相连所有链路两端标签状态进行比较, 如发现有两端标签状 态不一致, 则在链路的上游节点用特殊标识把标签标识为占用, 以便 LSP 建立分配标签时规避之; 如发现原被占用的一端已变为空闲, 则将特殊标 识的另一端的标签状态修改为空闲, 以便 LSP建立时能对其重新加以利用。
但该方法需要组网中各节点将本节点所有链路标签状态信息通过 0SPF-TE协议洪泛, 极大地增加了通信数据量; 同时由于 0SPF-TE协议洪 泛刷新可能会存在不及时的问题, 为避免误校验, 需要连续多次校验加以 确认, 从而导致检测处理不及时。 发明内容
本发明实施例提供一种检测链路标签状态的方法, 通过扩展后的 LinkSum mary消息, 比较两端的标签状态信息, 从而可以以较小的通信量, 及时地对 链路两端的标签状态进行检测。
本发明实施例一方面提出一种检测链路标签状态的方法, 包括以下步 骤:
接收 LinkSummary消息,所述 LinkSu匪 ary消息包括链路标签状态信息; 根据所述 LinkSummary消息, 得到远端链路上所有 LSP的出标签信息的 状态和入标签信息的状态,并与本端链路上所有 LSP的出标签信息的状态和 入标签信息的状态进行相应地比较; 得到两端链路标签状态是否一致的结 果。
另一方面, 本发明实施例还提供了一种节点设备, 包括:
标签状态模块, 用于收集本端链路上的链路标签状态信息, 并发送到 所述发送模块和所述比较模块;
发送模块, 用于把所述本端链路上的链路标签状态信息添加到 LinkSu mmary消息中发送出去;
比较模块, 用于接收远端链路发送的 LinkSummary消息, 并根据所述 L inkSummary消息得到链路标签状态信息, 比较所述远端链路发送的链路标 签状态信息和所述本端链路上的链路标签状态信息, 将比较结果发送至所 述结果模块;
结果模块, 用于将所述比较结果发送出去。
另一方面, 本发明实施例还提供了一种检测链路标签状态的系统, 包 括:
第一节点, 用于收集本端链路上的链路标签状态信息, 并将该信息添 加到 LinkSummary消息中发送出去;
第二节点, 用于接收所述 LinkSummary消息, 并根据所述 LinkSummary 消息得到所述链路标签状态信息, 并与本端的链路上相应的出标签状态和 入标签状态进行比较, 得到并发送比较结果。
本发明实施例的技术方案, 通过对 LinkSummary消息进行扩展, 增加了 链路标签状态一致性校验功能, 从而可以以较小的通信量, 及时地对链路两 端的标签状态进行检测。 附图说明
此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部 分, 并不构成对本发明的限定。 在附图中:
图 1为现有技术中两端标签状态不一致示意图;
图 2为本发明实施例一种检测链路标签状态的方法的流程示意图; 图 3为本发明实施例一种检测链路标签状态的方法的流程示意图; 图 4为本发明实施例 LinkSummary消息的帧结构示意图;
图 5为本发明实施例一种节点设备的结构示意图;
图 6为本发明实施例一种检测链路标签状态的系统结构示意图。 具体实施方式
为使本发明的目的、 技术方案和优点更加清楚明白, 下面结合实施方式 和附图, 对本发明做进一步详细说明。 在此, 本发明的示意性实施方式及其 说明用于解释本发明, 但并不作为对本发明的限定。
本发明实施例具体方法流程如图 2所示, 包括以下步骤:
步骤 S201 , 接收 LinkSummary消息, 所述 LinkSummary消息包括链路标 签状态信息。
具体地, 所述 LinkSummary消息包括远端链路上所有 LSP的出标签信息 的状态和入标签信息的状态。
步骤 S202 , 根据所述 LinkSummary消息, 得到远端链路上所有 LSP的出 标签信息的状态和入标签信息的状态,并与本端链路上所有 LSP的出标签信 息的状态和入标签信息的状态进行相应地比较。
步骤 S203 , 得到两端链路标签状态是否一致的结果。
本发明实施例的技术方案, 通过对 LinkSummary消息进行扩展, 增加了 链路标签状态一致性校验功能, 从而可以以较小的通信量, 及时地对链路两 端的标签状态进行检测。 为了更清楚地描述本发明实施例, 下面结合附图和实施例, 对本发明 的具体实施方式作进一步详细描述:
实施例一
如图 3所示, 为本发明实施例一, 一种检测链路标签状态的方法的流程示 意图, 其中 B节点为 A节点的对端节点, 包括以下步骤:
步骤 S301 , A节点在链路本端收集所有状态为占用的 LSP的出、 入标签信 息, 将这些信息放入 LinkSummary消息中, 并将 LinkSummary消息发送到链路 对端节点^
如图 4所示, 对 LinkSummary消息中的 Data— Link对象进行子对象的扩展。 扩展后的子对象 Label— Status具体包括:
Type帧: 用于表示子对象内容的类型。
Length帧: 记录这个子对象所占的字节长度, 长度必须为 4的倍数。
Status帧: 表示标签的状态, 0x0000表示这个标签是空闲的; 0x0001表 示这个标签是占用的。
Direction帧: 标识标签的方向, 0x0000 表示方向为入标签; 0x0001表 示方向为出标签。
Label ID帧: 记录所有标签状态和方向都相同的标签 ID, 每个标签 ID占 4 个字节。
在现有 LMP协议的标准中定义的 LinkSummary消息是用来进行 TE链路属性 一致性校验的功能, TE链路属性一致性校验现在主要的校验内容是: 校验 TE 链路两端的标识 (Link— Id)类型以及数据链路两端接口 (Interface— Id ) 标 识类型。 本发明实施例对 LinkSummary消息进行扩展后, 增加了链路标签状态 一致性校验功能, 具体如下:
假设 A节点有 3条 LSP, 其标签分别为 Ll, L2, L3 , 其中 L1的入标签状态为 占用, 出标签状态为空闲; L2的出、 入标签状态均为占用; L3的出、 入标签 状态均为空闲。 贝 ijA节点收集所有状态为占用的 LSP的出、 入标签信息, 发现 L1的入标签状态和 L2的出、 入标签状态均为占用, 然后根据出、 入两种不同 的标签方向, 将 L1的入标签和 L2的出、 入标签分别放入 2个子对象 Label— Status中。其中一个 Label— Status放状态为占用的入标签,其 Label— ID 是 Ll, L2; 另一个 Label— Status放状态为占用的出标签, 其 Label— ID是 L2。 将包含上述标签状态信息的 LinkSummary消息发送给对端 B节点, 其中 A节点也 可以周期性地将包含上述标签状态信息的 LinkSummary消息发送给对端 B节 点。
步骤 S302 , B节点根据接收到的 LinkSummary消息得到 A节点处的出、 入标 签信息, 与本端链路上所有的出、 入标签信息进行比较。
其中 B节点默认没有收到的远端标签信息的状态均为空闲。
步骤 S303, 如链路两端相对应的标签状态不一致, 采取相应的处理措施: 如上报告警, 清理释放残留的标签状态等。
步骤 S304, 如链路两端相对应的标签状态一致, 不做任何处理。
在上述步骤 S301和步骤 S302中, A节点也可以只收集本端链路上所有状态 为空闲的 LSP的出、 入标签信息, 此时 B节点将默认没有收到的远端标签信 息的状态均为占用; A节点也可以将本端链路上所有状态的 LSP的出、 入标签 信息收集起来一并发给 B节点。
本发明实施例的技术方案, 通过对 LinkSummary消息进行扩展, 增加了 链路标签状态一致性校验功能, 从而可以以较小的通信量, 及时地对链路两 端的标签状态进行检;
本发明实施例二, 一种节点设备, 结合图 5所示, 包括标签状态模块, 比较模块, 发送模块和结果模块:
标签状态模块, 用于收集本端链路上的链路标签状态信息, 并发送到 所述发送模块和所述比较模块;
发送模块, 用于把所述本端链路上的链路标签状态信息添加到 LinkSummary消息中发送出去;
比较模块, 用于接收远端链路发送的 LinkSummary消息, 并根据所述
LinkSummary消息得到链路标签状态信息,比较所述远端链路发送的链路标 签状态信息和所述本端链路上的链路标签状态信息, 将比较结果发送至所 述结果模块;
结果模块, 用于将所述比较结果发送出去。
其中,所述链路标签状态信息包括所有状态为占用的 LSP的出、入标签 信息, 或所有状态为空闲的 LSP的出、 入标签信息, 或所有 LSP的出、 入标 签信息状态。
其中, 当所述比较模块接收到的链路标签状态信息为所有状态为占用 的 LSP的出、 入标签信息时, 默认没有收到的链路上 LSP的出标签信息和入 标签信息的状态均为空闲;
当所述比较模块接收到的链路标签状态信息为所有状态为空闲的 LSP 的出、入标签信息时,默认没有收到的链路上 LSP的出标签信息和入标签信 息的状态均为占用。
本发明实施例的技术方案具有以下优点, 通过对 LinkSummary消息进行 扩展, 增加了链路标签状态一致性校验功能, 从而可以以较小的通信量, 及 时地对链路两端的标签状态进行检测。 本发明实施例三, 一种检测链路标签状态的系统, 如图 6所示, 包括: 第一节点, 用于收集本端链路上的链路标签状态信息, 并将该信息添 加到 Li nkSu匪 ary消息中发送出去;
第二节点, 用于接收所述 LinkSummary消息, 并根据所述 LinkSummary 消息得到所述链路标签状态信息, 并与本端的链路上相应的出标签状态和 入标签状态进行比较, 得到并发送比较结果。
其中,所述链路标签状态信息包括所有状态为占用的 LSP的出、入标签 信息, 或所有状态为空闲的 LSP的出、 入标签信息, 或所有 LSP的出、 入标 签信息状态。
其中, 当所述第二节点接收到的链路标签状态信息为所有状态为占用 的 LSP的出、 入标签信息时, 默认没有收到的链路上 LSP的出标签信息和入 标签信息的状态均为空闲;
当所述第二节点接收到的链路标签状态信息为所有状态为空闲的 LSP 的出、入标签信息时,默认没有收到的链路上 LSP的出标签信息和入标签信 息的状态均为占用。
其中, 所述第一节点周期性发送所述信息。
上述系统模块之间具体的信号处理、 执行过程等内容, 由于与本发明方 法实施例基于同一构想, 可参见本发明实施例一中的叙述, 此处不再赘述。
本发明实施例的技术方案具有以下优点, 通过对 LinkSummary 消息进 行扩展, 增加了链路标签状态一致性校验功能, 从而可以以较小的通信量, 及时地对链路两端的标签状态进行检测。
本领域普通技术人员可以理解: 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成, 前述的程序可以存储于一计算机可读 取存储介质中, 该程序在执行时, 执行包括上述方法实施例的步骤, 而前述 的存储介质包括: R0M、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。 以上所述的具体实施方式, 对本发明的目的、 技术方案和有益效果进行 了进一步详细说明, 所应理解的是, 以上所述仅为本发明的具体实施方式而 已, 并不用于限定本发明的保护范围, 凡在本发明的精神和原则之内, 所做 的任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。

Claims

权 利 要 求 书
1、 一种检测链路标签状态的方法, 其特征在于, 该方法包括: 接收 LinkSummary消息,所述 LinkSu匪 ary消息包括链路标签状态信息; 根据所述 LinkSummary消息, 得到远端链路上所有 LSP的出标签信息的 状态和入标签信息的状态,并与本端链路上所有 LSP的出标签信息的状态和 入标签信息的状态进行相应地比较; 得到两端链路标签状态是否一致的结 果。
2、 如权利要求 1所述一种检测链路标签状态的方法, 其特征在于, 所 述链路标签状态信息包括所有状态为占用的 LSP的出、入标签信息,或所有 状态为空闲的 LSP的出、 入标签信息, 或所有 LSP的出、 入标签信息状态。
3、 如权利要求 2所述一种检测链路标签状态的方法, 其特征在于, 所述 根据所述 LinkSummary消息, 得到远端链路上所有 LSP的出标签信息的状态 和入标签信息的状态具体为:
当所述链路标签状态信息包括所有状态为占用的 LSP的出、入标签信息 时,默认没有收到的远端链路上 LSP的出标签信息和入标签信息的状态均为 空闲;
当所述链路标签状态信息包括所有状态为空闲的 LSP的出、入标签信息 时,默认没有收到的远端链路上 LSP的出标签信息和入标签信息的状态均为 占用。
4、 如权利要求 1所述一种检测链路标签状态的方法, 其特征在于, 所述 接收 L i nkSummary消息具体为接收对端节点周期性发送的 L i nkSummary消 息。
5、 一种节点设备, 其特征在于, 包括标签状态模块, 比较模块, 发送 模块和结果模块:
标签状态模块, 用于收集本端链路上的链路标签状态信息, 并发送到 所述发送模块和所述比较模块;
发送模块, 用于把所述本端链路上的链路标签状态信息添加到 LinkSu mmary消息中发送出去;
比较模块, 用于接收远端链路发送的 LinkSummary消息, 并根据所述 L inkSummary消息得到链路标签状态信息, 比较所述远端链路发送的链路标 签状态信息和所述本端链路上的链路标签状态信息, 将比较结果发送至所 述结果模块;
结果模块, 用于将所述比较结果发送出去。
6、 如权利要求 5所述一种节点设备, 其特征在于, 所述链路标签状态信 息包括所有状态为占用的 LSP的出、 入标签信息, 或所有状态为空闲的 LSP 的出、 入标签信息, 或所有 LSP的出、 入标签信息状态。
7、 如权利要求 6所述一种节点设备, 其特征在于,
当所述比较模块接收到的链路标签状态信息为所有状态为占用的 LSP 的出、入标签信息时,默认没有收到的链路上 LSP的出标签信息和入标签信 息的状态均为空闲;
当所述比较模块接收到的链路标签状态信息为所有状态为空闲的 LSP 的出、入标签信息时,默认没有收到的链路上 LSP的出标签信息和入标签信 息的状态均为占用。
8、 一种网络系统, 其特征在于, 包括:
第一节点, 用于收集本端链路上的链路标签状态信息, 并将该信息添 加到 Li nkSu匪 ary消息中发送出去;
第二节点, 用于接收所述 LinkSummary消息, 并根据所述 LinkSummary 消息得到所述链路标签状态信息, 并与本端的链路上相应的出标签状态和 入标签状态进行比较, 得到并发送比较结果。
9、 如权利要求 8所述的一种网络系统, 其特征在于, 所述链路标签状 态信息包括所有状态为占用的 LSP的出、入标签信息,或所有状态为空闲的 LSP的出、 入标签信息, 或所有 LSP的出、 入标签信息状态。
10、 如权利要求 9所述的一种网络系统, 其特征在于,
当所述第二节点接收到的链路标签状态信息为所有状态为占用的 LSP 的出、入标签信息时,默认没有收到的链路上 LSP的出标签信息和入标签信 息的状态均为空闲;
当所述第二节点接收到的链路标签状态信息为所有状态为空闲的 LSP 的出、 入标签信息时, 默认没有收到的链路上 LSP的出标签信息和入标签 信息的状态均为占用。
PCT/CN2009/073083 2008-09-22 2009-08-04 一种检测链路标签状态的方法、设备与系统 WO2010031283A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN 200810216304 CN101686186B (zh) 2008-09-22 2008-09-22 一种检测链路标签状态的方法、设备与系统
CN200810216304.6 2008-09-22

Publications (1)

Publication Number Publication Date
WO2010031283A1 true WO2010031283A1 (zh) 2010-03-25

Family

ID=42039084

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/073083 WO2010031283A1 (zh) 2008-09-22 2009-08-04 一种检测链路标签状态的方法、设备与系统

Country Status (2)

Country Link
CN (1) CN101686186B (zh)
WO (1) WO2010031283A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106803785A (zh) * 2015-11-26 2017-06-06 中兴通讯股份有限公司 一种链路管理方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859371A (zh) * 2005-10-28 2006-11-08 华为技术有限公司 一种流量工程链路时隙状态一致性校验方法
US20070133540A1 (en) * 2005-12-08 2007-06-14 Kyung Gyu Chun Method for measuring performance of MPLS LSP
CN101047700A (zh) * 2006-05-01 2007-10-03 华为技术有限公司 一种提高lmp控制通道可靠性的方法与装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859371A (zh) * 2005-10-28 2006-11-08 华为技术有限公司 一种流量工程链路时隙状态一致性校验方法
US20070133540A1 (en) * 2005-12-08 2007-06-14 Kyung Gyu Chun Method for measuring performance of MPLS LSP
CN101047700A (zh) * 2006-05-01 2007-10-03 华为技术有限公司 一种提高lmp控制通道可靠性的方法与装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LANG J., RFC4204 LINK MANAGEMENT PROTOCOL (LMP), October 2005 (2005-10-01) *

Also Published As

Publication number Publication date
CN101686186B (zh) 2012-11-14
CN101686186A (zh) 2010-03-31

Similar Documents

Publication Publication Date Title
US8289843B2 (en) Service failure recovery method and system
US8014300B2 (en) Resource state monitoring method, device and communication network
EP1845640B1 (en) Method for restoring link failure and apparatus thereof
WO2007128176A1 (fr) Procédé de commutation de service et noeud de réseau associé
CN108924044B (zh) 链路维持方法、pe设备及可读存储介质
WO2007048299A1 (fr) Procede et dispositif pour la verification de coherence de l’etat d’intervalle temporel dans la liaison d’ingenierie de trafic.
US20100128611A1 (en) Transmitting apparatus, alarm control method, and computer product
US20150186202A1 (en) Method and Device for Sending Inter-Domain Fault Information
Le Roux et al. Evaluation of existing GMPLS protocols against multi-layer and multi-region networks (MLN/MRN)
WO2012071909A1 (zh) 业务恢复方法及装置
CN102315987B (zh) 环网保护组链路回切方法及装置
US10135715B2 (en) Buffer flush optimization in Ethernet ring protection networks
CN101248630A (zh) 一种自动交换光网络快速重路由的实现方法
WO2010031283A1 (zh) 一种检测链路标签状态的方法、设备与系统
CN1983908B (zh) 一种标签资源管理的自纠错方法
US8462617B2 (en) Method for relieving failure, and packet communication device
Kim et al. Protection switching methods for point‐to‐multipoint connections in packet transport networks
WO2014026585A1 (zh) 一种单光纤故障处理方法及装置
US10432505B2 (en) Systems, apparatuses, and methods for rerouting network traffic
Kim et al. Enhanced linear protection switching methods supporting dual node interconnection in packet transport networks
JP2006203721A (ja) 故障箇所発見方法および故障箇所発見装置
WO2017066971A1 (zh) 一种清除残留标签交换路径lsp的方法及装置
EP1450525B1 (en) Control plane stability in communications networks
Gong et al. Single-node failure notification for data-intensive transmission in GMPLS network
Ruepp et al. Epidemic Network Failures in Optical Transport Networks

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09814004

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09814004

Country of ref document: EP

Kind code of ref document: A1