Handling high data rates in protocol stack when using high frequency spectrum

Patent metadata

Field	Value
Publication number	US-12369067-B2
Application number	US-202117439342-A
Country	US
Kind code	B2
Filing date	May 10, 2021
Priority date	May 10, 2021
Publication date	Jul 22, 2025
Grant date	Jul 22, 2025

Abstract

To accommodate a mix of high frequency carriers and lower frequency carriers, a protocol stack may include a radio link control (RLC) entity that allows configuration of status reporting control parameters on per carrier, or per subcarrier spacing. Alternatively, a protocol stack may include two RLC entities, one for handling high frequency carriers, and another for handling lower frequency carriers. (High frequency carriers and lower frequency carriers may be distinguished based on a frequency threshold.) Furthermore, a user equipment may transmit (to the network) an indication of its L2 buffer size. The network may configure the UE and/or control scheduling, to ensure the UE's L2 buffer does not overrun. Alternatively, the UE may indicate that it can support a percentage of a maximum buffer size. The network may configure the UE and/or control scheduling so that the UE's buffer occupancy does not exceed the percentage.

First claim

We claim:

1. A baseband processor comprising processing circuitry, wherein the processing circuitry is configured to perform operations including:
configuring a protocol stack to use a plurality of carriers, wherein the protocol stack includes a first radio link control (RLC) entity and a second RLC entity, both interfaced with a packet data convergence protocol (PDCP) entity, wherein the carriers include one or more first carriers whose respective carrier frequencies are below a frequency threshold, and one or more second carriers whose respective carrier frequencies are greater than or equal to the frequency threshold, wherein said configuring includes configuring the first carriers differently from the second carriers including:
configuring the first RLC entity to handle the first carriers, wherein the first RLC entity is configured to use a first value of a status reporting control parameter for the first carriers; and
configuring the second RLC entity to handle the second carriers, wherein the second RLC entity is configured to use a second value of the status reporting control parameter, wherein the second value is configured for the second carriers separately from the first value and is configured to be smaller than the first value, wherein the status reporting control parameter represents an amount of time to count, starting from a time of last uplink feedback transmission, before allowing another uplink feedback transmission.

2. The baseband processor of claim 1 , wherein the status reporting control parameter represents:
an amount of time to count, starting from a last poll request, before re-transmitting the same poll request, in case there was no status report from the last poll request, or
a number of protocol data unit (PDUs) to count between successive poll request transmissions; or
a number of bytes to be transmitted between successive poll request transmissions.

3. The baseband processor of claim 1 , wherein the first and second RLC entities are configured so that one or more RLC parameter values relating to round trip time are smaller for the second RLC entity than for the first RLC entity.

4. The baseband processor of claim 1 , wherein said configuring is performed in response to reception of configuration signals from a base station.

5. A method, comprising:
configuring a protocol stack to use a plurality of carriers, wherein the protocol stack includes a first radio link control (RLC) entity and a second RLC entity, both interfaced with a packet data convergence protocol (PDCP) entity, wherein the carriers include one or more first carriers whose respective carrier frequencies are below a frequency threshold, and one or more second carriers whose respective carrier frequencies are greater than or equal to the frequency threshold, wherein said configuring includes configuring the first carriers differently from the second carriers including:
configuring the first RLC entity to handle the first carriers, wherein the first RLC entity is configured to use a first value of a status reporting control parameter for the first carriers; and
configuring the second RLC entity to handle the second carriers, wherein the second RLC entity is configured to use a second value of the status reporting control parameter, wherein the second value is configured for the second carriers separately from the first value and is configured to be smaller than the first value, wherein the status reporting control parameter represents an amount of time to count, starting from a time of last uplink feedback transmission, before allowing another uplink feedback transmission.

6. The method of claim 5 , wherein the status reporting control parameter represents:
an amount of time to count, starting from a last poll request, before re-transmitting the same poll request, in case there was no status report from the last poll request, or
a number of protocol data unit (PDUs) to count between successive poll request transmissions; or
a number of bytes to be transmitted between successive poll request transmissions.

7. The method of claim 5 , wherein the first and second RLC entities are configured so that one or more RLC parameter values relating to round trip time are smaller for the second RLC entity than for the first RLC entity.

8. The method of claim 5 , wherein the method is performed by a user equipment (UE), wherein said configuring is performed in response to reception of configuration signals from a base station.

9. The method of claim 5 , wherein the method is performed by a network element.

10. The method of claim 5 , wherein the method is performed by a base station.

11. A user equipment (UE), comprising:
a radio; and
a processor communicatively coupled to the radio, wherein the radio and the processor are configured to perform operations comprising:
configuring a protocol stack to use a plurality of carriers, wherein the protocol stack includes a first radio link control (RLC) entity and a second RLC entity, both interfaced with a packet data convergence protocol (PDCP) entity, wherein the carriers include one or more first carriers whose respective carrier frequencies are below a frequency threshold, and one or more second carriers whose respective carrier frequencies are greater than or equal to the frequency threshold, wherein said configuring includes configuring the first carriers differently from the second carriers including:
configuring the first RLC entity to handle the first carriers, wherein the first RLC entity is configured to use a first value of a status reporting control parameter for the first carriers; and
configuring the second RLC entity to handle the second carriers, wherein the second RLC entity is configured to use a second value of the status reporting control parameter, wherein the second value is configured for the second carriers separately from the first value and is configured to be smaller than the first value, wherein the status reporting control parameter represents an amount of time to count, starting from a time of last uplink feedback transmission, before allowing another uplink feedback transmission.

12. The UE of claim 11 , wherein the status reporting control parameter represents:
an amount of time to count, starting from a last poll request, before re-transmitting the same poll request, in case there was no status report from the last poll request, or
a number of protocol data unit (PDUs) to count between successive poll request transmissions; or
a number of bytes to be transmitted between successive poll request transmissions.

13. The UE of claim 11 , wherein the first and second RLC entities are configured so that one or more RLC parameter values relating to round trip time are smaller for the second RLC entity than for the first RLC entity.

14. The UE of claim 11 , wherein said configuring is performed in response to reception of configuration signals from a base station.

Assignees

• Apple Inc

Inventors

• Palle Venkata Naveen Kumar R
• Rossbach Ralf
• Zhang Dawei
• Hu Haijing
• Xu Fangli
• Chen Yuqin
• Wu Zhibin
• Vangala Sarma V
• Nimmala Srinivasan
• Lovlekar Srirang A
• Gurumoorthy Sethuraman

Classifications

• H04W80/02

  Data link layer protocols · CPC title

• H04W28/0278

  using buffer status reports (dynamic wireless traffic scheduling definition H04W72/12) · CPC title

• H04L1/1812

  Hybrid protocols; Hybrid automatic repeat request [HARQ] · CPC title

• H04L45/245

  Link aggregation, e.g. trunking · CPC title

• H04W28/0231 Primary

  based on communication conditions (dynamic wireless traffic scheduling definition based on channel quality criteria H04W72/54) · CPC title