IP Library › Granted Patent US 12,526,347
Granted Patent B2
US 12,526,347 · App. 18/490,432 · Granted Jan 13, 2026

Wireless device capability information

Inventors: Kyungmin Park (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Weihua Qiao (Herndon, VA); Peyman Talebi Fard (Vienna, VA); Alireza Babaei (Fairfax, VA); Hyoungsuk Jeon (Centreville, VA); Hua Zhou (Vienna, VA)
Assignee: Comcast Cable Communications, LLC
H04L69/04H04L69/22H04W8/08H04W36/0005H04W36/0033H04W36/0088H04W40/24H04W72/0446H04W72/0453H04W76/15H04W76/27H04L5/001H04W74/0833H04W80/02H04W80/08
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,526,347
App. No.
18/490,432
Filed
Oct 19, 2023
Granted
Jan 13, 2026
Kind
B2
Art Unit
2465
USPC
370/331
Abstract

Systems, apparatuses, and methods are described for wireless communications. A base station and wireless device may communicate capability information associated with a wireless device. The capability information may include information indicating support for an Ethernet type packet data unit session or header parameter compression. An Ethernet type packet data unit session may be instantiated based on the capability information.

Claims (113)

1 . A method comprising:

sending, by a wireless device to a core network, a wireless device capability parameter indicating whether the wireless device supports an Ethernet session type between the wireless device and the core network; and

sending, by the wireless device, a message associated with a session of the Ethernet session type.

2 . The method of claim 1 , wherein the wireless device capability parameter indicates at least one of:

a transmission bit rate,

multiple Ethernet addresses for the wireless device, or

an Ethernet standard version.

3 . The method of claim 1 , wherein the sending the wireless device capability parameter comprises sending, to the core network via a base station, at least one non-access stratum parameter comprising:

the wireless device capability parameter, and

a packet data unit (PDU) session type parameter indicating a type of a requested PDU session.

4 . The method of claim 1 , wherein the core network comprises an access and mobility function (AMF) device and a user plane function (UPF) device, and

wherein the sending the wireless device capability parameter comprises sending, by the wireless device to the AMF device via a base station, the wireless device capability parameter indicating whether the wireless device supports the Ethernet session type between the wireless device and the UPF device.

5 . The method of claim 1 , wherein the Ethernet session type comprises an Ethernet packet data unit (PDU) session type,

wherein the session comprises a PDU session of the Ethernet PDU session type, and

wherein the message comprises at least one Ethernet frame message.

6 . The method of claim 1 , further comprising:

receiving, by the wireless device, a second message comprising one or more configuration parameters for the session.

7 . A method comprising:

receiving, by a base station, a wireless device capability parameter indicating whether a wireless device supports an Ethernet session type between the wireless device and a core network; and

receiving, by the base station from the wireless device, a message associated with a session of the Ethernet session type.

8 . The method of claim 7 , wherein the wireless device capability parameter comprises at least one indication field indicating at least one of:

a transmission bit rate,

multiple Ethernet addresses for the wireless device, or

an Ethernet standard version.

9 . The method of claim 7 , wherein the receiving the wireless device capability parameter comprises receiving, by the base station from the wireless device, at least one non-access stratum parameter comprising:

the wireless device capability parameter, and

a packet data unit (PDU) session type parameter indicating a type of a requested PDU session.

10 . The method of claim 7 , wherein the core network comprises an access and mobility function (AMF) device and a user plane function (UPF) device,

wherein the receiving the wireless device capability parameter comprises receiving, by the base station from the wireless device, the wireless device capability parameter indicating whether the wireless device supports the Ethernet session type between the wireless device and the UPF device, and

wherein the method further comprises sending, by the base station to the AMF device, the wireless device capability parameter.

11 . The method of claim 7 , wherein the Ethernet session type comprises an Ethernet packet data unit (PDU) session type,

wherein the session comprises a PDU session of the Ethernet PDU session type, and

wherein the message comprises at least one Ethernet frame message.

12 . The method of claim 7 , further comprising:

sending, by the base station to the wireless device, a second message comprising one or more configuration parameters for the session.

13 . A wireless device comprising:

one or more processors;

memory storing instructions that, when executed by the one or more processors, configure the wireless device to:

send, to a core network, a wireless device capability parameter indicating whether the wireless device supports an Ethernet session type between the wireless device and the core network; and

send a message associated with a session of the Ethernet session type.

14 . The wireless device of claim 13 , wherein the wireless device capability parameter indicates at least one of:

a transmission bit rate,

multiple Ethernet addresses for the wireless device, or

an Ethernet standard version.

15 . The wireless device of claim 13 , wherein the instructions, when executed by the one or more processors, configure the wireless device to send the wireless device capability parameter by sending, to the core network via a base station, at least one non-access stratum parameter comprising:

the wireless device capability parameter, and

a packet data unit (PDU) session type parameter indicating a type of a requested PDU session.

16 . The wireless device of claim 13 , wherein the core network comprises an access and mobility function (AMF) device and a user plane function (UPF) device, and

wherein the instructions, when executed by the one or more processors, configure the wireless device to send the wireless device capability parameter by sending, to the AMF device via a base station, the wireless device capability parameter indicating whether the wireless device supports the Ethernet session type between the wireless device and the UPF device.

17 . The wireless device of claim 13 , wherein the Ethernet session type comprises an Ethernet packet data unit (PDU) session type,

wherein the session comprises a PDU session of the Ethernet PDU session type, and

wherein the message comprises at least one Ethernet frame message.

18 . The wireless device of claim 13 , wherein the instructions, when executed by the one or more processors, further configure the wireless device to:

receive a second message comprising one or more configuration parameters for the session.

19 . A base station comprising:

one or more processors;

memory storing instructions that, when executed by the one or more processors, configure the base station to:

receive a wireless device capability parameter indicating whether a wireless device supports an Ethernet session type between the wireless device and a core network; and

receive, from the wireless device, a message associated with a session of the Ethernet session type.

20 . The base station of claim 19 , wherein the wireless device capability parameter comprises at least one indication field indicating at least one of:

a transmission bit rate,

multiple Ethernet addresses for the wireless device, or

an Ethernet standard version.

21 . The base station of claim 19 , wherein the instructions, when executed by the one or more processors, configure the base station to receive the wireless device capability parameter by receiving, from the wireless device, at least one non-access stratum parameter comprising:

the wireless device capability parameter, and

a packet data unit (PDU) session type parameter indicating a type of a requested PDU session.

22 . The base station of claim 19 , wherein the core network comprises an access and mobility function (AMF) device and a user plane function (UPF) device,

wherein the instructions, when executed by the one or more processors, configure the base station to receive the wireless device capability parameter by receiving, from the wireless device, the wireless device capability parameter indicating whether the wireless device supports the Ethernet session type between the wireless device and the UPF device, and

wherein the instructions, when executed by the one or more processors, further configure the base station to send, to the AMF device, the wireless device capability parameter.

23 . The base station of claim 19 , wherein the Ethernet session type comprises an Ethernet packet data unit (PDU) session type,

wherein the session comprises a PDU session of the Ethernet PDU session type, and

wherein the message comprises at least one Ethernet frame message.

24 . The base station of claim 19 , wherein the instructions, when executed by the one or more processors, further configure the base station to:

send, to the wireless device, a second message comprising one or more configuration parameters for the session.

25 . A non-transitory computer-readable medium storing instructions that, when executed, cause:

sending, by a wireless device to a core network, a wireless device capability parameter indicating whether the wireless device supports an Ethernet session type between the wireless device and the core network; and

sending, by the wireless device, a message associated with a session of the Ethernet session type.

26 . The non-transitory computer-readable medium of claim 25 , wherein the wireless device capability parameter indicates at least one of:

a transmission bit rate,

multiple Ethernet addresses for the wireless device, or

an Ethernet standard version.

27 . The non-transitory computer-readable medium of claim 25 , wherein the instructions, when executed, cause the sending the wireless device capability parameter by sending, to the core network via a base station, at least one non-access stratum parameter comprising:

the wireless device capability parameter, and

a packet data unit (PDU) session type parameter indicating a type of a requested PDU session.

28 . The non-transitory computer-readable medium of claim 25 , wherein the core network comprises an access and mobility function (AMF) device and a user plane function (UPF) device, and

wherein the instructions, when executed, cause the sending the wireless device capability parameter by sending, by the wireless device to the AMF device via a base station, the wireless device capability parameter indicating whether the wireless device supports the Ethernet session type between the wireless device and the UPF device.

29 . A non-transitory computer-readable medium storing instructions that, when executed, cause:

receiving, by a base station, a wireless device capability parameter indicating whether a wireless device supports an Ethernet session type between the wireless device and a core network; and

receiving, by the base station from the wireless device, a message associated with a session of the Ethernet session type.

30 . The non-transitory computer-readable medium of claim 29 , wherein the wireless device capability parameter comprises at least one indication field indicating at least one of:

a transmission bit rate,

multiple Ethernet addresses for the wireless device, or

an Ethernet standard version.

31 . The non-transitory computer-readable medium of claim 29 , wherein the instructions, when executed, cause the receiving the wireless device capability parameter by receiving, by the base station from the wireless device, at least one non-access stratum parameter comprising:

the wireless device capability parameter, and

a packet data unit (PDU) session type parameter indicating a type of a requested PDU session.

32 . The non-transitory computer-readable medium of claim 29 , wherein the core network comprises an access and mobility function (AMF) device and a user plane function (UPF) device,

wherein the instructions, when executed, cause the receiving the wireless device capability parameter by receiving, by the base station from the wireless device, the wireless device capability parameter indicating whether the wireless device supports the Ethernet session type between the wireless device and the UPF device, and

wherein the instructions, when executed, further cause sending, by the base station to the AMF device, the wireless device capability parameter.

33 . A system comprising:

a core network; and

a wireless device configured to:

send, to the core network, a wireless device capability parameter indicating whether the wireless device supports an Ethernet session type between the wireless device and the core network; and

send a message associated with a session of the Ethernet session type.

34 . The system of claim 33 , wherein the wireless device capability parameter indicates at least one of:

a transmission bit rate,

multiple Ethernet addresses for the wireless device, or

an Ethernet standard version.

35 . The system of claim 33 , wherein the wireless device is configured to send the wireless device capability parameter by sending, to the core network via a base station, at least one non-access stratum parameter comprising:

the wireless device capability parameter, and

a packet data unit (PDU) session type parameter indicating a type of a requested PDU session.

36 . The system of claim 33 , wherein the core network comprises an access and mobility function (AMF) device and a user plane function (UPF) device, and

wherein the wireless device is configured to send the wireless device capability parameter by sending, by the wireless device to the AMF device via a base station, the wireless device capability parameter indicating whether the wireless device supports the Ethernet session type between the wireless device and the UPF device.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2024
From: PARK, KYUNGMIN; DINAN, ESMAEL HEJAZI; QIAO, WEIHUA; TALEBI FARD, PEYMAN; BABAEI, ALIREZA; JEON, HYOUNGSUK; ZHOU, HUA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068709/0724 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2024
From: PARK, KYUNGMIN; DINAN, ESMAEL HEJAZI; QIAO, WEIHUA; TALEBI FARD, PEYMAN; BABAEI, ALIREZA; JEON, HYOUNGSUK; ZHOU, HUA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068709/0684 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2024
From: PARK, KYUNGMIN; DINAN, ESMAEL HEJAZI; QIAO, WEIHUA; TALEBI FARD, PEYMAN; BABAEI, ALIREZA; JEON, HYOUNGSUK; ZHOU, HUA
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068709/0788 →
Continuity (6)
Continuation 18150031 · Jan 4, 2023
Continuation 17107132 · Nov 30, 2020
Continuation 16165613 · Oct 19, 2018
Provisional Application 62574954 · Oct 20, 2017
Provisional Application 62575127 · Oct 20, 2017
Related Publication 20240146827A1 · May 2, 2024
References Cited (116)
US 10251147B2 · Park et al. · 2019 [cited by applicant]
US 10264506B2 · Faccin et al. · 2019 [cited by applicant]
US 10271333B2 · Cui et al. · 2019 [cited by applicant]
US 10356678B2 · Guo et al. · 2019 [cited by applicant]
US 10785820B2 · Salkintzis · 2020 [cited by examiner]
US 10812629B2 · Park et al. · 2020 [cited by applicant]
US 10855814B2 · Park · 2020 [cited by examiner]
US 11006316B2 · Qiao · 2021 [cited by examiner]
US 11153813B2 · Qiao · 2021 [cited by examiner]
US 11375576B2 · Backman · 2022 [cited by examiner]
US 11576079B2 · Qiao et al. · 2023 [cited by applicant]
US 11582330B2 · Park · 2023 [cited by examiner]
US 11659621B2 · Backman · 2023 [cited by examiner]
US 11849009B2 · Park · 2023 [cited by examiner]
US 20140204927A1 · Horn et al. · 2014 [cited by applicant]
US 20140219267A1 · Eyuboglu et al. · 2014 [cited by applicant]
US 20140355516A1 · Baudoin et al. · 2014 [cited by applicant]
US 20170289019A1 · Faccin et al. · 2017 [cited by applicant]
US 20170318510A1 · Guo et al. · 2017 [cited by applicant]
US 20180115928A1 · Kim et al. · 2018 [cited by applicant]
US 20180262905A1 · Dhanapal et al. · 2018 [cited by applicant]
US 20180270782A1 · Park et al. · 2018 [cited by applicant]
US 20180270888A1 · Faccin · 2018 [cited by applicant]
US 20180332523A1 · Faccin et al. · 2018 [cited by applicant]
US 20190116517A1 · Liu · 2019 [cited by applicant]
US 20190116520A1 · Chaponniere et al. · 2019 [cited by applicant]
US 20190116521A1 · Qiao · 2019 [cited by examiner]
US 20190150219A1 · Wang et al. · 2019 [cited by applicant]
US 20190166647A1 · Velev et al. · 2019 [cited by applicant]
US 20190182895A1 · Di Girolamo et al. · 2019 [cited by applicant]
US 20190200264A1 · Kim et al. · 2019 [cited by applicant]
US 20190261159A1 · Wang et al. · 2019 [cited by applicant]
US 20190274178A1 · Salkintzis · 2019 [cited by examiner]
US 20190289666A1 · Backman · 2019 [cited by examiner]
US 20190313473A1 · Kim et al. · 2019 [cited by applicant]
US 20190335366A1 · Jin et al. · 2019 [cited by applicant]
US 20190342927A1 · Ohseki et al. · 2019 [cited by applicant]
US 20190364496A1 · Jin · 2019 [cited by applicant]
US 20190364541A1 · Ryu · 2019 [cited by applicant]
US 20190380104A1 · Vrzic et al. · 2019 [cited by applicant]
US 20200029380A1 · Kawasaki et al. · 2020 [cited by applicant]
US 20200037386A1 · Park · 2020 [cited by examiner]
US 20200170067A1 · Kawasaki et al. · 2020 [cited by applicant]
EP 3094155A1 · 2016 [cited by applicant]
EP 3337284A1 · 2018 [cited by applicant]
EP 3425993A1 · 2019 [cited by applicant]
WO 2014011008A1 · 2014 [cited by applicant]
WO 2014094287A1 · 2014 [cited by applicant]
WO 2017030420A1 · 2017 [cited by applicant]
WO 2017171514A1 · 2017 [cited by applicant]
WO 2018006017A1 · 2018 [cited by applicant]
WO 2018130968A1 · 2018 [cited by applicant]
Mar. 21, 2019—EP Extended Search Report—EP 18201708.7. [cited by applicant]
C1-174177 3GPP TSG-CT WG1 Meeting #106, Kochi, India, Oct. 23-27, 2017, Source: LG Electronics, Ericsson, Title: Corrections on PDU session type and PDU type. [cited by applicant]
R3-161353 3GPP TSG RAN WG3 Meeting #92, Nanjing, China, May 23-27, 2016, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Proposal for RAN-CN Functional Split. [cited by applicant]
S2-177144 3GPP SA WG2 Meeting #123, Ljubljana, Slovenia, Oct. 23-27, 2017, Source: Huawei, HiSilicon, Title: Clarification on Ethernet PDU session. [cited by applicant]
C1-173155 3GPP TSG-CT WG1 Meeting #105, Krakow, Poland, Aug. 21-25, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Pseudo-CR on support of 5GSM PDU session types. [cited by applicant]
3GPP TS 36.323 V14.3.1 (Jun. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Conve… [cited by applicant]
3GPP TS 36.331 V14.3.0 (Jun. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Co… [cited by applicant]
3GPP TS 38.300 V1.0.1 (Oct. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15). [cited by applicant]
3GPP TS 38.323 V0.3.0 (Aug. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 15). [cited by applicant]
Cisco, Next-Generation Enterprise WAN: Cisco ISRs with 4G LTE Deployment Guide, May 2014. [cited by applicant]
Effnet Platform, Effnet EthHC™, 2017. [cited by applicant]
Wikipedia, “Ethernet frame”, last edited Sep. 24, 2017. [cited by applicant]
Wikipedia, “EtherType”, last edited Aug. 10, 2017. [cited by applicant]
Wikipedia, “IEEE 802.1Q”, last edited Aug. 7, 2017. [cited by applicant]
S2-177974 3GPP SA WG2 Meeting #123, Ljubljana, Slovenia, Oct. 23-27, 2017, Source: Huawei, HiSilicon, Title: Classification on Ethernet PDU session. [cited by applicant]
S2-178029 3GPP SA WG2 Meeting #123, Ljubljana, Slovenia, Oct. 23-27, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Corrections and Improvements for Ethernet PDU Session Type. [cited by applicant]
3GPP TS 36.211 V14.4.0 (Sep. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels… [cited by applicant]
3GPP TS 36.212 V14.4.0 (Sep. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and … [cited by applicant]
3GPP TS 36.300 V14.4.0 (Sep. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Univer… [cited by applicant]
3GPP TS 36.321 V14.4.0 (Sep. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Con… [cited by applicant]
3GPP TS 36.331 V14.4.0 (Sep. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Co… [cited by applicant]
3GPP TS 36.213 V14.4.0 (Sep. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer Pr… [cited by applicant]
S2-184514 3GPP TSG-SA WG2 Meeting #127, Sanya, China, Apr. 16-20, 2018, Source: Qualcomm Incorporated, Spreadtrum Communications, Ericsson, Title: Consolidation of UE Network Capabilities. [cited by applicant]
S2-183522 3GPP TSG-SA WG2 Meeting #127, Sanya, China, Apr. 16-20, 2018, Source: Qualcomm Incorporated, Title: Consolidation of UE Network Capabilities. [cited by applicant]
R1-1719301 3GPP TSG RAN WG1 Meeting #91, Reno, USA, Source: MCC Support, Title: Final Report of 3GPP TSG RAN WG1 #90bis v1.0.0 (Prague, Czech Republic, Oct. 9-13, 2017). [cited by applicant]
R1-1717057 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon, Title: On initial active bandwidth part. [cited by applicant]
R1-1717077 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon, Title: Remaining issues on bandwidth part. [cited by applicant]
R1-1717400 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Intel Corporation, Title: Remaining details for bandwidth parts. [cited by applicant]
R1-1717504 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: vivo, Title: Remaining details for bandwidth part operation. [cited by applicant]
R1-1717675 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: On Bandwidth Part Operation. [cited by applicant]
R1-1717839 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: CATT, Title: Remaining aspects of BWP operation. [cited by applicant]
R1-1717905 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon, Title: Bandwidth part activation and adaptation. [cited by applicant]
R1-1717972 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: LG Electronics, Title: Remaining issues on bandwidth parts. [cited by applicant]
R1-1718050 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: OPPO, Title: Remaining issues on bandwidth part configuration and activation. [cited by applicant]
R1-1718223 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: NTT DOCOMO, Inc., Title: Remaining issues on bandwidth parts for NR. [cited by applicant]
R1-1718327 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: MediaTek Inc., Title: Remaining Details on Bandwidth Part Operation in NR. [cited by applicant]
R1-1718365 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: InterDigital, Inc., Title: Remaining details of BWP. [cited by applicant]
R1-1718404 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: AT&T, Title: Remaining details for bandwidth parts. [cited by applicant]
R1-1718523 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Ericsson, Title: On bandwidth parties. [cited by applicant]
R1-1718580 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Qualcomm Incorporated, Title: Open Issues on BWP. [cited by applicant]
R1-1718607 3GPP TSG RAN WG1 Meeting #90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Nokia, Nokia Shanghai Bell, Title: On remaining aspects of BWPs. [cited by applicant]
R1-1718901 3GPP TSG RAN WG1 Meeting 90bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: MediaTek Inc., Title: Summary of Bandwidth Part Operation. [cited by applicant]
R2-1710091 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: Random Access in RRC Connected: Bandwidth Part Aspects. [cited by applicant]
R2-1710125 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: OPPO, Title: Impact of BWP on CA. [cited by applicant]
R2-1710126 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: OPPO, Title: Timer based BWP switching. [cited by applicant]
R2-1710217 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon, Title: User plane impacts for Bandwidth Parts. [cited by applicant]
R2-1710274 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: CATT, Title: Modeling Bandwidth Parts in MAC. [cited by applicant]
R2-1710275 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: CATT, Title: BWP model. [cited by applicant]
R2-1710457 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Huawei, HiSilicon, Title: Control plane impacts for Bandwidth Parts. [cited by applicant]
R2-1710592 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Intel Corporation, Title: Overall impact in RAN2 for BWP. [cited by applicant]
R1-1710864 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Mediatek Inc., Title: Basic Framework for Bandwidth Part Operation. [cited by applicant]
R2-1710965 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: vivo, Title: Discussion on bandwidth part operation. [cited by applicant]
R2-1711065 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Cell and BWP relation. [cited by applicant]
R2-1711187 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: Framework to support bandwidth parts in NR. [cited by applicant]
R2-1711188 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: Signaling to support bandwidth part. [cited by applicant]
R2-1711189 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: Activation/deactivation of bandwidth parts in NR. [cited by applicant]
R2-1711388 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: LG Electronics Inc., Title: RRC Procedures for BWP Configuration. [cited by applicant]
R2-1711595 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: The impact of bandwidth part on RAN2: Overview and Issues. [cited by applicant]
R2-1711607 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: Samsung, Title: Scenarios of Measurement Gap Considering Bandwidth Part. [cited by applicant]
R2-1711640 3GPP TSG RAN WG2 Meeting #99bis, Prague, Czech Republic, Oct. 9-13, 2017, Source: ZTE Corporation, Sane Chips, Title: Initial discussion on the impacts of BWP on RAN2. [cited by applicant]
R2-1712101 3GPP TSG RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ETSI MCC, Title: Report of 3GPP TSG Ran2 #99bis Meeting in Prague. [cited by applicant]
3GPPS 23.501 V15.2.0 (Jun. 2018); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15). [cited by applicant]
Jun. 17, 2020—European Office Action—EP 18201708.7. [cited by applicant]
Jun. 9, 2022—EP Search Report—EP App. No. 22158164.8. [cited by applicant]