PDU Session Request for MBS Joining in 5G Networks

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current 3GPP specifications do not define how a User Equipment (UE) can request to join a Multicast Broadcast Services (MBS) session using the PDU session establishment procedure for existing or Multi-Access (MA) PDU sessions, other than for new PDU sessions.

Innovation Solution

A method where a UE sends a PDU session establishment request message with a Requested MBS container IE and specific request types to initiate a PDU session establishment procedure for joining an MBS session, indicating whether it is for an existing PDU session or an MA PDU session, allowing scenarios such as handover from non-3GPP to 3GPP, transferring 4G PDN connections to 5G, and establishing user-plane resources over 3GPP for MA PDU sessions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the PDU session establishment procedure is used for new PDU sessions only, then the specification is simple and clear, but it cannot support MBS session joining for existing or MA PDU sessions

Engineering Contradiction:

ImproveMBS session joining capabilityVSAvoidprocedure complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The PDU session establishment procedure is extended to serve multiple purposes: it can be used for new PDU session establishment, existing PDU session MBS joining, and MA PDU session MBS joining. This is achieved by introducing a request type field that distinguishes between different scenarios, allowing one procedure to handle multiple functions without creating separate procedures for each case.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The procedure is modified by adding a request type parameter that can take different values (e.g., first value for new PDU session, second value for existing PDU session, third value for MA PDU session). This parameter change allows the same procedure framework to adapt to different MBS joining scenarios, resolving the contradiction between versatility and complexity.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If separate procedures are defined for different MBS joining scenarios, then each scenario is handled specifically, but the overall system complexity increases

Engineering Contradiction:

Improvescenario handling accuracyVSAvoidprocedure complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

Instead of creating separate procedures for new PDU session MBS joining, existing PDU session MBS joining, and MA PDU session MBS joining, a single unified PDU session establishment procedure is designed to handle all three scenarios. The request type field acts as a dispatcher that routes each scenario to the appropriate handling logic within the same procedure, maintaining reliability while reducing complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Multiple MBS joining procedures are merged into one unified PDU session establishment procedure. By combining the handling of new PDU sessions, existing PDU sessions, and MA PDU sessions into a single procedure with a request type discriminator, the system achieves scenario-specific reliability without the overhead of multiple separate procedures.

Inventive Principle:

Principle #5Merging (Combining)

3Adaptability or versatility

If the PDU session establishment procedure is extended to existing and MA PDU sessions, then MBS session joining is supported for all scenarios, but the procedure becomes more complex

Engineering Contradiction:

ImproveMBS session joining coverageVSAvoidprocedure simplicity

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The PDU session establishment procedure is enhanced by introducing a request type parameter that can indicate different scenarios (new PDU session, existing PDU session, MA PDU session). This parameter-based approach allows the procedure to adapt to different MBS joining scenarios without requiring complex conditional logic or separate procedures, maintaining ease of operation while achieving full scenario coverage.

Inventive Principle:

Principle #35Parameter changes

Solution Approach 2:

The procedure is segmented by request type, where different values of the request type field direct the processing to different handling paths. This segmentation allows each MBS joining scenario to be handled with specific logic while maintaining a unified procedure structure, balancing versatility with operational simplicity.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS20240057217A1Request to join MBS session during establishment procedure

Publication Date: 2024.02.15 MEDIATEK INC

AI summary

A method for requesting to join an MBS session via a PDU session establishment procedure for existing PDU or MA PDU session is provided. A UE sends a PDU session establishment request message that includes a requested MBS container IE to request to join an MBS session. The request message initiates a PDU session establishment procedure, with a request type indicating that the PDU session establishment procedure is for an existing PDU session, or for an MA PDU session. A specific request type is used to indicate: 1)HANDOVER 5G PDU SESSION FROM NON-3GPP TO 3GPP; 2) TRANSFER 4G PDN CONNECTION (EPS) TO 5G; 3) TRANSFER 4G PDN CONNECTION (NON-3GPP) TO 5G; 4) ESTABLISH UP RESOURCE OVER 3GPP FOR 5G MA PDU; and 5) TRANSFER MA PDU (PDN LEG IN EPS) TO 5G MA PDU.