SYSTEM AND METHOD OF AUTOMATICALLY CONFIGURING I-SIDS IN GMPLS CONTROLLED ETHERNET PROVIDER BACKBONE BRIDGED NETWORKS

Abstract

A system and method of automatically configuring a Service Instance Identifier (I-SID) in a Generalized Multiprotocol Label Switching (GMPLS) controlled network. The method begins by identifying a specific I-SID for a specific service in the GMPLS controlled network. Next, the identified I-SID is automatically configured within a Backbone Edge Bridge (BEB) with a Resource Reservation Protocol-Traffic Engineering (RSVP-TE) extension. The automatic configuration may be implemented by several different embodiments. In one embodiment, the I-SID may be carried in a SESSION_ATTRIBUTE object. In another embodiment, the I-SID may be mapped to a Short Call ID field in a Session object. Alternatively, the I-SID may be carried in an Endpoint ID Type-Length-Value (TLV). The I-SID may also be carried in a new TLV in a LSP_ATTRIBUTES or CALL_ATTRIBUTES object.

Description

TECHNICAL FIELD

The present invention relates generally to communications networks, and in particular, to a system and method providing automatic Service Instance Identifier (I-SID) configurations for Generalized Multiprotocol Label Switching (GMPLS) Controlled Ethernet Provider Backbone Bridged Networks.

BACKGROUND

The Institute of Electrical and Electronics Engineers (IEEE) is amending Ethernet standards to equip Ethernet with new features required for Wide Area Network (WAN) deployment. The relevant extensions include: Connectivity Fault Management (CFM); Provider Bridging (PB); Provider Backbone Bridging (PBB); and Provider Backbone Bridging-Traffic Engineering (PBB-TE).

PB and PBB are enhancing Ethernet scalability. With PB, a new Virtual Local Area Network (VLAN) tag, the Service VLAN (S-VALN) tag, has been introduced to allow providers to use a separate VLAN space while transparently maintaining the Customer VLAN (C-VLAN) information.

PBB allows a full separation of the customer and provider address spaces by encapsulating customer frames adding a “backbone” MAC header. This enables both the MAC addresses and the whole VLAN space to be in control of the provider. The fields of the encapsulation header for the “Backbone” MAC header include Backbone Destination Address (B-DA), Backbone Source Address (B-SA) and Backbone VLAN (B-VLAN). In addition to the “backbone” MAC header, a new tag, the Service Instance Tag (I-TAG) is added when customer frames are encapsulated. The I-TAG has a 24-bit Service Instance Identifier (I-SID) field. The I-SID unambiguously identifies customer services. In PBB, edge bridges, such as Backbone Edge Bridges (BEBs), which process customer frames and add the backbone MAC header, and the I-SID can be distinguished from core bridges, such as Backbone Core Bridges (BCBs), which are forwarding frames based on the backbone MAC header.

PBB-TE decouples the Ethernet data and control planes by explicitly supporting external control/management mechanisms to configure static filtering entries in bridges and creating explicitly routed connections. In addition, PBB-TE defines mechanisms for 1:1 protection switching of bidirectional Ethernet connections.

In the Internet Engineering Task Force (IETF), the Generalized Multiprotocol Label Switching (GMPLS) controlled Ethernet Label Switching (GELS) is extending the GMPLS control plane for PBB-TE Ethernet networks. GMPLS established PBB-TE connections are referred to as Ethernet Label Switched Paths (LSPs). GELS enables the application of Multiprotocol Label Switching-Traffic Engineering (MPLS-TE) and GMPLS provisioning and recovery features in Ethernet networks.

In PBB, the I-SID identifies a service instance. However, there is currently no mechanism in GMPLS to provide this information.

SUMMARY

In PBB networks, the I-SID identifies a specific service. The I-SID must be configured at the BEBs interfacing with the customer. To ease network management and avoid misconfiguration by manual setup of the I-SID in each BEB, a control plane mechanism is needed to provide I-SID configuration. In a GMPLS controlled Ethernet network, the present invention provides extensions to the Resource Reservation Protocol-Traffic Engineering (RSVP-TE protocol) to provide the I-SID configuration.

Thus, in one embodiment, the present invention is directed to a method of automatically configuring an I-SID in a GMPLS network. The method begins by identifying a specific I-SID for a specific service in the GMPLS controlled network. Next, the identified I-SID is automatically configured within a Backbone Edge Bridge (BEB) with a Resource Reservation Protocol-Traffic Engineering (RSVP-TE) extension. The automatic configuration may be implemented by several different embodiments. In one embodiment, the I-SID may be carried in a SESSION_ATTRIBUTE object. In another embodiment, the I-SID may be mapped to a Short Call ID field in a Session object. Alternatively, the I-SID may be carried in an Endpoint ID Type-Length-Value (TLV). The I-SID may also be carried in a new TLV in a LSP_ATTRIBUTES or CALL_ATTRIBUTES object

In another embodiment, the present invention is directed to a system for automatically configuring an I-SID in a GMPLS controlled network. The system includes a BEB in the GMPLS network. The system identifies a specific I-SID for a specific service in the GMPLS controlled network and automatically configures the identified I-SID within a BEB with a RSVP-TE extension.

In still another embodiment, the present invention is directed to a node for automatically configuring an I-SID in a GMPLS controlled network. The node identifies a specific I-SID for a specific service in the GMPLS controlled network and automatically configures the identified I-SID within a BEB with a RSVP-TE extension.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified block diagram illustrating elements of a PBB network;

FIG. 2 illustrates a format of a session attribute object having a Session name in a one embodiment of the present invention;

FIG. 3 illustrates a format of the SESSION object carrying a short call ID in a second embodiment of the present invention;

FIG. 4 illustrates a format of an endpoint ID TLV;

FIG. 5 illustrates a configuration of a possible extension of the endpoint ID TLV in a third embodiment of the present invention;

FIG. 6 illustrates a format of a configuration of an I-SID TLV carried in the LSP_ATTRIBUTES or CALL_ATTRIBUTE object in a fourth embodiment of the present invention;

FIG. 7 illustrates a 1-to-1 mapping scheme between an I-SID and short call IDs; and

FIG. 8 is a flow chart illustrating the method of automatically configuring an I-SID within a GMPLS controlled network according to the teachings of the present invention.

DETAILED DESCRIPTION

The present invention is a system and method providing automatic I-SID configurations for Generalized Multiprotocol Label Switching (GMPLS) Controlled Ethernet Provider Backbone Bridged Networks. FIG. 1 is a simplified block diagram illustrating elements of a PBB network 100 according to the teachings of the present invention. The network includes a first BEB 102 communicating with a second BEB 104 through one or more Ethernet Switched Paths (ESPs) 106.

In “Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 User-Network Interface (UNI)”, Internal Draft and “Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Services”, Resource Reservation Protocol-Traffic Engineering (RSVP-TE) extensions are defined to support a UNI. It is proposed in these documents to use a Call construct and a new Type-Length-Value (TLV), i.e., the Endpoint ID TLV in the LSP_ATTRIBUTES object, to establish and identify a specific Ethernet service. However, these extensions do not address utilizing and configuring the I-SID.

The present invention provides a system and method for automatically configuring I-SIDs in GMPLS networks. The present invention provides several embodiments for automatically configuring the I-SIDs. In one embodiment, the present invention utilizes a SESSION_ATTRIBUTE object to signal the I-SID. The Session Name field of the SESSION_ATTRIBUTE Object carries a Null padded display string. In the case the Session Name is used as a notify message to establish a call, this field is interpreted as the Long Call ID. The purpose of the I-SID is similar to the Call ID, and as such may be encoded in the Session Name field. FIG. 2 illustrates a format of a session attribute object 200 having a Session name 202. The I-SID may be either encoded as a numeric value or converted to a character string. The field Name Length is typically fixed to 4 and 8, respectively. Alternatively, the Session Name may contain readable text and the I-SID value may be appended to that text surrounded by control characters. This way, a meaningful text as well as the I-SID value may be carried in this field.

In another embodiment, the I-SID may be mapped to a short call ID. FIG. 3 illustrates a format of the SESSION object 210 carrying a short call ID 212. The Short Call ID is carried in a 16 bit field in the SESSION object 210. It identifies all LSPs setup to support a given Call. Since the I-SID is a 24 bit field, it may only be carried in the Short Call ID if a proper “compressed” encoding is utilized. This requires some management mechanisms to pre-allocate I-SID ranges to edge bridges. However, this pre-allocation may ensure that no I-SID collision occurs during signaling.

In another embodiment, the I-SID may be carried in an Endpoint ID Type-Length-Value (TLV). FIG. 4 illustrates a format of an endpoint ID TLV 240. In a similar fashion as the Session Name field in the SESSION_ATTRIBUTE object, the Endpoint ID is a null padded variable length object. However, the Endpoint ID TLV may be extended with a new field to carry the I-SID. FIG. 5 illustrates a configuration of a possible extension of the endpoint ID TLV 250 according to the teachings of the present invention. As depicted in FIG. 5, a new I-SID field 252 is provided in the endpoint ID TLV.

In still another embodiment, a new Ethernet specific TLV may be introduced in the LSP_ATTRIBUTES or CALL_ATTRIBUTES Object to carry the I-SID. FIG. 6 illustrates a format of a configuration of an I-SID TLV 260 carried in the LSP_ATTRIBUTES according to the teachings of the present invention.

Session Name and Endpoint ID fields, as discussed in FIGS. 2 and 4, were originally defined to transmit displayable identifiers for management purposes even, when the signaling is automated. Therefore, to transmit the I-SID, the I-SID must be concatenated to the original string.

Using the short Call ID, as discussed in FIG. 3, to transmit the low 16 bits of the I-SID provides the simplest solution. However, this method may only be used if a Call is associated to each service. In addition, 1-to-1 assignment between the 24 bit I-SID and the 16 bit Short Call ID is essential.

Creating a new TLV to transmit the I-SID, as discussed in FIG. 6, provides the most general solution. This embodiment is applicable even if no Call is associated to a particular service.

The embodiment discussed in FIG. 3 has a crucial issue. Specifically, only 16 bits are available to encode the I-SID in the Short Call ID field, since the I-SID is 24 bits. To accommodate the I-SID in this abbreviated 16 bit field, the present invention may map the I-SID to the 16 bits field. In one embodiment, to avoid I-SID collision, the I-SID space is split into multiple non-overlapping domains, where each domain is dedicated to a single BEB. The I-SID may be logically divided into the Originator BEB ID and the Service Differentiator. The originator BEB ID can be either disseminated in advance using the routing protocol (OSPF-TE/ISIS-TE), carried in RSVP-TE, or be configured by management.

The I-SID may be split to Originator BEB IDs and Service differentiator fields using different ratios. For example, 8 bits for BEB ID and 16 bits for Service differentiation may be used in one embodiment. In another embodiment, 12 bits for BEB IDs and 12 bits for Service Differentiation may be used. In the first case, there can be 2̂8=256 BEBs and up to 2̂16˜65 k service instances initiated by each BEB. In the second case, up to 4096 BEBs can be differentiated. However, only 4096 service instances can be initiated by a BEB.

The Router ID is a 32 bit identifier assigned to every node in a GMPLS controlled network. At the same time, the Router IDs are routable control plane IP addresses. Thus, the router IDs may be treated as regular IP address.

The Originator BEB ID may be derived from the Router ID of the source node. In the present invention, the lowest 8 bits of the Router ID may be interpreted as the BEB ID. This embodiment requires that the lowest 8 bits of the Router IDs of the BEBs must uniquely identify BEBs. The I-SID (24 bits) is then the concatenation of the lowest 8 bit of the Router ID and the Short Call ID. FIG. 7 illustrates a 1-to-1 mapping scheme between an I-SID 300 and short call IDs 302. Thus, the Originator BEB ID (8 bits) allows unique identification of 256 edge bridges. The Service Differentiator is 16 bits.

To ensure the uniqueness of the BEB IDs, several assumptions are made. Specifically, the control plane of a PBB-TE network is assumed to consist of a single IP network domain. Thus, the Network address portion is common. Since the host address must be unique within the control plane, the host address is assumed to be unique for the PBB-TE domain as well. This mapping scheme may be used only if the network address is 24 bit long.

If the network address is longer than 24 bits, some of its bits must be used as well. However, in general, their uniqueness cannot be ensured. If it is shorter than 24 bits, the lowest 8 bits of the host address will not be unique.

To fix these address spacing problems, a subnet may be preserved only for the BEBs that extend the network address to 24 bits. The other subnets may be used for the other nodes.

FIG. 8 is a flow chart illustrating the method of automatically configuring an I-SID within a GMPLS network according to the teachings of the present invention. With reference to FIGS. 1-8, the present invention will now be explained. The method begins in step 400 where a specific I-SID identifies a specific service in the PBB network 100. Next, in step 402, the I-SID is automatically configured at the BEB interfacing with a subscriber. Within the GMPLS controlled Ethernet network, extensions are utilized in the RSVP-TE protocol. To configure the I-SID, the present invention may utilize several different embodiments discussed above. The present invention may use the Session Name field of the SESSION_ATTRIBUTE Object. In another embodiment, the I-SID may be mapped to the Short Call ID. In still another embodiment, the I-SID may be carried in the Endpoint ID TLV. Additionally, a new Ethernet specific TLV may be introduced in the LSP_ATTRIBUTES or CALL_ATTRIBUTES object to carry the I-SID. In step 404, if the I-SID is mapped to the Short Call ID, whereby the I-SID is mapped to the 16 bit Short CALL ID field.

The present invention provides many advantages over existing systems. The present invention provides for the automatic distribution and configuration of the I-SID on BEBs supporting a particular service instance. This reduces operational complexity and decreases the possibility of misconfiguration. In addition, the present invention provides a mechanism to unambiguously partition the I-SID space. This is beneficial to avoid possible I-SID collisions when configuring the services on BEBs. I-SIDs must be globally unique in the network. Thus, I-SID collision could occur if the allocation is done independently at BEBs or when there would be I-SID space partitioning among BEBs.

The present invention may of course, be carried out in other specific ways than those herein set forth without departing from the essential characteristics of the invention. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.

Claims

1. A method of automatically configuring a Service Instance Identifier, I-SID, in a Generalized Multiprotocol Label Switching, GMPLS, controlled network, the method comprising the steps of: identifying a specific I-SID for a specific service in the GMPLS controlled network; andautomatically configuring the identified I-SID within a Backbone Edge Bridge, BEB, with a Resource Reservation Protocol-Traffic Engineering, RSVP-TE, extension.

2. The method according to claim 1 wherein the step of automatically configuring the identified I-SID includes using a SESSION_ATTRIBUTE object.

3. The method according to claim 2 wherein the I-SID is concatenated to an original string of the SESSION_ATTRIBUTE object.

4. The method according to claim 2 wherein a Session Name field in the SESSION_ATTRIBUTE object carries the I-SID.

5. The method according to claim 4 wherein the I-SID is appended to text in the Session Name field.

6. The method according to claim 2 wherein the I-SID is encoded as a numeric value.

7. The method according to claim 2 wherein the I-SID is encoded as a converted character string.

8. The method according to claim 1, wherein the I-SID is mapped to a Short Call ID field in a session object.

9. The method according to claim 8 wherein the I-SID is mapped to a 16 bit Short Call ID field.

10. The method according to claim 8 wherein the I-SID is split into an originator BEB ID and a Service Differentiator.

11. The method according to claim 8 wherein the I-SID is mapped to the Short Call ID by utilizing a Router ID field in the object

12. The method according to claim 8 wherein the I-SID is concatenated to the lowest 8 bits of the Router ID and the Short Call ID.

13. The method according to claim 1, wherein the step of automatically configuring the identified I-SID includes carrying the I-SID in an Endpoint ID Type-Length-Value, TLV, of a session object.

14. The method according to claim 13, wherein the I-SID is concatenated to an original string within the object.

15. The method according to claim 1, wherein the step of automatically configuring the identified I-SID includes carrying the I-SID in a new TLV in a LSP_ATTRIBUTES or CALL_ATTRIBUTES object.

16. The method according to claim 15, wherein the I-SID is concatenated to an original string within the object.

17. A system for automatically configuring a Service Instance Identifier, I-SID, in a Generalized Multiprotocol Label Switching, GMPLS, controlled network, the system comprising: a Backbone Edge Bridge, BEB, in the GMPLS controlled network;means adapted to identify a specific I-SID for a specific service in the GMPLS controlled network;means adapted to automatically configure the identified I-SID within the BEB with a Resource Reservation Protocol-Traffic Engineering, RSVP-TE, extension.

18. The system according to claim 17 wherein the means to automatically configure the identified I-SID is adapted to carry the I-SID by utilizing a SESSION_ATTRIBUTE object.

19. The system according to claim 18 wherein the I-SID is concatenated to an original string of the SESSION_ATTRIBUTE object.

20. The system according to claim 18 wherein a Session Name field in the SESSION_ATTRIBUTE object carries the I-SID.

21. The system according to claim 20 wherein the I-SID is appended to text in the Session Name field.

22. The system according to claim 18 wherein the I-SID is encoded as a numeric value.

23. The system according to claim 18 wherein the I-SID is encoded as a converted character string.

24. The system according to claim 17 wherein the means to automatically configure the identified I-SID includes means adapted to map to a Short Call ID field in a session object.

25. The system according to claim 24 wherein the means to automatically configure the identified I-SID includes means adapted to map the I-SID to a 16 bit Short Call ID field.

26. The system according to claim 24 wherein the means to automatically configure the identified I-SID includes means adapted to split the I-SID into an originator BEB ID and a Service Differentiator.

27. The system according to claim 24 wherein the means to map the I-SID is further adapted to map the I-SID to the Short Call ID by utilizing a Router ID field in the object.

28. The system according to claim 24 wherein the means to map the I-SID is further adapted to concatenate the I-SID to the lowest 8 bits of the Router ID and the Short Call ID.

29. The system according to claim 17 wherein the means to automatically configure the identified I-SID includes means adapted to carry the I-SID in an Endpoint ID Type-Length-Value, TLV, of a session object.

30. The system according to claim 29 wherein the means to automatically configure the identified I-SID includes means adapted to concatenate the I-SID to an original string within the object.

31. The system according to claim 17 wherein the means to automatically configure the identified I-SID includes means adapted to carry the I-SID in a new TLV in a LSP_ATTRIBUTES or CALL_ATTRIBUTES object.

32. The system according to claim 31 wherein the means to automatically configure the identified I-SID includes means adapted to concatenate the I-SID to an original string within the object.

33. A node for automatically configuring a Service Instance Identifier, I-SID, in a Generalized Multiprotocol Label Switching, GMPLS, controlled network, the node comprising: means adapted to identify a specific I-SID for a specific service in the GMPLS controlled network;means adapted to automatically configure the identified I-SID within a BEB with a Resource Reservation Protocol-Traffic Engineering, RSVP-TE, extension.

34. The node according to claim 33 wherein the means to automatically configure the identified I-SID includes at least one of: means adapted to carry the I-SID utilizing a SESSION_ATTRIBUTE object,means adapted to map the I-SID to a Short Call ID field in a session object,means adapted to carry the I-SID in an Endpoint ID Type-Length-Value, TLV, of a session object, andmeans adapted to carry the I-SID in a new TLV in a LSP_ATTRIBUTES or CALL_ATTRIBUTES object.