Session-Based SDN Policy Engine for Network Traffic Management

Solution Overview

Problem

Conventional SDN controllers face scalability and resource efficiency issues due to IP flow level control, which is resource-intensive and costly, especially in large and busy networks with millions or billions of active IP flows.

Innovation Solution

Implementing session-based SDN management using a policy engine that determines 3GPP session information and generates SDN policy information to provide quality of service (QoS) for SDN-related traffic, correlating it with 3GPP sessions using a source address associated with the user device, thereby grouping related IP flows into sessions and reducing memory needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If IP flow level control is implemented in SDN controllers, then network traffic management capability is improved, but resource consumption (memory, processing) increases significantly

Engineering Contradiction:

Improvenetwork traffic management capabilityVSAvoidmemory resources

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple IP flows that belong to the same 3GPP session into a single aggregated flow representation. Instead of maintaining separate flow entries for each individual IP flow in the SDN controller, flows are consolidated at the session level, reducing the number of flow entries from millions/billions to a manageable number while preserving QoS capabilities through session-level policy enforcement.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent implements a universal session-level control mechanism that can handle multiple IP flows simultaneously through a single flow entry. The SDN controller uses 3GPP session identifiers to group and manage multiple flows under unified QoS policies, making the control system scalable and resource-efficient while maintaining the ability to differentiate and control individual flows when necessary.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If IP flow level control is implemented in SDN controllers, then network traffic management capability is improved, but operational expenses increase

Engineering Contradiction:

Improvenetwork traffic management capabilityVSAvoidoperational expenses

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent merges multiple IP flows that belong to the same 3GPP session into a single aggregated flow representation. Instead of maintaining separate flow entries for each individual IP flow in the SDN controller, flows are consolidated at the session level, reducing the number of flow entries from millions/billions to a manageable number while preserving QoS capabilities through session-level policy enforcement.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent uses 3GPP session information as a template or copy to create SDN flow entries. Rather than maintaining complete flow state information for every IP flow, the system copies essential QoS parameters from 3GPP session records and applies them to aggregated flows, reducing storage requirements and processing overhead while maintaining control capabilities.

Inventive Principle:

Principle #26Copying

3Productivity

If flow information is frequently updated in switches to reduce unused entries, then processing efficiency is improved, but scalability and resource efficiency remain problematic

Engineering Contradiction:

Improvepacket processing efficiencyVSAvoidscalability

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent merges multiple IP flows that belong to the same 3GPP session into a single aggregated flow representation. Instead of maintaining separate flow entries for each individual IP flow in the SDN controller, flows are consolidated at the session level, reducing the number of flow entries from millions/billions to a manageable number while preserving QoS capabilities through session-level policy enforcement.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent extracts and removes unnecessary flow-level details from the SDN controller, keeping only essential QoS parameters and session identifiers. By taking out the granular IP flow state information and storing it in distributed switches rather than centralizing it in the controller, the system reduces controller memory requirements and improves scalability while maintaining the ability to enforce QoS policies.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS10148509B2Methods, systems, and computer readable media for session based software defined networking (SDN) management

Publication Date: 2018.12.04 ORACLE INT CORP

AI summary

Methods, systems, and computer readable media for session based software defined networking (SDN) management are disclosed. According to one method, the method occurs at a policy engine. The method includes determining, using a session identifier, Third Generation Partnership Project (3GPP) session information associated with a user device. The method also includes generating, using the 3GPP session information, SDN policy information for SDN related traffic associated with the 3GPP session, wherein the SDN policy information is for providing a quality of service (QoS) for the SDN related traffic corresponding to a QoS associated with the 3GPP session information, wherein the SDN related traffic is correlated with the 3GPP session using a source address associated with the user device.