Section: 5.3.5.13.8 Subsequent CPAC execution
Content: Upon the conditional reconfiguration execution for subsequent CPAC, the UE shall: 1> if the selected subsequent CPAC candidate configuration is stored in MCG VarConditionalReconfig: 2> release/clear all current dedicated radio configuration except for the following: - the MCG C-RNTI; - the AS security configurations associated with the master key and the secondary key; - for each SRB/DRB in current UE configuration: - keep the associated RLC, PDCP and SDAP entities, their state variables, buffers and timers; - release all fields related to the SRB/DRB configuration except for srb-Identity and drb-Identity; - the UE variables VarConditionalReconfig and VarServingSecurityCellSetID. 2> release/clear all current common radio configuration; 1> else: 2> release/clear all current dedicated radio configuration associated with the SCG except for the following: - the AS security configurations associated with the secondary key; - for each SRB/DRB in current UE configuration which is using the secondary key: - keep the associated RLC, PDCP and SDAP entities, their state variables, buffers and timers; - release all fields related to the SRB/DRB configuration except for srb-Identity and drb-Identity; - the UE variables VarConditionalReconfig. 2> release/clear all current common radio configuration associated with the SCG; 1> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311 for the cell group for which the subsequent CPAC cell switch procedure is triggered; 1> if the securityCellSetId is included in the entry in VarConditionalReconfig containing the RRCReconfiguration message: 2> if servingSecurityCellSetId is not included within VarServingSecurityCellSetID; or 2> if the value of the securityCellSetId is not equal to the value of servingSecurityCellSetId within VarServingSecurityCellSetID: 3> consider the first sk-Counter value in the sk-CounterList associated with the securityCellSetId within the VarConditionalReconfig as the selected sk-Counter value, and perform security key update procedure as specified in 5.3.5.7; 3> remove the selected sk-Counter value from the sk-CounterList associated with the securityCellSetId within the VarConditionalReconfig; 3> if the current VarServingSecurityCellSetID includes servingSecurityCellSetId: 4> replace the value of servingSecurityCellSetId within VarServingSecurityCellSetID with the value of securityCellSetId associated with the selected cell; 3> else: 4> store the servingSecurityCellSetId within VarServingSecurityCellSetID with the value of securityCellSetId associated with the selected cell; 1> if the selected subsequent CPAC candidate configuration is stored in the SCG VarConditionalReconfig: 2> for each drb-Identity value included in RadioBearerConfig associated with the secondary key (S-KgNB) as indicated by keyToUse that is part of the current UE configuration: 3> trigger the PDCP entity of the AM DRB to perform PDCP data recovery as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ]  [5]; 3> re-establish the corresponding RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ]  [4]; Editor's Note: FFS how the L2 reset (PDCP re-establishment, PDCP recovery, and RLC re-establishment) is indicated by the network in case of subsequent CPAC. 1> else: 2> for each drb-Identity value included in RadioBearerConfig that is part of the current UE configuration: 3> if a different keyToUse value is configured; or 3> if a new sk-Counter value has been selected due to the conditional reconfiguration execution for subsequent CPAC: 4> trigger the PDCP entity of the bearer to perform PDCP reestablishment as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ]  [5]; 3> else: 4> trigger the PDCP entity of the AM DRB to perform PDCP data recovery as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ]  [5]; 4> re-establish the corresponding RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ]  [4]; 1> if scpac-ConfigComplete is not included within the VarConditionalReconfig for the selected cell: 2> if the subsequent CPAC candidate cell configuration is stored in MCG VarConditionalReconfig: 3> consider scpac-ReferenceConfiguration in MCG VarConditionalReconfig to be the current UE configuration; 2> else: 3> consider scpac-ReferenceConfiguration in SCG VarConditionalReconfig to be the current SCG configuration; NOTE 1: When the UE considers the reference configuration to be the current UE configuration, the UE should store fields and configurations that are part of the reference configuration but should not execute any actions or procedures triggered by the reception of an RRCReconfiguration message which are described in clause 5.3.5.3. 1> apply the stored condRRCReconfig of the selected cell(s) and perform the actions as specified in 5.3.5.3; 1> release the radio bearer(s) and the associated logical channel(s) that are part of the current UE configuration but not part of the subsequent CPAC candidate configuration for the selected cell, or the subsequent CPAC reference configuration (in case the subsequent CPAC candidate configuration does not include scpac-ConfigComplete). NOTE 2: When scpac-ConfigComplete is not included for the selected cell, before a subsequent CPAC execution, a UE implementation may generate and store an RRC reconfiguration message by applying the received subsequent CPAC candidate configuration on top of the subsequent CPAC reference configuration, and the stored RRC reconfiguration message is applied for subsequent CPAC execution.