US20080212496A1 - Communication network system and signal transmission method between leaf-nodes of multicast tree and node thereof - Google Patents

Communication network system and signal transmission method between leaf-nodes of multicast tree and node thereof Download PDF

Info

Publication number
US20080212496A1
US20080212496A1 US12/118,509 US11850908A US2008212496A1 US 20080212496 A1 US20080212496 A1 US 20080212496A1 US 11850908 A US11850908 A US 11850908A US 2008212496 A1 US2008212496 A1 US 2008212496A1
Authority
US
United States
Prior art keywords
node
connection
leaf
root
signal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12/118,509
Inventor
Shimin Zou
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Assigned to HUAWEI TECHNOLOGIES CO., LTD. reassignment HUAWEI TECHNOLOGIES CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ZOU, SHIMIN
Publication of US20080212496A1 publication Critical patent/US20080212496A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks

Definitions

  • the present disclosure relates to multicast service technology, and in particular to a method for transmitting a signal between leaf-nodes of a multicast tree in the communication network, to a communication network system and a node thereof.
  • a multicast tree is a tree-shaped unidirectional connection with a fixed bandwidth, from a source node to a plurality of destination nodes.
  • the source node of a multicast tree is normally named as the root-node node, and the respective destination nodes of the multicast tree are normally named as the leaf-node nodes.
  • the multicast tree can be used to support unidirectional broadcast or multicast services, such as VOD service and the like.
  • an end-to-end connection can be rapidly established in a connection-oriented communication network through the introduction of the control plane technology.
  • signaling technology and routing technology of the control plane it is possible to swiftly establish the multicast tree and efficiently share the network resource.
  • all the branches of the multicast tree are unidirectional connections.
  • the unidirectional establishing process needs to be initiated from the root-node to every leaf-node.
  • the bandwidth resource on the public path can be shared through a merging process for resources.
  • all the unidirectional connections of the multicast tree can efficiently share the bandwidth resource of the public path. As shown in FIG.
  • the node LSR A initiates the establishing process for the unidirectional connection LSP (Label Switch Path) 1 to leaf-node LSR D, through LSR B and LSR C, the establishing process for the unidirectional connection LSP 2 to leaf-node LSR F, through LSR B and LSR E, and the establishing process for the unidirectional connection LSP 3 to leaf-node LSR G, through LSR B and LSR E.
  • the three unidirectional connections are associated with each other through unique multicast identifier, and a plurality of unidirectional LSPs is merged on the public path to share the transmission resource.
  • LSP 1 , LSP 2 and LSP 3 share the label resource (L 1 , L 2 ) at the entrance and the exit of LSR A, as well as the label resource (L 1 ) at the entrance of LSR B.
  • LSP 2 and LSP 3 share the label resource (L 1 , L 2 ) at the entrance and the exit of LSR A, the label resource (L 1 , L 3 ) at the entrance and exit of LSR B, and the label resource (L 1 ) at the entrance of LSR E.
  • the present disclosure provides a method for transmitting a signal between leaf-nodes of a multicast tree in the communication network, and provides a communication network system and a node thereof.
  • the network resource occupied by the existing multicast tree can be shared to the maximum.
  • the method for transmitting a signal between leaf-nodes of a multicast tree in a communication network includes:
  • a root-node includes:
  • connection establishing unit adapted to establish a connection with a source leaf-node of a multicast tree for transmitting a signal
  • a signal forwarding unit adapted to forward the signal received from the source leaf-node through the established connection to the destination leaf-node of the multicast tree for receiving the signal.
  • a leaf-node includes:
  • connection establishing unit adapted to establish a connection with a root-node of the multicast tree
  • a signal transmitting unit adapted to transmit the signal to be transmitted to a destination leaf-node, to the root-node through the established connection.
  • a communication network system includes a root-node and a leaf-node of a multicast tree, and the connection established from the leaf-node to the root-node.
  • the leaf-node is adapted to transmit a signal to the root-node through the established connection; and the root-node is adapted to forward the signal that is received through the established connection, to the destination leaf-node of the multicast tree for receiving the signal.
  • a method for establishing a quasi bi-directional connection between a root-node and a leaf-node of a multicast tree includes:
  • the present disclosure provides a method for transmitting a signal between leaf-nodes of a multicast tree in the communication network, including the steps of: establishing a connection from the source leaf-node of the multicast tree, which is adapted to transmit a signal, to the root-node; transmitting, by the source leaf-node of the multicast tree for transmitting the signal, the signal to the root-node through the established connection; and forwarding, by the root-node of the multicast tree, the received signal to the destination leaf-node of the multicast tree for receiving the signal, so as to implement the transmission of a signal.
  • the arrangement makes it possible for the leaf-node to transmit the signal to other leaf-nodes in a connection-oriented network, while efficiently taking use of the existing network resources of the multicast tree, and reducing the overhead on signaling to the maximum.
  • FIG. 1 is a schematic diagram illustrating the establishment of a multicast tree in prior art
  • FIG. 2 is a primary flow chart illustrating a method for transmitting a signal between leaf-nodes in the communication network according to an embodiment of the present disclosure
  • FIG. 3 is a primary flow chart for establishing the quasi bi-directional connection from the root-node to the leaf-node according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram illustrating the object of connection attributes added through extending GMPLS RSVP-TE signaling protocol according to the present disclosure
  • FIG. 5 is a flow chart illustrating a method for transmitting a signal between the leaf-nodes of the multicast tree according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram illustrating the object of request instruction for the leaf-node added through extending GMPLS RSVP-TE signaling protocol according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram illustrating a practical implementation of the multicast tree according to the present disclosure, which realizes the function that a leaf-node transmits signal to other leaf-nodes of the multicast tree;
  • FIG. 8 is a schematic diagram illustrating the allocation of label resources in the multicast tree shown in FIG. 7 ;
  • FIG. 9 is a signaling flow chart illustrating a practical implementation that a multicast service is established between the leaf-node LSR D and the root-node LSR A by means of the extended GMPLS RSVP-TE signaling protocol;
  • FIG. 10 is a signaling flow chart illustrating the practical implementation shown in FIG. 7 , where the leaf-node LSR F in the multicast tree transmits local user signal to other nodes;
  • FIG. 11 is a flow chart illustrating the practical implementation that a leaf-node establishes a new unidirectional connection to the root-node upon transmitting a user signal;
  • FIG. 12 is a schematic diagram illustrating a practical implementation that the leaf-node transmits a signal through a newly established connection from the leaf-node to the root-node, in accordance with the present disclosure
  • FIG. 13 is a schematic diagram illustrating the allocation of label resources in the multicast tree shown in FIG. 12 ;
  • FIG. 14 is a signaling flow chart illustrating the practical implementation that the leaf-node LSR D in the multicast tree transmits local user signal to other nodes of the multicast tree;
  • FIG. 15 is a schematic diagram illustrating a practical implementation of the communication network system according to the present disclosure.
  • FIG. 16 is a structural block diagram for implementing the communication network shown in FIG. 15 , in accordance with one embodiment of the present disclosure.
  • FIG. 17 is a structural block diagram for implementing the communication network shown in FIG. 15 , in accordance with another embodiment of the present disclosure.
  • a leaf-node in a multicast tree requests to transmit a signal to other leaf-nodes
  • a new connection is established between the root-node and the leaf-node or existing connection is modified, so that the signal from the leaf-node can be transmitted to the root-node.
  • the root-node switches the signal from the leaf-node to the other leaf-nodes along the direction of the multicast tree.
  • the arrangement makes it possible for a leaf-node to transmit signal to other leaf-nodes using the network resources of the existing multicast tree.
  • FIG. 2 is a primary flow chart illustrating a method for transmitting a signal between leaf-nodes in the communication network according to an embodiment of the present disclosure, including the following steps.
  • step 11 establish a connection from the source leaf-node of the multicast tree, which is adapted to transmit a signal, to the root-node.
  • the established connection can be a bi-directional connection from the root-node to the source leaf-node, or a unidirectional connection that is newly established from the source leaf-node to the root-node.
  • step 12 the source leaf-node of the multicast tree that is adapted to transmit the signal transmits the signal to the root-node through the established connection.
  • step 13 after receiving the signal, the root-node of the multicast tree forwards the signal to the destination leaf-node of the multicast tree, which is adapted to receive the signal, thereby implementing the transmission of a signal.
  • the establishment of the connection between the source leaf-node and the root-node described above can be realized by modifying the existing connection from the root-node to the leaf-node.
  • the existing connection is a quasi bi-directional connection from the root-node to the leaf-node, the quasi bi-directional connection having the following attributes.
  • the unidirectional connection from the root-node to the leaf-node reserves resource on the control plane, and allocates the resource on the transmission plane; the unidirectional connection from the leaf-node to the root-node only reserves resource on the control plane, and does not allocate the resource on the transmission plane.
  • FIG. 3 is a primary flow chart for establishing the quasi bi-directional connection from the root-node to the leaf-node according to an embodiment of the present disclosure, wherein the root-node of the multicast tree initiates the request to establish a quasi bi-directional connection to each leaf-node; each leaf-node of the multicast tree establishes a quasi bi-directional connection with the root-node in response to establish the quasi bi-directional connection.
  • the specific process is as below.
  • step s 11 the root-node determines the quasi bi-directional connection to each leaf-node
  • step s 12 the root-node transmits to each leaf-node a call request message which contains the instruction information that instructs to establish the quasi bi-directional connection;
  • each leaf-node determines the request from the root-node for establishing the quasi bi-directional connection, according to the instruction information, and returns the call responding message to the root-node;
  • the root-node transmits to each leaf-node a connection request message which contains the instruction information by which the unidirectional connection from the root-node to the leaf-node reserves the resource on the control plane, and allocates the resource on the transmission plane, while the unidirectional connection from the leaf-node to the root-node only reserves the resource on the control plane, and does not allocate the resource on the transmission plane;
  • step s 15 the leaf-node that has received the connection request message performs actions to reserve corresponding resource according to the instruction information contained in the connection request message, and then returns a connection responding message to the root-node.
  • the embodiments of the present disclosure can be achieved through extending RSVP-TE (RSVP Traffic Engineering) signaling protocol of the current GMPLS (Generalized Multi-Protocol Label Switch).
  • RSVP-TE RSVP Traffic Engineering
  • the call request message and the connection request message can both use the PATH message of the RSVP-TE protocol of the extended GMPLS
  • the call responding message and the connection responding message can both use the Resv message of the extended GMPLS RSVP-TE protocol.
  • the PATH message in the extended GMPLS RSVP-TE protocol can be extended to add into an object of connection attributes, which is used to contain an instruction information instructing the establishment of the quasi bi-directional connection, or an instruction information by which the unidirectional connection from the root-node to the leaf-node reserves resource on the control plane, and allocates the resource on the transmission plane, while the unidirectional connection from the leaf-node to the root-node only reserves the resource on the control plane, and does not allocate resource on the transmission plane.
  • an object of connection attributes which is used to contain an instruction information instructing the establishment of the quasi bi-directional connection, or an instruction information by which the unidirectional connection from the root-node to the leaf-node reserves resource on the control plane, and allocates the resource on the transmission plane, while the unidirectional connection from the leaf-node to the root-node only reserves the resource on the control plane, and does not allocate resource on the transmission plane.
  • the embodiments of the present disclosure may introduce a new object of connection attributes, namely, CONNECTIONG_ATTRI, into the current message of GMPLS RSVP-TE signaling protocol.
  • the CONNECTIONG_ATTRI object may contain the following components:
  • Length the length of the object in octet, including the heading part.
  • the length value of the object may be 8;
  • Class-Num type code, whose value is allocated by the IANA, for example 222;
  • C-Type subtype code, whose value is allocated by the IANA, for example 1;
  • FIG. 5 is a flow chart illustrating a method for transmitting a signal of the leaf-nodes of the multicast tree according to an embodiment of the present disclosure, including the following primary steps.
  • the source leaf-node for transmitting the signal initiates an establishment request to modify the quasi bi-directional connection from the root-node to the source leaf-node, into a bi-directional connection.
  • the source leaf-node for transmitting a signal transmits to the root-node a call request message containing the instruction information indicating that the source leaf-node requests the transmission of a signal.
  • the root-node that has received the call request message determines, according to local policy, whether or not to accept the call request from the source leaf-node.
  • the root-node determines that the source leaf-node requests the transmission of a signal according to the instruction information, and transmits a responding message back to the source leaf-node. Else, the root-node transmits a call rejecting message to the source leaf-node.
  • step s 22 establish a bi-directional connection from the root-node to the source leaf-node in response to the establishment request from the source leaf-node to modify the quasi bi-directional connection into a bi-directional connection.
  • the root-node transmits a connection request message to the source leaf-node through transit nodes.
  • the connection request message contains the instruction information for modifying the quasi bi-directional connection into a bi-directional connection.
  • the source leaf-node and the transit nodes that have received the connection request message reserve corresponding resources for the bi-directional connection according to the instruction information, and return a responding message to the root-node.
  • step s 23 the source leaf-node transmits message to the root-node through the connection from the source leaf-node to the root-node of the bi-directional connection between the two nodes.
  • step s 24 the root-node switches the connection from the source leaf-node to the root-node, which is along the receiving direction, to the connection that is along the transmitting direction of the multicast tree.
  • step s 25 the root-node forwards the signal to each destination leaf-node through the connection that is along the transmitting direction of the multicast tree.
  • the embodiment of the present disclosure can be implemented by extending the current GMPLS RSVP-TE signaling protocol.
  • the call request message and connection request message can both use the Path message in the extended GMPLS RSVP-TE protocol
  • the call responding message and connection responding message can both use the Resv message in the extended GMPLS RSVP-TE protocol.
  • the PATH message in the extended GMPLS RSVP-TE protocol can be extended to add into an object of request instruction to which the signal is transmitted by the leaf-node, which is used to contain the instruction information indicating that the source leaf-node requests the transmission of a signal, as well as an object of connection attributes, which is used to contain the instruction information for the modification from the quasi bi-directional connection into the bi-directional connection.
  • object of connection attributes The actual implementation of the object of connection attributes has been shown above, and here is an example to demonstrate the implementation of the object of request instruction to which the signal is transmitted by the source leaf-node.
  • the embodiment of the present disclosure may introduce a new object of request instruction to which the signal is transmitted by the leaf-node, namely, SEND_DATA_REQUEST, into the current GMPLS RSVP-TE signaling protocol.
  • the SEND_DATA_REQUEST object may contain the following components:
  • Length the length of the object in octet, including the object's head.
  • the length value of the object may be 12;
  • Class-Num type code, whose value is allocated by the IANA, for example 223;
  • C-Type subtype code, whose value is allocated by the IANA, for example 1;
  • SendDataReq the request instruction for the leaf-node to transmit signal, which may take one of the following values:
  • NodeId the serial number of the leaf-node that requests to transmit the signal
  • the root-node that has been instructed by the object of request instruction can communicate with the leaf-node to initiate the transmission of a signal.
  • FIG. 7 is a schematic diagram illustrating a practical implementation of the multicast tree according to the present disclosure, which realizes the function that a leaf-node transmits signal to other leaf-nodes of the multicast tree.
  • the nodes that participate in the multicast service include LSR A, LSR B, LSR C, LSR D, LSR E, LSR F and LSR G, of which the LSR A is the root-node of the multicast tree.
  • LSR A is the root-node of the multicast tree.
  • each leaf-node joins the multicast tree it first transmits an end-to-end request towards the root-node of the multicast tree.
  • the establishment process for the quasi bi-directional connection from the root-node to the leaf-node is initiated only following the completion of the call.
  • the leaf-nodes of the multicast tree LSR D, LSR F and LSR G have respectively established a quasi bi-directional connection with the root-node LSR A, namely, LSP 1 , LSP 2 , LSP 3 .
  • LSP 1 ,LSP 2 and LSP 3 share the resource between LSR A and LSR B; LSP 2 and LSP 3 share the resource through LSR A, LSR B and LSR E.
  • the quasi bi-directional connection LSP 1 includes the unidirectional connection 1 from LSR A to LSR D and the unidirectional connection 2 from LSR D to LSR A.
  • the quasi bi-directional connection LSP 2 includes unidirectional connections 3 and 4
  • the quasi bi-directional connection LSP 3 includes unidirectional connections 5 and 6 .
  • the unidirectional connections 1 , 3 and 5 reserve the resource on the control plane and allocate the resource on the transmission plane
  • the unidirectional connections 2 , 4 and 6 reserve the resource on the control plane but do not allocate the resource on the transmission plane.
  • the current signaling protocol can be extended to modify the connection attributes of LSP 1 , so that the unidirectional connection 2 reserves resource on the control plane and allocates resource on the transmission plane, thus modifying the quasi bi-directional connection LSP 1 into a bi-directional connection.
  • the root-node LSR A switches from the unidirectional connection 2 of the LSP 1 to the unidirectional connection 1 through local process 7 .
  • the user signal 11 of LSR D can be transmitted to all leaf-nodes, but the user signal 10 of LSR A can no longer be transmitted at the same time.
  • LSR A first modifies the connection attributes of LSP 1 related to LSR D that is currently transmitting signal, recovering LSP 1 to its original status, that is, the unidirectional connection 2 reserves the resource on the control plane and releases the allocated resource on the transmission plane, while the unidirectional connection 1 retains its current status.
  • the connection attribute of LSP 2 is modified, that is, the unidirectional connection 4 reserves the resource on the control plane and allocates the resource on the transmission plane.
  • connection attributes of LSP 1 and LSP 2 can also be performed simultaneously, or the connection attribute of LSP 2 is first modified and then the connection attribute of LSP 1 is modified.
  • the root-node LSR A switches from the unidirectional connection 4 of the LSP 2 to the unidirectional connection 3 through local process 7 .
  • the user signal 12 of LSR F can be transmitted to all leaf-nodes, but the user signal 11 of LSR D can no longer be transmitted at the same time.
  • the establishment process of the multicast tree includes the following steps.
  • the root-node LSR A of a certain multicast service is determined in a connection-oriented network
  • a leaf-node LSR D demanding to join the multicast tree transmits a call request to the root-node LSR A;
  • LSR A determines that LSR D can be added into the multicast tree, and responds the call request from LSR D;
  • LSR A works out a best path to reach the leaf-node LSR D: LSRA-LSR B-LSR C-LSR D;
  • connection path is associated with a unique multicast identifier in the multicast tree, and transmits a signaling message that requests to establish a quasi bi-directional LSP with taking LSR D as the destination node.
  • the connection attribute parameters contained in the parameters of the connection request message of the quasi bi-directional LSP connection has the following characteristics: a) the unidirectional connection from the root-node to the leaf-node reserves the resource on the control plane and allocates the resource on the transmission plane; b) the unidirectional connection from the leaf-node to the root-node reserves the resource on the control plane but does not allocate the resource on the transmission plane.
  • the new parameters for connection attributes in step 5 can be contained in CONNECTIONG_ATTRI, an object of connection attributes that is newly introduced into the current (G)MPLS signaling protocol.
  • the quasi bi-directional LSP connection with above attributes can be established using the signaling mechanism defined in the current ITU-T Recommendation G7713.2.
  • the leaf-node LSR D can receive user signal 10 from the root-node, but at this time, the leaf-node LSR D can not transmit local user signal 11 to other leaf-nodes.
  • the multicast tree includes three quasi bi-directional connections, of which LSP 1 , LSP 2 and LSP 3 share the bi-directional label resources (L 2 , L 1 ) between LSR A and LSR B.
  • LSR B exchanges the local label L 1 to the exit labels L 2 and L 3 .
  • LSR B only maintains the simultaneous exchanging relationships from the entrance labels L 2 and L 3 to the exit label L 1 on the control plane, while it does not actually perform the exchange action on the transmission plane.
  • the bi-directional labels from the root-node to the leaf-node is reserved on the control plane, but only unidirectional labels from the root-node to the leaf-node is allocate on the transmission plane, and the unidirectional labels from the leaf-node to the root-node is not allocated on the transmission plane.
  • LSP 2 and LSP 3 share the bi-directional label resources (L 2 , L 1 ) between LSR A and LSR B, and the bi-directional label resources (L 3 , L 1 ) between LSR B and LSR E.
  • LSR E exchanges the local label L 1 to the exit labels L 2 and L 3 .
  • LSR E only maintains the simultaneous exchanging relationships from the entrance labels L 2 and L 3 to the exit label L 1 on the control plane, while it does not actually perform the exchange action on the transmission plane.
  • an embodiment in which a multicast service is established between the leaf-node LSR D and the root-node LSR A by means of the extended GMPLS RSVP-TE signaling protocol includes the following signaling steps.
  • the leaf-node LSR F requests to transmit local user signal 12 to other leaf-nodes
  • the leaf-node LSR F for transmitting the signal transmits a call request message to the root-node LSR A.
  • the request message contains the instruction information indicating that the leaf-node LSR F demands to transmit the signal.
  • the root-node LSR A determines whether the call request can be permitted based on the local policy. If the call request is not permitted, then LSR A transmits a call rejecting message to the leaf-node LSR F, and the request process is over.
  • the bi-directional connection which is related to the leaf-node LSR D which is currently transmitting signal, is determined as LSP 1 .
  • the modification for the attributes of LSP 1 is implemented through transmitting a modifying message that contains the CONNECTIONG_ATTRI object to LSR D.
  • the unidirectional connection 2 which is from the leaf-node LSR D that is currently transmitting signal, to the root-node LSR A, releases the resource it has occupied on the transmission plane, and maintains a reserved status on the control plane. While the unidirectional connection 1 , which is from LSR A to LSR D, maintains its original status.
  • LSR A After determining that the modification signaling process for the connection status of LSP 1 is complete, LSR A transmits a connection request message which contains the CONNECTIONG_ATTRI object to implement the modification on the attributes of LSP 2 , to the leaf-node LSR F that requests the transmission of a signal, so that resources are allocated for the unidirectional connection 4 from the leaf-node LSR F to the root-node LSR A.
  • the information from the unidirectional of the root-node LSR F is locally switched to the unidirectional connection 3 which is along the transmitting direction of the root-node LSR A. In this way, the leaf-node LSR F can transmit the signal 12 to other leaf-nodes of the multicast tree, while the transmission of the user signal 11 of LSR D is stopped.
  • the extended GMPLS RSVP-TE signaling protocol is used, and the signaling flow for requesting the transmission of a signal from the leaf-node LSR F to the root-node LSR A is as follows.
  • PATH message the call request message from LSR F to LSR A, which contains the extended object SEND_DATA_REQUEST according to the embodiment of the present disclosure
  • RESV message the call responding message from LSR A to LSR F;
  • LSR A determines that LSR D is the node that is currently transmitting signal, and then LSR A transmits to LSR B a connection request message aiming at LSP 1 .
  • the LSP 1 is the connection between LSR A and LSR D.
  • PATH message which is the connection request message from LSR B to LSR C.
  • LSR B releases the resource that the unidirectional connection 2 of LSP 1 has allocated on the transmission plane based on the new values of the connection attributes and forwards the CONNECTIONG_ATTRI object to downstream;
  • PATH message which is the connection request message from LSR C to LSR D.
  • LSR C releases the resource that the unidirectional connection 2 of LSP 1 has allocated on the transmission plane based on the new values of the connection attributes and forwards the CONNECTIONG_ATTRI object to downstream;
  • LSR D After receiving the PATH message, LSR D releases the resource that the unidirectional connection 2 of LSP 1 has allocated on the transmission plane based on the new values of the connection attributes and transmits a connection responding message to upstream;
  • LSR C After receiving the RESV message, LSR C forwards the connection responding message to upstream;
  • LSR B After receiving the RESV message, LSR B forwards the connection responding message to upstream;
  • LSR A transmits to LSR B a connection request message aiming at LSP 2 .
  • LSP 2 is the connection between LSR A and LSR F.
  • PATH message which is the connection request message from LSR B to LSR E.
  • LSR B allocates resource for the unidirectional connection 4 of LSP 2 on the transmission plane, and forwards the CONNECTIONG_ATTRI object to downstream;
  • PATH message which is the connection request message from LSR E to LSR F.
  • LSR E allocates resource for the unidirectional connection 4 of LSP 2 on the transmission plane, and forwards the CONNECTIONG_ATTRI object to downstream;
  • LSR F allocates resource for the unidirectional connection 4 of LSP 2 on the transmission plane according to the new value of the connection attributes, and transmits a connection responding message to upstream;
  • LSR E After receiving the RESV message, LSR E forwards the connection responding message to upstream;
  • LSR B After receiving the RESV message, LSR B forwards the connection responding message to upstream;
  • LSR A After receiving the RESV message, LSR A performs local switching process by which the connection 4 that is along the receiving direction of LSP 2 is switched to the connection 3 that is along the transmitting direction. When the modification for the connection is complete, LSR F can transmit the signal 12 to other leaf-nodes.
  • the steps 104 , 105 , 106 , 107 , 108 are performed first, and then the steps 104 a , 105 a , 106 a , 107 a , 108 a are performed, or these steps can also be performed simultaneously, or the steps 104 a , 105 a , 106 a , 107 a , 108 a are performed first, and then the steps 104 , 105 , 106 , 107 , 108 are performed.
  • the existing quasi bi-directional connection is modified to establish a bi-directional connection from the root-node to the leaf-node, so as to implement the transmission of a signal among leaf-nodes.
  • the transmission of a signal may be implemented by establishing unidirectional connection from the source leaf-node to the root-node.
  • the source leaf-node that transmits the signal initiates a request for establishing a connection to the root-node.
  • the connection from the source leaf-node to the root-node is established; then the root-node switches the newly established unidirectional connection to the connection along the transmitting direction of the multicast tree.
  • the leaf-node can transmit local user signal to other leaf-nodes of the multicast tree
  • FIG. 11 is a flow chart illustrating the practical implementation that a leaf-node establishes a new unidirectional connection to the root-node upon transmitting a user signal, including the following primary steps.
  • step s 31 the source leaf-node that transmits the signal transmits to the root-node a call request message which contains the instruction information indicating that the source leaf-node requests the transmission of a signal.
  • step s 32 the root-node that has received the call request message determines that the source leaf-node requests the transmission of a signal according to the instruction information, and returns a call responding message back to the source leaf-node.
  • step s 33 the source leaf-node transmits a connection request message to the root-node.
  • step s 34 the root-node returns a connection responding message back to the source leaf-node to complete the establishment of the connection.
  • step s 35 the source leaf-node transmits the signal to the root-node through the connection from the source leaf-node to the root-node.
  • step s 36 the root-node switches the connection from the source leaf-node to the root-node, which is along the receiving direction, to the connection that is along the transmitting direction of the multicast tree.
  • step s 37 the root-node forwards the signal to each destination leaf-node through the connection that is along the transmitting direction of the multicast tree.
  • the present disclosure can be implemented by extending the current GMPLS RSVP-TE signaling protocol.
  • the call request message and the connection request message can both be the PATH message in the extended GMPLS RSVP-TE protocol
  • the call responding message and the connection responding message can both be the Resv message in the extended GMPLS RSVP-TE protocol.
  • the PATH message in the extended GMPLS RSVP-TE protocol can be extended to add into an object of request instruction SEND_DATA REQUEST of the leaf-node for transmitting the signal.
  • the PATH message is used to contain the instruction information indicating that the source leaf-node requests transmission of a signal.
  • the actual implementation of the object of request instruction for a leaf-node to transmit signal has been described above, so there is no need for repetition here.
  • all nodes that the multicast tree transits include: LSR A, LSR B, LSR C, LSR D, LSR E, LSR F and LSR G, of which LSR A is the root-node, while LSR D, LSR F and LSR G are the leaf-nodes.
  • LSR A is the root-node
  • LSR D, LSR F and LSR G are the leaf-nodes.
  • LSR A is the root-node
  • LSR D, LSR F and LSR G are the leaf-nodes.
  • LSR A unidirectional connections from LSR A to the leaf-nodes are established respectively, including LSP 1 to the leaf-node LSR D, LSP 2 to the leaf-node LSR F, and LSP 3 to the leaf-node LSR G.
  • a merging process for the three LSPs is performed on the public path in order to share resources.
  • the unidirectional connections LSP 1 , LSP 2 and LSP 3 share the resource between LSR A and LSR B, and LSR B exchanges the local entrance label L 1 to the exit labels L 2 and L 3 simultaneously.
  • the unidirectional connections LSP 2 and LSP 3 share the resource among LSR A, LSR B and LSR E, and LSR E exchanges the local entrance label L 1 to the exit labels L 2 and L 3 simultaneously.
  • the root-node LSR A exchanges the local user signal 10 from the local entrance label L 1 to the local exit label L 2 .
  • the leaf-nodes LSR D, LSR F and LSR G can now receive the local user signal 10 from the root-node LSR A through the multicast tree.
  • LSR D when the leaf-node LSR D demands to transmit the local user signal 11 to other leaf-nodes, LSR D initiates a request to LSR A for a unidirectional connection, and establishes that a unidirectional connection LSP 4 from LSR D to LSR A, through a node LSR H in the network. After the unidirectional connection LSP 4 is established, the allocation of label resources is shown in the 130 part of FIG. 13 .
  • the leaf-node LSR D maps the local user signal 11 to be transmitted into the local entrance label L 2 , and exchanges the entrance label L 2 to the exit label L 3 .
  • LSR H exchanges the entrance label L 2 to the exit label L 1
  • LSR A allocates the entrance label L 3 for the unidirectional connection LSP 4
  • LSR A locally exchanges the entrance label L 3 to the exit label L 2 (as the process 7 in FIG. 12 ), and deletes the existing local exchanging relationship from the entrance label L 1 to the exit label L 2 .
  • the local user signal 11 from LSR D can be transmitted to both leaf-nodes LSR F and LSR G, through the cooperation of the newly established unidirectional connection LSP 4 and the original multicast tree.
  • the local user signal 10 from LSR A may no longer be transmitted to other leaf-nodes of the multicast tree.
  • the steps for the leaf-node LSR D to transmit the local user signal 11 to other leaf-nodes of the multicast tree using the GMPLS RSVP-TE signaling protocol are as follows.
  • LSR D transmits the call request message PATH to LSR A, the call request message PATH containing the object of request instruction SEND_DATA REQUEST that the leaf-node LSR D requests transmission of a signal to transmit the local user signal 11 to other leaf-nodes of the multicast tree;
  • LSR A After determining to receive the call request, LSR A transmits the call responding message RESV to LSR D;
  • LSR D can establish unidirectional connection LSP to LSR A via LSR H through route querying process, and transmits a PATH message to LSR H for requesting to establish a unidirectional connection from LSR D to LSR A;
  • LSR H transmits a PATH message to LSR A for requesting to establish a unidirectional connection from LSR D to LSR A;
  • LSR A allocates local entrance label L 3 for that unidirectional connection upon receiving the PATH message requesting the unidirectional connection, and transmits a connection responding message RESV to LSR H;
  • LSR H allocates local entrance label L 2 and exit label L 1 for the unidirectional connection upon receiving the connection responding message, and transmits a connection respond message RESV to LSR D;
  • LSR D allocates local entrance label L 2 and exit label L 3 for the unidirectional connection upon receiving the connection responding message, and transmits a connection confirming message Confirm to LSR H;
  • LSR H forwards the Confirm message to LSR A after necessary local processes (such as the startup of monitoring and alarm process), upon receiving the Confirm message;
  • LSR A confirms the unidirectional connection from LSR D to LSR A to be established successfully after receiving the Confirm message; LSR A exchanges the local entrance label L 3 to the exit label L 2 , and deletes the original exchanging relationship from the entrance label L 1 to the exit label L 2 .
  • the leaf-node LSR D of the multicast tree can transmit the local user signal 11 to other leaf-nodes of the multicast tree.
  • FIG. 15 is a schematic diagram illustrating a practical implementation of the communication network system according to the present disclosure.
  • the communication network includes the root-node 800 and the leaf-node 900 in the multicast tree.
  • the leaf-node 900 transmits signal to other leaf-node of the multicast tree, it can be called as source leaf-node.
  • the leaf-node 900 transmits a signal to the root-node 800 through the established connection, and the root-node 800 forwards the signal received by the established connection to the destination leaf-nodes of the multicast tree for receiving the signal (not shown in the figure).
  • connection there are various forms to establish the connection from the leaf-node to the root-node.
  • the connection can be established by modifying the quasi bi-directional connection from the root-node to each leaf-node; or by establishing a new unidirectional connection from the leaf-node to the root-node when requiring the transmission of a signal.
  • the root-node 800 includes: a connection establishing unit 810 adapted to establish the connection with the source leaf-node 900 which transmit a signal in the multicast tree; and a signal forwarding unit 820 adapted to forward the signal received from the source leaf-node 900 through the established connection to the destination leaf-nodes of the multicast tree for receiving the signal.
  • the source leaf-node 900 includes: a connection establishing unit 910 adapted to establish a connection to the root-node 800 in the multicast tree; and a signal transmitting unit 920 adapted to transmit the signal that needs to reach the destination leaf-nodes of the multicast tree to the root-node 800 through the established connection.
  • the connection establishing unit 810 of the root-node 800 includes: a call request message processing unit 811 adapted to parse the call request message from the source leaf-node 900 , the call request message containing the instruction information indicating that the source leaf-node requests the transmission of a signal; a call responding message processing unit 812 adapted to generate the call responding message to the source leaf-node 900 according to the instruction information; a call rejecting message processing unit 813 adapted to generate the call rejecting message to the source leaf-node 900 from which the call request message is transmitted; a call request determining unit 814 adapted to determine whether or not to accept the call request from the source leaf-node which transmitting the request message based on local policy, then informs the call responding message processing unit 812 if determining to receive, or informs the call rejecting message processing unit 813 if determining to reject; and a connection request message processing unit 815 adapted to generate a connection request message
  • the signal forwarding unit 820 of the root-node 800 includes: a connection switching unit 821 adapted to switch the connection from the source leaf-node to the root-node, which is along the receiving direction, to the connection that is along the transmitting direction of the multicast tree; and a signal transmitting unit 822 adapted to forward the signal to each destination leaf-node through the connection that is along the transmitting direction of the multicast tree.
  • the connection establishing unit 910 of the source leaf-node includes: a call request message processing unit 911 adapted to generate a call request message to the root-node 800 , the call request message containing the instruction information indicating that the source leaf-node requests the transmission of a signal; a connection request message processing unit 912 adapted to parse the connection request message which is transmitted by the root-node 800 through transit nodes, the connecting request message containing the instruction information that requests to modify the quasi bi-directional connection into a bi-directional connection; and a bi-directional connection processing unit 913 adapted to reserve resources according to the instruction information, and return a connection responding message to the root-node.
  • the call request message processing unit 811 of the root-node 800 is a first path message processing unit which is adapted to deal with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information indicating that the source leaf-node requests the transmission of a signal;
  • the connection request message processing unit 815 of the root-node 800 is a second path message processing unit which is adapted to deal with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information for the modification from the quasi bi-directional connection to a bi-directional connection.
  • the call request message processing unit 911 of the source leaf-node 900 is a fourth path message processing unit which adapted to deal with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information indicating that the source leaf-node requests the transmission of a signal;
  • the connection request message processing unit 912 of the source leaf-node 900 is a fifth path message processing unit that deals with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information for the modification from the quasi bi-directional connection to a bi-directional connection.
  • connection establishing unit 810 of the root-node includes:
  • a call request message processing unit 811 adapted to parse a call request message from the source leaf-node, the call request message containing the instruction information indicating that the source leaf-node requests the transmission of a signal; a call responding message processing unit 812 adapted to generate a call responding message to the source leaf-node according to the instruction information; a call rejecting message processing unit 813 adapted to generate a call rejecting message to the source leaf-node 900 from which the call request message is transmitted; a call request determining unit 814 adapted to determine whether or not to accept the call request from the source leaf-node which transmitting the request message based on local policy, then informs the call responding message processing unit 812 if determining to receive, or informs the call rejecting message processing unit 813 if determining to reject; and a connection request message processing unit 816 adapted to parse the connection request message from the source leaf-node; and a connection responding message processing unit 817 adapted to generate a connection responding message to
  • the signal forwarding unit 820 of the root-node 800 includes: a connection switching unit 821 adapted to switch the connection from the source leaf-node to the root-node, which is along the receiving direction, to the connection that is along the transmitting direction of the multicast tree; and a signal transmitting unit 822 adapted to forward the signal to each destination leaf-node through the connection that is along the transmitting direction of the multicast tree.
  • the connection establishing unit 910 of the source leaf-node 900 includes: a call request message processing unit 911 adapted to generate a call request message to the root-node, the call request message containing the instruction information indicating that the source leaf-node requests the transmission of a signal; a connection request message processing unit 912 adapted to generate a connection request message transmitted to the root-node; and a connection responding message processing unit 914 adapted to parse a connection responding message returned by the root-node.
  • the call request message processing unit 811 of the root-node 800 is a third path message processing unit which is adapted to deal with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information indicating that the source leaf-node requests the transmission of a signal.
  • the call request message processing unit 911 of the source leaf-node 900 is the sixth path message processing unit which is adapted to deal with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information indicating that the source leaf-node requests the transmission of a signal.

Abstract

A method of leaf-node of the multicast tree signal transmission and communication network system and node thereof in the communication network. Establishing the connection between the source leaf-node and root node of the transmitting signal in the multicast tree; the source leaf-node of the transmitting signal in the multicast tree transmits signal to the root node through the established connection; the root node in the multicast tree receives the transmitted signal and transmits the signal to the destination leaf-node in the multicast tree. An establishing method of the preparative bi-directional connection from the root-node to the leaf-node in the multicast tree. When the multicast service supported multicasting tree was established in the connection-oriented network, each leaf-node in the multicast tree may act as the signal source node that send signal to other leaf-nodes in the multicast tree, and it is able to share the multicast tree possessive network resource furthest during the signal transmitting between multi leaf-nodes.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • The present application is a continuation application of PCT application No. PCT/CN2006/003024 filed on Nov. 10, 2006, which claims the priority of the Chinese Patent Application No. 200510101168.2 filed on Nov. 11, 2005, entitled “A Method For Transmitting Signal Between Leaf-Nodes of Multicast Tree in the Communication Network,” both of which are hereby incorporated by reference in their entirety.
  • FIELD OF THE INVENTION
  • The present disclosure relates to multicast service technology, and in particular to a method for transmitting a signal between leaf-nodes of a multicast tree in the communication network, to a communication network system and a node thereof.
  • BACKGROUND OF THE INVENTION
  • Along with the increasing demand for communication services, the demand for multicast services such as video conferencing, Video on Demand (VOD) and multi-lateral database backup has emerged in communication networks. The multicast services require the communication network to provide QoS (Quality of Service) assurance for voice, data, and video services. Usually a multicast tree is established and maintained in the connection-oriented communication network to support these types of multicast services. A multicast tree is a tree-shaped unidirectional connection with a fixed bandwidth, from a source node to a plurality of destination nodes. The source node of a multicast tree is normally named as the root-node node, and the respective destination nodes of the multicast tree are normally named as the leaf-node nodes. The multicast tree can be used to support unidirectional broadcast or multicast services, such as VOD service and the like.
  • At present, an end-to-end connection can be rapidly established in a connection-oriented communication network through the introduction of the control plane technology. Using signaling technology and routing technology of the control plane, it is possible to swiftly establish the multicast tree and efficiently share the network resource. In prior art, all the branches of the multicast tree are unidirectional connections. In order to establish the multicast tree, the unidirectional establishing process needs to be initiated from the root-node to every leaf-node. After all the unidirectional connections have been established, the bandwidth resource on the public path can be shared through a merging process for resources. With the calculation of efficient routing for the root-node, all the unidirectional connections of the multicast tree can efficiently share the bandwidth resource of the public path. As shown in FIG. 1, when the nodes LSR (Label Switch Router) D, and LSR F and LSR G are receiving the multicast signal from LSR A, the node LSR A initiates the establishing process for the unidirectional connection LSP (Label Switch Path) 1 to leaf-node LSR D, through LSR B and LSR C, the establishing process for the unidirectional connection LSP2 to leaf-node LSR F, through LSR B and LSR E, and the establishing process for the unidirectional connection LSP3 to leaf-node LSR G, through LSR B and LSR E. The three unidirectional connections are associated with each other through unique multicast identifier, and a plurality of unidirectional LSPs is merged on the public path to share the transmission resource. The sharing of resource among the above three unidirectional LSPs after their establishment is specifically as follows: LSP 1, LSP 2 and LSP 3 share the label resource (L1, L2) at the entrance and the exit of LSR A, as well as the label resource (L1) at the entrance of LSR B. LSP 2 and LSP 3 share the label resource (L1, L2) at the entrance and the exit of LSR A, the label resource (L1, L3) at the entrance and exit of LSR B, and the label resource (L1) at the entrance of LSR E.
  • In prior art, in order to transmit signal from a leaf-node to other leaf-nodes of the multicast tree, it is usually necessary to form a new multicast tree, taking the leaf-node requesting signal transmission as a root-node, and other leaf-nodes as new leaf-nodes. In this way, the demand to transmit multicast signal from any leaf-node to other appointed leaf-nodes is fulfilled.
  • The above prior art has the following defects:
  • Firstly, in order to transmit signal from a certain leaf-node to other leaf-nodes of the multicast tree, it is usually necessary to form a new multicast tree, taking the leaf-node requesting signal transmission as the root-node. The arrangement can not efficiently utilize the network resource occupied by the current multicast tree, thus is a waste of network resource. Furthermore, in a TDM (Time Division Multiplexing) network such as SDH (Synchronous Digital Hierarchy), where the general connections are bi-directional, if unidirectional connection is established, the time slot resource of another direction is hard to be utilized. Therefore, the network resource will suffer a very low utilization ratio if a new unidirectional multicast tree is established. In addition, sometimes it is impossible to establish a new multicast tree due to various prerequisites to establish connections.
  • Secondly, during the establishment of a new multicast tree in order to transmit signal from a certain leaf-node to other leaf-nodes, it is inevitable to cause an increase of resource overhead on control plane signaling and routing, including the overhead on extended signaling network, and the overhead for the nodes to save and process new signaling and routing information.
  • SUMMARY OF THE INVENTION
  • The present disclosure provides a method for transmitting a signal between leaf-nodes of a multicast tree in the communication network, and provides a communication network system and a node thereof. When the multicast tree that supports multicast service has been established in a connection-oriented network, with a plurality of leaf-nodes participating in the signal transmission together, the network resource occupied by the existing multicast tree can be shared to the maximum.
  • According to one aspect of the present disclosure, the method for transmitting a signal between leaf-nodes of a multicast tree in a communication network includes:
  • establishing a connection from a source leaf-node which transmits a signal, to a root-node in the multicast tree;
  • transmitting, by the source leaf-node of the multicast tree which transmits a signal, a signal, to the root-node through the established connection; and
  • forwarding, by the root-node of the multicast tree, the received signal, to the destination leaf-node of the multicast tree which is adapted to receive the signal.
  • According to another aspect of the present disclosure, a root-node includes:
  • a connection establishing unit, adapted to establish a connection with a source leaf-node of a multicast tree for transmitting a signal;
  • a signal forwarding unit, adapted to forward the signal received from the source leaf-node through the established connection to the destination leaf-node of the multicast tree for receiving the signal.
  • According to a further aspect of the present disclosure, a leaf-node includes:
  • a connection establishing unit, adapted to establish a connection with a root-node of the multicast tree;
  • a signal transmitting unit, adapted to transmit the signal to be transmitted to a destination leaf-node, to the root-node through the established connection.
  • According to a still further aspect of the present disclosure, a communication network system includes a root-node and a leaf-node of a multicast tree, and the connection established from the leaf-node to the root-node.
  • The leaf-node is adapted to transmit a signal to the root-node through the established connection; and the root-node is adapted to forward the signal that is received through the established connection, to the destination leaf-node of the multicast tree for receiving the signal.
  • According to another aspect of the present disclosure, a method for establishing a quasi bi-directional connection between a root-node and a leaf-node of a multicast tree includes:
  • initiating, by a root-node, a request to establish a quasi bi-directional connection to each leaf-node; and
  • establishing quasi bi-directional connections between each leaf-node of the multicast tree and the root-node, in response to the request to establish the quasi bi-directional connections.
  • The present disclosure provides a method for transmitting a signal between leaf-nodes of a multicast tree in the communication network, including the steps of: establishing a connection from the source leaf-node of the multicast tree, which is adapted to transmit a signal, to the root-node; transmitting, by the source leaf-node of the multicast tree for transmitting the signal, the signal to the root-node through the established connection; and forwarding, by the root-node of the multicast tree, the received signal to the destination leaf-node of the multicast tree for receiving the signal, so as to implement the transmission of a signal. The arrangement makes it possible for the leaf-node to transmit the signal to other leaf-nodes in a connection-oriented network, while efficiently taking use of the existing network resources of the multicast tree, and reducing the overhead on signaling to the maximum.
  • BRIEF DESCRIPTIONS OF THE DRAWINGS
  • FIG. 1 is a schematic diagram illustrating the establishment of a multicast tree in prior art;
  • FIG. 2 is a primary flow chart illustrating a method for transmitting a signal between leaf-nodes in the communication network according to an embodiment of the present disclosure;
  • FIG. 3 is a primary flow chart for establishing the quasi bi-directional connection from the root-node to the leaf-node according to an embodiment of the present disclosure;
  • FIG. 4 is a schematic diagram illustrating the object of connection attributes added through extending GMPLS RSVP-TE signaling protocol according to the present disclosure;
  • FIG. 5 is a flow chart illustrating a method for transmitting a signal between the leaf-nodes of the multicast tree according to an embodiment of the present disclosure;
  • FIG. 6 is a schematic diagram illustrating the object of request instruction for the leaf-node added through extending GMPLS RSVP-TE signaling protocol according to an embodiment of the present disclosure;
  • FIG. 7 is a schematic diagram illustrating a practical implementation of the multicast tree according to the present disclosure, which realizes the function that a leaf-node transmits signal to other leaf-nodes of the multicast tree;
  • FIG. 8 is a schematic diagram illustrating the allocation of label resources in the multicast tree shown in FIG. 7;
  • FIG. 9 is a signaling flow chart illustrating a practical implementation that a multicast service is established between the leaf-node LSR D and the root-node LSR A by means of the extended GMPLS RSVP-TE signaling protocol;
  • FIG. 10 is a signaling flow chart illustrating the practical implementation shown in FIG. 7, where the leaf-node LSR F in the multicast tree transmits local user signal to other nodes;
  • FIG. 11 is a flow chart illustrating the practical implementation that a leaf-node establishes a new unidirectional connection to the root-node upon transmitting a user signal;
  • FIG. 12 is a schematic diagram illustrating a practical implementation that the leaf-node transmits a signal through a newly established connection from the leaf-node to the root-node, in accordance with the present disclosure;
  • FIG. 13 is a schematic diagram illustrating the allocation of label resources in the multicast tree shown in FIG. 12;
  • FIG. 14 is a signaling flow chart illustrating the practical implementation that the leaf-node LSR D in the multicast tree transmits local user signal to other nodes of the multicast tree;
  • FIG. 15 is a schematic diagram illustrating a practical implementation of the communication network system according to the present disclosure;
  • FIG. 16 is a structural block diagram for implementing the communication network shown in FIG. 15, in accordance with one embodiment of the present disclosure; and
  • FIG. 17 is a structural block diagram for implementing the communication network shown in FIG. 15, in accordance with another embodiment of the present disclosure.
  • DETAILED DESCRIPTIONS OF THE EMBODIMENTS
  • In embodiments of the present disclosure, when a leaf-node in a multicast tree requests to transmit a signal to other leaf-nodes, a new connection is established between the root-node and the leaf-node or existing connection is modified, so that the signal from the leaf-node can be transmitted to the root-node. Through a local switching process, the root-node switches the signal from the leaf-node to the other leaf-nodes along the direction of the multicast tree. The arrangement makes it possible for a leaf-node to transmit signal to other leaf-nodes using the network resources of the existing multicast tree.
  • Referring to FIG. 2, FIG. 2 is a primary flow chart illustrating a method for transmitting a signal between leaf-nodes in the communication network according to an embodiment of the present disclosure, including the following steps.
  • In step 11, establish a connection from the source leaf-node of the multicast tree, which is adapted to transmit a signal, to the root-node. In practical cases, the established connection can be a bi-directional connection from the root-node to the source leaf-node, or a unidirectional connection that is newly established from the source leaf-node to the root-node.
  • In step 12, the source leaf-node of the multicast tree that is adapted to transmit the signal transmits the signal to the root-node through the established connection.
  • In step 13, after receiving the signal, the root-node of the multicast tree forwards the signal to the destination leaf-node of the multicast tree, which is adapted to receive the signal, thereby implementing the transmission of a signal.
  • The establishment of the connection between the source leaf-node and the root-node described above can be realized by modifying the existing connection from the root-node to the leaf-node. The existing connection is a quasi bi-directional connection from the root-node to the leaf-node, the quasi bi-directional connection having the following attributes.
  • Within the quasi bi-directional connection, the unidirectional connection from the root-node to the leaf-node reserves resource on the control plane, and allocates the resource on the transmission plane; the unidirectional connection from the leaf-node to the root-node only reserves resource on the control plane, and does not allocate the resource on the transmission plane.
  • In the embodiments of the present disclosure, when a leaf-node requests to transmit signal, it is possible to use existing call and connection establishment process to perform control over the unidirectional connection from the leaf-node to the root-node so as to allocate the resource on the transmission plane, thus modifying the quasi bi-directional connection into a bi-directional connection from the root-node to the leaf-node.
  • Referring to FIG. 3, FIG. 3 is a primary flow chart for establishing the quasi bi-directional connection from the root-node to the leaf-node according to an embodiment of the present disclosure, wherein the root-node of the multicast tree initiates the request to establish a quasi bi-directional connection to each leaf-node; each leaf-node of the multicast tree establishes a quasi bi-directional connection with the root-node in response to establish the quasi bi-directional connection. The specific process is as below.
  • In step s11, the root-node determines the quasi bi-directional connection to each leaf-node;
  • In step s12, the root-node transmits to each leaf-node a call request message which contains the instruction information that instructs to establish the quasi bi-directional connection;
  • In step s13, each leaf-node determines the request from the root-node for establishing the quasi bi-directional connection, according to the instruction information, and returns the call responding message to the root-node;
  • In step s14, the root-node transmits to each leaf-node a connection request message which contains the instruction information by which the unidirectional connection from the root-node to the leaf-node reserves the resource on the control plane, and allocates the resource on the transmission plane, while the unidirectional connection from the leaf-node to the root-node only reserves the resource on the control plane, and does not allocate the resource on the transmission plane;
  • In step s15, the leaf-node that has received the connection request message performs actions to reserve corresponding resource according to the instruction information contained in the connection request message, and then returns a connection responding message to the root-node.
  • When actually realizing the above process with signaling, the embodiments of the present disclosure can be achieved through extending RSVP-TE (RSVP Traffic Engineering) signaling protocol of the current GMPLS (Generalized Multi-Protocol Label Switch). For example, the call request message and the connection request message can both use the PATH message of the RSVP-TE protocol of the extended GMPLS, and the call responding message and the connection responding message can both use the Resv message of the extended GMPLS RSVP-TE protocol. As a practical implementation, the PATH message in the extended GMPLS RSVP-TE protocol can be extended to add into an object of connection attributes, which is used to contain an instruction information instructing the establishment of the quasi bi-directional connection, or an instruction information by which the unidirectional connection from the root-node to the leaf-node reserves resource on the control plane, and allocates the resource on the transmission plane, while the unidirectional connection from the leaf-node to the root-node only reserves the resource on the control plane, and does not allocate resource on the transmission plane.
  • To demonstrate that with an actual message expansion of signaling protocol, the embodiments of the present disclosure may introduce a new object of connection attributes, namely, CONNECTIONG_ATTRI, into the current message of GMPLS RSVP-TE signaling protocol.
  • As shown in FIG. 4, the CONNECTIONG_ATTRI object may contain the following components:
  • 1. Length: the length of the object in octet, including the heading part. The length value of the object may be 8;
  • 2. Class-Num: type code, whose value is allocated by the IANA, for example 222;
  • 3. C-Type: subtype code, whose value is allocated by the IANA, for example 1;
  • 4. Up Attri: the attribute of the connection from the source node to the destination node, which may take one of the following values:
      • 0: the connection along the direction is nonexistent (if there is only a unidirectional connection from the destination to the source);
      • 1: reserve source on the control plane, and allocate resource on the transmission plane;
      • 2: reserve source on the control plane, but do not allocate resource on the transmission plane;
      • 3-255: reserved;
  • 5. Down Attri: the attribute of the connection from the destination node to the source node, which may take one of the following values:
      • 0: the connection along the direction is nonexistent (if there is only a unidirectional connection from the source to the destination);
      • 1: reserve source on the control plane, and allocate resource on the transmission plane;
      • 2: reserve source on the control plane, but do not allocate resource on the transmission plane;
      • 3˜255: reserved;
  • 6. Reserved: reserved.
  • Through instruction for the object of connection attributes, it is possible to communicate between the root-node and other nodes, so as to establish the quasi bi-directional connection.
  • Referring to FIG. 5, FIG. 5 is a flow chart illustrating a method for transmitting a signal of the leaf-nodes of the multicast tree according to an embodiment of the present disclosure, including the following primary steps.
  • In step s21, the source leaf-node for transmitting the signal initiates an establishment request to modify the quasi bi-directional connection from the root-node to the source leaf-node, into a bi-directional connection. In the case of the implementation, the source leaf-node for transmitting a signal transmits to the root-node a call request message containing the instruction information indicating that the source leaf-node requests the transmission of a signal. The root-node that has received the call request message determines, according to local policy, whether or not to accept the call request from the source leaf-node. If positive, the root-node determines that the source leaf-node requests the transmission of a signal according to the instruction information, and transmits a responding message back to the source leaf-node. Else, the root-node transmits a call rejecting message to the source leaf-node.
  • In step s22, establish a bi-directional connection from the root-node to the source leaf-node in response to the establishment request from the source leaf-node to modify the quasi bi-directional connection into a bi-directional connection. In the case of the implementation, the root-node transmits a connection request message to the source leaf-node through transit nodes. The connection request message contains the instruction information for modifying the quasi bi-directional connection into a bi-directional connection. The source leaf-node and the transit nodes that have received the connection request message reserve corresponding resources for the bi-directional connection according to the instruction information, and return a responding message to the root-node.
  • In step s23, the source leaf-node transmits message to the root-node through the connection from the source leaf-node to the root-node of the bi-directional connection between the two nodes.
  • In step s24, the root-node switches the connection from the source leaf-node to the root-node, which is along the receiving direction, to the connection that is along the transmitting direction of the multicast tree.
  • In step s25, the root-node forwards the signal to each destination leaf-node through the connection that is along the transmitting direction of the multicast tree.
  • When actually implementing the above process with signaling, it is possible for the embodiment of the present disclosure to be implemented by extending the current GMPLS RSVP-TE signaling protocol. For example, the call request message and connection request message can both use the Path message in the extended GMPLS RSVP-TE protocol, and the call responding message and connection responding message can both use the Resv message in the extended GMPLS RSVP-TE protocol. In one embodiment, the PATH message in the extended GMPLS RSVP-TE protocol can be extended to add into an object of request instruction to which the signal is transmitted by the leaf-node, which is used to contain the instruction information indicating that the source leaf-node requests the transmission of a signal, as well as an object of connection attributes, which is used to contain the instruction information for the modification from the quasi bi-directional connection into the bi-directional connection. The actual implementation of the object of connection attributes has been shown above, and here is an example to demonstrate the implementation of the object of request instruction to which the signal is transmitted by the source leaf-node.
  • The embodiment of the present disclosure may introduce a new object of request instruction to which the signal is transmitted by the leaf-node, namely, SEND_DATA_REQUEST, into the current GMPLS RSVP-TE signaling protocol.
  • As shown in FIG. 6, the SEND_DATA_REQUEST object may contain the following components:
  • 1. Length: the length of the object in octet, including the object's head. The length value of the object may be 12;
  • 2. Class-Num: type code, whose value is allocated by the IANA, for example 223;
  • 3. C-Type: subtype code, whose value is allocated by the IANA, for example 1;
  • 4. SendDataReq: the request instruction for the leaf-node to transmit signal, which may take one of the following values:
      • 0: do not transmit the signal;
      • 1: the leaf-node requests to transmit the signal to other leaf-nodes of the multicast tree;
      • 2˜255: reserved;
  • 5. NodeId: the serial number of the leaf-node that requests to transmit the signal;
  • 6. Reserved: reserved.
  • The root-node that has been instructed by the object of request instruction can communicate with the leaf-node to initiate the transmission of a signal.
  • Referring the FIG. 7, the embodiment will be described as below. FIG. 7 is a schematic diagram illustrating a practical implementation of the multicast tree according to the present disclosure, which realizes the function that a leaf-node transmits signal to other leaf-nodes of the multicast tree.
  • In a connection-oriented network (such as GMPLS), the nodes that participate in the multicast service include LSR A, LSR B, LSR C, LSR D, LSR E, LSR F and LSR G, of which the LSR A is the root-node of the multicast tree. As each leaf-node joins the multicast tree, it first transmits an end-to-end request towards the root-node of the multicast tree. The establishment process for the quasi bi-directional connection from the root-node to the leaf-node is initiated only following the completion of the call. After each leaf-node has joined the call of the multicast tree and the connection signaling process has been completed, the leaf-nodes of the multicast tree LSR D, LSR F and LSR G have respectively established a quasi bi-directional connection with the root-node LSR A, namely, LSP1, LSP2, LSP3. Of these connections, LSP1,LSP2 and LSP3 share the resource between LSR A and LSR B; LSP2 and LSP 3 share the resource through LSR A, LSR B and LSR E. As shown in FIG. 7, the quasi bi-directional connection LSP1 includes the unidirectional connection 1 from LSR A to LSR D and the unidirectional connection 2 from LSR D to LSR A. Similarly, the quasi bi-directional connection LSP2 includes unidirectional connections 3 and 4, and the quasi bi-directional connection LSP3 includes unidirectional connections 5 and 6. Among the quasi bi-directional connections LSP1, LSP2 and LSP3, the unidirectional connections 1, 3 and 5 reserve the resource on the control plane and allocate the resource on the transmission plane, while the unidirectional connections 2, 4 and 6 reserve the resource on the control plane but do not allocate the resource on the transmission plane. After the connections LSP1, LSP2 and LSP3, which possess the above attributes, have been established, all of the leaf-nodes LSR D, LSR F and LSR G can receive the user signal 10 transmitted from the root-node LSR A.
  • When LSR D requests to transmit a signal to other leaf-nodes of the multicast tree, the current signaling protocol can be extended to modify the connection attributes of LSP1, so that the unidirectional connection 2 reserves resource on the control plane and allocates resource on the transmission plane, thus modifying the quasi bi-directional connection LSP1 into a bi-directional connection. In addition, the root-node LSR A switches from the unidirectional connection 2 of the LSP1 to the unidirectional connection 1 through local process 7. At this time, the user signal 11 of LSR D can be transmitted to all leaf-nodes, but the user signal 10 of LSR A can no longer be transmitted at the same time.
  • In the case that any other leaf-node requires to perform the transmission of a signal, for example, if the node LSR F requests LSR A to transmit a signal, LSR A first modifies the connection attributes of LSP1 related to LSR D that is currently transmitting signal, recovering LSP1 to its original status, that is, the unidirectional connection 2 reserves the resource on the control plane and releases the allocated resource on the transmission plane, while the unidirectional connection 1 retains its current status. The connection attribute of LSP2 is modified, that is, the unidirectional connection 4 reserves the resource on the control plane and allocates the resource on the transmission plane. Of course, the modifications on the connection attributes of LSP1 and LSP2 can also be performed simultaneously, or the connection attribute of LSP2 is first modified and then the connection attribute of LSP1 is modified. After the modifications for the connection attributes of LSP1 and LSP2 is finished, the root-node LSR A switches from the unidirectional connection 4 of the LSP2 to the unidirectional connection 3 through local process 7. At this time, the user signal 12 of LSR F can be transmitted to all leaf-nodes, but the user signal 11 of LSR D can no longer be transmitted at the same time.
  • In the embodiment, the establishment process of the multicast tree includes the following steps.
  • 1. The root-node LSR A of a certain multicast service is determined in a connection-oriented network;
  • 2. A leaf-node LSR D demanding to join the multicast tree transmits a call request to the root-node LSR A;
  • 3. LSR A determines that LSR D can be added into the multicast tree, and responds the call request from LSR D;
  • 4. Taking efficient use of the current allocated resource in the multicast tree, LSR A works out a best path to reach the leaf-node LSR D: LSRA-LSR B-LSR C-LSR D;
  • 5. After LSR A determines the best path, the connection path is associated with a unique multicast identifier in the multicast tree, and transmits a signaling message that requests to establish a quasi bi-directional LSP with taking LSR D as the destination node. The connection attribute parameters contained in the parameters of the connection request message of the quasi bi-directional LSP connection has the following characteristics: a) the unidirectional connection from the root-node to the leaf-node reserves the resource on the control plane and allocates the resource on the transmission plane; b) the unidirectional connection from the leaf-node to the root-node reserves the resource on the control plane but does not allocate the resource on the transmission plane.
  • In the above process, the new parameters for connection attributes in step 5 can be contained in CONNECTIONG_ATTRI, an object of connection attributes that is newly introduced into the current (G)MPLS signaling protocol. For example, the quasi bi-directional LSP connection with above attributes can be established using the signaling mechanism defined in the current ITU-T Recommendation G7713.2.
  • After the connection is established, the leaf-node LSR D can receive user signal 10 from the root-node, but at this time, the leaf-node LSR D can not transmit local user signal 11 to other leaf-nodes.
  • Upon completion of the establishment of the multicast tree according to the above steps, the allocation of label resources is shown in FIG. 8. The multicast tree includes three quasi bi-directional connections, of which LSP1, LSP2 and LSP3 share the bi-directional label resources (L2, L1) between LSR A and LSR B. Along the direction from LSR A to the leaf-node, LSR B exchanges the local label L1 to the exit labels L2 and L3. Along another direction, however, LSR B only maintains the simultaneous exchanging relationships from the entrance labels L2 and L3 to the exit label L1 on the control plane, while it does not actually perform the exchange action on the transmission plane. That is, the bi-directional labels from the root-node to the leaf-node is reserved on the control plane, but only unidirectional labels from the root-node to the leaf-node is allocate on the transmission plane, and the unidirectional labels from the leaf-node to the root-node is not allocated on the transmission plane.
  • LSP2 and LSP3 share the bi-directional label resources (L2, L1) between LSR A and LSR B, and the bi-directional label resources (L3, L1) between LSR B and LSR E. Along the direction from LSR A to the leaf-node, LSR E exchanges the local label L1 to the exit labels L2 and L3. Along another direction, however, LSR E only maintains the simultaneous exchanging relationships from the entrance labels L2 and L3 to the exit label L1 on the control plane, while it does not actually perform the exchange action on the transmission plane.
  • As shown in FIG. 9, an embodiment in which a multicast service is established between the leaf-node LSR D and the root-node LSR A by means of the extended GMPLS RSVP-TE signaling protocol includes the following signaling steps.
      • 91. PATH message, the call request message from LSR D to LSRA;
      • 92. RESV message, the call responding message from LSR A to LSR D;
      • 93. PATH message, the bi-directional connection request message from LSR A to LSR B, which contains the extended object CONNECTIONG_ATTRI according to the embodiment of the present disclosure, where Up Attri=1, Down Attri=2. LSR A correspondingly reserves and allocates local resources based on the values of the connection attributes;
      • 94. PATH message, the connection request message from LSR B to LSR C. LSR B correspondingly reserves and allocates local resources based on the values of the connection attributes and forwards the CONNECTIONG_ATTRI object to downstream;
      • 95. PATH message, the connection request message from LSR C to LSR D. LSR C correspondingly reserves and allocates local resources based on the values of the connection attributes and forwards the CONNECTIONG_ATTRI object to downstream;
      • 96. RESV message. After receiving the PATH message, LSR D correspondingly reserves and allocates local resources based on the values of the connection attributes and transmits a connection responding message to upstream;
      • 97. RESV message. After receiving the RESV message, LSR C correspondingly reserves and allocates local resources based on the values of the connection attributes and transmits a connection responding message to upstream;
      • 98. RESV message. After receiving the RESV message, LSR B correspondingly reserves and allocates local resources based on the values of the connection attributes and transmits a connection responding message to upstream;
      • 99. After receiving the RESV message, LSR A correspondingly reserves and allocates local resources based on the values of the connection attributes and the connection is established.
  • In the multicast tree of the embodiment of the present disclosure, if the leaf-node LSR F requests to transmit local user signal 12 to other leaf-nodes, the leaf-node LSR F for transmitting the signal transmits a call request message to the root-node LSR A. The request message contains the instruction information indicating that the leaf-node LSR F demands to transmit the signal. After receiving the call request message from the leaf-node LSR F, the root-node LSR A determines whether the call request can be permitted based on the local policy. If the call request is not permitted, then LSR A transmits a call rejecting message to the leaf-node LSR F, and the request process is over. If the root-node LSR A determines to accept the request from the leaf-node LSR F, the bi-directional connection, which is related to the leaf-node LSR D which is currently transmitting signal, is determined as LSP1. The modification for the attributes of LSP1 is implemented through transmitting a modifying message that contains the CONNECTIONG_ATTRI object to LSR D. Namely, the unidirectional connection 2, which is from the leaf-node LSR D that is currently transmitting signal, to the root-node LSR A, releases the resource it has occupied on the transmission plane, and maintains a reserved status on the control plane. While the unidirectional connection 1, which is from LSR A to LSR D, maintains its original status. After determining that the modification signaling process for the connection status of LSP1 is complete, LSR A transmits a connection request message which contains the CONNECTIONG_ATTRI object to implement the modification on the attributes of LSP2, to the leaf-node LSR F that requests the transmission of a signal, so that resources are allocated for the unidirectional connection 4 from the leaf-node LSR F to the root-node LSR A. Upon receiving the message that the modification on the connection is complete, the information from the unidirectional of the root-node LSR F is locally switched to the unidirectional connection 3 which is along the transmitting direction of the root-node LSR A. In this way, the leaf-node LSR F can transmit the signal 12 to other leaf-nodes of the multicast tree, while the transmission of the user signal 11 of LSR D is stopped.
  • As shown in FIG. 10, the extended GMPLS RSVP-TE signaling protocol is used, and the signaling flow for requesting the transmission of a signal from the leaf-node LSR F to the root-node LSR A is as follows.
  • 101. PATH message, the call request message from LSR F to LSR A, which contains the extended object SEND_DATA_REQUEST according to the embodiment of the present disclosure;
  • 102. RESV message: the call responding message from LSR A to LSR F;
  • 103. PATH message. After determining the call request, LSR A determines that LSR D is the node that is currently transmitting signal, and then LSR A transmits to LSR B a connection request message aiming at LSP1. The LSP1 is the connection between LSR A and LSR D. The connection request message contains the extended object CONNECTIONG_ATTRI according to the present disclosure, where Up Attri=1, Down Attri=2. According to the new connection attributes, LSR A releases the resource that the unidirectional connection 2 of LSP 1 has allocated on the transmission plane.
  • 104. PATH message, which is the connection request message from LSR B to LSR C. LSR B releases the resource that the unidirectional connection 2 of LSP1 has allocated on the transmission plane based on the new values of the connection attributes and forwards the CONNECTIONG_ATTRI object to downstream;
  • 105. PATH message, which is the connection request message from LSR C to LSR D. LSR C releases the resource that the unidirectional connection 2 of LSP1 has allocated on the transmission plane based on the new values of the connection attributes and forwards the CONNECTIONG_ATTRI object to downstream;
  • 106. RESV message. After receiving the PATH message, LSR D releases the resource that the unidirectional connection 2 of LSP1 has allocated on the transmission plane based on the new values of the connection attributes and transmits a connection responding message to upstream;
  • 107. RESV message. After receiving the RESV message, LSR C forwards the connection responding message to upstream;
  • 108. RESV message. After receiving the RESV message, LSR B forwards the connection responding message to upstream;
  • 103a. PATH message. LSR A transmits to LSR B a connection request message aiming at LSP2. LSP2 is the connection between LSR A and LSR F. The connection request message contains the extended object CONNECTIONG_ATTRI according to the present disclosure, where Up Attri=1, Down Attri=1. According to the new value of the connection attributes, LSR A allocates resource for the unidirectional connection 4 of LSP2 on the transmission plane.
  • 104a. PATH message, which is the connection request message from LSR B to LSR E. According to the new value of the connection attributes, LSR B allocates resource for the unidirectional connection 4 of LSP2 on the transmission plane, and forwards the CONNECTIONG_ATTRI object to downstream;
  • 105a. PATH message, which is the connection request message from LSR E to LSR F. According to the new value of the connection attributes, LSR E allocates resource for the unidirectional connection 4 of LSP2 on the transmission plane, and forwards the CONNECTIONG_ATTRI object to downstream;
  • 106a. RESV message. After receiving the PATH message, LSR F allocates resource for the unidirectional connection 4 of LSP2 on the transmission plane according to the new value of the connection attributes, and transmits a connection responding message to upstream;
  • 107a. RESV message. After receiving the RESV message, LSR E forwards the connection responding message to upstream;
  • 108a. RESV message. After receiving the RESV message, LSR B forwards the connection responding message to upstream;
  • 109a. After receiving the RESV message, LSR A performs local switching process by which the connection 4 that is along the receiving direction of LSP2 is switched to the connection 3 that is along the transmitting direction. When the modification for the connection is complete, LSR F can transmit the signal 12 to other leaf-nodes.
  • Among the above steps, it is feasible that the steps 104, 105, 106, 107, 108 are performed first, and then the steps 104 a, 105 a, 106 a, 107 a, 108 a are performed, or these steps can also be performed simultaneously, or the steps 104 a, 105 a, 106 a, 107 a, 108 a are performed first, and then the steps 104, 105, 106, 107, 108 are performed.
  • According to the above embodiments, the existing quasi bi-directional connection is modified to establish a bi-directional connection from the root-node to the leaf-node, so as to implement the transmission of a signal among leaf-nodes. In a connection-oriented network, in the case of the unidirectional multicast tree established by current method from the root-node to a plurality of leaf-nodes, according to the embodiment of the present disclosure, the transmission of a signal may be implemented by establishing unidirectional connection from the source leaf-node to the root-node. When a leaf-node demands to transmit local user signal to other leaf-nodes of the multicast tree, the source leaf-node that transmits the signal initiates a request for establishing a connection to the root-node. In response to the request for establishing the connection from the source leaf-node, the connection from the source leaf-node to the root-node is established; then the root-node switches the newly established unidirectional connection to the connection along the transmitting direction of the multicast tree. At this time, the leaf-node can transmit local user signal to other leaf-nodes of the multicast tree
  • Referring to FIG. 11, FIG. 11 is a flow chart illustrating the practical implementation that a leaf-node establishes a new unidirectional connection to the root-node upon transmitting a user signal, including the following primary steps.
  • In step s31, the source leaf-node that transmits the signal transmits to the root-node a call request message which contains the instruction information indicating that the source leaf-node requests the transmission of a signal.
  • In step s32, the root-node that has received the call request message determines that the source leaf-node requests the transmission of a signal according to the instruction information, and returns a call responding message back to the source leaf-node.
  • In step s33, the source leaf-node transmits a connection request message to the root-node.
  • In step s34, the root-node returns a connection responding message back to the source leaf-node to complete the establishment of the connection.
  • In step s35, the source leaf-node transmits the signal to the root-node through the connection from the source leaf-node to the root-node.
  • In step s36, the root-node switches the connection from the source leaf-node to the root-node, which is along the receiving direction, to the connection that is along the transmitting direction of the multicast tree.
  • In step s37, the root-node forwards the signal to each destination leaf-node through the connection that is along the transmitting direction of the multicast tree.
  • When the above process is implemented by means of signaling, the present disclosure can be implemented by extending the current GMPLS RSVP-TE signaling protocol. For example, the call request message and the connection request message can both be the PATH message in the extended GMPLS RSVP-TE protocol, and the call responding message and the connection responding message can both be the Resv message in the extended GMPLS RSVP-TE protocol. As a practical implementation for the message, the PATH message in the extended GMPLS RSVP-TE protocol can be extended to add into an object of request instruction SEND_DATA REQUEST of the leaf-node for transmitting the signal. The PATH message is used to contain the instruction information indicating that the source leaf-node requests transmission of a signal. The actual implementation of the object of request instruction for a leaf-node to transmit signal has been described above, so there is no need for repetition here.
  • The following is an example to demonstrate the process. As shown in FIG. 12, all nodes that the multicast tree transits include: LSR A, LSR B, LSR C, LSR D, LSR E, LSR F and LSR G, of which LSR A is the root-node, while LSR D, LSR F and LSR G are the leaf-nodes. According to the current method to establish a multicast tree, unidirectional connections from LSR A to the leaf-nodes are established respectively, including LSP1 to the leaf-node LSR D, LSP2 to the leaf-node LSR F, and LSP3 to the leaf-node LSR G. A merging process for the three LSPs is performed on the public path in order to share resources. After the unidirectional connections in the multicast tree are established, the allocation of label resources is shown in the 131 part of FIG. 13. The unidirectional connections LSP1, LSP2 and LSP3 share the resource between LSR A and LSR B, and LSR B exchanges the local entrance label L1 to the exit labels L2 and L3 simultaneously. The unidirectional connections LSP2 and LSP3 share the resource among LSR A, LSR B and LSR E, and LSR E exchanges the local entrance label L1 to the exit labels L2 and L3 simultaneously. At this time, the root-node LSR A exchanges the local user signal 10 from the local entrance label L1 to the local exit label L2. The leaf-nodes LSR D, LSR F and LSR G can now receive the local user signal 10 from the root-node LSR A through the multicast tree.
  • As shown in FIG. 12, when the leaf-node LSR D demands to transmit the local user signal 11 to other leaf-nodes, LSR D initiates a request to LSR A for a unidirectional connection, and establishes that a unidirectional connection LSP4 from LSR D to LSR A, through a node LSR H in the network. After the unidirectional connection LSP4 is established, the allocation of label resources is shown in the 130 part of FIG. 13. The leaf-node LSR D maps the local user signal 11 to be transmitted into the local entrance label L2, and exchanges the entrance label L2 to the exit label L3. LSR H exchanges the entrance label L2 to the exit label L1, and LSR A allocates the entrance label L3 for the unidirectional connection LSP4. LSR A locally exchanges the entrance label L3 to the exit label L2 (as the process 7 in FIG. 12), and deletes the existing local exchanging relationship from the entrance label L1 to the exit label L2. At this time, the local user signal 11 from LSR D can be transmitted to both leaf-nodes LSR F and LSR G, through the cooperation of the newly established unidirectional connection LSP4 and the original multicast tree. The local user signal 10 from LSR A may no longer be transmitted to other leaf-nodes of the multicast tree.
  • As shown in FIG. 14, the steps for the leaf-node LSR D to transmit the local user signal 11 to other leaf-nodes of the multicast tree using the GMPLS RSVP-TE signaling protocol are as follows.
  • 141. LSR D transmits the call request message PATH to LSR A, the call request message PATH containing the object of request instruction SEND_DATA REQUEST that the leaf-node LSR D requests transmission of a signal to transmit the local user signal 11 to other leaf-nodes of the multicast tree;
  • 142. After determining to receive the call request, LSR A transmits the call responding message RESV to LSR D;
  • 143. LSR D can establish unidirectional connection LSP to LSR A via LSR H through route querying process, and transmits a PATH message to LSR H for requesting to establish a unidirectional connection from LSR D to LSR A;
  • 144. LSR H transmits a PATH message to LSR A for requesting to establish a unidirectional connection from LSR D to LSR A;
  • 145. LSR A allocates local entrance label L3 for that unidirectional connection upon receiving the PATH message requesting the unidirectional connection, and transmits a connection responding message RESV to LSR H;
  • 146. LSR H allocates local entrance label L2 and exit label L1 for the unidirectional connection upon receiving the connection responding message, and transmits a connection respond message RESV to LSR D;
  • 147. LSR D allocates local entrance label L2 and exit label L3 for the unidirectional connection upon receiving the connection responding message, and transmits a connection confirming message Confirm to LSR H;
  • 148. LSR H forwards the Confirm message to LSR A after necessary local processes (such as the startup of monitoring and alarm process), upon receiving the Confirm message;
  • 149. LSR A confirms the unidirectional connection from LSR D to LSR A to be established successfully after receiving the Confirm message; LSR A exchanges the local entrance label L3 to the exit label L2, and deletes the original exchanging relationship from the entrance label L1 to the exit label L2.
  • After the above steps are complete, the leaf-node LSR D of the multicast tree can transmit the local user signal 11 to other leaf-nodes of the multicast tree.
  • Referring to FIG. 15, FIG. 15 is a schematic diagram illustrating a practical implementation of the communication network system according to the present disclosure.
  • The communication network includes the root-node 800 and the leaf-node 900 in the multicast tree. When the leaf-node 900 transmits signal to other leaf-node of the multicast tree, it can be called as source leaf-node. Between the leaf-node 900 and the root-node 800, there is a connection from the leaf-node 900 to the root-node 800. The leaf-node 900 transmits a signal to the root-node 800 through the established connection, and the root-node 800 forwards the signal received by the established connection to the destination leaf-nodes of the multicast tree for receiving the signal (not shown in the figure).
  • In the embodiment, there are various forms to establish the connection from the leaf-node to the root-node. For example, the connection can be established by modifying the quasi bi-directional connection from the root-node to each leaf-node; or by establishing a new unidirectional connection from the leaf-node to the root-node when requiring the transmission of a signal.
  • The root-node 800 includes: a connection establishing unit 810 adapted to establish the connection with the source leaf-node 900 which transmit a signal in the multicast tree; and a signal forwarding unit 820 adapted to forward the signal received from the source leaf-node 900 through the established connection to the destination leaf-nodes of the multicast tree for receiving the signal.
  • The source leaf-node 900 includes: a connection establishing unit 910 adapted to establish a connection to the root-node 800 in the multicast tree; and a signal transmitting unit 920 adapted to transmit the signal that needs to reach the destination leaf-nodes of the multicast tree to the root-node 800 through the established connection.
  • As shown in FIG. 16, in one embodiment, the connection establishing unit 810 of the root-node 800 includes: a call request message processing unit 811 adapted to parse the call request message from the source leaf-node 900, the call request message containing the instruction information indicating that the source leaf-node requests the transmission of a signal; a call responding message processing unit 812 adapted to generate the call responding message to the source leaf-node 900 according to the instruction information; a call rejecting message processing unit 813 adapted to generate the call rejecting message to the source leaf-node 900 from which the call request message is transmitted; a call request determining unit 814 adapted to determine whether or not to accept the call request from the source leaf-node which transmitting the request message based on local policy, then informs the call responding message processing unit 812 if determining to receive, or informs the call rejecting message processing unit 813 if determining to reject; and a connection request message processing unit 815 adapted to generate a connection request message to the source leaf-node 900 through transit nodes (not shown in the figure), the connection request message containing the instruction information that requests to modify the quasi bi-directional connection into a bi-directional connection.
  • The signal forwarding unit 820 of the root-node 800 includes: a connection switching unit 821 adapted to switch the connection from the source leaf-node to the root-node, which is along the receiving direction, to the connection that is along the transmitting direction of the multicast tree; and a signal transmitting unit 822 adapted to forward the signal to each destination leaf-node through the connection that is along the transmitting direction of the multicast tree.
  • The connection establishing unit 910 of the source leaf-node includes: a call request message processing unit 911 adapted to generate a call request message to the root-node 800, the call request message containing the instruction information indicating that the source leaf-node requests the transmission of a signal; a connection request message processing unit 912 adapted to parse the connection request message which is transmitted by the root-node 800 through transit nodes, the connecting request message containing the instruction information that requests to modify the quasi bi-directional connection into a bi-directional connection; and a bi-directional connection processing unit 913 adapted to reserve resources according to the instruction information, and return a connection responding message to the root-node.
  • In the embodiment, the call request message processing unit 811 of the root-node 800 is a first path message processing unit which is adapted to deal with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information indicating that the source leaf-node requests the transmission of a signal; the connection request message processing unit 815 of the root-node 800 is a second path message processing unit which is adapted to deal with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information for the modification from the quasi bi-directional connection to a bi-directional connection.
  • Accordingly, the call request message processing unit 911 of the source leaf-node 900 is a fourth path message processing unit which adapted to deal with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information indicating that the source leaf-node requests the transmission of a signal; the connection request message processing unit 912 of the source leaf-node 900 is a fifth path message processing unit that deals with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information for the modification from the quasi bi-directional connection to a bi-directional connection.
  • In another embodiment, the connection establishing unit 810 of the root-node includes:
  • a call request message processing unit 811 adapted to parse a call request message from the source leaf-node, the call request message containing the instruction information indicating that the source leaf-node requests the transmission of a signal; a call responding message processing unit 812 adapted to generate a call responding message to the source leaf-node according to the instruction information; a call rejecting message processing unit 813 adapted to generate a call rejecting message to the source leaf-node 900 from which the call request message is transmitted; a call request determining unit 814 adapted to determine whether or not to accept the call request from the source leaf-node which transmitting the request message based on local policy, then informs the call responding message processing unit 812 if determining to receive, or informs the call rejecting message processing unit 813 if determining to reject; and a connection request message processing unit 816 adapted to parse the connection request message from the source leaf-node; and a connection responding message processing unit 817 adapted to generate a connection responding message to the source leaf-node so as to finish the establishment of the connection.
  • The signal forwarding unit 820 of the root-node 800 includes: a connection switching unit 821 adapted to switch the connection from the source leaf-node to the root-node, which is along the receiving direction, to the connection that is along the transmitting direction of the multicast tree; and a signal transmitting unit 822 adapted to forward the signal to each destination leaf-node through the connection that is along the transmitting direction of the multicast tree.
  • The connection establishing unit 910 of the source leaf-node 900 includes: a call request message processing unit 911 adapted to generate a call request message to the root-node, the call request message containing the instruction information indicating that the source leaf-node requests the transmission of a signal; a connection request message processing unit 912 adapted to generate a connection request message transmitted to the root-node; and a connection responding message processing unit 914 adapted to parse a connection responding message returned by the root-node.
  • In the embodiment, the call request message processing unit 811 of the root-node 800 is a third path message processing unit which is adapted to deal with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information indicating that the source leaf-node requests the transmission of a signal.
  • The call request message processing unit 911 of the source leaf-node 900 is the sixth path message processing unit which is adapted to deal with the PATH message of the extended GMPLS RSVP-TE protocol, the PATH message containing the instruction information indicating that the source leaf-node requests the transmission of a signal.
  • The present disclosure is disclosed by, but not limited to, above exemplary embodiments. Any modifications, variations, and/or improvements in the scopes of the concepts and principles of the present disclosure shall fall within the scope of the appended claims of the present disclosure.

Claims (19)

1. A method for transmitting a signal between leaf-nodes of a multicast tree in a communication network, comprising:
establishing a connection from a source leaf-node which transmits a signal, to a root-node in the multicast tree;
transmitting, by the source leaf-node, the signal to the root-node through the established connection; and
forwarding, by the root-node of the multicast tree, the received signal to a destination leaf-node of the multicast tree which is adapted to receive the signal.
2. The method according to claim 1, wherein a quasi bi-directional connection from the root-node to each leaf-node is established in the multicast tree; and the establishing a connection from a source leaf-node which transmits a signal, to a root-node in a multicast tree, comprises:
initiating, by the source leaf-node, an establishment request to modify the quasi bi-directional connection from the root-node to the source leaf-node into a bi-directional connection; and
establishing the bi-directional connection from the root-node to the source leaf-node in response to the establishment request.
3. The method according to claim 1, wherein, the establishing a connection from a source leaf-node which transmits a signal, to a root-node in a multicast tree, comprises:
initiating, by the source leaf-node, a connection establishment request to the root-node;
establishing the connection from the source leaf-node to the root-node in response to the connection establishment request.
4. The method according to claim 1, wherein the establishing a connection from a source leaf-node which transmits a signal, to a root-node in a multicast tree, comprises:
transmitting, by the source leaf-node, a call request message which contains the instruction information indicating that the source leaf-node requests the transmission of a signal, to the root-node; and
determining, by the root-node that has received the call request message, the source leaf-node requesting the transmission of the signal based on the instruction information, and transmitting a call responding message to the source leaf-node.
5. The method according to claim 4, wherein before the determining, by the root-node, the source leaf-node requesting the transmission of the signal based on the instruction information, and transmitting a call responding message to the source leaf-node, the method further comprises:
determining, by the root-node that has received the call request message, whether or not to accept the call request from the source leaf-node according to local policy; if determining not to accept the call request from the source leaf-node based on the local policy, then the root-node transmits a call rejecting message to the source leaf-node.
6. The method according to claim 2, wherein the establishing the bi-directional connection from the root-node to the source leaf-node in response to the establishment request, comprises:
transmitting, by the root-node, a connection request message to the source leaf-node through a transit node, the connection request message containing the instruction information indicating the request to modify the quasi bi-directional connection into the bi-directional connection; and
reserving, by the source leaf-node and the transit node that have received the connection request message, resource for the bi-directional connection, according to the instruction information, and returning a connection responding message back to the root-node.
7. The method according to claim 3, wherein the establishing the connection from the source leaf-node to the root-node in response to the connection establishment request, comprises:
transmitting, by the source leaf-node, a connection request message to the root-node; and
returning, by the root-node, a connection responding message to the source leaf-node so as to complete the establishment of the connection.
8. The method according to claim 1, wherein the forwarding, by the root-node, the received signal to a destination leaf-node of the multicast tree which is adapted to receive the signal, comprises:
switching, by the root-node, the connection from the source leaf-node to the root-node that is along the receiving direction, to the connection that is along the transmitting direction of the multicast tree; and
forwarding, by the root-node, the signal to each destination leaf-node through the connection that is along the transmitting direction of the multicast tree.
9. A method for establishing a quasi bi-directional connection between a root-node and a leaf-node of a multicast tree, comprising:
initiating, by a root-node of the multicast tree, a request to establish a quasi bi-directional connection to each leaf-node of the multicast tree; and
establishing, by each leaf-node of the multicast tree, a quasi bi-directional connection with the root-node respectively in response to the request for establishing the quasi bi-directional connection.
10. The method according to claim 9, wherein the establishing, by each leaf-node of the multicast tree, a quasi bi-directional connection with the root-node respectively in response to the request for establishing the quasi bi-directional connection, comprises:
transmitting, by the root-node, a connection request message to each leaf-node, the connection request message containing instruction information indicating that the unidirectional connection from the root-node to the leaf-node reserves resource on the control plane and allocates resource on the transmission plane, while the unidirectional connection from the leaf-node to the root-node only reserves the resource on the control plane and does not allocate the resource on the transmission plane; and
reserving, by the leaf-node that has received the connection request message, corresponding resource according to the instruction information in the connection request message, and returning a connection responding message back to the root-node.
11. A root-node, comprising:
a connection establishing unit adapted to establish a connection to a source leaf-node that transmits a signal in a multicast tree; and
a signal forwarding unit adapted to forward the signal received from the source leaf-node through the established connection to a destination leaf-node of the multicast tree which is adapted to receive the signal.
12. The root-node according to claim 11, wherein the connection establishing unit comprises:
a call request message processing unit adapted to parse a call request message from the source leaf-node, the call request message containing instruction information indicating that the source leaf-node requests the transmission of the signal;
a call responding message processing unit adapted to generate a call responding message to be transmitted to the source leaf-node according to the instruction information; and
a connection request message processing unit adapted to generate a connection request message transmitted to the source leaf-node through a transit node, the connection request message containing instruction information that requests to modify a quasi bi-directional connection into a bi-directional connection.
13. The root-node according to claim 11, wherein the connection establishing unit comprises:
a call request message processing unit adapted to parse a call request message from the source leaf-node, the call request message containing instruction information indicating that the source leaf-node requests the transmission of the signal;
a call responding message processing unit adapted to generate a call responding message to be transmitted to the source leaf-node according to the instruction information;
a connection request message processing unit adapted to parse a connection request message from the source leaf-node; and
a connection responding message processing unit adapted to generate a connection responding message to transmitted to the source leaf-node so as to finish the establishment of the connection.
14. The root-node according to claim 11, wherein the signal forwarding unit comprises:
a connection switching unit adapted to switch the connection from the source leaf-node to the root-node that is along the receiving direction, to the connection that is along the transmitting direction of the multicast tree; and
a signal transmitting unit adapted to forward the signal to each destination leaf-node through the connection that is along the transmitting direction of the multicast tree.
15. A leaf-node, comprising:
a connection establishing unit adapted to establish a connection to a root-node of a multicast tree; and
a signal transmitting unit adapted to transmit a signal to be transmitted to a destination leaf-node of the multicast tree, to the root-node through the established connection.
16. The leaf-node according to claim 15, wherein the connection establishing unit comprises:
a call request message processing unit adapted to generate a call request message transmitted to the root-node, the call request message containing instruction information indicating that the source leaf-node requests the transmission of the signal;
a connection request message processing unit adapted to parse a connection request message transmitted by the root-node through a transit node, the connection request message containing instruction information that requests to modify a quasi bi-directional connection into a bi-directional connection; and
a bi-directional connection processing unit adapted to reserve resources for the bi-directional connection according to the instruction information, and return a connection responding message to the root-node.
17. The leaf-node according to claim 15, wherein the connection establishing unit comprises:
a call request message processing unit adapted to generate a call request message transmitted to the root-node, the call request message containing instruction information indicating that the source leaf-node requests the transmission of the signal;
a connection request message processing unit adapted to generate a connection request message transmitted to the root-node; and
a connection responding message processing unit adapted to parse a connection responding message returned by the root-node.
18. A communication network system, comprising a root-node and a leaf-node of a multicast tree, wherein a connection from the leaf-node to the root-node is established between the leaf-node and the root-node;
the leaf-node is adapted to transmit a signal to the root-node through the established connection; and the root-node is adapted to forward the signal received through the connection to a destination leaf-node of the multicast tree which is adapted to receive the signal.
19. The communication network system according to claim 18, wherein the connection from the leaf-node to the root-node comprises either a connection from the leaf-node to the root-node after the quasi bi-directional connection from the root-node to each leaf-node is modified into a bi-directional connection, or a unidirectional connection from the leaf-node to the root-node that is newly established upon transmitting the signal.
US12/118,509 2005-11-11 2008-05-09 Communication network system and signal transmission method between leaf-nodes of multicast tree and node thereof Abandoned US20080212496A1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CNB2005101011682A CN100563203C (en) 2005-11-11 2005-11-11 The method that multicast tree leaf node network element signal transmits in the communication network
CN200510101168.2 2005-11-11
PCT/CN2006/003024 WO2007054032A1 (en) 2005-11-11 2006-11-10 Communication network system and leaf-node network element of the multicasting tree signal transmission method and node network element thereof

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003024 Continuation WO2007054032A1 (en) 2005-11-11 2006-11-10 Communication network system and leaf-node network element of the multicasting tree signal transmission method and node network element thereof

Publications (1)

Publication Number Publication Date
US20080212496A1 true US20080212496A1 (en) 2008-09-04

Family

ID=38022977

Family Applications (1)

Application Number Title Priority Date Filing Date
US12/118,509 Abandoned US20080212496A1 (en) 2005-11-11 2008-05-09 Communication network system and signal transmission method between leaf-nodes of multicast tree and node thereof

Country Status (4)

Country Link
US (1) US20080212496A1 (en)
EP (1) EP1953956B1 (en)
CN (1) CN100563203C (en)
WO (1) WO2007054032A1 (en)

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090077237A1 (en) * 2007-09-03 2009-03-19 Alcatel Lucent Method for establishing a bidirectional point-to-point connection
US20090086633A1 (en) * 2007-10-02 2009-04-02 Chenjiang Hu Using A Link-State Advertisement To Inform Nodes Of The Availability Of Traffic Management Resources
US20090086632A1 (en) * 2007-09-28 2009-04-02 Folkes Ronald P Using A Link Attribute To Inform Nodes Of The Availability Of Traffic Management Resources
US20130058208A1 (en) * 2010-07-06 2013-03-07 Benjamin L. Pfaff Fault tolerant managed switching element architecture
US8964528B2 (en) 2010-07-06 2015-02-24 Nicira, Inc. Method and apparatus for robust packet distribution among hierarchical managed switching elements
US20150124642A1 (en) * 2013-11-05 2015-05-07 Cisco Technology, Inc. Running link state routing protocol in clos networks
US9432204B2 (en) 2013-08-24 2016-08-30 Nicira, Inc. Distributed multicast by endpoints
US9602392B2 (en) 2013-12-18 2017-03-21 Nicira, Inc. Connectivity segment coloring
US9602385B2 (en) 2013-12-18 2017-03-21 Nicira, Inc. Connectivity segment selection
US9680750B2 (en) 2010-07-06 2017-06-13 Nicira, Inc. Use of tunnels to hide network addresses
US9794079B2 (en) 2014-03-31 2017-10-17 Nicira, Inc. Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks
US9948384B1 (en) * 2016-11-23 2018-04-17 Google Llc Identifying network faults
US10182496B2 (en) 2013-11-05 2019-01-15 Cisco Technology, Inc. Spanning tree protocol optimization
US10382345B2 (en) 2013-11-05 2019-08-13 Cisco Technology, Inc. Dynamic flowlet prioritization
US10432578B2 (en) 2016-09-27 2019-10-01 Cisco Technology, Inc. Client address based forwarding of dynamic host configuration protocol response packets
US10454882B2 (en) 2017-06-30 2019-10-22 Cisco Technology, Inc. DHCP in layer-3 overlay with anycast address support and network address transparency
US10516612B2 (en) 2013-11-05 2019-12-24 Cisco Technology, Inc. System and method for identification of large-data flows
US10778457B1 (en) 2019-06-18 2020-09-15 Vmware, Inc. Traffic replication in overlay networks spanning multiple sites
US10778584B2 (en) 2013-11-05 2020-09-15 Cisco Technology, Inc. System and method for multi-path load balancing in network fabrics
US11784922B2 (en) 2021-07-03 2023-10-10 Vmware, Inc. Scalable overlay multicast routing in multi-tier edge gateways

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8775579B2 (en) * 2010-01-13 2014-07-08 Htc Corporation Method for addressing management object in management tree and associated device management system
CN102340446B (en) * 2010-07-20 2015-06-03 华为技术有限公司 Method for realizing Ethernet-tree (E-tree) service in virtual private local area network service (VPLS) network and provider edge (PE) equipment
CN102487351A (en) * 2010-12-01 2012-06-06 中兴通讯股份有限公司 Establishment method of end-to-end multicast label switched path, apparatus thereof and system
CN102571616B (en) * 2012-03-16 2017-09-19 中兴通讯股份有限公司 Merging, dividing method, tunnel-associated device and the router in tunnel
CN102761493B (en) * 2012-07-26 2015-04-08 杭州华三通信技术有限公司 Multicast routing item updating method and device of multilink transparent internet
CN103731279B (en) * 2012-10-11 2019-01-25 中兴通讯股份有限公司 Operation executes method and device
CN104394004B (en) * 2014-11-24 2018-02-23 浪潮电子信息产业股份有限公司 A kind of high-availability cluster heartbeat message repeating method
CN105763411B (en) * 2014-12-15 2019-12-13 华为技术有限公司 Method and device for establishing multicast tunnel

Citations (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5265207A (en) * 1990-10-03 1993-11-23 Thinking Machines Corporation Parallel computer system including arrangement for transferring messages from a source processor to selected ones of a plurality of destination processors and combining responses
US5353412A (en) * 1990-10-03 1994-10-04 Thinking Machines Corporation Partition control circuit for separately controlling message sending of nodes of tree-shaped routing network to divide the network into a number of partitions
US5361363A (en) * 1990-10-03 1994-11-01 Thinking Machines Corporation Input/output system for parallel computer for performing parallel file transfers between selected number of input/output devices and another selected number of processing nodes
US5388214A (en) * 1990-10-03 1995-02-07 Thinking Machines Corporation Parallel computer system including request distribution network for distributing processing requests to selected sets of processors in parallel
US5687319A (en) * 1994-09-27 1997-11-11 International Business Machines Corporation Method and system for determining maximum cable segments between all possible node to node paths on a serial bus
US5748736A (en) * 1996-06-14 1998-05-05 Mittra; Suvo System and method for secure group communications via multicast or broadcast
US6055561A (en) * 1996-10-02 2000-04-25 International Business Machines Corporation Mapping of routing traffic to switching networks
US6078590A (en) * 1997-07-14 2000-06-20 Cisco Technology, Inc. Hierarchical routing knowledge for multicast packet routing
US6104715A (en) * 1997-04-28 2000-08-15 International Business Machines Corporation Merging of data cells in an ATM network
US6262984B1 (en) * 1998-05-12 2001-07-17 3Com Corporation Method of preventing overlapping branches in point to multipoint calls in PNNI networks
US20010034839A1 (en) * 1999-12-24 2001-10-25 Guenter Karjoth Method and apparatus for secure transmission of data and applications
US20020064148A1 (en) * 2000-01-20 2002-05-30 Hall Thomas Glenn Intelligent network and method for providing voice telephony over ATM and point-to-multipoint connectivity
US6421316B1 (en) * 1998-07-16 2002-07-16 Nec Corporation Point-to-multipoint connection restoration
US6449263B2 (en) * 1998-03-02 2002-09-10 Motorola, Inc. Method for communicating signaling messages through a broadband network
US20020150099A1 (en) * 2001-04-13 2002-10-17 Pung Hung Keng Multicast routing method satisfying quality of service constraints, software and devices
US6502155B1 (en) * 1998-11-30 2002-12-31 Sony Corporation Radio network and method of establishing time synchronization among a plurality of buses
US20030211859A1 (en) * 2002-05-08 2003-11-13 Chen An Mei Method and apparatus for supporting application-layer media multicasting
US20040023651A1 (en) * 1991-05-13 2004-02-05 Gollnick Charles D. Network supporting roaming, sleeping terminals
US20040059831A1 (en) * 2002-09-24 2004-03-25 Chu Thomas P. Methods and systems for efficiently configuring IP-based, virtual private networks
US6717921B1 (en) * 2000-05-17 2004-04-06 Lucent Technologies Inc. Method for configuring a shared tree for routing traffic in a multicast conference
US6728777B1 (en) * 1999-06-02 2004-04-27 Nortel Networks Limited Method for engineering paths for multicast traffic
US20040088735A1 (en) * 2002-09-03 2004-05-06 Charles Kristofek Method & apparatus for providing multicast capability within an ATM network
US20040153766A1 (en) * 2001-04-11 2004-08-05 Shoichi Yamamoto Communication system,transmission device, reception device, and communication system having them
US6795403B1 (en) * 2000-03-31 2004-09-21 Cisco Technology, Inc. Automatic discovery of switch devices in a network
US20040236829A1 (en) * 2003-05-13 2004-11-25 Yikang Xu Reliable delivery of multi-cast conferencing data
US6831918B1 (en) * 1997-12-01 2004-12-14 Telia Ab IP/ATM network system adapted for the simultaneous transmission of IP data packets to a plurality of users
US20040260814A1 (en) * 2003-06-18 2004-12-23 Utah State University Efficient unicast-based multicast tree construction and maintenance for multimedia transmission
US20040264462A1 (en) * 2003-06-25 2004-12-30 Bardalai Snigdho C Method and system for multicasting data packets in an MPLS network
US20050002405A1 (en) * 2001-10-29 2005-01-06 Hanzhong Gao Method system and data structure for multimedia communications
US20050002388A1 (en) * 2001-10-29 2005-01-06 Hanzhong Gao Data structure method, and system for multimedia communications
US20050015404A1 (en) * 2003-07-15 2005-01-20 Ludmila Cherkasova System and method having improved efficiency for distributing a file among a plurality of recipients
US6879594B1 (en) * 1999-06-07 2005-04-12 Nortel Networks Limited System and method for loop avoidance in multi-protocol label switching
US20050169266A1 (en) * 2004-02-03 2005-08-04 Rahul Aggarwal MPLS traffic engineering for point-to-multipoint label switched paths
US6931005B1 (en) * 2000-03-10 2005-08-16 Nortel Networks Limited IP multicast services over ATM multicast
US20050201278A1 (en) * 2004-03-11 2005-09-15 Sujata Banerjee Reconfiguring a multicast tree
US20060090007A1 (en) * 2003-03-12 2006-04-27 Nec Corporation Message delivery apparatus, method thereof, system thereof, and program thereof
US7383436B2 (en) * 1999-12-22 2008-06-03 Cisco Technology, Inc. Method and apparatus for distributing and updating private keys of multicast group managers using directory replication
US7450526B2 (en) * 2003-03-28 2008-11-11 Samsung Electronics Co., Ltd. Configuring direction-based core based tree (CBT) for CBT-based overlay multicast
US7564786B2 (en) * 2004-02-12 2009-07-21 Samsung Electronics Co., Ltd. Multicast method in zigbee network
US7583601B2 (en) * 2003-02-07 2009-09-01 Nippon Telegraph And Telephone Corporation Multicast transfer route setting method, and multicast label switching method for implementing former method

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4375054B2 (en) * 2004-02-26 2009-12-02 日本電気株式会社 Network node device, server device, multicast tree construction method and program

Patent Citations (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5265207A (en) * 1990-10-03 1993-11-23 Thinking Machines Corporation Parallel computer system including arrangement for transferring messages from a source processor to selected ones of a plurality of destination processors and combining responses
US5353412A (en) * 1990-10-03 1994-10-04 Thinking Machines Corporation Partition control circuit for separately controlling message sending of nodes of tree-shaped routing network to divide the network into a number of partitions
US5361363A (en) * 1990-10-03 1994-11-01 Thinking Machines Corporation Input/output system for parallel computer for performing parallel file transfers between selected number of input/output devices and another selected number of processing nodes
US5388214A (en) * 1990-10-03 1995-02-07 Thinking Machines Corporation Parallel computer system including request distribution network for distributing processing requests to selected sets of processors in parallel
US20040023651A1 (en) * 1991-05-13 2004-02-05 Gollnick Charles D. Network supporting roaming, sleeping terminals
US20040073933A1 (en) * 1991-05-13 2004-04-15 Gollnick Charles D. Network supporting roaming, sleeping terminals
US5687319A (en) * 1994-09-27 1997-11-11 International Business Machines Corporation Method and system for determining maximum cable segments between all possible node to node paths on a serial bus
US5748736A (en) * 1996-06-14 1998-05-05 Mittra; Suvo System and method for secure group communications via multicast or broadcast
US6055561A (en) * 1996-10-02 2000-04-25 International Business Machines Corporation Mapping of routing traffic to switching networks
US6104715A (en) * 1997-04-28 2000-08-15 International Business Machines Corporation Merging of data cells in an ATM network
US6078590A (en) * 1997-07-14 2000-06-20 Cisco Technology, Inc. Hierarchical routing knowledge for multicast packet routing
US6831918B1 (en) * 1997-12-01 2004-12-14 Telia Ab IP/ATM network system adapted for the simultaneous transmission of IP data packets to a plurality of users
US6449263B2 (en) * 1998-03-02 2002-09-10 Motorola, Inc. Method for communicating signaling messages through a broadband network
US6262984B1 (en) * 1998-05-12 2001-07-17 3Com Corporation Method of preventing overlapping branches in point to multipoint calls in PNNI networks
US6421316B1 (en) * 1998-07-16 2002-07-16 Nec Corporation Point-to-multipoint connection restoration
US6502155B1 (en) * 1998-11-30 2002-12-31 Sony Corporation Radio network and method of establishing time synchronization among a plurality of buses
US6728777B1 (en) * 1999-06-02 2004-04-27 Nortel Networks Limited Method for engineering paths for multicast traffic
US6879594B1 (en) * 1999-06-07 2005-04-12 Nortel Networks Limited System and method for loop avoidance in multi-protocol label switching
US7383436B2 (en) * 1999-12-22 2008-06-03 Cisco Technology, Inc. Method and apparatus for distributing and updating private keys of multicast group managers using directory replication
US20010034839A1 (en) * 1999-12-24 2001-10-25 Guenter Karjoth Method and apparatus for secure transmission of data and applications
US20020064148A1 (en) * 2000-01-20 2002-05-30 Hall Thomas Glenn Intelligent network and method for providing voice telephony over ATM and point-to-multipoint connectivity
US6931005B1 (en) * 2000-03-10 2005-08-16 Nortel Networks Limited IP multicast services over ATM multicast
US6795403B1 (en) * 2000-03-31 2004-09-21 Cisco Technology, Inc. Automatic discovery of switch devices in a network
US6717921B1 (en) * 2000-05-17 2004-04-06 Lucent Technologies Inc. Method for configuring a shared tree for routing traffic in a multicast conference
US20040153766A1 (en) * 2001-04-11 2004-08-05 Shoichi Yamamoto Communication system,transmission device, reception device, and communication system having them
US20020150099A1 (en) * 2001-04-13 2002-10-17 Pung Hung Keng Multicast routing method satisfying quality of service constraints, software and devices
US20050002405A1 (en) * 2001-10-29 2005-01-06 Hanzhong Gao Method system and data structure for multimedia communications
US20050002388A1 (en) * 2001-10-29 2005-01-06 Hanzhong Gao Data structure method, and system for multimedia communications
US20030211859A1 (en) * 2002-05-08 2003-11-13 Chen An Mei Method and apparatus for supporting application-layer media multicasting
US20040088735A1 (en) * 2002-09-03 2004-05-06 Charles Kristofek Method & apparatus for providing multicast capability within an ATM network
US20040059831A1 (en) * 2002-09-24 2004-03-25 Chu Thomas P. Methods and systems for efficiently configuring IP-based, virtual private networks
US7583601B2 (en) * 2003-02-07 2009-09-01 Nippon Telegraph And Telephone Corporation Multicast transfer route setting method, and multicast label switching method for implementing former method
US20060090007A1 (en) * 2003-03-12 2006-04-27 Nec Corporation Message delivery apparatus, method thereof, system thereof, and program thereof
US7450526B2 (en) * 2003-03-28 2008-11-11 Samsung Electronics Co., Ltd. Configuring direction-based core based tree (CBT) for CBT-based overlay multicast
US20040236829A1 (en) * 2003-05-13 2004-11-25 Yikang Xu Reliable delivery of multi-cast conferencing data
US20040260814A1 (en) * 2003-06-18 2004-12-23 Utah State University Efficient unicast-based multicast tree construction and maintenance for multimedia transmission
US20080056258A1 (en) * 2003-06-25 2008-03-06 Fujitsu Limited Method and System for Multicasting Data Packets in an MPLS Network
US20040264462A1 (en) * 2003-06-25 2004-12-30 Bardalai Snigdho C Method and system for multicasting data packets in an MPLS network
US20050015404A1 (en) * 2003-07-15 2005-01-20 Ludmila Cherkasova System and method having improved efficiency for distributing a file among a plurality of recipients
US20050169266A1 (en) * 2004-02-03 2005-08-04 Rahul Aggarwal MPLS traffic engineering for point-to-multipoint label switched paths
US7564786B2 (en) * 2004-02-12 2009-07-21 Samsung Electronics Co., Ltd. Multicast method in zigbee network
US20050201278A1 (en) * 2004-03-11 2005-09-15 Sujata Banerjee Reconfiguring a multicast tree

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Escalona et al., "Established Source-Routed Bidirectional Connection over the Unidirectional ASON/GMPLS Carisma Testbed," 2005, Institute of Electrical and Electronic Engineers, Geneva, Switzerland. *

Cited By (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8514850B2 (en) * 2007-09-03 2013-08-20 Alcatel Lucent Method for establishing a bidirectional point-to-point connection
US20090077237A1 (en) * 2007-09-03 2009-03-19 Alcatel Lucent Method for establishing a bidirectional point-to-point connection
US20090086632A1 (en) * 2007-09-28 2009-04-02 Folkes Ronald P Using A Link Attribute To Inform Nodes Of The Availability Of Traffic Management Resources
US7768924B2 (en) * 2007-09-28 2010-08-03 Fujitsu Limited Using a link attribute to inform nodes of the availability of traffic management resources
US20090086633A1 (en) * 2007-10-02 2009-04-02 Chenjiang Hu Using A Link-State Advertisement To Inform Nodes Of The Availability Of Traffic Management Resources
US11743123B2 (en) 2010-07-06 2023-08-29 Nicira, Inc. Managed switch architectures: software managed switches, hardware managed switches, and heterogeneous managed switches
US9231891B2 (en) 2010-07-06 2016-01-05 Nicira, Inc. Deployment of hierarchical managed switching elements
US8964598B2 (en) 2010-07-06 2015-02-24 Nicira, Inc. Mesh architectures for managed switching elements
US8964528B2 (en) 2010-07-06 2015-02-24 Nicira, Inc. Method and apparatus for robust packet distribution among hierarchical managed switching elements
US9007903B2 (en) 2010-07-06 2015-04-14 Nicira, Inc. Managing a network by controlling edge and non-edge switching elements
US9680750B2 (en) 2010-07-06 2017-06-13 Nicira, Inc. Use of tunnels to hide network addresses
US9049153B2 (en) 2010-07-06 2015-06-02 Nicira, Inc. Logical packet processing pipeline that retains state information to effectuate efficient processing of packets
US9077664B2 (en) 2010-07-06 2015-07-07 Nicira, Inc. One-hop packet processing in a network with managed switching elements
US9112811B2 (en) 2010-07-06 2015-08-18 Nicira, Inc. Managed switching elements used as extenders
US8913483B2 (en) * 2010-07-06 2014-12-16 Nicira, Inc. Fault tolerant managed switching element architecture
US9300603B2 (en) 2010-07-06 2016-03-29 Nicira, Inc. Use of rich context tags in logical data processing
US9306875B2 (en) 2010-07-06 2016-04-05 Nicira, Inc. Managed switch architectures for implementing logical datapath sets
US11641321B2 (en) 2010-07-06 2023-05-02 Nicira, Inc. Packet processing for logical datapath sets
US10686663B2 (en) 2010-07-06 2020-06-16 Nicira, Inc. Managed switch architectures: software managed switches, hardware managed switches, and heterogeneous managed switches
US20130058208A1 (en) * 2010-07-06 2013-03-07 Benjamin L. Pfaff Fault tolerant managed switching element architecture
US10038597B2 (en) 2010-07-06 2018-07-31 Nicira, Inc. Mesh architectures for managed switching elements
US10021019B2 (en) 2010-07-06 2018-07-10 Nicira, Inc. Packet processing for logical datapath sets
US9692655B2 (en) 2010-07-06 2017-06-27 Nicira, Inc. Packet processing in a network with hierarchical managed switching elements
US10623194B2 (en) 2013-08-24 2020-04-14 Nicira, Inc. Distributed multicast by endpoints
US9887851B2 (en) 2013-08-24 2018-02-06 Nicira, Inc. Distributed multicast by endpoints
US9432204B2 (en) 2013-08-24 2016-08-30 Nicira, Inc. Distributed multicast by endpoints
US10218526B2 (en) 2013-08-24 2019-02-26 Nicira, Inc. Distributed multicast by endpoints
US10606454B2 (en) 2013-11-05 2020-03-31 Cisco Technology, Inc. Stage upgrade of image versions on devices in a cluster
US11625154B2 (en) 2013-11-05 2023-04-11 Cisco Technology, Inc. Stage upgrade of image versions on devices in a cluster
US11888746B2 (en) 2013-11-05 2024-01-30 Cisco Technology, Inc. System and method for multi-path load balancing in network fabrics
US9654300B2 (en) 2013-11-05 2017-05-16 Cisco Technology, Inc. N-way virtual port channels using dynamic addressing and modified routing
US20150124642A1 (en) * 2013-11-05 2015-05-07 Cisco Technology, Inc. Running link state routing protocol in clos networks
US10164782B2 (en) 2013-11-05 2018-12-25 Cisco Technology, Inc. Method and system for constructing a loop free multicast tree in a data-center fabric
US10182496B2 (en) 2013-11-05 2019-01-15 Cisco Technology, Inc. Spanning tree protocol optimization
US9698994B2 (en) 2013-11-05 2017-07-04 Cisco Technology, Inc. Loop detection and repair in a multicast tree
US11528228B2 (en) 2013-11-05 2022-12-13 Cisco Technology, Inc. System and method for multi-path load balancing in network fabrics
US10382345B2 (en) 2013-11-05 2019-08-13 Cisco Technology, Inc. Dynamic flowlet prioritization
US10778584B2 (en) 2013-11-05 2020-09-15 Cisco Technology, Inc. System and method for multi-path load balancing in network fabrics
US9634846B2 (en) * 2013-11-05 2017-04-25 Cisco Technology, Inc. Running link state routing protocol in CLOS networks
US10516612B2 (en) 2013-11-05 2019-12-24 Cisco Technology, Inc. System and method for identification of large-data flows
US9667431B2 (en) 2013-11-05 2017-05-30 Cisco Technology, Inc. Method and system for constructing a loop free multicast tree in a data-center fabric
US9985794B2 (en) 2013-11-05 2018-05-29 Cisco Technology, Inc. Traceroute in a dense VXLAN network
US11310150B2 (en) 2013-12-18 2022-04-19 Nicira, Inc. Connectivity segment coloring
US9602385B2 (en) 2013-12-18 2017-03-21 Nicira, Inc. Connectivity segment selection
US9602392B2 (en) 2013-12-18 2017-03-21 Nicira, Inc. Connectivity segment coloring
US10999087B2 (en) 2014-03-31 2021-05-04 Nicira, Inc. Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks
US10333727B2 (en) 2014-03-31 2019-06-25 Nicira, Inc. Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks
US9794079B2 (en) 2014-03-31 2017-10-17 Nicira, Inc. Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks
US11923996B2 (en) 2014-03-31 2024-03-05 Nicira, Inc. Replicating broadcast, unknown-unicast, and multicast traffic in overlay logical networks bridged with physical networks
US10432578B2 (en) 2016-09-27 2019-10-01 Cisco Technology, Inc. Client address based forwarding of dynamic host configuration protocol response packets
US9948384B1 (en) * 2016-11-23 2018-04-17 Google Llc Identifying network faults
US10454882B2 (en) 2017-06-30 2019-10-22 Cisco Technology, Inc. DHCP in layer-3 overlay with anycast address support and network address transparency
US10778457B1 (en) 2019-06-18 2020-09-15 Vmware, Inc. Traffic replication in overlay networks spanning multiple sites
US11456888B2 (en) 2019-06-18 2022-09-27 Vmware, Inc. Traffic replication in overlay networks spanning multiple sites
US11784842B2 (en) 2019-06-18 2023-10-10 Vmware, Inc. Traffic replication in overlay networks spanning multiple sites
US11784922B2 (en) 2021-07-03 2023-10-10 Vmware, Inc. Scalable overlay multicast routing in multi-tier edge gateways

Also Published As

Publication number Publication date
EP1953956A1 (en) 2008-08-06
WO2007054032A1 (en) 2007-05-18
EP1953956A4 (en) 2010-03-24
CN1964313A (en) 2007-05-16
EP1953956B1 (en) 2017-09-06
CN100563203C (en) 2009-11-25

Similar Documents

Publication Publication Date Title
US20080212496A1 (en) Communication network system and signal transmission method between leaf-nodes of multicast tree and node thereof
US8588611B2 (en) Method for establishing an inter-domain path that satisfies wavelength continuity constraint
EP1696618B1 (en) Forwarding state sharing between multiple traffic paths in a communication network
US7394772B2 (en) Method of routing point-to-multipoint traffic on an MPLS network
US8514850B2 (en) Method for establishing a bidirectional point-to-point connection
JP4476292B2 (en) Real-time service data transmission line selection method
US9112776B2 (en) Method and apparatus for fast reroute in a connection-oriented network
US7095712B2 (en) Method and apparatus for protection path setup
US7787364B2 (en) Control scheme for standby channel route
US8605723B2 (en) MPLS traffic engineering for point-to-multipoint label switched paths
US8422361B2 (en) Management of protection path bandwidth and changing of path bandwidth
CN106982157B (en) Traffic engineering tunnel establishment method and device
US20140348028A1 (en) Method for creating ring network label switched path, related device, and communications system
EP2503742B1 (en) Method for implementing shared mesh protection, equipment and optical network system
WO2017193569A1 (en) Path establishment method and controller
US20090103533A1 (en) Method, system and node apparatus for establishing identifier mapping relationship
WO2011157130A2 (en) Path establishment method and apparatus
WO2012075914A1 (en) Method and system for implementing point-to-multipoint label switched path protection
WO2007009335A1 (en) A method for realizing the multicast service in an automatic switch optical network
CN109005473B (en) Method, device and system for cooperatively selecting path
JPWO2004102904A1 (en) PATH SETTING METHOD AND COMMUNICATION APPARATUS IN COMMUNICATION NETWORK COMMUNICating THROUGH MULTILAYER
EP2466813B1 (en) Method and system for determining initiator and terminator in forwarding adjacency label switched path
EP2624505A1 (en) Method and system for establishing, grafting and cutting bidirectional point-to-multipoint label switched path
CN102201970B (en) Method and system for performing routing optimization on associated bidirectional label switched path (LSP)
JP4386598B2 (en) Hierarchical path setting method and node device for realizing the same

Legal Events

Date Code Title Description
AS Assignment

Owner name: HUAWEI TECHNOLOGIES CO., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ZOU, SHIMIN;REEL/FRAME:020936/0952

Effective date: 20080422

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION