5G Communication Behavior Enforcement via API and UDM
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current 5G systems lack the ability to make UE communication behavior restrictions aware, failing to enforce allowed communication behaviors and notify external entities of non-allowed behavior, which is crucial for secure and controlled network operations, especially in mixed deployment scenarios like Non-Public Networks.
Innovation Solution
A method is introduced to set up and manage expected communication behavior in a 5G system through API calls, mapping IP or MAC addresses to subscribers, updating subscriber information, and performing N4 session modifications to enforce communication restrictions, allowing external entities to specify allowed behaviors and actions for unallowed traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If 5G system implements communication behavior restrictions and enforcement mechanisms, then network security and control are improved, but system complexity increases
Solution Approach 1:
The system segments communication behavior management into distinct functional components: behavior definition modules, enforcement modules at different network points (UPF, SMF, AMF), and notification modules. This segmentation allows the complex security enforcement task to be distributed across multiple specialized components rather than centralized in a single complex system.
Solution Approach 2:
The system performs preliminary actions by defining expected communication behaviors in advance through API calls from external entities. These behaviors are stored and prepared before actual communication occurs, allowing the enforcement mechanisms to simply check against pre-defined rules rather than making complex decisions in real-time.
2Adaptability or versatility
If 5G system monitors and enforces UE communication behavior, then network control capability is improved, but processing time and operational complexity increase
Solution Approach 1:
Communication behaviors are defined and stored in advance using API calls from external entities. The system prepares enforcement rules beforehand, so when actual communication occurs, the system only needs to check against pre-defined behaviors rather than analyzing and decide in real-time, significantly reducing processing time.
Solution Approach 2:
The system introduces intermediary components (SMF, UPF, AMF) that handle specific enforcement tasks. These intermediaries act as mediators between the core network and UEs, distributing the monitoring and enforcement workload across multiple specialized functions rather than requiring centralized real-time processing.
3Adaptability or versatility
If 5G system integrates multiple network functions for behavior management, then functionality is improved, but device complexity increases
Solution Approach 1:
The system implements multi-functionality within key network functions. The SMF, for example, handles both session management and communication behavior enforcement. The UPF performs both user plane routing and behavior monitoring. This multi-functionality reduces the need for separate dedicated components for each function, managing complexity while maintaining versatility.
Solution Approach 2:
The system segments behavior management functionality across existing network components rather than creating a single monolithic behavior management device. The AMF handles mobility-related behavior, the SMF handles session-related behavior, and the UPF handles user plane behavior enforcement. This segmentation distributes complexity across existing infrastructure components.
Data Source
AI summary
A communication system includes an external entity and a 5G system (5GS), wherein the 5GS comprises a 5G core (5GC), wherein the 5GC comprises a functional entity, a Unified Data Management (UDM), a Session Management Function (SMF), and a User Plane Function (UPF). A method for setting up expected communication behavior information in the system includes: performing, by the external entity, an Application Programming Interface (API) call via an API of the functional entity and setting up an expected communication behavior for a subscriber or set of subscribers, a data network name (DNN), a 5G virtual network (VN), a slice or a combination thereof that the functional entity is allowed to manage.