Operator-Service-Tag Binding for UE Applications and UPF Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile network operators face challenges in managing user equipment (UE) sessions for latency-sensitive applications in multi-edge access computing (MEC) architectures, where centralized control-plane and distributed user-plane configurations lead to gaps in service differentiation and complexity in managing multiple PDU sessions within a single data network name (DNN).
Innovation Solution
Introduce an operator-defined data field, referred to as the Operator-Service-Tag, which indicates network service configurations to select appropriate user plane functions (UPFs) for PDU sessions, allowing service differentiation within a single DNN by specifying whether a UPF instance is deployed at the edge or central location and its encryption capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized control-plane and distributed user-plane configuration is used in MEC architectures, then service differentiation for latency-sensitive applications is improved, but device complexity and configuration management complexity increase
Solution Approach 1:
The patent introduces an operator-defined data field (Operator-Service-Tag) that encodes network service configuration parameters. This allows the network to indicate UPF deployment location (edge vs. central) and encryption capabilities through standardized parameter values, enabling service differentiation without increasing structural complexity
Solution Approach 2:
The Operator-Service-Tag field serves multiple functions simultaneously: it indicates UPF deployment location, specifies encryption capabilities, and guides PDU session establishment. This multi-functional approach consolidates multiple configuration indicators into a single field, reducing overall configuration complexity
2Adaptability or versatility
If multiple PDU sessions are managed within a single DNN, then service differentiation is improved, but the quantity of configuration parameters and management overhead increase
Solution Approach 1:
The patent merges multiple configuration indicators (UPF deployment location, encryption capabilities, session management parameters) into a single Operator-Service-Tag field. This consolidation allows multiple PDU sessions with different service requirements to be managed within a single DNN without proportionally increasing configuration parameter quantity
Solution Approach 2:
By encoding network service configuration into standardized parameter values within the Operator-Service-Tag, the patent enables efficient representation of multiple service configurations. The core network can indicate different UPF types (edge-deployed or centrally-deployed) and encryption capabilities using predefined parameter values, reducing the need for extensive custom configuration parameters
Data Source
AI summary
Techniques are provided for operator specific customization of a network service configuration. In some embodiments, an operator defines a mapping between an application executing on a user equipment (UE) and a network service configuration. In some embodiments, the network service configuration indicates whether the application is to be supported via a UPF instance located within the core network or deployed at a network edge. The mapping is then provided to the UE, and passed back to the core network, for example, when the UE establishes a connection on behalf of the UE application. The core network then supports the UE application consistent with the configuration specified by the mapping.