IP Library › Granted Patent US 12,316,465
Granted Patent B2
US 12,316,465 · App. 18/440,302 · Granted May 27, 2025

Packet duplication control

Inventors: Kyungmin Park (Vienna, VA); Esmael Hejazi Dinan (McLean, VA); Hyoungsuk Jeon (Centreville, VA); Hua Zhou (Vienna, VA); Alireza Babaei (Fairfax, VA); Ali Cagatay Cirik (Chantilly, VA)
Assignee: Comcast Cable Communications, LLC
H04L1/189H04L5/0098H04W24/08H04W76/11H04W76/12H04W76/27H04W80/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,316,465
App. No.
18/440,302
Granted
May 27, 2025
Kind
B2
Abstract

Wireless communications are described. A central unit control plane (CU-CP) node of a base station may activate and/or deactivate packet duplication based on status information from self-monitoring, from a distributed unit (DU), from a wireless device, and/or from a central unit user plane (CU-UP) node. The CU-UP node and/or the DU may activate and/or deactivate packet duplication based on status information from self-monitoring, from each other, from the wireless device, and/or from the CU-CP node. The CU-UP node and/or the DU, after activating and/or deactivating packet duplication, may report the activation and/or deactivation to the CU-CP node.

Claims (114)

1. A method comprising:

sending, by a central unit control plane (CU-CP) node to a central unit user plane (CU-UP) node, a message comprising:

a first field indicating configuration of packet duplication for a bearer associated with a wireless device, and

a second field indicating a packet duplication state, wherein the packet duplication state is one of activated or deactivated; and

receiving, by the CU-CP node from the CU-UP node and based on the message, a response.

2. The method of claim 1 , wherein the message further comprises a bearer configuration request for the wireless device.

3. The method of claim 1 , wherein the message further comprises logical channel information for the bearer, the logical channel information comprising:

a first logical channel identifier of a first logical channel for at least one packet, and

a second logical channel identifier of a second logical channel for at least one duplicated version of the at least one packet.

4. The method of claim 1 , further comprising:

after sending the message, receiving, by the CU-CP node from the CU-UP node, at least one second message comprising uplink tunnel information for the bearer, the uplink tunnel information comprising:

a first uplink tunnel endpoint identifier for a first tunnel for at least one uplink packet, and

a second uplink tunnel endpoint identifier for a second tunnel for at least one duplicated uplink packet.

5. The method of claim 4 , further comprising:

after receiving the at least one second message, sending, to the CU-UP node, a configuration update message indicating downlink tunnel information for the bearer.

6. The method of claim 1 , further comprising:

sending, to the CU-UP node, status information comprising an indication of at least one of:

a hardware load,

a load of an N2 interface between the CU-UP node and a core network entity,

a load of an F1 interface between the CU-UP node and at least one distributed unit (DU) node,

status information associated with the CU-CP node,

status information associated with the at least one DU node,

a composite available capacity group, or

a network slice overload.

7. The method of claim 1 , wherein the response comprises an indication of an activation or a deactivation of the packet duplication.

8. The method of claim 1 , wherein the configuration of the packet duplication comprises configuration of packet data convergence protocol (PDCP) packet duplication.

9. The method of claim 1 , wherein the packet duplication state is activated.

10. A central unit control plane (CU-CP) node comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, configure the CU-CP node to:

send, to a central unit user plane (CU-UP) node, a message comprising:

a first field indicating configuration of packet duplication for a bearer associated with a wireless device, and

a second field indicating a packet duplication state, wherein the packet duplication state is one of activated or deactivated; and

receive, from the CU-UP node and based on the message, a response.

11. The CU-CP node of claim 10 , wherein the message further comprises a bearer configuration request for the wireless device.

12. The CU-CP node of claim 10 , wherein the message further comprises logical channel information for the bearer, the logical channel information comprising:

a first logical channel identifier of a first logical channel for at least one packet, and

a second logical channel identifier of a second logical channel for at least one duplicated version of the at least one packet.

13. The CU-CP node of claim 10 , wherein the instructions, when executed by the one or more processors, further configure the CU-CP node to:

after sending the message, receive, from the CU-UP node, at least one second message comprising uplink tunnel information for the bearer, the uplink tunnel information comprising:

a first uplink tunnel endpoint identifier for a first tunnel for at least one uplink packet, and

a second uplink tunnel endpoint identifier for a second tunnel for at least one duplicated uplink packet.

14. The CU-CP node of claim 13 , wherein the instructions, when executed by the one or more processors, further configure the CU-CP node to:

after receiving the at least one second message, send, to the CU-UP node, a configuration update message indicating downlink tunnel information for the bearer.

15. The CU-CP node of claim 10 , wherein the instructions, when executed by the one or more processors, further configure the CU-CP node to:

send, to the CU-UP node, status information comprising an indication of at least one of:

a hardware load,

a load of an N2 interface between the CU-UP node and a core network entity,

a load of an F1 interface between the CU-UP node and at least one distributed unit (DU) node,

status information associated with the CU-CP node,

status information associated with the at least one DU node,

a composite available capacity group, or

a network slice overload.

16. The CU-CP node of claim 10 , wherein the response comprises an indication of an activation or a deactivation of the packet duplication.

17. The CU-CP node of claim 10 , wherein the configuration of the packet duplication comprises configuration of packet data convergence protocol (PDCP) packet duplication.

18. The CU-CP node of claim 10 , wherein the packet duplication state is activated.

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

sending, by a central unit control plane (CU-CP) node to a central unit user plane (CU-UP) node, a message comprising:

a first field indicating configuration of packet duplication for a bearer associated with a wireless device, and

a second field indicating a packet duplication state, wherein the packet duplication state is one of activated or deactivated; and

receiving, by the CU-CP node from the CU-UP node and based on the message, a response.

20. The non-transitory computer-readable medium of claim 19 , wherein the message further comprises a bearer configuration request for the wireless device.

21. The non-transitory computer-readable medium of claim 19 , wherein the message further comprises logical channel information for the bearer, the logical channel information comprising:

a first logical channel identifier of a first logical channel for at least one packet, and

a second logical channel identifier of a second logical channel for at least one duplicated version of the at least one packet.

22. The non-transitory computer-readable medium of claim 19 , wherein the instructions, when executed, further cause:

after sending the message, receiving, by the CU-CP node from the CU-UP node, at least one second message comprising uplink tunnel information for the bearer, the uplink tunnel information comprising:

a first uplink tunnel endpoint identifier for a first tunnel for at least one uplink packet, and

a second uplink tunnel endpoint identifier for a second tunnel for at least one duplicated uplink packet.

23. The non-transitory computer-readable medium of claim 22 , wherein the instructions, when executed, further cause:

after receiving the at least one second message, sending, to the CU-UP node, a configuration update message indicating downlink tunnel information for the bearer.

24. The non-transitory computer-readable medium of claim 19 , wherein the instructions, when executed, further cause:

sending, to the CU-UP node, status information comprising an indication of at least one of:

a hardware load,

a load of an N2 interface between the CU-UP node and a core network entity,

a load of an F1 interface between the CU-UP node and at least one distributed unit (DU) node,

status information associated with the CU-CP node,

status information associated with the at least one DU node,

a composite available capacity group, or

a network slice overload.

25. The non-transitory computer-readable medium of claim 19 , wherein the response comprises an indication of an activation or a deactivation of the packet duplication.

26. The non-transitory computer-readable medium of claim 19 , wherein the configuration of the packet duplication comprises configuration of packet data convergence protocol (PDCP) packet duplication.

27. The non-transitory computer-readable medium of claim 19 , wherein the packet duplication state is activated.

28. A system comprising:

a central unit control plane (CU-CP) node; and

a central unit user plane (CU-UP) node,

wherein the CU-CP node is configured to:

send, to the CU-UP node, a message comprising:

a first field indicating configuration of packet duplication for a bearer associated with a wireless device, and

a second field indicating a packet duplication state, wherein the packet duplication state is one of activated or deactivated, and

wherein the CU-UP node is configured to:

send, to the CU-CP node and based on the message, a response.

29. The system of claim 28 , wherein the message further comprises a bearer configuration request for the wireless device.

30. The system of claim 28 , wherein the message further comprises logical channel information for the bearer, the logical channel information comprising:

a first logical channel identifier of a first logical channel for at least one packet, and

a second logical channel identifier of a second logical channel for at least one duplicated version of the at least one packet.

31. The system of claim 28 , wherein the CU-UP node is further configured to:

after the message is sent, send, to the CU-CP node, at least one second message comprising uplink tunnel information for the bearer, the uplink tunnel information comprising:

a first uplink tunnel endpoint identifier for a first tunnel for at least one uplink packet, and

a second uplink tunnel endpoint identifier for a second tunnel for at least one duplicated uplink packet.

32. The system of claim 31 , wherein the CU-CP node is further configured to:

after receiving the at least one second message, send, to the CU-UP node, a configuration update message indicating downlink tunnel information for the bearer.

33. The system of claim 28 , wherein the CU-CP node is further configured to:

send, to the CU-UP node, status information comprising an indication of at least one of:

a hardware load,

a load of an N2 interface between the CU-UP node and a core network entity,

a load of an F1 interface between the CU-UP node and at least one distributed unit (DU) node,

status information associated with the CU-CP node,

status information associated with the at least one DU node,

a composite available capacity group, or

a network slice overload.

34. The system of claim 28 , wherein the response comprises an indication of an activation or a deactivation of the packet duplication.

35. The system of claim 28 , wherein the configuration of the packet duplication comprises configuration of packet data convergence protocol (PDCP) packet duplication.

36. The system of claim 28 , wherein the packet duplication state is activated.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 2, 2024
From: PARK, KYUNGMIN; DINAN, ESMAEL HEJAZI; JEON, HYOUNGSUK; ZHOU, HUA; BABAEI, ALIREZA; CIRIK, ALI CAGATAY
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068761/0749 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 2, 2024
From: PARK, KYUNGMIN; DINAN, ESMAEL HEJAZI; JEON, HYOUNGSUK; ZHOU, HUA; BABAEI, ALIREZA; CIRIK, ALI CAGATAY
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 068761/0754 →
Continuity (4)
Continuation 17572211 · Jan 10, 2022
Continuation 16409260 · May 10, 2019
Provisional Application 62669927 · May 10, 2018
Related Publication 20240187147A1 · Jun 6, 2024
References Cited (361)
US 8798093B2 · Wu · 2014 [cited by applicant]
US 9432847B2 · Yi et al. · 2016 [cited by applicant]
US 9596674B2 · Somasundaram et al. · 2017 [cited by applicant]
US 20080310367A1 · Meylan · 2008 [cited by applicant]
US 20090175163A1 · Sammour et al. · 2009 [cited by applicant]
US 20090190480A1 · Sammour et al. · 2009 [cited by applicant]
US 20100034169A1 · Maheshwari et al. · 2010 [cited by applicant]
US 20120069732A1 · Xu et al. · 2012 [cited by applicant]
US 20130250828A1 · Chou et al. · 2013 [cited by applicant]
US 20140079022A1 · Wang et al. · 2014 [cited by applicant]
US 20140192775A1 · Li et al. · 2014 [cited by applicant]
US 20150016312A1 · Li et al. · 2015 [cited by applicant]
US 20170041767A1 · Vajapeyam et al. · 2017 [cited by applicant]
US 20170150408A1 · Joseph et al. · 2017 [cited by applicant]
US 20170202053A1 · Rune · 2017 [cited by applicant]
US 20180006770A1 · Guo et al. · 2018 [cited by applicant]
US 20180124642A1 · Phuyal et al. · 2018 [cited by applicant]
US 20180124825A1 · Lee et al. · 2018 [cited by applicant]
US 20180279168A1 · Jheng et al. · 2018 [cited by applicant]
US 20180279169A1 · Wang et al. · 2018 [cited by applicant]
US 20180279193A1 · Park et al. · 2018 [cited by applicant]
US 20180279204A1 · Kim et al. · 2018 [cited by applicant]
US 20180279218A1 · Park et al. · 2018 [cited by applicant]
US 20180279262A1 · Babaei et al. · 2018 [cited by applicant]
US 20180279401A1 · Hong et al. · 2018 [cited by applicant]
US 20180287677A1 · Nagaraja et al. · 2018 [cited by applicant]
US 20180352601A1 · Park et al. · 2018 [cited by applicant]
US 20180367288A1 · Vrzic et al. · 2018 [cited by applicant]
US 20180368107A1 · Babaei et al. · 2018 [cited by applicant]
US 20180376457A1 · Tseng et al. · 2018 [cited by applicant]
US 20190037635A1 · Guo et al. · 2019 [cited by applicant]
US 20190053325A1 · Yu et al. · 2019 [cited by applicant]
US 20190132790A1 · Lee et al. · 2019 [cited by applicant]
US 20190182211A1 · Yang · 2019 [cited by examiner]
US 20190215726A1 · Park et al. · 2019 [cited by applicant]
US 20190253926A1 · Kim et al. · 2019 [cited by applicant]
US 20190268799A1 · Hong et al. · 2019 [cited by applicant]
US 20200029252A1 · Marquezan et al. · 2020 [cited by applicant]
US 20200084682A1 · Wang et al. · 2020 [cited by applicant]
US 20200119864A1 · Xu et al. · 2020 [cited by applicant]
US 20200127766A1 · Jonsson et al. · 2020 [cited by applicant]
US 20200154498A1 · Wang · 2020 [cited by examiner]
US 20200162211A1 · Wang et al. · 2020 [cited by applicant]
US 20200382240A1 · Centonza et al. · 2020 [cited by applicant]
US 20210084515A1 · Yokoyama et al. · 2021 [cited by applicant]
US 20210092667A1 · Zhu et al. · 2021 [cited by applicant]
CN 102448060A · 2012 [cited by applicant]
WO 2018143703A1 · 2018 [cited by applicant]
WO 2018147677A1 · 2018 [cited by applicant]
WO 2018175199A1 · 2018 [cited by applicant]
WO 2018183085A1 · 2018 [cited by applicant]
WO 2018202933A1 · 2018 [cited by applicant]
WO 2018203736A1 · 2018 [cited by applicant]
WO 2018231425A1 · 2018 [cited by applicant]
WO 2018237001A1 · 2018 [cited by applicant]
WO 2019139530A1 · 2019 [cited by applicant]
R3-180599 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Huawei, Title: pCR to 38.473 on UE context management for mobility handling for SA operation. [cited by applicant]
R3-180606 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: NTT Docomo, Inc., Title: Summary of offline discussion on CU-DU QoS handling. [cited by applicant]
R3-180807 3GPP TSG-RAN WG3 Meeting #99, Athens, Greece, Feb. 26-Mar. 2, 2018, Source: CATT, Title: Discussion on activation of PDCP Duplication. [cited by applicant]
R3-181732 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: ZTE, Title: Bearer Context Modification over E1 interface for TS38.460. [cited by applicant]
R3-181733 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: ZTE, Title: Bearer Context Modification over E1 interface for TS38.463. [cited by applicant]
R3-181735 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: ZTE, Title: Discussion on PDCP Count wrap around. [cited by applicant]
R3-181736 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: ZTE, Title: Discussion on E1 interface setup. [cited by applicant]
R3-181833 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: NEC (Rapporteur), Title: Baseline CR for June version of TS 38.401 covering agreements of RAN3#99 on CPUP_Split. [cited by applicant]
R3-181842 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: (TP for CPUP_Split BL CR for TS 38.401) Support of change of gNB-CU-UP. [cited by applicant]
R3-181843 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: (TP for CPUP_Split BL CR for TS 38.401) FFS resolution for E1 overall procedures. [cited by applicant]
R3-181844 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Definition of gNB-CU-CP/UP. [cited by applicant]
R3-181845 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: E1 non-UE associated functions. [cited by applicant]
R3-181846 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: E1 non-UE associated procedures. [cited by applicant]
R3-181847 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: gNB-CU-UP notification function. [cited by applicant]
R3-181848 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: gNB-CU-UP notification procedure. [cited by applicant]
R3-181849 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Bearer Context Management procedures. [cited by applicant]
R3-181850 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Signalling transport for E1. [cited by applicant]
R3-181893 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: LG Electronics, KT Corp., Title: Procedures for Security Support in CU-CP/UP Separation. [cited by applicant]
R3-182056 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: LG Electronics, KT Corp., Title: Discussion on Bearer Context Modification. [cited by applicant]
R3-182078 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: E1 interface management procedures. [cited by applicant]
R3-182079 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: CU-UP Security Capability indication to CU-CP. [cited by applicant]
R3-182080 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: TP for TS 38.463 on E1 interface management. [cited by applicant]
R3-182081 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: Additional UE-associated E1 procedures. [cited by applicant]
R3-182082 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Samsung, Title: TP for TS 38.463 on additional UE-associated E1 procedures. [cited by applicant]
R3-182109 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Huawei, Title: Initial TPs to 38.462. [cited by applicant]
R3-182110 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Huawei, Title: Rapporteur editorial updates to 38.462. [cited by applicant]
R3-182129 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Huawei, Title: Inactivity monitoring in CP/UP separation. [cited by applicant]
R3-182130 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Huawei, Title: (TP for NR BL CR for TS 38.401) On RRC state transition for CP-UP separation. [cited by applicant]
R3-182131 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Huawei, Title: Data Forwarding in CP/UP separation. [cited by applicant]
R3-182132 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Huawei, Title: pCR to 38.460 on QoS handling over E1. [cited by applicant]
R3-182134 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Huawei, Title: pCR to 38.460 on secondary node modification triggered by gNB-CU-CP. [cited by applicant]
R3-182136 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Huawei, Title: pCR to 38.460 on centralized retransmission for CP-UP separation. [cited by applicant]
R3-182224 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: E1 support for RRC-inactive. [cited by applicant]
R3-182225 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Dual-connectivity configuration over E1. [cited by applicant]
R3-182226 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Potentials of RAN UP network function virtualization. [cited by applicant]
R3-182227 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Feb. 26-Mar. 2, 2018, Source: Ericsson, Title: PDCP duplication configuration. [cited by applicant]
R3-182228 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Vodafone, KT, At&T, Title: Support of RAN UP network function virtualization at handover. [cited by applicant]
R3-182229 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Support of RAN UP network function virtualization at handover—for 38.300. [cited by applicant]
R3-182230 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Support of RAN UP network function virtualization at handover—for 38.413. [cited by applicant]
R3-182231 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Support of RAN UP network function virtualization at handover—for 38.423. [cited by applicant]
R3-182232 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Support of RAN UP network function virtualization at handover—for 36.300. [cited by applicant]
R3-182233 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Bearer Context definition. [cited by applicant]
R3-182234 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Resolve FFS in procedures in TS 38.401. [cited by applicant]
R3-182235 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Multiple TNL associations over E1. [cited by applicant]
R3-182237 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: E1 Setup procedure. [cited by applicant]
R3-182238 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: E1 Reset procedure. [cited by applicant]
R3-182239 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: E1 Release procedure. [cited by applicant]
R3-182240 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: E1 Error Indication. [cited by applicant]
R3-182241 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Bearer Context Modification procedure. [cited by applicant]
R3-182242 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: E1 Configuration Update. [cited by applicant]
R2-1800898 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: vivo, Title: Text proposal for repetition of the configured grant. [cited by applicant]
R2-1800902 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: vivo, Title: Collision between dynamic grant and configured grant. [cited by applicant]
R2-1800925 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Intel Corporation, Title: URLLC exception for dynamic grant. [cited by applicant]
R2-1801032 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Leftovers of HARQ Transmission with Configured Grant Timer. [cited by applicant]
R2-1801033 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Corrections on HARQ Transmission with ConfiguredGrantTimer in TS 38.321. [cited by applicant]
R2-1801034 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Corrections on Retransmission for Configured Grant. [cited by applicant]
R2-1801035 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Corrections on calculations of transmission occasions of configured grant. [cited by applicant]
R2-1801036 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Further discussion on configuration of ConfiguredGrantTimer. [cited by applicant]
R2-1801037 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Corrections on flexible occasion of initial transmission and repetition for configured grant. [cited by applicant]
R2-1801038 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Impact of SUL on configured grant. [cited by applicant]
R2-1801039 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: Configured grant Type1 operation with BWP switch. [cited by applicant]
R2-1801052 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics Inc., Title: Correction on ConfiguredGrantTimer. [cited by applicant]
R2-1801063 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics Inc., Title: Repetition transmission on configured uplink grant. [cited by applicant]
R2-1801081 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: ZTE, Title: Consideration on the configured grant for supporting SUL. [cited by applicant]
R2-1801125 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: InterDigital Inc., Title: Correction on override of configured assignment by dynamic assignment. [cited by applicant]
R2-1801126 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: InterDigital Inc., Title: Override of configured grant by dynamic grant in case of URLLC. [cited by applicant]
R2-1801239 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics Inc., Title: Prioritization between dynamic grant and configured grant for URLLC. [cited by applicant]
R2-1801277 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics Inc., Title: Restart condition of sCellDeactivationTimer with skipping operation. [cited by applicant]
R2-1801371 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: Remaining Issue on SPS/Grant-free: How to Handle Dynamic Grant Coinciding with Configured Grant. [cited by applicant]
R2-1801475 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics Inc., Title: Prevention of using CS grant. [cited by applicant]
R3-174356 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Transport layer protocol for F1-C. [cited by applicant]
R3-174357 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Transport layer protocol for F1-U. [cited by applicant]
R3-174359 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, Title: UE Initial Access procedure. [cited by applicant]
R3-174360 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, KT, Title: FFS resolution in intra-gNB-CU mobility. [cited by applicant]
R3-174361 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, KT, Title: TP of UE Context Modification and UE Attached Indication (TS 38.470). [cited by applicant]
R3-174362 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, KT, Title: TP of UE Context Modification and UE Attached Indication (TS 38.473). [cited by applicant]
R3-174364 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Nokia, Nokia Shanghai Bell, Title: FFS resolution in Centralized Retransmission. [cited by applicant]
R3-174396 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ZTE, China Telecom, Title: Solution for UE Initial Access. [cited by applicant]
R3-174397 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ZTE, Title: Update on UE Context Management for TS38.470. [cited by applicant]
R3-174398 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ZTE, Title: Update on UE Context Management for TS38.473. [cited by applicant]
R3-174405 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ZTE, China Unicom, Title: Remaining Issues of Mobility Aspects. [cited by applicant]
R3-174408 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ZTE, Title: Consideration on the activation or deactivation of duplication. [cited by applicant]
R3-174409 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ZTE, China Telecom, Title: Remaining Issues of Centralized Retransmissions. [cited by applicant]
R3-174410 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ZTE, Title: TP for Centralized Retransmissions kept in TS38.475. [cited by applicant]
R3-174411 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ZTE, Title: TP for Centralized Retransmissions kept in TS38.425. [cited by applicant]
R3-174473 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, Title: pCR on open issues for PDCP duplication over F1 to 38.473. [cited by applicant]
R3-174482 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, Title: Further discussions on radio link outage indication. [cited by applicant]
R3-174533 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: CATT, Title: Discussion on CA based PDCP Duplication. [cited by applicant]
R3-174535 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: CATT, Title: Discussion on F1 Setup procedure. [cited by applicant]
R3-174536 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: CATT, Title: Discussion on Initial UE Access. [cited by applicant]
R3-174537 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: CATT, Title: Introduction of UE Reconfiguration Complete procedure. [cited by applicant]
R3-174538 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: CATT, Title: TP for 38.473 on UE Reconfiguration Completion procedure. [cited by applicant]
R3-174542 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: CATT, Title: Discussion on inter-DU mobility without MN involved. [cited by applicant]
R3-174543 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: CATT, Title: Stage 3 TP on inter-DU mobility without MN involved. [cited by applicant]
R3-174545 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: CATT, Title: Discussion on the Intra-cell HO and SCG change procedure. [cited by applicant]
R3-174546 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: CATT, Title: TP for 38.473 on Intra-cell HO and SCG change procedure. [cited by applicant]
R3-174606 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, KT, Title: Initial access procedure considering CU-DU split. [cited by applicant]
R3-174607 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, KT, Title: Stage 3 TP for TS38.473 to reflect initial access procedure. [cited by applicant]
R3-174608 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, KT, Title: RRC connection resume procedure considering CU-DU split. [cited by applicant]
R3-174609 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, KT, Title: RRC connection reestablishment procedure considering CU-DU split. [cited by applicant]
3GPP TS 38.331 V15.0.0 (Dec. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) Protocol Specification (Release 15). [cited by applicant]
3GPP TS 38.331 V15.3.0 (Sep. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) Protocol Specification (Release 15). [cited by applicant]
3GPP TS 38.463 V0.2.0 (Apr. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; E1 application protocol (E1AP) (Release 15). [cited by applicant]
3GPP TS 38.473 V15.0.0 (Dec. 2017), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15). [cited by applicant]
3GPP TS 38.473 V15.3.0 (Sep. 2018), Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15). [cited by applicant]
R2-1801279 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics Inc., Title: Restart condition of sCellDeactivationTimer with skipping operation. [cited by applicant]
R2-1712238 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: OPPO, Title: Discussion on Detailed Issues on RLM. [cited by applicant]
R2-1712276 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Spreadtrum Communications, Title: Discussions on the IS and OOS Counting Procedure. [cited by applicant]
R2-1712308 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: TCL, Title: Interaction between PDCP and RLC Entities for duplication in NR-NR DC. [cited by applicant]
R2-1712435 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ZTE Corporation, Title: Consideration on PDCP Duplication in NR. [cited by applicant]
R2-1712559 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, HiSilicon, Title: RLF for NR. [cited by applicant]
R2-1712736 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, ASUSTek, HiSilicon, Title: PDCP operation for packet duplication. [cited by applicant]
R2-1712737 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, HiSilicon, Title: PDCP data volume calculation for packet duplication. [cited by applicant]
R2-1712738 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, HiSilicon, Title: Clarification on bearer type for packet duplication. [cited by applicant]
R2-1712739 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Huawei, HiSilicon, Title: Enhancements for DL packet duplication. [cited by applicant]
R2-1712753 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: vivo, Title: RLM/RLF in NR. [cited by applicant]
R2-1712914 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Lenovo, Motorola Mobility, Title: PDCP packet duplication. [cited by applicant]
R2-1712926 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: PDCP duplication and discard. [cited by applicant]
R2-1712928 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: PDCP duplication for AM operation. [cited by applicant]
R2-1712929 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: PDCP duplication transmit procedure. [cited by applicant]
R2-1712932 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: PDCP data volume reporting in duplication. [cited by applicant]
R2-1712964 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, Title: Discussion on PDCP data volume calculation during PDCP Duplication. [cited by applicant]
R2-1712965 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Institute for Information Industry (III), Title: Discussion on Uplink Packet Duplication. [cited by applicant]
R2-1713004 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: vivo, Title: Layer-2 behaviors of PDCP duplication deactivation. [cited by applicant]
R2-1713005 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: vivo, Title: PDCP duplication impacts on LCP. [cited by applicant]
R2-1713006 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: vivo, Title: Discussion on the PDCP data volume. [cited by applicant]
R2-1713009 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: vivo, Title: UE layer-2 behaviors at Scell-failure. [cited by applicant]
R2-1713584 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Qualcomm Incorporated, Title: PDCP duplication. [cited by applicant]
R2-1713588 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: Remaining open issues of RLM and RLF in NR. [cited by applicant]
R2-1713641 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: ITL, Title: Configuration of PDCP duplication on default DRB. [cited by applicant]
R2-1713829 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, Title: Activation and Deactivation of PDCP Duplication. [cited by applicant]
R2-1713830 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, Title: Discussion on CA Duplication. [cited by applicant]
R2-1713831 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, Title: Initial State of Uplink Packet Duplication. [cited by applicant]
R2-1713848 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, Title: The Necessity of Fast RLF Recovery based on T312 in NR. [cited by applicant]
R2-1800155 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: OPPO, Title: Discussion on behaviour of ConfiguredGrantTimer. [cited by applicant]
R2-1800165 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: CATT, Title: UE behavior on configured grant timer upon DCI reception. [cited by applicant]
R2-1800334 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: SPS and BWP inactivity timer interaction. [cited by applicant]
R2-1800373 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung Electronics R&D Institute UK, Title: Preventing simultaneous Type 1 configured grants on SUL and UL. [cited by applicant]
R2-1800374 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung Electronics R&D Institute UK, Title: Corrections to preventing simultaneous Type 1 configured grants on SUL and UL. [cited by applicant]
R2-1800566 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics Inc., Title: BWP timer restart for DL SPS. [cited by applicant]
R2-1800586 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Prioritization between dynamic grant and configured grant. [cited by applicant]
R2-1800587 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Nokia, Nokia Shanghai Bell, Title: Correction on prioritization between dynamic grant and configured grant. [cited by applicant]
R2-1800622 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: Correction for SPS and Type-2 Configured Grant Calculation. [cited by applicant]
R2-1800624 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: Impact of Flexible Transmission on Configured Grant Operation. [cited by applicant]
R2-1800659 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: Draft CR for correction on SPS and Type-2 configured grant. [cited by applicant]
R2-1800661 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung, Title: Draft CR for flexible configured grant transmission. [cited by applicant]
R2-1800708 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Confirmation of Configured UL Grant Type 2 Activation for Multiple Aggregated Cells. [cited by applicant]
R2-1800709 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Alignment of terminology for Configured Scheduling and SPS. [cited by applicant]
R2-1800818 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung Electronics R&D Institute UK, Title: Corrections to prevent simultaneous Type 1 configured grants on SUL and UL. [cited by applicant]
R2-1800819 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Samsung Electronics R&D Institute UK, Title: Preventing simultaneous Type 1 configured grants on SUL and UL. [cited by applicant]
R2-162709 3GPP TSG-RAN WG2 Meeting #93bis, Dubrovnik, Croatia, Apr. 11-15, 2016, Source: Beam support in NR. [cited by applicant]
May 27, 2019—Extended European Search Report—19155025.0. [cited by applicant]
NTT Docomo, Inc.: “F1 interface: Radio resource configuration management”, May 15-19, 2017. [cited by applicant]
CMCC: “System information generation and delivery in CU-DU split architecture”, Aug. 21-25, 2017. [cited by applicant]
ZTE: “Discussion on the solution for UE Initial Access”, Oct. 9-13, 2017. [cited by applicant]
Feb. 27, 2019—EP Search Report—19151430.6. [cited by applicant]
May 14, 2017—TP for UE Radio Bearer Management. [cited by applicant]
Nokia—May 1, 2010—“Enabling MRO in case of re-establishment request in unprepared eNB”. [cited by applicant]
Apr. 8, 2019—Extended European Search Report—EP 19151473.6. [cited by applicant]
ZTE—Consideration on the activation or deactivation of duplication—Nov. 17, 2017. [cited by applicant]
CATT—Discussion on CA based PDCP Duplication—Sep. 30, 2017. [cited by applicant]
3GPP Standard—“3rd Generation Partnership Project: Technical Specification Group Radio Access Network; NG-RAN; F1 application protocol (F1AP) (Release 15)”—Dec. 11, 2017. [cited by applicant]
3GPP Standard—“3rd Generation Partnership Project; Technical Specification Group Radio Access Network NR Radio Resource Control (RRC) protocol specification (Release 15)”—Jan. 4, 2018. [cited by applicant]
Aug. 6, 2019—European Extended Search Report—EP 19157448.2. [cited by applicant]
3GPP TSG-RAN WG2 #100: “Discussion on Inter-nodeRRC container”, Dec. 1, 2017. [cited by applicant]
3GPP TSG-RAN Meeting #76: “Miscellaneous general corrections and clarifications resulting from ASN. 1 review”, Jun. 5, 2017. [cited by applicant]
R1-1704159 3GPP TSG-RAN WG2 Meeting #98, Hangzhou, China, May 15-19, 2017, Source: Samsung, Title: Random Access Response in NR. [cited by applicant]
R1-1704672 3GPP TSG-RAN WG2 Meeting #98, Hangzhou, China, May 15-19, 2017, Source: ZTE, Title: Consideration on the 4-step random access procedure. [cited by applicant]
R2-1704901 3GPP TSG-RAN WG2 Meeting #98, Hangzhou, China, May 15-19, 2017, Source: Qualcomm Incorporated, Title: Prioritized random access in NR. [cited by applicant]
R3-172102 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: China Telecom, Title: On the preliminary transport comparison between F1-C and F1-U protocols. [cited by applicant]
R3-172176 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Huawei, Title: F1AP procedures for RRC Connection Setup. [cited by applicant]
R3-172178 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Huawei, Title: TP on Transmitting RRC Connection Setup message over F1 to 38.470. [cited by applicant]
R3-172198 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Huawei, Title: Discussions on F1 interface management. [cited by applicant]
R3-172199 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Huawei, Title: TP on F1 interface management to 38.470. [cited by applicant]
R3-172200 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Huawei, HiSilicon, Title: TP on F1 interface management procedures to 38.473. [cited by applicant]
R3-172209 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Chinatelecom, Title: gNB and gNB-CU ID discussion. [cited by applicant]
R3-172218 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: CATT, Title: Discussion on the F1AP functions necessary for Option 3. [cited by applicant]
R3-172244 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Samsung, KT, SK Telecom, Title: Centralized retransmission of lost PDUs. [cited by applicant]
R3-172250 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Samsung, KT, SK Telecom, Title: On-demand SI support in high layer functional split. [cited by applicant]
R3-172251 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Samsung, KT, SK Telecom, Title: Stage 2 text proposal for TS38.401 on mechanism of centralized retransmission of lost PDUs. [cited by applicant]
R3-172256 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Samsung, KT, SK Telecom, Title: Stage 2 text proposal for TS38.401 on supporting on-demand SI. [cited by applicant]
R3-172266 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: LG Electronics Inc., Title: Issue on C-RNTI allocation for RRC connection resume. [cited by applicant]
R3-172309 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Inter-gNB-DU Mobility procedure. [cited by applicant]
R3-172310 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: TP of Inter-gNB-DU Mobility procedure (TS 38.401). [cited by applicant]
R3-172321 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: Retransmission procedure in radio link outage. [cited by applicant]
R3-172322 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: TP of Retransmission procedure in radio link outage (TS 38.401). [cited by applicant]
R3-172323 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: TP of Retransmission procedure in radio link outage (TS 38.475). [cited by applicant]
R3-172324 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Nokia, Title: [Draft] LS on retransmission procedure in radio link outage. [cited by applicant]
R3-172333 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: UE Initial Access Procedure. [cited by applicant]
R3-172334 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Nokia, Alcatel-Lucent Shanghai Bell, Title: TP of UE Initial Access procedure (TS 38.401). [cited by applicant]
R3-172342 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: LG Electronics Inc., Title: Consideration on C-RNTI during initial UE access. [cited by applicant]
R3-172343 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: LG Electronics Inc., Title: TP for consideration on C-RNTI during initial UE access. [cited by applicant]
R3-172344 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: LG Electronics Inc., Title: TP for consideration on C-RNTI during initial UE access. [cited by applicant]
R3-172345 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: ZTE, Title: RRC message transmission over F1 interface for TS 38.401. [cited by applicant]
R3-172346 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: ZTE, Title: RRC message transmission over F1 interface for TS 38.470. [cited by applicant]
R3-172347 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: ZTE, Title: RRC message transmission over F1 interface for TS 38.473. [cited by applicant]
R3-172356 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: ZTE, China Telecom, Title: Discussion on flow control over F1-U. [cited by applicant]
R3-172357 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: ZTE, Title: Update on flow control over F1 interface for TS 38.401. [cited by applicant]
R3-172358 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: ZTE, Title: Flow control over F1 interface for TS 38.475. [cited by applicant]
R3-172399 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: NEC, Title: How many gNB-DUs can be operated by one gNB-CU. [cited by applicant]
R3-174611 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, KT, Title: Mobility procedures with high layer split. [cited by applicant]
R3-174612 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, KT, Title: Stage 2 TP for TS38.470 on mobility related procedures. [cited by applicant]
R3-174613 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, KT, Title: Stage 3 TP for TS38.473 on mobility related procedures. [cited by applicant]
R3-174618 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, KT, Title: Further discussions on PDCP duplication in high-layer split. [cited by applicant]
R3-174637 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Intel Corporation, Title: Flow Control enhancements for downlink PDCP duplication. [cited by applicant]
R3-174638 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Intel Corporation, Title: Flow Control enhancements for uplink PDCP duplication. [cited by applicant]
R3-174663 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: CMCC, Title: UE initial access procedure for CU-DU architecture. [cited by applicant]
R3-174769 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: Discard the duplicated transmissions of PDCP PDUs. [cited by applicant]
R3-174772 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: Benefits of F1AP Transaction IDs. [cited by applicant]
R3-174773 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: Further discussion about TNL solution for F1-C. [cited by applicant]
R3-174774 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: On parallel transactions over F1. [cited by applicant]
R3-174781 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: Mobility procedures. [cited by applicant]
R3-174782 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Ericsson, Title: Content for UE mobility command messages. [cited by applicant]
R3-174786 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: NTT Docomo, Inc., Title: How to acquire status of re-transmitted packets. [cited by applicant]
R3-174850 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: NTT Docomo, Inc., Title: Consideration on data volume reporting. [cited by applicant]
R3-174854 3GPP TSG-RAN WG3 Meeting #98, Reno, USA, Nov. 27-Dec. 1, 2017, Source: KT Corp., Title: Considerations for F1 Setup Procedure. [cited by applicant]
R3-180123 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: ZTE, Title: QoS information transfer over F1 interface. [cited by applicant]
R3-180124 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: ZTE, Title: Update on QoS information transfer for TS38.473. [cited by applicant]
R3-180139 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: ZTE, Title: NW slicing for high layer functional split. [cited by applicant]
R3-180164 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: CATT, Title: TP for 38.401 BL on UE Reconfiguration Completion procedure. [cited by applicant]
R3-180179 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: CATT, Title: Discussion on UE Context Management procedure. [cited by applicant]
R3-180180 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: CATT, Title: TP for TS 38.473 on UE Context Management procedure. [cited by applicant]
R3-180188 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Nokia, Nokia Shanghai Bell, Title: QoS handling for F1. [cited by applicant]
R3-180189 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Nokia, Nokia Shanghai Bell, Title: TP of QoS handling for F1 (TS38.473). [cited by applicant]
R3-180190 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Nokia, Nokia Shanghai Bell, KT, Title: User inactivity monitoring. [cited by applicant]
R3-180234 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: LG Electronics Inc., KT Corp., Title: QoS aspect in UE context management function. [cited by applicant]
R3-180235 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: LG Electronics Inc., KT Corp., Title: Stage 3 on QoS aspect in UE context management function. [cited by applicant]
R3-180244 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Samsung, KT, Title: UE context management update considering parameters over X2 for EN-DC. [cited by applicant]
R3-180285 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Samsung, KT, Title: User inactivity monitoring in CU-DU architecture. [cited by applicant]
R3-180286 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Samsung, KT, Title: TP for TS 38.473 on user inactivity monitoring. [cited by applicant]
R3-180300 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: NEC, Title: RLC Mode indication in F1AP. [cited by applicant]
R3-180330 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: CMCC, Title: QoS management over F1. [cited by applicant]
R3-180343 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Huawei, Title: Further discussions on QoS info transfer over F1. [cited by applicant]
R3-180344 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Huawei, Title: pCR to 38.473 on QoS info transfer over F1. [cited by applicant]
R3-180352 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Huawei, Title: Further discussions on UE context management. [cited by applicant]
R3-180355 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Huawei, Title: CR to BL 38.473 on inter-gNB-DU or intra-gNB-DU handover case for SA operation. [cited by applicant]
R3-180356 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Huawei, Title: pCR to 38.473 on the introduction of Handover Preparation Information for SA Operation. [cited by applicant]
R3-180357 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Huawei, Title: Further discussions on the content of serving cell info. [cited by applicant]
R3-180367 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Huawei, Title: Further discussions on confirmation to gNB-DU about completion of RRC messages. [cited by applicant]
R3-180425 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Title: UE radio capabilities over F1. [cited by applicant]
R3-180426 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Title: Cell information over F1. [cited by applicant]
R3-180427 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Title: UE Context Setup over the F1. [cited by applicant]
R3-180428 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Title: UE Reject Indication and gNB-DU admission result. [cited by applicant]
R3-180429 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Title: Further analysis on inactivity monitoring. [cited by applicant]
R3-180430 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Title: Creation of signalling connection. [cited by applicant]
R3-180431 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Title: RRC Container in UE Context Setup Request. [cited by applicant]
R3-180432 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Title: RLC mode indication. [cited by applicant]
R3-180433 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Title: Introduction of UE Reconfiguration Complete procedure. [cited by applicant]
R3-180518 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Vodafone, Title: UE context Setup over the F1. [cited by applicant]
R3-180596 3GPP TSG-RAN WG3 NR Ad Hoc, Sophia Antipolis, France, Jan. 22-26, 2018, Source: Ericsson, Title: UE Reject Indication. [cited by applicant]
R3-172401 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: CMCC, Title: gNB ID and NCGI considering CU-DU split. [cited by applicant]
R3-172417 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: ZTE, China Unicom, Title: Discussion on CU DU ID and NCGI. [cited by applicant]
R3-172418 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: ZTE, China Unicom, Title: CUDU ID and NCGI for TS 38.300. [cited by applicant]
R3-172481 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Samsung, Title: Identification of gNB, gNB-CU/DU, and NR cell. [cited by applicant]
R3-172484 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Vodafone, Title: Common Radio Resource Management Functional Split for Different Deployment Scenarios. [cited by applicant]
R3-172511 3GPP TSG-RAN3 NR AdHoc Meeting, Qingdao, China, Jun. 27-29, 2017, Source: Ericsson, Title: Resilience and scalability in a disaggregated gNB. [cited by applicant]
3GPP TS 36.300 V14.3.0 (Jun. 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 38.300 V1.0.0 (Sep. 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]
R2-1707705 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: OPPO, Title: Control on UL packet duplication for split bearer. [cited by applicant]
R2-1707708 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: OPPO, Title: PDCP operation for UL packet duplication. [cited by applicant]
R2-1707717 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: UE behaviors upon deactivation of DC duplication. [cited by applicant]
R2-1707718 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, ASUSTeK, HiSilicon, Title: RLC behaviors upon duplicate deactivation. [cited by applicant]
R2-1707719 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, ASUSTek, HiSilicon, Title: PDCP operation for packet duplication. [cited by applicant]
R2-1707720 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: PDCP data volume calculation for packet duplication (Revision of R2-1706484). [cited by applicant]
R2-1707924 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: CATT, Title: PDCP Status Report for Duplication. [cited by applicant]
R2-1707925 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: CATT, Title: Duplication Bearer Type. [cited by applicant]
R2-1707982 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Nokia, Mediatek, Nokia Shanghai Bell, Title: Initial State of PDCP Duplication (Revision of R2-1706545). [cited by applicant]
R2-1707990 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Nokia, Nokia Shanghai Bell, Title: Duplication Impacts to PDCP. [cited by applicant]
R2-1708017 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Ericsson, Title: Aligned duplication support for DRBs and SRBs. [cited by applicant]
R2-1708097 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: MediaTek Inc., Title: Stage-2 aspects of data duplication (Revision of R2-1707260). [cited by applicant]
R2-1708098 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: MediaTek Inc., Title: Data duplication in NR (Revision of R2-1707261). [cited by applicant]
R2-1708329 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Ericsson, Title: PDCP and RLC behaviour for PDCP data duplication. [cited by applicant]
R2-1708333 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Ericsson, Title: Packet duplication in CA (Revision of R2-1707172). [cited by applicant]
R2-1708335 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Ericsson, Title: PDCP dynamic link switching. [cited by applicant]
R2-1708336 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Ericsson, Title: PDCP data volume reporting in duplication (Revision of R2-1704370). [cited by applicant]
R2-1708337 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Ericsson, Title: PDCP duplication control related to SCell control. [cited by applicant]
R2-1708444 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Samsung, Title: Discussion on PDCP data volume calculation. [cited by applicant]
R2-1708489 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Vivo, Title: Duplication deactivation due to SCell or BWP deactivation. [cited by applicant]
R2-1708508 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Vivo, Title: Layer-2 behaviors of PDCP duplication activation deactivation. [cited by applicant]
R2-1708573 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Panasonic, Title: Packet duplication during the handover. [cited by applicant]
R2-1708624 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Lenovo, Motorola Mobility, Title: PDCP packet duplication. [cited by applicant]
R2-1708691 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, HiSilicon, Title: Remaining stage 2 issues for CA duplication and for DC duplication. [cited by applicant]
R2-1708735 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: InterDigital Inc., Title: Details of duplication and routing for SRB. [cited by applicant]
R2-1708821 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Intel Corporation, Title: Support of CA packet duplication for RLC AM. [cited by applicant]
R2-1708862 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Fujitsu, Title: Stage 2 TP for RLC AM duplication. [cited by applicant]
R2-1708950 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Qualcomm Incorporated, Title: Further considerations for Packet duplication. [cited by applicant]
R2-1708951 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Qualcomm Incorporated, Title: PDCP duplication. [cited by applicant]
R2-1709032 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Samsung, Title: PDCP Duplication Operations (Revision of R2-177368). [cited by applicant]
R2-1709036 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Samsung, Title: Uplink DRB Duplication. [cited by applicant]
R2-1709061 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: LG Electronics Inc., Title: Discussion on the duplicate detection in PDCP. [cited by applicant]
R2-1709077 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: ITRI, Title: SCG Failure Case for Duplication SRB. [cited by applicant]
R2-1709095 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: LG Electronics Inc., Title: Need for Duplicate RB. [cited by applicant]
R2-1709100 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: LG Electronics Inc., Title: Packet duplication in PDCP (Revision of R2-1706870). [cited by applicant]
R2-1709870 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Ericsson, Title: TP on Radio Link Failure for 38.300. [cited by applicant]
R3-173128 3GPP TSG-RAN2 Meeting #99, Berlin, Germany, Aug. 21-25, 2017, Source: Huawei, Title: PDCP duplication for CU-DU. [cited by applicant]
R2-1800376 3GPP TSG-RAN WG2 NR Ad Hoc, Vancouver, Canada, Jan. 22-26, 2018, Source: Huawei, HiSilicon, Title: CR on the prioritization between dynamic scheduling and configured scheduling. [cited by applicant]
R2-1800158 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: OPPO, Title: CR on ConfiguredGrantTimer for C-RNTI based grant. [cited by applicant]
R2-1800647 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: OPPO, Title: Correction on ConfiguredGrantTimer. [cited by applicant]
R2-1800710 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: Ericsson, Title: Alignment of terminology for Configured Scheduling and SPS. [cited by applicant]
R2-1801053 3GPP TSG-RAN WG2 AH, Vancouver, Canada, Jan. 22-26, 2018, Source: LG Electronics Inc., Title: Correction on ConfiguredGrantTimer. [cited by applicant]
R3-182243 3GPP TSG RAN WG3 Meeting #99bis, Sanya, China, Apr. 16-20, 2018, Source: Ericsson, Title: Bearer Context Setup procedure. [cited by applicant]
R2-1713898 3GPP TSG-RAN WG2 Meeting #100, Reno, USA, Nov. 27-Dec. 1, 2017, Source: Samsung, Title: RLM RS type and L3 parameter differentiation. [cited by applicant]
Dec. 2, 2019—European Extended Search Report—EP 19173901.0. [cited by applicant]
R3-183279 3GPP TSG-RAN2 Meeting #100, Busan, Korea, May 21-25, 2019, Source: Huawei, Title: pCR to 38.460 on indication of PDCP duplication over E1 interface. [cited by applicant]
Sep. 24, 2021—European Office Action—EP 19173901.0. [cited by applicant]