name: PDCP
full_form: Packet Data Convergence Protocol
context: This solution supports UP IP at the PDCP layer using either E-UTRA PDCP or NR PDCP. For option 1 (eUTRA with EPC), the UP IP over E-UTRA PDCP is already specified in TS 33.401 [3] for the relay nodes. This solution reuses this feature to support UP IP at the E-UTRA PDCP layer. NOTE 1: Option 1 can use either E-UTRA PDCP or NR PDCP as determined by the eNB. For option 3 (eUTRA - NR Dual Connectivity or EN-DC), the network can either configure the UE with NR PDCP or E-UTRA PDCP for the MN terminated MCG bearers while NR PDCP is always configured for all other bearers, as specified in clause 4.2.2 of TS 37.340 [6] (as also shown in the figure below). NOTE 2: How the network configures the UE with NR PDCP or E-UTRA PDCP for MN terminated MCG bearers is not addressed in the present document. Figure 6.19.3-1: Radio Protocol Architecture for MCG, SCG and split bearers from a UE perspective in MR-DC with EPC (EN-DC) In this solution, when E-UTRA PDCP is configured, the UP IP is activated at
description: The Packet Data Convergence Protocol (PDCP) operates at the Radio Link Control (RLC) layer and above. It ensures efficient transmission of IP packets between the User Equipment (UE) and the network, providing convergence of packet data services over different radio access technologies.
explanation: The text describes PDCP as a protocol responsible for data transmission rules within telecommunications networks, specifically focusing on IP packet delivery across various radio access technologies.
section_title: 6.19.3	Solution description
biotag_Context: O,O,O,B-Protocol,B-Protocol,O,O,B-Protocol,O,O,O,B-Technology,B-Protocol,O,B-Network,O,O,O,O,O,O,O,O,B-Protocol,B-Protocol,O,B-Technology,B-Protocol,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,B-Protocol,O,O,B-Technology,B-Protocol,O,O,O,O,O,O,O,O,B-Technology,B-Protocol,O,B-Network,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Network,B-Technology,I-Technology,O,O,O,O,O,O,O,O,B-Device,O,B-Network,B-Protocol,O,B-Technology,B-Protocol,O,O,B-Network Function,O,B-Network,O,O,B-Network,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,B-Network,B-Protocol,O,B-Technology,B-Protocol,O,B-Network Function,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Device,O,O,B-Technology,O,B-Network,O,O,O,O,O,B-Technology,B-Protocol,O,O,O,B-Protocol,B-Protocol,O,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O