RSVP-TE Protocol Extension for Automatic I-SID Configuration in GMPLS Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In GMPLS controlled Ethernet networks, there is currently no mechanism to provide Service Instance Identifier (I-SID) configurations, leading to operational complexity and potential misconfiguration in network management.

Innovation Solution

The Resource Reservation Protocol-Traffic Engineering (RSVP-TE) protocol is extended to automatically configure I-SIDs within Backbone Edge Bridges (BEBs) by identifying specific I-SIDs and carrying them in new TLVs or objects such as LSP_ATTRIBUTES or CALL_ATTRIBUTES, ensuring global uniqueness and reducing misconfiguration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration of I-SID in each BEB is used, then network management flexibility is maintained, but operational complexity increases and misconfiguration risks arise

Engineering Contradiction:
Improvenetwork managementVSAvoidconfiguration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mechanism (control plane protocol extension) that automatically distributes I-SID configurations from a centralized controller to distributed BEBs, eliminating manual configuration while maintaining network management flexibility through the control plane interface

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If automatic I-SID configuration mechanism is implemented, then operational complexity is reduced and misconfiguration is prevented, but protocol complexity increases

Engineering Contradiction:
ImproveI-SID configurationVSAvoidprotocol complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extends existing RSVP-TE protocol objects (LSP_ATTRIBUTES, CALL_ATTRIBUTES) to carry I-SID information, allowing a single protocol extension to serve multiple functions: automatic I-SID distribution, configuration synchronization, and collision prevention across the network

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The BEBs automatically receive and configure I-SID values through the extended RSVP-TE signaling protocol without requiring manual intervention, with the system self-configuring I-SIDs based on service identification information carried in protocol messages

Inventive Principle:
Principle #25Self-service

3Manufacturing precision

If I-SID configuration is automated through control plane, then configuration accuracy is improved, but control plane overhead increases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidcontrol plane overhead
Core Design Contradiction:
Manufacturing precisionVSQuantity of substance

Solution Approach 1:

The patent merges I-SID configuration information with existing RSVP-TE signaling messages (LSP setup, path routing), combining multiple configuration tasks into a single protocol exchange to minimize control plane overhead while ensuring accurate I-SID distribution

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3119042B1A system and method of automatically configuring i-sids in gmpls controlled ethernet provider backbone bridged networks
Publication Date: 2017.10.25 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP3119042B1 patent drawing
  • EP3119042B1 patent drawing
  • EP3119042B1 patent drawing

AI summary

A system and method of automatically configuring an Service Instance Identifier (I-SID) in a Generalized Multiprotocol Label Switching (GMPLS) controlled network. The method comprises 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.