MBS Time-Domain Resource Allocation for State-Based TDRA Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current NR MBS technologies face challenges in determining appropriate time domain resource allocation (TDRA) lists for multicast and broadcast traffic, particularly for terminal devices in idle or inactive states without an active RRC connection, leading to misinterpretation of TDRA fields in DCI formats 1_0 and 1_1.

Innovation Solution

A mechanism to determine TDRA lists based on identifiers for scrambling DCI, RRC state, and type of traffic configured for the terminal device, ensuring a common understanding of TDRA fields for devices receiving multicast, broadcast, and unicast traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If DCI formats 1_0 and 1_1 are used for scheduling multicast traffic PDSCH resources, then unicast scheduling mechanisms can be maintained, but terminal devices in idle or inactive states cannot properly interpret TDRA fields

Engineering Contradiction:
Improvecompatibility with unicast schedulingVSAvoidTDRA field interpretation accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies local quality by configuring different TDRA tables for different RRC states. Terminal devices in RRC_CONNECTED state use one TDRA table configuration, while devices in RRC_IDLE or RRC_INACTIVE states use another TDRA table configuration. This allows the system to maintain compatibility with unicast scheduling mechanisms while ensuring reliable TDRA field interpretation for multicast traffic specifically针对 each state's characteristics.

Inventive Principle:
Principle #3Local quality

2Device complexity

If a single TDRA configuration is used for all terminal devices, then system complexity is reduced, but optimal resource allocation for different RRC states cannot be achieved

Engineering Contradiction:
ImproveTDRA configuration managementVSAvoidscheduling efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent implements dynamics by making the TDRA table selection dynamic based on the terminal device's RRC state. The network device determines which TDRA table to use based on whether the terminal is in RRC_CONNECTED, RRC_IDLE, or RRC_INACTIVE state. This dynamic adaptation allows optimal resource allocation for different states while the terminal device follows clear state-based selection rules, balancing complexity and efficiency.

Inventive Principle:
Principle #15Dynamics

3Measurement precision

If multiple TDRA tables are configured for different RRC states, then accurate resource allocation is achieved, but terminal device complexity increases

Engineering Contradiction:
Improvetime domain resource allocation accuracyVSAvoidTDRA table selection and management
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies self-service by enabling terminal devices to autonomously select the appropriate TDRA table based on their own RRC state without requiring complex network signaling or device intervention. The selection rule is state-dependent: devices in RRC_CONNECTED use one configuration, while devices in RRC_IDLE or RRC_INACTIVE use another. This self-service approach achieves accurate resource allocation while keeping terminal device complexity manageable through clear, state-based selection criteria.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12538316B2Time domain resource allocation for multicast broadcast service
Publication Date: 2026.01.27 NOKIA TECHNOLOGIES OY
  • US12538316B2 patent drawing
  • US12538316B2 patent drawing
  • US12538316B2 patent drawing

AI summary

Embodiments of the present disclosure relate to time domain resource allocation for multicast broadcast service. A first device receives, from a second device, DCI comprising a TDRA field, and determines, based on at least one of an identifier for scrambling the DCI, a RRC state of the first device or a type of traffic configured for the first device, a TDRA list from a set of configurations for TDRA. Then the first device applies, based on the TDRA list, the TDRA field for reception of the traffic from the second device. In this way, a TDRA list to be used may be determined in an optimal manner, with all terminal devices receiving multicast and broadcast traffic determining common values for time domain resources where data traffic would be scheduled.