IP Library › Granted Patent US 12,302,166
Granted Patent B2
US 12,302,166 · App. 18/442,215 · Granted May 13, 2025

Wireless communications apparatus and methods

Inventors: Vivek Sharma (Basingstoke, GB); Samuel Asangbeng Atungsiri (Basingstoke, GB); Shin Horng Wong (Basingstoke, GB); Kazuyuki Shimezawa (Basingstoke, GB); Hideji Wakabayashi (Basingstoke, GB)
Assignee: SONY GROUP CORPORATION
H04W28/0263H04W28/0268H04W28/0273H04W80/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,302,166
App. No.
18/442,215
Granted
May 13, 2025
Kind
B2
Abstract

A method of transmitting data by a communications device, the method comprising receiving a plurality of service data units including a first service data unit and a second service data unit at a Service Data Adaptation Protocol (SDAP), service access point (SAP) according to one or more quality of service (QoS) flows, each of the QoS flows defining a quality of service for the data received from the service data units, mapping the service data units received according to the one or more QoS flows on to one or more radio bearers, each of the one or more radio bearers being defined by a packet data convergence protocol (PDCP) entity within a PDCP layer, forming the service data units into protocol data units for transmission via the radio bearer to which the corresponding QoS flow has been mapped, and transmitting the protocol data units via the corresponding radio bearer.

Claims (76)

1. A method of transmitting data by a communications device, the method comprising

receiving a plurality of service data units including a first service data unit and a second service data unit at a Service Data Adaptation Protocol (SDAP) service access point (SAP) according to one or more quality of service (QOS) flows, each of the one or more QoS flows defining a QoS for data received from the service data units,

determining whether the second service data unit has a relative priority higher than a relative priority of the first service data unit;

mapping the first and second service data units according to the one or more QoS flows on to one or more radio bearers, each of the one or more radio bearers being defined by a packet data convergence protocol (PDCP) entity within a PDCP layer,

forming the first and second service data units into protocol data units for transmission via the one or more radio bearers to which the corresponding QoS flow has been mapped;

transmitting the protocol data units via the corresponding radio bearer according to the mapping,

wherein the first and second service data units are associated with a first QoS flow mapped to a first dedicated radio bearer (DRB), and

wherein the first DRB is associated with a first DRB priority; and

in response to at least one of determining that the second service data unit has a relative priority higher than a relative priority of the first service data unit, and a congestion threshold being met, associating the first QoS flow with a second DRB, the second DRB associated with a second DRB priority higher than the first DRB priority.

2. The method according to claim 1 , further comprising:

in response to the determining,

assigning a first PDCP sequence number to the first service data unit, and

assigning a second PDCP sequence number to the second service data unit,

wherein the first PDCP sequence number is higher than the second PDCP sequence number.

3. The method according to claim 2 , further comprising:

compressing a header associated with the first service data unit and a header associated with the second service data unit in accordance with the assigned first and second PDCP sequence numbers, respectively.

4. The method according to claim 1 , further comprising:

starting a first discard timer associated with the first service data unit, the first discard timer expiring after a first timer duration, and

starting a second discard timer associated with the second service data unit, the second discard timer expiring after a second timer duration,

wherein the second timer duration is longer than the first timer duration.

5. The method according to claim 1 , wherein the associating comprises initiating a QoS flow relocation procedure.

6. The method according to claim 1 , further comprising:

generating a SDAP protocol data unit (PDU), the SDAP PDU comprising the second service data unit and an SDAP header,

wherein the SDAP header comprises an indication that the second service data unit meets one or more criteria associated with the higher relative priority.

7. The method according to claim 1 , further comprising changing, at a radio link control (RLC) protocol entity, the order of transmission via the one of the radio bearers of the protocol data units formed from the first and second service data units.

8. The method according to claim 1 , further comprising changing, at the PDCP entity, the order of transmission of the protocol data units formed from the first and second service data units.

9. A communications device for transmitting data via a wireless communications network, the communications device comprising:

a transceiver configured to transmit signals and to receive signals on a wireless access interface of the wireless communications network,

a processor configured to control the transceiver to transmit the signals representing the data, the processor being configured:

to receive at a Service Data Adaptation Protocol (SDAP) service access point (SAP), service data units according to one or more quality of service (QoS) flows, each of the QoS flows defining a QoS for the data received in the service data units,

to determine whether one of the service data units has a relative priority higher than a relative priority of another of the service data units,

to map the service data units received according to the one or more QoS flows on to one or more radio bearers,

to form the service data units into protocol data units for transmission via the one or more radio bearers to which the corresponding QoS flow has been mapped,

to transmit the service data units via the corresponding radio bearer according to the mapping,

wherein the service data units are associated with a first QoS flow mapped to a first dedicated radio bearer (DRB), and

wherein the first DRB is associated with a first DRB priority, and

in response to at least one of determining that the one of the service data units has a relative priority higher than a relative priority of the another of the service data units, and a congestion threshold being met, to associate the first QoS flow with a second DRB, the second DRB associated with a second DRB priority higher than the first DRB priority.

10. The communications device according to claim 9 , wherein the processor is configured to, in response to the determining:

assign a first PDCP sequence number to the one of the service data units, and

assign a second PDCP sequence number to the another of the service data units, and

wherein the first PDCP sequence number is higher than the second PDCP sequence number.

11. The communications device according to claim 10 , wherein the processor is configured to:

compress a header associated with the one of the service data units and a header associated with the another of the service data units in accordance with the assigned first and second PDCP sequence numbers, respectively.

12. The communications device according to claim 9 , wherein the processor is configured to:

start a first discard timer associated with the one of the service data units, the first discard timer expiring after a first timer duration, and

start a second discard timer associated with the another of the service data units, the second discard timer expiring after a second timer duration, and

wherein the second timer duration is longer than the first timer duration.

13. The communications device according to claim 9 , wherein the associating comprises initiating a QoS flow relocation procedure.

14. The communications device according to claim 9 , wherein the processor is configured to:

generate a SDAP protocol data unit (PDU), the SDAP PDU comprising the another of the service data units and an SDAP header, and

wherein the SDAP header comprises an indication that the another of the service data units meets one or more criteria associated with the higher relative priority.

15. Circuitry for a communications device for transmitting data via a wireless communications network, the communications device comprising:

transceiver circuitry configured to transmit signals and to receive signals on a wireless access interface of the wireless communications network,

processor circuitry configured to control the transceiver circuitry to transmit the signals representing the data, the processor circuitry being configured:

to receive at a service data adaptation Protocol (SDAP) service access point (SAP), service data units according to one or more quality of service (QOS) flows, each of the QOS flows defining a quality of service for the data received in the service data units,

to determine whether one of the service data units has a relative priority higher than a relative priority of another of the service data units,

to map the service data units received according to the one or more QoS flows on to one or more radio bearers,

to form the service data units into protocol data units for transmission via the one or more radio bearers to which the corresponding QoS flow has been mapped,

to transmit the service data units via the corresponding radio bearer according to the mapping,

wherein the service data units are associated with a first QoS flow mapped to a first dedicated radio bearer (DRB), and

wherein the first DRB is associated with a first DRB priority, and

in response to at least one of determining that the one of the service data units has a relative priority higher than a relative priority of the another of the service data units, and a congestion threshold being met, to associate the first QoS flow with a second DRB, the second DRB associated with a second DRB priority higher than the first DRB priority.

16. The circuitry according to claim 15 , wherein the processor circuitry is configured to, in response to the determining:

assign a first PDCP sequence number to the one of the service data units, and

assign a second PDCP sequence number to the another of the service data units, and

wherein the first PDCP sequence number is higher than the second PDCP sequence number.

17. The circuitry according to claim 16 , wherein the processor circuitry is configured to:

compress a header associated with the one of the service data units and a header associated with the another of the service data units in accordance with the assigned first and second PDCP sequence numbers, respectively.

18. The circuitry according to claim 15 , wherein the processor circuitry is configured to:

start a first discard timer associated with the one of the service data units, the first discard timer expiring after a first timer duration, and

start a second discard timer associated with the another of the service data units, the second discard timer expiring after a second timer duration, and

wherein the second timer duration is longer than the first timer duration.

19. The circuitry according to claim 15 , wherein the associating comprises initiating a QoS flow relocation procedure.

20. The circuitry according to claim 15 , wherein the processor circuitry is configured to:

generate a SDAP protocol data unit (PDU), the SDAP PDU comprising the another of the service data units and an SDAP header, and

wherein the SDAP header comprises an indication that the another of the service data units meets one or more criteria associated with the higher relative priority.

Priority Claims (1)
EP 18172380 · May 15, 2018 · regional
Continuity (3)
Continuation 17750491 · May 23, 2022
Continuation 17055135
Related Publication 20240187915A1 · Jun 6, 2024
References Cited (32)
US 11343701B2 · Sharma et al. · 2022 [cited by applicant]
US 11930391B2 · Sharma · 2024 [cited by examiner]
US 20180041936A1 · Kim et al. · 2018 [cited by applicant]
US 20190053326A1 · Lee et al. · 2019 [cited by applicant]
US 20190320362A1 · Liu et al. · 2019 [cited by applicant]
US 20200128452A1 · Centonza et al. · 2020 [cited by applicant]
US 20200196189A1 · Jo et al. · 2020 [cited by applicant]
US 20200236519A1 · Chun et al. · 2020 [cited by applicant]
US 20200413479A1 · Yi et al. · 2020 [cited by applicant]
US 20210058819A1 · Ozturk · 2021 [cited by examiner]
US 20210153071A1 · Kim et al. · 2021 [cited by applicant]
US 20220015070A1 · Chen · 2022 [cited by examiner]
US 20220053362A1 · Sebire · 2022 [cited by examiner]
US 20220150782A1 · Liu et al. · 2022 [cited by applicant]
US 20220201538A1 · Lee · 2022 [cited by examiner]
US 20230362946A1 · Adjakple · 2023 [cited by examiner]
CN 1938969A · 2007 [cited by applicant]
CN 101843057A · 2010 [cited by applicant]
CN 107637123A · 2018 [cited by applicant]
EP 2670189A1 · 2013 [cited by applicant]
WO 2018070689A1 · 2018 [cited by applicant]
International Search Report and Written Opinion received for PCT Application No. PCT/EP2019/061452 mailed on May 31, 2019, 12 pages. [cited by applicant]
CATT, “QoS re-mapping of QoS flow and DRB”, 3GPP TSG-RAN WG2 Meeting No. 99, R2-1707939 resubmission of R2-1704266, Berlin, Germany, Aug. 21-25, 2017, pp. 1-3. [cited by applicant]
Mediatek Inc., “SDAP header design for reflective QoS indication and QoS flow remapping”, 3GPP TSG-RAN WG2 Meeting No. 99 R2-1708260, Berlin, Germany, Aug. 21-25, 2017, 7 pages. [cited by applicant]
Huawei et al., “QoS Flow to DRB Re-Mapping”, 3GPP TSG-RAN WG2 Meeting No. 99bis R2-1710228 Revision of R2-1708938, Prague, Czech Republic, Oct. 9-13, 2017, 3 pages. [cited by applicant]
LG Electronics, “QoS flow to DRB remapping”, 3GPP TSG-RAN WG2 NR Ad Hoc No. 3, R2-1801237 Resubmission of R2-1711558, Vancouver, Canada, Jan. 22-26, 2018, 3 pages. [cited by applicant]
Huawei, “Email discussion of [101bis#76][UP] SDAP end marker solutions”, 3GPP TSG RAN WG2 Meeting No. 102, R2-1807179, Busan, Korea, May 21-25, 2018, 16 pages. [cited by applicant]
3GPP, “Service Data Adaptation Protocol (SDAP) specification”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; E-UTRA and NR, Release 15, 3GPP TS 37.324 V1.5.0, Apr. 2018, pp. 1-1… [cited by applicant]
3GPP, “Packet Data Convergence Protocol (PDCP) specification”, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR, Release 15, 3GPP TS 38.323, V15.1.0, Mar. 2018, pp. 1-25. [cited by applicant]
Ericsson, “L2 differentiated handling of critical data”, 3GPP TSG-RAN WG2 No. 101bis R2-1806186, Sanya, P.R. of China, Apr. 16-20, 2018, pp. 1-6. [cited by applicant]
Holma et al., “LTE for UMTS OFDMA and SC-FDMA Based Radio Access”, System Architecture Based on 3GPP SAE, 2009, pp. 25-27. [cited by applicant]
Huawei, HiSilicon, “QoS Flow to DRB Re-Mapping”, 3GPP tsg_ran\WG2_RL2,TSGR2_99, Aug. 12, 2017, pp. 1-6, R2-1708938. [cited by applicant]