Summary based on the input provided by Nokia in RP-221201. This work item introduced NR power class 1 requirements to be applicable to all NR bands instead of only n14 like it was during REL16. The CR [3] has introduced core requirements for maximum output power, MPR and ACLR to be applicable to all bands. Release independence aspects were confirmed [4].

Summary based on the input provided by vivo in RP-220606. In Rel-15 and Rel-16, the UE FR1 transmit power and receiver sensitivity are tested by conducted methodology at the temporary antenna ports and it remains unknown what the actual performance of the UE would be in realistic network conditions with the UE antenna included. Radiated performance based on OTA testing is one of the most important characteristics to verify the entire UE performance under conditions more closely resembling the end user's interaction with the device. In order to ensure the good overall system performance, the requirements for NR UE TRP and TRS is important for consistent devices performance in the real NR networks which operate in the OTA manner. Unified requirements in 3GPP will provide authoritative guidance and will greatly promote the development of 5G industries. This WI defines the test methodology to verify the NR UE TRP TRS performance for NR standalone (SA) and NR non-standalone (NSA) operation mode. The outcome is captured in a new technical report TR 38.834. Then 3GPP can specify the follow-up OTA requirements for FR1 UE based on the available test method. A full package of test method under SA and NSA mode aiming to specify 3GPP TRP TRS OTA requirements is defined:

• UE type: The test method covers device types including Smartphone (1st priority), Tablet, LEE and LME.
• Usage scenarios: Talk mode using head & hand phantom for narrow devices between 56 mm and 72 mm and for wide devices with a width >72 mm and <92 mm; Browsing mode using hand phantom for narrow and wide phones; Free Space for devices not used in talk or browsing mode
• Performance metrics: Definition of TRP and TRS for Anechoic-Chamber-based test methodology
• UE positioning guidelines: UE positioning guidelines for Free space, Hand phantom only (Browsing mode), and Head and Hand phantom (Talk Mode); Both Wide Grip Hand and PDA Grip Hand positioning guidance (Wide Grip Hand for UE with Width >72mm and ≤92mm ; PDA Grip Hand for UE with Width ≥56mm and ≤72mm)
• Test procedure for SA and EN-DC: Test setup for Single-antenna and multiple-antennas anechoic chambers; TRP TRS calibration procedure; Ripple test procedure for 30cm and 50cm, both theta-axis and phi-axis; SA TRP TRS performance measurement procedure; EN-DC TRP TRS performance measurement procedure (Only NR carrier measurement is needed); Minimum measurement distance of anechoic chambers
• UE configurations: TRP antenna configuration (TAS OFF with antenna locked at primary antenna); TRS antenna configuration (no specific setting); EN-DC configuration (For TRP UL configuration: the UL output power of LTE carrier should be set as a constant power of 10dBm, while measuring NR at maximum output power, i.e., with fixed p-MaxEUTRA-r15=10 dBm, and p-NR-FR1 not configured; For TRS UL configuration: The UL power configuration for LTE and NR is 50%-50% power splitting, i.e. For PC3, p-MaxEUTRA-r15=20 dBm, and p-NR-FR1= 20dBm; For PC2, p-MaxEUTRA-r15=23 dBm, and p-NR-FR1= 23dBm.)
• Measurement uncertainty assessment (RAN5): Measurement error uncertainty contribution descriptions; Preliminary example of uncertainty budget (Expanded uncertainty for TRP hand only (browsing mode): 1.78 dB; Expanded uncertainty for TRP hand only (browsing mode): 2.20 dB)
  - Test phantom definition: PDA Grip Hand; Wide Grip Hand; Head Phantom

Summary based on the input provided by China Unicom in RP-220560. This WI specifies the interface, reusing E1 interface, interconnecting an eNB-CP (control plane and L2/L1 part of an eNB) and an eNB-UP (user plane part of an eNB) within E-UTRAN, or interconnecting an ng-eNB-CU-CP (control plane part of an ng-eNB central unit) and an ng-eNB-CU-UP (user plane part of an ng-eNB central unit) within NG-RAN[1]. In Release 16, E1 interface was limited to support interconnecting a gNB-CU-CP (control plane part of the gNB central unit) and a gNB-CU-UP (user plane part of the gNB central unit) in NG-RAN. In the WI, a split of eNB into an eNB-CP and an eNB-UP is defined for E-UTRAN, and a split of ng-eNB-CU into an ng-eNB-CU-CP and an ng-eNB-CU-UP is defined for NG-RAN. The eNB-CP hosts the RRC/ RLC/MAC/PHY and the control plane part of the PDCP protocol, and the eNB-UP hosts the user plane part of the PDCP protocol [3]. The split of ng-eNB-CU into an ng-eNB-CU-CP and an ng-eNB-CU-UP are defined for NG-RAN [4]. The ng-eNB-CU-CP hosts the RRC and the control plane part of the PDCP protocol of the ng-eNB-CU, and the ng-eNB-CU-UP hosts hosting the user plane part of the PDCP protocol and the SDAP protocol of the ng-eNB-CU. The E1 interface is used between an eNB-CP and an eNB-UP as shown in Figure 1, or between an ng-eNB-CU-CP and an ng-eNB-CU-UP as shown in Figure 2. The ng-eNB-CU-CP is connected with the ng-eNB-DU via the W1-C interface, while the ng-eNB-CU-UP is connected with the ng-eNB-DU through the W1-U interface. The architectures in Figure 1 and 2 enable the following deployment scenarios.

• An eNB may consist of an eNB-CP and multiple eNB-UPs.
• The eNB-UP is connected to the eNB-CP, while one eNB-UP is connected to only one eNB-CP.
• The eNB-CP and the eNB-UP terminates the UP interface used to convey E-UTRA or NR PDCP PDUs. NR user plane protocol, as defined in TS 38.425, is used for this interface.
• An ng-eNB may consist of an ng-eNB-CU-CP, one or more multiple ng-eNB-CU-UP(s) and one or more multiple ng-eNB-DU(s).
• One ng-eNB-DU is connected to only one ng-eNB-CU-CP, while one ng-eNB-CU-UP is connected to only one ng-eNB-CU-CP.
• One ng-eNB-DU can be connected to multiple ng-eNB-CU-UPs under the control of the same ng-eNB-CU-CP;
• One ng-eNB-CU-UP can be connected to multiple ng-eNB-DUs under the control of the same ng-eNB-CU-CP;
• An ng-eNB-CU-CP and an ng-eNB-CU-UP is connected via the E1 interface.
• An ng-eNB-DU is connected to an ng-eNB-CU-CP via the W1-C interface, and to an ng-eNB-CU-UP via the W1-U interface.

The general aspects and principles for E1 interface is specified in TS 37.480, and layer 1 of E1 is specified in TS 37.481.The E1 signalling transport supporting for ng-eNB-CU-CP/ng-eNB-CU-UP, eNB-CP/eNB-UP, which is based on the SCTP/IP protocol stack, are described in TS 37.482. The E1 application protocol (E1AP) supporting for ng-eNB-CU-CP/ng-eNB-CU-UP, eNB-CP/eNB-UP is specified in TS 37.483, including the relevant descriptions of E1 interface management procedures and E1AP elements, which allow to setup the E1 interface, exchange the relevant configuration data and date usage report in MR-DC between ng-eNB-CU-CP and ng-eNB-CU-UP, or between eNB-CP and eNB-UP.

Summary based on the input provided by Huawei, HiSiliconin RP-220410. This WI introduces the following enhancements:

• for Carrier Aggregation, faster SCell activation
• for EN-DC and for NR DC: a mechanism to deactivate and activate the NR Secondary Cell Group
• support of inter-SN Conditional PSCell Change and of Conditional PSCell Addition

The enhancement to SCell activation allows faster usage of SCells. For traffic consisting primarily in short bursts, this allows deactivating SCells while there is not traffic, and reduce the UE power consumption, and having the additional carrier more quickly available when the next traffic burst appears. The new SCG deactivation/activation mechanism allows keeping the NR SCG while saving UE power when the data traffic is lower and to activate the SCG again when needed due to increased traffic. This is also useful for bursty or variable data traffic. Conditional PSCell Change was introduced in Rel-16 but limited to intra-SN PSCell change. This WI is adding the support inter-SN Conditional PSCell Change, thus extending the benefits to wider areas. In addition, Conditional PSCell Addition is supported, so that a PSCell can be added as soon as allowed by radio conditions. Efficient SCell activation To enable fast SCell activation when Carrier Aggregation is configured, for each configured SCell, the network can configure a number of aperiodic CSI-RS for tracking for fast SCell activation. A new MAC Control Element (CE) that indicates SCell activation can indicate the aperiodic CSI-RS for tracking that is activated by the network to assist the UE for activation of the SCell. This aperiodic CSI-RS can be used to assist Automatic Gain Control (AGC) and time/frequency synchronization. SCG deactivation/activation SCG deactivation/activation applies to an NR SCG, in EN-DC and in NR-DC. UE behaviour while the SCG is deactivated When the SCG is deactivated, UE activities on the SCG are reduced:

• the UE does not transmit or receive any data via the SCG;
• the UE does not perform/report any physical layer measurements;
• all SCG SCells are deactivated.

However, other activities remain:

• if configured to do so, the UE performs radio link monitoring and beam failure detection on the PSCell
• the UE performs measurements for mobility, including measurements for SCG mobility configured by the SN;
• the UE can exchange RRC signalling with the SN via the MCG as in Rel-15 (e.g. to report SCG radio link/beam failure, mobility measurement results);
• in case of PSCell change, the UE does not perform random access towards the new PSCell if the SCG is to remain deactivated.

Data transmission while the SCG is deactivated When the SCG is deactivated:

• data can be transmitted or received via MCG bearers or via the MCG leg of split bearers;
• SCG bearers can remain configured;
• if there are uplink data to transmit on an SCG bearer, the UE indicates it to the network via RRC signalling.

SCG activation/deactivation The network activates or deactivates the SCG by sending an RRC reconfiguration message to the UE. For SCG activation, if the PSCell hasn't changed since the SCG deactivation, the timing advance is still valid and beam/radio link failure was not detected, it is possible to perform SCG activation without random access, i.e. the UE starts monitoring PDCCH and can receive downlink assignments and uplink grants. Otherwise, random access is necessary. On the network side, SCG activation and SCG deactivation is coordinated between the MN and the SN using the existing procedure for SN addition and SN modification. Both the MN and the SN can request SCG activation or SCG deactivation and the other node can accept or reject the request. Conditional PSCell Addition/Change From the UE perspective, inter-SN conditional PSCell change is very similar to intra-SN conditional PSCell change, with a few main differences:

• the conditional reconfiguration is received from the MCG;
• the conditional reconfiguration can include a reconfiguration of both MCG and SCG;
• the associated execution condition may refer to a conditional measurement configured by the MN (if initiated by the MN) or to a conditional measurement configured by the SN;
• at CPC execution, the UE indicates to the MN which conditional reconfiguration was applied.

On the network side, there are a number of new procedures. For instance, CPA and inter-SN CPC preparation requires exchanges between the MN, the SN and candidate target SN(s):

• the initiating node (MN or SN) indicates a list of candidate target PSCells and associated execution conditions;
• the MN provides this information to candidate target SN(s);
• candidate target SN(s) provide conditional reconfigurations for all or a subset of the candidate target PSCells;
• the MN transmits the conditional configurations to the UE, possibly with a MCG and SCG reconfiguration, as for any reconfiguration.

After CPA or CPC is prepared:

• the initiating node can request candidate target SNs to update their conditional reconfigurations according to a new UE configuration, or to release them;
• candidate target SN can initiate a modification or release already configured conditional reconfigurations.