Network Services Orchestration Module for Policy-Based Traffic Steering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network services orchestration solutions face challenges in managing complex service chains, handling hardware-based services, and optimizing performance and scale, as they often require manual intervention, restrict hardware implementations, and fail to efficiently route packets through ordered services.
Innovation Solution
A network services orchestration module that uses a service management northbound API to specify service data, including instance pools and performance types, with an instance management submodule for virtual and hardware-based instances, and an autoscaling and power management submodule to monitor statistics and adjust service instances, coupled with a steering module for policy-based traffic steering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If network services are managed as part of end user services orchestration, then service chaining is enabled, but hardware-based services cannot be included and manual intervention is required for routing changes
Solution Approach 1:
The patent replaces manual routing configuration with automated software-based flow steering. The steering module automatically programs flow rules on switches to route packets through hardware services without manual intervention, substituting the mechanical process of manual routing changes with automated software control.
Solution Approach 2:
The steering module acts as an intermediary between the orchestration system and hardware services. It receives service chain requirements, determines optimal routing paths, and automatically configures switches to steer traffic through hardware services, eliminating the need for direct manual routing configuration.
2Adaptability or versatility
If virtual appliances are used for network services, then orchestration flexibility is improved, but hardware-based services and bare metal implementations are excluded
Solution Approach 1:
The patent creates a universal orchestration framework that handles multiple service types through a single steering module. This module can steer traffic to virtual appliances, hardware services, or bare metal implementations based on service chain requirements, making the system multi-functional and adaptable to different deployment scenarios without requiring separate management mechanisms.
3Adaptability or versatility
If complex routing solutions using ACLs are programmed into switches, then service chaining is achieved, but reconfiguration requires manual intervention and is complex
Solution Approach 1:
The patent segments the routing function into a dedicated steering module that operates independently from service chain configuration. This module receives high-level service chain requirements, determines optimal paths, and automatically generates simplified flow rules for switches, separating complex routing logic from service configuration and reducing overall system complexity.
4Ease of operation
If service instances are manually configured, then precise control is achieved, but scaling and resource optimization are inefficient
Solution Approach 1:
The patent implements self-service through the autoscaling submodule that automatically monitors service demand and adjusts instance allocation without manual intervention. The system self-adjusts the number of active service instances based on real-time traffic patterns and service chain requirements, optimizing resource utilization while maintaining precise control through automated decision-making.
Data Source
AI summary
A method and apparatus for providing network services orchestration are described herein. The apparatus comprises a network controller that runs a network services orchestration module. The network services orchestration module has a service management northbound application programming interface (API), an instance management submodule, an autoscaling and power management submodule, and an instance location southbound API. A steering module is also described herein that includes a steering northbound API and an instance location northbound API.


