Link bundle co-routed VCAT via RSVP message bundling
View Patent ↗Multiple RSVP messages are used to separately signal components of co-routed VCAT to enable the separate components to be implemented on different physical fibers of a link bundle. To enable the PATH messages to be handled as a group, the multiple PATH messages are grouped together and sent out in a RSVP bundle message. When a RSVP bundle message containing multiple PATH messages is received at a network element, such as an ENNI, where the route for the PATH messages needs to be expanded, the route is expanded collectively and the expanded route is inserted into each individual PATH message. The modified PATH messages are then passed through the RSVP finite state machine one at a time to enable resources to be reserved for the connections of the VCAT. Thus, a single LSP may be created for each channel, and channels may be co-routed even where route expansion is required.
1. A method of processing a set of related PATH messages to enable co-routed Virtual Concatenation (VCAT) connections to be implemented over multiple communication channels, each communication channel having a respective transmitter and a respective receiver, the method comprising:
receiving a Reservation Protocol (RSVP) message;
determining that the RSVP message indicates traffic specifications for co-routed VCAT connections; and
processing the RSVP message to set up co-routed VCAT connections meeting the indicated traffic specifications.
2. The method of claim 1 , wherein the RSVP message is a RSVP bundle message, the RSVP bundle message containing multiple PATH messages, each of the PATH messages being associated with one of the co-routed VCAT connections such that there is a one-to-one relationship between the PATH messages and the co-routed VCAT connections.
3. The method of claim 2 , comprising:
determining whether it is necessary to expand a route for at least one of the PATH messages; and
if it is necessary to expand the route, performing route expansion to obtain an expanded route object for the PATH message and inserting the expanded route object into each of the multiple PATH messages.
4. The method of claim 3 , wherein connection control is performed on a PATH message only after the expanded route object has been inserted into the PATH message.
5. The method of claim 2 , wherein determining that the RSVP bundle message indicates traffic specifications for co-routed VCAT connections is performed by reading at least one flag of a RSVP bundle message header.
6. The method of claim 2 , wherein determining that the RSVP bundle message indicates traffic specifications for co-routed VCAT connections is performed by reading a message type field contained in a RSVP bundle message header.
7. The method of claim 2 , wherein determining that the RSVP bundle message indicates traffic specifications for co-routed VCAT connections is performed by reading a reserved field contained in a RSVP bundle message header.
8. The method of claim 2 , comprising performing connection control separately for each PATH message.
9. The method of claim 8 , wherein if one of the PATH messages fails connection control, the method comprises sending a message to a head-end node to indicate that one of the messages failed connection control.
10. The method of claim 8 , wherein if any one of the PATH messages fails connection control, the method comprises causing all of the PATH messages to fail connection control even if some of the other PATH messages had previously individually passed connection control.
11. A network element, comprising:
a plurality of transmitters, each transmitter being associated with a respective communication channel;
an External Network to Network Interface adapted to process a RSVP message to enable co-routed Virtual Concatenation (VCAT) connections to be implemented over multiple communication channels by:
receiving a Reservation Protocol (RSVP) message;
determining that the RSVP message indicates traffic specifications for co-routed VCAT connections; and
processing the RSVP message to set up co-routed VCAT connections meeting the indicated traffic specifications.
12. The network element of claim 11 , wherein the RSVP message is a RSVP bundle message, the RSVP bundle message containing multiple PATH messages, each of the PATH messages being associated with one of the co-routed VCAT connections such that there is a one-to-one relationship between the PATH messages and the co-routed VCAT connections.
13. The network element of claim 12 , wherein the External Network to Network Interface is adapted to process the RSVP bundle message by:
determining whether it is necessary to expand a route for at least one of the PATH messages; and
if it is necessary to expand the route, performing route expansion to obtain an expanded route object for the PATH message and inserting the expanded route object into each of the multiple PATH messages.
14. The network element of claim 13 , wherein performing connection control is performed on a PATH message only after the expanded route object has been inserted into the PATH message.
15. The network element of claim 12 , wherein determining that the RSVP bundle message indicates traffic specifications for co-routed VCAT connections is performed by reading at least one flag of a RSVP bundle message header.
16. The network element of claim 12 , wherein determining that the RSVP bundle message indicates traffic specifications for co-routed VCAT connections is performed by reading a message type field contained in a RSVP bundle message header.
17. The network element of claim 12 , wherein determining that the RSVP bundle message indicates traffic specifications for co-routed VCAT connections is performed by reading a reserved field contained in a RSVP bundle message header.
18. The network element of claim 12 , wherein the External Network to Network Interface is adapted to process the set of related PATH messages by performing connection control separately for each PATH message.
19. The network element of claim 18 , wherein if one of the PATH messages fails connection control, the External Network to Network Interface sends a message to a head-end node to indicate that one of the messages failed connection control.
20. The network element of claim 18 , wherein if any one of the PATH messages fails connection control, the External Network to Network Interface causes all of the PATH messages to fail connection control even if some of the other PATH messages had previously individually passed connection control.