WO2013037319A1 - 标签转发路径的带宽资源管理方法、装置和系统 - Google Patents

标签转发路径的带宽资源管理方法、装置和系统 Download PDF

Info

Publication number
WO2013037319A1
WO2013037319A1 PCT/CN2012/081474 CN2012081474W WO2013037319A1 WO 2013037319 A1 WO2013037319 A1 WO 2013037319A1 CN 2012081474 W CN2012081474 W CN 2012081474W WO 2013037319 A1 WO2013037319 A1 WO 2013037319A1
Authority
WO
WIPO (PCT)
Prior art keywords
bandwidth
node
intermediate node
value
bandwidth resource
Prior art date
Application number
PCT/CN2012/081474
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 WO2013037319A1 publication Critical patent/WO2013037319A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H04L45/507—Label distribution
    • 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/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H04L47/724—Admission control; Resource allocation using reservation actions during connection setup at intermediate nodes, e.g. resource reservation protocol [RSVP]

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a bandwidth resource management method, apparatus, and system for an LSP (Label Switched Path). Background technique
  • IPTV Internet Protocol television
  • MP2MP Point to Multiple Point
  • the LS P carries the multicast stream of the I PTV.
  • MLDP Multicast Label Distribution Protocol
  • the P2MP/MP2MP LSP established by MLDP is initiated by the leaf node.
  • the P2MP/MP2MP LSP reaches the ingress node (root node) through the transit node (intermediate node) and terminates at the ingress node.
  • the leaf node can automatically join the established P2MP/MP2MP LSP.
  • P2MP/MP2MP LSP established by MLDP does not have bandwidth resource reservation capability, and all P2MP/MP2MP LSP shared link available bandwidth resources, from group
  • the IPTV traffic from the broadcast source traverses the P2MP/MP2MP LSP and there is no bandwidth resource guarantee.
  • Video quality problems occur when users on the leaf node side receive I PTV traffic because there is no bandwidth guarantee.
  • An embodiment of the present invention provides a bandwidth resource management method, apparatus, and system for an LSP, so as to provide bandwidth resource guarantee for a data flow in an LS P established by MLDP.
  • a bandwidth resource management method for a label forwarding path includes:
  • the intermediate node receives a label distribution protocol message that is sent by the downstream node and carries a bandwidth reservation value, where the label distribution protocol message is used to establish a label forwarding path from the intermediate node to the downstream node;
  • the intermediate node reserves the downlink bandwidth resource according to the bandwidth reservation value, and sends a label distribution protocol message carrying the bandwidth reservation value to the upstream node of the intermediate node.
  • a bandwidth resource management device for a label forwarding path is disposed in a leaf node, and the device specifically includes:
  • a bandwidth reservation value determining module configured to acquire a bandwidth reservation value of the leaf node, where the bandwidth reservation value is a value of a downlink bandwidth resource that the intermediate node needs to reserve for the leaf node; a module, configured to send, to the intermediate node, a label distribution protocol message that carries the bandwidth reservation value, where the label distribution protocol message is used to establish a label forwarding path from the intermediate node to the leaf node;
  • the notification message processing module is configured to: after receiving the label distribution protocol message that is sent by the intermediate node and that does not have the bandwidth resource mismatch or the bandwidth reservation value mismatch information, resend the label distribution that carries the other bandwidth reservation value to the intermediate node.
  • a bandwidth resource management device for a label forwarding path is disposed in an intermediate node, where the device specifically includes:
  • a label distribution protocol message processing module configured to receive a label distribution protocol message that is sent by the downstream node and that carries a bandwidth reservation value, where the label distribution protocol message is used to establish a label forwarding path from the intermediate node to the downstream node;
  • the bandwidth resource reservation module is configured to reserve, according to the label distribution protocol, the bandwidth reservation value carried in the label distribution protocol message received by the % information processing module, that the downstream node reserves the downlink bandwidth resource.
  • a bandwidth resource management device of the label forwarding path is disposed in the root node, and includes: a label distribution protocol message receiving module, configured to receive a label distribution protocol message that is sent by the intermediate node and carries a bandwidth reservation value;
  • a downlink bandwidth resource reservation module configured to use, according to the bandwidth reservation value, a bandwidth resource reserved by the intermediate node for a row.
  • a bandwidth resource management system for a label forwarding path including:
  • the leaf node includes the bandwidth resource management device of the label forwarding path, and an intermediate node, where the intermediate node includes the bandwidth resource management device of the label forwarding path, and receives the carried bandwidth reserved value sent by the leaf node a label distribution protocol message, the label distribution protocol message is used to establish a label forwarding path from the intermediate node to the downstream node, and the bandwidth reserved value carried in the received label distribution protocol message is the leaf
  • the node reserves downlink bandwidth resources
  • the root node includes the bandwidth resource management device of the label forwarding path, the root node receives a label distribution protocol message sent by the intermediate node, and reserves bandwidth for the intermediate node according to the label distribution protocol message. Resources.
  • the embodiment of the present invention implements the LSP established by the MLDP by using the bandwidth reservation value sent by the leaf node according to the leaf node to reserve the bandwidth resource of the leaf node.
  • the bandwidth resource guarantee is provided for the data flow, and the bandwidth guarantee is provided for the I PTV traffic coming from the multicast source to traverse the LS P.
  • FIG. 1 is a leaf node and an intermediate section in an IP/MPLS network according to Embodiment 1 of the present invention; A schematic diagram of an application scenario in which an LSP is set up between the point and the root node through the mLDP.
  • FIG. 2 is a schematic diagram of a method for managing a bandwidth resource of an LSP according to Embodiment 1 of the present invention
  • FIG. 3 is a schematic diagram of a format of a DR-BW TLV according to Embodiment 1 of the present invention
  • a format diagram of a Label Mapping message carrying a DR-BW TLV
  • FIG. 5 is a schematic diagram of an application scenario of establishing an LSP by using an mLDP between a leaf node, an intermediate node, and a root node in an IP/MPLS network according to Embodiment 2 of the present invention
  • FIG. 6 is a flowchart of a bandwidth resource management method for an LSP according to Embodiment 2 of the present invention
  • FIG. 7 is an LDP notification message for an intermediate node to send a bandwidth resource mismatch information to a leaf node according to Embodiment 2 of the present invention
  • FIG. 8 is a schematic diagram of a format of a BW Stat u s cod e according to Embodiment 2 of the present invention
  • FIG. 9 is a schematic diagram of an MP carrying a BW Status code according to Embodiment 2 of the present invention.
  • FIG. 10 is a specific structural diagram of a bandwidth resource management apparatus 10 for an LSP according to Embodiment 3 of the present invention.
  • FIG. 1 is a structural diagram of another bandwidth resource management apparatus 1 for an LSP according to Embodiment 3 of the present invention.
  • FIG. 12 is a schematic structural diagram of another bandwidth resource management apparatus 1 for an LSP according to Embodiment 3 of the present invention.
  • FIG. 13 is a specific structural diagram of another bandwidth resource management apparatus 1 for an LSP according to Embodiment 3 of the present invention.
  • FIG. 14 is a specific structural diagram of a bandwidth resource management apparatus 14 for an LSP according to Embodiment 3 of the present invention.
  • FIG. 15 is a schematic structural diagram of another LSP bandwidth resource management apparatus 14 according to Embodiment 3 of the present invention
  • FIG. 16 is a schematic diagram of an LSP bandwidth resource management system 16 according to Embodiment 3 of the present invention
  • Body structure diagram is a schematic structural diagram of another LSP bandwidth resource management apparatus 14 according to Embodiment 3 of the present invention.
  • FIG. 1 An application scenario of establishing an LSP through a mLDP between a leaf node, a transit node, and an ingress in an IP/MPLS network provided in this embodiment is shown in FIG. 1 .
  • FIG. 1 An application scenario of establishing an LSP through a mLDP between a leaf node, a transit node, and an ingress in an IP/MPLS network provided in this embodiment is shown in FIG. 1 .
  • FIG. 1 An application scenario of establishing an LSP through a mLDP between a leaf node, a transit node, and an ingress in an IP/MPLS network provided in this embodiment is shown in FIG. 1 .
  • FIG. 1 An application scenario of establishing an LSP through a mLDP between a leaf node, a transit node, and an ingress in an IP/MPLS network provided in this embodiment is shown in FIG. 1 .
  • FIG. 1 An application scenario of establishing an LSP through a mLDP between a leaf node,
  • the specific processing flow of the LSP bandwidth resource management method provided in this embodiment is as shown in FIG. 2, and includes:
  • the intermediate node receives the LDP message that is sent by the leaf node and carries the bandwidth reservation value, and the LDP message is used to establish an LSP from the intermediate node to the leaf node.
  • the bandwidth reservation value may be represented by a DR-BW TLV (Downstream Receiver Bandwidth Type-Length-Value, a type length value of the downstream reception bandwidth) as shown in FIG. 3.
  • DR-BW TLV Downstream Receiver Bandwidth Type-Length-Value, a type length value of the downstream reception bandwidth
  • the length of the part, Value represents the value of the bandwidth reserved value carried in the DR-BW TLV.
  • the LDP message may be a Label Mapping message in the LDP protocol.
  • the Label Mapping carrying the DR-BW TLV is provided in this embodiment.
  • the format of the message is shown in Figure 4.
  • the DR-BW TLV is carried in the optional (optional) field in the Label Mapping message.
  • the intermediate node according to the bandwidth reservation value, is a leaf segment, and reserves a downlink bandwidth resource, and sends an LDP message carrying the bandwidth reservation value to an upstream root node of the intermediate node.
  • the intermediate node reserves, for the leaf node, a downlink bandwidth resource whose value is the bandwidth reserved value, And sending, to the upstream node of the intermediate node, an LDP message that carries the bandwidth reservation value; when the available bandwidth resource of the intermediate node is smaller than the bandwidth reservation value, the intermediate node sends the carried to the leaf node. LDP notification message with insufficient bandwidth resources.
  • the intermediate node receives the bandwidth reserved value of the LDP message sent by the leaf node and carries the bandwidth reservation value of 10M.
  • the intermediate node reserves 10M for the leaf node.
  • the downlink bandwidth resource is sent to the root node to send a Label Mapping message with a bandwidth reserved value of 10M.
  • the intermediate node and the root node further include other intermediate nodes, the intermediate node sends the Label Mapping message to the other intermediate nodes, and the other intermediate nodes further The Label Mapping message is gradually passed to the root node.
  • the root node reserves the egress bandwidth of the local node according to the bandwidth reservation value in the received Label Mapping message, and establishes an LSP. Then, the root node imports the multicast data stream from the multicast source into the LSP in a static or dynamic manner, and sends the multicast data stream to the intermediate node. The intermediate node then sends the multicast data stream to the leaf node.
  • the static mode refers to the command line configuration on the root node to import the multicast data stream into the LSP.
  • the dynamic mode refers to dynamically importing the multicast data stream into the LSP when the IP multicast tree is established.
  • the intermediate node receives the bandwidth reservation value of the Label Mapping message sent by the leaf node, the intermediate node sends the bandwidth resource with less than 10M.
  • the LDP notification message the bandwidth resource shortage information may be, for example, carrying a Status code as shown in FIG. MP Status TLV indicates that the Status code value is set to 1.
  • the BW Status code shown in FIG. 8 the BW Type indicates a type field, and the value of the field can be set to a customized value; the Length field indicates the length of the Status code field; and the value of the Status code field is defined.
  • the embodiment of the present invention also provides an MP Status TLV (Multicast Status Type Length Value) carrying the above Status code as shown in FIG. 9. Further, after receiving the LDP notification message carrying the insufficient bandwidth information, the leaf node selects to send an LDP message carrying the other bandwidth reservation value to the intermediate node according to the local configuration, when the other bandwidth reserved value For a special agreed value, such as 0, the intermediate node will provide a bandwidth resource guarantee to the leaf node in a best effort manner; or the leaf node sends a message to the intermediate node to revoke the establishment of the LSP, for example, the message Can be Label Withdraw.
  • MP Status TLV Multicast Status Type Length Value
  • the bandwidth reservation value sent by the leaf node to the intermediate node in the embodiment 21 can be obtained, for example, by:
  • Manner 1 The traffic of the multicast data stream that needs to be distributed to each leaf node received by the root node from the multicast source is statically configured with the bandwidth reserved value on the leaf node, and belongs to each leaf node of the same multicast group.
  • the bandwidth reserved values configured on the same are the same;
  • the root node sends an LDP message carrying the same bandwidth reservation value to each leaf node belonging to the same multicast group according to the traffic of the multicast data stream that is received from the multicast source and needs to be distributed to each leaf node.
  • BGP Border Gateway Protocol
  • the bandwidth reservation value in the LDP message or BGP message can also be carried by the DR-BW TLV.
  • the intermediate node reserves the downlink bandwidth resource according to the bandwidth reservation value sent by the leaf node, thereby realizing the establishment of the bandwidth through the MLDP.
  • the LSP provides bandwidth resource guarantee for the data stream.
  • the bandwidth resource management method of the LSP provided by the embodiment of the present invention further includes:
  • the intermediate node receives the LDP message that is sent by the root node and carries the uplink bandwidth reservation value, and the intermediate node reserves the uplink bandwidth resource according to the uplink bandwidth reservation value, and provides the uplink bandwidth resource to the root node.
  • the leaf node sends an LDP message carrying the uplink bandwidth reservation value.
  • the root node After the root node receives the Label Mapping message that is sent by the intermediate node and carries the bandwidth reservation value, the root node sends a Label carrying the uplink bandwidth reserved value to the intermediate node.
  • the mapping message initiates an LSP establishment process from the intermediate node to the root node.
  • the intermediate node reserves the uplink bandwidth resource for the root node, and sends the uplink bandwidth reservation to the downstream leaf node.
  • the leaf node reserves the uplink bandwidth resource for the intermediate node after receiving the Label Mapping message sent by the intermediate node, and completes the leaf node ⁇ intermediate node ⁇ root The establishment process of the node LSP.
  • the uplink bandwidth reservation value may also be represented by a DR-BW TLV as shown in FIG. 3, where the LDP message may be a Label Mapping message in the LDP protocol, where the uplink bandwidth reservation is performed.
  • the value may be the same as the bandwidth reservation value that is requested by the leaf node to the intermediate node and the root node, and the root node may obtain the bandwidth reservation from the received Label Mapping message sent by the intermediate node. value.
  • the value of the uplink bandwidth reservation may also be other values according to the service type and the requirement, and details are not described herein again.
  • the intermediate node reserves a value for the root node as the uplink bandwidth reserved value.
  • An uplink bandwidth resource and sending, to the leaf node, a Label Mapping message carrying the uplink bandwidth reserved value; when the available bandwidth resource of the intermediate node is smaller than
  • the intermediate node sends an LDP notification message carrying the bandwidth resource shortage information to the leaf node.
  • the leaf node reserves the egress bandwidth of the local node according to the received uplink bandwidth reservation value in the received Label Mapping message, and establishes an LSP. Then, the leaf node imports the multicast data stream received from the multicast source into the LSP in a static manner or a dynamic manner, and sends the LSP to the intermediate node, and the intermediate node sends the multicast data stream to the root node.
  • the static mode refers to the command line configuration on the leaf node to import the multicast data stream into the LSP.
  • the dynamic mode refers to dynamically importing the multicast data stream into the LSP when the IP multicast tree is established.
  • the embodiment of the present invention implements the LSP established by the MLDP by using the bandwidth reservation value sent by the leaf node according to the leaf node to reserve the bandwidth resource of the leaf node.
  • the bandwidth resource guarantee is provided for the data flow, and the bandwidth guarantee is provided for the I PTV traffic coming from the multicast source to traverse the LS P.
  • the root node is an intermediate node
  • the intermediate node reserves the uplink bandwidth for the leaf sub-node, so that the data flow sent by the leaf node and the intermediate node can be guaranteed.
  • FIG. 5 An application scenario of establishing an LSP through the mLDP between a leaf node, a transit node, and an ingress in another IP/MPLS network provided in this embodiment is shown in FIG. 5.
  • the intermediate node is connected to two downstream leaf nodes, respectively, the leaf node 1 and the leaf node 2, and the leaf node 1, the leaf node 2, and the intermediate node and the root node. Belong to the same multicast group. Only the case where the number of leaf nodes connected to the intermediate node is two is shown in FIG. 5, and those skilled in the art can understand that this embodiment can also be applied to the case where there are multiple leaf nodes connected to the intermediate node. Those skilled in the art can also It is understood that this embodiment can also be applied to a scenario in which a plurality of intermediate nodes are included between a leaf node and a root node.
  • the specific processing flow of the LSP bandwidth resource management method provided in this embodiment is as shown in FIG. 6, and includes:
  • the intermediate node receives an LDP message that is sent by the leaf node 1 and carries a bandwidth reservation value, where the LDP message is used to establish an LSP from the intermediate node to the leaf node 1.
  • the bandwidth reservation value may be represented by a DR-BW TLV (Downstream Receiver Bandwidth Type-Length-Value, a type length value of the downstream reception bandwidth) as shown in FIG. 3.
  • DR-BW TLV Downstream Receiver Bandwidth Type-Length-Value, a type length value of the downstream reception bandwidth
  • the length of the part, Value represents the value of the bandwidth reserved value carried in the DR-BW TLV.
  • the LDP message can be a Label Mapping message in the LDP protocol.
  • the format of a Label Mapping message carrying the DR-BW TLV is shown in Figure 4.
  • the DR-BW TLV is carried in the optional (optional) field in the Label Mapping message.
  • the intermediate node reserves a downlink bandwidth resource according to the bandwidth reservation value, and sends an LDP message carrying the bandwidth reservation value to the upstream root node of the intermediate node.
  • the intermediate node reserves, for the leaf node 1, a downlink bandwidth resource whose value is the bandwidth reserved value.
  • the intermediate node sends an LDP notification message carrying the bandwidth resource shortage information to the leaf node 1.
  • the LDP message may be a Label Mapping message
  • the intermediate node receives a bandwidth reservation value of 10M carried by the Label Mapping message sent by the leaf node 1, and the available bandwidth resource of the intermediate node is greater than or equal to 10M.
  • the intermediate node reserves 10 M downlink bandwidth resources for the leaf node 1 and sends a bearer bandwidth reserved value of 1 0 M to the root node.
  • Label Mapping message A person skilled in the art may understand that when the intermediate node and the root node further include other intermediate nodes, the intermediate node sends the Label Mapping message to the other intermediate nodes, and the other intermediate nodes further The Label Mapping message is passed to the root node step by step.
  • the root node reserves the egress bandwidth of the local node according to the bandwidth reservation value in the received Label Mapping message, and establishes an LSP. Then, the root node may import the multicast data stream received from the multicast source into the LSP in a static manner or a dynamic manner, and then send the multicast data stream to the leaf node 1.
  • the static mode refers to the command line configuration on the root node to import the multicast data stream into the LSP.
  • the dynamic mode refers to dynamically importing the multicast data stream into the LSP when the IP multicast tree is established.
  • the intermediate node receives the bandwidth reservation value of the Label Mapping message sent by the leaf node 1 and carries the bandwidth reservation value of 10M, and the available bandwidth resource of the intermediate node is less than 10M, the intermediate node sends insufficient bandwidth resources to the leaf node 1.
  • the bandwidth resource shortage information may be represented by, for example, an MP Status TLV carrying a Status code as shown in FIG. 8, where the BW Status code value is set to 1.
  • the leaf node 1 selects to send an LDP message carrying the other bandwidth reservation value to the intermediate node according to the local configuration.
  • the intermediate node when the other bandwidth reservation value is a special agreed value, such as 0, the intermediate node will provide the bandwidth resource guarantee to the leaf node 1 in a best effort manner; or the leaf node 1 sends the leaf node 1 to the intermediate node.
  • the message may be, for example, Label Withdraw.
  • the bandwidth reservation value sent by the leaf node 1 to the intermediate node in the present embodiment 61 can be obtained, for example, by:
  • Manner 1 The traffic of the multicast data stream that needs to be distributed to each leaf node received by the root node from the multicast source is statically configured with the bandwidth reserved value on the leaf node, and belongs to each leaf node of the same multicast group. The bandwidth reserved values configured on the same are the same;
  • Manner 2 The root node uses the extended bandwidth reservation value according to the traffic received from the multicast source to be distributed to the multicast data stream of each leaf node, and extends the LDP message or BGP (Border Gateway Protocol). The message is sent to each leaf node belonging to the same multicast group. In actual applications, the bandwidth reservation value in the LDP message or the BGP message may also be carried by the DR-BW TLV.
  • the intermediate node receives the LDP message that carries the bandwidth reservation value sent by the leaf node 2, and reserves the downlink bandwidth resource according to the bandwidth reservation value.
  • the LDP message may be, for example, a Label Mapping message. Because the intermediate node reserves the downlink bandwidth resources reserved for all the leaf nodes belonging to the same multicast group, the intermediate node determines the bandwidth reservation value sent by the leaf node 2 and sends the bandwidth reservation value to the leaf node 1 Whether the reserved downlink bandwidth resources are consistent, if yes, the intermediate node further reserves the downlink bandwidth resource for the leaf node 2 according to the bandwidth reservation value, and the leaf node 2 successfully joins the multicast group; otherwise The intermediate node sends an LDP notification message carrying the bandwidth resource mismatch information to the leaf node 2.
  • the information that the bandwidth resource does not match may include a downlink bandwidth value that the intermediate node has reserved for other leaf nodes.
  • the schematic diagram of the LDP notification message that the intermediate node sends the bandwidth resource mismatch information to the leaf node 2 is shown in FIG. 7.
  • the intermediate node sends the Label Mapping message according to the received leaf node 1.
  • 10M bandwidth resources have been reserved for leaf node 1.
  • the intermediate node returns an LDP notification message carrying the reserved bandwidth value mismatch information to the leaf node 2, for example, the bandwidth resource mismatch information may be It is represented by the MP Status TLV carrying the Status code as shown in Figure 8, where the BW Status code value is set to 2.
  • the intermediate node After receiving the Label Mapping message carrying the bandwidth reservation value sent by the other leaf node (in this embodiment, the leaf node 2) that belongs to the same multicast group as the leaf node 1, the intermediate node is based on the carried
  • the bandwidth reserved value is the other leaf section, and after the bandwidth resource is reserved,
  • the Label Mapping message carrying the bandwidth reservation value may be sent to the root node, or the Label Mapping message carrying the bandwidth reservation value may not be sent to the root node.
  • the root node then forwards the received multicast data stream to the LSP in a static or dynamic manner, and sends the multicast data stream to the leaf node.
  • the static mode refers to the command line configuration on the root node to import the multicast data stream into the LSP.
  • the dynamic mode refers to dynamically importing the multicast data stream into the LSP when the IP multicast tree is established.
  • the bandwidth reservation resource is reserved by the intermediate node according to the bandwidth reservation value sent by the leaf node, and the root node is based on the bandwidth sent by the intermediate node.
  • the value of the intermediate node is reserved for the bandwidth resource, which provides bandwidth guarantee for the data stream in the LSP established by the MLDP, and provides bandwidth guarantee for the I PTV traffic coming from the multicast source to traverse the LS P.
  • the method for managing the bandwidth resource of the LSP provided by the embodiment of the present invention further includes:
  • the leaf node 1 when the intermediate node carries the bandwidth reservation value carried in the LDP message sent by the leaf node 1, the leaf node 1 reserves the downlink bandwidth resource successfully, and then sends the downlink node resource to the intermediate node.
  • the upstream root node sends an LDP message carrying the bandwidth reserved value.
  • the root node After receiving the LDP message carrying the bandwidth reservation value, the root node triggers the establishment process of the LSP of the leaf node ⁇ the intermediate node ⁇ the root node, and sends an LDP message carrying the uplink bandwidth reservation value to the intermediate node.
  • the value of the uplink bandwidth reservation value BWup carried in the LDP message sent by the root node to the intermediate node is between 62 and the bandwidth pre- carried in the LDP message sent by the intermediate node to the root node.
  • N 1, that is, the uplink bandwidth reserved value carried in the LDP message sent by the root node to the intermediate node is equal to 62, and the intermediate node is to the root node.
  • N ⁇ this case is equivalent to the upstream bandwidth reserved value carried in the LDP message sent by the root node to the intermediate node, and the intermediate node reserves the bandwidth reserved for all leaf nodes belonging to the same multicast group.
  • the sum of resources is the sum of all downstream bandwidth resources.
  • the uplink bandwidth reservation value that the root node requests from the intermediate node may also be represented by the DR-BW TLV as shown in FIG. 3, and the LDP message used may be Label Mapping in the LDP protocol. Mapping) messages, which are not described here.
  • the intermediate node reserves the value for the root node as the The uplink bandwidth resource of the uplink bandwidth reservation value, and sends an LDP message carrying the uplink bandwidth reservation value to the leaf node 1 and the leaf node 2.
  • the uplink bandwidth reserved value carried in the LDP message sent by the intermediate node to the leaf node 1 and the bandwidth pre-loaded in the LDP message sent by the leaf node 1 received by the intermediate node in the step 61 in this embodiment The value of the LDP message carried in the LDP message sent by the intermediate node to the leaf node 2 is carried in the LDP message sent by the leaf node 2 received by the intermediate node in step 63 of this embodiment.
  • the bandwidth reservation value is the same.
  • the intermediate node sends an LDP notification message carrying the bandwidth resource shortage information to the root node.
  • the manner in which the intermediate node sends the DL P notification message carrying the bandwidth resource shortage information to the root node is the same as that in the foregoing steps, and details are not described herein again.
  • the intermediate node sends an LDP message carrying a bandwidth reserved value to the leaf node 1 and the leaf node 2.
  • the LDP message carrying the bandwidth reservation value is sent to the leaf node 1 and the leaf node 2, and the LDP message may be, for example, Label Mapping.
  • the intermediate node is The uplink bandwidth reservation value carried in the LDP message sent by the leaf node 1 is the same as the bandwidth reservation value carried in the LDP message sent by the leaf node 1 received by the intermediate node in the step 61 in the embodiment.
  • the uplink bandwidth reservation value carried in the LDP message sent by the node to the leaf node 2 is the same as the bandwidth reservation value carried in the LDP message sent by the leaf node 2 received by the intermediate node in step 63 of this embodiment.
  • the leaf node 1 and the leaf node 2 After receiving the Label Mapping message sent by the leaf node and carrying the uplink bandwidth reservation value, the leaf node 1 and the leaf node 2 reserve the egress bandwidth of the node according to the uplink bandwidth reservation value in the Label Mapping message, and establish an LSP. . Then, the leaf node 1 and the leaf node 2 import the multicast data stream received from the multicast source into the LSP in a static manner or a dynamic manner, and send it to the intermediate node, and the intermediate node sends the multicast data stream to the node. .
  • the static mode refers to the command line configuration on the leaf node to import the multicast data stream into the LSP.
  • the dynamic mode refers to dynamically importing the multicast data stream into the LSP when the IP multicast tree is established.
  • the embodiment provides an LSP bandwidth resource management device 10, and the device is disposed in a leaf node.
  • the specific structure is as shown in FIG. 10.
  • the device 10 specifically includes:
  • the bandwidth reservation value determining module 101 is configured to obtain a bandwidth reservation value of the leaf node, where the bandwidth reservation value is a value of a downlink bandwidth resource reserved by the intermediate node to the leaf node.
  • the manner in which the leaf node obtains the foregoing bandwidth reservation value includes, but is not limited to, the following two types: Mode 1: According to the root node, the traffic of the multicast data stream that needs to be distributed to each leaf node from the multicast source is in the leaf node.
  • the bandwidth reservation value is statically configured, and the bandwidth reservation values configured on each leaf node belonging to the same multicast group are the same;
  • Mode 2 The root node sends an LDP message or a BGP message carrying the same bandwidth reservation value to each leaf node belonging to the same multicast group according to the received traffic of the multicast data stream that needs to be distributed to each leaf node.
  • the bandwidth reservation value in the LDP message or the BGP message may also be carried by the DR-BW TLV.
  • the bandwidth reservation value sending module 102 is configured to send, to the intermediate node, an LDP message that carries the bandwidth reservation value, where the LDP message is used to establish an LSP from the intermediate node to the leaf node.
  • the foregoing bandwidth reservation value may be represented by a DR-BW TLV (Downstream Receiver Bandwidth Type-Length-Value, a type length value of a downstream reception bandwidth) as shown in FIG. 3.
  • the length of the part, Value represents the value of the bandwidth reserved value carried in the DR-BW TLV.
  • the LDP message can be a Label Mapping message in the LDP protocol.
  • the format of a Label Mapping message carrying the DR-BW TLV is shown in Figure 4.
  • the above DR-BW TLV is carried in the optional (optional) field in the Label Mapping message.
  • the bandwidth resource management apparatus 10 of the LS P may further include: a notification message processing module 103, configured to receive, by the intermediate node, an LDP that carries insufficient bandwidth resources or bandwidth reservation value mismatch information After the message, the LDP message carrying the other bandwidth reservation value is resent to the intermediate node.
  • the other bandwidth reservation value is a special agreed value, such as 0, the intermediate node will take the best effort to the leaf.
  • the node provides a bandwidth resource guarantee; or sends a cancellation, packet, to the intermediate node to cancel the establishment of the LSP.
  • the bandwidth resource management apparatus 10 of the LS P may further include: an uplink bandwidth reservation module 104, configured to: after receiving an label mapping message that is sent by the intermediate node and carrying an uplink bandwidth reservation value, The remaining bandwidth resource whose value is the reserved value of the uplink bandwidth.
  • an uplink bandwidth reservation module 104 configured to: after receiving an label mapping message that is sent by the intermediate node and carrying an uplink bandwidth reservation value, The remaining bandwidth resource whose value is the reserved value of the uplink bandwidth.
  • MP2MP LSP multi-point to multi-point LSP
  • each leaf node There are two-way LSPs in the LSP.
  • the LSP and leaf of the root node ⁇ intermediate node ⁇ leaf node need to be established.
  • the child node ⁇ intermediate node ⁇ LS P of the root node in addition to receiving the downlink data stream, each leaf node also sends an uplink data stream to the intermediate node.
  • the uplink bandwidth reservation module 104 reserves an uplink bandwidth resource whose value is the uplink bandwidth reserved value.
  • the bandwidth resource management apparatus 10 of the LSP may include only the bandwidth reservation value determining module 101 and the bandwidth reservation value sending module 102, and may also determine the bandwidth reserved value.
  • the module 101 and the bandwidth reservation value sending module 102 further include the foregoing notification message processing module 103 and the uplink bandwidth reservation module 104, or include the bandwidth reservation value determining module 101 and the bandwidth reserved value transmission.
  • the module 102 further includes any one of the foregoing notification message processing module 103 and the upstream bandwidth reservation module 104.
  • the embodiment further provides an LSP bandwidth resource management device 1 1 , which is disposed in an intermediate node, and the specific structure thereof is as shown in FIG.
  • the L D P message processing module 1 1 1 is configured to receive an LDP message that is sent by the downstream node and that carries a bandwidth reservation value, where the LDP message is used to establish an LSP from the intermediate node to the downstream node.
  • the bandwidth resource reservation module 1 12 is configured to reserve, according to the bandwidth reservation value carried in the LDP message received by the L D P message processing module 1 1 1 , the downlink bandwidth resource reserved by the downstream node.
  • the bandwidth resource reservation module 1 12 in the bandwidth resource management apparatus 1 of the LSP may include:
  • the available resource processing module 1 121 is configured to determine whether the value of the available bandwidth resource of the intermediate node is greater than or equal to the bandwidth reserved value carried in the LDP message received by the LDP message processing module 111, and if yes, The downstream node reserves a downlink bandwidth resource whose value is the bandwidth reserved value; otherwise, sends a bandwidth resource shortage message to the LDP notification message sending module 1122.
  • the LDP notification message sending module 1 122 is configured to send an LDP notification message carrying insufficient bandwidth resource information to the downstream node when receiving the bandwidth resource shortage message.
  • the above bandwidth resources are not
  • the foot information can be represented by the MP Status TLV carrying the above BW Status code (value 1) as described in the first embodiment.
  • the bandwidth resource reservation module 112 may further include: a resource matching processing module 1123, configured to determine, in the LDP message received by the LDP message processing module 112 The bandwidth reservation value is consistent with the downlink bandwidth resource that the intermediate node has reserved for the other downstream nodes. If yes, the bandwidth reserved value carried in the LDP message received by the LDP message processing module 112 is The downstream node reserves the downlink bandwidth resource; otherwise, sends a bandwidth resource mismatch message to the LDP notification message sending module 1122.
  • a resource matching processing module 1123 configured to determine, in the LDP message received by the LDP message processing module 112 The bandwidth reservation value is consistent with the downlink bandwidth resource that the intermediate node has reserved for the other downstream nodes. If yes, the bandwidth reserved value carried in the LDP message received by the LDP message processing module 112 is The downstream node reserves the downlink bandwidth resource; otherwise, sends a bandwidth resource mismatch message to the LDP notification message sending module 1122.
  • the LDP notification message sending module 1 123 is further configured to: when receiving the bandwidth resource mismatch message, send an LDP notification message that carries the bandwidth resource mismatch information to the downstream node.
  • the bandwidth resource mismatch information may be represented by the MP Status TLV carrying the foregoing S t a t s code (value 2) as described in the first embodiment.
  • the bandwidth resource management apparatus 1 of the LSP may further include: a downlink bandwidth reservation value sending module 1 1 3, configured to send, to the upstream node of the intermediate node, the LDP that carries the bandwidth reserved value. Message.
  • a downlink bandwidth reservation value sending module 1 1 3 configured to send, to the upstream node of the intermediate node, the LDP that carries the bandwidth reserved value.
  • the upstream node is a root node. It will be understood by those skilled in the art that when the intermediate node and the root node further include other intermediate nodes, the intermediate node will send the LDP message to the other intermediate nodes, and the other intermediate nodes will further The LDP message is gradually passed to the root node.
  • the bandwidth resource reservation module 12 provides the first downstream node of each downstream node belonging to the same multicast group. After the bandwidth resource is reserved, the downlink bandwidth reservation value sending module 112 sends an LDP message carrying the bandwidth reservation value to the upstream node of the intermediate node, where the intermediate node belongs to the same multicast group.
  • the LDP message is not sent to the upstream node of the intermediate node; Or after the bandwidth resource reservation module 112 reserves the downlink bandwidth resource with the value of the bandwidth reservation value for each downstream node that belongs to the same multicast group, the downlink bandwidth reservation value sending module The LDP message carrying the bandwidth reservation value is sent to the upstream node of the intermediate node.
  • the LDP message processing module 112 may also be configured to receive an LDP message that is sent by an upstream node and that carries an uplink bandwidth reservation value, where the uplink bandwidth is carried.
  • the reserved value LDP message is used to establish an LSP from the intermediate node to the upstream node.
  • the bandwidth resource reservation module 112 may further include:
  • the uplink bandwidth resource reservation module 1 124 is configured to: when the LDP message processing module 112 receives the LDP message that is sent by the upstream node and carries the uplink bandwidth reservation value, the uplink bandwidth reservation value is the upstream The node reserves uplink bandwidth resources.
  • the uplink bandwidth reservation value sending module 1 14 is configured to: the uplink bandwidth resource reservation module 1 124, according to the uplink bandwidth reservation value, that the upstream node reserves the uplink bandwidth resource successfully, and belongs to the same multicast group.
  • Each downstream node sends an LDP message carrying an uplink bandwidth reservation value.
  • the uplink bandwidth reservation value carried by the LDP message sent by the upstream bandwidth reservation value sending module 114 to each downstream node that belongs to the same multicast group may be received by the LDP message processing module 111.
  • the value of the uplink bandwidth reserved in the LDP message sent by the upstream node may also be other uplink bandwidth reservation values configured according to different service types and network topology scenarios.
  • the embodiment further provides an LSP bandwidth resource management device 14 , which is disposed in a root node, and has a specific structure as shown in FIG. 14 .
  • the device 14 specifically includes:
  • the L D P message receiving module 141 is configured to receive an LDP message that is sent by the intermediate node and carries a bandwidth reserved value
  • the downlink bandwidth resource reservation module 142 is configured to reserve downlink bandwidth resources according to the bandwidth reservation value.
  • the device 14 may further include:
  • the uplink bandwidth reservation value sending module 143 is configured to send, to the intermediate node, an LDP message that carries an uplink bandwidth reservation value.
  • the value of the uplink bandwidth reservation value BWup carried in the LDP message sent by the uplink bandwidth reservation value sending module 143 to the intermediate node is carried in the LDP message sent by the intermediate node to the root node.
  • the bandwidth reserved value is 1/N of BWdw and N times of BWdw, that is, BWdw/N ⁇ BWup ⁇ BWdw . N , where N is the number of leaf nodes.
  • the embodiment further provides an LSP bandwidth resource management system 16, which has a specific structure as shown in FIG. 16, and includes:
  • a leaf node 161 which includes the bandwidth resource management device 10 of the LSP, configured to acquire a bandwidth reservation value of the leaf node, where the bandwidth reservation value is a downlink bandwidth that the intermediate node needs to reserve for the leaf node.
  • the value of the resource; the LDP message carrying the bandwidth reservation value is sent to the intermediate node, and the LDP message is used to establish an LSP from the intermediate node to the leaf node.
  • the intermediate node 162, the bandwidth resource management device 1 1 of the LSP is configured to receive an LDP message that is sent by the leaf node and that carries a bandwidth reservation value, and the bandwidth reservation value carried in the LDP message is
  • the leaf node reserves the downlink bandwidth resource, and sends an LDP message carrying the bandwidth reservation value to the root node, where the LDP message is used to establish an LSP from the intermediate node to the root node.
  • the root node 163, the bandwidth resource management device 14 of the LSP is configured to receive an LDP message that carries the bandwidth reservation value sent by the intermediate node 162, and reserve the downlink according to the bandwidth reservation value. Bandwidth resources.
  • the bandwidth resource management system 16 of the LS P provided by the embodiment is a bandwidth resource management method corresponding to the method LSP in the embodiment 3 and the bandwidth resource management of the LSP of the bandwidth resource management device of the LSP.
  • the system, the bandwidth resource management device of the LSP included therein includes all the functions of the bandwidth resource management device of the LSP in Embodiment 3, and includes The method for performing the bandwidth resource management of the LSP between the leaf node 161, the intermediate node 162, and the root node 163 corresponds to the bandwidth resource management method of the LSP in the embodiments 1 and 2, and details are not described herein again.
  • the intermediate node reserves the bandwidth resource according to the bandwidth reservation value sent by the leaf node according to the leaf node, and the root node reserves the bandwidth according to the bandwidth reservation value sent by the intermediate node.
  • the resources are used to provide bandwidth guarantee for the data stream in the LSP established by the MLDP, and the bandwidth guarantee is provided for the I PTV traffic coming from the multicast source to traverse the LS P.
  • the root node is an intermediate node
  • the intermediate node reserves the uplink bandwidth for the leaf sub-node, so that the data flow sent by the leaf node and the intermediate node can be guaranteed.
  • the intermediate node can allocate the same bandwidth resource to each leaf node belonging to the same multicast source.
  • the embodiments of the present invention may reserve corresponding uplink and downlink bandwidth resources for the leaf node and the intermediate node for the P2MP LSP and the MP2MP LSP respectively.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

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

Abstract

本发明实施例提供了一种LSP（Label Switched Path，标签转发路径）的带宽资源管理方法、装置和系统。该方法主要包括：中间节点接收下游节点发送的携带带宽预留值的LDP（Label Distribution Protocol，组播标签分发协议）消息；所述中间节点根据所述带宽预留值为所述下游节点预留下行的带宽资源，向所述中间节点的上游节点发送携带所述带宽预留值的标签分发协议消息。利用本发明实施例，实现了在通过MLDP （Multicast Label Distribution Protocol，组播标签分发协议）建立的LSP中对数据流提供带宽资源保证，为从组播源发送的IPTV流量穿越LSP提供了带宽保证。

Description

标签转发路径的带宽资源管理方法、 装置和系统 技术领域
本发明涉及通信技术领域， 尤其涉及一种 LSP ( Label Switched Path , 标签转发路径） 的带宽资源管理方法、 装置和系统。 背景技术
随着 IPTV ( Internet Protocol television , 互联网协议电视） 的广泛使 用， 在 IP ( Internet Protocol , 互联网协议 /MPLS ( Multi Protocol Label Switching , 多协议标签交换） 骨干网上通常使用 P2MP ( Point to Multiple Point, 点到多点）/MP2MP ( Multiple Point to Multiple Point, 多点到多点） LS P来承载 I PTV的组播流。
可以使用 MLDP ( Multicast Label Distribution Protocol , 组播标签分 发协议）来建立 P2MP/MP2MP LSP。通过 MLDP建立的 P2MP/MP2MP LSP 由叶子节点发起建立，上述 P2MP/MP2MP LSP通过 transit节点（中间节点） 到达 ingress节点 （根节点） ， 在 ingress节点终结。 同时叶子节点可以自动 加入已经建立的 P2MP/MP2MP LSP。
在实现本发明过程中，发明人发现上述现有技术中至少存在如下问题： 通过 MLDP建立的 P2MP/MP2MP LSP不具有带宽资源预留能力， 所有 P2MP/MP2MP LSP共享链路可用带宽资源， 从组播源过来的 IPTV流量穿 越 P2MP/MP2MP LSP也没有带宽资源保证。 叶子节点侧的用户接收到 I PTV流量后由于没有带宽保证， 会出现视频质量问题。 发明内容
本发明的实施例提供了一种 L S P的带宽资源管理方法、 装置和系统， 以实现在通过 M L D P建立的 LS P中对数据流提供带宽资源保证。 一种标签转发路径的带宽资源管理方法， 包括：
中间节点接收到下游节点发送的携带带宽预留值的标签分发协议消 息， 所述标签分发协议消息用于建立从所述中间节点到所述下游节点的标 签转发路径；
所述中间节点根据所述带宽预留值为所述下游节点预留下行的带宽资 源， 向所述中间节点的上游节点发送携带所述带宽预留值的标签分发协议 消息。
一种标签转发路径的带宽资源管理装置， 设置在叶子节点中， 所述装 置具体包括：
带宽预留值确定模块， 用于获取所述叶子节点的带宽预留值， 所述带 宽预留值为中间节点需要给所述叶子节点预留的下行的带宽资源的数值； 带宽预留值发送模块， 用于向中间节点发送携带所述带宽预留值的标 签分发协议消息， 所述标签分发协议消息用于建立从所述中间节点到所述 叶子节点的标签转发路径；
通知消息处理模块， 用于接收到所述中间节点发送的携带带宽资源不 足或者带宽预留值不匹配信息的标签分发协议消息后， 向所述中间节点重 新发送携带其它带宽预留值的标签分发协议消息或者向所述中间节点发送 撤销建立所述标签转发路径的消息。
一种标签转发路径的带宽资源管理装置， 设置在中间节点中， 所述装 置具体包括：
标签分发协议消息处理模块， 用于接收下游节点发送的携带带宽预留 值的标签分发协议消息， 所述标签分发协议消息用于建立从所述中间节点 到所述下游节点的标签转发路径；
带宽资源预留模块， 用于根据所述标签分发协议、 %息处理模块所接收 到的标签分发协议消息中携带的带宽预留值为所述下游节点预留下行的带 宽资源。 一种标签转发路径的带宽资源管理装置， 设置在根节点中， 包括： 标签分发协议消息接收模块， 用于接收到中间节点发送的携带带宽预 留值的标签分发协议消息；
下行带宽资源预留模块， 用于根据所述带宽预留值为所述中间节点预 留下行的带宽资源。
一种标签转发路径的带宽资源管理系统， 包括：
叶子节点，该叶子节点包括所述的标签转发路径的带宽资源管理装置； 中间节点，该中间节点包括所述的标签转发路径的带宽资源管理装置， 接收所述叶子节点发送的携带带宽预留值的标签分发协议消息， 所述标签 分发协议消息用于建立从所述中间节点到所述下游节点的标签转发路径， 并根据接收到的标签分发协议消息中携带的带宽预留值为所述叶子节点预 留下行的带宽资源； 和
根节点， 该根节点包括所述的标签转发路径的带宽资源管理装置， 所 述根节点接收所述中间节点发送的标签分发协议消息并根据所述标签分发 协议消息为所述中间节点预留带宽资源。
由上述本发明的实施例提供的技术方案可以看出， 本发明实施例通过 中间节点根据叶子节点发送的带宽预留值为所述叶子节点预留带宽资源， 从而实现了在通过 MLDP建立的 LSP中对数据流提供带宽资源保证，为从组 播源过来的 I PTV流量穿越 LS P提供了带宽保证。 附图说明
为了更清楚地说明本发明实施例的技术方案， 下面将对实施例描述中 所需要使用的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅是 本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳 动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明实施例一提供的一种 I P / M P L S网络中的叶子节点、 中间节 点和根节点之间通过 mLDP建立 LSP的应用场景示意图；
图 2为本发明实施例一提供的一种 LSP的带宽资源管理方法的示意图； 图 3为本发明实施例一提供的一种 DR-BW TLV的格式示意图； 图 4为本发明实施例一提供的一种携带 DR-BW TLV的 Label Mapping 消息的格式示意图；
图 5为本发明实施例二提供的一种 IP/MPLS网络中的叶子节点、 中间节 点和根节点之间通过 mLDP建立 LSP的应用场景示意图；
图 6为本发明实施例二提供的一种 L S P的带宽资源管理方法的流程图； 图 7为本发明实施例二提供的一种中间节点向叶子节点发送携带带宽 资源不匹配信息的 LDP通知消息的示意图；
图 8为本发明实施例二提供的一种 BW Stat u s cod e的格式示意图； 图 9为本发明实施例二提供的一种携带了 BW Status code 的 MP
Status TLV的格式示意图；
图 1 0为本发明实施例三提供的一种 LSP的带宽资源管理装置 1 0的具体 结构图；
图 1 1为本发明实施例三提供的另一种 LSP的带宽资源管理装置 1 1的具 体结构图；
图 12为本发明实施例三提供的再一种 LSP的带宽资源管理装置 1 1的具 体结构图；
图 1 3为本发明实施例三提供的又一种 LSP的带宽资源管理装置 1 1的具 体结构图；
图 14为本发明实施例三提供的一种 LSP的带宽资源管理装置 14的具体 结构图；
图 1 5为本发明实施例三提供的另一种 LSP的带宽资源管理装置 14的具 体结构图； 图 16为本发明实施例三提供的一种 L S P的带宽资源管理系统 16的具 体结构图。
具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚， 下面将结合本 发明实施例中的附图， 对本发明实施例中的技术方案进行清楚、 完整地描 述， 显然， 所描述的实施例是本发明一部分实施例， 而不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有作出创造性劳动前提 下所获得的所有其他实施例， 都属于本发明保护的范围。
为便于对本发明实施例的理解， 下面将结合附图以几个具体实施例为 实施例一
本实施例提供的一种 IP/MPLS网络中叶子节点 （ leaf ) 、 中间节点 ( transit ) 和根节点 （ingress ) 之间通过 mLDP建立 LSP的应用场景如图 1 所示。图 1的场景中只列出了叶子节点和根节点之间只包括一个中间节点的 情况， 本领域的技术人员可以理解， 该实施例同样可以应用在叶子节点和 根节点之间包括多个中间节点的场景。
本实施例提供的一种 LSP的带宽资源管理方法的具体处理流程如图 2 所示， 包括：
21、 中间节点接收到叶子节点发送的携带带宽预留值的 LDP消息， 所 述 LDP消息用于建立从所述中间节点到所述叶子节点的 LSP。
举例来说， 上述带宽预留值可以通过如图 3所示的 DR-BW TLV ( Downstream Receiver Bandwidth Type-Length-Value,下游接收带宽的 类型长度值） 来表示， 在图 3中， Length表示 Value部分的长度， Value表 示 DR-BW TLV中携带的带宽预留值的值。
举例来说， 上述 LDP消息可以为 LDP协议中的 Label Mapping (标签映 射） 消息， 该实施例提供的一种携带了上述 DR-BW TLV的 Label Mapping 消息的格式如图 4所示。 在图 4中， 在 Label Mapping消息中的 optional (可 选） 字段中携带上述 DR-BW TLV。
22、 所述中间节点根据所述带宽预留值为所述叶子节, 预留下行的带 宽资源， 向所述中间节点的上游根节点发送携带所述带宽预留值的 LDP消 息。
具体地， 当所述中间节点的可用带宽资源的数值大于或者等于所述带 宽预留值时， 所述中间节点给所述叶子节点预留数值为所述带宽预留值的 下行的带宽资源， 并向所述中间节点的上游节点发送携带所述带宽预留值 的 LDP消息； 当所述中间节点的可用带宽资源小于所述带宽预留值时， 所 述中间节点向所述叶子节点发送携带带宽资源不足信息的 LDP通知消息。
举例来说， 中间节点接收到叶子节点发送的 LDP消息携带的带宽预留 值为 10M , 这时中间节点的可用带宽资源大于或者等于 10M , 则所述中间 节点为所述叶子节点预留 10M的下行的带宽资源， 并向所述根节点发送携 带带宽预留值为 1 0M的 Label Mapping消息。 本领域技术人员可以理解， 当 所述中间节点和根节点之间进一步包括其它中间节点时， 所述中间节点将 向所述其他中间节点发送上述 Label Mapping消息，所述其他中间节点再将 所述 Label Mapping消息逐步传递到根节点。 根节点根据收到的所述 Label Mapping消息中的带宽预留值预留本节点出口带宽， 并建立 LSP。 然后， 根 节点将从组播源接收到的组播数据流釆用静态方式或动态方式导入上述 LSP , 并下发给中间节点， 中间节点再将组播数据流下发给叶子节点。 其 中， 静态方式指在根节点上用命令行配置， 把组播数据流导入上述 LSP; 动态方式指在建立 IP组播树时， 就动态的将组播数据流导入上述 LSP。
举例来说，中间节点接收到叶子节点发送的 Label Mapping消息携带的 带宽预留值为 1 0M , 而这时中间节点的可用带宽资源小于 10M , 则中间节 点向叶子节点发送携带带宽资源不足信息的 LDP通知消息， 上述带宽资源 不足信息例如可以釆用携带如图 8所示的 Status code (带宽状态编码） 的 MP Status TLV来表示， 其中的 Status code值设置为 1。 图 8所示的 BW Status code中 BW Type表示类型字段， 该字段的值可以设置为自定义的 值； Length字段表示 Status code字段的长度； 定义 Status code字段的值为
1表示带宽资源不足； Status code字段的值为 2表示带宽预留值不匹配。 本 发明实施例同时还提供一种如图 9所示的携带上述 Status code 的 MP Status TLV (组播状态类型长度值） 。 进一步地， 上述叶子节点接收到所 述携带带宽资源不足信息的 LDP通知消息后， 根据本地配置情况， 选择向 所述中间节点发送携带其它带宽预留值的 LDP消息 , 当该其它带宽预留值 为某特殊约定值， 比如 0时， 中间节点将釆取尽力而为的方式向上述叶子节 点提供带宽资源保证； 或者上述叶子节点向所述中间节点发送撤销建立所 述 LSP的消息， 该消息例如可以为 Label Withdraw (标签撤销消息） 。
本实施例 21中叶子节点发送给中间节点的带宽预留值例如可以通过以 下方式得到：
方式 1：根据所述根节点从组播源接收到的需要分发给各个叶子节点的 组播数据流的流量在叶子节点上静态配置带宽预留值， 并且归属于同一组 播组的各个叶子节点上配置的带宽预留值是相同的；
方式 2：根节点根据从组播源接收到的需要分发给各个叶子节点的组播 数据流的流量， 向归属于同一组播组的各个叶子节点发送携带相同的带宽 预留值的 LDP消息或者 BGP ( Border Gateway Protocol , 边界网关协议） 消息。 在实际应用中， 上述 LDP消息或者 BGP消息中的带宽预留值也可以 通过上述 DR-BW TLV来携带。
由上述本发明的实施例提供的技术方案可以看出， 本发明实施例通过 中间节点根据叶子节点发送的带宽预留值为所述节点预留下行的带宽资 源， 从而实现了在通过 MLDP建立的 LSP中对数据流提供带宽资源保证。
以上描述的是建立 Ρ2ΜΡ LSP的过程， 如果需要建立 ΜΡ2ΜΡ LSP , 除 了建立上述根节点→中间节点→叶子节点的 LSP之外， 还需要建立叶子节 点→中间节点→根节点的 LSP , 也就是需要建立双向的 LSP。 对于需要建 立 MP2MP LSP的场景，本发明实施例的提供的 LSP的带宽资源管理方法进 一步包括：
23、 所述中间节点接收所述根节点发送的携带上行带宽预留值的 LDP 消息， 所述中间节点根据所述上行带宽预留值为所述根节点预留上行的带 宽资源 , 并向所述叶子节点发送携带所述上行带宽预留值的 LDP消息。
例如，对于需要建立 MP2MP LSP的场景， 在根节点接收到中间节点发 送的携带所述带宽预留值的 Label Mapping消息后，所述根节点向所述中间 节点发送携带上行带宽预留值的 Label Mapping消息，发起从中间节点到根 节点的 LSP建立过程。 所述中间节点收到根节点发送的携带所述上行带宽 预留值的 Label Mapping消息之后， 为所述根节点预留上行的带宽资源， 并 向下游的叶子节点发送携带所述上行带宽预留值的 Label Mapping消息，所 述叶子节点收到中间节点发送的携带所述上行带宽预留值的 Label Mapping消息之后， 为所述中间节点预留上行的带宽资源， 完成叶子节点 →中间节点→根节点 LSP的建立过程。
具体地， 所述上行带宽预留值同样可以通过如图 3所示的 DR-BW TLV 来表示， 上述 LDP消息可以为 LDP协议中的 Label Mapping (标签映射） 消 息， 其中所述上行带宽预留值可以与所述叶子节点向所述中间节点和所述 根节点请求的带宽预留值相同， 所述根节点可以从接收到的所述中间节点 发送的 Label Mapping消息中得到所述带宽预留值。所述上行带宽预留值也 可以根据业务类型和需求的不同为其他的数值， 这里不再赘述。
具体地， 当所述中间节点的可用带宽资源的数值大于或者等于所述根 节点请求的上行带宽预留值时， 所述中间节点给所述根节点预留数值为所 述上行带宽预留值的上行带宽资源， 并向所述叶子节点发送携带所述上行 带宽预留值的 Label Mapping消息； 当所述中间节点的可用带宽资源小于所 述上行带宽预留值时， 所述中间节点向所述叶子节点发送携带带宽资源不 足信息的 LDP通知消息。
叶子节点根据收到的所述 Label Mapping消息中的上述上行带宽预留 值预留本节点出口带宽， 并建立 LSP。 然后， 叶子节点将从组播源接收到 的组播数据流釆用静态方式或动态方式导入上述 LSP , 并发送给中间节点， 中间节点再将组播数据流发送给根节点。 其中， 静态方式指在叶子节点上 用命令行配置， 把组播数据流导入上述 LSP; 动态方式指在建立 IP组播树 时， 就动态的将组播数据流导入上述 LSP。
本领域技术可以理解， 上述建立叶子节点→中间节点→根节点的 LSP 的过程跟建立根节点→中间节点→叶子节点的 LSP过程基本相同， 在此不 再赘述。
由上述本发明的实施例提供的技术方案可以看出， 本发明实施例通过 中间节点根据叶子节点发送的带宽预留值为所述叶子节点预留带宽资源， 从而实现了在通过 MLDP建立的 LSP中对数据流提供带宽资源保证，为从组 播源过来的 I PTV流量穿越 LS P提供了带宽保证。
本发明实施例通过建立双向 LSP , 根节点为中间节点、 中间节点为叶 子节点预留上行的带宽， 可以使得叶子节点、 中间节点向上发送的数据流 量能够得到带宽保证。
实施例二
本实施例提供的另一种 IP/MPLS网络中叶子节点 （ leaf ) 、 中间节点 ( transit ) 和根节点 （ingress ) 之间通过 mLDP建立 LSP的应用场景如图 5 所示。 图 5的场景中中间节点与两个下游叶子节点分别相连， 所述两个叶子 节点分别为叶子节点 1和叶子节点 2 , 并且所述叶子节点 1、 叶子节点 2和所 述中间节点、根节点属于同一个组播组。 图 5中只列出了与中间节点相连的 叶子节点为两个的情况， 本领域技术人员可以理解， 本实施例同样可以应 用在与中间节点相连的叶子节点为多个的情况。 本领域技术人员同样可以 理解， 本实施例也可以应用在叶子节点和根节点之间包括多个中间节点的 场景。
本实施例提供的一种 LSP的带宽资源管理方法的具体处理流程如图 6 所示， 包括：
61、 中间节点接收叶子节点 1发送的携带带宽预留值的 LDP消息， 所述 LDP消息用于建立从所述中间节点到所述叶子节点 1的 LSP。
举例来说， 上述带宽预留值可以通过如图 3所示的 DR-BW TLV ( Downstream Receiver Bandwidth Type-Length-Value,下游接收带宽的 类型长度值） 来表示， 在图 3中， Length表示 Value部分的长度， Value表 示 DR-BW TLV中携带的带宽预留值的值。
上述 LDP消息可以为 LDP协议中的 Label Mapping (标签映射） 消息， 该实施例提供的一种携带了上述 DR-BW TLV的 Label Mapping消息的格式 如图 4所示。 其中， 在 Label Mapping消息中的 optional (可选）字段中携带 上述 DR-BW TLV。
62、所述中间节点根据所述带宽预留值为所述叶子节点 1预留下行的带 宽资源， 并向所述中间节点的上游根节点发送携带所述带宽预留值的 LDP 消息。
具体地， 当所述中间节点的可用带宽资源的数值大于或者等于所述带 宽预留值时，所述中间节点给所述叶子节点 1预留数值为所述带宽预留值的 下行的带宽资源； 当所述中间节点的可用带宽资源小于所述带宽预留值时， 所述中间节点向所述叶子节点 1发送携带带宽资源不足信息的 LDP通知消 息。
举例来说， 所述 LDP消息可以为 Label Mapping消息， 中间节点接收到 叶子节点 1发送的 Label Mapping消息携带的带宽预留值为 10M , 这时中间 节点的可用带宽资源大于或者等于 1 0M ,则所述中间节点为所述叶子节点 1 预留 10M的下行的带宽资源， 并向所述根节点发送携带带宽预留值为 1 0M 的 Label Mapping消息。 本领域技术人员可以理解， 当所述中间节点和根节 点之间进一步包括其它中间节点时， 所述中间节点将向所述其他中间节点 发送上述 Label Mapping消息， 所述其他中间节点再将所述 Label Mapping 消息逐步传递到根节点。根节点根据收到的所述 Label Mapping消息中的带 宽预留值预留本节点出口带宽， 并建立 LSP。 然后， 根节点可以将从组播源 接收到的组播数据流釆用静态方式或动态方式导入上述 LSP , 并下发给中 间节点， 中间节点再将组播数据流下发给叶子节点 1。 其中， 静态方式指在 根节点上用命令行配置，把组播数据流导入上述 LSP;动态方式指在建立 IP 组播树时， 就动态的将组播数据流导入上述 LSP。
举例来说， 中间节点接收到叶子节点 1发送的 Label Mapping消息携带 的带宽预留值为 1 0M , 而这时中间节点的可用带宽资源小于 10M , 则中间 节点向叶子节点 1发送携带带宽资源不足信息的 LDP通知消息，上述带宽资 源不足信息例如可以釆用携带如图 8所示的 Status code的 MP Status TLV 来表示， 其中的 BW Status code值设置为 1。 进一步地， 上述叶子节点 1接 收到所述携带带宽资源不足信息的 LDP通知消息后， 根据本地配置情况， 选择向所述中间节点发送携带其它带宽预留值的 LDP消息。 例如， 当该其 它带宽预留值为某特殊约定值， 比如 0时， 中间节点将釆取尽力而为的方式 向上述叶子节点 1提供带宽资源保证； 或者上述叶子节点 1向所述中间节点 发送携带撤销所述 LSP的指示信息的消息， 该消息例如可以为 Label Withdraw (标签撤销消息） 。
本实施例 61中叶子节点 1发送给中间节点的带宽预留值例如可以通过 以下方式得到：
方式 1：根据所述根节点从组播源接收到的需要分发给各个叶子节点的 组播数据流的流量在叶子节点上静态配置带宽预留值， 并且归属于同一组 播组的各个叶子节点上配置的带宽预留值是相同的； 方式 2：根节点根据从组播源接收到的需要分发给各个叶子节点的组播 数据流的流量，将对应的带宽预留值，通过扩展 LDP消息或者 BGP ( Border Gateway Protocol , 边界网关协议） 消息发送给归属于同一组播组的各个 叶子节点。 实际应用中， 上述 LDP消息或者 BGP消息中的带宽预留值也可 以通过上述 DR-BW TLV来携带。
63、 所述中间节点接收叶子节点 2发送的携带带宽预留值的 LDP消息， 根据所述带宽预留值为所述叶子节点 2预留下行的带宽资源。
具体地， 当所述中间节点接收到叶子节点 2发送的携带带宽预留值的 LDP消息时， 所述 LDP消息例如可以为 Label Mapping消息。 因为上述中间 节点给归属于同一组播组的所有叶子节点预留的下行的带宽资源必须相 同， 于是， 所述中间节点判断所述叶子节点 2发送的带宽预留值和给所述叶 子节点 1预留的下行的带宽资源是否一致， 如果是， 所述中间节点根据所述 带宽预留值另外为所述叶子节点 2预留下行的带宽资源， 所述叶子节点 2成 功加入组播组； 否则， 所述中间节点向所述叶子节点 2发送携带带宽资源不 匹配信息的 LDP通知消息。 所述带宽资源不匹配的信息中可以包括中间节 点已经给其它叶子节点预留的下行的带宽值。
举例来说，所述中间节点向叶子节点 2发送携带带宽资源不匹配信息的 LDP通知消息的示意图如图 7所示， 在图 7中， 中间节点根据接收到的叶子 节点 1发送的 Label Mapping消息， 已经给叶子节点 1预留了 1 0M的带宽资 源。 当叶子节点 2向中间节点发送携带预留带宽值为 8M的 Label Mapping 消息时， 中间节点向叶子节点 2返回携带预留带宽值不匹配信息的 LDP通知 消息， 上述带宽资源不匹配信息例如可以釆用携带如图 8所示的 Status code的 MP Status TLV来表示， 其中的 BW Status code值设置为 2。
所述中间节点在接收到与叶子节点 1归属于同一组播组的其他叶子节 点（本实施例中为叶子节点 2 )发送的携带所述带宽预留值的 Label Mapping 消息后，根据携带的所述带宽预留值为所述其他叶子节, 预留带宽资源后 , 可以向所述根节点发送携带所述带宽预留值的 Label Mapping消息，也可以 不向所述根节点发送携带所述带宽预留值的 Label Mapping消息。
所述根节点将接收到的组播数据流釆用静态方式或动态方式导入上述 LSP , 并下发给中间节点， 中间节点再将组播数据流下发给叶子节点。 其 中， 静态方式指在根节点上用命令行配置， 把组播数据流导入上述 LSP; 动态方式指在建立 IP组播树时， 就动态的将组播数据流导入上述 LSP。
由上述本发明的实施例提供的技术方案可以看出， 本发明实施例通过 中间节点根据叶子节点发送的带宽预留值为所述叶子节点预留带宽资源， 根节点根据中间节点发送的带宽预留值为所述中间节点预留带宽资源， 从 而实现了在通过 MLDP建立的 LSP中对数据流提供带宽资源保证，为从组播 源过来的 I PTV流量穿越 LS P提供了带宽保证。
以上描述的是建立 P2MP LSP的过程， 如果需要建立 MP2MP LSP , 除 了建立根节点→中间节点→叶子节点的 LSP之外， 还需要建立叶子节点→ 中间节点→根节点的 LSP , 也就是需要建立双向的 LSP。 对于需要建立 MP2MP LSP的场景，本发明实施例提供的 LSP的带宽资源管理方法进一步 包括：
64、 接收所述根节点发送的携带上行带宽预留值的 LDP消息， 根据所 述上行带宽预留值为所述根节点预留上行的带宽资源。
在本实施例 62中，当所述中间节点根据叶子节点 1发送的 L D P消息中携 带的所述带宽预留值为所述叶子节点 1预留下行的带宽资源成功后，向所述 中间节点的上游根节点发送携带所述带宽预留值的 LDP消息。 所述根节点 接收到携带所述带宽预留值的 LDP消息后， 触发叶子节点→中间节点→根 节点的 LSP的建立过程， 向所述中间节点发送携带上行带宽预留值的 LDP 消息。 举例来说， 所述根节点向所述中间节点发送的 LDP消息中携带的上 行带宽预留值 BWup的数值介于 62中所述中间节点向所述根节点发送的 LDP消息中携带的带宽预留值 BWdw的 1 /N和 N倍之间， 也就是 BWdw/N < BWup < BWdw - N , 其中 N为叶子节点的个数。 在本实施例中， 比较典型 的应用是 N = 1， 也就是所述根节点向所述中间节点发送的 LDP消息中携带 的上行带宽预留值等于 62中所述中间节点向所述根节点发送的 LDP消息中 携带的带宽预留值。 或者 N^†子数， 这个情况等同于根节点向所述中间节 点发送的 LDP消息中携带的上行带宽预留值为所述中间节点给属于同一组 播组中的所有叶子节点预留的带宽资源之和， 即为所有下行的带宽资源之 和。
具体地， 所述根节点向中间节点请求的上行带宽预留值同样可以通过 如图 3所示的 DR-BW TLV来表示， 所使用的所述 LDP消息可以为 LDP协议 中的 Label Mapping (标签映射） 消息， 在此不再赘述。
具体地， 当所述中间节点的可用带宽资源的数值大于或者等于根节点 发送的 LDP消息中携带的所述上行带宽预留值时， 所述中间节点给所述根 节点预留数值为所述上行带宽预留值的上行的带宽资源， 并向所述叶子节 点 1和所述叶子节点 2发送携带上行带宽预留值的 LDP消息。 这里， 所述中 间节点向所述叶子节点 1发送的 LDP消息中携带的上行带宽预留值与本实 施例步骤 61中所述中间节点接收到的叶子节点 1发送的 LDP消息中携带的 带宽预留值相同，所述中间节点向所述叶子节点 2发送的 LDP消息中携带的 上行带宽预留值与本实施例步骤 63中所述中间节点接收到的叶子节点 2发 送的 LDP消息中携带的带宽预留值相同。 当所述中间节点的可用带宽资源 小于所述上行带宽预留值时， 所述中间节点向所述根节点发送携带带宽资 源不足信息的 LDP通知消息。 这里中间节点向所述根节点发送携带带宽资 源不足信息的 L D P通知消息和前述步骤中的方式相同， 在此不再赘述。
65、 所述中间节点向所述叶子节点 1和所述叶子节点 2发送携带带宽预 留值的 L D P消息。 当所述中间节点为所述根节点预留上行的带宽资源成功 之后， 向所述叶子节点 1和所述叶子节点 2分别发送携带带宽预留值的 LDP 消息， 该 LDP消息例如可以是 Label Mapping消息。 这里， 所述中间节点向 所述叶子节点 1发送的 LDP消息中携带的上行带宽预留值与本实施例步骤 61中所述中间节点接收到的叶子节点 1发送的 LDP消息中携带的带宽预留 值相同，所述中间节点向所述叶子节点 2发送的 LDP消息中携带的上行带宽 预留值与本实施例步骤 63中所述中间节点接收到的叶子节点 2发送的 LDP 消息中携带的带宽预留值相同。
叶子节点 1和叶子节点 2接收到所述叶子节点发送的携带上行带宽预留 值的 Label Mapping消息之后， 根据所述 Label Mapping消息中的上行带宽 预留值预留本节点出口带宽， 并建立 LSP。 然后， 叶子节点 1和叶子节点 2 将从组播源接收到的组播数据流釆用静态方式或动态方式导入上述 LSP , 并发送给中间节点， 中间节点再将组播数据流发送给跟节点。 其中， 静态 方式指在叶子节点上用命令行配置， 把组播数据流导入上述 LSP; 动态方 式指在建立 IP组播树时， 就动态的将组播数据流导入上述 LSP。
本领域技术可以理解， 上述建立叶子节点→中间节点→根节点的 LSP 的过程跟建立根节点→中间节点→叶子节点的 LSP过程基本相同， 在此不 再赘述。
实施例三
该实施例提供了一种 LSP的带宽资源管理装置 1 0 , 该装置设置在叶子 节点中， 其具体结构如图 10所示， 所述装置 10具体包括：
带宽预留值确定模块 101 , 用于获取所述叶子节点的带宽预留值， 所述 带宽预留值为中间节点需要给所述叶子节, 预留的下行的带宽资源的数 值；
叶子节点获取上述带宽预留值的方式包括但不限于如下的两种： 方式 1：根据根节点接收到的从组播源过来的需要分发给各个叶子节点 的组播数据流的流量在叶子节点上静态配置带宽预留值， 并且在归属于同 一组播组中的各个叶子节点上配置的带宽预留值是相同的； 方式 2：根节点根据接收到的需要分发给各个叶子节点的组播数据流的 流量， 向归属于同一组播组的各个叶子节点发送携带相同的带宽预留值的 LDP消息或者 BGP消息。 在实际应用中， 上述 LDP消息或者 BGP消息中的 带宽预留值也可以通过上述 DR-BW TLV来携带。
带宽预留值发送模块 102 ,用于向中间节点发送携带所述带宽预留值的 LDP消息， 所述 LDP消息用于建立从所述中间节点到所述叶子节点的 LSP。
示例性的， 上述带宽预留值可以通过如图 3所示的 DR-BW TLV ( Downstream Receiver Bandwidth Type-Length-Value,下游接收带宽的 类型长度值） 来表示， 在图 3中， Length表示 Value部分的长度， Value表 示 DR-BW TLV中携带的带宽预留值的值。
上述 LDP消息可以为 LDP协议中的 Label Mapping (标签映射） 消息， 该实施例提供的一种携带了上述 DR-BW TLV的 Label Mapping消息的格式 如图 4所示。 在图 4中， 在 Label Mapping消息中的 optional (可选） 字段中 携带上述 DR-BW TLV。
举例来说， 所述 LS P的带宽资源管理装置 1 0可以进一步包括： 通知消息处理模块 1 03 ,用于接收到所述中间节点发送的携带带宽资源 不足或者带宽预留值不匹配信息的 LDP消息后， 向所述中间节点重新发送 携带其它带宽预留值的 LDP消息， 当该其它带宽预留值为某特殊约定值 , 比如 0时，中间节点将釆取尽力而为的方式向上述叶子节点提供带宽资源保 证； 或者向所述中间节点发送撤销建立所述 L S P的消 ,包、。
举例来说， 所述 LS P的带宽资源管理装置 1 0可以进一步包括： 上行带宽预留模块 1 04 ,用于接收到所述中间节点发送的携带上行带宽 预留值的 label Mapping消息后， 预留数值为所述上行带宽预留值的上行带 宽资源。
当建立的 LSP为多点到多点 LSP ( MP2MP LSP ) 时， 由于在 MP2MP
LSP中存在双向的 LSP ,需要建立根节点→中间节点→叶子节点的 LSP和叶 子节点→中间节点→根节点的 LS P , 各个叶子节点除了接收下行的数据流 之外，还向中间节点发送上行的数据流。 所述上行带宽预留模块 1 04接收到 所述中间节点发送的携带所述上行带宽预留值的 label Mapping消息后， 预 留数值为所述上行带宽预留值的上行带宽资源。
本领域技术人员可以理解， 所述 LSP的带宽资源管理装置 1 0可以只包 括所述带宽预留值确定模块 101和带宽预留值发送模块 1 02 , 也可以在包括 所述带宽预留值确定模块 1 01和带宽预留值发送模块 1 02的基础上进一步 包括上述通知消息处理模块 103和上行带宽预留模块 1 04 , 或者在包括所述 带宽预留值确定模块 101和带宽预留值发送模块 102的基础上进一步包括 上述通知消息处理模块 1 03和上行带宽预留模块 1 04中的任意一个。
该实施例还提供了一种 LSP的带宽资源管理装置 1 1 , 该装置设置在中 间节点中， 其具体结构如图 1 1所示， 所述装置 1 1具体包括：
L D P消息处理模块 1 1 1 , 用于接收下游节点发送的携带带宽预留值的 LDP消息， 所述 LDP消息用于建立从所述中间节点到所述下游节点的 LSP。
带宽资源预留模块 1 12 , 用于根据所述 L D P消息处理模块 1 1 1接收到的 LDP消息中携带的带宽预留值为所述下游节点预留下行的带宽资源。
举例来说， 如图 12所示， 所述 LSP的带宽资源管理装置 1 1中的所述带 宽资源预留模块 1 12可以包括：
可用资源处理模块 1 121 , 用于判断所述中间节点的可用带宽资源的数 值是否大于或者等于所述 LDP消息处理模块 1 1 1接收到的 LDP消息中携带 的带宽预留值， 如果是， 给所述下游节点预留数值为所述带宽预留值的下 行的带宽资源； 否则， 向 LDP通知消息发送模块 1 122发送带宽资源不足消 息。
LDP通知消息发送模块 1 122 , 用于接收到带宽资源不足消息时， 向所 述下游节点发送携带带宽资源不足信息的 LDP通知消息。 上述带宽资源不 足信息可以釆用如实施例一所述的携带上述 BW Status code (值为 1 ) 的 MP Status TLV来表示。
举例来说， 如图 13所示， 所述带宽资源预留模块 1 12可以进一步包括： 资源匹配处理模块 1 123 , 用于判断所述 LDP消息处理模块 1 1 1接收到 的 LDP消息中携带的带宽预留值与所述中间节点给其它下游节点已经预留 的下行的带宽资源是否一致， 如果是， 根据所述 LDP消息处理模块 1 1 1接收 到的 LDP消息中携带的带宽预留值为所述下游节点预留下行的带宽资源； 否则， 向 LDP通知消息发送模块 1 122发送带宽资源不匹配消息。
所述 LDP通知消息发送模块 1 123 , 进一步用于接收到带宽资源不匹配 消息时， 向所述下游节点发送携带带宽资源不匹配信息的 LDP通知消息。 上述带宽资源不匹配信息可以釆用如实施例一所述的携带上述 S t a t u s code (值为 2 ) 的 MP Status TLV来表示。
举例来说， 所述 LSP的带宽资源管理装置 1 1还可以进一步包括： 下行带宽预留值发送模块 1 1 3 ,用于向所述中间节点的上游节点发送携 带所述带宽预留值的 LDP消息。 当叶子节点和根节点之间包括一个中间节 点时， 所述上游节点为根节点。 本领域的技术人员可以理解， 当所述中间 节点和根节点之间进一步包括其它中间节点时， 所述中间节点将向所述其 他中间节点发送上述 LDP消息， 所述其他中间节点再将所述 LDP消息逐步 传递到根节点。
当中间节点有多个分支， 或者一个中间节点下面连接有多个叶子节点 时，在所述带宽资源预留模块 1 12给归属于同一组播组的各个下游节点中的 第一个下游节点预留带宽资源后，所述下行带宽预留值发送模块 1 1 3向所述 中间节点的上游节点发送携带所述带宽预留值的 LDP消息， 在所述中间节 点给归属于同一组播组的其他下游节点中的后续下游节点预留带宽资源 后， 不向所述中间节点的上游节点发送所述 LDP消息； 或者，在所述带宽资源预留模块 1 12给归属于同一组播组的每个下游节 点预留数值为所述带宽预留值的下行的带宽资源后， 所述下行带宽预留值 发送模块 1 13分别向所述中间节点的上游节点发送携带所述带宽预留值的 LDP消息。
当所述 LSP为多点到多点 LSP ( MP2MP LSP ) 时， 所述 LDP消息处理 模块 1 1 1还可以用于接收上游节点发送的携带上行带宽预留值的 LDP消息， 所述携带上行带宽预留值的 LDP消息用于建立从所述中间节点到所述上游 节点的 LSP。
举例来说， 所述带宽资源预留模块 1 12还可以进一步包括：
上行带宽资源预留模块 1 124 , 用于当所述 L D P消息处理模块 1 1 1接收 到上游节点发送的携带上行带宽预留值的 LDP消息时， 根据所述上行带宽 预留值为所述上游节点预留上行带宽资源。
上行带宽预留值发送模块 1 14 , 用于所述上行带宽资源预留模块 1 124 根据所述上行带宽预留值为所述上游节点预留上行带宽资源成功后， 向归 属于同一组播组的每个下游节点发送携带上行带宽预留值的 LDP消息。 举 例来说，此处上行带宽预留值发送模块 1 14向归属于同一组播组的每个下游 节点发送的 LDP消息携带的上行带宽预留值可以为所述 LDP消息处理模块 1 1 1接收到上游节点发送的 LDP消息中携带的所述上行带宽预留值，也可以 是根据不同的业务类型和网络拓朴场景而配置的其他上行带宽预留值。
该实施例还提供了一种 LSP的带宽资源管理装置 14 , 该装置设置在根 节点中， 其具体结构如图 14所示， 所述装置 14具体包括：
L D P消息接收模块 141 , 用于接收中间节点发送的携带带宽预留值的 LDP消息；
下行带宽资源预留模块 142 ,用于根据所述带宽预留值为所述中间节 , 预留下行的带宽资源。
如图 1 5所示， 所述装置 14可以进一步包括： 上行带宽预留值发送模块 143 ,用于向所述中间节点发送携带上行带宽 预留值的 LDP消息。
举例来说， 所述上行带宽预留值发送模块 143向所述中间节点发送的 LDP消息中携带的上行带宽预留值 BWup的数值介于中间节点向所述根节 点发送的 LDP消息中携带的带宽预留值 BWdw的 1 /N和 BWdw的 N倍之间， 也就是 BWdw/N < BWup < BWdw . N , 其中 N为叶子节点的个数。
本领域技术人员可以理解， 应用本发明上述实施例的装置进行带宽资 源预留的具体过程与前述方法实施例相对应， 此处不再赘述。
该实施例还提供了一种 LSP的带宽资源管理系统 16 , 其具体结构如图 16所示， 包括：
叶子节点 161 , 其包括所述 LSP的带宽资源管理装置 10 , 用于获取所述 叶子节点的带宽预留值， 所述带宽预留值为中间节点需要给所述叶子节点 预留的下行的带宽资源的数值； 向中间节点发送携带所述带宽预留值的 LDP消息， 所述 LDP消息用于建立从所述中间节点到所述叶子节点的 LSP。
中间节点 162 , 其包括所述 LSP的带宽资源管理装置 1 1 , 用于接收所述 叶子节点发送的携带带宽预留值的 LDP消息， 根据所述 LDP消息中携带的 带宽预留值为所述叶子节点预留下行的带宽资源， 向根节点发送携带所述 带宽预留值的 L D P消息， 所述 L D P消息用于建立从所述中间节点到所述根 节点的 LSP。
根节点 163 , 其包括所述 LSP的带宽资源管理装置 14 , 用于接收所述中 间节点 162发送的携带带宽预留值的 LDP消息 ,根据所述带宽预留值为所述 中间节点预留下行的带宽资源。
本领域技术人员可以理解， 该实施例提供的 LS P的带宽资源管理系统 16为对应于实施例 3中的方法 LSP的带宽资源管理方法和所述 LSP的带 宽资源管理装置的 LSP的带宽资源管理系统， 其包括的 LSP的带宽资源管 理装置包括实施例 3中的 LSP的带宽资源管理装置的所有功能， 并且包括的 叶子节点 161、 中间节点 162和根节点 163之间进行 LSP的带宽资源管理的 方法流程与实施例 1和 2中的 LSP的带宽资源管理方法相对应， 在此不再赘 述。 综上所述， 本发明实施例通过中间节点根据叶子节点发送的带宽预留 值为所述叶子节点预留带宽资源， 根节点根据中间节点发送的带宽预留值 为所述中间节点预留带宽资源，从而实现了在通过 MLDP建立的 LSP中对数 据流提供带宽资源保证， 为从组播源过来的 I PTV流量穿越 LS P提供了带宽 保证。
本发明实施例通过建立双向 LSP , 根节点为中间节点、 中间节点为叶 子节点预留上行的带宽， 可以使得叶子节点、 中间节点向上发送的数据流 量能够得到带宽保证。
本发明实施例可以实现中间节点给归属于同一组播源的每个叶子节,、 预留相同的带宽资源。
本发明实施例可以针对 P2MP LSP和 MP2MP LSP ,分别给叶子节点和 中间节点预留相应的上行和下行的带宽资源。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流 程， 是可以通过计算机程序来指令相关的硬件来完成， 所述的程序可存储 于一计算机可读取存储介质中， 该程序在执行时， 可包括如上述各方法的 实施例的流程。 其中， 所述的存储介质可为磁碟、 光盘、 只读存储记忆体 ( Read-Only Memory , ROM ) 或随机存储记忆体 ( Random Access Memory, RAM ) 等。
以上所述， 仅为本发明较佳的具体实施方式， 但本发明的保护范围并 不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可轻易想到的变化或替换， 都应涵盖在本发明的保护范围之内。 因此， 本 发明的保护范围应该以权利要求的保护范围为准。

Claims

权 利 要 求 书
1、 一种标签转发路径的带宽资源管理方法， 其特征在于， 包括： 中间节点接收到下游节点发送的携带带宽预留值的标签分发协议消 息， 所述标签分发协议消息用于建立从所述中间节点到所述下游节点的标 签转发路径；
所述中间节点根据所述带宽预留值为所述下游节点预留下行的带宽资 源， 向所述中间节点的上游节点发送携带所述带宽预留值的标签分发协议 消息。
2、 根据权利要求 1所述的标签转发路径的带宽资源管理方法， 其特征 在于， 所述中间节点根据所述带宽资源预留值为所述下游节点预留下行的 带宽资源， 包括：
当所述中间节点的可用带宽资源的数值大于或者等于所述带宽预留值 时， 所述中间节点给所述下游节点预留数值为所述带宽预留值的下行的带 宽资源； 当所述中间节点的可用带宽资源小于所述带宽预留值时， 所述中 间节点向所述下游节点发送携带带宽资源不足信息的标签分发协议通知消 息。
3、 根据权利要求 1所述的标签转发路径的带宽资源管理方法， 其特征 在于， 所述中间节点根据所述带宽资源预留值为所述下游节点预留下行的 带宽资源， 包括：
在所述中间节点接收到所述标签分发协议消息之前， 已经给和所述下 游节点归属于同一组播组的其它下游节点预留下行的带宽资源， 所述中间 节点判断所述带宽预留值和给所述其它下游节点预留的下行的带宽资源是 否一致， 如果是， 所述中间节点根据所述带宽预留值为所述下游节点预留 下行的带宽资源； 否则， 所述中间节点向所述下游节点发送携带带宽资源 不匹配信息的标签分发协议通知消息。
4、 根据权利要求 2所述的标签转发路径的带宽资源管理方法， 其特征 在于， 所述方法进一步包括；
所述下游节点接收到所述携带带宽资源不足信息的标签分发协议通知 消息后， 向所述中间节点重新发送携带其它带宽预留值的标签分发协议消 息或者向所述中间节点发送撤销建立所述标签转发路径的消息。
5、 根据权利要求 4所述的标签转发路径的带宽资源管理方法， 其特征 在于， 所述的向所述中间节点的上游节点发送携带所述带宽预留值的标签 分发协议消息， 包括：
所述中间节点在给归属于同一组播源的各个下游节点中的第一个发送 标签分发协议消息的下游节点预留下行的带宽资源后， 向所述中间节点的 上游节点发送携带所述带宽预留值的标签分发协议消息；
所述中间节点在给归属于同一组播源的各个下游节点中的后续下游节 点预留下行的带宽资源后， 选择向所述中间节点的上游节点发送或者不发 送携带所述带宽预留值的标签分发协议消息。
6、 根据权利要求 1 -5任意一项所述的标签转发路径的带宽资源管理方 法， 其特征在于， 所述方法进一步包括：
所述中间节点接收到所述中间节点的上游节点发送的携带上行带宽预 留值的标签分发协议消息后， 根据所述上行带宽预留值为所述根节点预留 上行的带宽资源。
7、 根据权利要求 6所述的标签转发路径的带宽资源管理方法， 其特征 在于， 所述中间节点的上游节点发送的标签分发协议消息中携带的上行带 宽预留值 BWup的数值介于所述中间节点向所述中间节点的上游节点发送 的标签分发协议消息中携带的带宽预留值 BWdw的 1 /N和 N倍之间， 也就是 BWdw/N < BWup < BWdw · N , 其中 N为叶子节点的个数。
8、 根据权利要求 7所述的标签转发路径的带宽资源管理方法， 其特征 在于， 所述方法进一步包括： 所述中间节点还给归属于同一组播组的每个下游节点发送携带上行带 宽预留值的标签分发协议消息， 以使得所述下游节点预留数值为所述中间 节点发送的标签分发协议消息中携带的上行带宽预留值的上行带宽资源。
9、 一种标签转发路径的带宽资源管理装置， 其特征在于， 设置在叶子 节点中， 所述装置具体包括：
带宽预留值确定模块， 用于获取所述叶子节点的带宽预留值， 所述带 宽预留值为中间节点需要给所述叶子节点预留的下行的带宽资源的数值； 带宽预留值发送模块， 用于向中间节点发送携带所述带宽预留值的标 签分发协议消息， 所述标签分发协议消息用于建立从所述中间节点到所述 叶子节点的标签转发路径；
通知消息处理模块， 用于接收到所述中间节点发送的携带带宽资源不 足或者带宽预留值不匹配信息的标签分发协议消息后， 向所述中间节点重 新发送携带其它带宽预留值的标签分发协议消息或者向所述中间节点发送 撤销建立所述标签转发路径的消息。
1 0、 一种标签转发路径的带宽资源管理装置， 其特征在于， 设置在中 间节点中， 所述装置具体包括：
标签分发协议消息处理模块， 用于接收下游节点发送的携带带宽预留 值的标签分发协议消息， 所述标签分发协议消息用于建立从所述中间节点 到所述下游节点的标签转发路径；
带宽资源预留模块， 用于根据所述标签分发协议、 %息处理模块所接收 到的标签分发协议消息中携带的带宽预留值为所述下游节点预留下行的带 宽资源。
1 1、 根据权利要求 1 0所述的标签转发路径的带宽资源管理装置， 其特 征在于， 所述带宽资源预留模块包括：
可用资源处理模块， 用于判断所述中间节点的可用带宽资源的数值是 否大于或者等于所述标签分发协议消息处理模块接收到的标签分发协议消 息中携带的带宽预留值， 如果是， 给所述下游节点预留数值为所述带宽预 留值的下行的带宽资源； 否则， 向标签分发协议通知消息发送模块发送带 宽资源不足消息；
标签分发协议通知消息发送模块， 用于接收到带宽资源不足消息时， 向所述下游节点发送携带带宽资源不足信息的标签分发协议通知消息。
12、 根据权利要求 1 1所述的标签转发路径的带宽资源管理装置， 其特 征在于， 所述带宽资源预留模块进一步包括：
资源匹配处理模块， 用于判断所述标签分发协议消息处理模块接收到 的标签分发协议消息中携带的带宽预留值与所述中间节点给其它下游节点 已经预留的下行的带宽资源是否一致， 如果是， 根据所述标签分发协议消 息处理模块接收到的标签分发协议消息中携带的带宽预留值为所述下游节 点预留下行的带宽资源； 否则， 向标签分发协议通知消息发送模块发送带 宽资源不匹配消息；
所述标签分发协议通知消息发送模块， 进一步用于接收到带宽资源不 匹配消息时， 向所述下游节点发送携带带宽资源不匹配信息的标签分发协 议通知消息。
13、 根据权利要求 1 1或 12所述的标签转发路径的带宽资源管理装置， 其特征在于， 所述装置还包括：
下行带宽预留值上报模块， 用于向所述中间节点的上游节点发送携带 所述带宽预留值的标签分发协议消息；
所述带宽资源预留模块进一步包括：
上行带宽资源预留模块， 用于当所述标签分发协议、 %息处理模块接收 到上游节点发送的携带上行带宽预留值的标签分发协议消息时， 根据所述 上行带宽预留值为所述上游节点预留上行带宽资源； 上行带宽预留值发送模块， 用于所述上行带宽资源预留模块根据所述 上行带宽预留值为所述上游节点预留上行带宽资源成功后， 向归属于同一 组播组的每个下游节点发送携带上行带宽预留值的标签分发协议消息。
14、 一种标签转发路径的带宽资源管理装置， 其特征在于， 设置在根 节点中， 包括：
标签分发协议消息接收模块， 用于接收到中间节点发送的携带带宽预 留值的标签分发协议消息；
下行带宽资源预留模块， 用于根据所述带宽预留值为所述中间节点预 留下行的带宽资源。
1 5、 根据权利要求 14所述的标签转发路径的带宽资源管理装置， 其特 征在于， 所述装置还包括：
上行带宽资源通知模块， 用于当所述标签转发路径为多点到多点标签 转发路径时， 向所述中间节点发送携带指定带宽预留值的标签分发协议消 息， 所述的指定带宽预留值为所述带宽预留值乘以设定倍数。
16、 一种标签转发路径的带宽资源管理系统， 其特征在于， 包括： 叶子节点，该叶子节点包括如权利要求 9所述的标签转发路径的带宽资 源管理装置；
中间节点，该中间节点包括如权利要求 1 0-1 3任意一项所述的标签转发 路径的带宽资源管理装置， 接收所述叶子节点发送的携带带宽预留值的标 签分发协议消息， 所述标签分发协议消息用于建立从所述中间节点到所述 下游节点的标签转发路径， 并根据接收到的标签分发协议消息中携带的带 宽预留值为所述叶子节点预留下行的带宽资源； 和
根节点， 该根节点包括和权利要求 14或 1 5所述的标签转发路径的带宽 资源管理装置， 所述根节点接收所述中间节点发送的标签分发协议： i % , 并 根据所述标签分发协议消息为所述中间节点预留带宽资源。
PCT/CN2012/081474 2011-09-16 2012-09-17 标签转发路径的带宽资源管理方法、装置和系统 WO2013037319A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110276056.6 2011-09-16
CN201110276056.6A CN102315989B (zh) 2011-09-16 2011-09-16 对ms-pw进行检测的方法及设备、系统

Publications (1)

Publication Number Publication Date
WO2013037319A1 true WO2013037319A1 (zh) 2013-03-21

Family

ID=45428826

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/081474 WO2013037319A1 (zh) 2011-09-16 2012-09-17 标签转发路径的带宽资源管理方法、装置和系统

Country Status (2)

Country Link
CN (1) CN102315989B (zh)
WO (1) WO2013037319A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113660028A (zh) * 2021-08-16 2021-11-16 北京邮电大学 双向lsp处理方法、电子设备、存储介质及程序产品

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102315989B (zh) * 2011-09-16 2015-03-25 华为技术有限公司 对ms-pw进行检测的方法及设备、系统
CN103051499B (zh) * 2012-12-31 2015-11-25 华为技术有限公司 一种检测报文的方法和装置
CN108156076B (zh) * 2017-12-18 2021-03-02 北京特立信电子技术股份有限公司 基于mpls-tp线性保护的bfd报文结构、检测方法与装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6336129B1 (en) * 1997-12-05 2002-01-01 Kabushiki Kaisha Toshiba Packet transfer method and node device using resource reservation or priority transfer control without requiring virtual connection merging
CN1761232A (zh) * 2004-10-15 2006-04-19 中国科学技术大学 移动自组网络的基于动态蜂窝的按需服务质量保证的方法
CN101155131A (zh) * 2006-09-29 2008-04-02 中国电信股份有限公司 最小化路径抢占代价的标签交换路径建立方法
US20090268731A1 (en) * 2008-04-23 2009-10-29 Cisco Technology, Inc. Point-to -multipoint for multicast and unicast forwarding
CN102315989A (zh) * 2011-09-16 2012-01-11 华为技术有限公司 对ms-pw进行检测的方法及设备、系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101409656B (zh) * 2008-10-15 2012-04-18 华为技术有限公司 一种虚电路连通性检查的方法、网络节点和通信系统
CN102055619A (zh) * 2009-11-02 2011-05-11 中兴通讯股份有限公司 一种实现双向路径段故障检测的方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6336129B1 (en) * 1997-12-05 2002-01-01 Kabushiki Kaisha Toshiba Packet transfer method and node device using resource reservation or priority transfer control without requiring virtual connection merging
CN1761232A (zh) * 2004-10-15 2006-04-19 中国科学技术大学 移动自组网络的基于动态蜂窝的按需服务质量保证的方法
CN101155131A (zh) * 2006-09-29 2008-04-02 中国电信股份有限公司 最小化路径抢占代价的标签交换路径建立方法
US20090268731A1 (en) * 2008-04-23 2009-10-29 Cisco Technology, Inc. Point-to -multipoint for multicast and unicast forwarding
CN102315989A (zh) * 2011-09-16 2012-01-11 华为技术有限公司 对ms-pw进行检测的方法及设备、系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113660028A (zh) * 2021-08-16 2021-11-16 北京邮电大学 双向lsp处理方法、电子设备、存储介质及程序产品
CN113660028B (zh) * 2021-08-16 2022-05-20 北京邮电大学 双向lsp处理方法、电子设备及存储介质

Also Published As

Publication number Publication date
CN102315989B (zh) 2015-03-25
CN102315989A (zh) 2012-01-11

Similar Documents

Publication Publication Date Title
US10313239B2 (en) Methods, apparatus, and articles of manufacture to provide a multicast virtual private network (MVPN)
EP4054125B1 (en) Global network state management
US9622276B2 (en) Method and device for determining to establish multi-protocol label switching traffic engineering tunnel
US7792111B2 (en) Point-to-multipoint for multicast and unicast forwarding
EP2005313B1 (en) Facilitating application synchronization with a reservation protocol at a sender without application receiver participation
US20160006614A1 (en) Source Routing Using Path Computation Elements
CN102291307B (zh) 一种跨vpn组播实现方法、装置及网络设备
US20120057505A1 (en) Method, apparatus, and system for setting up bidirectional point-to-multipoint label switched path
WO2007054032A1 (en) Communication network system and leaf-node network element of the multicasting tree signal transmission method and node network element thereof
US20110286450A1 (en) Multicast hello on demand
WO2009000180A1 (fr) Procédé, appareil et système de protection d&#39;un noeud amont d&#39;un trajet de commutation d&#39;étiquette point à multipoint
US10225091B2 (en) Method for implementing point-to-multipoint multicast, network node, and system
WO2012109967A1 (zh) 建立标签交换路径的方法、节点设备和系统
WO2013037319A1 (zh) 标签转发路径的带宽资源管理方法、装置和系统
WO2010124537A1 (zh) 节点关联通道能力的协商方法及节点设备
US10193941B2 (en) Interworking between first protocol entity of stream reservation protocol and second protocol entity of routing protocol
US20150003451A1 (en) Method and Apparatus for Establishing Multicast Path
WO2013013577A1 (zh) 标签转发路径的带宽资源管理方法、装置和系统
US9137159B2 (en) RSVP-TE MP2MP solution
WO2008138236A1 (fr) Procédé et dispositif de diffusion multidestinataire
WO2015014197A1 (zh) 组播负载场景下选路的方法和路由器
WO2013004140A1 (zh) 避免端系统地址分发信息协议报文风暴的方法及路由网桥
CN101789897A (zh) 一种协议无关组播中资源预留的方法和路由器
Chandrasekar et al. Performance of Video Conferencing using Protocol Independent Multicast Routing with Core failure
CN104753705B (zh) Ds域的生成方法、设备及系统

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

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

Country of ref document: EP

Kind code of ref document: A1