5G Multicast Session Management via PDU Context Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current multicast and broadcast technologies in 5G NR networks face inefficiencies in content delivery, particularly in supporting dynamic and popular content consumption, with existing architectures requiring significant infrastructure and not natively supporting unicast and multicast capabilities efficiently.
Innovation Solution
The proposed solution enhances the 5G NR architecture by integrating multicast/broadcast support with a minimal footprint over the unicast architecture, using a PDU session modification procedure to manage user equipment context updates and control/user plane network functions, potentially eliminating the need for dedicated middleware like eMBMS, and enabling efficient transport of multicast traffic through network slicing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional multicast/broadcast architecture (e.g., eMBMS) is used, then multicast content delivery is supported, but infrastructure requirements increase and network architecture becomes complex
Solution Approach 1:
The patent merges multicast functionality with the existing unicast PDU session architecture by introducing a flag in the PDU session modification procedure. The SMF and UPF handle both unicast and multicast traffic through the same architectural framework, eliminating the need for separate eMBMS infrastructure. This consolidation reduces network complexity while maintaining multicast delivery capability.
Solution Approach 2:
The PDU session architecture is designed to be universal, handling both unicast and multicast traffic through the same session management mechanism. The UPF and SMF perform multiple functions including unicast routing, multicast routing, and session modification for both traffic types, making the infrastructure multi-functional and reducing overall system complexity.
2Adaptability or versatility
If dedicated multicast infrastructure (e.g., MBMS-GW, eMBMS) is deployed, then multicast service is enabled, but infrastructure footprint increases
Solution Approach 1:
The patent extracts and eliminates the need for dedicated multicast infrastructure components such as MBMS-GW, eMBMS-GW, and separate multicast bearers. By taking out these specialized elements and replacing them with the existing unicast PDU session architecture enhanced with multicast capability flags, the infrastructure footprint is significantly reduced while maintaining full multicast service functionality.
Solution Approach 2:
The existing unicast UPF and SMF are made multi-functional to handle both unicast and multicast traffic. This universality eliminates the need for separate dedicated multicast infrastructure, as the same network elements perform both unicast routing and multicast distribution functions.
3Device complexity
If unicast architecture is used for all traffic, then infrastructure is simplified, but efficient multicast traffic transport is not achieved
Solution Approach 1:
The patent introduces dynamic capability through the PDU session modification procedure, where the network can dynamically switch between unicast and multicast delivery modes based on the service requirements and user equipment capabilities. The flag-based mechanism allows flexible adaptation of the delivery mode without changing the underlying architecture, maintaining simplicity while enabling efficient multicast transport when needed.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An apparatus in a network function comprising at least one processor and at least one memory including computer code for one or more programs, the at least one memory and the computer code configured, with the at least one processor, to cause the apparatus at least to: determine that a protocol data unit session for a user equipment is to be updated to add or modify multicast information; and provide multicast context information associated with said user equipment which causes said user equipment to receive multicast data associated with said multicast context information.