5G Multicast-Broadcast Architecture With Split MBSTF Interfaces

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Challenges arise in delivering a broadcast-multicast service in 5G networks due to ambiguity in the architecture and lack of specificity regarding how to set up and operate such services, leading to subpar performance and diminished throughput.

Innovation Solution

A 5G multicast-broadcast user service architecture is implemented, where the MBSTF is split into a multicast delivery function and a unicast server, enabling a 5MBS architecture with separate interfaces for multicast and unicast traffic, allowing for independent implementation and deployment of a 5MBS client, MBSTF, and a 5MBS application server.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a unified MBSTF architecture is used for multicast-broadcast service, then device complexity is reduced, but service performance and reliability deteriorate due to ambiguity in architecture and lack of specificity

Engineering Contradiction:
Improvearchitecture complexityVSAvoidservice performance
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the MBSTF into two distinct functional entities: a Multicast Delivery Function (MDLF) for multicast traffic and a Unicast Application Server (UCAS) for unicast traffic. This segmentation resolves the technical contradiction by providing specific, well-defined architectures for each function, improving service performance and reliability while maintaining manageable overall system complexity through clear functional separation.

Inventive Principle:
Principle #1Segmentation

2Reliability

If separate interfaces for multicast and unicast traffic are implemented, then service reliability improves, but device complexity increases

Engineering Contradiction:
Improveservice reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements separate interfaces (MBS-4-MC for multicast and MBS-4-UC for unicast) by segmenting the MBSTF into MDLF and UCAS. Each interface is dedicated to its specific traffic type with well-defined protocols and procedures, improving service reliability through specialized handling while managing complexity through clear functional boundaries and independent implementation.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If 5MBS client architecture is implemented with split MBSTF, then service provisioning and use are enhanced, but implementation complexity increases

Engineering Contradiction:
Improveservice provisioning capabilityVSAvoidimplementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent enhances service provisioning capability by implementing a 5MBS client architecture that can independently interact with the segmented MDLF and UCAS through dedicated interfaces. The client can selectively engage multicast or unicast services based on application requirements, improving adaptability and versatility while managing implementation complexity through well-defined, separate interaction protocols for each function.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4385172B1Multicast-broadcast user service architecture
Publication Date: 2025.11.19 QUALCOMM INC
  • EP4385172B1 patent drawingFigure 1
  • EP4385172B1 patent drawingFigure 2
  • EP4385172B1 patent drawingFigure 3

AI summary

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive, from a network entity, a multicast-broadcast user service description message. The UE may communicate, using a multicast-broadcast service (MBS) transport function (MBSTF) client, with an MBS entity of the network entity, in accordance with information included in the user service description message, wherein the MBS entity is split into a multicast delivery function and a unicast application server. Numerous other aspects are described.