Segment Routing Conduit for Service Provider Network Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems fail to provide customers with the ability to control the constraints and timing of ad hoc services within a service provider's network, limiting their ability to customize the paths on which their traffic is transported and lacking the control over the control plane of the service provider's network.
Innovation Solution
The introduction of a segment routing conduit system, which allows a network element in a first network to control the constraints, timing, and selection of services within a second network by defining a path using segment route identifiers and binding them to network interfaces, enabling customers to manage their traffic as if they owned the infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional path selection systems use the same set of criteria for all requests, then network operation is simplified, but customer control over traffic paths is lost
Solution Approach 1:
The patent segments the path selection process by introducing Segment Routing with Segment Identifiers (SIDs). Each SID represents a specific segment or hop in the network path, allowing customers to compose custom paths by selecting specific segments. This segmentation enables customer-controlled path differentiation while maintaining simplified network operations through standardized SID-based routing instructions.
2Adaptability or versatility
If service providers offer different classes of service, then service differentiation is improved, but basic path selection criteria remain unchanged
Solution Approach 1:
The patent changes the routing parameter from traditional metric-based selection (bandwidth, hop count) to Segment Identifier (SID) based selection. Customers can specify exact path parameters by selecting SIDs that correspond to desired network segments, enabling fine-grained service differentiation without complicating the underlying path selection mechanism. The network simply follows the SID-based instructions provided.
3Adaptability or versatility
If customers want to control the constraints and timing of ad hoc services, then customer control is improved, but network security and infrastructure protection are compromised
Solution Approach 1:
The patent introduces an intermediary mechanism where customers provide high-level routing intent and constraints, and the network's control plane translates these into specific SID-based paths. This intermediary translation layer protects network security by preventing direct access to the control plane while still enabling customer control over service constraints and timing through the SID framework.
4Stability of the object's composition
If traditional routing uses standardized criteria for all traffic, then network stability is maintained, but path differentiation among customers is lost
Solution Approach 1:
The patent introduces dynamic path differentiation through Segment Identifiers while maintaining stable network operations. The SID framework allows routing instructions to be dynamically customized per customer and service type, yet the underlying network stability is preserved because SIDs are processed as standardized routing instructions through the existing control plane, maintaining compositional stability.
Data Source
AI summary
Utilizing the systems disclosed herein, a network element (in a network) controls, within another network, the constraints of a service, timing of the creation of the service, and selection a service on which a packet is transmitted. For example, a first network element (located in a first network) receives a request associated with initiating a service. The request is received from a second network element located in a second network and includes at least one path constraint. The first network element controls creation of the service in the first network on behalf of the second network element located in the second network by, e.g., identifying a path based, at least in part, on the at least one path constraint; and binding an identifier and an interface to the path, wherein the interface is associated with one or more operation to perform on any traffic that is labeled with the identifier.