IP Library › Granted Patent US 12,401,536
Granted Patent B2
US 12,401,536 · App. 18/347,676 · Granted Aug 26, 2025

Ethernet type packet data unit session communications

Inventors: Weihua Qiao (Herndon, VA); Esmael Hejazi Dinan (McLean, VA); Kyungmin Park (Vienna, VA); Peyman Talebi Fard (Vienna, VA)
Assignee: Comcast Cable Communications, LLC
H04L12/1407H04L12/1435H04L12/1492H04L41/0893H04L41/50H04L47/20H04L47/24H04L63/0245H04L63/0254H04L63/20H04M15/00H04M15/66H04M15/8016H04M15/8228H04W4/24H04L41/0894H04L43/028H04W76/12
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,401,536
App. No.
18/347,676
Granted
Aug 26, 2025
Kind
B2
Abstract

Systems, apparatuses, and methods are described for wireless communications. A network function device, such as a policy control function device, may send a policy and charging control rule that is based on one or more Ethernet medium access control (MAC) addresses. For example, the policy control function device may send the policy and charging control rule to a session management function device to provide a packet data unit (PDU) session for a wireless device.

Claims (113)

1. A method comprising:

receiving, by a policy control function device, at least one Ethernet medium access control (MAC) address, for a packet data unit (PDU) session, of a wireless device; and

sending, by the policy control function device, at least one policy and charging control (PCC) rule, for the PDU session, that is based on the at least one Ethernet MAC address for the wireless device.

2. The method of claim 1 , wherein the receiving the at least one Ethernet MAC address comprises receiving, by the policy control function device, at least one Ethernet packet filter set, wherein the at least one Ethernet packet filter set comprises an Ethertype and the at least one Ethernet MAC address.

3. The method of claim 1 , further comprising receiving, from the wireless device, an Ethernet packet filter set,

wherein the at least one PCC rule is based on a comparison of the at least one Ethernet MAC address with information in the Ethernet packet filter set.

4. The method of claim 1 , wherein the at least one PCC rule comprises at least one of:

a quality of service policy associated with the wireless device;

a charging policy associated with the wireless device;

traffic steering control; or

Ethernet packet filter set information.

5. The method of claim 1 , wherein the receiving the at least one Ethernet MAC address comprises receiving, from a first device associated with a data network and via a second device, the at least one Ethernet MAC address, and

wherein the second device comprises at least one of:

a network exposure function device;

an application function device;

a unified data management device; or

a second policy control function device.

6. The method of claim 1 , wherein the policy control function device is selected, by a session management function device, based on the at least one Ethernet MAC address.

7. The method of claim 1 , wherein the at least one Ethernet MAC address comprises an Ethernet source MAC address.

8. The method of claim 1 , further comprising determining, by the policy control function device based on the at least one Ethernet MAC address for the wireless device, the at least one PCC rule.

9. The method of claim 8 , wherein the determining the at least one PCC rule comprises determining the at least one PCC rule based on at least one of: Ethernet packet filter set information or subscription information.

10. The method of claim 1 , wherein the receiving the at least one Ethernet MAC address comprises receiving the at least one Ethernet MAC address from a session management function device, and

wherein the sending the at least one PCC rule comprises sending the at least one PCC rule to the session management function device.

11. A method comprising:

sending, by a session management function device to a policy control function device, at least one Ethernet medium access control (MAC) address, for a packet data unit (PDU) session, of a wireless device; and

receiving, by the session management function device, at least one policy and charging control (PCC) rule, for the PDU session, that is based on the at least one Ethernet MAC address for the wireless device.

12. The method of claim 11 , wherein the sending the at least one Ethernet MAC address comprises sending at least one Ethernet packet filter set, wherein the at least one Ethernet packet filter set comprises an Ethertype and the at least one Ethernet MAC address.

13. The method of claim 11 , wherein the at least one PCC rule comprises at least one of:

a quality of service policy associated with the wireless device;

a charging policy associated with the wireless device;

traffic steering control; or

Ethernet packet filter set information.

14. The method of claim 11 , further comprising selecting, by the session management function device based on the at least one Ethernet MAC address, the policy control function device.

15. The method of claim 11 , wherein the at least one Ethernet MAC address comprises an Ethernet source MAC address.

16. The method of claim 11 , wherein the receiving the at least one PCC rule comprises receiving the at least one PCC rule from the policy control function device.

17. A policy control function device comprising:

one or more processors; and

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

receive at least one Ethernet medium access control (MAC) address, for a packet data unit (PDU) session, of a wireless device; and

send at least one policy and charging control (PCC) rule, for the PDU session, that is based on the at least one Ethernet MAC address for the wireless device.

18. The policy control function device of claim 17 , wherein the instructions, when executed by the one or more processors, configure the policy control function device to receive the at least one Ethernet MAC address by receiving at least one Ethernet packet filter set, and wherein the at least one Ethernet packet filter set comprises an Ethertype and the at least one Ethernet MAC address.

19. The policy control function device of claim 17 , wherein the instructions, when executed by the one or more processors, further configure the policy control function device to receive, from the wireless device, an Ethernet packet filter set, and

wherein the at least one PCC rule is based on a comparison of the at least one Ethernet MAC address with information in the Ethernet packet filter set.

20. The policy control function device of claim 17 , wherein the at least one PCC rule comprises at least one of:

a quality of service policy associated with the wireless device;

a charging policy associated with the wireless device;

traffic steering control; or

Ethernet packet filter set information.

21. The policy control function device of claim 17 , wherein the instructions, when executed by the one or more processors, configure the policy control function device to receive the at least one Ethernet MAC address by receiving, from a first device associated with a data network and via a second device, the at least one Ethernet MAC address, and

wherein the second device comprises at least one of:

a network exposure function device;

an application function device;

a unified data management device; or

a second policy control function device.

22. The policy control function device of claim 17 , wherein the policy control function device is selected, by a session management function device, based on the at least one Ethernet MAC address.

23. The policy control function device of claim 17 , wherein the at least one Ethernet MAC address comprises an Ethernet source MAC address.

24. The policy control function device of claim 17 , wherein the instructions, when executed by the one or more processors, further configure the policy control function device to determine, based on the at least one Ethernet MAC address for the wireless device, the at least one PCC rule.

25. The policy control function device of claim 24 , wherein the instructions, when executed by the one or more processors, configure the policy control function device to determine the at least one PCC rule by determining the at least one PCC rule based on at least one of: Ethernet packet filter set information or subscription information.

26. The policy control function device of claim 17 , wherein the instructions, when executed by the one or more processors, configure the policy control function device to receive the at least one Ethernet MAC address by receiving the at least one Ethernet MAC address from a session management function device, and

wherein the instructions, when executed by the one or more processors, configure the policy control function device to send the at least one PCC rule by sending the at least one PCC rule to the session management function device.

27. A session management function device comprising:

one or more processors; and

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

send, to a policy control function device, at least one Ethernet medium access control (MAC) address, for a packet data unit (PDU) session, of a wireless device; and

receive at least one policy and charging control (PCC) rule, for the PDU session, that is based on the at least one Ethernet MAC address for the wireless device.

28. The session management function device of claim 27 , wherein the instructions, when executed by the one or more processors, configure the session management function device to send the at least one Ethernet MAC address by sending at least one Ethernet packet filter set, wherein the at least one Ethernet packet filter set comprises an Ethertype and the at least one Ethernet MAC address.

29. The session management function device of claim 27 , wherein the at least one PCC rule comprises at least one of:

a quality of service policy associated with the wireless device;

a charging policy associated with the wireless device;

traffic steering control; or

Ethernet packet filter set information.

30. The session management function device of claim 27 , wherein the instructions, when executed by the one or more processors, further configure the session management function device to select, based on the at least one Ethernet MAC address, the policy control function device.

31. The session management function device of claim 27 , wherein the at least one Ethernet MAC address comprises an Ethernet source MAC address.

32. The session management function device of claim 27 , wherein the instructions, when executed by the one or more processors, configure the session management function device to receive the at least one PCC rule by receiving the at least one PCC rule from the policy control function device.

33. A non-transitory computer-readable medium storing instructions that, when executed, configure a policy control function device to:

receive at least one Ethernet medium access control (MAC) address, for a packet data unit (PDU) session, of a wireless device; and

send at least one policy and charging control (PCC) rule, for the PDU session, that is based on the at least one Ethernet MAC address for the wireless device.

34. The non-transitory computer-readable medium of claim 33 , wherein the instructions, when executed, configure the policy control function device to receive the at least one Ethernet MAC address by receiving at least one Ethernet packet filter set, and wherein the at least one Ethernet packet filter set comprises an Ethertype and the at least one Ethernet MAC address.

35. The non-transitory computer-readable medium of claim 33 , wherein the instructions, when executed, further configure the policy control function device to receive, from the wireless device, an Ethernet packet filter set, and

wherein the at least one PCC rule is based on a comparison of the at least one Ethernet MAC address with information in the Ethernet packet filter set.

36. The non-transitory computer-readable medium of claim 33 , wherein the at least one PCC rule comprises at least one of:

a quality of service policy associated with the wireless device;

a charging policy associated with the wireless device;

traffic steering control; or

Ethernet packet filter set information.

37. The non-transitory computer-readable medium of claim 33 , wherein the instructions, when executed, configure the policy control function device to receive the at least one Ethernet MAC address by receiving, from a first device associated with a data network and via a second device, the at least one Ethernet MAC address, and

wherein the second device comprises at least one of:

a network exposure function device;

an application function device;

a unified data management device; or

a second policy control function device.

38. A non-transitory computer-readable medium storing instructions that, when executed, configure a session management function device to:

send, to a policy control function device, at least one Ethernet medium access control (MAC) address, for a packet data unit (PDU) session, of a wireless device; and

receive at least one policy and charging control (PCC) rule, for the PDU session, that is based on the at least one Ethernet MAC address for the wireless device.

39. The non-transitory computer-readable medium of claim 38 , wherein the instructions, when executed, configure the session management function device to send the at least one Ethernet MAC address by sending at least one Ethernet packet filter set, wherein the at least one Ethernet packet filter set comprises an Ethertype and the at least one Ethernet MAC address.

40. The non-transitory computer-readable medium of claim 38 , wherein the at least one PCC rule comprises at least one of:

a quality of service policy associated with the wireless device;

a charging policy associated with the wireless device;

traffic steering control; or

Ethernet packet filter set information.

41. A system comprising:

a policy control function device; and

a session management function device configured to:

send, to the policy control function device, at least one Ethernet medium access control (MAC) address, for a packet data unit (PDU) session, of a wireless device, wherein the policy control function device is configured to:

send, to the session management function device, at least one policy and charging control (PCC) rule, for the PDU session, that is based on the at least one Ethernet MAC address for the wireless device.

42. The system of claim 41 , wherein the session management function device is configured to send the at least one Ethernet MAC address by sending at least one Ethernet packet filter set, and wherein the at least one Ethernet packet filter set comprises an Ethertype and the at least one Ethernet MAC address.

43. The system of claim 41 , wherein the policy control function device is further configured to receive, from the wireless device, an Ethernet packet filter set, and

wherein the at least one PCC rule is based on a comparison of the at least one Ethernet MAC address with information in the Ethernet packet filter set.

44. The system of claim 41 , wherein the at least one PCC rule comprises at least one of:

a quality of service policy associated with the wireless device;

a charging policy associated with the wireless device;

traffic steering control; or

Ethernet packet filter set information.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 8, 2023
From: QIAO, WEIHUA; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN; TALEBI FARD, PEYMAN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 064839/0740 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 8, 2023
From: QIAO, WEIHUA; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN; TALEBI FARD, PEYMAN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 064839/0748 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 8, 2023
From: QIAO, WEIHUA; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN; TALEBI FARD, PEYMAN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 064839/0752 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 8, 2023
From: QIAO, WEIHUA; DINAN, ESMAEL HEJAZI; PARK, KYUNGMIN; TALEBI FARD, PEYMAN
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 064839/0767 →
Continuity (6)
Continuation 16951875 · Nov 18, 2020
Continuation 16155378 · Oct 9, 2018
Provisional Application 62569935 · Oct 9, 2017
Provisional Application 62569927 · Oct 9, 2017
Provisional Application 62569910 · Oct 9, 2017
Related Publication 20240039744A1 · Feb 1, 2024
References Cited (113)
US 10251147B2 · Park et al. · 2019 [cited by applicant]
US 10264506B2 · Faccin et al. · 2019 [cited by applicant]
US 10951427B2 · Qiao · 2021 [cited by examiner]
US 12095576B2 · Qiao · 2024 [cited by examiner]
US 20130139221A1 · Gundavelli · 2013 [cited by examiner]
US 20140204927A1 · Horn et al. · 2014 [cited by applicant]
US 20140219267A1 · Eyuboglu et al. · 2014 [cited by applicant]
US 20150063331A1 · Scahill · 2015 [cited by examiner]
US 20160345170A1 · Mann · 2016 [cited by applicant]
US 20160345178A1 · Bronowich · 2016 [cited by applicant]
US 20170289019A1 · Faccin et al. · 2017 [cited by applicant]
US 20170303189A1 · Hampel et al. · 2017 [cited by applicant]
US 20180192390A1 · Li 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 20190116520A1 · Chaponniere et al. · 2019 [cited by applicant]
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 et al. · 2019 [cited by applicant]
US 20190306758A1 · Ma et al. · 2019 [cited by applicant]
US 20190313473A1 · Kim et al. · 2019 [cited by applicant]
US 20190335366A1 · Jin 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 20190387428A1 · Ahmad et al. · 2019 [cited by applicant]
US 20200084657A1 · Lee et al. · 2020 [cited by applicant]
US 20210075865A1 · Zhu et al. · 2021 [cited by applicant]
CN 101414940B · 2011 [cited by applicant]
EP 3094155A1 · 2016 [cited by applicant]
EP 3337284A1 · 2018 [cited by applicant]
EP 3425993A1 · 2019 [cited by applicant]
WO 2009052749A1 · 2009 [cited by applicant]
WO 2014011008A1 · 2014 [cited by applicant]
WO 2014094287A1 · 2014 [cited by applicant]
WO WO2016091298A1 · 2016 [cited by examiner]
WO 2017030420A1 · 2017 [cited by applicant]
WO 2017171514A1 · 2017 [cited by applicant]
WO 2018006017A1 · 2018 [cited by applicant]
WO 2018130968A1 · 2018 [cited by applicant]
R2-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]
3GPP TS 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]
S2-183494 3GPP TSG RAN WG2 Meeting #127, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, China Mobile, Title: Controlled Support of (AF) Session Binding for Ethernet PDU Session Type. [cited by applicant]
S2-173117 3GPP TSG RAN WG2 Meeting #121, Hangzhou, China, May 15-19, 2017, Source: Qualcomm Incorporated, Title: Options on Packet Filters Extension for PDU Sessions of Type Ethernet and Unstructured in 5GS. [cited by applicant]
S2-174838 3GPP SA WG2 Meeting #122, Cabo, Mexico, Jun. 26-30, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Update on policy control for QoS control functionalities. [cited by applicant]
S2-174210 3GPP SA WG2 Meeting #122, Cabo, Mexico, Jun. 26-30, 2017, Source: Ericsson, Title: 5G System details for PCC. [cited by applicant]
Jun. 9, 2021—European Search Report—EP 21157697.0. [cited by applicant]
Jun. 24, 2022—European Office Action—EP App. No. 21157697.0. [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, May23-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]
Feb. 22, 2024—European Office Action—EP App. No. 21157697.0. [cited by applicant]