DSDA Uplink Scheduling to Avoid Voice-Data Transmission Collisions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Dual SIM dual active (DSDA) user equipment (UE) experiences collisions between transmission data for voice and data subscribers due to prioritization of voice traffic, leading to increased block error rate (BLER) and reduced data throughput, as the data subscriber's transmissions are often blanked during voice prioritization periods, resulting in modulation and coding scheme (MCS) penalties and degraded performance.

Innovation Solution

Implementing a modified skipUplinkTxDynamic feature in DSDA UE to skip assembly and transmission of PUSCH for data subscriber during collisions, buffer L2 packets for blanked transmissions, and trigger a scheduling request (SR) to recover UL grants, avoiding BLER association and MCS penalties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If voice traffic is prioritized during transmission collisions in DSDA UE, then voice communication quality is improved, but data transmission throughput deteriorates significantly

Engineering Contradiction:

Improvevoice communication qualityVSAvoiddata transmission throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary detection of transmission collisions between voice and data subscribers before actual transmission occurs. When a collision is detected, the data PUSCH transmission is proactively skipped in advance, preventing the collision from affecting voice quality while preserving data transmission opportunities through subsequent scheduling requests and grants.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If data transmission is skipped during voice prioritization periods, then voice communication reliability is improved, but data throughput loss increases to 99%

Engineering Contradiction:

Improvevoice communication reliabilityVSAvoiddata throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system implements a feedback mechanism where the UE monitors transmission collisions and sends scheduling requests (SR) to the network when data transmission is skipped due to voice prioritization. The network responds with uplink grants that allow data transmission in subsequent non-collision periods, creating a closed-loop feedback system that recovers data throughput while maintaining voice quality.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system temporarily discards data PUSCH transmission when voice collision occurs, but recovers the data transmission opportunity through scheduling requests and subsequent network grants. This allows the system to sacrifice short-term data transmission in favor of voice quality while ensuring long-term data throughput recovery through the feedback mechanism.

Inventive Principle:

Principle #34Discarding and recovering

3Productivity

If data PUSCH transmission is performed during voice collision, then data throughput is maintained, but block error rate increases and MCS penalties are applied

Engineering Contradiction:

Improvedata throughputVSAvoidtransmission reliability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system performs preliminary detection of voice transmission collisions before data PUSCH transmission. When a collision is detected, the data transmission is skipped in advance, preventing BLER association and MCS penalties from occurring. This proactive approach maintains transmission reliability while preserving data throughput through subsequent scheduling recovery.

Inventive Principle:

Principle #10Preliminary action

4Productivity

If scheduling requests are triggered frequently to recover UL grants, then data throughput recovery is improved, but signaling overhead increases

Engineering Contradiction:

Improvedata throughput recoveryVSAvoidsignaling overhead

Core Design Contradiction:

ProductivityVSLoss of information

Solution Approach 1:

The system triggers scheduling requests selectively rather than continuously - specifically when data PUSCH transmission is skipped due to voice collision. This partial action approach recovers data throughput only when necessary, avoiding excessive signaling overhead during normal operation while ensuring throughput recovery when collisions occur.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS12610358B2Systems and methods for reducing transmission data collision for dual subscriber dual active devices

Publication Date: 2026.04.21 APPLE INC

AI summary

Systems and methods for reducing collisions of transmission data for a first subscriber (e.g., a voice subscriber) with transmission data for a second subscriber (e.g., a data subscriber) at a dual sim dual active (DSDA) user equipment (UE) are described herein. A DSDA UE may be configured to implement a modified skipUplinkTxDynamic feature that avoids collisions by buffering transmission data of the data subscriber and sending a (later) scheduling request (SR) for a grant for that data. A DSDA UE may regulate data subscriber transmissions to avoid a transmission duration for the voice subscriber. A DSDA UE may reduce certain transmissions for a voice subscriber (subject to a block error rate (BLER) threshold for the voice subscriber) to lower the probability of collision. A DSDA UE may operate a data subscriber and a voice subscriber in the same cell to avoid collisions due to RF tuning and/or relative slot overlap.