5.3.10 Radio resource configuration

36.3313GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Protocol specificationRadio Resource Control (RRC)Release 15TS

5.3.10.0 General

The UE shall:

1> if the received radioResourceConfigDedicated includes the srb-ToAddModList:

2> perform the SRB addition or reconfiguration as specified in 5.3.10.1;

1> if the received radioResourceConfigDedicated includes the drb-ToReleaseList:

2> perform DRB release as specified in 5.3.10.2;

1> if the received radioResourceConfigDedicated includes the drb-ToAddModList:

2> perform DRB addition or reconfiguration as specified in 5.3.10.3;

1> if the received radioResourceConfigDedicated includes the mac-MainConfig:

2> perform MAC main reconfiguration as specified in 5.3.10.4;

1> if the received radioResourceConfigDedicated includes sps-Config:

2> perform SPS reconfiguration according to 5.3.10.5;

1> if the received radioResourceConfigDedicated includes the physicalConfigDedicated:

2> reconfigure the physical channel configuration as specified in 5.3.10.6.

1> if the received radioResourceConfigDedicated includes the rlf-TimersAndConstants:

2> reconfigure the values of timers and constants as specified in 5.3.10.7;

1> if the received radioResourceConfigDedicated includes the measSubframePatternPCell:

2> reconfigure the time domain measurement resource restriction for the serving cell as specified in 5.3.10.8;

1> if the received radioResourceConfigDedicated includes the naics-Info:

2> perform NAICS neighbour cell information reconfiguration for the PCell as specified in 5.3.10.13;

1> if the received RadioResourceConfigDedicatedPSCell includes the naics-Info:

2> perform NAICS neighbour cell information reconfiguration for the PSCell as specified in 5.3.10.13;

1> if the received RadioResourceConfigDedicatedSCell-r10 includes the naics-Info:

2> perform NAICS neighbour cell information reconfiguration for the SCell as specified in 5.3.10.13;

1> if the received radioResourceConfigDedicated includes the srb-ToReleaseList:

2> perform SRB release as specified in 5.3.10.17;

1> if the received radioResourceConfigDedicated includes the schedulingRequestConfig:

2> perform scheduling request reconfiguration for the SCell as specified in 5.3.10.18.

5.3.10.1 SRB addition/ modification

The UE shall:

1> if the UE is a NB-IoT UE and SRB1 is not established; or

1> for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration (SRB establishment):

2> if the UE is not a NB-IoT UE that only supports the Control Plane CIoT EPS optimisation:

3> apply the specified configuration defined in 9.1.2 for the corresponding SRB;

3> establish a primary (MCG) RLC entity in accordance with the received rlc-Config;

3> establish a primary (MCG) DCCH logical channel in accordance with the received logicalChannelConfig and with the logical channel identity set in accordance with 9.1.2;

3> if the same srb-Identity is included in NR srb-ToAddModList:

4> after processing nr-RadioBearerConfig1 and nr-RadioBearerConfig2 if present in the RRCConnectionReconfiguration message which triggered the execution of the SRB addition/modification procedure, associate MCG RLC bearer with the NR PDCP entity associated with the same value of srb-Identity in the current UE configuraton as specified in TS 38.331 [82];

3> else:

4> establish a PDCP entity and configure it with the current (MCG) security configuration, if applicable;

3> if rlc-BearerConfigSecondary is received with value setup:

4> establish a secondary MCG RLC entity or entities and an associated DCCH logical channel in accordance with the received rlc-BearerConfigSecondary and associate these with the E-UTRA PDCP entity with the same value of srb-Identity within the current UE configuration;

4> configure the E-UTRA PDCP entity to activate duplication with t-Reordering set to infinity;

2> if the UE is a NB-IoT UE:

3> apply the specified configuration defined in 9.1.2 for SRB1bis;

3> establish an (MCG) RLC entity in accordance with the received rlc-Config;

3> establish a (MCG) DCCH logical channel in accordance with the received logicalChannelConfig and with the logical channel identity set in accordance with 9.1.2.1a;

1> if the UE is a NB-IoT UE and SRB1 is established; or

1> for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration (SRB reconfiguration):

2> if pdcp-verChange is included (i.e, NR PDCP to E-UTRA PDCP change):

3> establish an (E-UTRA) PDCP entity and configure it with the current (MCG) security configuration;

NOTE: The UE applies the LTE ciphering and integrity protection algorithms that are equivalent to the previously configured NR security algorithms.

3> associate the primary RLC bearer of this SRB with the established PDCP entity;

3> release the NR PDCP entity of this SRB;

2> reconfigure the primary RLC entity in accordance with the received rlc-Config;

2> reconfigure the primary DCCH logical channel in accordance with the received logicalChannelConfig;

2> if rlc-BearerConfigSecondary is included with value release:

3> release the secondary MCG RLC entity or entities as well as the associated DCCH logical channel;

2> if rlc-BearerConfigSecondary is received with value setup:

3> if the current SRB configuration does not include a secondary RLC bearer:

4> establish a secondary MCG RLC entity or entities and an associated DCCH logical channel in accordance with the received rlc-BearerConfigSecondary and associate these with the E-UTRA PDCP entity with the same value of srb-Identity within the current UE configuration;

4> configure the E-UTRA PDCP entity to activate duplication with t-Reordering set to infinity;

3> else:

4> reconfigure the secondary MCG RLC entity or entities and the associated DCCH logical channel in accordance with the received rlc-BearerConfigSecondary;

5.3.10.1a SCG RLC bearer addition or reconfiguration for SRBs

The UE shall:

1> for each srb-Identity value included in the srb-ToAddModListSCG that is not part of the current UE E-UTRA SCG configuration (i.e. SCG RLC bearer establishment):

2> apply the specified configuration defined in 9.1.2 for the corresponding SRB;

2> establish an (SCG) RLC entity in accordance with the received rlc-Config;

2> establish a (SCG) DCCH logical channel in accordance with the received logicalChannelConfig and with the logical channel identity set in accordance with 9.1.2;

2> if the UE is configured with DC:

3> associate the established SCG RLC bearer and DCCH logical channel with the E-UTRA PDCP entity with the same value of srb-Identity within the current UE configuration;

3> configure the E-UTRA PDCP entity to activate duplication with t-Reordering set to infinity;

2> else (i.e. the UE is configured with NE-DC):

3> associate the SCG RLC bearer and DCCH logical channel with the NR PDCP entity, i.e. as configured by NR see TS 38.331 [82], identified with the same srb-Identity within the current UE configuration;

1> for each srb-Identity value included in the srb-ToAddModListSCG that is part of the current UE SCG configuration (SCG RLC bearer reconfiguration):

2> re-establish the SCG RLC entity, if reestablishRLC is included;

2> reconfigure the RLC entity in accordance with the received rlc-Config;

2> reconfigure the DCCH logical channel in accordance with the received logicalChannelConfig;

5.3.10.2 DRB release

The UE shall:

1> for each drb-Identity value included in the drb-ToReleaseList or drb-ToReleaseListSCG that is part of the current UE configuration (DRB or RLC bearer release); or

1> for each drb-identity value that is to be released as the result of full configuration option according to 5.3.5.8:

2> if release of this DRB is result of full configuration option according to 5.3.5.8:

3> release the E-UTRA or NR PDCP entity;

2> else if this DRB is configured with pdcp-config:

3> release the E-UTRA PDCP entity;

2> else (release the RLC bearer configuration of MCG or of SCG):

3> re-establish the RLC entity as specified in 36.322 for this DRB;

2> release the RLC entity or entities;

2> release the DTCH logical channel;

2> if the UE is connected to EPC:

3> if the DRB was configured with pdcp-config and new DRB is not added with same eps-BearerIdentity in drb-ToAddModList nor nr-radioBearerConfig1 nor in nr-radioBearerConfig2:

4> if the procedure was triggered due to handover:

5> indicate the release of the DRB and the eps-BearerIdentity of the released DRB to upper layers after successful handover;

4> else:

5> indicate the release of the DRB and the eps-BearerIdentity of the released DRB to upper layers immediately.

NOTE 1: The UE does not consider the message as erroneous if the drb-ToReleaseList includes any drb-Identity value that is not part of the current UE configuration.

NOTE 2: The association of eps-BearerIdentity to an NR PDCP configuration as defined in TS 38.331 [82] can be included in the same message that releases an DRB associated to the same eps-BearerIdentity.

5.3.10.3 DRB addition/ modification

The UE shall:

1> for each drb-Identity value included in the drb-ToAddModList that is not part of the current UE configuration (DRB establishment including the case when full configuration option is used):

2> if the concerned entry of drb-ToAddModList includes the drb-TypeLWA set to TRUE (i.e. add LWA DRB):

3> perform the LWA specific DRB addition or reconfiguration as specified in 5.3.10.3a2;

2> if the concerned entry of drb-ToAddModList includes the drb-TypeLWIP (i.e. add LWIP DRB):

3> perform LWIP specific DRB addition or reconfiguration as specified in 5.3.10.3a3;

2> else if drb-ToAddModListSCG is not received or does not include the drb-Identity value (i.e. add MCG DRB or MCG RLC bearer):

3> if pdcp-Config is received, establish a PDCP entity and configure it with the current MCG security configuration and in accordance with the received pdcp-Config;

3> if rlc-Config is received, establish a (primary) MCG RLC entity or entities in accordance with the received rlc-Config;

3> if logicalChannelIdentity and logicalChannelConfig are received, establish a (primary) MCG DTCH logical channel in accordance with the received logicalChannelIdentity and the received logicalChannelConfig;

3> if rlc-BearerConfigSecondary is received with value setup:

4> establish a secondary MCG RLC entity or entities and an associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary and associate these with the E-UTRA PDCP entity with the same value of drb-Identity within the current UE configuration;

3> if pdcp-Config is not received, after processing nr-RadioBearerConfig1 and nr-RadioBearerConfig2 if present in the RRCConnectionReconfiguration message which triggered the execution of the DRB addition/modification procedure, associate MCG RLC bearer with the NR PDCP entity associated with the same value of drb-Identity in the current UE configuration as specified in TS 38.331 [82];

2> if a DRB was configured with the same eps-BearerIdentity (fullConfig or change to E-UTRA PDCP):

3> associate the established DRB with corresponding included eps-BearerIdentity;

2> else if the entry of drb-ToAddModList includes pdcp-config (establishment of bearer with E-UTRA PDCP):

3> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;

1> for each drb-Identity value included in the drb-ToAddModList that is part of the current UE configuration (DRB reconfiguration):

2> if the DRB indicated by drb-Identity is an LWA DRB (i.e. LWA to LTE only or reconfigure LWA DRB):

3> perform the LWA specific DRB reconfiguration as specified in 5.3.10.3a2;

2> else if the concerned entry of drb-ToAddModList includes the drb-TypeLWA set to TRUE (i.e. LTE only to LWA DRB):

3> perform the LWA specific DRB reconfiguration as specified in 5.3.10.3a2;

2> if the concerned entry of drb-ToAddModList includes the drb-TypeLWIP (i.e. add or reconfigure LWIP DRB):

3> perform LWIP specific DRB addition or reconfiguration as specified in 5.3.10.3a3;

2> if drb-ToAddModListSCG is not received or does not include the drb-Identity value:

3> if the DRB indicated by drb-Identity is an MCG DRB or configured with MCG RLC bearer (reconfigure MCG RLC bearer or reconfigure MCG DRB):

4> if the pdcp-Config is included:

5> reconfigure the PDCP entity in accordance with the received pdcp-Config;

4> if the rlc-Config is included:

5> if reestablishRLC is received:

6> re-establish the primary RLC entity of this DRB;

6> if the logicalChannelIdentity is included and the DRB indicated by drb-Identity is configured with MCG RLC bearer (reconfigure logical channel identity of MCG RLC bearer):

7> reconfigure the primary DTCH logical channel identity in accordance with the received logicalChannelIdentity;

5> reconfigure the primary RLC entity or entities in accordance with the received rlc-Config;

4> if the logicalChannelConfig is included:

5> reconfigure the primary DTCH logical channel in accordance with the received logicalChannelConfig;

4> if rlc-BearerConfigSecondary is included with value release:

5> release the secondary MCG RLC entity or entities as well as the associated DTCH logical channel;

4> if rlc-BearerConfigSecondary is included with value setup;

5> if the current DRB configuration does not include a secondary RLC bearer:

6> establish a secondary MCG RLC entity or entities and an associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary and associate these with the E-UTRA PDCP entity with the same value of drb-Identity within the current UE configuration;

5> else:

6> reconfigure the secondary MCG RLC entity or entities and the associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary;

NOTE: Removal and addition of DRB with pdcp-Config with the same drb-Identity in a single radioResourceConfigDedicated is not supported. In case drb-Identity is removed and added due to handover or re-establishment with the full configuration option, the eNB can use the same value of drb-Identity.

5.3.10.3a1 DC specific DRB addition or reconfiguration

For the drb-Identity value for which this procedure is initiated, the UE shall:

1> if drb-ToAddModListSCG is received and includes the drb-Identity value; and drb-Identity value is not part of the current UE configuration (i.e. DC specific DRB establishment):

2> if drb-ToAddModList is received and includes the drb-Identity value (i.e. add split DRB):

3> establish a PDCP entity and configure it with the current MCG security configuration and in accordance with the pdcp-Config included in drb-ToAddModList;

3> establish an MCG RLC entity and an MCG DTCH logical channel in accordance with the rlc-Config, logicalChannelIdentity and logicalChannelConfig included in drb-ToAddModList;

3> establish an SCG RLC entity and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG included in drb-ToAddModListSCG;

2> else (i.e. add SCG DRB):

3> establish a PDCP entity and configure it with the current SCG security configuration and in accordance with the pdcp-Config included in drb-ToAddModListSCG;

3> establish a primary SCG RLC entity or entities and a primary SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG included in drb-ToAddModListSCG;

3> if rlc-BearerConfigSecondary is included with value setup;

4> establish a secondary SCG RLC entity or entities and an associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary and associate these with the E-UTRA PDCP entity with the same value of srb-Identity within the current UE configuration;

2> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;

1> else (i.e. DC specific DRB modification; drb-ToAddModList and/ or drb-ToAddModListSCG received):

2> if the DRB indicated by drb-Identity is a split DRB:

3> if drb-ToAddModList is received and includes the drb-Identity value, while for this entry drb-TypeChange is included and set to toMCG (i.e. split to MCG):

4> release the SCG RLC entity or entities and the SCG DTCH logical channel(s);

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the primary MCG RLC entity and/ or the primary MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

4> if rlc-BearerConfigSecondary is included with value setup;

5> establish a secondary MCG RLC entity or entities and an associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary and associate these with the E-UTRA PDCP entity with the same value of srb-Identity within the current UE configuration;

3> else (i.e. reconfigure split):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the MCG RLC entity and/ or the MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

4> reconfigure the SCG RLC entity and/ or the SCG DTCH logical channel in accordance with the rlc-ConfigSCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

2> if the DRB indicated by drb-Identity is an SCG DRB:

3> if drb-ToAddModList is received and includes the drb-Identity value, while for this entry drb-TypeChange is included and set to toMCG (i.e. SCG to MCG):

4> reconfigure the PDCP entity with the current MCG security configuration and in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the SCG RLC entity or entities (both primary and secondary, if configured) and the SCG DTCH logical channel (both primary and secondary, if configured) to be an MCG RLC entity or entities and an MCG DTCH logical channel;

4> reconfigure the primary MCG RLC entity or entities and/ or the primary MCG DTCH logical channel in accordance with the rlc-Config, logicalChannelIdentity and logicalChannelConfig, if included in drb-ToAddModList;

4> if rlc-BearerConfigSecondary is included with value release:

5> release the secondary MCG RLC entity or entities as well as the associated DTCH logical channel;

4> if rlc-BearerConfigSecondary is included with value setup;

5> if the current DRB configuration does not include a secondary RLC bearer:

6> establish a secondary MCG RLC entity or entities and an associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary and associate these with the E-UTRA PDCP entity with the same value of srb-Identity within the current UE configuration;

5> else:

6> reconfigure the secondary MCG RLC entity or entities and the associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary;

3> else (i.e. drb-ToAddModListSCG is received and includes the drb-Identity value i.e. reconfigure SCG):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModListSCG;

4> reconfigure the primary SCG RLC entity or entities and/ or the primary SCG DTCH logical channel in accordance with the rlc-ConfigSCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

4> if rlc-BearerConfigSecondary is included with value release:

5> release the secondary SCG RLC entity or entities as well as the associated DTCH logical channel;

4> if rlc-BearerConfigSecondary is included with value setup;

5> if the current DRB configuration does not include a secondary RLC bearer:

6> establish a secondary SCG RLC entity or entities and an associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary and associate these with the E-UTRA PDCP entity with the same value of srb-Identity within the current UE configuration;

5> else:

6> reconfigure the secondary SCG RLC entity or entities and the associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary;

2> if the DRB indicated by drb-Identity is an MCG DRB:

3> if drb-ToAddModListSCG is received and includes the drb-Identity value, while for this entry drb-Type is included and set to split (i.e. MCG to split):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the primary MCG RLC entity and/ or the primary MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

4> if rlc-BearerConfigSecondary is included with value release:

5> release the secondary MCG RLC entity or entities as well as the associated DTCH logical channel;

4> establish an SCG RLC entity and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG, included in drb-ToAddModListSCG;

3> else (i.e. drb-Type is included and set to scg i.e. MCG to SCG):

4> reconfigure the PDCP entity with the current SCG security configuration and in accordance with the pdcp-Config, if included in drb-ToAddModListSCG;

4> reconfigure the MCG RLC entity or entities (both primary and secondary, if configured) and the MCG DTCH logical channel (both primary and secondary, if configured) to be an SCG RLC entity or entities and an SCG DTCH logical channel;

4> reconfigure the primary SCG RLC entity or entities and/ or the primary SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

4> if rlc-BearerConfigSecondary is included with value release:

5> release the secondary SCG RLC entity or entities as well as the associated DTCH logical channel;

4> if rlc-BearerConfigSecondary is included with value setup;

5> if the current DRB configuration does not include a secondary RLC bearer:

6> establish a secondary SCG RLC entity or entities and an associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary and associate these with the E-UTRA PDCP entity with the same value of srb-Identity within the current UE configuration;

5> else:

6> reconfigure the secondary SCG RLC entity or entities and the associated DTCH logical channel in accordance with the received rlc-BearerConfigSecondary;

5.3.10.3a2 LWA specific DRB addition or reconfiguration

For the drb-Identity value for which this procedure is initiated, the UE shall:

1> if the drb-Identity value is not part of the current UE configuration (i.e. add LWA DRB):

2> establish a PDCP entity and configure it with the current security configuration and in accordance with the pdcp-Config included in drb-ToAddModList;

2> establish an RLC entity and an DTCH logical channel in accordance with the rlc-Config, logicalChannelIdentity and logicalChannelConfig included in drb-ToAddModList;

2> enable data handling for this DRB at the LWAAP entity;

2> if lwa-WLAN-AC is configured:

3> apply the received lwa-WLAN-AC when performing transmissions of packets for this DRB over WLAN;

2> indicate the establishment of the DRB and the eps-BearerIdentity of the established DRB to upper layers;

1> else if the DRB indicated by drb-Identity is not an LWA DRB (i.e. LTE only to LWA DRB):

2> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

2> reconfigure the RLC entity and/ or the DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

2> enable data handling for this DRB at the LWAAP entity;

2> if lwa-WLAN-AC is configured:

3> apply the received lwa-WLAN-AC when performing transmissions of packets for this DRB over WLAN;

1> else if the concerned entry of drb-ToAddModList includes the drb-TypeLWA set to FALSE (i.e. LWA to LTE only DRB):

2> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

2> reconfigure the RLC entity and/ or the DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

2> perform PDCP data recovery as specified in TS 36.323 [8] if bearer is configured with RLC AM;

2> disable data handling for this DRB at the LWAAP entity;

1> else (i.e. reconfigure LWA DRB):

2> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

2> reconfigure the RLC entity and/ or the DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

2> if lwa-WLAN-AC is configured:

3>apply the received lwa-WLAN-AC when performing transmissions of packets for this DRB over WLAN;

5.3.10.3a3 LWIP specific DRB addition or reconfiguration

For the drb-Identity value for which this procedure is initiated, the UE shall:

1> if the drb-TypeLWIP is set to lwip:

2> indicate to higher layers to use LWIP resources in both UL and DL for the DRB associated with the drb-Identity;

2> if lwip-DL-Aggregation is set to TRUE:

3> indicate to higher layers to apply decoding of LWIPEP header with GRE sequence number for both LTE and WLAN DL reception for the DRB associated with the drb-Identity;

2> if lwip-DL-Aggregation is set to FALSE:

3> indicate to higher layers to stop decoding of LWIPEP header with GRE sequence number for both LTE and WLAN DL reception for the DRB associated with the drb-Identity;

2> if lwip-UL-Aggregation is set to TRUE:

3> indicate to higher layers to insert LWIPEP header with GRE sequence number for both LTE and WLAN UL transmissions for the DRB associated with the drb-Identity;

2> if lwip-UL-Aggregation is set to FALSE:

3> indicate to higher layers to stop inserting LWIPEP header with GRE sequence number for both LTE and WLAN UL transmissions for the DRB associated with the drb-Identity;

1> if the drb-TypeLWIP is set to lwip-DL-only:

2> indicate to higher layers to use LWIP resources in the DL only for the DRB associated with the drb-Identity;

2> if lwip-DL-Aggregation is set to TRUE:

3> indicate to higher layers to apply decoding of LWIPEP header with GRE sequence number for both LTE and WLAN DL reception for the DRB associated with the drb-Identity;

1> if the drb-TypeLWIP is set to lwip-UL-only:

2> indicate to higher layers to use LWIP resources in the UL only for the DRB associated with the drb-Identity;

2> if lwip-UL-Aggregation is set to TRUE:

3> indicate to higher layers to insert LWIPEP header with GRE sequence number for both LTE and WLAN UL transmissions for the DRB associated with the drb-Identity;

1> if the drb-TypeLWIP is set to eutran:

2> indicate to higher layers to stop using LWIP resources for the DRB associated with the drb-Identity;

5.3.10.3a4 SCG RLC bearer addition or reconfiguration for DRBs in NE-DC

The UE shall:

1> for each drb-Identity value included in drb-ToAddModListSCG:

2> if drb-Identity value is not part of the current UE E-UTRA SCG configuration (SCG RLC bearer establishment):

3> establish an SCG RLC entity or entities and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG included in drb-ToAddModListSCG;

3> associate the SCG RLC bearer and DTCH logical channel with the NR PDCP entity, i.e. as configured by NR see TS 38.331 [82], identified with the same drb-Identity within the current UE configuration;

2> else:

3> re-establish the SCG RLC entity of this DRB, if reestablishRLC is included in rlc-Config;

3> reconfigure the SCG RLC entity or entities and/ or the SCG DTCH logical channel in accordance with the rlc-ConfigSCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

5.3.10.3a SCell release

The UE shall:

1> if the release is triggered by reception of the sCellToReleaseList or the sCellToReleaseListSCG:

2> for each sCellIndex value included either in the sCellToReleaseList or in the sCellToReleaseListSCG:

3> if the current UE configuration includes an SCell with value sCellIndex:

4> release the SCell;

1> if the release is triggered by RRC connection re-establishment; or

1> if the release is triggered when the UE is resuming an RRC connection from a suspended RRC connection or from RRC_INACTIVE as specified in clause 5.3.3.2:

2> release all SCells that are part of the current UE configuration;

5.3.10.3b SCell addition/ modification

The UE shall:

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell, both included either in the sCellToAddModList or in the sCellToAddModListSCG;

2> if sCellState is configured for the SCell and indicates activated:

3> configure lower layers to consider the SCell to be in activated state;

2> else if sCellState is configured for the SCell and indicates dormant:

3> configure lower layers to consider the SCell to be in dormant state;

2> else:

3> configure lower layers to consider the SCell to be in deactivated state;

2> for each measId included in the measIdList within VarMeasConfig:

3> if SCells are not applicable for the associated measurement; and

3> if the concerned SCell is included in cellsTriggeredList defined within the VarMeasReportList for this measId:

4> remove the concerned SCell from cellsTriggeredList defined within the VarMeasReportList for this measId;

1> for each sCellIndex value included either in the sCellToAddModList or in the sCellToAddModListSCG that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the radioResourceConfigDedicatedSCell, included either in the sCellToAddModList or in the sCellToAddModListSCG;

5.3.10.3c PSCell addition or modification

The UE shall:

1> if the PSCell is not part of the current UE configuration (i.e. PSCell addition):

2> add the PSCell, corresponding to the cellIdentification, in accordance with the received radioResourceConfigCommonPSCell and radioResourceConfigDedicatedPSCell;

2> configure lower layers to consider the PSCell to be in activated state;

1> if the PSCell is part of the current UE configuration (i.e. PSCell modification):

2> modify the PSCell configuration in accordance with the received radioResourceConfigDedicatedPSCell;

5.3.10.3d SCell group release

The UE shall:

1> if the release is triggered by reception of the sCellGroupToReleaseList:

2> for each sCellGroupIndex value included in the sCellGroupToReleaseList:

3> if the current UE configuration includes an SCell with value sCellGroupIndex:

4> consider the SCell not to be part of the SCell group indicated by sCellGroupIndex;

4> consider the sCellConfigCommon of the SCell group to be not applicable for the SCell;

3> release the SCell group;

1> if the release is triggered by RRC connection re-establishment:

2> release all SCell groups that are part of the current UE configuration;

5.3.10.3e SCell group addition/ modification

The UE shall:

1> for each sCellGroupIndex value included in the sCellGroupToAddModList that is part of the current UE configuration (SCell group modification):

2> for each sCellIndex value included in the sCellToReleaseList that is part of the SCell group indicated by sCellGroupIndex (SCell deletion from SCell group):

3> consider the sCellConfigCommon of the SCell group to be not applicable for the SCell;

3> consider the SCell not to be part of the SCell group indicated by sCellGroupIndex

2> for each sCellIndex value included in the sCellToAddModList that is not part of the SCell group indicated by sCellGroupIndex (SCell addition to SCell group):

3> consider the SCell to be part of the SCell group indicated by sCellGroupIndex;

3> apply the SCell configuration for parameters not already configured as part of the current SCell configuration in accordance with the sCellConfigCommon for the SCell group;

2> if sCellConfigCommon is included (modify the SCell group configuration):

3> for each SCell that is part of the current SCell group indicated by sCellGroupIndex:

4> apply the SCell configuration for parameters not already configured as part of the current SCell configuration in accordance with the sCellConfigCommon for the SCell group;

1> for each sCellGroupIndex value included in the sCellGroupToAddModList that is not part of the current UE configuration (SCell group addition):

2> for each sCellIndex value included in the sCellToAddModList (SCell addition to the group):

3> consider the SCell to be part of the SCell group indicated by sCellGroupIndex

3> apply the SCell configuration for parameters not already configured as part of the current SCell configuration in accordance with the sCellConfigCommon for the SCell group;

5.3.10.4 MAC main reconfiguration

Except for NB-IoT, the UE shall:

1> if the procedure is triggered to perform SCG MAC main reconfiguration:

2> if SCG MAC is not part of the current UE configuration (i.e. SCG establishment):

3> create an SCG MAC entity;

2> reconfigure the SCG MAC main configuration as specified in the following i.e. assuming it concerns the SCG MAC whenever MAC main configuration is referenced and that it is based on the received mac-MainConfigSCG instead of mac-MainConfig:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig other than stag-ToReleaseList and stag-ToAddModList;

1> if the received mac-MainConfig includes the stag-ToReleaseList:

2> for each STAG-Id value included in the stag-ToReleaseList that is part of the current UE configuration:

3> release the STAG indicated by STAG-Id;

1> if the received mac-MainConfig includes the stag-ToAddModList:

2> for each stag-Id value included in stag-ToAddModList that is not part of the current UE configuration (STAG addition):

3> add the STAG, corresponding to the stag-Id, in accordance with the received timeAlignmentTimerSTAG;

2> for each stag-Id value included in stag-ToAddModList that is part of the current UE configuration (STAG modification):

3> reconfigure the STAG, corresponding to the stag-Id, in accordance with the received timeAlignmentTimerSTAG;

For NB-IoT, the UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

5.3.10.5 Semi-persistent scheduling reconfiguration

The UE shall:

1> reconfigure the semi-persistent scheduling in accordance with the received sps-Config;

5.3.10.6 Physical channel reconfiguration

Except for NB-IoT, the UE shall:

1> if the antennaInfo-r10 is included in the received physicalConfigDedicated and the previous version of this field that was received by the UE was antennaInfo (without suffix i.e. the version defined in REL-8):

2> apply the default antenna configuration as specified in 9.2.4;

1> if the cqi-ReportConfig-r10 is included in the received physicalConfigDedicated and the previous version of this field that was received by the UE was cqi-ReportConfig (without suffix i.e. the version defined in REL-8):

2> apply the default CQI reporting configuration as specified in 9.2.4;

NOTE: Application of the default configuration involves release of all extensions introduced in REL-9 and later.

1> reconfigure the physical channel configuration in accordance with the received physicalConfigDedicated;

1> if the antennaInfo is included and set to explicitValue:

2> if the configured transmissionMode is tm1, tm2, tm5, tm6 or tm7; or

2> if the configured transmissionMode is tm8 and pmi-RI-Report is not present; or

2> if the configured transmissionMode is tm9 and pmi-RI-Report is not present; or

2> if the configured transmissionMode is tm9 and pmi-RI-Report is present and antennaPortsCount within csi-RS is set to an1:

3> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to defaultValue:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> if the pusch-EnhancementsConfig is included in the received physicalConfigDedicated, for the associated serving cell:

2> if PUSCH enhancement mode is previously released or not configured and pusch-EnhancementsConfig is set to setup, or

2> if PUSCH enhancement mode is previously configured and pusch-EnhancementConfig is set to release:

3> instruct the associated MAC entity to perform partial reset;

1> if the procedure was not triggered due to handover and ce-Mode is included in the received physicalConfigDedicated, for the associated serving cell:

2> if ce-Mode is not currently configured and ce-Mode is set to setup, or

2> if ce-Mode is currently configured and ce-Mode is set to release:

3> instruct the associated MAC entity to perform partial reset;

For NB-IoT, the UE shall:

1> if the carrierConfigDedicated is not included in the received physicalConfigDedicated:

2> if the UE is configured with a carrier configuration previously received in carrierConfigDedicated:

3> use the carrier configuration received in carrierConfigDedicated;

2> else:

3> use the carrier configuration received in system information for the uplink and downlink carrier used during the random access procedure;

1> else:

2> use the carrier configuration received in carrierConfigDedicated;

2> start to use the new carrier immediately after the last transport block carrying the RRC message has been acknowledged by the MAC layer, and any subsequent RRC response message sent for the current RRC procedure is therefore sent on the new carrier;

1> reconfigure the physical channel configuration in accordance with the received physicalConfigDedicated.

5.3.10.7 Radio Link Failure Timers and Constants reconfiguration

The UE shall:

1> if the received rlf-TimersAndConstants is set to release:

2> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SystemInformationBlockType2 (or SystemInformationBlockType2-NB in NB-IoT);

1> else:

2> reconfigure the value of timers and constants in accordance with received rlf-TimersAndConstants;

1> if the received rlf-TimersAndConstantsSCG is set to release:

2> stop timer T313, if running, and

2> release the value of timer t313 as well as constants n313 and n314;

1> else:

2> reconfigure the value of timers and constants in accordance with received rlf-TimersAndConstantsSCG;

5.3.10.8 Time domain measurement resource restriction for serving cell

The UE shall:

1> if the received measSubframePatternPCell is set to release:

2> release the time domain measurement resource restriction for the PCell, if previously configured;

1> else:

2> apply the time domain measurement resource restriction for the PCell in accordance with the received measSubframePatternPCell;

5.3.10.9 Other configuration

The UE shall:

1> if the received otherConfig includes the reportProximityConfig:

2> if proximityIndicationEUTRA is set to enabled:

3> consider itself to be configured to provide proximity indications for E-UTRA frequencies in accordance with 5.3.14;

2> else:

3> consider itself not to be configured to provide proximity indications for E-UTRA frequencies;

2> if proximityIndicationUTRA is set to enabled:

3> consider itself to be configured to provide proximity indications for UTRA frequencies in accordance with 5.3.14;

2> else:

3> consider itself not to be configured to provide proximity indications for UTRA frequencies;

1> if the received otherConfig includes the obtainLocation:

2> attempt to have detailed location information available for any subsequent measurement report;

NOTE 1: The UE is requested to attempt to have valid detailed location information available whenever sending a measurement report for which it is configured to include available detailed location information. The UE may not succeed e.g. because the user manually disabled the GPS hardware, due to no/poor satellite coverage. Further details, e.g. regarding when to activate GNSS, are up to UE implementation.

1> if the received otherConfig includes the bt-NameListConfig:

2> if bt-NameListConfig is set to setup, attempt to have Bluetooth measurement results available for subsequent measurement report;

1> if the received otherConfig includes the wlan-NameListConfig:

2> if wlan-NameListConfig is set to setup, attempt to have WLAN measurement results available for subsequent measurement report;

NOTE 2: The UE is requested to attempt to have valid Bluetooth measurements and WLAN measurements whenever sending a measurement report for which it is configured to include these measurements. The UE may not succeed e.g. because the user manually disabled the WLAN or Bluetooth hardware. Further details, e.g. regarding when to activate WLAN or Bluetooth, are up to UE implementation.

1> if the received otherConfig includes the idc-Config:

2> if idc-Indication is included (i.e. set to setup):

3> consider itself to be configured to provide IDC indications in accordance with 5.6.9;

3> if idc-Indication-UL-CA is included (i.e. set to setup):

4> consider itself to be configured to indicate UL CA related information in IDC indications in accordance with 5.6.9;

3> if idc-HardwareSharingIndication is included (i.e. set to setup):

4> consider itself to be configured to indicate IDC hardware sharing problem indications in IDC indications in accordance with 5.6.9;

3> if idc-Indication-MRDC is included (i.e. set to setup):

4> consider itself to be configured to provide IDC indications for MR-DC in accordance with 5.6.9;

2> else:

3> consider itself not to be configured to provide IDC indications;

2> if autonomousDenialParameters is included:

3> consider itself to be allowed to deny any transmission in a particular UL subframe if during the number of subframes indicated by autonomousDenialValidity, preceeding and including this particular subframe, it autonomously denied fewer UL subframes than indicated by autonomousDenialSubframes;

2> else:

3> consider itself not to be allowed to deny any UL transmission;

1> if the received otherConfig includes the powerPrefIndicationConfig:

2> if powerPrefIndicationConfig is set to setup:

3> consider itself to be configured to provide power preference indications in accordance with 5.6.10;

2> else:

3> consider itself not to be configured to provide power preference indications;

1> if the received otherConfig includes the sps-AssistanceInfoReport:

2> if sps-AssistanceInfoReport is set to TRUE:

3> consider itself to be configured to provide SPS assistance information in accordance with 5.6.10;

2> else

3> consider itself not to be configured to provide SPS assistance information;

1> if the received otherConfig includes the bw-PreferenceIndicationTimer:

2> consider itself to be configured to provide maximum PDSCH/PUSCH bandwidth preference indication in accordance with 5.6.10;

1> else:

2> consider itself not to be configured to provide maximum PDSCH/PUSCH bandwidth indication preference;

1> if the received otherConfig includes the delayBudgetReportingConfig:

2> if delayBudgetReportingConfig is set to setup:

3> consider itself to be configured to send delay budget reports in accordance with 5.6.10;

2> else:

3> consider itself not to be configured to send delay budget reports and stop timer T342, if running;

1> if the received otherConfig includes the overheatingAssistanceConfig:

2> if overheatingAssistanceConfig is set to setup:

3> consider itself to be configured to provide overheating assistance information in accordance with 5.6.10;

2> else:

3> consider itself not to be configured to provide overheating assistance information and stop timer T345, if running;

1> for BL UEs or UEs in CE, if the received otherConfig includes the rlm-ReportConfig:

2> if rlm-ReportConfig is set to setup:

3> consider itself to be configured to detect "early-out-of-sync" and "early-in-sync" RLM events as specified in 5.3.11;

3> if rlmReportRep-MPDCCH is set to setup:

4> consider itself to be configured to report rlmReportRep-MPDCCH in accordance with 5.6.10;

2> else:

3> consider itself not to be configured to detect "early-out-of-sync" and "early-in-sync" RLM events and stop timer T343, timer T344, timer T314 and timer T315 if running;

1> if the received otherConfig includes the measConfigAppLayer:

2> if measConfigAppLayer is set to setup:

3> forward measConfigAppLayerContainer to upper layers considering the serviceType;

3> consider itself to be configured to send application layer measurement report in accordance with 5.6.19;

2> else:

3> inform upper layers to clear the stored application layer measurement configuration;

3> discard received application layer measurement report information from upper layers;

3> consider itself not to be configured to send application layer measurement report.

1> if the received otherConfig includes the ailc-BitConfig:

2> if ailc-BitConfig is set to TRUE:

3> consider itself to be configured to provide assistance information bit for local cache as specified in TS 36.323 [8], clause 6.2.3;

2> else:

3> consider itself not to be configured to provide assistance information bit for local cache;

5.3.10.10 SCG reconfiguration

The UE shall:

1> if makeBeforeBreakSCG is configured:

2> stop timer T313, if running;

2> start timer T307 with the timer value set to t307, as included in the mobilityControlInfoSCG;

2> start synchronising to the DL of the target PSCell, if needed;

2> perform the remainder of this procedure including and following resetting MAC after the UE has stopped the uplink transmission/downlink reception with the source PSCell;

NOTE 0a: It is up to UE implementation when to stop the uplink transmission/ downlink reception with the source PSCell to initiate re-tuning for the connection to the target cell, as specified in TS 36.133 [16], if makeBeforeBreakSCG is configured.

NOTE 0b: It is up to UE implementation when to stop the uplink transmission/ downlink reception with the source SCG SCell(s) after receiving mobilityControlInfoSCG.

1> if scg-Configuration is received and is set to release or includes the mobilityControlInfoSCG (i.e. SCG release/ change):

2> if mobilityControlInfo is not received (i.e. SCG release/ change without HO):

3> reset SCG MAC, if configured;

3> if the UE is not configured with NE-DC:

4> for each drb-Identity value that is part of the current UE configuration:

5> if the DRB indicated by drb-Identity is an SCG DRB:

6> re-establish the PDCP entity and the SCG RLC entity or entities;

5> if the DRB indicated by drb-Identity is a split DRB:

6> perform PDCP data recovery and re-establish the SCG RLC entity;

5> if the DRB indicated by drb-Identity is an MCG DRB; and

5> drb-ToAddModListSCG is received and includes the drb-Identity value, while for this entry drb-Type is included and set to scg (i.e. MCG to SCG):

6> re-establish the PDCP entity and the MCG RLC entity or entities;

3> configure lower layers to consider the SCG SCell(s), except for the PSCell, to be in deactivated state;

1> if scg-Configuration is received and is set to release:

2> release the entire SCG configuration, except for the DRB configuration (i.e. as configured by drb-ToAddModListSCG);

2> if the current UE configuration includes one or more split or SCG DRBs and the received RRCConnectionReconfiguration message includes radioResourceConfigDedicated including drb-ToAddModList:

3> reconfigure the SCG or split DRB by drb-ToAddModList as specified in 5.3.10.12;

2> stop timer T313, if running;

2> stop timer T307, if running;

1> else:

2> if scg-ConfigPartMCG is received and includes the scg-Counter:

3> update the S-KeNB key based on the KeNB key and using the received scg-Counter value, as specified in TS 33.401 [32];

3> derive the KUPenc key associated with the cipheringAlgorithmSCG included in mobilityControlInfoSCG within the received scg-ConfigPartSCG, as specified in TS 33.401 [32];

3> configure lower layers to apply the ciphering algorithm and the KUPenc key;

2> if scg-ConfigPartSCG is received and includes the radioResourceConfigDedicatedSCG:

3> reconfigure the dedicated radio resource configuration for the SCG as specified in 5.3.10.11;

2> if the current UE configuration includes one or more split or SCG DRBs and the received RRCConnectionReconfiguration message includes radioResourceConfigDedicated including drb-ToAddModList:

3> reconfigure the SCG or split DRB by drb-ToAddModList as specified in 5.3.10.12;

2> if scg-ConfigPartSCG is received and includes measConfigSN:

3> for measConfigSN perform the actions as specified in 5.5.2 for measConfig unless explicitly stated otherwise;

2> if scg-ConfigPartSCG is received and includes the sCellToReleaseListSCG:

3> perform SCell release for the SCG as specified in 5.3.10.3a;

2> if scg-ConfigPartSCG is received and includes the pSCellToAddMod:

3> perform PSCell addition or modification as specified in 5.3.10.3c;

NOTE 0: This procedure is also used to release the PSCell e.g. PSCell change, SI change for the PSCell.

2> if scg-ConfigPartSCG is received and includes the sCellToAddModListSCG:

3> perform SCell addition or modification as specified in 5.3.10.3b;

2> configure lower layers in accordance with mobilityControlInfoSCG, if received;

2> if rach-SkipSCG is configured:

3> configure lower layers to apply the rach-SkipSCG for the target SCG, as specified in TS 36.213 [23] and TS 36.321 [6];

2> if scg-ConfigPartSCG is received and includes the mobilityControlInfoSCG (i.e. SCG change):

3> resume all SCG DRBs and resume SCG transmission for split DRBs, if suspended;

3> stop timer T313, if running;

3> start timer T307 with the timer value set to t307, as included in the mobilityControlInfoSCG, if makeBeforeBreakSCG is not configured;

3> start synchronising to the DL of the target PSCell;

3> initiate the random access procedure on the PSCell, as specified in TS 36.321 [6], if rach-SkipSCG is not configured:

NOTE 1: The UE is not required to determine the SFN of the target PSCell by acquiring system information from that cell before performing RACH access in the target PSCell.

3> the procedure ends, except that the following actions are performed when MAC successfully completes the random access procedure on the PSCell or when MAC indicates the successful reception of a PDCCH transmission addressed to C-RNTI and if rach-skipSCG is configured:

4> stop timer T307;

4> release rach-SkipSCG;

4> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PSCell, if any;

4> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PSCell (e.g. periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PSCell;

NOTE 2: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

5.3.10.11 SCG dedicated resource configuration

The UE shall:

1> if the received radioResourceConfigDedicatedSCG includes the srb-ToReleaseListSCG:

2> for each srb-Identity value included in the srb-ToReleaseListSCG perform the SCG RLC bearer release as specified in 5.3.10.17;

1> if the received radioResourceConfigDedicatedSCG includes the srb-ToAddModListSCG:

2> for each srb-Identity value included in the srb-ToAddModListSCG perform the SCG RLC bearer addition or reconfiguration as specified in 5.3.10.1a;

1> if the received radioResourceConfigDedicatedSCG includes drb-ToReleaseListSCG:

2> perform the DRB release as specified in 5.3.10.2;

1> if the received radioResourceConfigDedicatedSCG includes the drb-ToAddModListSCG:

2> if the UE is configured with NE-DC:

3> for each drb-Identity value included in the drb-ToAddModListSCG perform the SCG RLC bearer addition or reconfiguration for DRBs in NE-DC as specified in 5.3.10.3a4;

2> else:

3> for each drb-Identity value included in the drb-ToAddModListSCG perform the DC specific DRB addition or reconfiguration as specified in 5.3.10.3a1;

1> if the received radioResourceConfigDedicatedSCG includes the mac-MainConfigSCG:

2> perform the SCG MAC main reconfiguration as specified in 5.3.10.4;

1> if the received radioResourceConfigDedicatedSCG includes the rlf-TimersAndConstantsSCG:

2> reconfigure the values of timers and constants as specified in 5.3.10.7;

5.3.10.12 Reconfiguration SCG or split DRB by drb-ToAddModList

The UE shall:

1> for each split or SCG DRBs that is part of the current configuration:

2> if the corresponding drb-Identity value is included in the received drb-ToAddModList; and

2> if the corresponding drb-Identity value is not included in the received drb-ToAddModListSCG (i.e. reconfigure split, split to MCG or SCG to MCG):

3> perform the DC specific DRB addition or reconfiguration as specified in 5.3.10.3a1;

5.3.10.13 Neighbour cell information reconfiguration

The UE shall:

1> if the received naics-Info is set to release:

2> instruct lower layer to release all the NAICS neighbour cell information for the concerned cell, if previously configured;

1> if the received naics-Info includes the neighCellsToReleaseList-r12:

2> for each physCellId-r12 value included in the neighCellsToReleaseList-r12 that is part of the current NAICS neighbour cell information of the concerned cell:

3> instruct lower layer to release the NAICS neighbour cell information for the concerned cell;

1> if the received naics-Info includes the NeighCellsToAddModList-r12:

2> for each physCellId-r12 value included in the neighCellsToAddModList-r12 that is not part of the current NAICS neighbour cell information of the concerned cell:

3> instruct lower layer to add the NAICS neighbour cell information for the concerned cell;

2> for each physCellId-r12 value included in the neighCellsToAddModList-r12 that is part of the current NAICS neighbour cell information of the concerned cell:

3> instruct lower layer to modify the NAICS neighbour cell information in accordance with the received NeighCellsInfo for the concerned cell;

5.3.10.14 Void

5.3.10.15 Sidelink dedicated configuration

The UE shall:

1> if the RRCConnectionReconfiguration message includes the sl-CommConfig:

2> if commTxResources is included and set to setup:

3> from the next SC period use the resources indicated by commTxResources for sidelink communication transmission, as specified in 5.10.4;

2> else if commTxResources is included and set to release:

3> from the next SC period, release the resources allocated for sidelink communication transmission previously configured by commTxResources;

1> if the RRCConnectionReconfiguration message includes the sl-DiscConfig:

2> if discTxResources is included and set to setup:

3> from the next discovery period, as defined by discPeriod, use the resources indicated by discTxResources for sidelink discovery announcement, as specified in 5.10.6;

2> else if discTxResources is included and set to release:

3> from the next discovery period, as defined by discPeriod, release the resources allocated for sidelink discovery announcement previously configured by discTxResources;

2> if discTxResourcesPS is included and set to setup:

3> from the next discovery period, as defined by discPeriod, use the resources indicated by discTxResourcesPS for sidelink discovery announcement, as specified in 5.10.6;

2> else if discTxResourcesPS is included and set to release:

3> from the next discovery period, as defined by discPeriod, release the resources allocated for sidelink discovery announcement previously configured by discTxResourcesPS;

2> if discTxInterFreqInfo is included and set to setup:

3> from the next discovery period, as defined by discPeriod, use the resources indicated by discTxInterFreqInfo for sidelink discovery announcement, as specified in 5.10.6;

2> else if discTxInterFreqInfo is included and set to release:

3> from the next discovery period, as defined by discPeriod, release the resources allocated for sidelink discovery announcement previously configured by discTxInterFreqInfo;

2> if discRxGapConfig is included and set to setup:

3> from the next gap period, as defined by gapPeriod, use the gaps indicated by discRxGapConfig for sidelink discovery monitoring, as specified in 5.10.5;

2> else if discRxGapConfig is included and set to release:

3> from the next gap period, as defined by gapPeriod, release the gaps configured for sidelink discovery monitoring previously configured by discRxGapConfig;

2> if discTxGapConfig is included and set to setup:

3> from the next gap period, as defined by gapPeriod, use the gaps indicated by discTxGapConfig for sidelink discovery announcement, as specified in 5.10.6;

2> else if discTxGapConfig is included and set to release:

3> from the next gap period, as defined by gapPeriod, release the gaps configured for sidelink discovery announcement previously configured by discTxGapConfig;

2> if discSysInfoToReportConfig is included and set to setup:

3> start timer T370 with the timer value set to 60s;

2> else if discSysInfoToReportConfig is included and set to release:

3> stop timer T370 and release discSysInfoToReportConfig;

5.3.10.15a V2X sidelink Communication dedicated configuration

The UE shall:

1> if the RRCConnectionReconfiguration message includes the sl-V2X-ConfigDedicated:

2> if commTxResources is included and set to setup:

3> use the resources indicated by commTxResources for V2X sidelink communication transmission, as specified in 5.10.13;

3> perform CBR measurement on the transmission resource pool indicated in commTxResources for V2X sidelink communication transmission, as specified in 5.5.3;

2> else if commTxResources is included and set to release:

3> release the resources allocated for V2X sidelink communication transmission previously configured by commTxResources;

2> if v2x-InterFreqInfoList is included:

3> use the synchronization configuration and resource configuration parameters for V2X sidelink communication on frequencies included in v2x-InterFreqInfoList, as specified in 5.10.13;

3> perform CBR measurement on the transmission resource pool indicated in v2x-InterFreqInfoList for V2X sidelink communication transmission, as specified in 5.5.3;

1> if the RRCConnectionReconfiguration message includes the mobilityControlInfoV2X:

2> if v2x-CommRxPool is included:

3> use the resources indicated by v2x-CommRxPool for V2X sidelink communication reception, as specified in 5.10.12;

2> if v2x-CommTxPoolExceptional is included:

3> use the resources indicated by v2x-CommTxPoolExceptional for V2X sidelink communication transmission, as specified in 5.10.13;

3> perform CBR measurement on the transmission resource pool indicated by v2x-CommTxPoolExceptional for V2X sidelink communication transmission, as specified in 5.5.3;

5.3.10.16 T370 expiry

The UE shall:

1> if T370 expires:

2> release discSysInfoToReportConfig;

5.3.10.17 SRB release

The UE shall:

1> for each srb-Identity value included in srb-ToReleaseList or in srb-ToReleaseListSCG that is part of the current UE configuration:

2> if the SRB configuration does not include an E-UTRA PDCP entity (release the SCG RLC bearer configuration):

3> re-establish the RLC entity as specified in TS 36.322 [7] for this SRB;

3> configure the E-UTRA PDCP entity to deactivate duplication;

2> release the RLC entity or entities;

2> release the DCCH logical channel;

2> if srb-Identity value is set to 4, release the PDCP entity;

5.3.10.18 Scheduling Request Configuration for NB-IoT

The UE shall:

1> apply sr-WithHARQ-ACK-Config, if included;

1> apply sr-WithoutHARQ-ACK-Config, if included;

1> apply sr-SPS-BSR-Config, if included;

5.3.10.19 NE-DC release

The UE shall:

1> if NE-DC release is triggered by NR:

2> reset SCG MAC, if configured;

2> for each RLC bearer that is part of the SCG configuration:

3> perform RLC bearer release procedure as specified in 5.3.10.17 (SRBs) and in 5.3.10.2 (DRBs);

2> release the measurement configuration;

2> release the SCG configuration i.e. release the MAC and physical configuration for each cell that is part of the SCG configuration;

2> stop timer T313 for the corresponding PSCell, if running;

2> stop timer T307 for the corresponding PSCell, if running.

NOTE: Upon NE-DC release the UE releases all fields configured by the RRCConnectionReconfiguration message.