WO2007124628A1 - Procédé d'allocation d'étiquette, de remise d'étiquette, et routeur de commutation d'étiquette - Google Patents
Procédé d'allocation d'étiquette, de remise d'étiquette, et routeur de commutation d'étiquette Download PDFInfo
- Publication number
- WO2007124628A1 WO2007124628A1 PCT/CN2006/003163 CN2006003163W WO2007124628A1 WO 2007124628 A1 WO2007124628 A1 WO 2007124628A1 CN 2006003163 W CN2006003163 W CN 2006003163W WO 2007124628 A1 WO2007124628 A1 WO 2007124628A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- label
- lsr
- lsp
- unicast
- multicast
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 89
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 123
- 238000013507 mapping Methods 0.000 claims description 30
- 238000012545 processing Methods 0.000 claims description 3
- 230000005540 biological transmission Effects 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 15
- 230000011664 signaling Effects 0.000 description 15
- 238000004891 communication Methods 0.000 description 8
- 238000002716 delivery method Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000010380 label transfer Methods 0.000 description 4
- 230000000644 propagated effect Effects 0.000 description 2
- 235000008694 Humulus lupulus Nutrition 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/16—Multipoint routing
-
- 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]
- H04L45/507—Label distribution
Definitions
- the present invention relates to multicast communication technologies, and in particular, to a label distribution method, a label delivery method, and a label switching router in multicast communication. Background of the invention
- Multi-Protocol Label Switching (MPLS) Multicast extends the Label Distribution Protocol (LDP) and Resource Reservation Protocol-Traffic Engineering (RSVP-TE) to support multicast trees.
- LDP Label Distribution Protocol
- RSVP-TE Resource Reservation Protocol-Traffic Engineering
- MPLS label switched path LSP
- the network entry classifies the packet, selects the corresponding LSP according to the classification result, and puts the corresponding label.
- the intermediate router After receiving the MPLS packet, the intermediate router directly forwards the label according to the label of the MPLS header without searching for the destination node through the IP address of the Internet Protocol (IP) packet header.
- IP Internet Protocol
- label allocation technology is usually used to ensure more All Label Switch Routers (LSRs) that broadcast 'next hops' have the same label.
- an upstream label allocation mode may be adopted, or a downstream label allocation mode based on an upstream recommendation may be adopted.
- the upstream label allocation mode all downstream LSRs in the next hop are assigned the same label by the upstream LSR in the multicast.
- the label assignment value is recommended by the upstream.
- the upstream recommended label value is used.
- Figure 1 shows a signaling flow diagram of an existing downstream label assignment method. Referring to Figure 1, the existing downstream label distribution methods include:
- the downstream LSR requests the message by using a label mapping message carrying a special label.
- the LSR grants a recommendation to the label of the next hop, where the special label indicates that the downstream LSR requests the upstream LSR for the label recommendation value.
- step 102 the upstream LSR sends the suggested value of the label to the downstream LSR through the label request message.
- step 103 the downstream LSR returns a label mapping message to the upstream LSR, indicating the label recommended by the upstream LSR.
- Figure 2 shows a schematic diagram of the network structure when unicast and multicast exist on the same network.
- the path of the unicast LSP in the network is routers R2 to R9 to R10 to R5, wherein the label assigned to R10 is K;
- the path of the multicast tree is routers R1 to R9 to R3 and R7, where The label for R3 and R7 is also K.
- the present invention provides a label allocation method capable of ensuring successful establishment of a multicast tree when a label conflict occurs.
- the label distribution method of the present invention includes:
- the first label is used as a multicast label, and is allocated to the multicast label switching path LSP between the upstream label switching router LSR and the downstream LSR;
- the first label allocated for the multicast LSP is the same as the first label used by the unicast LSP
- the first label used in the unicast LSP between the upstream LSR and the downstream LSR is transferred, and the unicast LSP is allocated.
- Second label The first label is reassigned as a multicast label to the multicast LSP between the upstream LSR and the downstream LSR.
- the present invention also provides a label delivery method capable of selling a unicast label when a unicast conflicts with a multicast label.
- the method includes:
- the unicast label is released, and the unicast LSP is assigned a second label.
- the present invention further provides a label switching router (LSR), which is capable of transmitting a unicast label when the unicast and the multicast label collide, and the LSR includes: a label release unit and a label distribution unit, where
- a label release unit configured to release the first label used by the unicast LSP when the first label allocated for the multicast label switched path LSP collides with the first label used by the unicast LSP, and notify the label allocation unit to re Allocating labels for the unicast LSP;
- a label allocation unit configured to receive a notification from the label release unit, and assign a second label to the unicast LSP after receiving the notification.
- the present invention has the following beneficial effects:
- the unicast transmits the label, that is, the unicast label is first released, and the downstream LSR allocates a new label for the unicast, and then Re-allocating the conflicting label to the multicast, effectively solving the conflict between the unicast label and the multicast label, ensuring the successful establishment of the multicast tree, and avoiding the phenomenon that the multicast data stream is propagated through the unicast path, simplifying The transfer process.
- FIG. 1 is a signaling flow chart of an existing upstream label-based downstream label allocation method
- FIG. 2 is a schematic diagram of a network structure when unicast and multicast exist on the same network
- 3 is a flow chart of a label distribution method of the present invention
- FIG. 4 is a signaling flow diagram of a label allocation method in an upstream on-demand allocation mode according to Embodiment 1 of the present invention.
- FIG. 5 is a signaling flow diagram of a label allocation method in an upstream active allocation mode according to Embodiment 1 of the present invention.
- FIG. 6 is a signaling flow diagram of a label allocation method in a downstream on-demand allocation mode according to Embodiment 2 of the present invention.
- FIG. 7 is a signaling flow diagram of a label allocation method in a downstream active allocation mode according to Embodiment 2 of the present invention.
- FIG. 8 is a signaling flow diagram of a label allocation method in an upstream on-demand allocation mode according to Embodiment 3 of the present invention.
- FIG. 9 is a signaling flow diagram of a label allocation method in a downstream active allocation mode according to Embodiment 3 of the present invention.
- FIG. 10 is a schematic diagram of data flow of a unicast label delivery process in Embodiment 3 of the present invention.
- FIG. 11 is a schematic structural diagram of a label switching router in the present invention. Mode for carrying out the invention
- the present invention provides a label allocation method, the basic idea of which is: when a unicast label is the same as a multicast label, a unicast label is issued when a conflict occurs.
- the present invention also provides a method for label delivery.
- the basic idea is: when a label conflicts, the downstream LSR interacts with the upstream LSR to allocate a new label to the unicast LSP between the two, and uses the unicast LSP.
- the conflicting label # put.
- Figure 3 illustrates a method of label assignment in accordance with the teachings of the present invention.
- the label distribution method of the present invention includes:
- the upstream LSR interacts with the downstream LSR, and allocates the first label as a multicast label to the multicast LSP between the upstream LSR and the downstream LSR.
- the first is allocated for the multicast LSP between the upstream LSR and the downstream LSR.
- the label is the same as the first label used by the unicast LSP between the upstream LSR and the downstream LSR
- the upstream LSR interacts with the downstream LSR, and the first unicast LSP is used between the upstream LSR and the downstream LSR.
- Label delivery and assigning a second label to the unicast LSP;
- step 303 the first label is reassigned as a multi-plug-tag to the multicast LSP between the upstream LSR and the downstream LSR.
- the unicast when a unicast conflicts with a multicast label, the unicast transmits the label, that is, releases the unicast label, and the downstream LSR allocates a new label for the unicast, and then reassigns the conflicting label to the label.
- Multicast which effectively resolves the conflict between the unicast tag and the multicast tag, ensures the successful establishment of the multicast tree, and can avoid the phenomenon that the multicast data stream propagates through the unicast path, simplifying the transmission process.
- the label allocation method of each embodiment of the present invention will be described below by taking the LDP protocol as an example.
- the following embodiments are still based on the network structure shown in FIG. 2, and still use R9 as the upstream LSR and R10 as the downstream LSR, and the conflicting label is referred to as the first label, and the newly assigned label is referred to as the second label.
- the label is allocated by the upstream LSR.
- the label is unicast, and the unicast label is first released and then re-allocated.
- This embodiment includes two modes: an upstream on-demand allocation mode and an upstream active allocation mode.
- FIG. 4 A signaling flow diagram of the label allocation method in the upstream on-demand allocation mode in this embodiment is shown in FIG. Referring to Figure 4, the label allocation method in the upstream on-demand allocation mode includes:
- step 401 402 R10 sends a Label Request message to R9 through the multicast LSP, requesting R9 to perform label allocation on the multicast; R9 carries the allocated first label in a Label Mapping message, Return to R10 through the multicast LSP.
- step 403 when R10 detects a label conflict, R10 sends a label to R9 through the multicast LSP. --- Label the Release message, indicating to R9 that the received label will be released.
- R10 compares the received first label with the unicast label used by itself in unicast. When the two labels are the same, it determines that a label conflict occurs, and then releases the first label from the multicast LSP. .
- R10 sends a Label Withdraw message carrying the first label to R9 through the unicast LSP, indicating that the first label is revoked; R9 returns a label release message to R10, indicating that the first label is released.
- the unicast does not use the first label that conflicts; R10 then assigns the second label as a new unicast label to unicast, and sends a label mapping message carrying the second label to R9 through the unicast LSP.
- the second tag is used to forward the unicast data packet.
- the above steps 404 - 406 are the label transfer process.
- R10 sends a Notification message to R9 on the multicast LSP, indicating that the first label in conflict is in an available state;
- R9 sends a label mapping message carrying the first label to the multicast LSP.
- R10 the first label is reassigned as a multicast label to the multicast LSP between R9 and R10.
- FIG. 5 is a signaling flow chart showing a label allocation method in an upstream active allocation mode in this embodiment.
- the label allocation method in the upstream active allocation mode includes:
- the first label allocated by the R9 for the multicast is carried in the label mapping message, and is sent to the RIO through the multicast LSP.
- the R10 sends the label release message to the R9 through the multicast LSP. , indicates to R9 that the received tag is released.
- the RIO sends a label revocation message carrying the first label to the R9 through the unicast LSP, indicating that the first label is revoked;
- R9 returns a label release message to the R10, releasing the first label; and then the R10 will
- the second label is assigned to the unicast as a new unicast label, and the label mapping message carrying the second label is sent to R9 through the unicast LSP.
- the unicast LSP between R9 and R10 uses the second label as the unicast label.
- the above steps 503 ⁇ 505 are the label transfer process.
- the R10 sends a notification message to the R9 on the multicast LSP, indicating that the first label in the conflict is in an available state; R9 sends the label mapping message carrying the first label to the R10 through the multicast LSP.
- the first label is reassigned as a multicast label to the multicast LSP between R9 and R10.
- the difference between the upstream active allocation mode and the upstream on-demand allocation mode is as follows: In the upstream active allocation mode, the R9 that is the upstream LSR actively performs label mapping without the R10 request.
- the unicast label is transmitted, that is, the unicast label is first released, and the downstream LSR allocates a new label for unicast, and then a conflict occurs.
- the tags are reassigned to multicast to ensure successful establishment of the multicast tree.
- the label is allocated by the downstream LSR.
- the label is unicast, and the unicast label is first released and then redistributed.
- This embodiment includes two modes: a downstream on-demand allocation mode and a downstream active allocation mode. Both of the above modes are based on the recommendations of the upstream LSR for label assignment.
- FIG. 6 A signaling flow diagram of the label allocation method in the downstream on-demand allocation mode in this embodiment is shown in FIG. Referring to Figure 6, the label allocation method in the downstream on-demand allocation mode includes:
- step 601 R9 sends a label with a recommended value equal to the first one through the multicast LSP. ... a tag request message for a tag, requesting R10 to assign a multicast tag to the multicast.
- R10 detects that a label conflict occurs, and determines that the first label is transmitted by unicast, and then sends a label revocation message carrying the first label to R9 through the unicast LSP, and notifies that R9 will be used for unicast.
- the first label is revoked;
- R9 returns a label release message to R10 through the unicast LSP, indicating that the first label in the unicast is released;
- R10 determines that the first label is unicast and then puts the second label re-allocated for unicast into the label. In the mapping message, it is sent to R9 on the unicast LSP.
- R10 parses the first label from the message, and the received first label and R10 are in unicast.
- the labels used are compared, and when the two labels are the same, it is determined that a label conflict occurs. Then, R10 decides to let the unicast sell the first label, and then informs R9 to sell the first label.
- R10 reassigns a second label to R10 in unicast, and submits the second label to R9 to re-establish unicast communication. Thereafter, the unicast communication between R10 and R9 uses the newly assigned second tag for packet forwarding without using the conflicting first tag.
- step 605 R10 sends a label mapping message carrying the first label to the R9 through the multicast LSP, and re-assigns the first label as a multicast label to the multicast LSP between R9 and R10.
- R10 detects that the first label has been released by unicast, and when it is in an available state, it re-assigns the first label to the multicast LSP between R9 and R10, thereby successfully establishing a multicast tree.
- the downstream LSR waits for the upstream LSR to request a multicast label and allocates labels according to the recommendations of the upstream LSR.
- Fig. 7 is a flow chart showing the signaling of the label allocation method in the downstream active allocation mode in this embodiment.
- the label allocation method in the downstream active allocation mode includes:
- R10 sends a label mapping message carrying a special label to R9 through the multicast LSP, and requests the recommended value of the multicast label from R9; R9 returns to R10 through the multicast LSP.
- the tag request message carrying the first tag requests R10 to allocate a multicast tag.
- R10 actively initiates label mapping, and sends a special label indicating the recommended value of the request label to R9;
- R9 determines the R10 request label recommendation value according to the received special label, then A label is sent as a suggestion label to R9.
- R10 detects that a label conflict occurs, and determines that the first label is transmitted by unicast, and then sends a label revocation message carrying the first label to R9 through the unicast LSP, and notifies that R9 will be used for unicast.
- the first label is revoked;
- R9 returns a label release message to R10 through the unicast LSP, indicating that the first label in the unicast is released;
- R10 determines that the first label is unicast and then puts the second label re-allocated for unicast into the label. In the mapping message, it is sent to R9 on the unicast LSP.
- the unicast LSP between R9 and R10 is tagged with the second tag, and the second tag is used for data forwarding during unicast communication.
- step 706 R10 sends a label mapping message carrying the first label to R9 through the multicast LSP, and then reassigns the first label as a multicast label to the multicast LSP between R9 and R10.
- steps 703 to 706 are the same as steps 602 to 605 in the label allocation method in the downstream on-demand allocation mode in this embodiment.
- downstream LSR actively initiates label mapping instead of waiting for the upstream LSR to initiate a label mapping request.
- the unicast label is sent, that is, the first unicast label is placed, and the downstream LSR allocates a new label for the unicast, and then the conflict occurs.
- the tag is reassigned to multicast to ensure successful establishment of the multicast tree.
- Embodiment 1 and Embodiment 2 when a label conflict occurs, the conflicting label is first released, and the new label is newly allocated for the unicast LSP. Such a method of first dismantling may result in a temporary interruption of the unicast service.
- this embodiment is The smooth label switching mode is implemented to realize label distribution.
- each LSR can maintain two different tags for the same forwarding equivalence class (FEC).
- FEC forwarding equivalence class
- an output interface table is set in the R9 as the upstream LSR for storing two tags as output tags from R10, and the two tags are the first tag and the second tag, respectively.
- Fig. 8 is a diagram showing the signaling flow of the label allocation method in the upstream on-demand allocation mode in this embodiment.
- the label allocation method in the upstream on-demand allocation mode in this embodiment includes:
- R10 sends a label request message to R9 through the multicast LSP, requesting R9 to perform label allocation on the multicast; R9 carries the allocated first label in the label mapping message, and returns to RIO through the multicast LSP. R10 sends a label release message to R9 through the multicast LSP when it detects a label collision, and indicates to R9 that the received label is released.
- R10 sends a label mapping message carrying the second label to the R9 through the unicast LSP, and allocates a new label for the unicast. Then, the R10 revokes the label carrying the first label through the unicast LSP. The message is sent to R9, indicating that the first label used in the unicast is revoked; R9 releases the first label used in unicast according to the label revocation message, and returns the label release message to R10 through the unicast LSP, and indicates the first The tag has been released by unicast.
- FIG. 10 is a schematic diagram showing the data flow in the unicast label delivery process of the embodiment.
- R10 assigns the second label to unicast after determining that the first label conflicts.
- the second label is parsed from the message, and the parsed second label is saved in the output interface table. Since the output interface table has already stored the first label before this, the unicast data output from R9 to R10 thereafter becomes changed respectively.
- Two copies of the second tag and the first tag are until R10 releases the first tag for unicast in step 806.
- the data information of the two copies of the data is identical, except that the corresponding tags are different.
- R10 receives the two copies of the data through the unicast LSP, only the data copy with the second label is processed, and the copy of the data with the first label is discarded.
- R10 sends a notification message to the R9 on the multicast LSP, indicating that the first label in conflict is in an available state;
- R9 sends the label mapping message carrying the first label to the R10 through the multicast LSP. Re-assign the first label as a multicast label to the multicast LSP between R9 and R10.
- the R10 request R9 in step 801 is not required to perform label allocation, but directly in step 802, the label assignment is initiated by R9.
- FIG. 9 is a flow chart showing the signaling of the label allocation method in the downstream active allocation mode in this embodiment.
- the label allocation method in the downstream active allocation mode includes:
- R10 sends a label mapping message carrying a special label to R9 through the multicast LSP, and requests the recommended value of the multicast label from R9; R9 returns the label carrying the first label to the R10 through the multicast LSP.
- Request message request R10 to assign a multicast label.
- R10 sends a label mapping message carrying the second label to the R9 through the unicast LSP, and allocates a new label for the unicast. Then, the R10 revokes the label carrying the first label through the unicast LSP. The message is sent to R9, indicating that the first label used in the unicast is revoked; R9 is based on the first label used in the unicast according to the label revocation message, and returns the label dry message to R10 through the unicast LSP, and indicates The first tag has been unicast # put.
- step 906 R10 sends a label carrying the first label to R9 through the multicast LSP.
- Apply amendment Animal amendment
- This step is the same as the operation of step 706 in the second embodiment.
- step 901 If the downstream on-demand allocation mode is adopted, step 901 is not performed, but in step 902, the label request message carrying the label recommendation value equal to the first label is sent to R10 through the multicast LSP by the R9 as the upstream LSR. R10 allocates multicast labels for multicast.
- R10 which is the downstream LSR
- R9 which is the upstream LSR
- R9 generates the unicast data as Two copies of the same data with different labels are sent.
- R10 only processes the copy of the data with the new label, and discards the copy of the data with the original label until the original label is released. In this way, the unicast service between R9 and R10 smoothly switches to the new label, thereby avoiding the interruption of the unicast service during the label switching process.
- the label distribution in the present invention can be implemented in two different manners.
- One is that when a label conflict occurs, the unicast first hashes the label, and then re-assigns a new label to the unicast.
- the other is to directly assign a new label to the unicast LSP when the label conflict occurs, and then release the conflicting label used by the unicast LSP.
- Both of the above label delivery methods can effectively solve the problem that the multicast tree establishment failure caused by the label conflict, and can make the multicast transmission process be performed smoothly and smoothly.
- the present invention further provides a label switching router LSR.
- the LSR includes: a label dry unit and a label distribution unit, wherein the label release unit is used for When the first label allocated by the LSP is in conflict with the first label used by the unicast LSP, # put the first label used by the unicast LSP, and notify the label allocation unit to re- The unicast LSP allocates a label; the label allocation unit is configured to receive the notification from the label release unit, and allocate a second label to the unicast LSP after receiving the notification.
- the timing at which the label release unit notifies the label allocation unit to re-tag the unicast LSP may be before the first label used by the unicast LSP is released, or after the first label used by the unicast LSP is released.
- the label release unit may include a revocation notification module, configured to notify the upstream LSR to revoke the unicast LSP by using a unicast LSP when the first label allocated for the multicast LSP collides with the first label used by the unicast LSP.
- the first label after receiving the revocation notification, the upstream LSR replies to the label release message, indicating # placing the first label.
- the label distribution unit may include a label notification module, configured to: after receiving the label release message of the upstream LSR, send the allocated second label to the upstream LSR by using the unicast LSP, and notify the upstream LSR that the second label is the unicast LSP. New label.
- the label #release unit releases the first label from the multicast LSP before the first label used by the unicast LSP.
- the label allocation unit allocates the second label to the unicast LSP
- the first label that is in conflict with the upstream LSR is notified that the first label is in the available state, and the upstream LSR re-allocates the first label to the multicast LSP.
- the LSR further includes a data processing unit for receiving two identical copies of the data from the upstream LSR with the first label and the second label, and processing the data copy with the second label, A copy of the data of a tag is discarded.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
标签分配方法、 标签出让方法及标签交换路由器, 技术领域
本发明涉及多播通信技术, 尤其涉及多播通信中的标签分配方法、 标签 出让方法及标签交换路由器。 发明背景
目前多播通信由于其能够将同一信息送往多个目的节点而成为网络应用 中的热点技术。 多协议标签交换( MPLS )多播对标签分发协议( LDP )及资 源预留协议-流量工程(RSVP-TE )进行扩展, 以支持多播树。 在 MPLS技 术中 , 通过诸如 LDP协议的 MPLS信令来建立 MPLS标记交换路径 (LSP), 在进行数据转发时, 网络入口对报文进行分类, 根据分类结果选择相应的 LSP, 并打上相应的标签。 中间路由器在收到 MPLS报文后, 直接根据 MPLS 报头的标签进行转发, 而无需通过互联网协议( IP )报文头的 IP地址查找目 的节点。
对于在 LSP隧道或者多接入链路 ( multi-access links )上的多播, 为了更 为有效地进行多播传输, 并且基于筒化多播传输操作的考虑, 通常利用标签 分配技术来保证多播'下一跳的所有标签交换路由器( LSR )具有相同的标签。
在目前的标签分配中, 可以采用上游标签分配模式, 也可以采用基于上 游建议的下游标签分配模式。 在上游标签分配模式中, 由多播中的上游 LSR 对下一跳中的所有下游 LSR分配相同的标签。在下游标签分配模式中, 由上 游来建议标签分配值, 下一跳的所有 LSR进行标签分配时, 都采用上游建议 的统一标签值。 图 1示出了现有的下游标签分配方法的信令流程图。 参见图 1, 现有的下游标签分配方法包括:
在步骤 101中, 下游 LSR通过携带有特殊标签的标签映射消息, 请求上
游 LSR对下一跳的标签给出建议,其中该特殊标签表明下游 LSR向上游 LSR 征求标签建议值。
在步骤 102中,上游 LSR通过标签请求消息将标签的建议值发送给下游 LSR。
在步骤 103中, 下游 LSR向上游 LSR返回标签映射消息, 指明采用上 游 LSR建议的标签。
图 2示出了单播和多播存在于同一网络时的网络结构示意图。 如图 2所 示, 该网络中单播 LSP的路径为路由器 R2至 R9至 R10至 R5 , 其中分配给 R10的标签为 K; 多播树的路径为路由器 R1至 R9至 R3和 R7, 其中分配给 R3和 R7的标签也为 K。
当路由器 Rl 0需要加入到多播树时, R9的所有下游 LSR均须使用相同 的标签, 即 R10必须与 R3和 R7—样, 所使用的标签也必须为 。 但是, 由 于单播已经先于多播存在, 并且 R10在单播 LSP中使用的标签也为 K, 因此 会导致 R10在加入多播时使用的标签 Κ出现冲突。此时对标签冲突的解决方 法是使多播树建立失败, 由 R9和 R10建立新的单播 LSP来传输多播数据。 这样, 多播数据流必须通过单播路径来进行传播, 传输过程较为复杂。 发明内容
有鉴于此, 本发明提供一种标签分配方法, 能够在出现标签冲突时保证 多播树建立成功。
为实现上述目的, 本发明标签分配方法包括:
将第一标签作为多播标签,分配给上游标签交换路由器 LSR与下游 LSR 之间的多播标记交换路径 LSP;
当为多播 LSP分配的第一标签与单播 LSP所使用的第一标签相同时,将 上游 LSR与下游 LSR之间的单播 LSP中使用的第一标签出让, 并为该单播 LSP分配第二标签;
将第一标签作为多播标签, 重新分配给上游 LSR与下游 LSR之间的多 播 LSP。
本发明还提供一种标签出让方法, 能够在单播与多播标签冲突时, 出让 单播的标签。 该方法包括:
当为多播标记交换路径 LSP分配的第一标签与单播 LSP所使用的第一标 签相同时, 将单播标签释放, 并为该单播 LSP分配第二标签。
另外, 本发明还提供了一种标签交换路由器 LSR, 能够在单播与多播标 签冲突时, 出让单播的标签, 该 LSR包括: 标签释放单元和标签分配单元, 其中,
标签释放单元, 用于在为多播标记交换路径 LSP分配的第一标签与单播 LSP所使用的第一标签发生冲突时, 释放单播 LSP所使用的第一标签 , 并通 知标签分配单元重新为该单播 LSP分配标签;
标签分配单元, 用于接收来自标签释放单元的通知, 并在收到通知后为 该单播 LSP分配第二标签。
应用本发明, 能够在出现标签冲突时保证多播树建立成功。 具体而言, 本发明具有如下有益效果: 在单播与多播标签发生冲突时, 单播对标签进行 出让, 即首先释放单播的标签, 并且下游 LSR为单播分配新的标签, 而后再 将出现冲突的标签重新分配给多播, 从而有效地解决单播标签与多播标签的 冲突, 保证多播树的成功建立, 能够避免多播数据流通过单播路径来进行传 播的现象, 简化传输过程。 附图简要说明
下面将通过参照附图详细描述本发明的示例性实施例, 使本领域的普通 技术人员更清楚本发明的上述及其它特征和优点, 附图中:
图 1为现有的基于上游建议的下游标签分配方法的信令流程图; 图 2为单播和多播存在于同一网络时的网络结构示意图;
图 3为本发明标签分配方法的流程图;
图 4为本发明实施例 1中上游按需分配模式下的标签分配方法的信令流 程图;
图 5为本发明实施例 1中上游主动分配模式下的标签分配方法的信令流 程图;
图 6为本发明实施例 2中下游按需分配模式下的标签分配方法的信令流 程图;
图 7为本发明实施例 2中下游主动分配模式下的标签分配方法的信令流 程图;
图 8为本发明实施例 3中上游按需分配模式下的标签分配方法的信令流 程图;
图 9为本发明实施例 3中下游主动分配模式下的标签分配方法的信令流 程图;
图 10为本发明实施例 3中单播标签出让过程的数据流示意图。
图 11为本发明中的标签交换路由器结构示意图。 实施本发明的方式
本发明提供一种标签分配方法, 其基本思想是: 在单播标签与多播标签 相同即出现冲突时, 出让单播标签。 本发明还提供一种标签出让方法, 其基 本思想是: 在标签出现冲突时, 下游 LSR与上游 LSR交互, 为两者之间的 单播 LSP分配新的标签, 并将该单播 LSP使用的发生冲突的标签#放。
图 3示出了依据本发明思想的标签分配方法。 如图 3所示, 本发明的标 签分配方法包括:
在步骤 301中, 上游 LSR与下游 LSR交互, 将第一标签作为多播标签, 分配给上游 LSR与下游 LSR之间的多播 LSP; ·
在步骤 302中, 当为上游 LSR与下游 LSR之间的多播 LSP分配的第一
标签与该上游 LSR与下游 LSR之间的单播 LSP所使用的第一标签相同即出 现冲突时, 上游 LSR与下游 LSR交互, 将上游 LSR与下游 LSR之间的单播 LSP中使用的第一标签出让, 并为该单播 LSP分配第二标签;
在步骤 303中, 将第一标签作为多插-标签, 重新分配给上游 LSR与下游 LSR之间的多播 LSP。
也就是说, 在单播与多播标签发生冲突时, 单播对标签进行出让, 即释 放单播的标签, 并且下游 LSR为单播分配新的标签, 而后再将出现冲突的标 签重新分配给多播, 从而有效地解决单播标签与多播标签的冲突, 保证多播 树的成功建立, 能够避免多播数据流通过单播路径来进行传播的现象, 简化 传输过程。
下面以 LDP协议为例, 对本发明中各个实施例的标签分配方法进行描 述。 以下各个实施例仍然基于图 2所示的网络结构, 仍以 R9为上游 LSR, 以 R10为下游 LSR, 并且将发生冲突的标签称为第一标签, 将新分配的标签 称为第二标签。 R9和 R10之间存在单播 LSP和多播 LSP, 并且两个 LSP属 于同一条物理链路。
实施例 1
本实施例中, 由上游 LSR对标签进行分配, 在出现标签冲突时, 单播出 让标签, 并且单播标签先释放, 再重新分配。 本实施例包括两种方式: 上游 按需分配模式和上游主动分配模式。
图 4中示出了本实施例中上游按需分配模式下的标签分配方法的信令流 程图。 参见图 4, 上游按需分配模式下的标签分配方法包括:
在步骤 401 402 中, R10通过多播 LSP 向 R9发送标签请求(Label Request )消息 , 请求 R9对多播进行标签分配; R9将所分配的第一标签携带 于标签映射( Label Mapping ) 消息中, 通过多播 LSP返回给 R10。
在步骤 403中, R10在检测到标签冲突时, 通过多播 LSP向 R9发送标
――― 签幹放 ( Label Release ) 消息, 向 R9指明将所接收到的标签释放。
本步骤中, R10将接收到的第一标签与其自身在单播中所使用的单播标 签进行比较, 在两个标签相同时, 判定出现标签冲突, 则将第一标签从多播 LSP中释放。
在步骤 404 ~ 406中, R10通过单播 LSP向 R9发送携带有第一标签的标 签撤销 ( Label Withdraw ) 消息, 指明将该第一标签撤销; R9向 R10回复标 签释放消息, 指明释放第一标签, 单播不再使用发生冲突的第一标签; 而后, R10将第二标签作为新的单播标签分配给单播, 并通过单播 LSP将携带有第 二标签的标签映射消息发送给 R9。
在 R9接收到第二标签后, 使用该第二标签进行单播数据包的转发。 上 述步骤 404 - 406为标签出让过程。
在步骤 407 ~ 408中, R10在多播 LSP上向 R9发送通知 ( Notification ) 消息, 指明发生冲突的第一标签处于可用状态; R9通过多播 LSP将携带有 第一标签的标签映射消息发送给 R10, 重新将第一标签作为多播标签分配给 R9与 R10之间的多播 LSP。
在此处的两个步驟中, 当 R10获得第二标签后,第一标签已被单播释放, 因此该第一标签可以被用于多播通信中, 因此 R9再次为多播 LSP打上第一 标签。 此时, 多播树成功建立, 并且 R10在单播和多播中使用不同的标签, 两种通信均能够正常进行。
至此, 完成了本实施例中上游按需分配模式下的标签分配流程。
图 5示出了本实施例中上游主动分配模式下的标签分配方法的信令流程 图。 如图 5所示, 上游主动分配模式下的标签分配方法包括:
在步驟 501 ~ 502中, R9将为多播分配的第一标签携带于标签映射消息 中, 通过多播 LSP发送给 RIO; R10在检测到标签冲突时, 通过多播 LSP向 R9发送标签释放消息, 向 R9指明将所接收到的标签释放。
在步骤 503 ~ 505中, RIO通过单播 LSP向 R9发送携带有第一标签的标 签撤销消息, 指明将该第一标签撤销; R9向 R10回复标签释放消息, 释放 第一标签; 而后, R10将第二标签作为新的单播标签分配给单播, 并通过单 播 LSP将携带有第二标签的标签映射消息发送给 R9。
在 R9接收到新的单播标签后, R9与 R10之间的单播 LSP使用第二标签 作为单播标签。
上述步驟 503 ~ 505为标签出让过程。
在步驟 506 ~ 507中, R10在多播 LSP上向 R9发送通知消息, 指明发生 冲突的第一标签处于可用状态; R9通过多播 LSP, 将携带有第一标签的标签 映射消息发送给 R10, 重新将第一标签作为多播标签分配给 R9与 R10之间 的多播 LSP。
至此, 完成了本实施例中上游主动分配模式下的标签分配流程。
上游主动分配模式与上游按需分配模式的区别在于: 上游主动分配模式 下, 作为上游 LSR的 R9主动进行标签映射, 而无需 R10的请求。
由上述的两个流程可见, 在单播与多播标签发生冲突时, 对单播标签进 行出让, 即首先释放单播的标签, 并且下游 LSR为单播分配新的标签, 而后 再将出现冲突的标签重新分配给多播, 以保证多播树的成功建立。
实施例 2
本实施例中, 由下游 LSR对标签进行分配, 在出现标签冲突时, 单播出 让标签, 并且单播标签先释放, 再重新分配。 本实施例包括两种方式: 下游 按需分配模式和下游主动分配模式。上述两种模式均基于上游 LSR的建议进 行标签分配。
图 6中示出了本实施例中下游按需分配模式下的标签分配方法的信令流 程图。 参见图 6, 下游按需分配模式下的标签分配方法包括:
在步骤 601中, R9通过多播 LSP向 R10发送携带有标签建议值等于第
... 一标签的标签请求消息, 请求 R10为多播分配多播标签。
在步骤 602 ~ 604中, R10检测到发生标签冲突, 决定由单播出让第一标 签, 则通过单播 LSP向 R9发送携带有第一标签的标签撤销消息, 通知 R9 将用于单播的第一标签撤销; R9通过单播 LSP向 R10返回标签释放消息, 指明释放单播中的第一标签; R10确定第一标签被单播释放后, 将为单播重 新分配的第二标签放入标签映射消息中, 在单播 LSP上发送给 R9。
在此处三个步驟所构成的标签出让过程中, R10接收到来自于 R9的标 签请求消息后, 从该消息中解析出第一标签, 并将接收到的第一标签与 R10 在单播中使用的标签相比较, 在两个标签相同时, 判定出现标签冲突。 而后, R10决定使单播出让该第一标签, 则通知 R9 l销第一标签。 R10在确知 R9 释放单播中的第一标签后, 为单播中的 R10再分配一个第二标签, 并将该第 二标签提交给 R9, 重新建立单播通信。 此后, R10与 R9之间的单播通信使 用新分配的第二标签进行数据包转发, 而不再使用发生冲突的第一标签。
在步楝 605中, R10通过多播 LSP向 R9发送携带有第一标签的标签映 射消息, 重新将第一标签作为多播标签, 分配给 R9和 R10之间的多播 LSP。
在本步骤中, R10检测到第一标签已被单播释放, 处于可用状态时, 则 重新将该第一标签分配给 R9和 R10之间的多播 LSP, 从而成功地建立多播 树。
至此, 完成下游按需分配模式下的标签分配流程。
由上述流程可见, 在下游按需分配模式下, 下游 LSR等待上游 LSR请 求多播标签, 并根据上游 LSR的建议分配标签。
图 7示出了本实施例中下游主动分配模式下的标签分配方法的信令流程 图。 如图 7所示, 下游主动分配模式下的标签分配方法包括:
在步驟 701 ~ 702中, R10通过多播 LSP向 R9发送携带有特殊标签的标 签映射消息, 向 R9征求多播标签的建议值; R9再通过多播 LSP向 R10返回
携带有第一标签的标签请求消息, 请求 R10分配多播标签。
在此处的两个步驟中, R10主动发起标签映射, 将表明征求标签的建议 值的特殊标签发送给 R9; R9才艮据接收到的特殊标签确定此时 R10征求标签 建议值, 则将第一标签作为建议标签, 发送给 R9。
在步骤 703 ~ 705中, R10检测到发生标签冲突, 决定由单播出让第一标 签, 则通过单播 LSP向 R9发送携带有第一标签的标签撤销消息, 通知 R9 将用于单播的第一标签撤销; R9通过单播 LSP向 R10返回标签释放消息, 指明释放单播中的第一标签; R10确定第一标签被单播释放后, 将为单播重 新分配的第二标签放入标签映射消息中, 在单播 LSP上发送给 R9。
经过此处三个步骤组成的标签出让过程, R9与 R10之间的单播 LSP被 打上第二标签, 并在单播通信过程中使用该第二标签进行数据转发。
在步骤 706中 , R10通过多播 LSP向 R9发送携带有第一标签的标签映 射消息, 重新将第一标签作为多播标签分配给 R9和 R10之间的多播 LSP。
上述步骤 703至 706与本实施例中下游按需分配模式下的标签分配方法 中的步骤 602至 605相同。
至此, 完成本实施例中下游主动分配模式下的标签分配流程。
由上述流程可见,在下游主动分配模式下,下游 LSR主动发起标签映射, 而非等待上游 LSR发起标签映射请求。
在本实施例中, 在单播与多播标签发生冲突时, 对单播标签进行出让, 即首先 #放单播的标签, 并且下游 LSR为单播分配新的标签, 而后再将出现 冲突的标签重新分配给多播 , 以保证多播树的成功建立。
实施例 3
在上述的实施例 1和实施例 2中, 在出现标签冲突时, 首先释放出现冲 突的标签, 再为单播 LSP重新分配新的标签。 此种先拆除后建立的方法有可 能会导致单播业务的暂时性中断。 为了保证单播业务的连续性, 本实施例通
过平滑标签切换方式, 实现标签的分配。
在本实施例中, 每个 LSR都能够为同一个转发等价类(FEC )维护两个 不同的标签。 这样, 在 LSR出现单播与多播的标签冲突时, 首先为单播分配 新的标签,再将发生冲突的标签释放, 即允许新旧两个标签同时由单播使用。
下面仍以 LDP协议为例,对本实施例中的标签分配方法进行说明。 本实 施例中预先在作为上游 LSR的 R9中设置输出接口表, 用于存储来自于 R10 的作为输出标签的两个标签, 并且这两个标签分别为第一标签和第二标签。
图 8示出了本实施例中上游按需分配模式下的标签分配方法的信令流程 图。 参见图 8, 本实施例中的上游按需分配模式下的标签分配方法包括:
^步骤 801 ~ 803中, R10通过多播 LSP向 R9发送标签请求消息, 请求 R9对多播进行标签分配; R9将所分配的第一标签携带于标签映射消息中, 通过多播 LSP返回给 RIO; R10在检测到标签冲突时, 通过多播 LSP向 R9 发送标签释放消息, 向 R9指明将所接收到的标签释放。
此处的三个步骤与实施例 1中上游按需分配模式下的步骤 401至 403的 操作相同。
在步驟 804 ~ 806中, R10通过单播 LSP向 R9发送携带有第二标签的标 签映射消息, 为单播分配新的标签; 而后, R10再通过单播 LSP将携带有第 一标签的标签撤销消息发送给 R9, 指明将单播中使用的第一标签撤销; R9 根据标签撤销消息释放在单播中使用的第一标签,并通过单播 LSP将标签释 放消息返回给 R10 , 并指明第一标签已被单播释放。
图 10 示出了本实施例的单播标签出让过程中的数据流示意图。 参见图 10, 在此处的标签出让过程中, R10在确定第一标签发生冲突后, 将第二标 签分配给单播。 当 R9收到标签映射消息后, 从该消息中解析出第二标签, 并将解析出的第二标签保存在输出接口表中。 由于输出接口表在此之前已经 保存有第一标签, 因此, 此后从 R9输出给 R10的单播数据变为分别被打上
第二标签和第一标签的两份拷贝, 直到 R10在步骤 806中将用于单播的第一 标签释放。 这两份数据拷贝的数据信息完全相同, 只是对应的标签不同。 并 且, R10在通过单播 LSP接收到这两份数据拷贝时, 只对带有第二标签的数 据拷贝进行处理, 而将带有第一标签的数据拷贝丢弃。
在步骤 807 ~ 808中, R10在多播 LSP上, 向 R9发送通知消息, 指明发 生沖突的第一标签处于可用状态; R9通过多播 LSP,将携带有第一标签的标 签映射消息发送给 R10, 重新将第一标签作为多播标签分配给 R9和 R10之 间的多播 LSP。
此处的两个步骤与实施例 1中的步骤 407和 408的操作相同。
至此, 完成本实施例中上游按需分配模式下的标签分配流程。
如果采用上游主动分配模式, 则无需执行步骤 801中 R10请求 R9进行 标签分配, 而是直接在步骤 802中, 由 R9主动发起标签分配。
图 9示出了本实施例中下游主动分配模式下的标签分配方法的信令流程 图。 如图 9所示, 下游主动分配模式下的标签分配方法包括:
在步骤 901 ~ 902中, R10通过多播 LSP向 R9发送携带有特殊标签的标 签映射消息, 向 R9征求多播标签的建议值; R9再通过多播 LSP向 R10返回 携带有第一标签的标签请求消息, 请求 R10分配多播标签。
. 此处的两个步骤与实施例 2中的步骤 701和 702的操作相同。
在步骤 903 ~ 905中, R10通过单播 LSP向 R9发送携带有第二标签的标 签映射消息, 为单播分配新的标签; 而后, R10再通过单播 LSP将携带有第 一标签的标签撤销消息发送给 R9, 指明将单播中使用的第一标签撤销; R9 根据标签撤销消息鋒放在单播中使用的第一标签, 并通过单播 LSP将标签幹 放消息返回给 R10, 并指明第一标签已被单播#放。
此处的三个步驟与本实施例中的步驟 804至 806的操作相同。
在步驟 906中, R10通过多播 LSP向 R9发送携带有第一标签的标签映
„„„ 射消息, 重新将第一标签作为多播标签分配给 R9和 R10之间的多播 LSP。
本步驟与实施例 2中的步骤 706的操作相同。
至此, 完成了本实施例中下游主动分配模式下的标签分配流程。
如果采用下游按需分配模式, 则无需执行步驟 901 , 而是在步驟 902中 由作为上游 LSR的 R9通过多播 LSP将携带有标签建议值等于第一标签的标 签请求消息发送给 R10, 对请求 R10为多播分配多播标签。
在本实施例中, 当发生标签冲突时,作为下游 LSR的 R10将新的单 4番标 签发送给作为上游 LSR的 R9, 此后在单播释放发生冲突的标签之前, R9将 单播数据生成为两份分别带有不同标签的相同数据拷贝进行下发, R10只对 带有新的标签的数据拷贝进行处理, 而将带有原有标签的数据拷贝丢弃, 直 到原有标签释放。 这样, R9与 R10之间的单播业务平滑地切换到新的标签 上, 而避免了单播业务在标签切换过程中出现中断的现象。
由上述的三个实施例可见, 本发明中的标签出让可以采用两种不同的方 式, 一种是在出现标签冲突时, 单播先 #放冲突标签, 然后再重新为单播分 配新的标签;另一种是在出现标签冲突时,先直接为单播 LSP分配新的标签, 然后再将该单播 LSP使用的发生冲突的标签释放。上述两种标签出让方式均 能够有效地解决标签冲突导致的多播树建立失败的情况, 并且能够使得多播 传输过程筒单而顺利地进行。
以上为以 LDP 协议为例所描述的本发明中标签分配以及标签出让方法 的实施例, 本发明的思想同样能够适用于其他标签分配协议, 例如 RSVP-TE 协议等。
另外, 对应本发明的方法, 本发明还提供了一种标签交换路由器 LSR, 参见图 11所示, 该 LSR包括: 标签幹放单元和标签分配单元, 其中, 标签 释放单元,用于在为多播 LSP分配的第一标签与单播 LSP所使用的第一标签 发生冲突时, #放单播 LSP所使用的第一标签, 并通知标签分配单元重新为
该单播 LSP分配标签; 标签分配单元, 用于接收来自标签释放单元的通知, 并在收到通知后为该单播 LSP分配第二标签。
关于标签释放单元通知标签分配单元重新为该单播 LSP 分配标签的时 机,可在释放单播 LSP所使用的第一标签之前,也可在释放单播 LSP所使用 的第一标签之后。
其中, 标签释放单元可包括撤销通知模块, 用于在为多播 LSP分配的第 一标签与单播 LSP所使用的第一标签发生冲突时, 通过单播 LSP通知上游 LSR撤销该单播 LSP中的第一标签, 上游 LSR收到撤消通知后, 回复标签 释放消息, 指明 #放第一标签。 标签分配单元可包括标签通知模块, 用于在 收到上游 LSR的标签释放消息后, 通过单播 LSP将分配的第二标签发送给 上游 LSR, 通知上游 LSR该第二标签为该单播 LSP的新标签。
标签 #放单元在幹放单播 LSP所使用的第一标签之前,将该第一标签从 所述多播 LSP中释放。标签分配单元在为单播 LSP分配第二标签之后,通过 多播 LSP通知上游 LSR发生冲突的第一标签处于可用状态, 上游 LSR重新 将该第一标签分配给该多播 LSP。
该 LSR进一步包括数据处理单元, 用于接收来自上游 LSR的分别带有 第一标签和第二标签的两份相同的数据拷贝, 并对带有第二标签的数据拷贝 进行处理, 将带有第一标签的数据拷贝丢弃。
以上所述仅为本发明的较佳实施例而已 , 并不用以限制本发明, 凡在本 发明的精神和原则之内, 所做的任何修改、 等同替换、 改进等, 均应包含在 本发明的保护范围之内。
Claims
1、 一种标签分配方法, 其特征在于, 该方法包括:
将第一标签作为多播标签,分配给上游标签交换路由器 LSR与下游 LSR 之间的多播标记交换路径 LSP;
当为多播 LSP分配的第一标签与单播 LSP所使用的第一标签相同时,将 上游 LSR与下游 LSR之间的单播 LSP中使用的第一标签出让, 并为该单播 LSP分配第二标签;
将第一标签作为多播标签, 重新分配给上游 LSR与下游 LSR之间的多 播 LSP。
2、 如权利要求 1所述的方法, 其特征在于, 所述将第一标签作为多播标 签, 分配给上游 LSR与下游 LSR之间的多播 LSP, 其步骤为:
下游 LSR请求上游 LSR分配多播标签, 上游 LSR将第一标签分配给该 多播 LSP, 并将该第一标签返回给下游 LSR。
3、如权利要求 2所述的方法,其特征在于,所述下游 LSR请求上游 LSR 分配多播标签为: 下游 LSR通过多播 LSP向上游 LSR发送标签请求消息。
4、 如权利要求 1所述的方法, 其特征在于, 所述将第一标签作为多播标 签, 分配给上游 LSR与下游 LSR之间的多播 LSP, 其步驟为:
上游 LSR将第一标签分配给该多播 LSP, 并将该第一标签返回给下游 LSR。
5、 如权利要求 2或 4所述的方法, 其特征在于, 所述将该第一标签返回 给下游 LSR为:
上游 LSR通过多播 LSP向下游 LSR发送携带有第一标签的标签映射消 l¾
6、 如权利要求 2或 4所述的方法, 其特征在于, 所述将上游 LSR与下 游 LSR之间的单播 LSP中使用的第一标签出让之前, 该方法进一步包括:
下游 LSR将该第一标签从所述多播 LSP中释放。
7、 如权利要求 6所述的方法, 其特征在于, 所述下游 LSR将第一标签 从所述多播 LSP中释放为:
下游 LSR通过多播 LSP向上游 LSR发送标签释放消息。
8、 如权利要求 2或 4所述的方法, 其特征在于, 所述将第一标签重新分 配给多播 LSP为:
下游 LSR向上游 LSR指明发生冲突的该第一标签处于可用状态, 上游 LSR将第一标签发送给下游 LSR, 重新将该第一标签分配给该多播 LSP。
9、 如权利要求 8所述的方法, 其特征在于, 所述下游 LSR向上游 LSR 指明该第一标签处于可用状态为: 下游 LSR通过多播 LSP向上游 LSR发送 通知消息;
所述上游 LSR将第一标签发送给下游 LSR,重新将该第一标签分配给该 多播 LSP 为: 上游 LSR通过多播 LSP将携带有第一标签的标签映射消息发 送给下游 LSR。
10、 如权利要求 1所述的方法, 其特征在于, 所述将第一标签作为多播 标签, 分配给上游 LSR与下游 LSR之间的多播 LSP为:
上游 LSR将第一标签作为多播标签的建议值, 发送给下游 LSR。
11、 如权利要求 1所述的方法, 其特征在于, 所述将第一标签作为多播 标签, 分配给上游 LSR与下游 LSR之间的多播 LSP为:
下游 LSR请求上游 LSR给出该多播 LSP的多播标签, 上游 LSR根据接 收到的请求, 将第一标签作为多 ·标签建议值, 发送给下游 LSR。
12、 如权利要求 11所述的方法, 其特征在于, 所述下游 LSR请求上游 LSR给出该多播 LSP的多播标签为:
下游 LSR通过多播 LSP向上游 LSR发送携带有表明征求标签建议值的 特殊标签的标签映射消息。
13、 如权利要求 10或 11所述的方法, 其特征在于, 所述上游 LSR将第 一标签作为多播标签的建议值, 发送给下游 LSR为:
上游 LSR通过多播 LSP向下游 LSR发送携带有第一标签的标签请求消
14、 如权利要求 10或 11所述的方法, 其特征在于, 所述将第一标签重 新分配给多播 LSP为:
下游 LSR通过多播 LSP向上游 LSR发送携带有第一标签的标签映射消 息。
15、 如权利要求 1所述的方法, 其特征在于, 所述将单播 LSP中使用的 第一标签出让, 并为该单播 LSP分配第二标签为:
下游 LSR确定出让单播 LSP中的第一标签, 通知上游 LSR撤销该第一 标签, 上游 LSR通知下游 LSR # :该第一标签, 下游 LSR再将第二标签作 为新的单播标签, 发送给上游 LSR。
16、 如权利要求 1所述的方法, 其特征在于, 所述将单播 LSP中使用的 第一标签出让, 并为该单播 LSP分配第二标签为:
下游 LSR将第二标签作为新的单播标签, 发送给上游 LSR, 而后下游 LSR通知上游 LSR撤销该第一标签, 上游 LSR通知下游 LSR释放该第一标 签。
17、 如权利要求 16所述的方法, 其特征在于, 预先在所述上游 LSR中 设置输出接口表, 所述下游 LSR将第二标签发送给上游 LSR之后, 该方法 进一步包括:
上游 LSR将接收到的第二标签记录在所述输出接口表中,将要传送给该 下游 LSR 的单播数据生成为分别带有第一标签和第二标签的两份相同的数 据拷贝, 并通过单播 LSP发送给下游 LSR; 下游 LSR对带有第二标签的数 据拷贝进行处理, 将带有第一标签的数据拷贝丟弃。
18、 如权利要求 15、 16或 17所述的方法, 其特征在于, 所述下游 LSR 通知上游 LSR撤销该单播 LSP中的第一标签为: 下游 LSR通过单播 LSP向 上游 LSR发送携带有第一标签的标签撤销消息;
所述上游 LSR通知下游 LSR释放该第一标签为:上游 LSR通过单播 LSP 向下游 LSR回复标签释放消息;
下游 LSR将第二标签发送给上游 LSR为: 下游 LSR通过单播 LSP将携 带有第二标签的标签映射消息发送给上游 LSR。
19、 一种标签出让方法, 其特征在于, 该方法包括:
当为多播标记交换路径 LSP分配的第一标签与单播 LSP所使用的第一标 签相同时, 将单播标签释放, 并为该单播 LSP分配第二标签。
20、 如权利要求 19所述的方法, 其特征在于, 所述将单播标签释放, 并_ 为该单播 LSP分配第二标签包括:
下游 LSR通过单播 LSP向上游 LSR发送携带有第一标签的标签撤销消 息, 通知上游 LSR撤销该单播 LSP中的第一标签;
上游 LSR将该第一标签从单播 LSP中幹放后,通过单播 LSP向下游 LSR 回复标签释放消息, 通知下游 LSR释放该第一标签;
下游 LSR通过单播 LSP将携带有第二标签的标签映射消息发送给上游 LSR, 通知上游 LSR该第二标签为该单播 LSP的新标签。
21、 如权利要求 19所述的方法, 其特征在于, 所述将单播标签舞放, 并 为该单播 LSP分配第二标签包括:
下游 LSR通过单播 LSP将携带有第二标签的标签映射消息发送给上游 LSR, 通知上游 LSR该第二标签为该单播 LSP的新标签;
下游 LSR通过单播 LSP向上游 LSR发送携带有笫一标签的标签撤销消 息, 通知上游 LSR撤销该单播 LSP中的第一标签;
上游 LSR将该第一标签从单播 LSP中释放后,通过单播 LSP向下游 LSR
回复标签释放消息, 通知下游 LSR释放该第一标签。
22、 如权利要求 21所述的方法, 其特征在于, 预先在所述上游 LSR中 方法进一步包括:
上游 LSR将接收到的第二标签记录在所述输出接口表中,将要传送给该 下游 LSR的单播数据生成为分别带有第一标签和第二标签的两份相同的数 据拷贝, 并通过单播 LSP发送给下游 LSR; 下游 LSR对带有第二标签的数 据拷贝进行处理, 将带有第一标签的数据拷贝丢弃。
23、 一种标签交换路由器 LSR, 其特征在于, 该 LSR包括: 标签释放单 元和标签分配单元, 其中,
标签释放单元, 用于在为多播标记交换路径 LSP分配的第一标签与单播 LSP所使用的第一标签发生冲突时, 释^:单播 LSP所使用的第一标签, 并通 知标签分配单元重新为该单播 LSP分配标签;
标签分配单元, 用于接收来自标签释放单元的通知, 并在收到通知后为 该单播 LSP分配第二标签。
24、 根据权利要求 23所述的 LSR, 其特征在于, 所述标签释放单元包 括撤销通知模块,用于在为多播 LSP分配的第一标签与单播 LSP所使用的第 一标签发生冲突时, 通过单播 LSP通知上游 LSR撤销该单播 LSP中的第一 标签。
25、 根据权利要求 23所述的 LSR, 其特征在于, 所述标签分配单元包 括标签通知模块, 用于通过单播 LSP将分配的第二标签发送给上游 LSR, 通 知上游 LSR该第二标签为该单播 LSP的新标签。
26、 根据权利要求 23所述的 LSR, 其特征在于, 所述标签鋒放单元进 一步用于, 在释放单播 LSP所使用的第一标签之前, 将该第一标签从所述多 播 LSP中释放。
27、 根据权利要求 23所述的 LSR, 其特征在于, 所述标签分配单元进 一步用于, 在为所述单播 LSP分配第二标签之后, 通过多播 LSP通知上游 LSR发生冲突的第一标签处于可用状态。
28、 根据权利要求 23所述的 LSR, 其特征在于, 该 LSR进一步包括数 据处理单元,用于接收来自上游 LSR的分别带有第一标签和第二标签的两份 相同的数据拷贝, 并对带有第二标签的数据拷贝进行处理, 将带有第一标签 的数据拷贝丟弃。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP06817889.6A EP1976198B1 (en) | 2006-04-27 | 2006-11-24 | Method for allocating label, for remising label, and label switch router |
US12/172,402 US7787457B2 (en) | 2006-04-27 | 2008-07-14 | Label assigning method, label replacing method and label switching router |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200610076080.4 | 2006-04-27 | ||
CN2006100760804A CN101047624B (zh) | 2006-04-27 | 2006-04-27 | 标签分配方法以及标签出让方法 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/172,402 Continuation US7787457B2 (en) | 2006-04-27 | 2008-07-14 | Label assigning method, label replacing method and label switching router |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2007124628A1 true WO2007124628A1 (fr) | 2007-11-08 |
Family
ID=38655038
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2006/003163 WO2007124628A1 (fr) | 2006-04-27 | 2006-11-24 | Procédé d'allocation d'étiquette, de remise d'étiquette, et routeur de commutation d'étiquette |
Country Status (4)
Country | Link |
---|---|
US (1) | US7787457B2 (zh) |
EP (1) | EP1976198B1 (zh) |
CN (1) | CN101047624B (zh) |
WO (1) | WO2007124628A1 (zh) |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2920624B1 (fr) * | 2007-09-03 | 2010-03-12 | Alcatel Lucent | Procede d'etablissement d'une connexion bidirectionnelle point a multipoint |
CN100589113C (zh) * | 2008-07-23 | 2010-02-10 | 云南昆船设计研究院 | 用于rfid系统的自适应二进制树的多标签冲突仲裁方法 |
US8411681B2 (en) * | 2008-12-10 | 2013-04-02 | Electronics And Telecommunications Research Institute | Multicasting method in network including T-MPLS network and WDM network and apparatus therefor |
US8644315B2 (en) * | 2009-06-04 | 2014-02-04 | Cisco Technology, Inc. | Label distribution protocol label filtering |
CN101997762B (zh) * | 2009-08-13 | 2015-08-12 | 中兴通讯股份有限公司 | 利用每个层的层发现信息进行层间路径计算的方法 |
CN102130829B (zh) * | 2010-12-28 | 2013-06-05 | 华为技术有限公司 | 一种lsp的建立方法、装置 |
EP2793921B1 (en) | 2011-12-22 | 2019-04-24 | Children's Medical Center Corporation | Saposin-a derived peptides and uses thereof |
US8995304B2 (en) * | 2012-12-11 | 2015-03-31 | Futurewei Technologies, Inc. | Enhanced upstream label assignment (ULA) mechanism for point to multi-point (P2MP) and/or multi-point to multi-point (MP2MP) facility protection |
US9137146B2 (en) * | 2012-12-11 | 2015-09-15 | Futurewei Technologies, Inc. | Enhanced upstream label assignment (ULA) mechanism for point to multi-point (P2MP) and/or multi-point to multi-point (MP2MP) facility protection |
US9001697B2 (en) * | 2012-12-14 | 2015-04-07 | Western Digital Technologies, Inc. | Methods and devices for replacing and configuring a router in a network |
CN106411543B (zh) * | 2015-07-27 | 2020-06-05 | 中兴通讯股份有限公司 | 一种多段伪线拆除方法和装置 |
CN108924893B (zh) * | 2017-04-26 | 2020-12-25 | 中国移动通信有限公司研究院 | 一种承载释放方法、装置、mme及sae-gw |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005072906A (ja) * | 2003-08-22 | 2005-03-17 | Nippon Telegr & Teleph Corp <Ntt> | マルチキャスト迂回経路設定方法及びラベルスイッチングルータ及びマルチキャスト迂回経路設定プログラム |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3688877B2 (ja) * | 1997-08-08 | 2005-08-31 | 株式会社東芝 | ノード装置及びラベルスイッチングパスのループ検出方法 |
JP3641139B2 (ja) * | 1998-06-30 | 2005-04-20 | 株式会社東芝 | ホップカウント管理方法およびノード装置 |
US6879594B1 (en) * | 1999-06-07 | 2005-04-12 | Nortel Networks Limited | System and method for loop avoidance in multi-protocol label switching |
JP4388667B2 (ja) * | 2000-04-12 | 2009-12-24 | 富士通株式会社 | ラベルスイッチングネットワークにおけるパス設定装置および方法 |
US7281058B1 (en) * | 2002-10-09 | 2007-10-09 | Juniper Networks, Inc. | Delivering and receiving multicast content across a unicast network |
US20050169270A1 (en) * | 2003-03-19 | 2005-08-04 | Ryoichi Mutou | Router, frame forwarding method, and lower layer frame virtual forwarding system |
US7174427B2 (en) * | 2003-12-05 | 2007-02-06 | Intel Corporation | Device and method for handling MPLS labels |
KR100693052B1 (ko) * | 2005-01-14 | 2007-03-12 | 삼성전자주식회사 | Mpls 멀티캐스트의 고속 재경로 설정 장치 및 방법 |
US7570649B2 (en) * | 2005-02-28 | 2009-08-04 | Alcatel Lucent | Forwarding state sharing between multiple traffic paths in a communication network |
US8488616B2 (en) * | 2005-04-05 | 2013-07-16 | Cisco Technology, Inc. | Building multipoint-to-multipoint label switch paths |
US8934486B2 (en) * | 2006-03-16 | 2015-01-13 | Cisco Technology, Inc. | System and method for implementing multicast over a label-switched core network |
-
2006
- 2006-04-27 CN CN2006100760804A patent/CN101047624B/zh active Active
- 2006-11-24 EP EP06817889.6A patent/EP1976198B1/en not_active Not-in-force
- 2006-11-24 WO PCT/CN2006/003163 patent/WO2007124628A1/zh active Application Filing
-
2008
- 2008-07-14 US US12/172,402 patent/US7787457B2/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005072906A (ja) * | 2003-08-22 | 2005-03-17 | Nippon Telegr & Teleph Corp <Ntt> | マルチキャスト迂回経路設定方法及びラベルスイッチングルータ及びマルチキャスト迂回経路設定プログラム |
Non-Patent Citations (3)
Title |
---|
JIANG S. AND LV G.: "Survey of MPLS multicast traffic engineering", IT AGE, no. 1, 15 January 2006 (2006-01-15), pages 69 - 73 * |
LI L., XIONG J., XU H.: "Mergence of MPLS and IP multicast technology", TELECOMMUNICATIONS TECHNOLOGY, no. 3, 31 March 2005 (2005-03-31) * |
See also references of EP1976198A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN101047624A (zh) | 2007-10-03 |
CN101047624B (zh) | 2010-06-09 |
US20090016341A1 (en) | 2009-01-15 |
EP1976198A1 (en) | 2008-10-01 |
EP1976198A4 (en) | 2009-05-20 |
US7787457B2 (en) | 2010-08-31 |
EP1976198B1 (en) | 2013-08-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2007124628A1 (fr) | Procédé d'allocation d'étiquette, de remise d'étiquette, et routeur de commutation d'étiquette | |
US7940698B1 (en) | Point to multi-point label switched paths with label distribution protocol | |
US7233569B1 (en) | Tunnel reroute | |
US6751190B1 (en) | Multihop nested tunnel restoration | |
US8462635B1 (en) | Resource reservation protocol with traffic engineering point to multi-point label switched path hierarchy | |
US7839862B1 (en) | Upstream label assignment for the label distribution protocol | |
US9178811B2 (en) | Method, apparatus and system for generating label forwarding table on ring topology | |
CN1992676B (zh) | 在通信网络中多个业务路径之间共享转发状态的方法和设备 | |
US7742482B1 (en) | Upstream label assignment for the resource reservation protocol with traffic engineering | |
WO2019001350A1 (zh) | 一种生成转发表项的方法、控制器和网络设备 | |
WO2012106986A1 (zh) | 流标签的协商方法、相关装置以及系统 | |
WO2010051699A1 (zh) | 建立标签交换路径的方法、系统及网络节点 | |
WO2010127570A1 (zh) | 一种双向点到多点标签交换路径的建立方法、装置及系统 | |
JP2008172710A (ja) | 予備パス帯域の管理およびパス帯域の変更 | |
US10225091B2 (en) | Method for implementing point-to-multipoint multicast, network node, and system | |
WO2007143929A1 (fr) | Procédé, système et appareil d'affectation d'étiquettes | |
US9137146B2 (en) | Enhanced upstream label assignment (ULA) mechanism for point to multi-point (P2MP) and/or multi-point to multi-point (MP2MP) facility protection | |
WO2014059570A1 (zh) | 建立标签交换路径的方法、设备和系统 | |
JP2010098602A (ja) | 擬似ワイヤの設定方法及び装置 | |
WO2013037260A1 (zh) | 一种标签分配方法及装置 | |
US8995304B2 (en) | Enhanced upstream label assignment (ULA) mechanism for point to multi-point (P2MP) and/or multi-point to multi-point (MP2MP) facility protection | |
WO2022062956A1 (zh) | 一种流量处理方法、装置和网络设备 | |
US8149852B2 (en) | Transmission method, system and router based on a border gateway protocol | |
WO2006011569A1 (ja) | 移動通信アクセスシステム、パケット転送装置及びパス張り替え方法 | |
WO2012041143A1 (zh) | 双向点到多点标签转发路径建立、接枝和剪枝方法及系统 |
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: 06817889 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006817889 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2006817889 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |