Section: 5.3.5.11 Full configuration
Content: The UE shall: 1> release/ clear all current dedicated radio configurations except for the following: - the MCG C-RNTI; - the AS security configurations associated with the master key; - the SRB1/SRB2 configurations and DRB/multicast MRB configurations as configured by radioBearerConfig or radioBearerConfig2. NOTE 1: Radio configuration is not just the resource configuration but includes other configurations like MeasConfig. Radio configuration also includes the RLC bearer configurations as configured by RLC-BearerConfig, PC5 Relay RLC channel as configured by SL-RLC-ChannelConfig, and Uu Relay RLC channel as configured by Uu-RelayRLC-ChannelConfig. In case NR-DC or NE-DC is configured, this also includes the entire NR or E-UTRA SCG configuration which are released according to the MR-DC release procedure as specified in 5.3.5.10. NOTE 1a: For NR sidelink communication/discovery, the radio configuration includes the sidelink RRC configuration received from the network, but does not include the sidelink RRC reconfiguration and sidelink UE capability received from other UEs via PC5-RRC. In addition, the UE considers the new NR sidelink configurations as full configuration, in case of state transition and change of system information used for NR sidelink communication/discovery. NOTE 1b: To establish the RLC bearer of SRB(s) after release due to fullConfig, the network can include the srb-Identity within srb-ToAddModList (i.e. the UE applies RLC default configuration) and/or provide rlc-BearerToAddModList of concerned SRB(s) explicitly. - the logged measurement configuration; 1> if the spCellConfig in the masterCellGroup includes the reconfigurationWithSync: 2> release/ clear all current common radio configurations; 2> if sl-PathSwitchConfig was included in reconfigurationWithSync: 3> use the default values specified in 9.2.3 for timer T311; 2> else: 3> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311; 1> else (full configuration after re-establishment or during RRC resume): 2> if the UE is acting as L2 U2N Remote UE: 3> use value for timer T311, as included in ue-TimersAndConstants received in SIB1 2> else: 3> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1; 1> if no measConfigAppLayerId is included: 2> inform upper layers about the release of all application layer measurement configurations; 2> discard any received application layer measurement report from upper layers; 2> consider itself not to be configured to send application layer measurement report. 1> if the UE is acting as L2 U2N Remote UE at the target side during reconfiguration with sync, or after re-establishment, or during RRC resume: 2> apply the default configuration of SL-RLC1 as specified in clause 9.2.4 and associate it with the SRB1; 1> else: 2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the following: - parameters for which values are provided in SIB1; 2> apply the default MAC Cell Group configuration as specified in 9.2.2; 2> for each srb-Identity value included in the srb-ToAddModList (SRB reconfiguration): 3> establish an RLC entity for the corresponding SRB; 3> apply the default SRB configuration defined in 9.2.1 for the corresponding SRB; NOTE 2: This is to get the SRBs (SRB1 and SRB2 for reconfiguration with sync and SRB2 for resume and reconfiguration after re-establishment) to a known state from which the reconfiguration message can do further configuration. 1> for each pdu-Session that is part of the current UE configuration: 2> release the SDAP entity (clause 5.1.2 in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ]  [24]); 2> release each DRB associated to the pdu-Session as specified in 5.3.5.6.4; NOTE 3: This will retain the pdu-Session but remove the DRBs including drb-identity of these bearers from the current UE configuration. Setup of the DRBs within the AS is described in clause 5.3.5.6.5 using the new configuration. The pdu-Session acts as the anchor for associating the released and re-setup DRB. In the AS the DRB re-setup is equivalent with a new DRB setup (including new PDCP and logical channel configurations). 1> for each mbs-SessionId that is part of the current UE configuration and associated to a multicast MRB: 2> release the SDAP entity (clause 5.1.2 in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ]  [24]); 2> release each multicast MRB associated to the mbs-SessionId as specified in 5.3.5.6.6; NOTE 4: This will retain the mbs-SessionId but remove the multicast MRBs including mrb-identity of these bearers from the current UE configuration. Setup of the multicast MRBs within the AS is described in clause 5.3.5.6.7 using the new configuration. The mbs-SessionId acts as the anchor for associating the released and re-setup multicast MRB. In the AS the multicast MRB re-setup is equivalent with a new multicast MRB setup (including new PDCP and logical channel configurations). 1> for each pdu-Session that is part of the current UE configuration but not added with same pdu-Session in the drb-ToAddModList: 2> if the procedure was triggered due to reconfiguration with sync: 3> indicate the release of the user plane resources for the pdu-Session to upper layers after successful reconfiguration with sync; 2> else: 3> indicate the release of the user plane resources for the pdu-Session to upper layers immediately; 1> for each mbs-SessionId that is part of the current UE configuration but not added with the same mbs-SessionId in the mrb-ToAddModList: 2> if the procedure was triggered due to reconfiguration with sync: 3> indicate the release of the user plane resources for the mbs-SessionId to upper layers after successful reconfiguration with sync; 2> else: 3> indicate the release of the user plane resources for the mbs-SessionId to upper layers immediately.