Receiver-Side Buffering for Time-Aware Cellular Scheduling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Time-aware scheduling in wireless communication networks increases buffer requirements on the transmitter side, as traffic cannot be transmitted outside designated time windows, even if link capacity is available, posing a burden on devices with limited memory resources.

Innovation Solution

Implementing receiver-side buffering, where the transmitting node informs the receiving node about designated time intervals, allowing preemptive transmission of traffic data outside the designated time window, and the receiving node buffers the data until the next time interval, ensuring compliance with the time-aware schedule while efficiently using available bandwidth.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If time-aware scheduling is implemented with transmitter-side buffering, then traffic can be transmitted within designated time windows, but buffer requirements on the transmitter side increase, burdening devices with limited memory resources

Engineering Contradiction:
Improvetime-aware scheduling complianceVSAvoidbuffer memory resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent inverts the traditional buffering location from the transmitter side to the receiver side. Instead of the transmitter buffering traffic data until the designated time window, the receiver buffers the data after reception. This inversion allows the transmitter to use available link capacity immediately while the receiver handles the timing compliance, thereby reducing transmitter buffer requirements while maintaining scheduling reliability.

Inventive Principle:
Principle #13The other way round (Inversion)

2Reliability

If traffic is restricted to designated time windows only, then time-aware scheduling is maintained, but bandwidth utilization decreases when link capacity is available outside time windows

Engineering Contradiction:
Improvetime-aware scheduling complianceVSAvoidbandwidth utilization
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent enables preliminary transmission of traffic data outside the designated time window by buffering at the receiver side. The transmitter can send data immediately when link capacity is available, and the receiver stores it temporarily until the designated time window arrives. This preliminary action allows full utilization of available bandwidth while ensuring time-aware scheduling compliance through delayed delivery at the receiver.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If transmitter buffers traffic data until designated time windows, then scheduling compliance is ensured, but transmission latency increases even when link capacity is available

Engineering Contradiction:
Improvetime-aware scheduling complianceVSAvoidtransmission latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

By inverting the buffering location to the receiver side, the patent eliminates the waiting time at the transmitter. Data is transmitted immediately when available, and the receiver handles the timing delay by buffering until the designated time window. This inversion transfers the time loss from transmission waiting to receiver buffering, effectively reducing overall transmission latency while maintaining scheduling compliance.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentEP3753286B1Receiver-side buffering for time-aware scheduling across cellular link
Publication Date: 2024.09.18 QUALCOMM INC
  • EP3753286B1 patent drawingFigure 1
  • EP3753286B1 patent drawingFigure 2
  • EP3753286B1 patent drawingFigure 3

AI summary

Apparatus and methods of wireless communications include, at a receiving node, receiving timing information corresponding to a traffic class identifier. The timing information being associated with a time interval for communicating data of a traffic class corresponding to the traffic class identifier. Aspects include receiving traffic data pertaining to the traffic class, determining that the traffic data was transmitted or is received outside the time interval, and then buffering the traffic data. Additionally, aspects include forwarding the traffic data in response to a next occurrence of the time interval. A transmitting node may be configured with complimentary functions.