Network Slice Enablement Server for Application-Aware QoS Routing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile network technology lacks the ability to proactively inform mobile applications executing on User Equipment (UEs) about the specific network slices being utilized, and applications are unable to obtain or communicate desired Quality of Service (QoS) requirements.

Innovation Solution

Implementing a Network Slice Enablement (NSE) server that interacts with application servers and the mobile core network to identify and inform mobile applications of the network slices to be used for sessions, based on user subscriptions and application identifiers, and provides this information to the applications and users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network slicing is implemented in mobile networks, then network customization and QoS requirements can be met, but network complexity increases

Engineering Contradiction:
Improvenetwork customizationVSAvoidnetwork complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a Network Slice Enablement Server as an intermediary component that mediates between mobile applications and the core network. This server translates application QoS requirements into network slice selections and communicates slice information back to applications, thereby enabling network customization without requiring complex modifications to the application layer or core network infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the network functionality by introducing a dedicated Network Slice Enablement Server that handles slice selection and management tasks separately from the core network operations. This segmentation allows the complex network slicing functionality to be managed as a distinct module, reducing the perceived complexity of the overall network architecture.

Inventive Principle:
Principle #1Segmentation

2Productivity

If applications are informed about network slices, then application performance can be optimized, but information management complexity increases

Engineering Contradiction:
Improveapplication performanceVSAvoidinformation management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent enables mobile applications to self-select appropriate network slices by providing them with the necessary slice information and selection criteria. The Network Slice Enablement Server supplies applications with slice identifiers and characteristics, allowing applications to autonomously make slicing decisions without requiring complex centralized control or manual configuration.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements a feedback mechanism where the Network Slice Enablement Server continuously provides slice selection information to applications based on their QoS requirements and current network conditions. This feedback loop enables dynamic optimization of application performance while keeping information management relatively simple through automated, rule-based slice selection.

Inventive Principle:
Principle #23Feedback

3Loss of information

If network slice information is provided to applications, then network visibility is improved, but data management overhead increases

Engineering Contradiction:
Improvenetwork visibilityVSAvoiddata management overhead
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential network slice information (such as slice identifiers and basic characteristics) that applications need to function effectively, rather than providing complete network state information. This selective extraction reduces data management overhead while maintaining sufficient network visibility for application optimization.

Inventive Principle:
Principle #2Taking out (Extraction)

4Adaptability or versatility

If dynamic network slicing is implemented, then network flexibility increases, but control complexity increases

Engineering Contradiction:
Improvenetwork flexibilityVSAvoidcontrol complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by having the Network Slice Enablement Server pre-establish slice selection policies and criteria based on application QoS requirements. When applications need network resources, the server can quickly match them with appropriate pre-defined slices, enabling dynamic flexibility without requiring complex real-time control decisions for each connection request.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12483978B2Application identity based network slice enablement server
Publication Date: 2025.11.25 VERIZON PATENT & LICENSING INC
  • US12483978B2 patent drawing
  • US12483978B2 patent drawing
  • US12483978B2 patent drawing

AI summary

A network device requests, from a mobile network, a check of network slicing eligibility for a first session involving a first user, a first application, and a first application server. The network device receives, based on the check of network slicing eligibility, network slicing plan information associated with the first user and network slicing configuration information of the mobile network. The network device identifies a network slice identifier (ID) of a first network slice of the mobile network based on an identity of the first application, the network slicing plan information, and the network slicing configuration information; and sends a notification message, that includes the network slice ID, to the first application server for notifying the first application of the first network slice to use for the first session.