Orchestration Server NSH Header Embedding for NFV Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In virtualized network function environments, the orchestrator faces significant overhead and performance slowdowns due to the need for prepopulation with subscriber details or making API calls to obtain necessary information, leading to memory/storage requirements and latency issues.
Innovation Solution
A system where an authentication server provides data to an orchestration server, which embeds relevant information into payload headers using the Network Service Header (NSH) protocol, allowing the orchestration server to route virtualized network functions without a priori knowledge of subscriber requirements, thus eliminating the need for prepopulation and API calls.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the orchestrator prepopulates with subscriber details, then the orchestrator can make routing decisions, but memory/storage requirements increase significantly
Solution Approach 1:
The patent extracts the subscriber details storage function from the orchestrator and relocates it to the authentication server. The orchestrator only retains the capability to make routing decisions based on received information, while the actual subscriber data resides externally at the authentication server, reducing the orchestrator's memory burden.
Solution Approach 2:
The patent introduces an intermediary mechanism (the authentication server) that acts as a mediator between the orchestrator and subscriber data. Instead of the orchestrator directly storing and managing subscriber details, it receives processed routing information from the authentication server, which serves as the intermediary holding and processing the actual subscriber data.
2Ease of operation
If the orchestrator makes API calls to obtain subscriber information, then routing decisions can be made, but latency increases and performance slows down
Solution Approach 1:
The patent applies preliminary action by having the authentication server prepare and embed the necessary routing information into packet headers in advance, during the authentication process. This eliminates the need for the orchestrator to make time-consuming API calls later, as the information is already prepared and attached to the packets before they reach the orchestrator.
Solution Approach 2:
The system enables self-service by having the authentication server automatically embed the routing information into packet headers without requiring the orchestrator to actively query or request this information. The orchestrator passively receives pre-prepared packets with embedded routing data, eliminating the active API call process and associated latency.
3Measurement precision
If the orchestrator processes each packet with full subscriber details, then accurate routing decisions are made, but processing overhead increases
Solution Approach 1:
The patent extracts only the essential routing information from the complete subscriber details and embeds only this extracted subset into the packet headers. The orchestrator processes only this extracted routing information rather than full subscriber details, reducing processing overhead while maintaining sufficient accuracy for routing decisions.
Solution Approach 2:
The patent applies local quality by embedding routing information specifically in the packet headers where it is most needed for routing decisions, rather than processing all subscriber details throughout the entire packet processing chain. This localized approach ensures routing accuracy at the critical decision point while minimizing overall processing overhead.
Data Source
AI summary
A system leveraging the authentication control plane of a communications network to influence the associated Network Service header (NSH) values on a per subscriber packet basis; thus presenting a subscriber aware service chain header on which influences the processing of virtualized network function (VNF). This system implements vendor specific attributes (VSA) within the authentication provider platform to create an association of subscriber identity which may include MAC address, MAC and IP address as a tuple, circuit identifier string, realm based authentication data, IMSI, in part or in addition to leveraging DHCP Relay information sub options that may be present, which when processed inherit one or multiple vendor specific attributes from the authentication platform. These VSA values, each no greater than 2 bytes define the payload headers the participating subscriber gateway will shim to its layer 2 payload for processing as a Service Chain through one or multiple virtual network functions located elsewhere in the network.