MBS Session Context for Mobility Between Access Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication technologies face challenges in enabling seamless multicast service data transport for mobility between multicast/broadcast service (MBS) supporting and non-supporting access nodes, particularly in 5G networks, where not all base stations support MBS, leading to disruptions during handovers.
Innovation Solution
The system establishes radio resources using an MBS session context that associates multicast and unicast Quality of Service (QoS) flow IDs, allowing for the continuation of MBS sessions during mobility events by transitioning between multicast and unicast delivery methods based on the capabilities of target base stations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multicast service data transport is implemented in 5G networks, then service quality and data rates are improved, but network complexity increases due to the need to support both MBS supporting and non-supporting base stations
Solution Approach 1:
The patent introduces an intermediary mechanism where the source base station prepares both MBS and unicast session contexts before handover. When mobility occurs, the system uses the appropriate context (MBS if target supports it, unicast if target doesn't support it) as an intermediary to ensure continuous service. This mediator approach allows seamless transition between different delivery modes without requiring complete network redesign.
Solution Approach 2:
The patent implements multi-functionality by enabling base stations to operate in both MBS and unicast modes. The wireless device can receive service from MBS-capable base stations using multicast delivery, and from non-MBS base stations using unicast delivery. This universal approach allows the network to maintain service continuity across heterogeneous nodes without requiring all base stations to support MBS.
2Adaptability or versatility
If handover between MBS supporting and non-supporting base stations is enabled, then network coverage is expanded, but service disruption occurs during transition
Solution Approach 1:
The patent applies preliminary action by having the source base station prepare both MBS session context and unicast session context before actual handover occurs. The wireless device also prepares both contexts in advance. When handover is needed, the appropriate pre-prepared context can be immediately activated, eliminating service disruption. This advance preparation ensures that whether the target base station supports MBS or not, the necessary resources are already allocated.
Solution Approach 2:
The patent implements dynamics by allowing the delivery mode (MBS or unicast) to change dynamically based on the target base station's capabilities. The system can switch between multicast and unicast delivery modes during mobility events, adapting the service transmission method to match the capabilities of the current network node while maintaining continuous service.
3Adaptability or versatility
If unicast delivery is used as fallback for non-MBS base stations, then compatibility is improved, but resource efficiency decreases
Solution Approach 1:
The patent applies local quality by tailoring the delivery method to the specific characteristics of each base station. MBS-capable base stations receive multicast delivery for efficient resource utilization, while non-MBS base stations receive unicast delivery for compatibility. This localized adaptation ensures that each node receives the appropriate service mode matched to its capabilities, optimizing both efficiency and compatibility at the local level.
Data Source
AI summary
Embodiments include systems and methods for enabling multicast service data transport for mobility between multicast/broadcast service (MBS) supporting and non-MBS supporting access nodes. Various aspects include methods for supporting an MBS session. In some embodiments, an MBS session context may indicate at least one multicast flow identifier (ID) for an MBS session and a unicast Quality of Service (QoS) flow ID for a unicast Packet Data Unit (PDU) session, wherein the MBS session context associates the unicast QoS flow ID with the at least one multicast flow ID.