3rd Generation Partnership Project;

Technical Specification Group Radio Access Network;

3GPP TS 36.331
Evolved Universal Terrestrial Radio Access (E-UTRA);
V15.4.0 (2018-12)
Radio Resource Control (RRC);
Technical Specification
Protocol specification
(Release 15)

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this
Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 15 2 3GPP TS 36.331 V15.4.0 (2018-12)

Keywords
LTE, E-UTRAN, radio

3GPP

Postal address

3GPP support office address

650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet
http://www.3gpp.org

Copyright Notification

No part may be reproduced except as authorized by written permission.

The copyright and the foregoing restriction extend to reproduction in all media.

© 2018, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.

UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association
Bluetooth® is a Trade Mark of the Bluetooth SIG registered for the benefit of its members

3GPP
Release 15 3 3GPP TS 36.331 V15.4.0 (2018-12)

Contents
Foreword........................................................................................................................................................22
1 Scope....................................................................................................................................................23
2 References............................................................................................................................................23
3 Definitions, symbols and abbreviations................................................................................................27
3.1 Definitions.........................................................................................................................................................27
3.2 Abbreviations.....................................................................................................................................................29
4 General.................................................................................................................................................32
4.1 Introduction.......................................................................................................................................................32
4.2 Architecture.......................................................................................................................................................34
4.2.1 UE states and state transitions including inter RAT....................................................................................34
4.2.2 Signalling radio bearers...............................................................................................................................36
4.3 Services..............................................................................................................................................................37
4.3.1 Services provided to upper layers................................................................................................................37
4.3.2 Services expected from lower layers...........................................................................................................37
4.4 Functions...........................................................................................................................................................37
4.5 Data available for transmission for NB-IoT......................................................................................................39
5 Procedures............................................................................................................................................39
5.1 General...............................................................................................................................................................39
5.1.1 Introduction..................................................................................................................................................39
5.1.2 General requirements...................................................................................................................................39
5.2 System information............................................................................................................................................40
5.2.1 Introduction..................................................................................................................................................40
5.2.1.1 General...................................................................................................................................................40
5.2.1.2 Scheduling..............................................................................................................................................41
5.2.1.2a Scheduling for NB-IoT...........................................................................................................................42
5.2.1.3 System information validity and notification of changes.......................................................................43
5.2.1.4 Indication of ETWS notification............................................................................................................44
5.2.1.5 Indication of CMAS notification............................................................................................................45
5.2.1.6 Notification of EAB parameters change................................................................................................45
5.2.1.7 Access Barring parameters change in NB-IoT.......................................................................................45
5.2.2 System information acquisition...................................................................................................................46
5.2.2.1 General...................................................................................................................................................46
5.2.2.2 Initiation.................................................................................................................................................46
5.2.2.3 System information required by the UE.................................................................................................46
5.2.2.4 System information acquisition by the UE............................................................................................47
5.2.2.5 Essential system information missing....................................................................................................51
5.2.2.6 Actions upon reception of the MasterInformationBlock message.........................................................52
5.2.2.7 Actions upon reception of the SystemInformationBlockType1 message................................................52
5.2.2.8 Actions upon reception of SystemInformation messages.......................................................................54
5.2.2.9 Actions upon reception of SystemInformationBlockType2....................................................................54
5.2.2.10 Actions upon reception of SystemInformationBlockType3....................................................................55
5.2.2.11 Actions upon reception of SystemInformationBlockType4....................................................................56
5.2.2.12 Actions upon reception of SystemInformationBlockType5....................................................................56
5.2.2.13 Actions upon reception of SystemInformationBlockType6....................................................................57
5.2.2.14 Actions upon reception of SystemInformationBlockType7....................................................................57
5.2.2.15 Actions upon reception of SystemInformationBlockType8....................................................................58
5.2.2.16 Actions upon reception of SystemInformationBlockType9....................................................................58
5.2.2.17 Actions upon reception of SystemInformationBlockType10..................................................................59
5.2.2.18 Actions upon reception of SystemInformationBlockType11..................................................................59
5.2.2.19 Actions upon reception of SystemInformationBlockType12..................................................................59
5.2.2.20 Actions upon reception of SystemInformationBlockType13..................................................................60
5.2.2.21 Actions upon reception of SystemInformationBlockType14..................................................................60
5.2.2.22 Actions upon reception of SystemInformationBlockType15..................................................................61
5.2.2.23 Actions upon reception of SystemInformationBlockType16..................................................................61

3GPP
Release 15 4 3GPP TS 36.331 V15.4.0 (2018-12)

5.2.2.24 Actions upon reception of SystemInformationBlockType17..................................................................61

5.2.2.25 Actions upon reception of SystemInformationBlockType18..................................................................61
5.2.2.26 Actions upon reception of SystemInformationBlockType19..................................................................61
5.2.2.27 Actions upon reception of SystemInformationBlockType20..................................................................62
5.2.2.28 Actions upon reception of SystemInformationBlockType21..................................................................62
5.2.2.29 Actions upon reception of SystemInformationBlockType22-NB............................................................62
5.2.2.30 Actions upon reception of SystemInformationBlockType23-NB............................................................62
5.2.2.31 Actions upon reception of SystemInformationBlockType24..................................................................62
5.2.2.32 Actions upon reception of SystemInformationBlockType25..................................................................62
5.2.2.33 Actions upon reception of SystemInformationBlockType26..................................................................62
5.2.2.34 Actions upon reception of SystemInformationBlockPos........................................................................63
5.2.3 Acquisition of an SI message.......................................................................................................................63
5.2.3a Acquisition of an SI message by BL UE or UE in CE or a NB-IoT UE.....................................................63
5.2.3b Acquisition of an SI message from MBMS-dedicated cell..........................................................................64
5.3 Connection control............................................................................................................................................65
5.3.1 Introduction..................................................................................................................................................65
5.3.1.1 RRC connection control.........................................................................................................................65
5.3.1.2 Security...................................................................................................................................................67
5.3.1.2a RN security.............................................................................................................................................68
5.3.1.3 Connected mode mobility......................................................................................................................69
5.3.1.4 Connection control in NB-IoT...............................................................................................................70
5.3.2 Paging..........................................................................................................................................................71
5.3.2.1 General...................................................................................................................................................71
5.3.2.2 Initiation.................................................................................................................................................71
5.3.2.3 Reception of the Paging message by the UE.........................................................................................71
5.3.3 RRC connection establishment....................................................................................................................73
5.3.3.1 General...................................................................................................................................................73
5.3.3.1a Conditions for establishing RRC Connection for sidelink communication/ discovery/ V2X
sidelink communication.........................................................................................................................75
5.3.3.1b Conditions for initiating EDT................................................................................................................77
5.3.3.2 Initiation.................................................................................................................................................77
5.3.3.3 Actions related to transmission of RRCConnectionRequest message....................................................83
5.3.3.3a Actions related to transmission of RRCConnectionResumeRequest message.......................................84
5.3.3.3b Actions related to transmission of RRCEarlyDataRequest message.....................................................87
5.3.3.3c UE actions upon receiving EDT fallback indication from lower layers................................................87
5.3.3.4 Reception of the RRCConnectionSetup by the UE................................................................................87
5.3.3.4a Reception of the RRCConnectionResume by the UE.............................................................................91
5.3.3.4b Reception of the RRCEarlyDataComplete by the UE...........................................................................94
5.3.3.5 Cell re-selection or cell selection while T300, T302, T303, T305, T306, T308 or T309 is running.....95
5.3.3.6 T300 expiry............................................................................................................................................96
5.3.3.7 T302, T303, T305, T306, or T308 expiry or stop..................................................................................98
5.3.3.8 Reception of the RRCConnectionReject by the UE...............................................................................98
5.3.3.9 Abortion of RRC connection establishment.........................................................................................100
5.3.3.9a Abortion of UP-EDT............................................................................................................................100
5.3.3.10 Handling of SSAC related parameters.................................................................................................100
5.3.3.11 Access barring check............................................................................................................................101
5.3.3.12 EAB check............................................................................................................................................102
5.3.3.13 Access barring check for ACDC..........................................................................................................103
5.3.3.14 Access Barring check for NB-IoT........................................................................................................103
5.3.3.15 Failure to deliver NAS information in RRCConnectionSetupComplete message...............................105
5.3.3.16 Integrity check failure from lower layers while T300 is running for UP-EDT or
RRC_INACTIVE.................................................................................................................................105
5.3.3.17 Inability to comply with RRCConnectionResume................................................................................106
5.3.4 Initial security activation............................................................................................................................106
5.3.4.1 General.................................................................................................................................................106
5.3.4.2 Initiation...............................................................................................................................................106
5.3.4.3 Reception of the SecurityModeCommand by the UE...........................................................................106
5.3.5 RRC connection reconfiguration...............................................................................................................108
5.3.5.1 General.................................................................................................................................................108
5.3.5.2 Initiation...............................................................................................................................................108

3GPP
Release 15 5 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.5.3 Reception of an RRCConnectionReconfiguration not including the mobilityControlInfo by the

UE.........................................................................................................................................................108
5.3.5.4 Reception of an RRCConnectionReconfiguration including the mobilityControlInfo by the UE
(handover)............................................................................................................................................111
5.3.5.5 Reconfiguration failure........................................................................................................................116
5.3.5.6 T304 expiry (handover failure)............................................................................................................117
5.3.5.7 Void......................................................................................................................................................118
5.3.5.7a T307 expiry (SCG change failure).......................................................................................................118
5.3.5.8 Radio Configuration involving full configuration option....................................................................118
5.3.6 Counter check............................................................................................................................................120
5.3.6.1 General.................................................................................................................................................120
5.3.6.2 Initiation...............................................................................................................................................121
5.3.6.3 Reception of the CounterCheck message by the UE............................................................................121
5.3.7 RRC connection re-establishment..............................................................................................................121
5.3.7.1 General.................................................................................................................................................121
5.3.7.2 Initiation...............................................................................................................................................122
5.3.7.3 Actions following cell selection while T311 is running.......................................................................124
5.3.7.4 Actions related to transmission of RRCConnectionReestablishmentRequest message.......................124
5.3.7.5 Reception of the RRCConnectionReestablishment by the UE.............................................................125
5.3.7.6 T311 expiry..........................................................................................................................................128
5.3.7.7 T301 expiry or selected cell no longer suitable....................................................................................128
5.3.7.8 Reception of RRCConnectionReestablishmentReject by the UE.........................................................129
5.3.8 RRC connection release.............................................................................................................................129
5.3.8.1 General.................................................................................................................................................129
5.3.8.2 Initiation...............................................................................................................................................129
5.3.8.3 Reception of the RRCConnectionRelease by the UE...........................................................................129
5.3.8.4 T320 expiry..........................................................................................................................................132
5.3.8.5 T322 expiry..........................................................................................................................................132
5.3.8.6 UE actions upon receiving the expiry of DataInactivityTimer............................................................132
5.3.8.7 UE actions upon entering RRC_INACTIVE.......................................................................................132
5.3.9 RRC connection release requested by upper layers...................................................................................133
5.3.9.1 General.................................................................................................................................................133
5.3.9.2 Initiation...............................................................................................................................................133
5.3.10 Radio resource configuration.....................................................................................................................133
5.3.10.0 General.................................................................................................................................................133
5.3.10.1 SRB addition/ modification..................................................................................................................134
5.3.10.2 DRB release..........................................................................................................................................135
5.3.10.3 DRB addition/ modification.................................................................................................................136
5.3.10.3a1 DC specific DRB addition or reconfiguration......................................................................................137
5.3.10.3a2 LWA specific DRB addition or reconfiguration..................................................................................138
5.3.10.3a3 LWIP specific DRB addition or reconfiguration.................................................................................139
5.3.10.3a SCell release.........................................................................................................................................140
5.3.10.3b SCell addition/ modification................................................................................................................140
5.3.10.3c PSCell addition or modification...........................................................................................................141
5.3.10.4 MAC main reconfiguration..................................................................................................................141
5.3.10.5 Semi-persistent scheduling reconfiguration.........................................................................................142
5.3.10.6 Physical channel reconfiguration.........................................................................................................142
5.3.10.7 Radio Link Failure Timers and Constants reconfiguration..................................................................143
5.3.10.8 Time domain measurement resource restriction for serving cell.........................................................143
5.3.10.9 Other configuration..............................................................................................................................143
5.3.10.10 SCG reconfiguration............................................................................................................................146
5.3.10.11 SCG dedicated resource configuration.................................................................................................148
5.3.10.12 Reconfiguration SCG or split DRB by drb-ToAddModList.................................................................148
5.3.10.13 Neighbour cell information reconfiguration.........................................................................................148
5.3.10.14 Void......................................................................................................................................................149
5.3.10.15 Sidelink dedicated configuration..........................................................................................................149
5.3.10.15a V2X sidelink Communication dedicated configuration.......................................................................150
5.3.10.16 T370 expiry..........................................................................................................................................151
5.3.10.17 SRB release..........................................................................................................................................151
5.3.10.18 Scheduling Request Configuration for NB-IoT...................................................................................151
5.3.11 Radio link failure related actions...............................................................................................................151

3GPP
Release 15 6 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.11.1 Detection of physical layer problems in RRC_CONNECTED...........................................................151

5.3.11.1a Early detection of physical layer problems in RRC_CONNECTED...................................................151
5.3.11.1b Detection of physical layer improvements in RRC_CONNECTED....................................................151
5.3.11.2 Recovery of physical layer problems...................................................................................................152
5.3.11.2a Recovery of early detection of physical layer problems......................................................................152
5.3.11.2b Cancellation of physical layer improvements in RRC_CONNECTED...............................................152
5.3.11.3 Detection of radio link failure..............................................................................................................152
5.3.11.3a Detection of early-out-of-sync event....................................................................................................154
5.3.11.3b Detection of early-in-sync event..........................................................................................................154
5.3.12 UE actions upon leaving RRC_CONNECTED or RRC_INACTIVE.......................................................155
5.3.13 UE actions upon PUCCH/ SPUCCH/ SRS release request.......................................................................156
5.3.13a UE actions upon SR release request for NB-IoT.......................................................................................156
5.3.14 Proximity indication...................................................................................................................................157
5.3.14.1 General.................................................................................................................................................157
5.3.14.2 Initiation...............................................................................................................................................157
5.3.14.3 Actions related to transmission of ProximityIndication message........................................................157
5.3.15 Void............................................................................................................................................................158
5.3.16 Unified Access Control..............................................................................................................................158
5.3.16.1 General.................................................................................................................................................158
5.3.16.2 Initiation...............................................................................................................................................158
5.3.16.3 Void......................................................................................................................................................160
5.3.16.4 T302, T309 expiry or stop (Barring alleviation)..................................................................................160
5.3.16.5 Access barring check............................................................................................................................160
5.3.17 RAN notification area update....................................................................................................................160
5.3.17.1 General.................................................................................................................................................160
5.3.17.2 Initiation...............................................................................................................................................161
5.3.17.3 Inter RAT cell reselection or CN type change.....................................................................................161
5.4 Inter-RAT mobility..........................................................................................................................................161
5.4.1 Introduction................................................................................................................................................161
5.4.2 Handover to E-UTRA................................................................................................................................161
5.4.2.1 General.................................................................................................................................................161
5.4.2.2 Initiation...............................................................................................................................................162
5.4.2.3 Reception of the RRCConnectionReconfiguration by the UE.............................................................162
5.4.2.4 Reconfiguration failure........................................................................................................................165
5.4.2.5 T304 expiry (handover to E-UTRA failure)........................................................................................165
5.4.3 Mobility from E-UTRA.............................................................................................................................166
5.4.3.1 General.................................................................................................................................................166
5.4.3.2 Initiation...............................................................................................................................................166
5.4.3.3 Reception of the MobilityFromEUTRACommand by the UE..............................................................166
5.4.3.4 Successful completion of the mobility from E-UTRA.........................................................................168
5.4.3.5 Mobility from E-UTRA failure............................................................................................................169
5.4.4 Handover from E-UTRA preparation request (CDMA2000)....................................................................169
5.4.4.1 General.................................................................................................................................................169
5.4.4.2 Initiation...............................................................................................................................................170
5.4.4.3 Reception of the HandoverFromEUTRAPreparationRequest by the UE............................................170
5.4.5 UL handover preparation transfer (CDMA2000)......................................................................................170
5.4.5.1 General.................................................................................................................................................170
5.4.5.2 Initiation...............................................................................................................................................170
5.4.5.3 Actions related to transmission of the ULHandoverPreparationTransfer message............................171
5.4.5.4 Failure to deliver the ULHandoverPreparationTransfer message......................................................171
5.4.6 Inter-RAT cell change order to E-UTRAN................................................................................................171
5.4.6.1 General.................................................................................................................................................171
5.4.6.2 Initiation...............................................................................................................................................171
5.4.6.3 UE fails to complete an inter-RAT cell change order..........................................................................171
5.5 Measurements..................................................................................................................................................172
5.5.1 Introduction................................................................................................................................................172
5.5.2 Measurement configuration.......................................................................................................................174
5.5.2.1 General.................................................................................................................................................174
5.5.2.2 Measurement identity removal.............................................................................................................175
5.5.2.2a Measurement identity autonomous removal........................................................................................175
5.5.2.3 Measurement identity addition/ modification......................................................................................175

3GPP
Release 15 7 3GPP TS 36.331 V15.4.0 (2018-12)

5.5.2.4 Measurement object removal...............................................................................................................176

5.5.2.5 Measurement object addition/ modification.........................................................................................177
5.5.2.6 Reporting configuration removal.........................................................................................................179
5.5.2.7 Reporting configuration addition/ modification...................................................................................180
5.5.2.8 Quantity configuration.........................................................................................................................180
5.5.2.9 Measurement gap configuration...........................................................................................................180
5.5.2.9a Measurement gap configuration for RSTD measurements with dense PRS configuration.................182
5.5.2.10 Discovery signals measurement timing configuration.........................................................................182
5.5.2.11 RSSI measurement timing configuration.............................................................................................182
5.5.2.12 Measurement gap sharing configuration..............................................................................................183
5.5.2.13 NR measurement timing configuration................................................................................................183
5.5.3 Performing measurements..........................................................................................................................183
5.5.3.1 General.................................................................................................................................................183
5.5.3.2 Layer 3 filtering....................................................................................................................................187
5.5.3.3 Derivation of NR cell quality...............................................................................................................188
5.5.3.4 Derivation of NR beam quality............................................................................................................188
5.5.4 Measurement report triggering...................................................................................................................188
5.5.4.1 General.................................................................................................................................................188
5.5.4.2 Event A1 (Serving becomes better than threshold)..............................................................................195
5.5.4.3 Event A2 (Serving becomes worse than threshold).............................................................................195
5.5.4.4 Event A3 (Neighbour becomes offset better than PCell/ PSCell)........................................................196
5.5.4.5 Event A4 (Neighbour becomes better than threshold).........................................................................196
5.5.4.6 Event A5 (PCell/ PSCell becomes worse than threshold1 and neighbour becomes better than
threshold2)............................................................................................................................................197
5.5.4.6a Event A6 (Neighbour becomes offset better than SCell).....................................................................198
5.5.4.7 Event B1 (Inter RAT neighbour becomes better than threshold).........................................................199
5.5.4.8 Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour becomes better than
threshold2)............................................................................................................................................199
5.5.4.9 Event C1 (CSI-RS resource becomes better than threshold)...............................................................200
5.5.4.10 Event C2 (CSI-RS resource becomes offset better than reference CSI-RS resource).........................200
5.5.4.11 Event W1 (WLAN becomes better than a threshold)...........................................................................201
5.5.4.12 Event W2 (All WLAN inside WLAN mobility set becomes worse than threshold1 and a WLAN
outside WLAN mobility set becomes better than threshold2).............................................................202
5.5.4.13 Event W3 (All WLAN inside WLAN mobility set becomes worse than a threshold)........................202
5.5.4.14 Event V1 (The channel busy ratio is above a threshold)......................................................................203
5.5.4.15 Event V2 (The channel busy ratio is below a threshold).....................................................................203
5.5.4.16 Event H1 (The Aerial UE height is above a threshold)........................................................................204
5.5.4.17 Event H2 (The Aerial UE height is below a threshold).......................................................................204
5.5.5 Measurement reporting..............................................................................................................................205
5.5.5.1 General.................................................................................................................................................205
5.5.5.2 Determination of available NR measurement results...........................................................................211
5.5.5.3 Selection of NR sorting quality............................................................................................................212
5.5.6 Measurement related actions......................................................................................................................212
5.5.6.1 Actions upon handover and re-establishment......................................................................................212
5.5.6.2 Speed dependant scaling of measurement related parameters.............................................................213
5.5.7 Inter-frequency RSTD measurement indication........................................................................................214
5.5.7.1 General.................................................................................................................................................214
5.5.7.2 Initiation...............................................................................................................................................214
5.5.7.3 Actions related to transmission of InterFreqRSTDMeasurementIndication message.........................215
5.6 Other................................................................................................................................................................215
5.6.0 General.......................................................................................................................................................215
5.6.1 DL information transfer.............................................................................................................................216
5.6.1.1 General.................................................................................................................................................216
5.6.1.2 Initiation...............................................................................................................................................216
5.6.1.3 Reception of the DLInformationTransfer by the UE...........................................................................216
5.6.2 UL information transfer.............................................................................................................................217
5.6.2.1 General.................................................................................................................................................217
5.6.2.2 Initiation...............................................................................................................................................217
5.6.2.3 Actions related to transmission of ULInformationTransfer message..................................................217
5.6.2.4 Failure to deliver ULInformationTransfer message.............................................................................217
5.6.2a UL information transfer for MR-DC.........................................................................................................218

3GPP
Release 15 8 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.2a.1 General.................................................................................................................................................218
5.6.2a.2 Initiation...............................................................................................................................................218
5.6.2a.3 Actions related to transmission of ULInformationTransferMRDC message.......................................218
5.6.2a.4 Void......................................................................................................................................................219
5.6.3 UE capability transfer................................................................................................................................219
5.6.3.1 General.................................................................................................................................................219
5.6.3.2 Initiation...............................................................................................................................................219
5.6.3.3 Reception of the UECapabilityEnquiry by the UE..............................................................................219
5.6.4 CSFB to 1x Parameter transfer..................................................................................................................223
5.6.4.1 General.................................................................................................................................................223
5.6.4.2 Initiation...............................................................................................................................................224
5.6.4.3 Actions related to transmission of CSFBParametersRequestCDMA2000 message............................224
5.6.4.4 Reception of the CSFBParametersResponseCDMA2000 message.....................................................224
5.6.5 UE Information..........................................................................................................................................224
5.6.5.1 General.................................................................................................................................................224
5.6.5.2 Initiation...............................................................................................................................................224
5.6.5.3 Reception of the UEInformationRequest message...............................................................................224
5.6.6 Logged Measurement Configuration.........................................................................................................226
5.6.6.1 General.................................................................................................................................................226
5.6.6.2 Initiation...............................................................................................................................................226
5.6.6.3 Reception of the LoggedMeasurementConfiguration by the UE.........................................................227
5.6.6.4 T330 expiry..........................................................................................................................................227
5.6.7 Release of Logged Measurement Configuration.......................................................................................227
5.6.7.1 General.................................................................................................................................................227
5.6.7.2 Initiation...............................................................................................................................................227
5.6.8 Measurements logging...............................................................................................................................228
5.6.8.1 General.................................................................................................................................................228
5.6.8.2 Initiation...............................................................................................................................................228
5.6.9 In-device coexistence indication................................................................................................................231
5.6.9.1 General.................................................................................................................................................231
5.6.9.2 Initiation...............................................................................................................................................231
5.6.9.3 Actions related to transmission of InDeviceCoexIndication message.................................................232
5.6.10 UE Assistance Information........................................................................................................................233
5.6.10.1 General.................................................................................................................................................233
5.6.10.2 Initiation...............................................................................................................................................234
5.6.10.3 Actions related to transmission of UEAssistanceInformation message...............................................235
5.6.11 Mobility history information......................................................................................................................236
5.6.11.1 General.................................................................................................................................................236
5.6.11.2 Initiation...............................................................................................................................................236
5.6.12 RAN-assisted WLAN interworking...........................................................................................................237
5.6.12.1 General.................................................................................................................................................237
5.6.12.2 Dedicated WLAN offload configuration..............................................................................................237
5.6.12.3 WLAN offload RAN evaluation..........................................................................................................237
5.6.12.4 T350 expiry or stop..............................................................................................................................238
5.6.12.5 Cell selection/ re-selection while T350 is running...............................................................................238
5.6.13 SCG failure information.............................................................................................................................238
5.6.13.1 General.................................................................................................................................................238
5.6.13.2 Initiation...............................................................................................................................................238
5.6.13.3 Actions related to transmission of SCGFailureInformation message..................................................239
5.6.13a NR SCG failure information......................................................................................................................240
5.6.13a.1 General.................................................................................................................................................240
5.6.13a.2 Initiation...............................................................................................................................................240
5.6.13a.3 Actions related to transmission of SCGFailureInformationNR message.............................................240
5.6.14 LTE-WLAN Aggregation..........................................................................................................................240
5.6.14.1 Introduction..........................................................................................................................................240
5.6.14.2 Reception of LWA configuration.........................................................................................................241
5.6.14.3 Release of LWA configuration............................................................................................................241
5.6.15 WLAN connection management................................................................................................................242
5.6.15.1 Introduction..........................................................................................................................................242
5.6.15.2 WLAN connection status reporting......................................................................................................242
5.6.15.2.1 General............................................................................................................................................242

3GPP
Release 15 9 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.15.2.2 Initiation..........................................................................................................................................242
5.6.15.2.3 Actions related to transmission of WLANConnectionStatusReport message.................................243
5.6.15.3 T351 Expiry (WLAN connection attempt timeout).............................................................................243
5.6.15.4 WLAN status monitoring.....................................................................................................................243
5.6.16 RAN controlled LTE-WLAN interworking...............................................................................................244
5.6.16.1 General.................................................................................................................................................244
5.6.16.2 WLAN traffic steering command.........................................................................................................244
5.6.17 LTE-WLAN aggregation with IPsec tunnel..............................................................................................244
5.6.17.1 General.................................................................................................................................................244
5.6.17.2 LWIP reconfiguration..........................................................................................................................245
5.6.17.3 LWIP release........................................................................................................................................245
5.6.18 Void............................................................................................................................................................246
5.6.19 Application layer measurement reporting..................................................................................................246
5.6.19.1 General.................................................................................................................................................246
5.6.19.2 Initiation...............................................................................................................................................246
5.6.20 Idle Mode Measurements...........................................................................................................................246
5.6.20.1 General.................................................................................................................................................246
5.6.20.2 Initiation...............................................................................................................................................246
5.6.20.3 T331 expiry or stop..............................................................................................................................247
5.6.21 Failure information....................................................................................................................................247
5.6.21.1 General.................................................................................................................................................247
5.6.21.2 Initiation...............................................................................................................................................247
5.6.21.3 Actions related to transmission of FailureInformation message.........................................................248
5.7 Generic error handling.....................................................................................................................................248
5.7.1 General.......................................................................................................................................................248
5.7.2 ASN.1 violation or encoding error.............................................................................................................248
5.7.3 Field set to a not comprehended value.......................................................................................................248
5.7.4 Mandatory field missing............................................................................................................................249
5.7.5 Not comprehended field.............................................................................................................................250
5.8 MBMS.............................................................................................................................................................250
5.8.1 Introduction................................................................................................................................................250
5.8.1.1 General.................................................................................................................................................250
5.8.1.2 Scheduling............................................................................................................................................250
5.8.1.3 MCCH information validity and notification of changes.....................................................................251
5.8.2 MCCH information acquisition.................................................................................................................252
5.8.2.1 General.................................................................................................................................................252
5.8.2.2 Initiation...............................................................................................................................................252
5.8.2.3 MCCH information acquisition by the UE..........................................................................................252
5.8.2.4 Actions upon reception of the MBSFNAreaConfiguration message....................................................253
5.8.2.5 Actions upon reception of the MBMSCountingRequest message........................................................253
5.8.3 MBMS PTM radio bearer configuration....................................................................................................253
5.8.3.1 General.................................................................................................................................................253
5.8.3.2 Initiation...............................................................................................................................................253
5.8.3.3 MRB establishment..............................................................................................................................253
5.8.3.4 MRB release.........................................................................................................................................253
5.8.4 MBMS Counting Procedure......................................................................................................................253
5.8.4.1 General.................................................................................................................................................253
5.8.4.2 Initiation...............................................................................................................................................254
5.8.4.3 Reception of the MBMSCountingRequest message by the UE............................................................254
5.8.5 MBMS interest indication..........................................................................................................................255
5.8.5.1 General.................................................................................................................................................255
5.8.5.2 Initiation...............................................................................................................................................255
5.8.5.3 Determine MBMS frequencies of interest...........................................................................................256
5.8.5.4 Actions related to transmission of MBMSInterestIndication message.................................................257
5.8a SC-PTM...........................................................................................................................................................258
5.8a.1 Introduction................................................................................................................................................258
5.8a.1.1 General.................................................................................................................................................258
5.8a.1.2 SC-MCCH scheduling..........................................................................................................................258
5.8a.1.3 SC-MCCH information validity and notification of changes..............................................................258
5.8a.1.4 Procedures............................................................................................................................................259
5.8a.2 SC-MCCH information acquisition...........................................................................................................259

3GPP
Release 15 10 3GPP TS 36.331 V15.4.0 (2018-12)

5.8a.2.1 General.................................................................................................................................................259
5.8a.2.2 Initiation...............................................................................................................................................259
5.8a.2.3 SC-MCCH information acquisition by the UE....................................................................................259
5.8a.2.4 Actions upon reception of the SCPTMConfiguration message...........................................................260
5.8a.3 SC-PTM radio bearer configuration..........................................................................................................260
5.8a.3.1 General.................................................................................................................................................260
5.8a.3.2 Initiation...............................................................................................................................................260
5.8a.3.3 SC-MRB establishment........................................................................................................................260
5.8a.3.4 SC-MRB release...................................................................................................................................261
5.9 RN procedures.................................................................................................................................................261
5.9.1 RN reconfiguration....................................................................................................................................261
5.9.1.1 General.................................................................................................................................................261
5.9.1.2 Initiation...............................................................................................................................................261
5.9.1.3 Reception of the RNReconfiguration by the RN..................................................................................261
5.10 Sidelink............................................................................................................................................................262
5.10.1 Introduction................................................................................................................................................262
5.10.1a Conditions for sidelink communication operation.....................................................................................262
5.10.1d Conditions for V2X sidelink communication operation............................................................................263
5.10.2 Sidelink UE information............................................................................................................................263
5.10.2.1 General.................................................................................................................................................263
5.10.2.2 Initiation...............................................................................................................................................264
5.10.2.3 Actions related to transmission of SidelinkUEInformation message...................................................269
5.10.3 Sidelink communication monitoring..........................................................................................................271
5.10.4 Sidelink communication transmission.......................................................................................................273
5.10.5 Sidelink discovery monitoring...................................................................................................................274
5.10.6 Sidelink discovery announcement.............................................................................................................275
5.10.6a Sidelink discovery announcement pool selection......................................................................................278
5.10.6b Sidelink discovery announcement reference carrier selection...................................................................278
5.10.7 Sidelink synchronisation information transmission...................................................................................279
5.10.7.1 General.................................................................................................................................................279
5.10.7.2 Initiation...............................................................................................................................................280
5.10.7.3 Transmission of SLSS..........................................................................................................................282
5.10.7.4 Transmission of MasterInformationBlock-SL or MasterInformationBlock-SL-V2X message.............284
5.10.7.5 Void......................................................................................................................................................285
5.10.8 Sidelink synchronisation reference............................................................................................................285
5.10.8.1 General.................................................................................................................................................285
5.10.8.2 Selection and reselection of synchronisation reference.......................................................................285
5.10.8a Selection and reselection of synchronisation carrier frequency.................................................................288
5.10.9 Sidelink common control information.......................................................................................................291
5.10.9.1 General.................................................................................................................................................291
5.10.9.2 Actions related to reception of MasterInformationBlock-SL/ MasterInformationBlock-SL-V2X
message................................................................................................................................................291
5.10.10 Sidelink relay UE operation.......................................................................................................................291
5.10.10.1 General.................................................................................................................................................291
5.10.10.2 AS-conditions for relay related sidelink communication transmission by sidelink relay UE..............292
5.10.10.3 AS-conditions for relay PS related sidelink discovery transmission by sidelink relay UE.................292
5.10.10.4 Sidelink relay UE threshold conditions................................................................................................292
5.10.11 Sidelink remote UE operation....................................................................................................................292
5.10.11.1 General.................................................................................................................................................292
5.10.11.2 AS-conditions for relay related sidelink communication transmission by sidelink remote UE..........293
5.10.11.3 AS-conditions for relay PS related sidelink discovery transmission by sidelink remote UE..............293
5.10.11.4 Selection and reselection of sidelink relay UE.....................................................................................293
5.10.11.5 Sidelink remote UE threshold conditions.............................................................................................294
5.10.12 V2X sidelink communication monitoring..................................................................................................294
5.10.13 V2X sidelink communication transmission...............................................................................................295
5.10.13.1 Transmission of V2X sidelink communication....................................................................................295
5.10.13.1a Transmission of P2X related V2X sidelink communication................................................................297
5.10.13.2 V2X sidelink communication transmission pool selection..................................................................298
5.10.13.3 V2X sidelink communication transmission reference cell selection....................................................299
5.10.14 DFN derivation from GNSS......................................................................................................................300

3GPP
Release 15 11 3GPP TS 36.331 V15.4.0 (2018-12)

6 Protocol data units, formats and parameters (tabular & ASN.1).........................................................300

6.1 General.............................................................................................................................................................300
6.2 RRC messages.................................................................................................................................................302
6.2.1 General message structure.........................................................................................................................302
– EUTRA-RRC-Definitions.....................................................................................................................302
– BCCH-BCH-Message...........................................................................................................................302
– BCCH-BCH-Message-MBMS..............................................................................................................302
– BCCH-DL-SCH-Message.....................................................................................................................303
– BCCH-DL-SCH-Message-BR..............................................................................................................303
– BCCH-DL-SCH-Message-MBMS........................................................................................................303
– MCCH-Message...................................................................................................................................304
– PCCH-Message....................................................................................................................................304
– DL-CCCH-Message.............................................................................................................................304
– DL-DCCH-Message.............................................................................................................................305
– UL-CCCH-Message.............................................................................................................................305
– UL-DCCH-Message.............................................................................................................................306
– SC-MCCH-Message.............................................................................................................................306
6.2.2 Message definitions....................................................................................................................................307
– CounterCheck.......................................................................................................................................307
– CounterCheckResponse........................................................................................................................308
– CSFBParametersRequestCDMA2000..................................................................................................309
– CSFBParametersResponseCDMA2000...............................................................................................309
– DLInformationTransfer........................................................................................................................310
– FailureInformation...............................................................................................................................310
– HandoverFromEUTRAPreparationRequest (CDMA2000).................................................................311
– InDeviceCoexIndication.......................................................................................................................312
– InterFreqRSTDMeasurementIndication...............................................................................................315
– LoggedMeasurementConfiguration.....................................................................................................317
– MasterInformationBlock......................................................................................................................319
– MasterInformationBlock-MBMS..........................................................................................................320
– MBMSCountingRequest.......................................................................................................................320
– MBMSCountingResponse.....................................................................................................................321
– MBMSInterestIndication......................................................................................................................322
– MBSFNAreaConfiguration...................................................................................................................323
– MeasReportAppLayer...........................................................................................................................324
– MeasurementReport.............................................................................................................................324
– MobilityFromEUTRACommand...........................................................................................................325
– Paging..................................................................................................................................................328
– ProximityIndication..............................................................................................................................329
– RNReconfiguration...............................................................................................................................330
– RNReconfigurationComplete...............................................................................................................331
– RRCConnectionReconfiguration..........................................................................................................331
– RRCConnectionReconfigurationComplete...........................................................................................339
– RRCConnectionReestablishment..........................................................................................................341
– RRCConnectionReestablishmentComplete..........................................................................................341
– RRCConnectionReestablishmentReject................................................................................................342
– RRCConnectionReestablishmentRequest.............................................................................................343
– RRCConnectionReject..........................................................................................................................344
– RRCConnectionRelease.......................................................................................................................345
– RRCConnectionRequest.......................................................................................................................350
– RRCConnectionResume.......................................................................................................................351
– RRCConnectionResumeComplete........................................................................................................352
– RRCConnectionResumeRequest...........................................................................................................353
– RRCConnectionSetup...........................................................................................................................354
– RRCConnectionSetupComplete............................................................................................................354
– RRCEarlyDataComplete......................................................................................................................357
– RRCEarlyDataRequest.........................................................................................................................358
– SCGFailureInformation.......................................................................................................................359
– SCGFailureInformationNR..................................................................................................................360
– SCPTMConfiguration...........................................................................................................................360
– SCPTMConfiguration-BR....................................................................................................................361

3GPP
Release 15 12 3GPP TS 36.331 V15.4.0 (2018-12)

– SecurityModeCommand.......................................................................................................................362
– SecurityModeComplete........................................................................................................................362
– SecurityModeFailure............................................................................................................................363
– SidelinkUEInformation.........................................................................................................................363
– SystemInformation................................................................................................................................366
– SystemInformationBlockType1.............................................................................................................367
– SystemInformationBlockType1-MBMS................................................................................................375
– UEAssistanceInformation.....................................................................................................................377
– UECapabilityEnquiry...........................................................................................................................381
– UECapabilityInformation.....................................................................................................................382
– UEInformationRequest.........................................................................................................................383
– UEInformationResponse......................................................................................................................384
– ULHandoverPreparationTransfer (CDMA2000)................................................................................390
– ULInformationTransfer........................................................................................................................391
– ULInformationTransferMRDC.............................................................................................................392
– WLANConnectionStatusReport............................................................................................................392
6.3 RRC information elements..............................................................................................................................393
6.3.1 System information blocks.........................................................................................................................393
– SystemInformationBlockPos.................................................................................................................393
– SystemInformationBlockType2.............................................................................................................393
– SystemInformationBlockType3.............................................................................................................399
– SystemInformationBlockType4.............................................................................................................402
– SystemInformationBlockType5.............................................................................................................403
– SystemInformationBlockType6.............................................................................................................408
– SystemInformationBlockType7.............................................................................................................411
– SystemInformationBlockType8.............................................................................................................412
– SystemInformationBlockType9.............................................................................................................416
– SystemInformationBlockType10...........................................................................................................417
– SystemInformationBlockType11...........................................................................................................417
– SystemInformationBlockType12...........................................................................................................418
– SystemInformationBlockType13...........................................................................................................419
– SystemInformationBlockType14...........................................................................................................419
– SystemInformationBlockType15...........................................................................................................420
– SystemInformationBlockType16...........................................................................................................421
– SystemInformationBlockType17...........................................................................................................422
– SystemInformationBlockType18...........................................................................................................423
– SystemInformationBlockType19...........................................................................................................424
– SystemInformationBlockType20...........................................................................................................426
– SystemInformationBlockType21...........................................................................................................429
– SystemInformationBlockType24...........................................................................................................430
– SystemInformationBlockType25...........................................................................................................432
– SystemInformationBlockType26...........................................................................................................434
6.3.2 Radio resource control information elements............................................................................................435
– AntennaInfo..........................................................................................................................................435
– AntennaInfoUL.....................................................................................................................................438
– AUL-Config..........................................................................................................................................438
– CQI-ReportAperiodic...........................................................................................................................439
– CQI-ReportBoth...................................................................................................................................443
– CQI-ReportConfig................................................................................................................................444
– CQI-ReportPeriodic.............................................................................................................................447
– CQI-ReportPeriodicProcExtId.............................................................................................................451
– CrossCarrierSchedulingConfig............................................................................................................451
– CSI-IM-Config......................................................................................................................................452
– CSI-IM-ConfigId..................................................................................................................................453
– CSI-Process..........................................................................................................................................453
– CSI-ProcessId.......................................................................................................................................454
– CSI-RS-Config......................................................................................................................................455
– CSI-RS-ConfigBeamformed.................................................................................................................456
– CSI-RS-ConfigEMIMO.........................................................................................................................458
– CSI-RS-ConfigNonPrecoded................................................................................................................458
– CSI-RS-ConfigNZP...............................................................................................................................459

3GPP
Release 15 13 3GPP TS 36.331 V15.4.0 (2018-12)

– CSI-RS-ConfigNZPId...........................................................................................................................461
– CSI-RS-ConfigZP.................................................................................................................................461
– CSI-RS-ConfigZPId..............................................................................................................................462
– DataInactivityTimer.............................................................................................................................462
– DMRS-Config.......................................................................................................................................462
– DRB-Identity.........................................................................................................................................463
– EPDCCH-Config..................................................................................................................................463
– EIMTA-MainConfig.............................................................................................................................466
– LogicalChannelConfig.........................................................................................................................466
– LWA-Configuration..............................................................................................................................468
– LWIP-Configuration.............................................................................................................................469
– MAC-MainConfig.................................................................................................................................469
– P-C-AndCBSR......................................................................................................................................475
– PDCCH-ConfigSCell...........................................................................................................................476
– PDCP-Config.......................................................................................................................................477
– PDSCH-Config.....................................................................................................................................481
– PDSCH-RE-MappingQCL-ConfigId....................................................................................................485
– PerCC-GapIndicationList....................................................................................................................485
– PHICH-Config.....................................................................................................................................486
– PhysicalConfigDedicated.....................................................................................................................486
– P-Max...................................................................................................................................................497
– PRACH-Config.....................................................................................................................................498
– PresenceAntennaPort1.........................................................................................................................501
– PUCCH-Config....................................................................................................................................501
– PUSCH-Config.....................................................................................................................................506
– RACH-ConfigCommon.........................................................................................................................512
– RACH-ConfigDedicated.......................................................................................................................515
– RadioResourceConfigCommon............................................................................................................515
– RadioResourceConfigDedicated..........................................................................................................521
– RCLWI-Configuration..........................................................................................................................529
– RLC-Config..........................................................................................................................................530
– RLF-TimersAndConstants....................................................................................................................533
– RN-SubframeConfig.............................................................................................................................534
– SchedulingRequestConfig.....................................................................................................................536
– SlotOrSubslotPDSCH-Config..............................................................................................................537
– SlotOrSubslotPUSCH-Config..............................................................................................................538
– SoundingRS-UL-Config........................................................................................................................539
– SPDCCH-Config..................................................................................................................................542
– SPS-Config...........................................................................................................................................544
– SPUCCH-Config..................................................................................................................................550
– SRS-TPC-PDCCH-Config....................................................................................................................551
– TDD-Config..........................................................................................................................................552
– TimeAlignmentTimer............................................................................................................................553
– TimeReferenceInfo...............................................................................................................................553
– TPC-PDCCH-Config...........................................................................................................................554
– TunnelConfigLWIP...............................................................................................................................555
– UplinkPowerControl............................................................................................................................555
– WLAN-Id-List.......................................................................................................................................560
– WLAN-MobilityConfig.........................................................................................................................560
6.3.3 Security control information elements.......................................................................................................562
– NextHopChainingCount.......................................................................................................................562
– SecurityAlgorithmConfig......................................................................................................................562
– ShortMAC-I..........................................................................................................................................562
6.3.4 Mobility control information elements......................................................................................................563
– AdditionalSpectrumEmission...............................................................................................................563
– AdditionalSpectrumEmissionNR..........................................................................................................563
– ARFCN-ValueCDMA2000...................................................................................................................563
– ARFCN-ValueEUTRA..........................................................................................................................563
– ARFCN-ValueGERAN..........................................................................................................................564
– ARFCN-ValueNR.................................................................................................................................564
– ARFCN-ValueUTRA.............................................................................................................................564

3GPP
Release 15 14 3GPP TS 36.331 V15.4.0 (2018-12)

– BandclassCDMA2000..........................................................................................................................564
– BandIndicatorGERAN..........................................................................................................................565
– CarrierFreqCDMA2000.......................................................................................................................565
– CarrierFreqGERAN.............................................................................................................................565
– CarrierFreqsGERAN...........................................................................................................................565
– CarrierFreqListMBMS.........................................................................................................................566
– CDMA2000-Type.................................................................................................................................566
– CellIdentity...........................................................................................................................................567
– CellIndexList........................................................................................................................................567
– CellReselectionPriority........................................................................................................................567
– CellSelectionInfoCE.............................................................................................................................567
– CellSelectionInfoCE1...........................................................................................................................568
– CellReselectionSubPriority..................................................................................................................568
– CSFB-RegistrationParam1XRTT.........................................................................................................568
– CellGlobalIdEUTRA............................................................................................................................569
– CellGlobalIdUTRA...............................................................................................................................570
– CellGlobalIdGERAN............................................................................................................................570
– CellGlobalIdCDMA2000.....................................................................................................................570
– CellSelectionInfoNFreq........................................................................................................................571
– CSG-Identity.........................................................................................................................................571
– FreqBandIndicator...............................................................................................................................571
– FreqBandIndicatorNR..........................................................................................................................572
– MobilityControlInfo.............................................................................................................................572
– MobilityParametersCDMA2000 (1xRTT)............................................................................................575
– MobilityStateParameters......................................................................................................................576
– MultiBandInfoList................................................................................................................................576
– MultiFrequencyBandListNR.................................................................................................................576
– NS-PmaxList.........................................................................................................................................577
– NS-PmaxListNR....................................................................................................................................577
– PhysCellId............................................................................................................................................577
– PhysCellIdRange..................................................................................................................................578
– PhysCellIdRangeUTRA-FDDList........................................................................................................578
– PhysCellIdCDMA2000.........................................................................................................................578
– PhysCellIdGERAN...............................................................................................................................579
– PhysCellIdNR.......................................................................................................................................579
– PhysCellIdUTRA-FDD.........................................................................................................................579
– PhysCellIdUTRA-TDD.........................................................................................................................579
– PLMN-Identity......................................................................................................................................580
– PLMN-IdentityList3..............................................................................................................................580
– PmaxNR................................................................................................................................................580
– PreRegistrationInfoHRPD...................................................................................................................581
– Q-QualMin...........................................................................................................................................581
– Q-RxLevMin.........................................................................................................................................581
– Q-OffsetRange......................................................................................................................................582
– Q-OffsetRangeInterRAT.......................................................................................................................582
– ReselectionThreshold...........................................................................................................................582
– ReselectionThresholdQ........................................................................................................................582
– SCellIndex............................................................................................................................................582
– ServCellIndex.......................................................................................................................................583
– SpeedStateScaleFactors.......................................................................................................................583
– SystemInfoListGERAN.........................................................................................................................583
– SystemTimeInfoCDMA2000.................................................................................................................584
– ThresholdNR.........................................................................................................................................584
– TrackingAreaCode...............................................................................................................................585
– T-Reselection........................................................................................................................................585
– T-ReselectionEUTRA-CE.....................................................................................................................585
6.3.5 Measurement information elements...........................................................................................................585
– AllowedMeasBandwidth.......................................................................................................................585
– BT-NameList.........................................................................................................................................586
– CSI-RSRP-Range..................................................................................................................................586
– Hysteresis.............................................................................................................................................586

3GPP
Release 15 15 3GPP TS 36.331 V15.4.0 (2018-12)

– LocationInfo.........................................................................................................................................587
– LogMeasResultListBT..........................................................................................................................588
– LogMeasResultListWLAN....................................................................................................................588
– MBSFN-RSRQ-Range..........................................................................................................................588
– MeasConfig..........................................................................................................................................589
– MeasDS-Config....................................................................................................................................592
– MeasGapConfig...................................................................................................................................593
– MeasGapConfigDensePRS...................................................................................................................594
– MeasGapConfigPerCC-List.................................................................................................................595
– MeasGapSharingConfig.......................................................................................................................595
– MeasId..................................................................................................................................................596
– MeasIdleConfig....................................................................................................................................596
– MeasIdToAddModList..........................................................................................................................597
– MeasObjectCDMA2000.......................................................................................................................598
– MeasObjectEUTRA..............................................................................................................................598
– MeasObjectGERAN..............................................................................................................................602
– MeasObjectId.......................................................................................................................................602
– MeasObjectNR.....................................................................................................................................603
– MeasObjectToAddModList...................................................................................................................603
– MeasObjectUTRA.................................................................................................................................604
– MeasObjectWLAN................................................................................................................................605
– MeasResults..........................................................................................................................................606
– MeasScaleFactor..................................................................................................................................614
– MeasSensing-Config.............................................................................................................................614
– MTC-SSB-NR.......................................................................................................................................615
– QuantityConfig.....................................................................................................................................615
– ReportConfigEUTRA............................................................................................................................617
– ReportConfigId.....................................................................................................................................621
– ReportConfigInterRAT.........................................................................................................................622
– ReportConfigToAddModList................................................................................................................625
– ReportInterval......................................................................................................................................625
– RS-IndexNR..........................................................................................................................................626
– RSRP-Range.........................................................................................................................................626
– RSRP-RangeNR....................................................................................................................................627
– RSRQ-Range.........................................................................................................................................627
– RSRQ-RangeNR...................................................................................................................................627
– RSRQ-Type...........................................................................................................................................627
– RS-SINR-Range....................................................................................................................................628
– RS-SINR-RangeNR...............................................................................................................................628
– RSSI-Range-r13....................................................................................................................................628
– SS-RSSI-Measurement..........................................................................................................................628
– TimeToTrigger.....................................................................................................................................629
– UL-DelayConfig...................................................................................................................................629
– WLAN-CarrierInfo...............................................................................................................................629
– WLAN-NameList...................................................................................................................................630
– WLAN-RSSI-Range...............................................................................................................................630
– WLAN-RTT...........................................................................................................................................631
– WLAN-Status.......................................................................................................................................631
– WLAN-SuspendConfig..........................................................................................................................631
6.3.6 Other information elements.......................................................................................................................632
– AbsoluteTimeInfo.................................................................................................................................632
– AMF-Identifier.....................................................................................................................................632
– AreaConfiguration...............................................................................................................................632
– C-RNTI.................................................................................................................................................633
– DedicatedInfoCDMA2000....................................................................................................................633
– DedicatedInfoNAS................................................................................................................................633
– FilterCoefficient...................................................................................................................................634
– FlightPathInfoReportConfig................................................................................................................634
– GNSS-ID...............................................................................................................................................634
– I-RNTI...................................................................................................................................................634
– LoggingDuration..................................................................................................................................635

3GPP
Release 15 16 3GPP TS 36.331 V15.4.0 (2018-12)

– LoggingInterval....................................................................................................................................635
– MeasSubframePattern..........................................................................................................................635
– MMEC..................................................................................................................................................635
– NeighCellConfig...................................................................................................................................636
– NG-5G-S-TMSI.....................................................................................................................................636
– OtherConfig..........................................................................................................................................636
– RAN-AreaCode.....................................................................................................................................639
– RAND-CDMA2000 (1xRTT)................................................................................................................639
– RAT-Type..............................................................................................................................................639
– ResumeIdentity.....................................................................................................................................639
– RRC-TransactionIdentifier...................................................................................................................640
– SBAS-ID...............................................................................................................................................640
– ShortI-RNTI..........................................................................................................................................640
– S-NSSAI................................................................................................................................................640
– S-TMSI..................................................................................................................................................641
– TraceReference.....................................................................................................................................641
– UE-CapabilityRAT-ContainerList........................................................................................................641
– UE-EUTRA-Capability.........................................................................................................................642
– UE-RadioPagingInfo............................................................................................................................697
– UE-TimersAndConstants......................................................................................................................698
– VisitedCellInfoList................................................................................................................................699
– WLAN-OffloadConfig...........................................................................................................................699
6.3.7 MBMS information elements.....................................................................................................................701
– MBMS-NotificationConfig...................................................................................................................701
– MBMS-ServiceList................................................................................................................................702
– MBSFN-AreaId.....................................................................................................................................702
– MBSFN-AreaInfoList...........................................................................................................................702
– MBSFN-SubframeConfig.....................................................................................................................703
– PMCH-InfoList.....................................................................................................................................704
6.3.7a SC-PTM information elements..................................................................................................................706
– SC-MTCH-InfoList...............................................................................................................................706
– SC-MTCH-InfoList-BR.........................................................................................................................707
– SCPTM-NeighbourCellList..................................................................................................................709
6.3.8 Sidelink information elements...................................................................................................................710
– SL-AnchorCarrierFreqList-V2X..........................................................................................................710
– SL-CBR-CommonTxConfigList............................................................................................................710
– SL-CBR-PPPP-TxConfigList...............................................................................................................711
– SL-CommConfig...................................................................................................................................712
– SL-CommResourcePool.......................................................................................................................713
– SL-CommTxPoolSensingConfig...........................................................................................................717
– SL-CP-Len............................................................................................................................................718
– SL-DiscConfig......................................................................................................................................718
– SL-DiscResourcePool...........................................................................................................................721
– SL-DiscSysInfoReport..........................................................................................................................722
– SL-DiscTxPowerInfo............................................................................................................................723
– SL-GapConfig.......................................................................................................................................723
– SL-GapRequest.....................................................................................................................................724
– SL-HoppingConfig...............................................................................................................................724
– SL-InterFreqInfoListV2X.....................................................................................................................725
– SL-V2X-UE-ConfigList.........................................................................................................................726
– SL-OffsetIndicator................................................................................................................................727
– SL-P2X-ResourceSelectionConfig........................................................................................................728
– SL-PeriodComm...................................................................................................................................728
– SL-Priority............................................................................................................................................728
– SL-PSSCH-TxConfigList......................................................................................................................728
– SL-RestrictResourceReservationPeriodList.........................................................................................730
– SLSSID.................................................................................................................................................730
– SL-SyncAllowed....................................................................................................................................730
– SL-SyncConfig......................................................................................................................................731
– SL-TF-ResourceConfig.........................................................................................................................733
– SL-TxPower..........................................................................................................................................734

3GPP
Release 15 17 3GPP TS 36.331 V15.4.0 (2018-12)

– SL-TypeTxSync.....................................................................................................................................734
– SL-ThresPSSCH-RSRP-List.................................................................................................................734
– SL-TxParameters..................................................................................................................................735
– SL-TxPoolIdentity.................................................................................................................................735
– SL-TxPoolToReleaseList......................................................................................................................736
– SL-V2X-ConfigDedicated.....................................................................................................................736
– SL-V2X-FreqSelectionConfigList.........................................................................................................738
– SL-V2X-PacketDuplicationConfig.......................................................................................................738
– SL-V2X-SyncFreqList...........................................................................................................................739
– SL-ZoneConfig.....................................................................................................................................739
6.4 RRC multiplicity and type constraint values...................................................................................................739
– Multiplicity and type constraint definitions...............................................................................................739
– End of EUTRA-RRC-Definitions..............................................................................................................743
6.5 PC5 RRC messages.........................................................................................................................................743
6.5.1 General message structure.........................................................................................................................743
– PC5-RRC-Definitions...........................................................................................................................743
– SBCCH-SL-BCH-Message...................................................................................................................743
– SBCCH-SL-BCH-Message-V2X...........................................................................................................744
6.5.2 Message definitions....................................................................................................................................744
– MasterInformationBlock-SL.................................................................................................................744
– MasterInformationBlock-SL-V2X.........................................................................................................745
– End of PC5-RRC-Definitions...............................................................................................................745
6.6 Direct Indication Information..........................................................................................................................745
6.6a Direct Indication FeMBMS.............................................................................................................................746
6.7 NB-IoT RRC messages...................................................................................................................................746
6.7.1 General NB-IoT message structure............................................................................................................746
– BCCH-BCH-Message-NB....................................................................................................................747
– BCCH-BCH-Message-TDD-NB...........................................................................................................747
– BCCH-DL-SCH-Message-NB..............................................................................................................747
– PCCH-Message-NB.............................................................................................................................748
– DL-CCCH-Message-NB.......................................................................................................................748
– DL-DCCH-Message-NB.......................................................................................................................748
– UL-CCCH-Message-NB.......................................................................................................................749
– SC-MCCH-Message-NB.......................................................................................................................749
– UL-DCCH-Message-NB.......................................................................................................................749
6.7.2 NB-IoT Message definitions......................................................................................................................750
– DLInformationTransfer-NB.................................................................................................................750
– MasterInformationBlock-NB................................................................................................................750
– MasterInformationBlock-TDD-NB.......................................................................................................752
– Paging-NB............................................................................................................................................755
– RRCConnectionReconfiguration-NB...................................................................................................756
– RRCConnectionReconfigurationComplete-NB....................................................................................756
– RRCConnectionReestablishment-NB...................................................................................................757
– RRCConnectionReestablishmentComplete-NB....................................................................................758
– RRCConnectionReestablishmentRequest-NB.......................................................................................758
– RRCConnectionReject-NB...................................................................................................................759
– RRCConnectionRelease-NB.................................................................................................................760
– RRCConnectionRequest-NB.................................................................................................................761
– RRCConnectionResume-NB.................................................................................................................762
– RRCConnectionResumeComplete-NB..................................................................................................763
– RRCConnectionResumeRequest-NB....................................................................................................764
– RRCConnectionSetup-NB.....................................................................................................................764
– RRCConnectionSetupComplete-NB.....................................................................................................765
– RRCEarlyDataComplete-NB................................................................................................................766
– RRCEarlyDataRequest-NB..................................................................................................................767
– SCPTMConfiguration-NB....................................................................................................................767
– SystemInformation-NB.........................................................................................................................768
– SystemInformationBlockType1-NB......................................................................................................768
– UECapabilityEnquiry-NB....................................................................................................................772
– UECapabilityInformation-NB..............................................................................................................773
– ULInformationTransfer-NB.................................................................................................................774

3GPP
Release 15 18 3GPP TS 36.331 V15.4.0 (2018-12)

6.7.3 NB-IoT information elements....................................................................................................................774

6.7.3.1 NB-IoT System information blocks.....................................................................................................774
– SystemInformationBlockType2-NB......................................................................................................774
– SystemInformationBlockType3-NB......................................................................................................775
– SystemInformationBlockType4-NB......................................................................................................777
– SystemInformationBlockType5-NB......................................................................................................778
– SystemInformationBlockType14-NB....................................................................................................779
– SystemInformationBlockType15-NB....................................................................................................780
– SystemInformationBlockType16-NB....................................................................................................781
– SystemInformationBlockType20-NB....................................................................................................781
– SystemInformationBlockType22-NB....................................................................................................783
– SystemInformationBlockType23-NB..................................................................................................786
6.7.3.2 NB-IoT Radio resource control information elements.........................................................................787
– CarrierConfigDedicated-NB................................................................................................................787
– CarrierFreq-NB...................................................................................................................................789
– DL-Bitmap-NB.....................................................................................................................................789
– DL-CarrierConfigCommon-NB...........................................................................................................790
– DL-GapConfig-NB...............................................................................................................................791
– LogicalChannelConfig-NB...................................................................................................................791
– MAC-MainConfig-NB..........................................................................................................................792
– NPDCCH-ConfigDedicated-NB...........................................................................................................793
– NPDSCH-ConfigCommon-NB.............................................................................................................794
– NPRACH-ConfigSIB-NB......................................................................................................................794
– NPUSCH-Config-NB............................................................................................................................800
– PDCP-Config-NB.................................................................................................................................801
– PhysicalConfigDedicated-NB..............................................................................................................802
– RACH-ConfigCommon-NB..................................................................................................................803
– RadioResourceConfigCommonSIB-NB................................................................................................804
– RadioResourceConfigDedicated-NB....................................................................................................805
– RLC-Config-NB....................................................................................................................................807
– RLF-TimersAndConstants-NB.............................................................................................................807
– SchedulingRequestConfig-NB..............................................................................................................808
– UplinkPowerControl-NB......................................................................................................................810
– WUS-Config-NB...................................................................................................................................811
6.7.3.3 NB-IoT Security control information elements....................................................................................812
6.7.3.4 NB-IoT Mobility control information elements...................................................................................812
– AdditionalBandInfoList-NB..................................................................................................................812
– FreqBandIndicator-NB........................................................................................................................812
– MultiBandInfoList-NB..........................................................................................................................813
– NS-PmaxList-NB.................................................................................................................................813
– T-Reselection-NB.................................................................................................................................813
6.7.3.5 NB-IoT Measurement information elements.......................................................................................814
– CQI-NPDCCH-NB...............................................................................................................................814
– CQI-NPDCCH-Short-NB.....................................................................................................................814
– MeasResultServCell-NB.......................................................................................................................814
– NSSS-RRM-Config-NB.........................................................................................................................815
6.7.3.6 NB-IoT Other information elements....................................................................................................815
– EstablishmentCause-NB.......................................................................................................................815
– UE-Capability-NB................................................................................................................................816
– UE-RadioPagingInfo-NB.....................................................................................................................819
– UE-TimersAndConstants-NB...............................................................................................................820
6.7.3.7 NB-IoT MBMS information elements.................................................................................................821
6.7.3.7a NB-IoT SC-PTM information elements...............................................................................................821
– SC-MTCH-InfoList-NB.........................................................................................................................821
– SCPTM-NeighbourCellList-NB............................................................................................................822
6.7.4 NB-IoT RRC multiplicity and type constraint values................................................................................823
– Multiplicity and type constraint definitions...............................................................................................823
– End of NBIOT-RRC-Definitions...............................................................................................................823
6.7.5 Direct Indication Information....................................................................................................................823
7 Variables and constants......................................................................................................................824
7.1 UE variables....................................................................................................................................................824

3GPP
Release 15 19 3GPP TS 36.331 V15.4.0 (2018-12)

– EUTRA-UE-Variables..........................................................................................................................824
– VarConnEstFailReport.........................................................................................................................825
– VarLogMeasConfig..............................................................................................................................825
– VarLogMeasReport..............................................................................................................................826
– VarMeasConfig....................................................................................................................................826
– VarMeasIdleConfig..............................................................................................................................827
– VarMeasIdleReport..............................................................................................................................827
– VarMeasReportList..............................................................................................................................827
– VarMobilityHistoryReport...................................................................................................................828
– VarPendingRnaUpdate........................................................................................................................828
– VarRLF-Report.....................................................................................................................................828
– VarShortINACTIVE-MAC-Input..........................................................................................................828
– VarShortMAC-Input.............................................................................................................................829
– VarShortResumeMAC-Input.................................................................................................................829
– VarWLAN-MobilityConfig...................................................................................................................830
– VarWLAN-Status..................................................................................................................................830
– Multiplicity and type constraint definitions.........................................................................................830
– End of EUTRA-UE-Variables..............................................................................................................831
7.1a NB-IoT UE variables.......................................................................................................................................831
– NBIOT-UE-Variables...........................................................................................................................831
– End of NBIOT-UE-Variables...............................................................................................................831
7.2 Counters...........................................................................................................................................................831
7.3 Timers..............................................................................................................................................................832
7.3.1 Timers (Informative)..................................................................................................................................832
7.3.2 Timer handling...........................................................................................................................................835
7.4 Constants.........................................................................................................................................................835
8 Protocol data unit abstract syntax.......................................................................................................836
8.1 General.............................................................................................................................................................836
8.2 Structure of encoded RRC messages...............................................................................................................836
8.3 Basic production..............................................................................................................................................836
8.4 Extension.........................................................................................................................................................836
8.5 Padding............................................................................................................................................................837
9 Specified and default radio configurations.........................................................................................837
9.1 Specified configurations..................................................................................................................................837
9.1.1 Logical channel configurations..................................................................................................................837
9.1.1.1 BCCH configuration............................................................................................................................837
9.1.1.2 CCCH configuration............................................................................................................................838
9.1.1.3 PCCH configuration.............................................................................................................................838
9.1.1.4 MCCH and MTCH configuration........................................................................................................838
9.1.1.5 SBCCH configuration..........................................................................................................................838
9.1.1.6 STCH configuration.............................................................................................................................839
9.1.1.7 SC-MCCH and SC-MTCH configuration............................................................................................839
9.1.1.8 BR-BCCH configuration......................................................................................................................839
9.1.2 SRB configurations....................................................................................................................................840
9.1.2.1 SRB1....................................................................................................................................................840
9.1.2.1a SRB1bis................................................................................................................................................840
9.1.2.2 SRB2....................................................................................................................................................840
9.1.2.3 SRB4....................................................................................................................................................840
9.2 Default radio configurations............................................................................................................................840
9.2.1 SRB configurations....................................................................................................................................841
9.2.1.1 SRB1....................................................................................................................................................841
9.2.1.2 SRB2....................................................................................................................................................841
9.2.2 Default MAC main configuration..............................................................................................................842
9.2.3 Default semi-persistent scheduling configuration......................................................................................842
9.2.4 Default physical channel configuration.....................................................................................................842
9.2.5 Default values timers and constants...........................................................................................................844
9.3 Sidelink pre-configured parameters.................................................................................................................844
9.3.1 Specified parameters..................................................................................................................................844
9.3.2 Pre-configurable parameters......................................................................................................................844
– SL-Preconfiguration.............................................................................................................................845

3GPP
Release 15 20 3GPP TS 36.331 V15.4.0 (2018-12)

– SL-V2X-Preconfiguration.....................................................................................................................847
10 Radio information related interactions between network nodes..........................................................851
10.1 General.............................................................................................................................................................851
10.2 Inter-node RRC messages...............................................................................................................................851
10.2.1 General.......................................................................................................................................................851
– EUTRA-InterNodeDefinitions....................................................................................................................851
10.2.2 Message definitions....................................................................................................................................852
– HandoverCommand.............................................................................................................................852
– HandoverPreparationInformation.......................................................................................................853
– SCG-Config..........................................................................................................................................855
– SCG-ConfigInfo....................................................................................................................................856
– UEPagingCoverageInformation..........................................................................................................859
– UERadioAccessCapabilityInformation................................................................................................860
– UERadioPagingInformation................................................................................................................860
10.3 Inter-node RRC information element definitions............................................................................................861
– AS-Config.............................................................................................................................................861
– AS-Context............................................................................................................................................863
– ReestablishmentInfo.............................................................................................................................864
– RRM-Config.........................................................................................................................................865
10.4 Inter-node RRC multiplicity and type constraint values.................................................................................866
– Multiplicity and type constraints definitions.............................................................................................866
– End of EUTRA-InterNodeDefinitions........................................................................................................866
10.5 Mandatory information in AS-Config..............................................................................................................866
10.6 Inter-node NB-IoT messages...........................................................................................................................867
10.6.1 General.......................................................................................................................................................867
– NB-IoT-InterNodeDefinitions....................................................................................................................867
10.6.2 Message definitions....................................................................................................................................867
– HandoverPreparationInformation-NB.................................................................................................867
– UEPagingCoverageInformation-NB....................................................................................................868
– UERadioAccessCapabilityInformation-NB..........................................................................................869
– UERadioPagingInformation-NB..........................................................................................................869
10.7 Inter-node NB-IoT RRC information element definitions..............................................................................870
– AS-Config-NB.......................................................................................................................................870
– AS-Context-NB.....................................................................................................................................870
– ReestablishmentInfo-NB.......................................................................................................................871
– RRM-Config-NB...................................................................................................................................871
10.8 Inter-node RRC multiplicity and type constraint values.................................................................................872
– Multiplicity and type constraints definitions.............................................................................................872
– End of NB-IoT-InterNodeDefinitions.........................................................................................................872
10.9 Mandatory information in AS-Config-NB........................................................................................................872
11 UE capability related constraints and performance requirements.......................................................872
11.1 UE capability related constraints.....................................................................................................................872
11.2 Processing delay requirements for RRC procedures.......................................................................................873
11.3 Void.................................................................................................................................................................876

Annex A (informative): Guidelines, mainly on use of ASN.1...........................................................876

A.1 Introduction.....................................................................................................................................................876
A.2 Procedural specification...................................................................................................................................876
A.2.1 General principles......................................................................................................................................876
A.2.2 More detailed aspects.................................................................................................................................877
A.3 PDU specification............................................................................................................................................877
A.3.1 General principles......................................................................................................................................877
A.3.1.1 ASN.1 sections.....................................................................................................................................877
A.3.1.2 ASN.1 identifier naming conventions..................................................................................................877
A.3.1.3 Text references using ASN.1 identifiers..............................................................................................879
A.3.2 High-level message structure.....................................................................................................................879
A.3.3 Message definition.....................................................................................................................................880
A.3.4 Information elements.................................................................................................................................881
A.3.5 Fields with optional presence.....................................................................................................................882
A.3.6 Fields with conditional presence................................................................................................................883

3GPP
Release 15 21 3GPP TS 36.331 V15.4.0 (2018-12)

A.3.7 Guidelines on use of lists with elements of SEQUENCE type..................................................................883

A.4 Extension of the PDU specifications...............................................................................................................884
A.4.1 General principles to ensure compatibility................................................................................................884
A.4.2 Critical extension of messages and fields..................................................................................................884
A.4.3 Non-critical extension of messages............................................................................................................886
A.4.3.1 General principles................................................................................................................................886
A.4.3.2 Further guidelines.................................................................................................................................886
A.4.3.3 Typical example of evolution of IE with local extensions...................................................................887
A.4.3.4 Typical examples of non critical extension at the end of a message....................................................888
A.4.3.5 Examples of non-critical extensions not placed at the default extension location...............................889
– ParentIE-WithEM.................................................................................................................................889
– ChildIE1-WithoutEM...........................................................................................................................889
– ChildIE2-WithoutEM...........................................................................................................................890
A.5 Guidelines regarding inclusion of transaction identifiers in RRC messages...................................................891
A.6 Protection of RRC messages (informative).....................................................................................................891
A.7 Miscellaneous..................................................................................................................................................893

Annex B (normative): Release 8 and 9 AS feature handling.........................................................894

B.1 Feature group indicators..................................................................................................................................894
B.2 CSG support....................................................................................................................................................902

Annex C (normative): Release 10 AS feature handling.................................................................903

C.1 Feature group indicators..................................................................................................................................903

Annex D (informative): Descriptive background information........................................................906

D.1 Signalling of Multiple Frequency Band Indicators (Multiple FBI).................................................................906
D.1.1 Mapping between frequency band indicator and multiple frequency band indicator................................906
D.1.2 Mapping between inter-frequency neighbour list and multiple frequency band indicator........................906
D.1.3 Mapping between UTRA FDD frequency list and multiple frequency band indicator.............................907

Annex E (normative): TDD/FDD differentiation of FGIs/capabilities in TDD-FDD CA............909

Annex F (normative): UE requirements on ASN.1 comprehension.............................................910
Annex G (normative): List of CRs Containing Early Implementable Features and
Corrections..................................................................................................911
Annex H (informative): Change history..............................................................................................912

3GPP
Release 15 22 3GPP TS 36.331 V15.4.0 (2018-12)

Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:

Version x.y.z

where:

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.

z the third digit is incremented when editorial only changes have been incorporated in the document.

3GPP
Release 15 23 3GPP TS 36.331 V15.4.0 (2018-12)

1 Scope
The present document specifies the Radio Resource Control protocol for the radio interface between UE and E-UTRAN
as well as for the radio interface between RN and E-UTRAN.

The scope of the present document also includes:

- the radio related information transported in a transparent container between source eNB and target eNB upon
inter eNB handover;

- the radio related information transported in a transparent container between a source or target eNB and another
system upon inter RAT handover.

2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.

- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.

- For a specific reference, subsequent revisions do not apply.

- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[2] Void.

[3] 3GPP TS 36.302: "Evolved Universal Terrestrial Radio Access (E-UTRA); Services provided by
the physical layer ".

[4] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); UE Procedures in Idle
Mode".

[5] 3GPP TS 36.306 "Evolved Universal Terrestrial Radio Access (E-UTRA); UE Radio Access
Capabilities".

[6] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access
Control (MAC) protocol specification".

[7] 3GPP TS 36.322:"Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control
(RLC) protocol specification".

[8] 3GPP TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data
Convergence Protocol (PDCP) Specification".

[9] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2".

[10] 3GPP TS 22.011: "Service accessibility".

[11] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle
mode".

[12] 3GPP2 C.S0002-F v1.0: "Physical Layer Standard for cdma2000 Spread Spectrum Systems".

[13] ITU-T Recommendation X.680 (07/2002) "Information Technology - Abstract Syntax Notation
One (ASN.1): Specification of basic notation" (Same as the ISO/IEC International Standard 8824-
1).

3GPP
Release 15 24 3GPP TS 36.331 V15.4.0 (2018-12)

[14] ITU-T Recommendation X.681 (07/2002) "Information Technology - Abstract Syntax Notation
One (ASN.1): Information object specification" (Same as the ISO/IEC International Standard
8824-2).

[15] ITU-T Recommendation X.691 (07/2002) "Information technology - ASN.1 encoding rules:
Specification of Packed Encoding Rules (PER)" (Same as the ISO/IEC International Standard
8825-2).

[16] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management".

[17] 3GPP TS 25.101: "Universal Terrestrial Radio Access (UTRA); User Equipment (UE) radio
transmission and reception (FDD)".

[18] 3GPP TS 25.102: "Universal Terrestrial Radio Access (UTRA); User Equipment (UE) radio
transmission and reception (TDD)".

[19] 3GPP TS 25.331:"Universal Terrestrial Radio Access (UTRA); Radio Resource Control (RRC);
Protocol specification".

[20] 3GPP TS 45.005: "Radio transmission and reception".

[21] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and
Modulation".

[22] 3GPP TS 36.212: "Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and
channel coding".

[23] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures".

[24] 3GPP2 C.S0057-E v1.0: "Band Class Specification for cdma2000 Spread Spectrum Systems".

[25] 3GPP2 C.S0005-F v1.0: "Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread
Spectrum Systems".

[26] 3GPP2 C.S0024-C v2.0: "cdma2000 High Rate Packet Data Air Interface Specification".

[27] 3GPP TS 23.003: "Numbering, addressing and identification".

[28] 3GPP TS 45.008: "Radio subsystem link control".

[29] 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)".

[30] 3GPP TS 25.123: "Requirements for Support of Radio Resource Management (TDD)".

[31] 3GPP TS 36.401: "Evolved Universal Terrestrial Radio Access (E-UTRA); Architecture
description".

[32] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".

[33] 3GPP2 A.S0008-C v4.0: "Interoperability Specification (IOS) for High Rate Packet Data (HRPD)
Radio Access Network Interfaces with Session Control in the Access Network"

[34] 3GPP2 C.S0004-F v1.0: "Signaling Link Access Control (LAC) Standard for cdma2000 Spread
Spectrum Systems"

[35] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage
3".

[36] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station
System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".

[37] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".

[38] 3GPP TS 23.038: "Alphabets and Language".

3GPP
Release 15 25 3GPP TS 36.331 V15.4.0 (2018-12)

[39] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access (E-UTRAN); S1 Application

Protocol (S1 AP)".

[40] 3GPP TS 25.304: "Universal Terrestrial Radio Access (UTRAN); User Equipment (UE)
procedures in idle mode and procedures for cell reselection in connected mode".

[41] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) access".

[42] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
radio transmission and reception".

[43] 3GPP TS 45.005: "GSM/EDGE Radio transmission and reception".

[44] 3GPP2 C.S0087-A v2.0: "E-UTRAN - cdma2000 HRPD Connectivity and Interworking Air
Interface Specification"

[45] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC)
protocol".

[46] 3GPP TS 25.223: "Spreading and modulation (TDD)".

[47] 3GPP TS 36.104: "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS)
radio transmission and reception".

[48] 3GPP TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer -
Measurements".

[49] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3".

[50] 3GPP TS 45.010:"Radio subsystem synchronization".

[51] 3GPP TS 23.272: "Circuit Switched Fallback in Evolved Packet System; Stage 2".

[52] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting
packet based services and Packet Data Networks (PDN)".

[53] 3GPP2 C.S0097-0 v3.0: "E-UTRAN - cdma2000 1x Connectivity and Interworking Air Interface
Specification".

[54] 3GPP TS 36.355: "LTE Positioning Protocol (LPP)".

[55] 3GPP TS 36.216: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer for
relaying operation".

[56] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional
description".

[57] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".

[58] 3GPP TS 32.422: "Telecommunication management; Subsriber and equipment trace; Trace control
and confiuration management".

[59] 3GPP TS 22.368: "Service Requirements for Machine Type Communications; Stage 1".

[60] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial
Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT);
Overall description; Stage 2".

[61] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".

[62] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service (MBMS); Stage 1".

[63] 3GPP TR 36.816: "Evolved Universal Terrestrial Radio Access (E-UTRA); Study on signalling
and procedure for interference avoidance for in-device coexistence".

[64] IS-GPS-200F: "Navstar GPS Space Segment/Navigation User Segment Interfaces".

3GPP
Release 15 26 3GPP TS 36.331 V15.4.0 (2018-12)

[65] 3GPP TS 25.307: "Requirement on User Equipments (UEs) supporting a release-independent

frequency band".

[66] 3GPP TS 24.312: "Access Network Discovery and Selection Function (ANDSF) Management
Object (MO)".

[67] IEEE 802.11-2012, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer
(PHY) specifications, IEEE Std.

[68] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2".

[69] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol
aspects; Stage 3".

[70] 3GPP TS 24.333: "Proximity-services (ProSe) Management Objects (MO)".

[71] 3GPP TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2-
Measurements".

[72] 3GPP TS 24.105: "Application specific Congestion control for Data Communication (ACDC)
Management Object (MO)".

[73] 3GPP TS 23.179: "Functional architecture and information flows to support mission critical
communication services; Stage 2".

[74] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access
networks".

[75] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses; Stage-2".

[76] Wi-Fi Alliance® Technical Committee, Hotspot 2.0 Technical Task Group Hotspot 2.0 (Release
2) Technical Specification Version 3.11.

[77] 3GPP TS 22.101: "Service aspects; Service principles".

[78] 3GPP TS 23.285: "Technical Specification Group Services and System Aspects; Architecture
enhancements for V2X services".

[79] 3GPP TS 36.307: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements on User
Equipments (UEs) supporting a release-independent frequency band".

[80] Military Standard WGS84 Metric MIL-STD-2401 (11 January 1994): "Military Standard
Department of Defence World Geodetic System (WGS)".

[81] 3GPP TS 37.340: "NR; Multi-connectivity; Overall description; Stage-2".

[82] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".

[83] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) Specification".

[84] 3GPP TS 38.133: "NR; Requirements for support of radio resource management".

[85] 3GPP TS 38.101: "NR; User Equipment (UE) radio transmission and reception".

[86] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System".

[87] 3GPP TS 38.306: "NR; UE Radio Access Capabilities".

[88] 3GPP TS 38.213: "NR; Physical layer procedures".

[89] 3GPP TS 38.215: "NR; Physical layer measurements".

[90] 3GPP TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive
Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".

[91] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception".

3GPP
Release 15 27 3GPP TS 36.331 V15.4.0 (2018-12)

[92] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state".

[93] Bluetooth Special Interest Group: "Bluetooth Core Specification v5.0", December 2016.

[94] 3GPP TS 37.213: "Physical layer procedures for shared spectrum channel access".

[95] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".

[96] 3GPP TS 22.261: "Service requirements for the 5G System".

[97] 3GPP TS 37.324: "Service Data Adaptation Protocol (SDAP) specification".

[98] ATIS 0700041: "WEA 3.0: Device-Based Geo-Fencing".

3 Definitions, symbols and abbreviations

3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].

Anchor carrier: In NB-IoT, a carrier where the UE assumes that NPSS/NSSS/NPBCH/SIB-NB for FDD or
NPSS/NSSS/NPBCH for TDD are transmitted.

Bandwidth Reduced: Refers to operation in downlink and uplink with a limited channel bandwidth of 6 PRBs.

Cellular IoT EPS Optimisation: Provides improved support of small data transfer, as defined in TS 24.301 [35].

Commercial Mobile Alert System: Public Warning System that delivers Warning Notifications provided by Warning
Notification Providers to CMAS capable UEs.

Common access barring parameters: The common access barring parameters refer to the access class barring
parameters that are broadcast in SystemInformationBlockType2 outside the list of PLMN specific parameters (i.e. in ac-
BarringPerPLMN-List).

Control plane CIoT EPS optimisation: Enables support of efficient transport of user data (IP, non-IP or SMS) over
control plane via the MME without triggering data radio bearer establishment, as defined in TS 24.301 [35].

Control plane EDT: Early Data Transmission used with the Control plane CIoT EPS optimisation.

CSG member cell: A cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN and
for which the CSG whitelist of the UE includes an entry comprising cell's CSG ID and the respective PLMN identity.

Dual Connectivity: A UE in RRC_CONNECTED is configured with Dual Connectivity when configured with a
Master and a Secondary Cell Group.

Early Data Transmission: Allows one uplink data transmission optionally followed by one downlink data
transmission during the random access procedure as specified in TS 36.300 [9]. The S1 connection is established or
resumed upon reception of the uplink data and may be released or suspended along with the transmission of the
downlink data. Early data transmission refers to both CP-EDT and UP-EDT.

E-UTRA-NR Dual Connectivity: A form of dual connectivity, defined in TS 37.340 [81], in which a UE in
RRC_CONNECTED is configured with MCG cells using E-UTRA and SCG cells using NR as defined in TS 37.340
[81].

EU-Alert: Public Warning System that delivers Warning Notifications provided by Warning Notification Providers
using the same AS mechanisms as defined for CMAS.

Field: The individual contents of an information element are referred as fields.

Floor: Mathematical function used to 'round down' i.e. to the nearest integer having a lower or equal value.

Information element: A structural element containing a single or multiple fields is referred as information element.

3GPP
Release 15 28 3GPP TS 36.331 V15.4.0 (2018-12)

Korean Public Alert System (KPAS): Public Warning System that delivers Warning Notifications provided by
Warning Notification Providers using the same AS mechanisms as defined for CMAS.

Master Cell Group: For a UE not configured with DC, the MCG comprises all serving cells. For a UE configured with
DC, the MCG concerns a subset of the serving cells comprising of the PCell and zero or more secondary cells.

Mixed Operation Mode: In NB-IoT FDD, multi-carrier operation where the anchor carrier is in standalone mode while
the non-anchor carrier is in inband or guardand mode, and vice versa. See TS 36.300 [9].

MBMS service: MBMS bearer service as defined in TS 23.246 [56] (i.e. provided via an MRB or an SC-MRB).

NB-IoT: NB-IoT allows access to network services via E-UTRA with a channel bandwidth limited to 200 kHz.

NB-IoT UE: A UE that uses NB-IoT.

NCSG: Network controlled small gap as defined in TS 36.133 [16].

Non-anchor carrier: In NB-IoT, a carrier where the UE does not assume that NPSS/NSSS/NPBCH/SIB-NB for FDD
or NPSS/NSSS/NPBCH for TDD are transmitted.

NR Carrier Frequency: Frequency referring to the position of resource element RE=#0 (subcarrier #0) of resource
block RB#10 of the SS block.

Primary Cell: The cell, operating on the primary frequency, in which the UE either performs the initial connection
establishment procedure or initiates the connection re-establishment procedure, or the cell indicated as the primary cell
in the handover procedure.

Primary Secondary Cell: The SCG cell in which the UE is instructed to perform random access or initial PUSCH
transmission if random access procedure is skipped when performing the SCG change procedure.

Primary Timing Advance Group: Timing Advance Group containing the PCell or the PSCell.

PUCCH SCell: An SCell configured with PUCCH.

RLC bearer configuration: The lower layer part of the radio bearer configuration comprising the RLC and logical
channel configurations.

Secondary Cell: A cell, operating on a secondary frequency, which may be configured once an RRC connection is
established and which may be used to provide additional radio resources. Except for the case of EN-DC, the PSCell is
considered to be an SCell.

Secondary Cell Group: For a UE configured with DC, the subset of serving cells not part of the MCG, i.e. comprising
of the PSCell and zero or more other secondary cells.

Secondary Timing Advance Group: Timing Advance Group neither containing the PCell nor the PSCell. A secondary
timing advance group contains at least one cell with configured uplink.

Serving Cell: For a UE in RRC_CONNECTED not configured with CA/ DC there is only one serving cell comprising
of the primary cell. For a UE in RRC_CONNECTED configured with CA/ DC the term 'serving cells' is used to denote
the set of one or more cells comprising of the primary cell and all secondary cells.

Sidelink: UE to UE interface for sidelink communication, V2X sidelink communication and sidelink discovery. The
sidelink corresponds to the PC5 interface as defined in TS 23.303 [68].

Sidelink communication: AS functionality enabling ProSe Direct Communication as defined in TS 23.303 [68],
between two or more nearby UEs, using E-UTRA technology but not traversing any network node. In this version, the
terminology "sidelink communication" without "V2X" prefix only concerns PS unless specifically stated otherwise.

Sidelink discovery: AS functionality enabling ProSe Direct Discovery as defined in TS 23.303 [68], using E-UTRA
technology but not traversing any network node.

Sidelink operation: Includes sidelink communication, V2X sidelink communication and sidelink discovery.

Split SRB: in MR-DC, an SRB between the MN and the UE, allowing selection of either the direct path or the path via
the SN as well as duplication of RRC PDUs across both paths as defined in TS 37.340 [81].

3GPP
Release 15 29 3GPP TS 36.331 V15.4.0 (2018-12)

Timing Advance Group: A group of serving cells that is configured by RRC and that, for the cells with an UL
configured, use the same timing reference cell and the same Timing Advance value. A Timing Advance Group only
includes cells of the same cell group i.e. it either includes MCG cells or SCG cells.

UE Inactive AS Context: UE Inactive AS Context is stored when the connection is suspended and restored when the
connection is resumed. It includes information as defined in subclause 5.3.8.7.

UE in CE: Refers to a UE that is capable of using coverage enhancement, and requires coverage enhancement mode to
access a cell or is configured in a coverage enhancement mode.

User plane CIoT EPS optimisation: Enables support for change from EMM-IDLE mode to EMM-CONNECTED
mode without the need for using the Service Request procedure, as defined in TS 24.301 [35].

User plane EDT: Early Data Transmission used with the User plane CIoT EPS optimisation.

V2X Sidelink communication: AS functionality enabling V2X Communication as defined in TS 23.285 [78], between
nearby UEs, using E-UTRA technology but not traversing any network node.

3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 36.300 [9] and the following
apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if
any, in TR 21.905 [1] or TS 36.300 [9].

1xRTT CDMA2000 1x Radio Transmission Technology

AB Access Barring
ACDC Application specific Congestion control for Data Communication
ACK Acknowledgement
AILC Assistance Information bit for Local Cache
AM Acknowledged Mode
ANDSF Access Network Discovery and Selection Function
ARQ Automatic Repeat Request
AS Access Stratum
ASN.1 Abstract Syntax Notation One
AUL Autonomous Uplink
BCCH Broadcast Control Channel
BCD Binary Coded Decimal
BCH Broadcast Channel
BL Bandwidth reduced Low complexity
BLER Block Error Rate
BR Bandwidth Reduced
BR-BCCH Bandwidth Reduced Broadcast Control Channel
CA Carrier Aggregation
CBR Channel Busy Ratio
CCCH Common Control Channel
CCO Cell Change Order
CE Coverage Enhancement
CG Cell Group
CIoT Cellular IoT
CMAS Commercial Mobile Alert Service
CP Control Plane
CP-EDT Control Plane EDT
C-RNTI Cell RNTI
CRS Cell-specific Reference Signal
CSFB CS fallback
CSG Closed Subscriber Group
CSI Channel State Information
DC Dual Connectivity
DCCH Dedicated Control Channel
DCI Downlink Control Information
DCN Dedicated Core Networks
DFN Direct Frame Number

3GPP
Release 15 30 3GPP TS 36.331 V15.4.0 (2018-12)

DL Downlink
DL-SCH Downlink Shared Channel
DRB (user) Data Radio Bearer
DRX Discontinuous Reception
DTCH Dedicated Traffic Channel
EAB Extended Access Barring
eDRX Extended DRX
EDT Early Data Transmission
EHPLMN Equivalent Home Public Land Mobile Network
eIMTA Enhanced Interference Management and Traffic Adaptation
ENB Evolved Node B
EN-DC E-UTRA NR Dual Connectivity
EPC Evolved Packet Core
EPDCCH Enhanced Physical Downlink Control Channel
EPS Evolved Packet System
ETWS Earthquake and Tsunami Warning System
E-UTRA Evolved Universal Terrestrial Radio Access
E-UTRA/5GC E-UTRA connected to 5GC
E-UTRA/EPC E-UTRA connected to EPC
E-UTRAN Evolved Universal Terrestrial Radio Access Network
FDD Frequency Division Duplex
FFS For Further Study
GERAN GSM/EDGE Radio Access Network
GNSS Global Navigation Satellite System
G-RNTI Group RNTI
GSM Global System for Mobile Communications
HARQ Hybrid Automatic Repeat Request
HFN Hyper Frame Number
HPLMN Home Public Land Mobile Network
HRPD CDMA2000 High Rate Packet Data
HSDN High Speed Dedicated Network
H-SFN Hyper SFN
IDC In-Device Coexistence
IE Information element
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
IoT Internet of Things
ISM Industrial, Scientific and Medical
kB Kilobyte (1000 bytes)
L1 Layer 1
L2 Layer 2
L3 Layer 3
LAA Licensed-Assisted Access
LWA LTE-WLAN Aggregation
LWAAP LTE-WLAN Aggregation Adaptation Protocol
LWIP LTE-WLAN Radio Level Integration with IPsec Tunnel
MAC Medium Access Control
MBMS Multimedia Broadcast Multicast Service
MBSFN Multimedia Broadcast multicast service Single Frequency Network
MCG Master Cell Group
MCOT Maximum Channel Occupancy Time
MCPTT Mission Critical Push To Talk
MDT Minimization of Drive Tests
MIB Master Information Block
MO Mobile Originating
MPDCCH MTC Physical Downlink Control Channel
MRB MBMS Point to Multipoint Radio Bearer
MRO Mobility Robustness Optimisation
MSI MCH Scheduling Information
MT Mobile Terminating
MTSI Multimedia Telephony Service for IMS

3GPP
Release 15 31 3GPP TS 36.331 V15.4.0 (2018-12)

MUST MultiUser Superposition Transmission

N/A Not Applicable
NACC Network Assisted Cell Change
NAICS Network Assisted Interference Cancellation/Suppression
NAS Non Access Stratum
NB-IoT NarrowBand Internet of Things
NPBCH Narrowband Physical Broadcast channel
NPDCCH Narrowband Physical Downlink Control channel
NPDSCH Narrowband Physical Downlink Shared channel
NPRACH Narrowband Physical Random Access channel
NPSS Narrowband Primary Synchronization Signal
NPUSCH Narrowband Physical Uplink Shared channel
NR NR Radio Access
NRS Narrowband Reference Signal
NSSAI Network Slice Selection Assistance Information
NSSS Narrowband Secondary Synchronization Signal
OS OFDM Symbol
P2X Pedestrian-to-Everything
PCCH Paging Control Channel
PCell Primary Cell
PDCCH Physical Downlink Control Channel
PDCP Packet Data Convergence Protocol
PDU Protocol Data Unit
PLMN Public Land Mobile Network
PMK Pairwise Master Key
PO Paging Occasion
posSIB Positioning SIB
ProSe Proximity based Services
PS Public Safety (in context of sidelink), Packet Switched (otherwise)
PSCell Primary Secondary Cell
PSK Pre-Shared Key
PTAG Primary Timing Advance Group
PUCCH Physical Uplink Control Channel
QCI QoS Class Identifier
QoE Quality of Experience
QoS Quality of Service
RACH Random Access CHannel
RAI Release Assistance Indication
RAT Radio Access Technology
RB Radio Bearer
RCLWI RAN Controlled LTE-WLAN Integration
RLC Radio Link Control
RMTC RSSI Measurement Timing Configuration
RN Relay Node
RNA RAN-based Notification Area
RNAU RAN-based Notification Area Update
RNTI Radio Network Temporary Identifier
ROHC RObust Header Compression
RPLMN Registered Public Land Mobile Network
RRC Radio Resource Control
RSCP Received Signal Code Power
RSRP Reference Signal Received Power
RSRQ Reference Signal Received Quality
RSS Resynchronisation signal
RSSI Received Signal Strength Indicator
SAE System Architecture Evolution
SAP Service Access Point
SBAS Satellite Based Augmentation System
SC Sidelink Control
SCell Secondary Cell
SCG Secondary Cell Group

3GPP
Release 15 32 3GPP TS 36.331 V15.4.0 (2018-12)

SC-MRB Single Cell MRB

SC-RNTI Single Cell RNTI
SD-RSRP Sidelink Discovery Reference Signal Received Power
SFN System Frame Number
SI System Information
SIB System Information Block
SI-RNTI System Information RNTI
SL Sidelink
SLSS Sidelink Synchronisation Signal
SMC Security Mode Control
SPDCCH Short PDCCH
SPS Semi-Persistent Scheduling
SPT Short Processing Time
SPUCCH Short PUCCH
SR Scheduling Request
SRB Signalling Radio Bearer
S-RSRP Sidelink Reference Signal Received Power
SSAC Service Specific Access Control
SSTD SFN and Subframe Timing Difference
STAG Secondary Timing Advance Group
S-TMSI SAE Temporary Mobile Station Identifier
STTI Short TTI
TA Tracking Area
TAG Timing Advance Group
TDD Time Division Duplex
TDM Time Division Multiplexing
TM Transparent Mode
TPC-RNTI Transmit Power Control RNTI
T-RPT Time Resource Pattern of Transmission
TTI Transmission Time Interval
TTT Time To Trigger
UDC Uplink Data Compression
UE User Equipment
UICC Universal Integrated Circuit Card
UL Uplink
UL-SCH Uplink Shared Channel
UM Unacknowledged Mode
UP User Plane
UP-EDT User Plane EDT
UTC Coordinated Universal Time
UTRAN Universal Terrestrial Radio Access Network
V2X Vehicle-to-Everything
VoLTE Voice over Long Term Evolution
WLAN Wireless Local Area Network
WT WLAN Termination
WUS Wake-up Signal

In the ASN.1, lower case may be used for some (parts) of the above abbreviations e.g. c-RNTI.

4 General

4.1 Introduction
In this specification, (parts of) procedures and messages specified for the UE equally apply to the RN for functionality
necessary for the RN. There are also (parts of) procedures and messages which are only applicable to the RN in its
communication with the E-UTRAN, in which case the specification denotes the RN instead of the UE. Such
RN-specific aspects are not applicable to the UE.

3GPP
Release 15 33 3GPP TS 36.331 V15.4.0 (2018-12)

This specification covers EN-DC i.e. the case in which the UE is configured with resources belonging to a secondary
node using NR RAT. The NR related configuration is performed using NR RRC as specified in TS 38.331 [82].

NB-IoT is a non backward compatible variant of E-UTRAN supporting a reduced set of functionality. In this
specification, (parts of) procedures and messages specified for the UE equally apply to the UE in NB-IoT. There are
also some features and related procedures and messages that are not supported by UEs in NB-IoT.

In particular, the following features are not supported in NB-IoT and corresponding procedures and messages do not
apply to the UE in NB-IoT:

- Connected mode mobility (Handover and measurement reporting);

- Inter-RAT cell reselection or inter-RAT mobility in connected mode;

- E-UTRA connected to 5GC;

- RRC_INACTIVE;

- CSG;

- Relay Node (RN);

- Carrier Aggregation (CA);

- Dual connectivity (DC);

- E-UTRA NR Dual Connectivity (EN-DC);

- PDCP duplication;

- GBR (QoS);

- ACB, EAB, SSAC and ACDC;

- MBMS, except for MBMS via SC-PTM in Idle mode;

- Self-configuration and self-optimisation;

- Measurement logging and reporting for network performance optimisation;

- Public warning systems e.g. CMAS, ETWS and PWS;

- Broadcast of positioning assistance data;

- Real time services (including emergency call);

- CS services and CS fallback;

- In-device coexistence;

- RAN assisted WLAN interworking;

- Network-assisted interference cancellation/suppression;

- Sidelink (including direct communication and direct discovery).

NOTE: In regard to mobility, NB-IoT is a separate RAT from E-UTRAN.

In this specification, there are also (parts of) procedures and messages which are only applicable to UEs in NB-IoT, in
which case this is stated explicitly.

This specification is organised as follows:

- sub-clause 4.2 describes the RRC protocol model;

- sub-clause 4.3 specifies the services provided to upper layers as well as the services expected from lower layers;

- sub-clause 4.4 lists the RRC functions;

3GPP
Release 15 34 3GPP TS 36.331 V15.4.0 (2018-12)

- clause 5 specifies RRC procedures, including UE state transitions;

- clause 6 specifies the RRC message in a mixed format (i.e. tabular & ASN.1 together);

- clause 7 specifies the variables (including protocol timers and constants) and counters to be used by the UE;

- clause 8 specifies the encoding of the RRC messages;

- clause 9 specifies the specified and default radio configurations;

- clause 10 specifies the RRC messages transferred across network nodes;

- clause 11 specifies the UE capability related constraints and performance requirements.

4.2 Architecture
4.2.1 UE states and state transitions including inter RAT
A UE is in RRC_CONNECTED when an RRC connection has been established or in RRC_INACTIVE (if the UE is
connected to 5GC) when RRC connection is suspended. If this is not the case, i.e. no RRC connection is established, the
UE is in RRC_IDLE state. The RRC states can further be characterised as follows:

- RRC_IDLE:

- A UE specific DRX may be configured by upper layers (not applicable for NB-IoT);

- UE controlled mobility;

- The UE:

- Monitors a Paging channel to detect incoming calls (by CN paging), system information change, for
ETWS capable UEs, ETWS notification, and for CMAS capable UEs, CMAS notification;

- Performs neighbouring cell measurements and cell (re-)selection;

- Acquires system information.

- Performs logging of available measurements together with location and time for logged measurement
configured UEs.

- May perform EDT.

- RRC_INACTIVE:

- A UE specific DRX may be configured by upper layers or by RRC layer;

- A RAN-based notification area is configured by RRC layer;

- The UE stores the UE Inactive AS context;

- The UE:

- Applies RRC_IDLE procedures unless specified otherwise;

- Monitors a Paging channel for CN paging using 5G-S-TMSI and RAN paging using fullI-RNTI;

- Performs periodic RAN-based notification area update;

- Performs RAN-based notification area update when moving out of the configured RAN-based
notification area;

- RRC_CONNECTED:

- Transfer of unicast data to/from UE.

- At lower layers, the UE may be configured with a UE specific DRX.

3GPP
Release 15 35 3GPP TS 36.331 V15.4.0 (2018-12)

- For UEs supporting CA, use of one or more SCells, aggregated with the PCell, for increased bandwidth;

- For UEs supporting DC, use of one SCG, aggregated with the MCG, for increased bandwidth;

- For UEs supporting EN-DC, option to configure one NR SCG in conjunction with the MCG for DRBs and
SRBs, for improved performance (SRBs) and increased bandwidth (DRBs);

- Network controlled mobility, i.e. handover and cell change order with optional network assistance (NACC)
to GERAN (not applicable for NB-IoT);

- The UE:

- Monitors a Paging channel and/ or System Information Block Type 1 contents to detect system
information change, for ETWS capable UEs, ETWS notification, and for CMAS capable UEs, CMAS
notification (not applicable for BL UEs, UEs in CE and NB-IoT UEs);

- Monitors control channels associated with the shared data channel to determine if data is scheduled for it;

- Provides channel quality and feedback information (not applicable for NB-IoT);

- Performs neighbouring cell measurements and measurement reporting (not applicable for NB-IoT);

- Acquires system information (not applicable for BL UEs, UEs in CE and NB-IoT UEs).

The following figure not only provides an overview of the RRC states in E-UTRA, but also illustrates the mobility
support between E-UTRAN, E-UTRA/5GC, UTRAN and GERAN.

GSM_Connected
CELL_DCH Handover E-UTRA Handover
RRC_CONNECTED
GPRS Packet
transfer mode
CELL_FACH Connection CCO with
resume/suspend optional CCO,
NACC Reselection
CELL_PCH
Reselection
URA_PCH E-UTRA
RRC_INACTIVE Connection
establishment/release
Reselection
Reselection
Connection
Connection release
establishment/release
Connection
establishment/release
Reselection

Reselection
Reselection E-UTRA GSM_Idle/GPRS
UTRA_Idle
RRC_IDLE CCO, Reselection Packet_Idle

Figure 4.2.1-1: E-UTRA states and inter RAT mobility procedures, 3GPP

The following figure illustrates the mobility support between E-UTRAN, E-UTRA/5GC, CDMA2000 1xRTT and
CDMA2000 HRPD. The details of the CDMA2000 state models are out of the scope of this specification.

3GPP
Release 15 36 3GPP TS 36.331 V15.4.0 (2018-12)

1xRTT CS Active Handover E-UTRA Handover HRPD

RRC_CONNECTED HRPD Dormant
Active

Connection
resume/suspend

E-UTRA
RRC_INACTIVE

Reselection Connection
release Connection
establishment/release Reselection

Reselection E-UTRA Reselection HRPD Idle

1xRTT Dormant
RRC_IDLE

Figure 4.2.1-2: Mobility procedures between E-UTRA and CDMA2000

The inter-RAT handover procedure(s) supports the case of signalling, conversational services, non-conversational
services and combinations of these.

In addition to the state transitions shown in Figure 4.2.1-1 and Figure 4.2.1-2, there is support for connection release
with redirection information from E-UTRA RRC_CONNECTED to GERAN, UTRAN and CDMA2000 (HRPD Idle/
1xRTT Dormant mode). A UE in RRC_INACTIVE enters RRC_IDLE when it enters another RAT or switches to
another CN type.

For NB-IoT, mobility between E-UTRA and UTRAN, GERAN and between E-UTRA and CDMA2000 1xRTT and
CDMA2000 HRPD is not supported at AS level and hence only the E-UTRA states depicted in Figure 4.2.1-1 are
applicable.

4.2.2 Signalling radio bearers

"Signalling Radio Bearers" (SRBs) are defined as Radio Bearers (RB) that are used only for the transmission of RRC
and NAS messages. More specifically, the following SRBs are defined:

- SRB0 is for RRC messages using the CCCH logical channel;

- SRB1 is for RRC messages (which may include a piggybacked NAS message) as well as for NAS messages
prior to the establishment of SRB2, all using DCCH logical channel;

- For NB-IoT, SRB1bis is for RRC messages (which may include a piggybacked NAS message) as well as for
NAS messages prior to the activation of security, all using DCCH logical channel;

- SRB2 is for RRC messages which include logged measurement information as well as for NAS messages, all
using DCCH logical channel. SRB2 has a lower-priority than SRB1 and is always configured by E-UTRAN after
security activation. SRB2 is not applicable for NB-IoT;

- SRB4 is for RRC messages which include application layer measurement reporting information, all using DCCH
logical channel. SRB4 can only be configured by E-UTRAN after security activation. SRB4 is not applicable for
NB-IoT.

In downlink piggybacking of NAS messages is used only for one dependant (i.e. with joint success/ failure) procedure:
bearer establishment/ modification/ release. In uplink NAS message piggybacking is used only for transferring the
initial NAS message during connection setup.

NOTE 1: The NAS messages transferred via SRB2 are also contained in RRC messages, which however do not
include any RRC protocol control information.

Once security is activated, all RRC messages on SRB1, SRB2 and SRB4, including those containing NAS or non-3GPP
messages, are integrity protected and ciphered by PDCP. NAS independently applies integrity protection and ciphering
to the NAS messages.

3GPP
Release 15 37 3GPP TS 36.331 V15.4.0 (2018-12)

For a UE configured with DC, all RRC messages, regardless of the SRB used and both in downlink and uplink, are
transferred via the MCG. In case of EN-DC, after connection establishment NR PDCP may be configured for both
SRB1 and SRB2 and if so, these SRBs may be configured as split SRB. For a split SRB, the UE receives RRC
messages via both MCG and NR SCG i.e. handles out of order and duplicate PDUs as specified in TS 38.323 [83]. For
a split SRB, the network configures via the cell group(s) the UE sends uplink RRC messages.

NOTE 2: In case of EN-DC, SRB3 may be configured for the transfer of some NR RRC messages between UE and
SgNB via the NR radio interface, see TS 38.331 [82].

Editor's note: Duplication in UL, for split SRB and DRBs, is FFS and completed in June 2018.

4.3 Services
4.3.1 Services provided to upper layers
The RRC protocol offers the following services to upper layers:

- Broadcast of common control information;

- Broadcast of positioning assistance data;

- Notification of UEs in RRC_IDLE and RRC_INACTIVE, e.g. about a terminating call, for ETWS, for CMAS;

- Transfer of dedicated control information, i.e. information for one specific UE.

4.3.2 Services expected from lower layers

In brief, the following are the main services that RRC expects from lower layers:

- PDCP: integrity protection and ciphering;

- RLC: reliable and in-sequence transfer of information, without introducing duplicates and with support for
segmentation and concatenation.

Further details about the services provided by Packet Data Convergence Protocol layer (e.g. integrity and ciphering) are
provided in TS 36.323 [8]. The services provided by Radio Link Control layer (e.g. the RLC modes) are specified in TS
36.322 [7]. Further details about the services provided by Medium Access Control layer (e.g. the logical channels) are
provided in TS 36.321 [6]. The services provided by physical layer (e.g. the transport channels) are specified in TS
36.302 [3].

4.4 Functions
The RRC protocol includes the following main functions:

- Broadcast of system information:

- Including NAS common information;

- Information applicable for UEs in RRC_IDLE, e.g. cell (re-)selection parameters, neighbouring cell
information and information (also) applicable for UEs in RRC_CONNECTED, e.g. common channel
configuration information;

- Including ETWS notification, CMAS notification (not applicable for NB-IoT);

- Including positioning assistance data.

- RRC connection control:

- Paging;

3GPP
Release 15 38 3GPP TS 36.331 V15.4.0 (2018-12)

- Establishment/ modification/ suspension / resumption / release of RRC connection, including e.g.

assignment/ modification of UE identity (C-RNTI), establishment/ modification/ suspension/ resumption/
release of SRB1, SRB1bis, SRB2 and SRB4, access class barring;

- Initial security activation, i.e. initial configuration of AS integrity protection (SRBs) and AS ciphering
(SRBs, DRBs);

- For RNs, configuration of AS integrity protection for DRBs;

- RRC connection mobility including e.g. intra-frequency and inter-frequency handover, associated security
handling, i.e. key/ algorithm change, specification of RRC context information transferred between network
nodes;

NOTE 1: In NB-IoT, only key change (but no re-keying) at RRC Connection Resumption and RRC context
information transfer are applicable.

- Establishment/ modification/ release of RBs carrying user data (DRBs);

- Radio configuration control including e.g. assignment/ modification of ARQ configuration, HARQ
configuration, DRX configuration;

- For RNs, RN-specific radio configuration control for the radio interface between RN and E-UTRAN;

- In case of CA, cell management including e.g. change of PCell, addition/ modification/ release of SCell(s)
and addition/modification/release of STAG(s);

- In case of DC, cell management including e.g. change of PSCell, addition/ modification/ release of SCG
cell(s) and addition/modification/release of SCG TAG(s).

- In case of EN-DC, transparent transfer of NR RRC messages (e.g. DL: reconfiguration messages used to add
or modify the NR SCG configuration or to (re-)configure measurements; UL: measurement reports and
reconfiguration complete messages) and of configurations of radio bearers using NR PDCP.

- QoS control including assignment/ modification of semi-persistent scheduling (SPS) configuration

information for DL and UL, assignment/ modification of parameters for UL rate control in the UE, i.e.
allocation of a priority and a prioritised bit rate (PBR) for each RB (not applicable for NB-IoT);

- Recovery from radio link failure;

- In case of LWA, RCLWI and LWIP, WLAN mobility set management including e.g. addition/ modification/
release of WLAN(s) from the WLAN mobility set;

- Inter-RAT mobility including e.g. security activation, transfer of RRC context information (not applicable for
NB-IoT);

- Measurement configuration and reporting (not applicable for NB-IoT):

- Establishment/ modification/ release of measurements (e.g. intra-frequency, inter-frequency and inter- RAT
measurements);

- Setup and release of measurement gaps;

- Measurement reporting;

- Other functions including e.g. transfer of dedicated NAS information and non-3GPP dedicated information,
transfer of UE radio access capability information, support for E-UTRAN sharing (multiple PLMN identities);

- Generic protocol error handling;

- Support of self-configuration and self-optimisation (not applicable for NB-IoT);

- Support of measurement logging and reporting for network performance optimisation, as specified in TS 37.320
[60] (not applicable for NB-IoT);

NOTE 2: Random access is specified entirely in the MAC including initial transmission power estimation.

3GPP
Release 15 39 3GPP TS 36.331 V15.4.0 (2018-12)

4.5 Data available for transmission for NB-IoT

For the purpose of MAC Data Volume and Power Headroom reporting, the NB-IoT UE shall consider the following as
data available for transmission in the RRC layer:

- For SDUs to be submitted to lower layers:

- the SDU itself, if the SDU has not yet been processed by RRC, or

- the PDU if the SDU has been processed by RRC; or

- The data available for transmission in upper layers not submitted to the RRC layer.

5 Procedures

5.1 General
5.1.1 Introduction
The procedural requirements are structured according to the main functional areas: system information (5.2), connection
control (5.3), inter-RAT mobility (5.4) and measurements (5.5). In addition, sub-clause 5.6 covers other aspects e.g.
NAS dedicated information transfer, UE capability transfer, sub-clause 5.7 specifies the generic error handling, sub-
clause 5.8 covers MBMS (i.e. MBMS service reception via MRB), sub-clause 5.8a covers SC-PTM (i.e. MBMS service
reception via SC-MRB), sub-clause 5.9 covers RN-specific procedures and sub-clause 5.10 covers sidelink.

For NB-IoT, only a subset of the above procedural requirements applies: system information (5.2), connection control
(5.3), some part of other aspects (5.6), general error handling (5.7), and SC-PTM (5.8a). Subclauses inter-RAT mobility
(5.4), measurements (5.5), MBMS (5.8), RN procedures (5.9) and Sidelink (5.10) are not applicable in NB-IoT.

5.1.2 General requirements

The UE shall:

1> process the received messages in order of reception by RRC, i.e. the processing of a message shall be completed
before starting the processing of a subsequent message;

NOTE 1: E-UTRAN may initiate a subsequent procedure prior to receiving the UE's response of a previously
initiated procedure.

1> within a sub-clause execute the steps according to the order specified in the procedural description;

1> consider the term 'radio bearer' (RB) to cover SRBs and DRBs but not MRBs or SC-MRBs unless explicitly
stated otherwise;

1> set the rrc-TransactionIdentifier in the response message, if included, to the same value as included in the
message received from E-UTRAN that triggered the response message;

1> upon receiving a choice value set to setup:

2> apply the corresponding received configuration and start using the associated resources, unless explicitly
specified otherwise;

1> upon receiving a choice value set to release:

2> clear the corresponding configuration and stop using the associated resources;

NOTE 1a: Following receipt of choice value set to release, the UE considers the field as if it was never configured.

1> upon handover to E-UTRA; or

1> upon receiving an RRCConnectionReconfiguration message including the fullConfig:

3GPP
Release 15 40 3GPP TS 36.331 V15.4.0 (2018-12)

2> apply the Conditions in the ASN.1 for inclusion of the fields for the DRB/PDCP/RLC setup during the
reconfiguration of the DRBs included in the drb-ToAddModList;

NOTE 2: At each point in time, the UE keeps a single value for each field except for during handover when the UE
temporarily stores the previous configuration so it can revert back upon handover failure. In other words:
when the UE reconfigures a field, the existing value is released except for during handover.

NOTE 3: Although not explicitly stated, the UE initially considers all functionality to be deactivated/ released until
it is explicitly stated that the functionality is setup/ activated. Correspondingly, the UE initially considers
lists to be empty e.g. the list of radio bearers, the list of measurements.

1> upon receiving an extension field comprising the entries in addition to the ones carried by the original field
(regardless of whether E-UTRAN may signal more entries in total); apply the following generic behaviour if
explicitly stated to be applicable:

2> create a combined list by concatenating the additional entries included in the extension field to the original
field while maintaining the order among both the original and the additional entries;

2> for the combined list, created according to the previous, apply the same behaviour as defined for the original
field;

NOTE 4: A field comprising a list of entries normally includes 'list' in the field name. The typical way to extend
(the size of) such a list is to introduce a field comprising the additional entries, which should include
'listExt' in the name of the field/ IE. E.g. field1List-RAT, field1ListExt-RAT.

1> consider the term DC to cover the case of an E-UTRA MCG and SCG, while the term EN-DC covers the case of
an E-UTRA MCG and NR SCG (as well as an E-UTRA MCG with NR PDCP configuration in a secondary
node); Likewise, MCG covers the case of an E-UTRA MCG, SCG covers the case of an E-UTRA SCG, serving
cell covers the case of an E-UTRA serving cell, PDCP covers the case of PDCP defined by E-UTRA
specifications;

NOTE 5: In this specification, UE configuration refers to the parameters configured by E-UTRA RRC unless stated
otherwise.

5.2 System information

5.2.1 Introduction

5.2.1.1 General
System information is divided into the MasterInformationBlock (MIB) and a number of SystemInformationBlocks
(SIBs) and SystemInformationBlockPos (posSIBs). The MIB includes a limited number of most essential and most
frequently transmitted parameters that are needed to acquire other information from the cell, and is transmitted on BCH.
SIBs other than SystemInformationBlockType1 and posSIBs are carried in SystemInformation (SI) messages. The
mapping of SIBs and posSIBs to SI messages is flexibly configurable by schedulingInfoList and posSchedulingInfoList,
respectively, included in SystemInformationBlockType1, with restrictions that: each SIB is contained only in a single SI
message and each SIB and posSIB is contained at most once in that SI message; only SIBs and posSIBs having the
same scheduling requirement (periodicity) can be mapped to the same SI message; SystemInformationBlockType2 is
always mapped to the SI message that corresponds to the first entry in the list of SI messages in schedulingInfoList.
There may be multiple SI messages transmitted with the same periodicity. SystemInformationBlockType1 and all SI
messages are transmitted on DL-SCH.

The Bandwidth reduced Low Complexity (BL) UEs and UEs in Coverage Enhancement (CE) apply Bandwidth
Reduced (BR) version of the SIB, posSIB or SI messages. A UE considers itself in enhanced coverage as specified in
TS 36.304 [4]. In this and subsequent clauses, anything applicable for a particular SIB, posSIB or SI message equally
applies to the corresponding BR version unless explicitly stated otherwise.

For NB-IoT, a reduced set of system information block with similar functionality but different content is defined; the
UE applies the NB-IoT (NB) version of the MIB and the SIBs. These are denoted MasterInformationBlock-NB,
MasterInformationBlock-TDD-NB and SystemInformationBlockTypeX-NB in this specification. All other system
information blocks (without NB suffix) are not applicable to NB-IoT; this is not further stated in the corresponding text.

3GPP
Release 15 41 3GPP TS 36.331 V15.4.0 (2018-12)

NOTE 1: The physical layer imposes a limit to the maximum size a SIB can take. When DCI format 1C is used the
maximum allowed by the physical layer is 1736 bits (217 bytes) while for format 1A the limit is 2216 bits
(277 bytes), see TS 36.212 [22] and TS 36.213 [23]. For BL UEs and UEs in CE, the maximum SIB and
SI message size is 936 bits, see TS 36.213 [23]. For NB-IoT, the maximum SIB and SI message size is
680 bits, see TS 36.213 [23].

In addition to broadcasting, E-UTRAN may provide SystemInformationBlockType1 and/or

SystemInformationBlockType2, including the same parameter values, via dedicated signalling i.e., within an
RRCConnectionReconfiguration message.

The UE applies the system information acquisition and change monitoring procedures for the PCell, except when being
a BL UE or a UE in CE or a NB-IoT UE in RRC_CONNECTED mode while T311 is not running. For an SCell, E-
UTRAN provides, via dedicated signalling, all system information relevant for operation in RRC_CONNECTED when
adding the SCell. However, a UE that is configured with DC shall aquire the MasterInformationBlock of the PSCell but
use it only to determine the SFN timing of the SCG, which may be different from the MCG. Upon change of the
relevant system information of a configured SCell, E-UTRAN releases and subsequently adds the concerned SCell,
which may be done with a single RRCConnectionReconfiguration message. If the UE is receiving or interested to
receive an MBMS service in a cell, the UE shall apply the system information acquisition and change monitoring
procedure to acquire parameters relevant for MBMS operation and apply the parameters acquired from system
information only for MBMS operation for this cell.

NOTE 2: E-UTRAN may configure via dedicated signalling different parameter values than the ones broadcast in
the concerned SCell.

In MBMS-dedicated cell, non-MBSFN subframes are used for providing MasterInformationBlock-MBMS (MIB-
MBMS) and SystemInformationBlockType1-MBMS. SIBs other than SystemInformationBlockType1-MBMS are carried
in SystemInformation-MBMS message which is also provided on non-MBSFN subframes.

An RN configured with an RN subframe configuration does not need to apply the system information acquisition and
change monitoring procedures. Upon change of any system information relevant to an RN, E-UTRAN provides the
system information blocks containing the relevant system information to an RN configured with an RN subframe
configuration via dedicated signalling using the RNReconfiguration message. For RNs configured with an RN subframe
configuration, the system information contained in this dedicated signalling replaces any corresponding stored system
information and takes precedence over any corresponding system information acquired through the system information
acquisition procedure. The dedicated system information remains valid until overridden.

NOTE 3: E-UTRAN may configure an RN, via dedicated signalling, with different parameter values than the ones
broadcast in the concerned cell.

5.2.1.2 Scheduling
The MIB uses a fixed schedule with a periodicity of 40 ms and repetitions made within 40 ms. The first transmission of
the MIB is scheduled in subframe #0 of radio frames for which the SFN mod 4 = 0, and repetitions are scheduled in
subframe #0 of all other radio frames. For TDD/FDD system with a bandwidth larger than 1.4 MHz that supports BL
UEs or UEs in CE, MIB transmission may additionally be repeated in subframe#0 of the same radio frame, and in
subframe#9 of the previous radio frame for FDD and subframe #5 of the same radio frame for TDD.

NOTE: The UE may assume the scheduling of MIB repetitions does not change. E-UTRAN may indicate in
MobilityControlInfo whether optional MIB repetitions are enabled or not.

The MIB-MBMS uses a fixed schedule with a periodicity of 160 ms and repetitions made within 160 ms. The first
transmission of the MIB-MBMS is scheduled in subframe #0 of radio frames for which the SFN mod 16 = 0, and
repetitions are scheduled in subframe #0 of all other radio frames for which the SFN mod 4 = 0.

The SystemInformationBlockType1 uses a fixed schedule with a periodicity of 80 ms and repetitions made within 80 ms.
The first transmission of SystemInformationBlockType1 is scheduled in subframe #5 of radio frames for which the SFN
mod 8 = 0, and repetitions are scheduled in subframe #5 of all other radio frames for which SFN mod 2 = 0.

For BL UEs or UEs in CE, MIB is applied which may be provided with additional repetitions, while for SIB1 and
further SI messages, separate messages are used which are scheduled independently and with content that may differ.
The separate instance of SIB1 is named as SystemInformationBlockType1-BR. The SystemInformationBlockType1-BR
uses a schedule with a periodicity of 80ms. TBS for SystemInformationBlockType1-BR and the repetitions made within

3GPP
Release 15 42 3GPP TS 36.331 V15.4.0 (2018-12)

80ms are indicated via schedulingInfoSIB1-BR in MIB or optionally in the RRCConnectionReconfiguration message
including the MobilityControlInfo.

The SystemInformationBlockType1-MBMS uses fixed schedule with a periodicity of 160 ms. The first transmission of
SystemInformationBlockType1-MBMS is scheduled in subframe #0 of radio frames for which the SFN mod 16 = 0, and
repetitions are scheduled in subframe #0 of all other radio frames for which SFN mod 8 = 0. Additionally, the
SystemInformationBlockType1-MBMS and other system informations blocks may be scheduled in additional non-
MBSFN subframes indicated in MasterInformationBlock-MBMS.

The SI messages are transmitted within periodically occurring time domain windows (referred to as SI-windows) using
dynamic scheduling. Each SI message is associated with a SI-window and the SI-windows of different SI messages do
not overlap. That is, within one SI-window only the corresponding SI is transmitted. The length of the SI-window is
common for all SI messages, and is configurable. Within the SI-window, the corresponding SI message can be
transmitted a number of times in any subframe other than MBSFN subframes, uplink subframes in TDD, and subframe
#5 of radio frames for which SFN mod 2 = 0. The UE acquires the detailed time-domain scheduling (and other
information, e.g. frequency-domain scheduling, used transport format) from decoding SI-RNTI on PDCCH (see TS
36.321 [6]). For a BL UE or a UE in CE, the detailed time/frequency domain scheduling information for the SI
messages is provided in SystemInformationBlockType1-BR.

For UEs other than BL UE or UEs in CE SI-RNTI is used to address SystemInformationBlockType1 as well as all SI
messages. On MBMS-dedicated cell and on FeMBMS/Unicast-mixed cell, SI-RNTI with value in accordance with TS
36.321 [6] is used to address all SI messages whereas SI-RNTI with value in accordance with TS 36.321 [6] is used to
address SystemInformationBlockType1-MBMS.

SystemInformationBlockType1 configures the SI-window length and the transmission periodicity for the SI messages.

5.2.1.2a Scheduling for NB-IoT

The MasterInformationBlock-NB (MIB-NB) uses a fixed schedule with a periodicity of 640 ms and repetitions made
within 640 ms. The first transmission of the MIB-NB is scheduled in subframe #0 of radio frames for which the SFN
mod 64 = 0 and repetitions are scheduled in subframe #0 of all other radio frames. The transmissions are arranged in 8
independently decodable blocks of 80 ms duration.

The MasterInformationBlock-TDD-NB (MIB-TDD-NB) uses a fixed schedule with a periodicity of 640 ms and
repetitions made within 640 ms. The first transmission of the MIB-TDD-NB is scheduled in subframe #9 of radio
frames for which the SFN mod 64 = 0 and repetitions are scheduled in subframe #9 of all other radio frames. The
transmissions are arranged in 8 independently decodable blocks of 80 ms duration.

The SystemInformationBlockType1-NB (SIB1-NB) uses a fixed schedule with a periodicity of 2560 ms.

For FDD, SIB1-NB transmission occurs in subframe #4 of every other frame in 16 continuous frames. The starting
frame for the first transmission of the SIB1-NB is derived from the cell PCID and the number of repetitions within the
2560 ms period and repetitions are made, equally spaced, within the 2560 ms period (see TS 36.213 [23]). TBS for
SystemInformationBlockType1-NB and the repetitions made within the 2560 ms are indicated by schedulingInfoSIB1
field in the MIB-NB. If additionalTransmissionSIB1 is set to TRUE in the MIB-NB, additional SIB1-NB transmission
occurs in subframe #3 of the same radio frames where SIB1-NB transmission occurs with the same number of
repetitions.

For TDD, SIB1-NB transmission on the anchor carrier occurs in either subframe #0 or subframe #4 of every other
frame in 16 continuous frames and SIB1-NB transmission on a non-anchor carrier occurs in subframe #0 and next in
subframe #5 of every other frame in 16 continuous frames. The starting frame for the first transmission of the SIB1-NB
is derived from the cell PCID and the number of repetitions within the 2560 ms period and repetitions are made, equally
spaced, within the 2560 ms period (see TS 36.213 [23]). TBS for SystemInformationBlockType1-NB, the repetitions
made within the 2560 ms, and the subframe index (#0 or #4) are indicated by schedulingInfoSIB1 field in the MIB-
TDD-NB.

The SI messages are transmitted within periodically occurring time domain windows (referred to as SI-windows) using
scheduling information provided in SystemInformationBlockType1-NB. Each SI message is associated with a SI-
window and the SI-windows of different SI messages do not overlap. That is, within one SI-window only the
corresponding SI is transmitted. The length of the SI-window is common for all SI messages, and is configurable.

Within the SI-window, the corresponding SI message can be transmitted a number of times over 2 or 8 consecutive NB-
IoT downlink subframes depending on TBS.The UE acquires the detailed time/frequency domain scheduling

3GPP
Release 15 43 3GPP TS 36.331 V15.4.0 (2018-12)

information and other information, e.g. used transport format for the SI messages from schedulingInfoList field in
SystemInformationBlockType1-NB. The UE is not required to accumulate several SI messages in parallel but may need
to accumulate a SI message across multiple SI windows, depending on coverage condition.

SystemInformationBlockType1-NB configures the SI-window length and the transmission periodicity for all SI
messages.

5.2.1.3 System information validity and notification of changes

Change of system information (other than for ETWS, CMAS and EAB parameters and other than for AB parameters for
NB-IoT) only occurs at specific radio frames, i.e. the concept of a modification period is used. System information may
be transmitted a number of times with the same content within a modification period, as defined by its scheduling. The
modification period boundaries are defined by SFN values for which SFN mod m= 0, where m is the number of radio
frames comprising the modification period. The modification period is configured by system information. If H-SFN is
provided in SystemInformationBlockType1-BR, modification period boundaries for BL UEs and UEs in CE are defined
by SFN values for which (H-SFN * 1024 + SFN) mod m=0. For NB-IoT, H-SFN is always provided and the
modification period boundaries are defined by SFN values for which (H-SFN * 1024 + SFN) mod m=0.

To enable system information update notification for RRC_IDLE UEs configured to use a DRX cycle longer than the
modification period, an eDRX acquisition period is defined. The boundaries of the eDRX acquisition period are
determined by H-SFN values for which H-SFN mod 256 =0. For NB-IoT, the boundaries of the eDRX acquisition
period are determined by H-SFN values for which H-SFN mod 1024 =0.

NOTE 1: If the UE in RRC_IDLE is configured to use extended DRX cycle, e.g., in the order of several minutes or
longer, in case the eNB is reset the UE SFN may not be synchronized to the new eNB SFN. The UE is
expected to recover, e.g., acquire MIB within a reasonable time, to avoid repeated paging failures.

When the network changes (some of the) system information, it first notifies the UEs about this change, i.e. this may be
done throughout a modification period. In the next modification period, the network transmits the updated system
information. These general principles are illustrated in figure 5.2.1.3-1, in which different colours indicate different
system information. Upon receiving a change notification, the UE not configured to use a DRX cycle that is longer than
the modification period acquires the new system information immediately from the start of the next modification period.
Upon receiving a change notification applicable to eDRX, a UE in RRC_IDLE configured to use a DRX cycle that is
longer than the modification period acquires the updated system information immediately from the start of the next
eDRX acquisition period. The UE applies the previously acquired system information until the UE acquires the new
system information. The possible boundaries of modification for SystemInformationBlockType1-BR are defined by SFN
values for which SFN mod 512 = 0 except for notification of ETWS/CMAS for which the eNB may change
SystemInformationBlockType1-BR content at any time. For NB-IoT, the possible boundaries of modification for
SystemInformationBlockType1-NB are defined by SFN values for which (H-SFN * 1024 + SFN) mod 4096 = 0.

Change notification Updated information

BCCH modification period (n) BCCH modification period (n+1)

Figure 5.2.1.3-1: Change of system Information

The Paging message is used to inform UEs in RRC_IDLE and UEs in RRC_CONNECTED about a system information
change. If the UE is in RRC_CONNECTED or is not configured to use a DRX cycle longer than the modification
period in RRC_IDLE, and receives a Paging message including the systemInfoModification, it knows that the system
information will change at the next modification period boundary. A UE in RRC_IDLE that is configured to use a DRX
cycle longer than the modification period, and receives in an eDRX acquisition period at least one Paging message
including the systemInfoModification-eDRX, shall acquire the updated system information at the next eDRX acquisition
period boundary. Although the UE may be informed about changes in system information, no further details are
provided e.g. regarding which system information will change, except if systemInfoValueTagSI is received by BL UEs
or UEs in CE.

3GPP
Release 15 44 3GPP TS 36.331 V15.4.0 (2018-12)

In RRC_CONNECTED, BL UEs or UEs in CE or NB-IoT UEs are not required to acquire system information except
when T311 is running or upon handover where the UE is only required to acquire the MasterInformationBlock in the
target PCell. In RRC_IDLE, E-UTRAN may notify BL UEs or UEs in CE or NB-IoT UEs about SI update, and except
for NB-IoT, ETWS and CMAS notification and EAB modification, using Direct Indication information, as specified in
6.6 (or 6.7.5 in NB-IoT) and TS 36.212 [22].

NOTE 2: Upon system information change essential for BL UEs, UEs in CE, or NB-IoT UEs in
RRC_CONNECTED, E-UTRAN may initiate connection release.

SystemInformationBlockType1 (or MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB in NB-IoT) includes

a value tag systemInfoValueTag, that indicates if a change has occurred in the SI messages. UEs may use
systemInfoValueTag, e.g. upon return from out of coverage, to verify if the previously stored SI messages are still valid.
MasterInformationBlock (using systemInfoUnchanged-BR) and RSS (if transmitted) may indicate that a change has not
occurred in the SIB1-BR and SI messages of the current cell at least over the SI validity time, and the BL UEs or UEs in
CE may use systemInfoUnchanged-BR or RSS, e.g. upon return from out of coverage, to verify if the previously stored
SIB1-BR and SI messages are still valid. Additionally, for other than BL UEs or UEs in CE or NB-IoT UEs, the UE
considers stored system information to be invalid after 3 hours from the moment it was successfully confirmed as valid,
unless specified otherwise. BL UE or UE in CE considers stored system information to be invalid after 24 hours from
the moment it was successfully confirmed as valid, unless the UE is configured by parameter si-ValidityTime to
consider stored system information to be invalid 3 hours after validity confirmation. NB-IoT UE considers stored
system information to be invalid after 24 hours from the moment it was successfully confirmed as valid. If a BL UE,
UE in CE or NB-IoT UE in RRC_CONNECTED state considers the stored system information invalid, the UE shall
continue using the stored system information while in RRC_CONNECTED state in the serving cell.

For BL UEs or UEs in CE or NB-IoT UEs, the change of specific SI message can additionally be indicated by a SI
message specific value tag systemInfoValueTagSI. If systemInfoValueTag included in the
SystemInformationBlockType1-BR (or MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB in NB-IoT) is
different from the one of the stored system information and if systemInfoValueTagSI is included in the
SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB in NB-IoT) for a specific SI message and is
different from the stored one, the UE shall consider this specific SI message to be invalid. If only systemInfoValueTag is
included and is different from the stored one, the BL UE or UE in CE should consider any stored system information
except SystemInformationBlockType10, SystemInformationBlockType11, SystemInformationBlockType12 and
SystemInformationBlockType14 to be invalid; the NB-IoT UE should consider any stored system information except
SystemInformationBlockType14-NB to be invalid.

On MBMS-dedicated cell and on FeMBMS/Unicast-mixed cell, the change of system information and ETWS/CMAS
notification is indicated by using Direct Indication FeMBMS defined in 6.6a. The modification periodicity follows
MCCH modification periodicity as defined in 5.8.1.3.

E-UTRAN may not update systemInfoValueTag upon change of some system information e.g. ETWS information,
CMAS information, regularly changing parameters like time information (SystemInformationBlockType8,
SystemInformationBlockType16, hyperSFN-MSB in SystemInformationBlockType1-NB), EAB and AB parameters, or
positioning system information blocks. Similarly, E-UTRAN may not include the systemInfoModification within the
Paging message upon change of some system information.

The UE that is not configured to use a DRX cycle longer than the modification period verifies that stored system
information remains valid by either checking systemInfoValueTag in SystemInformationBlockType1 (or
MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB in NB-IoT) after the modification period boundary, or
attempting to find the systemInfoModification indication at least modificationPeriodCoeff times during the modification
period in case no paging is received, in every modification period. If no paging message is received by the UE during a
modification period, the UE may assume that no change of system information will occur at the next modification
period boundary. If UE in RRC_CONNECTED, during a modification period, receives one paging message, it may
deduce from the presence/ absence of systemInfoModification whether a change of system information other than
ETWS information, CMAS information and EAB parameters will occur in the next modification period or not.

When the RRC_IDLE UE is configured with a DRX cycle that is longer than the modification period, and at least one
modification period boundary has passed since the UE last verified validity of stored system information, the UE
verifies that stored system information remains valid by checking the systemInfoValueTag before establishing or
resuming an RRC connection.

ETWS and/or CMAS capable UEs in RRC_CONNECTED, other than BL UEs and UEs in CE, shall attempt to read
paging at least once every defaultPagingCycle to check whether ETWS and/or CMAS notification is present or not.

3GPP
Release 15 45 3GPP TS 36.331 V15.4.0 (2018-12)

5.2.1.4 Indication of ETWS notification

ETWS primary notification and/ or ETWS secondary notification can occur at any point in time. The Paging message is
used to inform ETWS capable UEs in RRC_IDLE and UEs in RRC_CONNECTED about presence of an ETWS
primary notification and/ or ETWS secondary notification. If the UE receives a Paging message including the etws-
Indication, it shall start receiving the ETWS primary notification and/ or ETWS secondary notification according to
schedulingInfoList contained in SystemInformationBlockType1. If the UE receives Paging message including the etws-
Indication while it is acquiring ETWS notification(s), the UE shall continue acquiring ETWS notification(s) based on
the previously acquired schedulingInfoList until it re-acquires schedulingInfoList in SystemInformationBlockType1.
NOTE: The UE is not required to periodically check schedulingInfoList contained in
SystemInformationBlockType1, but Paging message including the etws-Indication triggers the UE to re-
acquire schedulingInfoList contained in SystemInformationBlockType1 for scheduling changes for
SystemInformationBlockType10 and SystemInformationBlockType11. The UE may or may not receive a
Paging message including the etws-Indication and/or systemInfoModification when ETWS is no longer
scheduled.

ETWS primary notification is contained in SystemInformationBlockType10 and ETWS secondary notification is

contained in SystemInformationBlockType11. Segmentation can be applied for the delivery of a secondary notification.
The segmentation is fixed for transmission of a given secondary notification within a cell (i.e. the same segment size for
a given segment with the same messageIdentifier, serialNumber and warningMessageSegmentNumber). An ETWS
secondary notification corresponds to a single CB data IE as defined according to TS 23.041 [37].

5.2.1.5 Indication of CMAS notification

CMAS notification can occur at any point in time. The Paging message is used to inform CMAS capable UEs in
RRC_IDLE and UEs in RRC_CONNECTED about presence of one or more CMAS notifications. If the UE receives a
Paging message including the cmas-Indication, it shall start receiving the CMAS notifications according to
schedulingInfoList contained in SystemInformationBlockType1. If the UE receives Paging message including the cmas-
Indication while it is acquiring CMAS notification(s), the UE shall continue acquiring CMAS notification(s) based on
the previously acquired schedulingInfoList until it re-acquires schedulingInfoList in SystemInformationBlockType1.
NOTE: The UE is not required to periodically check schedulingInfoList contained in
SystemInformationBlockType1, but Paging message including the cmas-Indication triggers the UE to re-
acquire schedulingInfoList contained in SystemInformationBlockType1 for scheduling changes for
SystemInformationBlockType12. The UE may or may not receive a Paging message including the cmas-
Indication and/or systemInfoModification when SystemInformationBlockType12 is no longer scheduled.

CMAS notification is contained in SystemInformationBlockType12. Segmentation can be applied for the delivery of a
CMAS notification. The segmentation is fixed for transmission of a given CMAS notification within a cell (i.e. the
same segment size for a given segment with the same messageIdentifier, serialNumber and
warningMessageSegmentNumber). E-UTRAN does not interleave transmissions of CMAS notifications, i.e. all
segments of a given CMAS notification transmission are transmitted prior to those of another CMAS notification. A
CMAS notification corresponds to a single CB data IE as defined according to TS 23.041 [37].

5.2.1.6 Notification of EAB parameters change

Change of EAB parameters can occur at any point in time. The EAB parameters are contained in
SystemInformationBlockType14. The Paging message is used to inform EAB capable UEs in RRC_IDLE about a
change of EAB parameters or that SystemInformationBlockType14 is no longer scheduled. If the UE receives a Paging
message including the eab-ParamModification, it shall acquire SystemInformationBlockType14 according to
schedulingInfoList contained in SystemInformationBlockType1. If the UE receives a Paging message including the eab-
ParamModification while it is acquiring SystemInformationBlockType14, the UE shall continue acquiring
SystemInformationBlockType14 based on the previously acquired schedulingInfoList until it re-acquires
schedulingInfoList in SystemInformationBlockType1.
NOTE: The EAB capable UE is not expected to periodically check schedulingInfoList contained in
SystemInformationBlockType1.

5.2.1.7 Access Barring parameters change in NB-IoT

Change of Access Barring (AB) parameters can occur at any point in time. The AB parameters are contained in
SystemInformationBlockType14-NB. Update of the AB parameters does not impact the systemInfoValueTag in the

3GPP
Release 15 46 3GPP TS 36.331 V15.4.0 (2018-12)

MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB or the systemInfoValueTagSI in

SystemInformationBlockType1-NB.

A NB-IoT UE checks ab-Enabled indication in theMasterInformationBlock-NB/ MasterInformationBlock-TDD-NB to

know whether access barring is enabled. If access barring is enabled the UE shall not initiate the RRC connection
establishment / resume for all access causes except mobile terminating calls until the UE has a valid version of
SystemInformationBlockType14-NB.

5.2.2 System information acquisition

5.2.2.1 General

UE E-UTRAN

MasterInformationBlock

SystemInformationBlockType1

SystemInformation

Figure 5.2.2.1-1: System information acquisition, normal

The UE applies the system information acquisition procedure to acquire the AS- and NAS- and positioning-system
information that is broadcasted by the E-UTRAN. The procedure applies to UEs in RRC_IDLE and UEs in
RRC_CONNECTED.

For BL UE, UE in CE and NB-IoT UE, specific conditions apply, as specified below.

5.2.2.2 Initiation
The UE shall apply the system information acquisition procedure upon selecting (e.g. upon power on) and upon re-
selecting a cell, after handover completion, after entering E-UTRA from another RAT, upon return from out of
coverage, upon receiving a notification that the system information has changed, upon receiving an indication about the
presence of an ETWS notification, upon receiving an indication about the presence of a CMAS notification, upon
receiving a notification that the EAB parameters have changed, upon receiving a request from CDMA2000 upper
layers, upon receiving a request from positioning upper layers and upon exceeding the maximum validity duration.
Unless explicitly stated otherwise in the procedural specification, the system information acquisition procedure
overwrites any stored system information, i.e. delta configuration is not applicable for system information and the UE
discontinues using a field if it is absent in system information unless explicitly specified otherwise.

In RRC_CONNECTED, BL UEs and UEs in CE are required to acquire system information when T311 is running or
upon handover where the UE is only required to acquire the MasterInformationBlock in the target PCell.

NOTE: Upon handover, E-UTRAN provides system information required by the UE in RRC_CONNECTED
except MIB with RRC signalling, i.e. systemInformationBlockType1Dedicated and mobilityControlInfo.

5.2.2.3 System information required by the UE

The UE shall:

1> ensure having a valid version, as defined below, of (at least) the following system information, also referred to as
the 'required' system information:

2> if in RRC_IDLE:

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

3GPP
Release 15 47 3GPP TS 36.331 V15.4.0 (2018-12)

4> the MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB and

SystemInformationBlockType1-NB as well as SystemInformationBlockType2-NB through
SystemInformationBlockType5-NB, SystemInformationBlockType22-NB;

3> else:

4> the MasterInformationBlock and SystemInformationBlockType1 (or SystemInformationBlockType1-

BR depending on whether the UE is a BL UE or the UE in CE) as well as
SystemInformationBlockType2 through SystemInformationBlockType8 and
SystemInformationBlockType24 (depending on support of the concerned RATs),
SystemInformationBlockType17 (depending on support of RAN-assisted WLAN interworking when
the UE is connected to EPC), SystemInformationBlockType25 (depending on support of E-
UTRA/5GC);

2> if in RRC_INACTIVE:

3> the MasterInformationBlock and SystemInformationBlockType1 as well as SystemInformationBlockType2

through SystemInformationBlockType8 (depending on support of the concerned RATs),
SystemInformationBlockType25;

2> if in RRC_CONNECTED; and

2> the UE is not a BL UE; and

2> the UE is not in CE; and

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

3> the MasterInformationBlock, SystemInformationBlockType1 and SystemInformationBlockType2 as well as

SystemInformationBlockType8 (depending on support of CDMA2000), SystemInformationBlockType17
(depending on support of RAN-assisted WLAN interworking when the UE is connected to EPC),
SystemInformationBlockType25 (depending on support of E-UTRA/5GC);

2> if in RRC_CONNECTED and T311 is running; and

2> the UE is a BL UE or the UE is in CE or the UE is a NB-IoT UE;

3> the MasterInformationBlock (or MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB in NB-

IoT), SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB in NB-IoT) and
SystemInformationBlockType2 (or SystemInformationBlockType2-NB in NB-IoT), and for NB-IoT
SystemInformationBlockType22-NB;

1> delete any stored system information after 3 hours or 24 hours from the moment it was confirmed to be valid as
defined in 5.2.1.3, unless specified otherwise;

1> consider any stored system information except SystemInformationBlockType10, SystemInformationBlockType11,

systemInformationBlockType12 and systemInformationBlockType14 (systemInformationBlockType14-NB in NB-
IoT) to be invalid if systemInfoValueTag included in the SystemInformationBlockType1
(MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB in NB-IoT) is different from the one of the
stored system information and in case of NB-IoT UEs, BL UEs and UEs in CE, systemInfoValueTagSI is not
broadcasted. Otherwise consider system information validity as defined in 5.2.1.3;

5.2.2.4 System information acquisition by the UE

The UE shall:

1> apply the specified BCCH configuration defined in 9.1.1.1 or BR-BCCH configuration defined in 9.1.1.8;

1> if the procedure is triggered by a system information change notification:

2> if the UE uses an idle DRX cycle longer than the modification period:

3> start acquiring the required system information, as defined in 5.2.2.3, from the next eDRX acquisition
period boundary;

3GPP
Release 15 48 3GPP TS 36.331 V15.4.0 (2018-12)

2> else

3> start acquiring the required system information, as defined in 5.2.2.3, from the beginning of the
modification period following the one in which the change notification was received;

NOTE 1: The UE continues using the previously received system information until the new system information has
been acquired.

1> if the UE is in RRC_IDLE and enters a cell for which the UE does not have stored a valid version of the system
information required in RRC_IDLE, as defined in 5.2.2.3:

2> acquire, using the system information acquisition procedure as defined in 5.2.3, the system information
required in RRC_IDLE, as defined in 5.2.2.3;

1> following successful handover completion to a PCell for which the UE does not have stored a valid version of
the system information required in RRC_CONNECTED, as defined in 5.2.2.3:

2> acquire, using the system information acquisition procedure as defined in 5.2.3, the system information
required in RRC_CONNECTED, as defined in 5.2.2.3;

2> upon acquiring the concerned system information:

3> discard the corresponding radio resource configuration information included in the
radioResourceConfigCommon previously received in a dedicated message, if any;

1> following a request from CDMA2000 upper layers:

2> acquire SystemInformationBlockType8, as defined in 5.2.3;

1> neither initiate the RRC connection establishment/resume procedure nor initiate transmission of the
RRCConnectionReestablishmentRequest message until the UE has a valid version of the
MasterInformationBlock (MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB in NB-IoT) and
SystemInformationBlockType1 (SystemInformationBlockType1-NB in NB-IoT) messages as well as
SystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT), and for NB-IoT,
SystemInformationBlockType22-NB;

1> not initiate the RRC connection establishment/resume procedure subject to EAB until the UE has a valid version
of SystemInformationBlockType14, if broadcast;

1> if the UE is ETWS capable:

2> upon entering a cell during RRC_IDLE, following successful handover or upon connection re-establishment:

3> discard any previously buffered warningMessageSegment;

3> clear, if any, the current values of messageIdentifier and serialNumber for
SystemInformationBlockType11;

2> when the UE acquires SystemInformationBlockType1 following ETWS indication, upon entering a cell
during RRC_IDLE, following successful handover or upon connection re-establishment:

3> if schedulingInfoList indicates that SystemInformationBlockType10 is present:

4> if the UE is in CE:

5> start acquiring SystemInformationBlockType10;

4> else

5> start acquiring SystemInformationBlockType10 immediately;

3> if schedulingInfoList indicates that SystemInformationBlockType11 is present:

4> start acquiring SystemInformationBlockType11 immediately;

NOTE 2: UEs shall start acquiring SystemInformationBlockType10 and SystemInformationBlockType11 as

described above even when systemInfoValueTag in SystemInformationBlockType1 has not changed.

3GPP
Release 15 49 3GPP TS 36.331 V15.4.0 (2018-12)

1> if the UE is CMAS capable:

2> upon entering a cell during RRC_IDLE, following successful handover or upon connection re-establishment:

3> discard any previously buffered warningMessageSegment;

3> clear, if any, stored values of messageIdentifier and serialNumber for SystemInformationBlockType12
associated with the discarded warningMessageSegment;

2> when the UE acquires SystemInformationBlockType1 following CMAS indication, upon entering a cell
during RRC_IDLE, following successful handover and upon connection re-establishment:

3> if schedulingInfoList indicates that SystemInformationBlockType12 is present:

4> acquire SystemInformationBlockType12;

NOTE 3: UEs shall start acquiring SystemInformationBlockType12 as described above even when
systemInfoValueTag in SystemInformationBlockType1 has not changed.
1> if the UE is interested to receive MBMS services:

2> if the UE is capable of MBMS reception as specified in 5.8:

3> if schedulingInfoList indicates that SystemInformationBlockType13 is present and the UE does not have
stored a valid version of this system information block:

4> acquire SystemInformationBlockType13;

3> else if SystemInformationBlockType13 is present in SystemInformationBlockType1-MBMS and the UE

does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType13 from SystemInformationBlockType1-MBMS;

2> if the UE is capable of SC-PTM reception as specified in 5.8a:

3> if schedulingInfoList indicates that SystemInformationBlockType20 (SystemInformationBlockType20-NB

in NB-IoT) is present and the UE does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType20 (SystemInformationBlockType20-NB in NB-IoT);

2> if the UE is capable of MBMS Service Continuity:

3> if schedulingInfoList indicates that SystemInformationBlockType15 (SystemInformationBlockType15-NB

in NB-IoT) is present and the UE does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType15 (SystemInformationBlockType15-NB in NB-IoT);

1> if the UE is EAB capable:

2> when the UE does not have stored a valid version of SystemInformationBlockType14 upon entering
RRC_IDLE, or when the UE acquires SystemInformationBlockType1 following EAB parameters change
notification, or upon entering a cell during RRC_IDLE, or before establishing an RRC connection if using
eDRX with DRX cycle longer than the modification period:

3> if schedulingInfoList indicates that SystemInformationBlockType14 is present:

4> start acquiring SystemInformationBlockType14 immediately;

3> else:

4> discard SystemInformationBlockType14, if previously received;

NOTE 4: EAB capable UEs start acquiring SystemInformationBlockType14 as described above even when
systemInfoValueTag in SystemInformationBlockType1 has not changed.
NOTE 5: EAB capable UEs maintain an up to date SystemInformationBlockType14 in RRC_IDLE.

3GPP
Release 15 50 3GPP TS 36.331 V15.4.0 (2018-12)

1> if the UE is capable of sidelink communication and is configured by upper layers to receive or transmit sidelink
communication:

2> if the cell used for sidelink communication meets the S-criteria as defined in TS 36.304 [4]; and

2> if schedulingInfoList indicates that SystemInformationBlockType18 is present and the UE does not have
stored a valid version of this system information block:

3> acquire SystemInformationBlockType18;

1> if the UE is capable of sidelink discovery and is configured by upper layers to receive or transmit sidelink
discovery announcements on the primary frequency:

2> if schedulingInfoList of the serving cell/ PCell indicates that SystemInformationBlockType19 is present and
the UE does not have stored a valid version of this system information block:

3> acquire SystemInformationBlockType19;

1> if the UE is capable of sidelink discovery and, for each of the one or more frequencies included in
discInterFreqList, if included in SystemInformationBlockType19 and for which the UE is configured by upper
layers to receive sidelink discovery announcements on:

2> if SystemInformationBlockType19 of the serving cell/ PCell does not provide the corresponding reception
resources; and

2> if schedulingInfoList of the cell on the concerned frequency indicates that SystemInformationBlockType19 is
present and the UE does not have stored a valid version of this system information block:

3> acquire SystemInformationBlockType19;

1> if the UE is capable of sidelink discovery and, for each of the one or more frequencies included in
discInterFreqList, if included in SystemInformationBlockType19 and for which the UE is configured by upper
layers to transmit sidelink discovery announcements on:

2> if SystemInformationBlockType19 of the serving cell/ PCell includes discTxResourcesInterFreq which is set
to acquireSI-FromCarrier; and

2> if schedulingInfoList of the cell on the concerned frequency indicates that SystemInformationBlockType19 is
present and the UE does not have stored a valid version of this system information block:

3> acquire SystemInformationBlockType19;

1> if the UE is a NB-IoT UE and if ab-Enabled included in MasterInformationBlock-NB/ MasterInformationBlock-

TDD-NB is set to TRUE:

2> not initiate the RRC connection establishment/resume procedure for all access causes except mobile
terminating calls until the UE has acquired the SystemInformationBlockType14-NB;

1> if the UE is capable of V2X sidelink communication and is configured by upper layers to receive or transmit
V2X sidelink communication on a frequency:

2> if schedulingInfoList on the serving cell/PCell indicates that SystemInformationBlockType21 is present and
the UE does not have stored valid version of this system information block:

3> acquire SystemInformationBlockType21 from serving cell/PCell;

2> if schedulingInfoList on the serving cell/PCell indicates that SystemInformationBlockType26 is present and
the UE does not have stored valid version of this system information block;

3> acquire SystemInformationBlockType26 from serving cell/PCell;

1> if the UE is capable of V2X sidelink communication and is configured by upper layers to receive V2X sidelink
communication on a frequency, which is not primary frequency:

2> if neither SystemInformationBlockType21 nor SystemInformationBlockType26 of the serving cell/ PCell

provide reception resource pool for V2X sidelink communication for the concerned frequency; and

3GPP
Release 15 51 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the cell used for V2X sidelink communication on the concerned frequency meets the S-criteria as defined
in TS 36.304 [4]:

3> if schedulingInfoList on the concerned frequency indicates that SystemInformationBlockType21 is present

and the UE does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType21 from the concerned frequency;

3> if schedulingInfoList on the concerned frequency indicates that SystemInformationBlockType26 is present

and the UE does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType26 from the concerned frequency;

1> if the UE is capable of V2X sidelink communication and is configured by upper layers to transmit V2X sidelink
communication on a frequency, which is not primary frequency and is not included in v2x-InterFreqInfoList in
SystemInformationBlockType21 nor SystemInformationBlockType26 of the serving cell/PCell:

2> if the cell used for V2X sidelink communication on the concerned frequency meets the S-criteria as defined
in TS 36.304 [4]:

3> if schedulingInfoList on the concerned frequency indicates that SystemInformationBlockType21 is present

and the UE does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType21 from the concerned frequency;

3> if schedulingInfoList on the concerned frequency indicates that SystemInformationBlockType26 is present

and the UE does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType26 from the concerned frequency;

1> if the NB-IoT UE supports NPRACH resources using preamble format 2:

2> if schedulingInfoList indicates that SystemInformationBlockType23-NB is present and the UE does not have
stored a valid version of this system information block:

3> acquire SystemInformationBlockType23-NB;

1> following a request from positioning upper layers:

2> acquire SystemInformationBlockPos, as defined in 5.2.3;

The UE may apply the received SIBs or posSIBs immediately, i.e. the UE does not need to delay using a SIB or posSIB
until all SI messages have been received. The UE may delay applying the received SIBs until completing lower layer
procedures associated with a received or a UE originated RRC message, e.g. an ongoing random access procedure.

NOTE 6: While attempting to acquire a particular SIB/posSIB, if the UE detects from schedulingInfoList/
posSchedulingInfoList that it is no longer present, the UE should stop trying to acquire the particular SIB/
posSIB.

5.2.2.5 Essential system information missing

The UE shall:

1> if in RRC_IDLE, RRC_INACTIVE or in RRC_CONNECTED while T311 is running:

2> if the UE is unable to acquire the MasterInformationBlock (MasterInformationBlock-NB/

MasterInformationBlock-TDD-NB in NB-IoT); or

2> if the UE is neither a BL UE nor in CE nor in NB-IoT and the UE is unable to acquire the
SystemInformationBlockType1; or

2> if the BL UE or UE in CE is unable to acquire SystemInformationBlockType1-BR or

SystemInformationBlockType1-BR is not scheduled; or

2> if the NB-IoT UE is unable to acquire the SystemInformationBlockType1-NB:

3GPP
Release 15 52 3GPP TS 36.331 V15.4.0 (2018-12)

3> consider the cell as barred in accordance with TS 36.304 [4]; and

3> perform barring as if intraFreqReselection is set to allowed, and as if the csg-Indication is set to FALSE;

2> else:

3> if the UE is unable to acquire the SystemInformationBlockType2 (or SystemInformationBlockType2-NB

in NB-IoT) and for NB-IoT, SystemInformationBlockType22-NB if scheduled; or

3> if SystemInformationBlockType25 is broadcast and if the UE is connected to 5GC and is unable to acquire
the SystemInformationBlockType25:

4> treat the cell as barred in accordance with TS 36.304 [4];

5.2.2.6 Actions upon reception of the MasterInformationBlock message

Upon receiving the MasterInformationBlock message the UE shall:

1> apply the radio resource configuration included in the phich-Config;

1> if the UE is in RRC_IDLE or if the UE is in RRC_CONNECTED while T311 is running:

2> if the UE has no valid system information stored according to 5.2.2.3 for the concerned cell:

3> apply the received value of dl-Bandwidth to the ul-Bandwidth until SystemInformationBlockType2 is
received;

Upon receiving the MasterInformationBlock-NB or MasterInformationBlock-TDD-NB message the UE shall:

1> apply the radio resource configuration included in accordance with the operationModeInfo.

No UE requirements related to the contents of MasterInformationBlock-MBMS apply other than those specified
elsewhere e.g. within procedures using the concerned system information, and/ or within the corresponding field
descriptions.

5.2.2.7 Actions upon reception of the SystemInformationBlockType1 message

Upon receiving the SystemInformationBlockType1 or SystemInformationBlockType1-BR either via broadcast or via
dedicated signalling, the UE shall:

1> if the upper layers indicate the selected core network type as 5GC:

2> if the cellAccessRelatedInfoList-5GC contains an entry with the plmn-Identity or plmn-Index of the selected
PLMN:

3> in the remainder of the procedures use plmn-IdentityList, trackingAreaCode, and cellIdentity for the cell
as received in the corresponding cellAccessRelatedInfoList-5GC containing the selected PLMN;

1> else if the cellAccessRelatedInfoList contains an entry with the PLMN-Identity of the selected PLMN:

2> in the remainder of the procedures use plmn-IdentityList, trackingAreaCode, and cellIdentity for the cell as
received in the corresponding cellAccessRelatedInfoList containing the selected PLMN;

1> if in RRC_IDLE or in RRC_CONNECTED while T311 is running; and

1> if the UE is a category 0 UE according to TS 36.306 [5]; and

1> if category0Allowed is not included in SystemInformationBlockType1:

2> consider the cell as barred in accordance with TS 36.304 [4];

1> if in RRC_CONNECTED while T311 is not running, and the UE supports multi-band cells as defined by bit 31
in featureGroupIndicators:

2> disregard the freqBandIndicator and multiBandInfoList, if received, while in RRC_CONNECTED;

3GPP
Release 15 53 3GPP TS 36.331 V15.4.0 (2018-12)

2> forward the cellIdentity to upper layers;

2> forward the trackingAreaCode to upper layers;

1> else:

2> if the frequency band indicated in the freqBandIndicator is part of the frequency bands supported by the UE
and it is not a downlink only band; or

2> if the UE supports multiBandInfoList, and if one or more of the frequency bands indicated in the
multiBandInfoList are part of the frequency bands supported by the UE and they are not downlink only
bands:

3> forward the cellIdentity to upper layers;

3> forward the trackingAreaCode to upper layers;

3> if in RRC_INACTIVE and the forwarded trackingAreaCode does not trigger message transmission by
upper layers:

4> if the serving cell does not belong to the configured ran-NotificationAreaInfo:

5> initiate an RNA update as specified in 5.3.17.2;

3> forward the ims-EmergencySupport to upper layers, if present;

3> forward the eCallOverIMS-Support to upper layers, if present;

3> if the UE is capable of 5G NAS:

4> forward the ims-EmergencySupport-5GC to upper layers, if present;

4> forward the eCallOverIMS-Support-5GC to upper layers, if present;

3> if, for the frequency band selected by the UE (from freqBandIndicator or multiBandInfoList), the
freqBandInfo or the multiBandInfoList-v10j0 is present and the UE capable of multiNS-Pmax supports at
least one additionalSpectrumEmission in the NS-PmaxList within the freqBandInfo or multiBandInfoList-
v10j0:

4> apply the first listed additionalSpectrumEmission which it supports among the values included in NS-
PmaxList within freqBandInfo or multiBandInfolist-v10j0;

4> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within
NS-PmaxList:

5> apply the additionalPmax;

4> else:

5> apply the p-Max;

3> else:

4> apply the additionalSpectrumEmission in SystemInformationBlockType2 and the p-Max;

2> else:

3> consider the cell as barred in accordance with TS 36.304 [4]; and

3> perform barring as if intraFreqReselection is set to notAllowed, and as if the csg-Indication is set to
FALSE;

1> if in RRC_INACTIVE:

2> if the cell does not belong to the RAN notification area configured by RAN-NotificationAreaInfo:

3> initiate the RAN notification area update procedure as specified in 5.3.17;

3GPP
Release 15 54 3GPP TS 36.331 V15.4.0 (2018-12)

Upon receiving the SystemInformationBlockType1-NB, the UE shall:

1> if the frequency band indicated in the freqBandIndicator is part of the frequency bands supported by the UE; or

1> if one or more of the frequency bands indicated in the multiBandInfoList are part of the frequency bands
supported by the UE:

2> forward the cellIdentity to upper layers;

2> forward the trackingAreaCode to upper layers;

2> if attachWithoutPDN-Connectivity is received for the selected PLMN:

3> forward the attachWithoutPDN-Connectivity to upper layers;

2> else

3> indicate to upper layers that attachWithoutPDN-Connectivity is not present;

2> if, for the frequency band selected by the UE (from freqBandIndicator or multiBandInfoList), the
freqBandInfo is present and the UE capable of multiNS-Pmax supports at least one
additionalSpectrumEmission in the NS-PmaxList within the freqBandInfo:

3> apply the first listed additionalSpectrumEmission which it supports among the values included in NS-
PmaxList within freqBandInfo;

3> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within NS-
PmaxList:

4> apply the additionalPmax;

3> else:

4> apply the p-Max;

2> else:

3> apply the additionalSpectrumEmission in SystemInformationBlockType2-NB and the p-Max;

1> else:

2> consider the cell as barred in accordance with TS 36.304 [4]; and

2> perform barring as if intraFreqReselection is set to notAllowed.

No UE requirements related to the contents of SystemInformationBlockType1-MBMS apply other than those specified
elsewhere e.g. within procedures using the concerned system information, and/ or within the corresponding field
descriptions.

5.2.2.8 Actions upon reception of SystemInformation messages

No UE requirements related to the contents of the SystemInformation messages apply other than those specified
elsewhere e.g. within procedures using the concerned system information, and/ or within the corresponding field
descriptions.

5.2.2.9 Actions upon reception of SystemInformationBlockType2

Upon receiving SystemInformationBlockType2, the UE shall:

1> apply the configuration included in the radioResourceConfigCommon;

1> if in RRC_INACTIVE:

2> apply the shortest of the ran-PagingCycle (if configured), the (UE specific) paging cycle (if indicated by upper
layers), and the defaultPagingCycle included in the radioResourceConfigCommon;

3GPP
Release 15 55 3GPP TS 36.331 V15.4.0 (2018-12)

1> else if upper layers indicate that a (UE specific) paging cycle is configured:

2> apply the shortest of the (UE specific) paging cycle and the defaultPagingCycle included in the
radioResourceConfigCommon;

1> if the mbsfn-SubframeConfigList is included:

2> consider that DL assignments may occur in the MBSFN subframes indicated in the mbsfn-
SubframeConfigList under the conditions specified in TS 36.213 [23], clause 7.1;

1> apply the specified PCCH configuration defined in 9.1.1.3;

1> not apply the timeAlignmentTimerCommon;

1> if in RRC_CONNECTED and UE is configured with RLF timers and constants values received within rlf-
TimersAndConstants:

2> not update its values of the timers and constants in ue-TimersAndConstants except for the value of timer
T300;

1> if in RRC_CONNECTED while T311 is not running; and the UE supports multi-band cells as defined by bit 31
in featureGroupIndicators or multipleNS-Pmax:

2> disregard the additionalSpectrumEmission and ul-CarrierFreq, if received, while in RRC_CONNECTED;

1> if attachWithoutPDN-Connectivity is received for the selected PLMN:

2> forward attachWithoutPDN-Connectivity to upper layers;

1> else:

2> indicate to upper layers that attachWithoutPDN-Connectivity is not present;

1> if cp-CIoT-EPS-Optimisation is received for the selected PLMN:

2> forward cp-CIoT-EPS-Optimisation to upper layers;

1> else:

2> indicate to upper layers that cp-CIoT-EPS-Optimisation is not present;

1> if up-CIoT-EPS-Optimisation is received for the selected PLMN:

2> forward up-CIoT-EPS-Optimisation to upper layers;

1> else:

2> indicate to upper layers that up-CIoT-EPS-Optimisation is not present;

1> to upper layers either forward upperLayerIndication, if present for the selected PLMN, or otherwise indicate
absence of this field;

Upon receiving SystemInformationBlockType2-NB, the UE shall:

1> apply the configuration included in the radioResourceConfigCommon;

1> apply the defaultPagingCycle included in the radioResourceConfigCommon;

1> if SystemInformationBlockType22-NB is scheduled:

2> read and act on information sent in SystemInformationBlockType22-NB;

1> apply the specified PCCH configuration defined in 9.1.1.3.

1> if in RRC_CONNECTED and UE is configured with RLF timers and constants values received within rlf-
TimersAndConstants:

3GPP
Release 15 56 3GPP TS 36.331 V15.4.0 (2018-12)

2> not update its values of the timers and constants in ue-TimersAndConstants except for the value of timer
T300;

5.2.2.10 Actions upon reception of SystemInformationBlockType3

Upon receiving SystemInformationBlockType3, the UE shall:

1> if in RRC_IDLE, the redistributionServingInfo is included and the UE is redistribution capable:

2> perform E-UTRAN inter-frequency redistribution procedure as specified in TS 36.304 [4], clause 5.2.4.10;

1> if in RRC_IDLE, or in RRC_CONNECTED while T311 is running:

2> if, for the frequency band selected by the UE (from the procedure in Section 5.2.2.7) to represent the serving
cell's carrier frequency, the freqBandInfo or the multiBandInfoList-v10j0 is present in
SystemInformationBlockType3 and the UE capable of multiNS-Pmax supports at least one
additionalSpectrumEmission in the NS-PmaxList within the freqBandInfo or multiBandInfoList-v10j0:

3> apply the first listed additionalSpectrumEmission which it supports among the values included in NS-
PmaxList within freqBandInfo or multiBandInfoList-v10j0;

3> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within NS-
PmaxList:

4> apply the additionalPmax;

3> else:

4> apply the p-Max;

2> else:

3> apply the p-Max;

Upon receiving SystemInformationBlockType3-NB, the UE shall:

1> if in RRC_IDLE, or in RRC_CONNECTED while T311 is running:

2> if, for the frequency band selected by the UE (from the procedure in subclause 5.2.2.7) to represent the
serving cell's carrier frequency, the freqBandInfo or the multiBandInfoList is present in
SystemInformationBlockType3-NB and the UE capable of multiNS-Pmax supports at least one
additionalSpectrumEmission in the NS-PmaxList within the freqBandInfo or the multiBandInfoList:

3> apply the first listed additionalSpectrumEmission which it supports among the values included in NS-
PmaxList within freqBandInfo or multiBandInfoList;

3> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within NS-
PmaxList:

4> apply the additionalPmax;

3> else:

4> apply the p-Max;

2> else:

3> apply the p-Max;

5.2.2.11 Actions upon reception of SystemInformationBlockType4

No UE requirements related to the contents of this SystemInformationBlock (SystemInformationBlockType4 or
SystemInformationBlockType4-NB) apply other than those specified elsewhere e.g. within procedures using the
concerned system information, and/ or within the corresponding field descriptions.

3GPP
Release 15 57 3GPP TS 36.331 V15.4.0 (2018-12)

5.2.2.12 Actions upon reception of SystemInformationBlockType5

Upon receiving SystemInformationBlockType5, the UE shall:

1> if in RRC_IDLE, the redistributionInterFreqInfo is included and the UE is redistribution capable:

2> perform E-UTRAN inter-frequency redistribution procedure as specified in TS 36.304 [4], clause 5.2.4.10;

1> if in RRC_IDLE, or in RRC_CONNECTED while T311 is running:

2> if the frequency band selected by the UE to represent a non-serving E UTRA carrier frequency is not a
downlink only band:

3> if, for the selected frequency band, the freqBandInfo or the multiBandInfoList-v10j0 is present and the UE
capable of multiNS-Pmax supports at least one additionalSpectrumEmission in the NS-PmaxList within
freqBandInfo or multiBandInfoList-v10j0:

4> apply the first listed additionalSpectrumEmission which it supports among the values included in NS-
PmaxList within freqBandInfo or multiBandInfoList-v10j0;

4> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within
NS-PmaxList:

5> apply the additionalPmax;

4> else:

5> apply the p-Max;

3> else:

4> apply the p-Max;

1> if in RRC_IDLE and UE has stored VarMeasIdleConfig and SIB5 includes the measIdleConfigSIB and the UE is
capable of IDLE mode measurements for CA:

2> if T331 is running and VarMeasIdleConfig does not contain measIdleCarrierListEUTRA received from the
RRCConnectionRelease message:

3> store the measIdleCarrierListEUTRA of measIdleConfigSIB within VarMeasIdleConfig;

2> perform idle mode measurements on supported carriers as specified in 5.6.20;

Upon receiving SystemInformationBlockType5-NB, the UE shall:

1> if in RRC_IDLE, or in RRC_CONNECTED while T311 is running:

2> if, for the frequency band selected by the UE (from multiBandInfoList) to represent a non-serving NB-IoT
carrier frequency, the freqBandInfo is present and the UE capable of multiNS-Pmax supports at least one
additionalSpectrumEmission in the NS-PmaxList within the freqBandInfo:

3> apply the first listed additionalSpectrumEmission which it supports among the values included in NS-
PmaxList within freqBandInfo;

3> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within NS-
PmaxList:

4> apply the additionalPmax;

3> else:

4> apply the p-Max;

2> else:

3> apply the p-Max;

3GPP
Release 15 58 3GPP TS 36.331 V15.4.0 (2018-12)

5.2.2.13 Actions upon reception of SystemInformationBlockType6

No UE requirements related to the contents of this SystemInformationBlock apply other than those specified elsewhere
e.g. within procedures using the concerned system information, and/ or within the corresponding field descriptions.

5.2.2.14 Actions upon reception of SystemInformationBlockType7

No UE requirements related to the contents of this SystemInformationBlock apply other than those specified elsewhere
e.g. within procedures using the concerned system information, and/ or within the corresponding field descriptions.

5.2.2.15 Actions upon reception of SystemInformationBlockType8

Upon receiving SystemInformationBlockType8, the UE shall:

1> if sib8-PerPLMN-List is included and the UE is capable of network sharing for CDMA2000:

2> apply the CDMA2000 parameters below corresponding to the RPLMN;

1> if the systemTimeInfo is included:

2> forward the systemTimeInfo to CDMA2000 upper layers;

1> if the UE is in RRC_IDLE and if searchWindowSize is included:

2> forward the searchWindowSize to CDMA2000 upper layers;

1> if parametersHRPD is included:

2> forward the preRegistrationInfoHRPD to CDMA2000 upper layers only if the UE has not received the
preRegistrationInfoHRPD within an RRCConnectionReconfiguration message after entering this cell;

2> if the cellReselectionParametersHRPD is included:

3> forward the neighCellList to the CDMA2000 upper layers;

1> if the parameters1XRTT is included:

2> if the csfb-RegistrationParam1XRTT is included:

3> forward the csfb-RegistrationParam1XRTT to the CDMA2000 upper layers which will use this
information to determine if a CS registration/re-registration towards CDMA2000 1xRTT in the EUTRA
cell is required;

2> else:

3> indicate to CDMA2000 upper layers that CSFB Registration to CDMA2000 1xRTT is not allowed;

2> if the longCodeState1XRTT is included:

3> forward the longCodeState1XRTT to CDMA2000 upper layers;

2> if the cellReselectionParameters1XRTT is included:

3> forward the neighCellList to the CDMA2000 upper layers;

2> if the csfb-SupportForDualRxUEs is included:

3> forward csfb-SupportForDualRxUEs to the CDMA2000 upper layers;

2> else:

3> forward csfb-SupportForDualRxUEs, with its value set to FALSE, to the CDMA2000 upper layers;

2> if ac-BarringConfig1XRTT is included:

3> forward ac-BarringConfig1XRTT to the CDMA2000 upper layers;

3GPP
Release 15 59 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the csfb-DualRxTxSupport is included:

3> forward csfb-DualRxTxSupport to the CDMA2000 upper layers;

2> else:

3> forward csfb-DualRxTxSupport, with its value set to FALSE, to the CDMA2000 upper layers;

5.2.2.16 Actions upon reception of SystemInformationBlockType9

Upon receiving SystemInformationBlockType9, the UE shall:

1> if hnb-Name is included, forward the hnb-Name to upper layers;

5.2.2.17 Actions upon reception of SystemInformationBlockType10

Upon receiving SystemInformationBlockType10, the UE shall:
1> forward the received warningType, messageIdentifier and serialNumber to upper layers;

5.2.2.18 Actions upon reception of SystemInformationBlockType11

Upon receiving SystemInformationBlockType11, the UE shall:
1> if there is no current value for messageIdentifier and serialNumber for SystemInformationBlockType11; or

1> if either the received value of messageIdentifier or of serialNumber or of both are different from the current
values of messageIdentifier and serialNumber for SystemInformationBlockType11:

2> use the received values of messageIdentifier and serialNumber for SystemInformationBlockType11 as the
current values of messageIdentifier and serialNumber for SystemInformationBlockType11;

2> discard any previously buffered warningMessageSegment;

2> if all segments of a warning message have been received:

3> assemble the warning message from the received warningMessageSegment;

3> forward the received warning message, messageIdentifier, serialNumber and dataCodingScheme to upper
layers;

3> stop reception of SystemInformationBlockType11;

3> discard the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;

2> else:

3> store the received warningMessageSegment;

3> continue reception of SystemInformationBlockType11;

1> else if all segments of a warning message have been received:

2> assemble the warning message from the received warningMessageSegment;

2> forward the received complete warning message, messageIdentifier, serialNumber and dataCodingScheme to
upper layers;

2> stop reception of SystemInformationBlockType11;

2> discard the current values of messageIdentifier and serialNumber for SystemInformationBlockType11;

1> else:

2> store the received warningMessageSegment;

2> continue reception of SystemInformationBlockType11;

3GPP
Release 15 60 3GPP TS 36.331 V15.4.0 (2018-12)

The UE should discard any stored warningMessageSegment and the current value of messageIdentifier and
serialNumber for SystemInformationBlockType11 if the complete warning message has not been assembled within a
period of 3 hours.

5.2.2.19 Actions upon reception of SystemInformationBlockType12

Upon receiving SystemInformationBlockType12, the UE shall:
1> if the SystemInformationBlockType12 contains a complete warning message and the complete geographical area
coordinates (if any):

2> forward the received warning message, messageIdentifier, serialNumber, dataCodingScheme and the
geographical area coordinates (if any) to upper layers;

2> continue reception of SystemInformationBlockType12;

1> else:

2> if the received values of messageIdentifier and serialNumber are the same (each value is the same) as a pair
for which a warning message and the geographical area coordinates (if any) are currently being assembled:

3> store the received warningMessageSegment;

3> store the received warningAreaCoordinatesSegment (if any);

3> if all segments of a warning message and geographical area coordinates (if any) have been received:

4> assemble the warning message from the received warningMessageSegment;

4> assemble the geographical area coordinates from the received warningAreaCoordinatesSegment (if
any);

4> forward the received warning message, messageIdentifier, serialNumber, dataCodingScheme and
geographical area coordinates (if any) to upper layers;

4> stop assembling a warning message and warning area coordinates (if any) for this messageIdentifier
and serialNumber and delete all stored information held for it;

3> continue reception of SystemInformationBlockType12;

2> else if the received values of messageIdentifier and/or serialNumber are not the same as any of the pairs for
which a warning message is currently being assembled:

3> start assembling a warning message for this messageIdentifier and serialNumber pair;

3> start assembling the geographical area coordinates (if any) for this messageIdentifier and serialNumber
pair;

3> store the received warningMessageSegment;

3> store the received warningAreaCoordinatesSegment (if any);

3> continue reception of SystemInformationBlockType12;

The UE should discard warningMessageSegment and warningAreaCoordinatesSegment (if any) and the associated
values of messageIdentifier and serialNumber for SystemInformationBlockType12 if the complete warning message and
the warning area coordinates (if any) have not been assembled within a period of 3 hours.
NOTE: The number of warning messages that a UE can re-assemble simultaneously is a function of UE
implementation.

5.2.2.20 Actions upon reception of SystemInformationBlockType13

No UE requirements related to the contents of this SystemInformationBlock apply other than those specified elsewhere
e.g. within procedures using the concerned system information, and/ or within the corresponding field descriptions.

3GPP
Release 15 61 3GPP TS 36.331 V15.4.0 (2018-12)

5.2.2.21 Actions upon reception of SystemInformationBlockType14

No UE requirements related to the contents of this SystemInformationBlock (SystemInformationBlockType14 or
SystemInformationBlockType14-NB) apply other than those specified elsewhere e.g. within procedures using the
concerned system information, and/ or within the corresponding field descriptions.

5.2.2.22 Actions upon reception of SystemInformationBlockType15

No UE requirements related to the contents of this SystemInformationBlock (SystemInformationBlockType15 or
SystemInformationBlockType15-NB) apply other than those specified elsewhere e.g. within procedures using the
concerned system information, and/ or within the corresponding field descriptions.

5.2.2.23 Actions upon reception of SystemInformationBlockType16

Upon receiving SystemInformationBlockType16 with timeReferenceInfo, the UE may perform the related actions as
specified in subclause 5.6.1.3.

5.2.2.24 Actions upon reception of SystemInformationBlockType17

Upon receiving SystemInformationBlockType17, the UE shall:

1> if wlan-OffloadConfigCommon corresponding to the RPLMN is included:

2> if the UE is not configured with rclwi-Configuration with command set to steerToWLAN:

3> apply the wlan-Id-List corresponding to the RPLMN;

2> if not configured with the wlan-OffloadConfigDedicated:

3> apply the wlan-OffloadConfigCommon corresponding to the RPLMN;

5.2.2.25 Actions upon reception of SystemInformationBlockType18

Upon receiving SystemInformationBlockType18, the UE shall:

1> if SystemInformationBlockType18 message includes the commConfig:

2> if configured to receive sidelink communication:

3> from the next SC period, as defined by sc-Period, use the resource pool indicated by commRxPool for
sidelink communication monitoring, as specified in 5.10.3;

2> if configured to transmit sidelink communication:

3> from the next SC period, as defined by sc-Period, use the resource pool indicated by
commTxPoolNormalCommon, commTxPoolNormalCommonExt or by commTxPoolExceptional for
sidelink communication transmission, as specified in 5.10.4;

5.2.2.26 Actions upon reception of SystemInformationBlockType19

Upon receiving SystemInformationBlockType19, the UE shall:

1> if SystemInformationBlockType19 message includes the discConfig or discConfigPS:

2> from the next discovery period, as defined by discPeriod, use the resources indicated by discRxPool,
discRxResourcesInterFreq or discRxPoolPS for sidelink discovery monitoring, as specified in 5.10.5;

2> if SystemInformationBlockType19 message includes the discTxPoolCommon or discTxPoolPS-Common; and

the UE is in RRC_IDLE:

3> from the next discovery period, as defined by discPeriod, use the resources indicated by
discTxPoolCommon or discTxPoolPS-Common for sidelink discovery announcement, as specified in
5.10.6;

3GPP
Release 15 62 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the SystemInformationBlockType19 message includes the discTxPowerInfo:

3> use the power information included in discTxPowerInfo for sidelink discovery transmission on the serving
frequency, as specified in TS 36.213 [23];

1> if SystemInformationBlockType19 message includes the discConfigRelay:

2> if the SystemInformationBlockType19 message includes the txPowerInfo:

3> use the power information included in txPowerInfo for sidelink discovery transmission on the
corresponding non-serving frequency, as specified in TS 36.213 [23];

5.2.2.27 Actions upon reception of SystemInformationBlockType20

No UE requirements related to the contents of this SystemInformationBlock (SystemInformationBlockType20 or
SystemInformationBlockType20-NB) apply other than those specified elsewhere e.g. within procedures using the
concerned system information, and/ or within the corresponding field descriptions.

5.2.2.28 Actions upon reception of SystemInformationBlockType21

Upon receiving SystemInformationBlockType21, the UE shall:

1> if SystemInformationBlockType21 message includes sl-V2X-ConfigCommon:

2> if configured to receive V2X sidelink communication:

3> use the resource pool indicated by v2x-CommRxPool in sl-V2X-ConfigCommon for V2X sidelink
communication monitoring, as specified in 5.10.12;

2> if configured to transmit V2X sidelink communication:

3> use the resource pool indicated by v2x-CommTxPoolNormalCommon, p2x-

CommTxPoolNormalCommon, v2x-CommTxPoolNormal, p2x-CommTxPoolNormal or by v2x-
CommTxPoolExceptional for V2X sidelink communication transmission, as specified in 5.10.13;

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

5.2.2.29 Actions upon reception of SystemInformationBlockType22-NB

No UE requirements related to the contents of this SystemInformationBlock apply other than those specified elsewhere
e.g. within procedures using the concerned system information, and/ or within the corresponding field descriptions.

5.2.2.30 Actions upon reception of SystemInformationBlockType23-NB

No UE requirements related to the contents of this SystemInformationBlock apply other than those specified elsewhere
e.g. within procedures using the concerned system information, and/ or within the corresponding field descriptions.

5.2.2.31 Actions upon reception of SystemInformationBlockType24

No UE requirements related to the contents of this SystemInformationBlock apply other than those specified elsewhere
e.g. within procedures using the concerned system information, and/ or within the corresponding field descriptions.

5.2.2.32 Actions upon reception of SystemInformationBlockType25

No UE requirements related to the contents of this SystemInformationBlock apply other than those specified elsewhere
e.g. within procedures using the concerned system information, and/ or within the corresponding field descriptions.

5.2.2.33 Actions upon reception of SystemInformationBlockType26

Upon receiving SystemInformationBlockType26, the UE shall:

3GPP
Release 15 63 3GPP TS 36.331 V15.4.0 (2018-12)

1> if configured to receive V2X sidelink communication:

2> use the resource pool indicated by v2x-CommRxPool for V2X sidelink communication monitoring, as
specified in 5.10.12;

1> if configured to transmit V2X sidelink communication:

2> use the resource pool indicated by v2x-CommTxPoolNormal, p2x-CommTxPoolNormal or by v2x-

CommTxPoolExceptional for V2X sidelink communication transmission, as specified in 5.10.13;

2> perform CBR measurement on the transmission resource pool(s) indicated by v2x-CommTxPoolNormal and
v2x-CommTxPoolExceptional for V2X sidelink communication transmission, as specified in 5.5.3;

5.2.2.34 Actions upon reception of SystemInformationBlockPos

No UE requirements related to the contents of the SystemInformationBlockPos apply other than those specified
elsewhere e.g. within TS 36.355 [54], and/or within the corresponding field descriptions.

5.2.3 Acquisition of an SI message

When acquiring an SI message, the UE shall:

1> determine the start of the SI-window for the concerned SI message as follows:

2> if the concerned SI message is configured in the schedulingInfoList or if the concerned SI message is
configured in the pos-schedulingInfoList and si-posOffset is not configured;

3> for the concerned SI message, determine the number n which corresponds to the order of entry in the
concatenated list of SI messages configured by schedulingInfoList and posSchedulingInfoList in
SystemInformationBlockType1;

3> determine the integer value x = (n – 1)*w, where w is the si-WindowLength;

3> the SI-window starts at the subframe #a, where a = x mod 10, in the radio frame for which SFN mod T =
FLOOR(x/10), where T is the si-Periodicity of the concerned SI message;

2> else if the concerned SI message is configured by the posSchedulingInfoList and si-posOffset is configured
determine the start of the SI-window for the concerned SI message as follows:

3> determine the number m which corresponds to the number of SI messages with an associated si-
Periodicity of 8 radio frames (80 ms), configured by schedulingInfoList in SystemInformationBlockType1;

3> for the concerned SI message, determine the number n which corresponds to the order of entry in the list
of SI messages configured by posSchedulingInfoList in SystemInformationBlockType1;

3> determine the integer value x = m*w + (n – 1)*w, where w is the si-WindowLength

3> the SI-window starts at the subframe #a, where a = x mod 10, in the radio frame for which SFN mod T =
FLOOR(x/10) + 8, where T is the si-posPeriodicity of the concerned SI message;

NOTE: E-UTRAN should configure an SI-window of 1 ms only if all SIs are scheduled before subframe #5 in
radio frames for which SFN mod 2 = 0.

1> receive DL-SCH using the SI-RNTI from the start of the SI-window and continue until the end of the SI-window
whose absolute length in time is given by si-WindowLength, or until the SI message was received, excluding the
following subframes:

2> subframe #5 in radio frames for which SFN mod 2 = 0;

2> any MBSFN subframes;

2> any uplink subframes in TDD;

3GPP
Release 15 64 3GPP TS 36.331 V15.4.0 (2018-12)

1> if the SI message was not received by the end of the SI-window, repeat reception at the next SI-window occasion
for the concerned SI message;

5.2.3a Acquisition of an SI message by BL UE or UE in CE or a NB-IoT UE

When acquiring an SI message, the BL UE or UE in CE or NB-IoT UE shall:

1> determine the start of the SI-window for the concerned SI message as follows:

2> if the concerned SI message is configured in the schedulingInfoList or if the concerned SI message is
configured in the pos-schedulingInfoList and si-posOffset is not configured;

3> for the concerned SI message, determine the number n which corresponds to the order of entry in the
concatenated list of SI messages configured by schedulingInfoList in SystemInformationBlockType1-BR
(or SystemInformationBlockType1-NB in NB-IoT) and posSchedulingInfoList in
SystemInformationBlockType1-BR;

3> determine the integer value x = (n – 1)*w, where w is the si-WindowLength-BR (or si-WindowLength in
NB-IoT);

2> else if the concerned SI message is configured by the posSchedulingInfoList and si-posOffset is configured
determine the start of the SI-window for the concerned SI message as follows:

3> determine the number m which corresponds to the number of SI messages with an associated si-
Periodicity of 8 radio frames (80 ms), configured by schedulingInfoList in
SystemInformationBlockType1-BR;

3> for the concerned SI message, determine the number n which corresponds to the order of entry in the list
of SI messages configured by posSchedulingInfoList in SystemInformationBlockType1-BR;

3> determine the integer value x = m*w + (n – 1)*w, where w is the si-WindowLength-BR

3> the SI-window starts at the subframe #a, where a = x mod 10, in the radio frame for which SFN mod T =
FLOOR(x/10) + 8, where T is the si-posPeriodicity of the concerned SI message;

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

3> the SI-window starts at the subframe #0 in the radio frame for which (H-SFN * 1024 + SFN) mod T =
FLOOR(x/10) + Offset, where T is the si-Periodicity of the concerned SI message and, Offset is the offset
of the start of the SI-Window (si-RadioFrameOffset);

2> else:

3> the SI-window starts at the subframe #0 in the radio frame for which SFN mod T = FLOOR(x/10), where
T is the si-Periodicity of the concerned SI message;

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

2> receive and accumulate SI message transmissions on DL-SCH from the start of the SI-window and continue
until the end of the SI-window whose absolute length in time is given by si-WindowLength, starting from the
radio frames as provided in si-RepetitionPattern and in subframes as provided in downlinkBitmap, or until
successful decoding of the accumulated SI message transmissions excluding the subframes used for
transmission of NPSS, NSSS, MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB and
SystemInformationBlockType1-NB. If there are not enough subframes for one SI message transmission in the
radio frames as provided in si-RepetitionPattern, the UE shall continue to receive the SI message
transmission in the radio frames following the radio frame indicated in si-RepetitionPattern;

1> else:

2> receive and accumulate SI message transmissions on DL-SCH on narrowband provided by si-Narrowband,
from the start of the SI-window and continue until the end of the SI-window whose absolute length in time is
given by si-WindowLength-BR, only in radio frames as provided in si-RepetitionPattern and subframes as
provided in fdd-DownlinkOrTddSubframeBitmapBR in bandwidthReducedAccessRelatedInfo, or until
successful decoding of the accumulated SI message transmissions;

3GPP
Release 15 65 3GPP TS 36.331 V15.4.0 (2018-12)

1> if the SI message was not possible to decode from the accumulated SI message transmissions by the end of the
SI-window, continue reception and accumulation of SI message transmissions on DL-SCH in the next SI-
window occasion for the concerned SI message;

5.2.3b Acquisition of an SI message from MBMS-dedicated cell

When acquiring an SI message, the UE shall:

1> determine the start of the SI-window for the concerned SI message as follows:

2> for the concerned SI message, determine the number n which corresponds to the order of entry in the list of
SI messages configured by schedulingInfoList in SystemInformationBlockType1-MBMS;

2> determine the integer value x = (n – 1)*w, where w is the si-WindowLength;

2> the SI-window starts always at the subframe #a, where a = x mod 10, in the radio frame for which SFN mod
T = FLOOR(x/10), where T is the si-Periodicity of the concerned SI message;

1> receive DL-SCH using SI-RNTI with value in accordance with 36.321 [6] from the start of the SI-window and
continue until the end of the SI-window whose absolute length in time is given by si-WindowLength, or until the
SI message was received, excluding the following subframes:

2> any MBSFN subframes;

1> if the SI message was not received by the end of the SI-window, repeat reception at the next SI-window occasion
for the concerned SI message;

5.3 Connection control

5.3.1 Introduction

5.3.1.1 RRC connection control

RRC connection establishment involves the establishment of SRB1. Except for EDT, E-UTRAN completes RRC
connection establishment prior to completing the establishment of the S1 connection, i.e. prior to receiving the UE
context information from the EPC. Consequently, AS security is not activated during the initial phase of the RRC
connection. During this initial phase of the RRC connection, the E-UTRAN may configure the UE to perform
measurement reporting, but the UE only sends the corresponding measurement reports after successful security
activation. However, the UE only accepts a handover message when security has been activated.

NOTE 1: In case the serving frequency broadcasts multiple overlapping bands, E-UTRAN can only configure
measurements after having obtained the UE capabilities, as the measurement configuration needs to be set
according to the band selected by the UE.

Upon receiving the UE context from the EPC, E-UTRAN activates security (both ciphering and integrity protection)
using the initial security activation procedure. The RRC messages to activate security (command and successful
response) are integrity protected, while ciphering is started only after completion of the procedure. That is, the response
to the message used to activate security is not ciphered, while the subsequent messages (e.g. used to establish SRB2 and
DRBs) are both integrity protected and ciphered.

After having initiated the initial security activation procedure, E-UTRAN initiates the establishment of SRB2 and
DRBs, i.e. E-UTRAN may do this prior to receiving the confirmation of the initial security activation from the UE. In
any case, E-UTRAN will apply both ciphering and integrity protection for the RRC connection reconfiguration
messages used to establish SRB2 and DRBs. E-UTRAN should release the RRC connection if the initial security
activation and/ or the radio bearer establishment fails (i.e. security activation and DRB establishment are triggered by a
joint S1-procedure, which does not support partial success).

For SRB2 and DRBs, security is always activated from the start, i.e. the E-UTRAN does not establish these bearers
prior to activating security.

3GPP
Release 15 66 3GPP TS 36.331 V15.4.0 (2018-12)

For some radio configuration fields, a critical extension has been defined. A switch from the original version of the field
to the critically extended version is allowed using any connection reconfiguration. The UE reverts to the original
version of some critically extended fields upon handover and re-establishment as specified elsewhere in this
specification. Otherwise, switching a field from the critically extended version to the original version is only possible
using the handover or re-establishment procedure with the full configuration option. This also applies for fields that are
critically extended within a release (i.e. original and extended version defined in same release).

After having initiated the initial security activation procedure, E-UTRAN may configure a UE that supports CA, with
one or more SCells in addition to the PCell that was initially configured during connection establishment. The PCell is
used to provide the security inputs and upper layer system information (i.e. the NAS mobility information e.g. TAI).
SCells are used to provide additional downlink and optionally uplink radio resources. When not configured with any
kind of DC, all SCells the UE is configured with, if any, are part of the MCG.

When configured with DC, some of the SCells are part of a SCG. In this case, user data carried by a DRB may either be
transferred via MCG (i.e. MCG-DRB), via SCG (SCG-DRB) or via both MCG and SCG in DL while E-UTRAN
configures the CG used in UL (split DRB). An RRC connection reconfiguration message may be used to change the
DRB type from MCG-DRB to SCG-DRB or to split DRB, as well as from SCG-DRB or split DRB to MCG-DRB.

DC employs SCG change, which is a synchronous SCG reconfiguration procedure (i.e. involving RA to the PSCell)
including reset/ re-establishment of layer 2 and, if SCG DRBs are configured, refresh of security. The procedure is used
in a number of different scenarios e.g. SCG establishment, PSCell change, Key refresh, change of DRB type. The UE
performs the SCG change related actions upon receiving an RRCConnectionReconfiguration message including
mobilityControlInfoSCG, see 5.3.10.10.

In case of EN-DC, the SCG cells use another RAT, namely NR. The configuration of an NR SCG, as used in case of
EN-DC, is specified in TS 38.331 [82]. When configured with EN-DC, user data carried by a DRB may either be
transferred via MCG, via NR SCG or via both MCG and NR SCG. Also RRC signalling carried by a SRB may either be
transferred via MCG or via both MCG and NR SCG. When DRBs and SRBs are configured with transmission via both
MCG and SCG, duplication may be used in both DL and UL.

Change to NR PDCP or vice versa, for both SRBs and DRBs, can be performed using an
RRCConnectionReconfiguration message including the mobilityControlInfo (handover) by release and addition of the
concerned RB (for DRBs) or of the concerned PDCP entity (for SRBs). The same RRCConnectionReconfiguration
message may be used to make changes regarding the CG(s) used for transmission. For SRBs, change from E-UTRA
PDCP to NR PDCP type may, before initial security activation, also be performed using an
RRCConnectionReconfiguration message not including the mobilityControlInfo.

In case of EN-DC, there are three types of NR SCG reconfigurations:

- Reconfiguration with sync and key change i.e. a procedure involving RA to the PSCell, including NR MAC
reset, re-establishment of NR RLC and NR PDCP and refresh of NR SCG security; and

- Reconfiguration with sync but without key change i.e. a procedure involving RA to the PSCell, including NR
MAC reset and NR RLC re-establishment and PDCP data recovery (for AM DRB); and

- Regular NR SCG reconfiguration neither involving refresh of NR SCG security, nor RA to the PSCell, NR MAC
reset or NR RLC re-establishment;

The network is only required to use the NR SCG reconfiguration with sync and key change in case the NR SCG
security key changes (i.e. handover, change of SNs, S-KgNB refresh). Further details are specified in NR RRC TS
38.331 [82].

NOTE 2: In case of EN-DC, E-UTRA RRC configuration parameters should only affect E-UTRA operation. E.g.,
s-Measure only affects measurements configured by parameters defined in this specification. Should an
E-UTRA RRC configuration change require a change of NR RRC configuration, the network should
indicate such NR change by NR RRC signalling. E.g. a specific indication is used to trigger RLC re-
establishment upon reconfigurations changing the CG(s) used for transmission (in DL or UL) that
otherwise would only involve NR RRC signalling.

In this release of the specification, change between DC and EN-DC is not supported (i.e. neither the direct
reconfiguration nor specific measurement events). Likewise, the direct transition between EN-DC and NR DC is not
supported in this release of the specification.

3GPP
Release 15 67 3GPP TS 36.331 V15.4.0 (2018-12)

The release of the RRC connection normally is initiated by E-UTRAN. The procedure may be used to re-direct the UE
to an E-UTRA frequency or an inter-RAT carrier frequency. Only in exceptional cases, as specified within this
specification, TS 36.300 [9], TS 36.304 [4] or TS 24.301 [35], may the UE abort the RRC connection, i.e. move to
RRC_IDLE without notifying E-UTRAN.

The suspension of the RRC connection is initiated by E-UTRAN. When the RRC connection is suspended, the UE
stores the UE AS context and the resumeIdentity, and transitions to RRC_IDLE state. The RRC message to suspend the
RRC connection is integrity protected and ciphered. Suspension can only be performed when at least 1 DRB is
successfully established.

The resumption of a suspended RRC connection is initiated by upper layers when the UE has a stored UE AS context,
RRC connection resume is permitted by E-UTRAN and the UE needs to transit from RRC_IDLE state to
RRC_CONNECTED state. When the RRC connection is resumed, RRC configures the UE according to the RRC
connection resume procedure based on the stored UE AS context and any RRC configuration received from E-UTRAN.
The RRC connection resume procedure re-activates security and re-establishes SRB(s) and DRB(s). The request to
resume the RRC connection includes the resumeIdentity. The request is not ciphered, but protected with a message
authentication code.

In response to a request to resume the RRC connection, E-UTRAN may resume the suspended RRC connection, reject
the request to resume and instruct the UE to either keep or discard the stored context, or setup a new RRC connection.

In case of CP-EDT, the data are appended in the RRCEarlyDataRequest and RRCEarlyDataComplete messages, if
available, and sent over SRB0. In case of UP-EDT, security is re-activated prior to transmission of RRC message using
the nextHopChainingCount provided in the RRCConnectionRelease message with suspend indication during the
preceding suspend procedure and the radio bearers are re-established. The uplink data are transmitted ciphered on
DTCH multiplexed with the RRCConnectionResumeRequest message on CCCH. In the downlink, the data, if available,
are transmitted on DTCH multiplexed with the RRCConnectionRelease message on DCCH. In response to a request for
EDT, E-UTRAN may also choose to establish or resume the RRC connection.

A UE in RRC_CONNECTED enters RRC_INACTIVE when the network indicates RRC connection suspension in
RRCConnectionRelease message. When entering RRC_INACTIVE, the UE stores the UE AS context and any RRC
configuration received from the network.

The resumption of an RRC connection from RRC_INACTIVE is initiated by upper layers when the UE needs to transit
from RRC_INACTIVE state to RRC_CONNECTED state or by RRC layer for, e.g. RNAU or reception of RAN
paging. When the RRC connection is resumed, network configures the UE according to the RRC connection resume
procedure based on the stored UE AS context and any RRC configuration received from the network. The RRC
connection resume procedure re-activates security and re-establishes SRB(s) and DRB(s).

In response to a request to resume the RRC connection from RRC_INACTIVE, the network may resume the suspended
RRC connection and UE enters to RRC_CONNECTED, or reject the request to resume using RRC message without
security protection and send UE to RRC_INACTIVE with wait time, or directly re-suspend the RRC connection and
send UE to RRC_INACTIVE, or directly release the RRC connection and send UE to RRC_IDLE, or instruct the UE to
initiate NAS level recovery.

5.3.1.2 Security
AS security comprises of the integrity protection of RRC signalling (SRBs) as well as the ciphering of RRC signalling
(SRBs) and user data (DRBs).

RRC handles the configuration of the security parameters which are part of the AS configuration: the integrity
protection algorithm, the ciphering algorithm and two parameters, namely the keyChangeIndicator and the
nextHopChainingCount, which are used by the UE to determine the AS security keys upon handover, connection re-
establishment, connection resume and/ or UP-EDT.

The integrity protection algorithm is common for signalling radio bearers SRB1, SRB2 and SRB4. When configured
with MCG only, the ciphering algorithm is common for all radio bearers (i.e. SRB1, SRB2, SRB4 and DRBs). Neither
integrity protection nor ciphering applies for SRB0.

RRC integrity and ciphering are always activated together, i.e. in one message/ procedure. RRC integrity and ciphering
are never de-activated. However, it is possible to switch to a 'NULL' ciphering algorithm (eea0).

The 'NULL' integrity protection algorithm (eia0) is used only for the UE in limited service mode, as specified in TS
33.401 [32]. In case the 'NULL' integrity protection algorithm is used, 'NULL' ciphering algorithm is also used.

3GPP
Release 15 68 3GPP TS 36.331 V15.4.0 (2018-12)

NOTE 1: Lower layers discard RRC messages for which the integrity check has failed and indicate the integrity
verification check failure to RRC.

The AS applies three different security keys: one for the integrity protection of RRC signalling (K RRCint), one for the
ciphering of RRC signalling (KRRCenc) and one for the ciphering of user data (KUPenc). All three AS keys are derived from
the KeNB key. The KeNB is based on the KASME key for E-UTRA/EPC, or KAMF for E-UTRA/5GC, which is handled by
upper layers.

Upon connection establishment new AS keys are derived. No AS-parameters are exchanged to serve as inputs for the
derivation of the new AS keys at connection establishment.

The integrity and ciphering of the RRC message used to perform handover is based on the security configuration used
prior to the handover and is performed by the source eNB.

The integrity and ciphering algorithms can only be changed upon handover. The four AS keys (KeNB, KRRCint, KRRCenc and
KUPenc) change upon every handover, connection re-establishment, connection resume and UP-EDT. The
keyChangeIndicator is used upon handover and indicates whether the UE should use the keys associated with the KASME
key for E-UTRA/EPC, or KAMF for E-UTRA/5GC, taken into use with the latest successful NAS SMC procedure. The
nextHopChainingCount parameter is used upon handover, connection re-establishment, connection resume and UP-
EDT by the UE when deriving the new KeNB that is used to generate KRRCint, KRRCenc and KUPenc (see TS 33.401 [32]). An
intra cell handover procedure may be used to change the keys in RRC_CONNECTED.

For each radio bearer an independent counter (COUNT, as specified in TS 36.323 [8] for E-UTRA/EPC, and TS 38.323
[83] for E-UTRA/5GC) is maintained for each direction. For each DRB, the COUNT is used as input for ciphering. For
each SRB, the COUNT is used as input for both ciphering and integrity protection. It is not allowed to use the same
COUNT value more than once for a given security key. At connection resume the COUNT is reset. In order to limit the
signalling overhead, individual messages/ packets include a short sequence number (PDCP SN, as specified in TS
36.323 [8] for E-UTRA/EPC, and TS 38.323 [83] for E-UTRA/5GC). In addition, an overflow counter mechanism is
used: the hyper frame number (TX_HFN and RX_HFN, as specified in TS 36.323 [8] for E-UTRA/EPC, and TS 38.323
[83] for E-UTRA/5GC). The HFN needs to be synchronized between the UE and the eNB. The eNB is responsible for
avoiding reuse of the COUNT with the same RB identity and with the same KeNB, e.g. due to the transfer of large
volumes of data, release and establishment of new RBs. In order to avoid such re-use, the eNB may e.g. use different
RB identities for successive RB establishments, trigger an intra cell handover or by triggering a transition from
RRC_CONNECTED to RRC_IDLE or RRC_INACTIVE and then back to RRC_CONNECTED.

For each SRB, the value provided by RRC to lower layers to derive the 5-bit BEARER parameter used as input for
ciphering and for integrity protection is the value of the corresponding srb-Identity with the MSBs padded with zeroes.

In case of DC, a separate KeNB is used for SCG-DRBs (S-KeNB). This key is derived from the key used for the MCG
(KeNB) and an SCG counter that is used to ensure freshness. To refresh the S-KeNB e.g. when the COUNT will wrap
around, E-UTRAN employs an SCG change, i.e. an RRCConnectionReconfiguration message including
mobilityControlInfoSCG. When performing handover, while at least one SCG-DRB remains configured, both KeNB and
S-KeNB are refreshed. In such case E-UTRAN performs handover with SCG change i.e. an
RRCConnectionReconfiguration message including both mobilityControlInfo and mobilityControlInfoSCG. The
ciphering algorithm is common for all radio bearers within a CG but may be different between MCG and SCG. The
ciphering algorithm for SCG DRBs can only be changed upon SCG change.

In case of EN-DC, the network indicates whether the UE shall use either KeNB or S-KgNB for a particular DRB. S-KgNB is
derived in the same way as S-KeNB as defined in TS 33.501 [86], uses a different counter (sk-Counter) and is used only
for DRBs using NR PDCP. Whenever there is a need to refresh S-KgNB, e.g. upon change of MN or SN, the NR SCG
reconfiguration with sync and key change is used (see 5.3.1.1). E-UTRAN provides a UE configured with EN-DC with
an sk-Counter even when no DRB is setup using S-KgNB i.e. to facilitate configuration of SRB3. The same ciphering
algorithm is used for all radio bearers using the same key (i.e. KeNB or S-KgNB). Likewise, the same integrity algorithm is
used for all SRBs using the same key. Although NR RRC uses different values for the security algorithms than E-
UTRA, the actual algorithms are the same in case of EN-DC in this version of the specification. Hence, for such
algorithms, the security capabilities supported by a UE are consistent across these RATs.

NOTE 2: The network ensures that different values are used for the SCG counter and for the sk-Counter when
deriving S-KgNB and/or S-KeNB from the same KeNB.

3GPP
Release 15 69 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.1.2a RN security
For RNs, AS security follows the procedures in 5.3.1.2. Furthermore, E-UTRAN may configure per DRB whether or
not integrity protection is used. The use of integrity protection may be configured only upon DRB establishment and
reconfigured only upon handover or upon the first reconfiguration following RRC connection re-establishment.

To provide integrity protection on DRBs between the RN and the E-UTRAN, the KUPint key is derived from the KeNB key
as described in TS 33.401 [32]. The same integrity protection algorithm used for SRBs also applies to the DRBs. The
KUPint changes at every handover and RRC connection re-establishment and is based on an updated KeNB which is derived
by taking into account the nextHopChainingCount. The COUNT value maintained for DRB ciphering is also used for
integrity protection, if the integrity protection is configured for the DRB.

5.3.1.3 Connected mode mobility

In RRC_CONNECTED, the network controls UE mobility, i.e. the network decides when the UE shall connect to
which E-UTRA cell(s), or inter-RAT cell. For network controlled mobility in RRC_CONNECTED, the PCell can be
changed using an RRCConnectionReconfiguration message including the mobilityControlInfo (handover), whereas the
SCell(s) can be changed using the RRCConnectionReconfiguration message either with or without the
mobilityControlInfo.

In DC, an SCG can be established, reconfigured or released by using an RRCConnectionReconfiguration message with
or without the mobilityControlInfo. In case Random Access to the PSCell or initial PUSCH transmission to the PSCell
if rach-SkipSCG is configured is required upon SCG reconfiguration, E-UTRAN employs the SCG change procedure
(i.e. an RRCConnectionReconfiguration message including the mobilityControlInfoSCG). The PSCell can only be
changed using the SCG change procedure and by release and addition of the PSCell.

In EN-DC, an NR SCG can be established or reconfigured by using an RRCConnectionReconfiguration message

containing nr-secondaryCellGroupConfig and nr-RadioBearerConfig. The contents of nr-secondaryCellGroupConfig
and nr-RadioBearerConfig, of other EN-DC fields as well as the associated procedures are specified in TS 38.331 [82].
In EN-DC, the PSCell can only be changed using the Reconfiguration with sync procedure, with or without EN-DC
release and addition.

The network triggers the handover procedure e.g. based on radio conditions, load. To facilitate this, the network may
configure the UE to perform measurement reporting (possibly including the configuration of measurement gaps). The
network may also initiate handover blindly, i.e. without having received measurement reports from the UE.

Before sending the handover message to the UE, the source eNB prepares one or more target cells. The source eNB
selects the target PCell. The source eNB may also provide the target eNB with a list of best cells on each frequency for
which measurement information is available, in order of decreasing RSRP. The source eNB may also include available
measurement information for the cells provided in the list. The target eNB decides which SCells are configured for use
after handover, which may include cells other than the ones indicated by the source eNB. If an SCG is configured,
handover involves either SCG release or either SCG change (in case of DC) or an NR SCG reconfiguration with sync
and key change (in case of EN-DC). In case the UE was configured with (EN-) DC, the target eNB indicates in the
handover message whether the UE shall release the entire (NR) SCG configuration. Upon connection re-establishment,
the UE releases the entire SCG configuration except for the DRB configuration, while E-UTRAN in the first
reconfiguration message following the re-establishment either releases the DRB(s) or reconfigures the DRB(s) to MCG
DRB(s).

The target eNB generates the message used to perform the handover, i.e. the message including the AS-configuration to
be used in the target cell(s). The source eNB transparently (i.e. does not alter values/ content) forwards the handover
message/ information received from the target to the UE. When appropriate, the source eNB may initiate data
forwarding for (a subset of) the DRBs.

After receiving the handover message, the UE attempts to access the target PCell at the first available RACH occasion
according to Random Access resource selection defined in TS 36.321 [6], i.e. the handover is asynchronous, or at the
first available PUSCH occasion if rach-Skip is configured. Consequently, when allocating a dedicated preamble for the
random access in the target PCell, E-UTRA shall ensure it is available from the first RACH occasion the UE may use.
The first available PUSCH occasion is provided by ul-ConfigInfo, if configured, otherwise UE shall monitor the
PDCCH of target eNB. Upon successful completion of the handover, the UE sends a message used to confirm the
handover.

If the target eNB does not support the release of RRC protocol which the source eNB used to configure the UE, the
target eNB may be unable to comprehend the UE configuration provided by the source eNB. In this case, the target eNB

3GPP
Release 15 70 3GPP TS 36.331 V15.4.0 (2018-12)

should use the full configuration option to reconfigure the UE for Handover and Re-establishment. Full configuration
option includes an initialization of the radio configuration, which makes the procedure independent of the configuration
used in the source cell(s) with the exception that the security algorithms are continued for the RRC re-establishment.

The same behavior applies in EN-DC, if upon handover the target eNB is unable to comprehend the MCG part of the
UE configuration i.e. the target eNB uses the full configuration option which involves release and configuration of
(most of the) MCG and NR SCG configuration. In case of EN-DC, the target SgNB may be unable to comprehend the
NR SCG configuration provided by the source SgNB. In such a case, release and addition may be applied for the NR
SCG part of the configuration.

NOTE 1: When using release and addition for the NR SCG configuration, E-UTRAN includes drb-ToReleaseList
for the SN terminated RBs.

After the successful completion of handover, PDCP SDUs may be re-transmitted in the target cell(s). This only applies
for DRBs using RLC-AM mode and for handovers not involving full configuration option. The further details are
specified in TS 36.323 [8]. After the successful completion of handover not involving full configuration option, the SN
and the HFN are reset except for the DRBs using RLC-AM mode (for which both SN and HFN continue). For
reconfigurations involving the full configuration option, the PDCP entities are newly established (SN and HFN do not
continue) for all DRBs irrespective of the RLC mode. The further details are specified in TS 36.323 [8].

One UE behaviour to be performed upon handover is specified, i.e. this is regardless of the handover procedures used
within the network (e.g. whether the handover includes X2 or S1 signalling procedures).

The source eNB should, for some time, maintain a context to enable the UE to return in case of handover failure. After
having detected handover failure, the UE attempts to resume the RRC connection either in the source PCell or in
another cell using the RRC re-establishment procedure. This connection resumption succeeds only if the accessed cell is
prepared, i.e. concerns a cell of the source eNB or of another eNB towards which handover preparation has been
performed. The cell in which the re-establishment procedure succeeds becomes the PCell while SCells and STAGs, if
configured, are released.

Normal measurement and mobility procedures are used to support handover to cells broadcasting a CSG identity. In
addition, E-UTRAN may configure the UE to report that it is entering or leaving the proximity of cell(s) included in its
CSG whitelist. Furthermore, E-UTRAN may request the UE to provide additional information broadcast by the
handover candidate cell e.g. global cell identity, CSG identity, CSG membership status.

NOTE 2: E-UTRAN may use the 'proximity report' to configure measurements as well as to decide whether or not
to request additional information broadcast by the handover candidate cell. The additional information is
used to verify whether or not the UE is authorised to access the target PCell and may also be needed to
identify handover candidate cell (PCI confusion i.e. when the physical layer identity that is included in
the measurement report does not uniquely identify the cell).

5.3.1.4 Connection control in NB-IoT

In NB-IoT, during the RRC connection establishment procedure, SRB1bis is established implicitly with SRB1.
SRB1bis uses the logical channel identity defined in 9.1.2a, with the same configuration as SRB1 but no PDCP entity.
SRB1bis is used until security is activated. The RRC messages to activate security (command and successful response)
are sent over SRB1 being integrity protected and ciphering is started after completion of the procedure. In case of
unsuccessful security activation, the failure message is sent over SRB1 and subsequent messages are sent over
SRB1bis. Once security is activated, new RRC messages shall be transmitted using SRB1. A NB-IoT UE that only
supports the Control Plane CIoT EPS optimisation (see TS 24.301 [35]) only establishes SRB1bis.

A NB-IoT UE only supports 0, 1 or 2 DRBs, depending on its capability. A NB-IoT UE that only supports the Control
Plane CIoT EPS optimisation (see TS 24.301 [35]) does not need to support any DRBs and associated procedures.

Table 5.3.1.4-1 lists the procedures that are applicable for NB-IoT. All other procedures are not applicable; this is not
further stated in the corresponding procedures.

3GPP
Release 15 71 3GPP TS 36.331 V15.4.0 (2018-12)

Table 5.3.1.4-1: Connection control procedures applicable to a NB-IoT UE

Sub-clause Procedures
5.3.2 Paging
5.3.3 RRC connection establishment
RRC connection resume (see NOTE)
CP-EDT
UP-EDT (see NOTE)
5.3.4 Initial security activation (see NOTE)
5.3.5 RRC connection reconfiguration (see NOTE)
5.3.7 RRC connection re-establishment
5.3.8 RRC connection release
5.3.9 RRC connection release requested by upper layers
5.3.10 Radio resource configuration
5.3.11 Radio link failure related actions
5.3.12 UE actions upon leaving RRC_CONNECTED

NOTE: Not applicable for a UE that only supports the Control Plane CIoT EPS optimisation (see TS 24.301
[35]).

5.3.2 Paging

5.3.2.1 General

UE EUTRAN

Paging

Figure 5.3.2.1-1: Paging

The purpose of this procedure is:

- to transmit CN initiated paging information to a UE in RRC_IDLE or RRC_INACTIVE and/ or;

- to transmit RAN initiated paging information to a UE in RRC_INACTIVE and/or;

- to inform UEs in RRC_IDLE, UEs in RRC_INACTIVE and UEs in RRC_CONNECTED other than NB-IoT
UEs, BL UEs and UEs in CE, about a system information change and/ or;

- to inform UEs in RRC_IDLE other than NB-IoT UEs, UEs in RRC_INACTIVE and UEs in
RRC_CONNECTED other than NB-IoT UEs, BL UEs and UEs in CE, about an ETWS primary notification and/
or ETWS secondary notification and/ or;

- to inform UEs in RRC_IDLE other than NB-IoT UEs, UEs in RRC_INACTIVE and UEs in
RRC_CONNECTED other than NB-IoT UEs, BL UEs and UEs in CE, about a CMAS notification and/ or;

- to inform UEs other than NB-IoT UEs in RRC_IDLE, and other than UEs connected to 5GC about an EAB
parameters modification and/ or;

- to inform UEs other than NB-IoT UEs in RRC_IDLE, and UEs in RRC_INACTIVE to perform E-UTRAN
inter-frequency redistribution procedure.

The paging information of CN initiated paging is provided to upper layers, which in response may initiate RRC
connection establishment, e.g. to receive an incoming call.

3GPP
Release 15 72 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.2.2 Initiation
E-UTRAN initiates the paging procedure by transmitting the Paging message at the UE's paging occasion as specified
in TS 36.304 [4]. E-UTRAN may address multiple UEs within a Paging message by including one PagingRecord for
each UE. E-UTRAN may also indicate a change of system information, and/ or provide an ETWS notification or a
CMAS notification in the Paging message.

5.3.2.3 Reception of the Paging message by the UE

Upon receiving the Paging message, the UE shall:

1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:

3> forward the ue-Identity, accessType (if present) and, except for NB-IoT, the cn-Domain to the upper
layers;

1> if in RRC_INACTIVE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches the stored fullI-RNTI:

3> if UE is configured with one or more access identities equal to 1, 2 or 11-15 applicable in the selected
PLMN:

4> initiate RRC connection resume procedure in 5.3.3.2 with cause value set to 'highProrityAccess';

3> else:

4> initiate the RRC connection resumption procedure according to 5.3.3.2 with cause value set to 'mt-
access';

2> else if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper
layers:

3> forward the ue-Identity, accessType (if present) and the cn-Domain to the upper layers;

3> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12, with release cause 'other';

1> if the UE is not configured with a DRX cycle longer than the modification period and the
systemInfoModification is included; or

1> if the UE is configured with a DRX cycle longer than the modification period and the systemInfoModification-
eDRX is included:

2> re-acquire the required system information using the system information acquisition procedure as specified in
5.2.2.

1> if the etws-Indication is included and the UE is ETWS capable:

2> re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information
modification period boundary;
2> if the schedulingInfoList indicates that SystemInformationBlockType10 is present:

3> acquire SystemInformationBlockType10;

NOTE: If the UE is in CE, it is up to UE implementation when to start acquiring SystemInformationBlockType10.

2> if the schedulingInfoList indicates that SystemInformationBlockType11 is present:

3> acquire SystemInformationBlockType11;

1> if the cmas-Indication is included and the UE is CMAS capable:

2> re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information
modification period boundary as specified in 5.2.1.5;

3GPP
Release 15 73 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the schedulingInfoList indicates that SystemInformationBlockType12 is present:

3> acquire SystemInformationBlockType12;

1> if in RRC_IDLE, the eab-ParamModification is included and the UE is EAB capable:

2> consider previously stored SystemInformationBlockType14 as invalid;

2> re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information
modification period boundary as specified in 5.2.1.6;

2> re-acquire SystemInformationBlockType14 using the system information acquisition procedure as specified in
5.2.2.4;

1> if in RRC_IDLE, the redistributionIndication is included and the UE is redistribution capable:

2> Perform E-UTRAN inter-frequency redistribution procedure as specified in TS 36.304 [4], clause 5.2.4.10;

5.3.3 RRC connection establishment

5.3.3.1 General

UE EUTRAN

RRCConnectionRequest

RRCConnectionSetup

RRCConnectionSetupComplete

Figure 5.3.3.1-1: RRC connection establishment, successful

UE EUTRAN

RRCConnectionRequest

RRCConnectionReject

Figure 5.3.3.1-2: RRC connection establishment, network reject

3GPP
Release 15 74 3GPP TS 36.331 V15.4.0 (2018-12)

UE EUTRAN

RRCConnectionResumeRequest

RRCConnectionResume

RRCConnectionResumeComplete

Figure 5.3.3.1-3: RRC connection resume (suspended RRC connection or RRC_INACTIVE), or UP-
EDT fallback to RRC connection resume, successful

UE EUTRAN

RRCConnectionResumeRequest

RRCConnectionSetup

RRCConnectionSetupComplete

Figure 5.3.3.1-4: RRC connection resume (suspended RRC connection or RRC_INACTIVE) or UP-EDT
fallback to RRC connection establishment, successful

UE EUTRAN

RRCConnectionResumeRequest

RRCConnectionReject

Figure 5.3.3.1-5: RRC connection resume or UP-EDT, network reject (suspended RRC connection or
RRC_INACTIVE) or release (suspended RRC connection)

3GPP
Release 15 75 3GPP TS 36.331 V15.4.0 (2018-12)

UE EUTRAN

RRCConnectionResumeRequest

RRCConnectionRelease

Figure 5.3.3.1-6: RRC connection resume (RRC_INACTIVE), network release or suspend or UP-EDT,
successful

UE EUTRAN

RRCEarlyDataRequest

RRCEarlyDataComplete

Figure 5.3.3.1-7: CP-EDT, successful

UE EUTRAN

RRCEarlyDataRequest

RRCConnectionSetup

RRCConnectionSetupComplete

Figure 5.3.3.1-8: CP-EDT fallback to RRC connection establishment, successful

UE EUTRAN

RRCEarlyDataRequest

RRCConnectionReject

Figure 5.3.3.1-9: CP-EDT, network reject

3GPP
Release 15 76 3GPP TS 36.331 V15.4.0 (2018-12)

The purpose of this procedure is to establish an RRC connection, to resume a suspended RRC connection, to move the
UE from RRC_INACTIVE to RRC_CONNECTED or to perform EDT. RRC connection establishment involves SRB1
(and SRB1bis for NB-IoT) establishment. The procedure is also used to transfer the initial NAS dedicated information/
message from the UE to E-UTRAN.

E-UTRAN applies the procedure as follows:

- When establishing an RRC connection:

- to establish SRB1 and, for NB-IoT, SRB1bis;

- When resuming an RRC connection from a suspended RRC connection or from RRC_INACTIVE:

- to restore the AS configuration from a stored context including resuming SRB(s) and DRB(s);

- When performing EDT.

5.3.3.1a Conditions for establishing RRC Connection for sidelink communication/

discovery/ V2X sidelink communication
For sidelink communication an RRC connection is initiated only in the following case:

1> if configured by upper layers to transmit non-relay related sidelink communication and related data is available
for transmission:

2> if SystemInformationBlockType18 is broadcast by the cell on which the UE camps; and if the valid version of
SystemInformationBlockType18 does not include commTxPoolNormalCommon;

1> if configured by upper layers to transmit relay related sidelink communication:

2> if the UE is acting as sidelink relay UE; and if SystemInformationBlockType18 is broadcast by the cell on
which the UE camps; or

2> if the UE has a selected sidelink relay UE; and if the sidelink remote UE threshold conditions as specified in
5.10.11.5 are met and if SystemInformationBlockType18 is broadcast by the cell on which the UE camps; and
if the valid version of SystemInformationBlockType18 does not include commTxPoolNormalCommon or
commTxAllowRelayCommon;

For V2X sidelink communication an RRC connection is initiated only in the following case:

1> if configured by upper layers to transmit non-P2X related V2X sidelink communication and related data is
available for transmission:

2> if the frequency on which the UE is configured to transmit non-P2X related V2X sidelink communication
concerns the camped frequency; and if SystemInformationBlockType21 is broadcast by the cell on which the
UE camps; and if the valid version of SystemInformationBlockType21 includes sl-V2X-ConfigCommon; and
sl-V2X-ConfigCommon does not include v2x-CommTxPoolNormalCommon; or

2> if the frequency on which the UE is configured to transmit non-P2X related V2X sidelink communication is
included in v2x-InterFreqInfoList within SystemInformationBlockType21 or SystemInformationBlockType26
broadcast by the cell on which the UE camps; and if neither the valid version of
SystemInformationBlockType21 nor that of SystemInformationBlockType26 includes v2x-
CommTxPoolNormal for the concerned frequency;

1> if configured by upper layers to transmit P2X related V2X sidelink communication and related data is available
for transmission:

2> if the frequency on which the UE is configured to transmit P2X related V2X sidelink communication
concerns the camped frequency; and if SystemInformationBlockType21 is broadcast by the cell on which the
UE camps; and if the valid version of SystemInformationBlockType21 includes sl-V2X-ConfigCommon; and
sl-V2X-ConfigCommon does not include p2x-CommTxPoolNormalCommon; or

2> if the frequency on which the UE is configured to transmit P2X related V2X sidelink communication is
included in v2x-InterFreqInfoList within SystemInformationBlockType21 or SystemInformationBlockType26
broadcast by the cell on which the UE camps; and if neither the valid version of

3GPP
Release 15 77 3GPP TS 36.331 V15.4.0 (2018-12)

SystemInformationBlockType21 nor that of SystemInformationBlockType26 includes p2x-

CommTxPoolNormal for the concerned frequency;

For sidelink discovery an RRC connection is initiated only in the following case:

1> if configured by upper layers to transmit non-PS related sidelink discovery announcements:

2> if the frequency on which the UE is configured to transmit non-PS related sidelink discovery announcements
concerns the camped frequency; and SystemInformationBlockType19 of the cell on which the UE camps does
not include discTxPoolCommon-r12; or

2> if the frequency on which the UE is configured to transmit non-PS related sidelink discovery announcements
is included in discInterFreqList in SystemInformationBlockType19 broadcast by the cell on which the UE
camps, with discTxResourcesInterFreq included within discResourcesNonPS and set to requestDedicated;

1> if configured by upper layers to transmit non-relay PS related sidelink discovery announcements:

2> if the frequency on which the UE is configured to transmit non-relay PS related sidelink discovery
announcements concerns the camped frequency; and SystemInformationBlockType19 of the cell on which the
UE camps includes discConfigPS but does not include discTxPoolPS-Common; or

2> if the frequency on which the UE is configured to transmit non-relay PS related sidelink discovery
announcements (e.g. group member discovery) is included in discInterFreqList in
SystemInformationBlockType19 broadcast by the cell on which the UE camps, with
discTxResourcesInterFreq within discResourcesPS included and set to requestDedicated;

1> if configured by upper layers to transmit relay PS related sidelink discovery announcements:

2> if the UE is acting as sidelink relay UE; and if the sidelink relay UE threshold conditions as specified in
5.10.10.4 are met; or

2> if the UE is selecting a sidelink relay UE / has a selected sidelink relay UE; and if the sidelink remote UE
threshold conditions as specified in 5.10.11.5 are met:

3> if the frequency on which the UE is configured to transmit relay PS related sidelink discovery
announcements concerns the camped frequency; and SystemInformationBlockType19 of the cell on which
the UE camps includes discConfigRelay and discConfigPS but does not include discTxPoolPS-Common;

NOTE: Upper layers initiate an RRC connection. The interaction with NAS is left to UE implementation.

5.3.3.1b Conditions for initiating EDT

A BL UE, UE in CE or NB-IoT UE can initiate EDT when all of the following conditions are fulfilled:

1> for CP-EDT, the upper layers request establishment of an RRC connection, the UE supports CP-EDT, and
SystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT) includes cp-EDT; or

1> for UP-EDT, the upper layers request resumption of an RRC connection, the UE supports UP-EDT,
SystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT) includes up-EDT, and the UE has
a stored value of the nextHopChainingCount provided in the RRCConnectionRelease message with suspend
indication during the preceding suspend procedure;

1> the establishment or resumption request is for mobile originating calls and the establishment cause is mo-Data or
mo-ExceptionData or delayTolerantAccess;

1> SystemInformationBlockType2 (SystemInformationBlockType2-NB in NB-IoT) includes edt-Parameters;

1> the size of the resulting MAC PDU including the total UL data is expected to be smaller than or equal to the TBS
signalled in edt-TBS as specified in TS 36.321 [6], clause 5.1.1;

1> EDT fallback indication has not been received from lower layers for this establishment or resumption procedure;

NOTE 1: Upper layers request or resume an RRC connection. The interaction with NAS is up to UE
implementation.

NOTE 2: It is up to UE implementation how the UE determines whether the size of UL data is suitable for EDT.

3GPP
Release 15 78 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.3.2 Initiation
The UE initiates the procedure when upper layers request establishment or resume of an RRC connection while the UE
is in RRC_IDLE or when upper layers request resume of an RRC connection or RRC layer requests resume of an RRC
connection for, e.g. RNAU or reception of RAN paging while the UE is in RRC_INACTIVE.

Except for NB-IoT, upon initiation of the procedure, if the UE is connected to EPC, the UE shall:

1> if SystemInformationBlockType2 includes ac-BarringPerPLMN-List and the ac-BarringPerPLMN-List contains

an AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers
(see TS 23.122 [11], TS 24.301 [35]):

2> select the AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by
upper layers;

2> in the remainder of this procedure, use the selected AC-BarringPerPLMN entry (i.e. presence or absence of
access barring parameters in this entry) irrespective of the common access barring parameters included in
SystemInformationBlockType2;

1> else

2> in the remainder of this procedure use the common access barring parameters (i.e. presence or absence of
these parameters) included in SystemInformationBlockType2;

1> if SystemInformationBlockType2 contains acdc-BarringPerPLMN-List and the acdc-BarringPerPLMN-List

contains an ACDC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by
upper layers (see TS 23.122 [11], TS 24.301 [35]):

2> select the ACDC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected
by upper layers;

2> in the remainder of this procedure, use the selected ACDC-BarringPerPLMN entry for ACDC barring check
(i.e. presence or absence of access barring parameters in this entry) irrespective of the acdc-
BarringForCommon parameters included in SystemInformationBlockType2;

1> else:

2> in the remainder of this procedure use the acdc-BarringForCommon (i.e. presence or absence of these
parameters) included in SystemInformationBlockType2 for ACDC barring check;

1> if upper layers indicate that the RRC connection is subject to EAB (see TS 24.301 [35]):

2> if the result of the EAB check, as specified in 5.3.3.12, is that access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication and that EAB is applicable, upon which the procedure ends;

1> if upper layers indicate that the RRC connection is subject to ACDC (see TS 24.301 [35]),
SystemInformationBlockType2 contains BarringPerACDC-CategoryList, and acdc-HPLMNonly indicates that
ACDC is applicable for the UE:

2> if the BarringPerACDC-CategoryList contains a BarringPerACDC-Category entry corresponding to the

ACDC category selected by upper layers:

3> select the BarringPerACDC-Category entry corresponding to the ACDC category selected by upper
layers;

2> else:

3> select the last BarringPerACDC-Category entry in the BarringPerACDC-CategoryList;

2> stop timer T308, if running;

2> perform access barring check as specified in 5.3.3.13, using T308 as "Tbarring" and acdc-BarringConfig in
the BarringPerACDC-Category as "ACDC barring parameter";

3GPP
Release 15 79 3GPP TS 36.331 V15.4.0 (2018-12)

2> if access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication and that access barring is applicable due to ACDC, upon which the
procedure ends;

1> else if the UE is establishing the RRC connection for mobile terminating calls:

2> if timer T302 is running:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication and that access barring for mobile terminating calls is applicable,
upon which the procedure ends;

1> else if the UE is establishing the RRC connection for emergency calls:

2> if SystemInformationBlockType2 includes the ac-BarringInfo:

3> if the ac-BarringForEmergency is set to TRUE:

4> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15,
which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11]:

NOTE 1: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the
HPLMN/ EHPLMN.

5> if the ac-BarringInfo includes ac-BarringForMO-Data, and for all of these valid Access Classes
for the UE, the corresponding bit in the ac-BarringForSpecialAC contained in ac-BarringForMO-
Data is set to one:

6> consider access to the cell as barred;

4> else:

5> consider access to the cell as barred;

2> if access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication, upon which the procedure ends;

1> else if the UE is establishing the RRC connection for mobile originating calls:

2> perform access barring check as specified in 5.3.3.11, using T303 as "Tbarring" and ac-BarringForMO-Data
as "AC barring parameter";

2> if access to the cell is barred:

3> if SystemInformationBlockType2 includes ac-BarringForCSFB or the UE does not support CS fallback:

4> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication and that access barring for mobile originating calls is applicable,
upon which the procedure ends;

3> else (SystemInformationBlockType2 does not include ac-BarringForCSFB and the UE supports CS
fallback):

4> if timer T306 is not running, start T306 with the timer value of T303;

4> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication and that access barring for mobile originating calls and mobile
originating CS fallback is applicable, upon which the procedure ends;

1> else if the UE is establishing the RRC connection for mobile originating signalling:

2> perform access barring check as specified in 5.3.3.11, using T305 as "Tbarring" and ac-BarringForMO-
Signalling as "AC barring parameter";

3GPP
Release 15 80 3GPP TS 36.331 V15.4.0 (2018-12)

2> if access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication and that access barring for mobile originating signalling is applicable,
upon which the procedure ends;

1> else if the UE is establishing the RRC connection for mobile originating CS fallback:

2> if SystemInformationBlockType2 includes ac-BarringForCSFB:

3> perform access barring check as specified in 5.3.3.11, using T306 as "Tbarring" and ac-BarringForCSFB
as "AC barring parameter";

3> if access to the cell is barred:

4> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication and that access barring for mobile originating CS fallback is
applicable, due to ac-BarringForCSFB, upon which the procedure ends;

2> else:

3> perform access barring check as specified in 5.3.3.11, using T306 as "Tbarring" and ac-BarringForMO-
Data as "AC barring parameter";

3> if access to the cell is barred:

4> if timer T303 is not running, start T303 with the timer value of T306;

4> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication and that access barring for mobile originating CS fallback and
mobile originating calls is applicable, due to ac-BarringForMO-Data, upon which the procedure ends;

1> else if the UE is establishing the RRC connection for mobile originating MMTEL voice, mobile originating
MMTEL video, mobile originating SMSoIP or mobile originating SMS:

2> if the UE is establishing the RRC connection for mobile originating MMTEL voice and
SystemInformationBlockType2 includes ac-BarringSkipForMMTELVoice; or

2> if the UE is establishing the RRC connection for mobile originating MMTEL video and
SystemInformationBlockType2 includes ac-BarringSkipForMMTELVideo; or

2> if the UE is establishing the RRC connection for mobile originating SMSoIP or SMS and
SystemInformationBlockType2 includes ac-BarringSkipForSMS:

3> consider access to the cell as not barred;

2> else:

3> if establishmentCause received from higher layers is set to mo-Signalling (including the case that mo-
Signalling is replaced by highPriorityAccess according to TS 24.301 [35] or by mo-VoiceCall according
to the subclause 5.3.3.3):

4> perform access barring check as specified in 5.3.3.11, using T305 as "Tbarring" and ac-
BarringForMO-Signalling as "AC barring parameter";

4> if access to the cell is barred:

5> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication and that access barring for mobile originating signalling is
applicable, upon which the procedure ends;

3> if establishmentCause received from higher layers is set to mo-Data (including the case that mo-Data is
replaced by highPriorityAccess according to TS 24.301 [35] or by mo-VoiceCall according to the
subclause 5.3.3.3):

3GPP
Release 15 81 3GPP TS 36.331 V15.4.0 (2018-12)

4> perform access barring check as specified in 5.3.3.11, using T303 as "Tbarring" and ac-
BarringForMO-Data as "AC barring parameter";

4> if access to the cell is barred:

5> if SystemInformationBlockType2 includes ac-BarringForCSFB or the UE does not support CS

fallback:

6> inform upper layers about the failure to establish the RRC connection or failure to resume the
RRC connection with suspend indication and that access barring for mobile originating calls is
applicable, upon which the procedure ends;

5> else (SystemInformationBlockType2 does not include ac-BarringForCSFB and the UE supports CS
fallback):

6> if timer T306 is not running, start T306 with the timer value of T303;

6> inform upper layers about the failure to establish the RRC connection or failure to resume the
RRC connection with suspend indication and that access barring for mobile originating calls
and mobile originating CS fallback is applicable, upon which the procedure ends;

Upon initiation of the procedure, if the UE is connected to 5GC, the UE shall:

1> if the upper layers provide an Access Category and one or more Access Identities upon requesting establishment
of an RRC connection:

2> perform the unified access control procedure as specified in 5.3.16 using the Access Category and Access
Identities provided by upper layers;

3> if the access attempt is barred, the procedure ends;

1> if the resumption of the RRC connection is triggered by response to NG-RAN paging:

2> select '0' as the Access Category;

2> perform the unified access control procedure as specified in 5.3.16 using the selected Access Category and
one or more Access Identities provided by upper layers;

3> if the access attempt is barred, the procedure ends;

1> else if the upper layers provide an Access Category and one or more Access Identities upon requesting the
resumption of an RRC connection:

2> perform the unified access control procedure as specified in 5.3.16 using the Access Category and Access
Identities provided by upper layers;

2> set the resumeCause in accordance with the information received from upper layers;

3> if the access attempt is barred, the procedure ends;

1> else if the resumption of the RRC connection is triggered due to an RNAU:

2> if an emergency service is ongoing:

3> select '2' as the Access Category;

2> else:

3> select '8' as the Access Category;

2> perform the unified access control procedure as specified in 5.3.16 using the selected Access Category and
one or more Access Identities to be applied as specified in TS 24.501 [95];

3> if the access attempt is barred:

4> set the variable pendingRnaUpdate to 'TRUE';

3GPP
Release 15 82 3GPP TS 36.331 V15.4.0 (2018-12)

4> the procedure ends;

Except for NB-IoT, upon initiating the procedure, if connected to EPC or 5GC, the UE shall:

1> if the UE is resuming an RRC connection from a suspended RRC connection or from RRC_INACTIVE:

2> if the UE is resuming an RRC connection from a suspended RRC connection:

3> if the UE was configured with EN-DC:

4> perform EN-DC release, as specified in TS 38.331 [82], clause 5.3.5.10;

2> release the MCG SCell(s), if configured, in accordance with 5.3.10.3a;

2> release powerPrefIndicationConfig, if configured and stop timer T340, if running;

2> release reportProximityConfig and clear any associated proximity status reporting timer;

2> release obtainLocationConfig, if configured;

2> release idc-Config, if configured;

2> release sps-AssistanceInfoReport, if configured;

2> release measSubframePatternPCell, if configured;

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

2> release naics-Info for the PCell, if configured;

2> release the LWA configuration, if configured, as described in 5.6.14.3;

2> release the LWIP configuration, if configured, as described in 5.6.17.3;

2> release bw-PreferenceIndicationTimer, if configured and stop timer T341, if running;

2> release delayBudgetReportingConfig, if configured and stop timer T342, if running;

2> release ailc-BitConfig, if configured;

2> release uplinkDataCompression, if configured;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> apply the CCCH configuration as specified in 9.1.1.2;

1> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

1> start timer T300;

1> if the UE is resuming an RRC connection from a suspended RRC connection:

2> initiate transmission of the RRCConnectionResumeRequest message in accordance with 5.3.3.3a;

1> else if the UE is resuming an RRC connection from RRC_INACTIVE:

2> stop T380, if running;

2> set the variable pendingRnaUpdate to 'FALSE';

2> initiate transmission of the RRCConnectionResumeRequest message in accordance with 5.3.3.3a;

1> else:

3GPP
Release 15 83 3GPP TS 36.331 V15.4.0 (2018-12)

2> if stored, discard the UE AS context, resumeIdentity, fullI-RNTI and shortI-RNTI;

2> if the UE is initiating CP-EDT in accordance with conditions in 5.3.3.1b:

3> initiate transmission of the RRCEarlyDataRequest message in accordance with 5.3.3.3b;

2> else:

3> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

NOTE 2: Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up
to date system information applicable only for UEs in RRC_IDLE state or UEs in RRC_INACTIVE.
However, the UE needs to perform system information acquisition upon cell re-selection.

For NB-IoT, upon initiation of the procedure, the UE shall:

1> if the UE is establishing or resuming the RRC connection for mobile originating exception data; or

1> if the UE is establishing or resuming the RRC connection for mobile originating data; or

1> if the UE is establishing or resuming the RRC connection for delay tolerant access; or

1> if the UE is establishing or resuming the RRC connection for mobile originating signalling;

2> perform access barring check as specified in 5.3.3.14;

2> if access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication and that access barring is applicable, upon which the procedure ends;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default MAC main configuration as specified in 9.2.2;

1> apply the CCCH configuration as specified in 9.1.1.2;

1> start timer T300;

1> if the UE is establishing an RRC connection:

2> if stored, discard the UE AS context and resumeIdentity;

2> if the UE is initiating CP-EDT in accordance with conditions in 5.3.3.1b:

3> initiate transmission of the RRCEarlyDataRequest message in accordance with 5.3.3.3b;

2> else:

3> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

1> else if the UE is resuming an RRC connection:

2> release schedulingRequestConfig, if configured;

2> initiate transmission of the RRCConnectionResumeRequest message in accordance with 5.3.3.3a;

NOTE 3: Upon initiating the connection establishment or resumption procedure, the UE is not required to ensure it
maintains up to date system information applicable only for UEs in RRC_IDLE state. However, the UE
needs to perform system information acquisition upon cell re-selection.

NOTE 4: For EDT, upon initiating the connection establishment or resumption procedure, it is up to UE
implementation whether to continue cell re-selection related measurements as well as cell re-selection
evaluation and, if the conditions for cell re-selection are fulfilled, whether to perform cell re-selection as
specified in 5.3.3.5.

3GPP
Release 15 84 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.3.3 Actions related to transmission of RRCConnectionRequest message

The UE shall set the contents of RRCConnectionRequest message as follows:

1> if the UE is connected to EPC:

2> set the ue-Identity as follows:

3> if upper layers provide an S-TMSI:

4> set the ue-Identity to the value received from upper layers;

3> else:

4> draw a random value in the range 0 .. 240-1 and set the ue-Identity to this value;

NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

2> if the UE supports mo-VoiceCall establishment cause and UE is establishing the RRC connection for mobile
originating MMTEL voice and SystemInformationBlockType2 includes voiceServiceCauseIndication and the
establishment cause received from upper layers is not set to highPriorityAccess:

3> set the establishmentCause to mo-VoiceCall;

2> else if the UE supports mo-VoiceCall establishment cause for mobile originating MMTEL video and UE is
establishing the RRC connection for mobile originating MMTEL video and SystemInformationBlockType2
includes videoServiceCauseIndication and the establishment cause received from upper layers is not set to
highPriorityAccess:

3> set the establishmentCause to mo-VoiceCall;

2> else:

3> set the establishmentCause in accordance with the information received from upper layers;

1> if the UE is connected to 5GC:

2> set the ue-Identity as follows:

3> if upper layers provide a 5G-S-TMSI:

4> set the ue-Identity to ng-5G-S-TMSI-Part1;

3> else:

4> draw a random value in the range 0 .. 240-1 and set the ue-Identity to this value;

2> set the establishmentCause in accordance with the information received from upper layers;

2> apply the default NR PDCP configuration as specified in TS 38.331 [82], clause 9.2.1.1 for SRB1;

2> use NR PDCP for all subsequent messages received and sent by the UE via SRB1;

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

2> if the UE supports multi-tone transmission, include multiToneSupport;

2> if the UE supports multi-carrier operation, include multiCarrierSupport;

2> if the UE supports DL channel quality reporting and cqi-Reporting is present in

SystemInformationBlockType2-NB:

3> set the cqi-NPDCCH to include the latest results of the downlink channel quality measurements of the
serving cell as specified in TS 36.133 [16];

NOTE 2: The downlink channel quality measurements may use measurement period T1 or T2, as defined in TS
36.133 [16]. In case period T2 is used the RRC-MAC interactions are left to UE implementation.

3GPP
Release 15 85 3GPP TS 36.331 V15.4.0 (2018-12)

2> set earlyContentionResolution to TRUE;

The UE shall submit the RRCConnectionRequest message to lower layers for transmission.

The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for
cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.5.

5.3.3.3a Actions related to transmission of RRCConnectionResumeRequest message

If the UE is resuming the RRC connection from a suspended RRC connection, the UE shall set the contents of
RRCConnectionResumeRequest message as follows:

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

1> if the UE is initiating UP-EDT in accordance with conditions in 5.3.3.1b; or

1> if field useFullResumeID is signalled in SystemInformationBlockType2:

2> set the resumeID to the stored resumeIdentity;

1> else:

2> set the truncatedResumeID to include bits in bit position 9 to 20 and 29 to 40 from the left in the stored
resumeIdentity.

1> if the UE supports mo-VoiceCall establishment cause and UE is resuming the RRC connection for mobile
originating MMTEL voice and SystemInformationBlockType2 includes voiceServiceCauseIndication and the
establishment cause received from upper layers is not set to highPriorityAccess:

2> set the resumeCause to mo-VoiceCall;

1> else if the UE supports mo-VoiceCall establishment cause for mobile originating MMTEL video and UE is
resuming the RRC connection for mobile originating MMTEL video and SystemInformationBlockType2 includes
videoServiceCauseIndication and the establishment cause received from upper layers is not set to
highPriorityAccess:

2> set the resumeCause to mo-VoiceCall;

1> else:

2> set the resumeCause in accordance with the information received from upper layers;

1> set the shortResumeMAC-I to the 16 least significant bits of the MAC-I calculated:

2> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortResumeMAC-Input (or
VarShortResumeMAC-Input-NB in NB-IoT);

2> with the KRRCint key and the previously configured integrity protection algorithm; and

2> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

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

2> if the UE supports DL channel quality reporting and cqi-Reporting is present in

SystemInformationBlockType2-NB:

3> set the cqi-NPDCCH to include the latest results of the downlink channel quality measurements of the
serving cell as specified in TS 36.133 [16];

NOTE 0: The downlink channel quality measurements may use measurement period T1 or T2, as defined in TS
36.133 [16]. In case period T2 is used the RRC-MAC interactions are left to UE implementation.

2> set earlyContentionResolution to TRUE;

1> restore the RRC configuration and security context from the stored UE AS context;

1> if the UE is initiating UP-EDT in accordance with conditions in 5.3.3.1b:

3GPP
Release 15 86 3GPP TS 36.331 V15.4.0 (2018-12)

2> restore the PDCP state and re-establish PDCP entities for all SRBs and all DRBs;

2> if drb-ContinueROHC has been provided in immediately preceding RRC connection release message, and the
UE is requesting to resume RRC connection in the same cell:

3> indicate to lower layers that stored UE AS context is used and that drb-ContinueROHC is configured;

3> continue the header compression protocol context for the DRBs configured with the header compression
protocol;

2> else:

3> indicate to lower layers that stored UE AS context is used;

3> reset the header compression protocol context for the DRBs configured with the header compression
protocol;

2> resume all SRBs and all DRBs;

2> derive the KeNB key based on the KASME key to which the current KeNB is associated, using the stored value of
nextHopChainingCount received in the RRCConnectionRelease message in the preceding connection, as
specified in TS 33.401 [32];

2> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401
[32];

2> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as
specified in TS 33.401 [32];

2> configure lower layers to resume integrity protection using the previously configured algorithm and the
KRRCint key derived in this subclause to all subsequent messages received and sent by the UE;

2> configure lower layers to resume ciphering and to apply the ciphering algorithm and the KRRCenc key derived
in this subclause to all subsequent messages received and sent by the UE;

2> configure lower layers to resume ciphering and to apply the ciphering algorithm and the KUPenc key derived in
this subclause immediately to the user data sent and received by the UE;

2> configure the lower layers to use EDT;

1> else:

2> if SRB1 was configured with NR PDCP:

3> for SRB1, release the NR PDCP entity and establish an E-UTRA PDCP entity with the current (MCG)
security configuration;

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

2> else:

3> for SRB1, restore the PDCP state and re-establish the PDCP entity;

If the UE is resuming the RRC connection from RRC_INACTIVE, the UE shall set the contents of
RRCConnectionResumeRequest message as follows:

2> if field useFullResumeID is signalled in SystemInformationBlockType2:

3> set the fullI-RNTI to the stored fullI-RNTI value provided in suspend;

2> else:

3> set the shortI-RNTI to the stored shortI-RNTI value provided in suspend;

2> restore the RRC configuration and the KeNB and KRRCint keys from the UE Inactive AS context except physical
layer, MAC configuration and pdcp-Config;

3GPP
Release 15 87 3GPP TS 36.331 V15.4.0 (2018-12)

2> set the shortResumeMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarINACTIVE-MAC-Input;

3> with the KRRCint key in the UE Inactive AS Context and the previously configured integrity protection
algorithm; and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

2> derive the KeNB key based on the current KeNB or the NH, using the stored nextHopChainingCount value, as
specified in TS 33.501 [86];

2> derive the KRRCenc key, the KRRCint and the KUPenc key;

2> apply the default configuration for SRB1 as specified in 9.2.1.1;

2> apply the default NR PDCP configuration as specified in TS 38.331 [82], section 9.2.1.1 for SRB1;

2> configure lower layers to resume integrity protection for all SRBs except SRB0 using the configured
algorithm and the KRRCint key derived in this subclause immediately, i.e., integrity protection shall be applied
to all subsequent messages received and sent by the UE;

2> configure lower layers to resume ciphering for all radio bearers except SRB0 and to apply the configured
ciphering algorithm, the KRRCenc key and the KUPenc key derived in this subclause, i.e. the ciphering
configuration shall be applied to all subsequent messages received and sent by the UE;

Following procedures are applied for both suspended RRC connection and RRC_INACTIVE:

2> resume SRB1;

NOTE 2: Until successful connection resumption, the default physical layer configuration and the default MAC
Main configuration are applied for the transmission of SRB0 and SRB1, and SRB1 is used only for the
transfer of RRCConnectionResume message.

The UE shall submit the RRCConnectionResumeRequest message to lower layers for transmission.

The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation.

If the UE is resuming the RRC connection from RRC_INACTIVE and if lower layers indicate an integrity check failure
while T300 is running, the UE shall perform actions specified in 5.3.3.16.

5.3.3.3b Actions related to transmission of RRCEarlyDataRequest message

The UE shall set the contents of RRCEarlyDataRequest message as follows:

1> set the s-TMSI to the value received from upper layers;

1> set the establishmentCause in accordance with the information received from upper layers;

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

2> if the UE supports DL channel quality reporting and cqi-Reporting is present in

SystemInformationBlockType2-NB:

3> set the cqi-NPDCCH to include the latest results of the downlink channel quality measurements of the
serving cell as specified in TS 36.133 [16];

NOTE: The downlink channel quality measurements may use measurement period T1 or T2, as defined in TS
36.133 [16]. In case period T2 is used the RRC-MAC interactions are left to UE implementation.

1> set the dedicatedInfoNAS to include the information received from upper layers;

The UE shall configure the lower layers to use EDT and submit the RRCEarlyDataRequest message to the lower layers
for transmission.

3GPP
Release 15 88 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.3.3c UE actions upon receiving EDT fallback indication from lower layers
Upon indication from lower layers that EDT is cancelled, the UE shall:

1> start or restart timer T300;

1> if the fallback is indicated by lower layers in response to the RRCEarlyDataRequest:

2> initiate transmission of RRCConnectionRequest message in accordance with 5.3.3.3;

1> else if the fallback is indicated by lower layers in response to the RRCConnectionResumeRequest for EDT and
the fallback is not due to the UL grant provided in Random Access Response not being for EDT:

2> perform the actions upon abortion of UP-EDT as specified in 5.3.3.9a;

2> initiate transmission of the RRCConnectionResumeRequest message in accordance with 5.3.3.3a;

NOTE: It is up to UE implementation to avoid data loss due to EDT fallback.

5.3.3.4 Reception of the RRCConnectionSetup by the UE

NOTE 1: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from a suspended RRC

connection:

2> release all radio resources, including release of the RLC entity, the MAC configuration and the associated
PDCP entity for all established or suspended RBs, except for SRB0;

2> discard the stored UE AS context and resumeIdentity;

2> if stored, discard the stored nextHopChainingCount;

2> if stored, discard the stored drb-ContinueROHC;

2> indicate to upper layers fallback of the RRC connection;

1> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest from

RRC_INACTIVE:

2> stop T380 if running;

2> discard stored UE Inactive AS context;

2> discard any current AS security context including the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc
key;

2> release radio resources for all established RBs except SRB0, including release of the RLC entities, of the
associated PDCP entities and of SDAP;

2> release the RRC configuration except for the default MAC main configuration and CCCH;

2> indicate to upper layers fallback of the RRC connection;

1> perform the radio resource configuration procedure in accordance with the received
radioResourceConfigDedicated and as specified in 5.3.10;

1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or
inherited from another RAT;

1> if stored, discard the dedicated offset provided by the redirectedCarrierOffsetDedicated;

1> stop timer T300;

1> stop timer T302, if running;

3GPP
Release 15 89 3GPP TS 36.331 V15.4.0 (2018-12)

1> stop timer T303, if running;

1> stop timer T305, if running;

1> stop timer T306, if running;

1> stop timer T308, if running;

1> perform the actions as specified in 5.3.3.7;

1> stop timer T320, if running;

1> stop timer T350, if running;

1> perform the actions as specified in 5.6.12.4;

1> release rclwi-Configuration, if configured, as specified in 5.6.16.2;

1> stop timer T360, if running;

1> stop timer T322, if running;

1> stop timer T309, if running, for all access categories;

1> enter RRC_CONNECTED;

1> stop the cell re-selection procedure;

1> consider the current cell to be the PCell;

1> set the content of RRCConnectionSetupComplete message as follows:

2> if the RRCConnectionSetup is received in response to an RRCConnectionResumeRequest:

3> if upper layers provide an S-TMSI:

4> set the s-TMSI to the value received from upper layers;

3> else if upper layers provide a 5G-S-TMSI:

4> set the ng-5G-S-TMSI-Bits to ng-5G-S-TMSI with the value received from upper layers;

2> else if upper layers provide a 5G-S-TMSI:

3> set the ng-5G-S-TMSI-Bits to ng-5G-S-TMSI-Part2 to the leftmost 8 bits of 5G-S-TMSI received from
upper layers;

2> set the selectedPLMN-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35])
from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1 (or
SystemInformationBlockType1-NB in NB-IoT);

2> if upper layers provide the 'Registered MME', include and set the registeredMME as follows:

3> if the PLMN identity of the 'Registered MME' is different from the PLMN selected by the upper layers:

4> include the plmnIdentity in the registeredMME and set it to the value of the PLMN identity in the
'Registered MME' received from upper layers;

3> set the mmegi and the mmec to the value received from upper layers;

2> if upper layers provided the 'Registered MME':

3> include and set the gummei-Type to the value provided by the upper layers;

2> if upper layers provide the 'Registered AMF', include and set the registeredAMF as follows:

3> if the PLMN identity of the 'Registered AMF' is different from the PLMN selected by the upper layers:

3GPP
Release 15 90 3GPP TS 36.331 V15.4.0 (2018-12)

4> include the plmnIdentity in the registeredAMF and set it to the value of the PLMN identity in the
'Registered AMF' received from upper layers;

3> set the amf-Identifier to the value received from upper layers;

2> if upper layers provided the 'Registered AMF':

3> include and set the guami-Type to the value provided by the upper layers;

2> if upper layers provide one or more S-NSSAI (see TS 23.003 [27]):

3> include the s-NSSAI-list and set the content to the values provided by the upper layers;

2> if the UE supports CIoT EPS optimisation(s):

3> include attachWithoutPDN-Connectivity if received from upper layers;

3> include up-CIoT-EPS-Optimisation if received from upper layers;

3> except for NB-IoT, include cp-CIoT-EPS-Optimisation if received from upper layers;

2> if connecting as an RN:

3> include the rn-SubframeConfigReq;

2> if the RRCConnectionSetup is received in response to RRCEarlyDataRequest:

3> set the dedicatedInfoNAS to a zero-length octet string;

2> else:

3> set the dedicatedInfoNAS to include the information received from upper layers;

2> if the UE is connected to EPC:

3> except for NB-IoT:

4> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the
RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

5> include rlf-InfoAvailable;

4> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in
plmn-IdentityList stored in VarLogMeasReport:

5> include logMeasAvailableMBSFN;

4> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in
plmn-IdentityList stored in VarLogMeasReport:

5> include logMeasAvailable;

4> if the UE has Bluetooth logged measurements available and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport:

5> include logMeasAvailableBT;

4> if the UE has WLAN logged measurements available and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport:

5> include logMeasAvailableWLAN;

4> if the UE has connection establishment failure information available in VarConnEstFailReport and if
the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

5> include connEstFailInfoAvailable;

3GPP
Release 15 91 3GPP TS 36.331 V15.4.0 (2018-12)

4> include the mobilityState and set it to the mobility state (as specified in TS 36.304 [4]) of the UE just
prior to entering RRC_CONNECTED state;

4> if the UE supports storage of mobility history information and the UE has mobility history
information available in VarMobilityHistoryReport:

5> include the mobilityHistoryAvail;

4> if the SIB2 contains idleModeMeasurements, and the UE has IDLE mode measurement information
available in VarMeasIdleReport:

5> include the idleMeasAvailable;

4> stop T331 (if running);

4> if the UE has flight path information available:

5> include flightPathInfoAvailable;

3> for NB-IoT:

4> if the UE supports serving cell idle mode measurements reporting and servingCellMeasInfo is present
in SystemInformationBlockType2-NB:

5> set the measResultServCell to include the measurements of the serving cell;

NOTE 2: The UE includes the latest results of the serving cell measurements as used for cell selection/ reselection
evaluation, which are performed in accordance with the performance requirements as specified in TS
36.133 [16].

3> include dcn-ID if a DCN-ID value (see TS 23.401 [41]) is received from upper layers;

2> if UE needs UL gaps during continuous uplink transmission:

3> include ue-CE-NeedULGaps;

1> submit the RRCConnectionSetupComplete message to lower layers for transmission;

1> the procedure ends:

5.3.3.4a Reception of the RRCConnectionResume by the UE

The UE shall:

1> stop timer T300;

1> stop timer T309, if running, for all access categories;

1> stop T380 if running;

1> except if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for EDT:

2> if resuming an RRC connection from a suspended RRC connection:

3> restore the PDCP state and re-establish PDCP entities for SRB2, if configured with E-UTRA PDCP, and
for all DRBs that are configured with E-UTRA PDCP;

3> if drb-ContinueROHC is included:

4> indicate to lower layers that stored UE AS context is used and that drb-ContinueROHC is configured;

4> continue the header compression protocol context for the DRBs configured with the header
compression protocol;

3> else:

4> indicate to lower layers that stored UE AS context is used;

3GPP
Release 15 92 3GPP TS 36.331 V15.4.0 (2018-12)

4> reset the header compression protocol context for the DRBs configured with the header compression
protocol;

3> discard the stored UE AS context and resumeIdentity;

2> else if the RRCConnectionResume message includes the fullConfig (for resuming an RRC connection from
RRC_INACTIVE):

3> perform the radio configuration procedure as specified in 5.3.5.8;

2> else (for resuming an RRC connection from RRC_INACTIVE)

3> re-establish PDCP entities for SRB2 and all DRBs;

3> restore the physical layer configuration, the MAC configuration, the RLC configuration and the PDCP
configuration from the stored UE Inactive AS context;

3> if drb-ContinueROHC is included:

4> indicate to lower layers that drb-ContinueROHC is configured;

3> discard the stored UE Inactive AS context, except ran-NotificationAreaInfo;

1> else:

2> discard the stored UE AS context and resumeIdentity;

1> perform the radio resource configuration procedure in accordance with the received
radioResourceConfigDedicated and as specified in 5.3.10;

NOTE: When performing the radio resource configuration procedure, for the physical layer configuration and the
MAC Main configuration, the restored RRC configuration from the stored UE AS context is used as basis
for the reconfiguration.

1> if the received RRCConnectionResume message includes the sk-Counter:

2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.8;

1> if the received RRCConnectionResume message includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionResume message includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> except if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for EDT:

2> resume SRB2 and all DRBs, if any, including RBs configured with NR PDCP;

1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or
inherited from another RAT;

1> if stored, discard the dedicated offset provided by the redirectedCarrierOffsetDedicated;

1> if the RRCConnectionResume message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> stop timer T302, if running;

1> stop timer T303, if running;

1> stop timer T305, if running;

1> stop timer T306, if running;

1> stop timer T308, if running;

3GPP
Release 15 93 3GPP TS 36.331 V15.4.0 (2018-12)

1> perform the actions as specified in 5.3.3.7;

1> stop timer T320, if running;

1> stop timer T350, if running;

1> perform the actions as specified in 5.6.12.4;

1> stop timer T360, if running;

1> stop timer T322, if running;

1> if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for EDT or an

RRCConnectionResumeRequest from RRC_INACTIVE:

2> ignore the nextHopChainingCount value indicated in the RRCConnectionResume message;

1> else:

2> if resuming an RRC connection from a suspended RRC connection:

3> update the KeNB key based on the KASME key to which the current KeNB is associated, using the
nextHopChainingCount value indicated in the RRCConnectionResume message, as specified in TS 33.401
[32];

3> store the nextHopChainingCount value;

3> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS
33.401 [32];

3> request lower layers to verify the integrity protection of the RRCConnectionResume message, using the
previously configured algorithm and the KRRCint key;

3> if the integrity protection check of the RRCConnectionResume message fails:

4> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause
'other', upon which the procedure ends;

3> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as
specified in TS 33.401 [32];

3> configure lower layers to resume integrity protection using the previously configured algorithm and the
KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and
sent by the UE;

3> configure lower layers to resume ciphering and to apply the ciphering algorithm, the KRRCenc key and the
KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent
by the UE;

1> enter RRC_CONNECTED;

1> indicate to upper layers that the suspended RRC connection has been resumed;

1> stop the cell re-selection procedure;

1> consider the current cell to be the PCell;

1> set the content of RRCConnectionResumeComplete message as follows:

2> set the selectedPLMN-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35])
from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1;

2> set the dedicatedInfoNAS to include the information received from upper layers;

2> except for NB-IoT:

3> if resuming an RRC connection from a suspended RRC connection:

3GPP
Release 15 94 3GPP TS 36.331 V15.4.0 (2018-12)

4> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the
RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

5> include rlf-InfoAvailable;

4> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in
plmn-IdentityList stored in VarLogMeasReport:

5> include logMeasAvailableMBSFN;

4> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in
plmn-IdentityList stored in VarLogMeasReport:

5> include logMeasAvailable;

4> if the UE has Bluetooth logged measurements available and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport:

5> include logMeasAvailableBT;

4> if the UE has WLAN logged measurements available and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport:

5> include logMeasAvailableWLAN;

4> if the UE has connection establishment failure information available in VarConnEstFailReport and if
the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

5> include connEstFailInfoAvailable;

4> include the mobilityState and set it to the mobility state (as specified in TS 36.304 [4]) of the UE just
prior to entering RRC_CONNECTED state;

3> if the UE supports storage of mobility history information and the UE has mobility history information
available in VarMobilityHistoryReport:

4> include mobilityHistoryAvail;

3> if the SIB2 contains idleModeMeasurements, and the UE has IDLE mode measurement information
available in VarMeasIdleReport:

4> include the idleMeasAvailable;

3> stop T331 (if running);

3> if the UE has flight path information available :

4> include flightPathInfoAvailable;

2> for NB-IoT:

3> if the UE supports serving cell idle mode measurements reporting and servingCellMeasInfo is present in
SystemInformationBlockType2-NB:

4> set the measResultServCell to include the measurements of the serving cell;

NOTE: The UE includes the latest results of the serving cell measurements as used for cell selection/ reselection
evaluation, which are performed in accordance with the performance requirements as specified in TS
36.133 [16].

1> submit the RRCConnectionResumeComplete message to lower layers for transmission;

1> the procedure ends.

5.3.3.4b Reception of the RRCEarlyDataComplete by the UE

The UE shall:

3GPP
Release 15 95 3GPP TS 36.331 V15.4.0 (2018-12)

1> indicate to upper layers that the RRC connection has been established;

1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or
inherited from another RAT;

1> if stored, discard the dedicated offset provided by the redirectedCarrierOffsetDedicated;

1> stop timer T300;

1> stop timer T302, if running;

1> stop timer T303, if running;

1> stop timer T305, if running;

1> stop timer T306, if running;

1> stop timer T308, if running;

1> perform the actions as specified in 5.3.3.7;

1> stop timer T320, if running;

1> stop timer T322, if running;

1> forward the dedicatedInfoNAS, if received, to the upper layers;

1> reset MAC and release the MAC configuration;

1> if the RRCEarlyDataComplete message includes redirectedCarrierInfo indicating redirection to geran; and

1> if upper layers indicate that redirect to GERAN without AS security is not allowed:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'other', upon
which the procedure ends;

1> if the RRCEarlyDataComplete message includes idleModeMobilityControlInfo:

2> store the cell reselection priority information provided by the idleModeMobilityControlInfo;

2> if the t320 is included:

3> start timer T320, with the timer value set according to the value of t320;

1> else:

2> apply the cell reselection priority information broadcast in the system information;

1> for NB-IoT, if the RRCEarlyDataComplete message includes redirectedCarrierInfo:

2> if the redirectedCarrierOffsetDedicated is included in the redirectedCarrierInfo:

3> store the dedicated offset for the frequency in redirectedCarrierInfo;

3> start timer T322, with the timer value set according to the value of T322 in redirectedCarrierInfo;

1> if the extendedWaitTime is present; and

1> if the UE supports delay tolerant access or the UE is a NB-IoT UE:

2> forward the extendedWaitTime to upper layers;

1> indicate the release of the RRC connection to upper layers together with the release cause 'other', upon which the
procedure ends;

3GPP
Release 15 96 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.3.5 Cell re-selection or cell selection while T300, T302, T303, T305, T306, T308
or T309 is running
The UE shall:

1> if in RRC_INACTIVE:

2> if cell reselection occurs while T300 or T302 is running:

3> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12 with release cause 'RRC
Resume failure';

1> else if cell reselection occurs while T300, T302, T303, T305, T306, or T308 is running:

2> if timer T302, T303, T305, T306, and/or T308 is running and if the UE is connected to EPC:

3> stop timer T302, T303, T305, T306, and T308, whichever ones were running;

3> perform the actions as specified in 5.3.3.7;

2> else if timer T302 is running and if the UE is connected to 5GC:

3> stop timer T302;

3> perform the actions as specified in 5.3.16.4;

2> if timer T300 is running:

3> stop timer T300;

3> if UE has sent RRCConnectionResumeRequest message and has not received RRCConnectionResume
message:

4> reset MAC;

4> if UE has initiated UP-EDT:

5> perform the actions upon abortion of UP-EDT as specified in 5.3.3.9a;

4> else:

5> re-establish RLC for all RBs that are established;

5> suspend SRB1;

3> else:

4> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established;

3> inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication;

1> else if cell selection or reselection occurs while T309 is running:

2> stop T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

5.3.3.6 T300 expiry

The UE shall:

1> if timer T300 expires:

2> if UE has sent RRCConnectionResumeRequest message and has not received RRCConnectionResume
message:

3GPP
Release 15 97 3GPP TS 36.331 V15.4.0 (2018-12)

3> reset MAC;

3> if UE has initiated UP-EDT:

4> perform the actions upon abortion of UP-EDT as specified in 5.3.3.9a;

3> else:

4> re-establish RLC for all RBs that are established;

4> suspend SRB1;

2> else:

3> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established;

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

3> if connEstFailOffset is included in SystemInformationBlockType2-NB:

4> use connEstFailOffset for the parameter Qoffsettemp for the concerned cell when performing cell
selection and reselection according to TS 36.304 [4];

3> else:

4> use value of infinity for the parameter Qoffsettemp for the concerned cell when performing cell
selection and reselection according to TS 36.304 [4];

NOTE 0: For NB-IoT, the number of times that the UE detects T300 expiry on the same cell before applying
connEstFailOffset and the amount of time that the UE applies connEstFailOffset before removing the
offset from evaluation of the cell is up to UE implementation.

2> else if the UE supports RRC Connection Establishment failure temporary Qoffset and T300 has expired a
consecutive connEstFailCount times on the same cell for which txFailParams is included in
SystemInformationBlockType2:

3> for a period as indicated by connEstFailOffsetValidity:

4> use connEstFailOffset for the parameter Qoffsettemp for the concerned cell when performing cell
selection and reselection according to TS 36.304 [4] and TS 25.304 [40];

NOTE 1: When performing cell selection, if no suitable or acceptable cell can be found, it is up to UE
implementation whether to stop using connEstFailOffset for the parameter Qoffsettemp during
connEstFailOffsetValidity for the concerned cell.

2> except for NB-IoT, store the following connection establishment failure information in the
VarConnEstFailReport by setting its fields as follows:

3> clear the information included in VarConnEstFailReport, if any;

3> set the plmn-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]) from the
PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1;

3> set the failedCellId to the global cell identity of the cell where connection establishment failure is
detected;

3> set the measResultFailedCell to include the RSRP and RSRQ, if available, of the cell where connection
establishment failure is detected and based on measurements collected up to the moment the UE detected
the failure;

3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-
selection, to include neighbouring cell measurements for at most the following number of neighbouring
cells: 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT
neighbours, per frequency/ set of frequencies (GERAN) per RAT and according to the following:

4> for each neighbour cell included, include the optional fields that are available;

3GPP
Release 15 98 3GPP TS 36.331 V15.4.0 (2018-12)

NOTE 2: The UE includes the latest results of the available measurements as used for cell reselection evaluation,
which are performed in accordance with the performance requirements as specified in TS 36.133 [16].

3> if available, set the logMeasResultListWLAN to include the WLAN measurement results, in order of
decreasing RSSI for WLAN APs;

3> if available, set the logMeasResultListBT to include the Bluetooth measurement results, in order of
decreasing RSSI for Bluetooth beacons;

3> if detailed location information is available, set the content of the locationInfo as follows:

4> include the locationCoordinates;

4> include the horizontalVelocity, if available;

3> set the numberOfPreamblesSent to indicate the number of preambles sent by MAC for the failed random
access procedure;

3> set contentionDetected to indicate whether contention resolution was not successful as specified in TS
36.321 [6] for at least one of the transmitted preambles for the failed random access procedure;

3> set maxTxPowerReached to indicate whether or not the maximum power level was used for the last
transmitted preamble, see TS 36.321 [6];

2> if in RRC_INACTIVE:

3> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12, with release cause 'RRC
connection failure';

2> else inform upper layers about the failure to establish the RRC connection or failure to resume the RRC
connection with suspend indication, upon which the procedure ends;

The UE may discard the connection establishment failure information, i.e. release the UE variable
VarConnEstFailReport, 48 hours after the failure is detected, upon power off or upon detach.

5.3.3.7 T302, T303, T305, T306, or T308 expiry or stop

If the UE is connected to EPC, the UE shall:

1> if timer T302 expires or is stopped:

2> inform upper layers about barring alleviation for mobile terminating access;

2> if timer T303 is not running:

3> inform upper layers about barring alleviation for mobile originating calls;

2> if timer T305 is not running:

3> inform upper layers about barring alleviation for mobile originating signalling;

2> if timer T306 is not running:

3> inform upper layers about barring alleviation for mobile originating CS fallback;

2> if timer T308 is not running:

3> inform upper layers about barring alleviation for ACDC;

1> if timer T303 expires or is stopped:

2> if timer T302 is not running:

3> inform upper layers about barring alleviation for mobile originating calls;

1> if timer T305 expires or is stopped:

3GPP
Release 15 99 3GPP TS 36.331 V15.4.0 (2018-12)

2> if timer T302 is not running:

3> inform upper layers about barring alleviation for mobile originating signalling;

1> if timer T306 expires or is stopped:

2> if timer T302 is not running:

3> inform upper layers about barring alleviation for mobile originating CS fallback;

1> if timer T308 expires or is stopped:

2> if timer T302 is not running:

3> inform upper layers about barring alleviation for ACDC;

5.3.3.8 Reception of the RRCConnectionReject by the UE

The UE shall:

1> stop timer T300;

1> stop timer T302, if running;

1> reset MAC;

1> except for NB-IoT, start timer T302, with the timer value set to the waitTime;

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

1> if the extendedWaitTime is present and the UE supports delay tolerant access:

2> forward the extendedWaitTime to upper layers;

1> if deprioritisationReq is included and the UE supports RRC Connection Reject with deprioritisation:

2> start or restart timer T325 with the timer value set to the deprioritisationTimer signalled;

2> store the deprioritisationReq until T325 expiry;

NOTE: The UE stores the deprioritisation request irrespective of any cell reselection absolute priority
assignments (by dedicated or common signalling) and regardless of RRC connections in E-UTRAN or
other RATs unless specified otherwise.

1> if the RRCConnectionReject is received in response to an RRCConnectionResumeRequest sent to resume a

suspended RRC connection:

2> if the rrc-SuspendIndication is not present:

3> release all radio resources, including release of the RLC entity, the MAC configuration and the associated
PDCP entity for all established or suspended RBs;

3> discard the stored UE AS context and resumeIdentity;

3> inform upper layers about the failure to resume the RRC connection without suspend indication and that
access barring for mobile originating calls, mobile originating signalling, mobile terminating access and
except for NB-IoT for mobile originating CS fallback is applicable, upon which the procedure ends;

2> else:

3> if the RRCConnectionReject is received in response to an RRCConnectionResumeRequest for EDT:

4> perform the actions upon abortion of UP-EDT as specified in 5.3.3.9a;

3> else:

4> suspend SRB1;

3GPP
Release 15 100 3GPP TS 36.331 V15.4.0 (2018-12)

3> inform upper layers about the failure to resume the RRC connection with suspend indication and that
access barring for mobile originating calls, mobile originating signalling, mobile terminating access and
except for NB-IoT for mobile originating CS fallback is applicable, upon which the procedure ends;

1> else if the RRCConnectionReject is received in response to an RRCConnectionResumeRequest sent while in

RRC_INACTIVE:

2> release the default MAC configuration;

2> if RRCConnectionReject is received in response to a request from upper layers:

3> inform the upper layer that access barring is applicable for all access categories except categories '0' and
'2';

2> if RRCConnectionReject is received in response to an RRCConnectionResumeRequest:

3> if resume is triggered by upper layers:

4> inform upper layers about the failure to resume the RRC connection;

3> if resume is triggered due to an RNA update:

4> set the variable pendingRnaUpdate to 'TRUE';

3> discard the current KeNB, KRRCenc key, KRRCint, KUPint key and KUPenc key;

3> suspend SRB1, upon which the procedure ends;

2> The UE shall continue to monitor RAN and CN paging while the timer T302 is running.

1> else:

2> release the default MAC configuration;

2> inform upper layers about the failure to establish the RRC connection and that access barring for mobile
originating calls, mobile originating signalling, mobile terminating access and except for NB-IoT, for mobile
originating CS fallback is applicable, upon which the procedure ends;

5.3.3.9 Abortion of RRC connection establishment

If upper layers abort the RRC connection establishment procedure while the UE has not yet entered
RRC_CONNECTED, the UE shall:

1> stop timer T300, if running;

1> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established;

5.3.3.9a Abortion of UP-EDT

The UE shall:

1> delete the KeNB, KRRCint, KRRCenc and KUPenc keys derived in accordance with 5.3.3.3a;

1> re-establish RLC entities for all SRBs and DRBs;

1> suspend all SRB(s) and DRB(s) except SRB0;

1> configure lower layers to suspend integrity protection and ciphering.

5.3.3.10 Handling of SSAC related parameters

Upon request from the upper layers, the UE shall:

3GPP
Release 15 101 3GPP TS 36.331 V15.4.0 (2018-12)

1> if SystemInformationBlockType2 includes ac-BarringPerPLMN-List and the ac-BarringPerPLMN-List contains

an AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers
(see TS 23.122 [11], TS 24.301 [35]):

2> select the AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by
upper layers;

2> in the remainder of this procedure, use the selected AC-BarringPerPLMN entry (i.e. presence or absence of
access barring parameters in this entry) irrespective of the common access barring parameters included in
SystemInformationBlockType2;

1> else:

2> in the remainder of this procedure use the common access barring parameters (i.e. presence or absence of
these parameters) included in SystemInformationBlockType2;

1> set the local variables BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice as follows:

2> if ssac-BarringForMMTEL-Voice is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which
is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the
HPLMN/ EHPLMN.

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC
contained in ssac-BarringForMMTEL-Voice is set to zero:

4> set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

3> else:

4> set BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice to the value of ac-

BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Voice, respectively;

2> else set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

1> set the local variables BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video as follows:

2> if ssac-BarringForMMTEL-Video is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which
is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC
contained in ssac-BarringForMMTEL-Video is set to zero:

4> set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

3> else:

4> set BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the value of ac-

BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Video, respectively;

2> else set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

1> forward the variables BarringFactorForMMTEL-Voice, BarringTimeForMMTEL-Voice,

BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the upper layers;

5.3.3.11 Access barring check

1> if timer T302 or "Tbarring" is running:

2> consider access to the cell as barred;

3GPP
Release 15 102 3GPP TS 36.331 V15.4.0 (2018-12)

1> else if SystemInformationBlockType2 includes "AC barring parameter":

2> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is
valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the
HPLMN/ EHPLMN.

2> for at least one of these valid Access Classes the corresponding bit in the ac-BarringForSpecialAC contained
in "AC barring parameter" is set to zero:

3> consider access to the cell as not barred;

2> else:

3> draw a random number 'rand' uniformly distributed in the range: 0 ≤ rand < 1;

3> if 'rand' is lower than the value indicated by ac-BarringFactor included in "AC barring parameter":

4> consider access to the cell as not barred;

3> else:

4> consider access to the cell as barred;

1> else:

2> consider access to the cell as not barred;

1> if access to the cell is barred and both timers T302 and "Tbarring" are not running:

2> draw a random number 'rand' that is uniformly distributed in the range 0 ≤ rand < 1;

2> start timer "Tbarring" with the timer value calculated as follows, using the ac-BarringTime included in "AC
barring parameter":

"Tbarring" = (0.7+ 0.6 * rand) * ac-BarringTime;

5.3.3.12 EAB check

The UE shall:

1> if SystemInformationBlockType14 is present:

2> if eab-PerRSRP is included:

3> if the establishmentCause received from higher layers is set to a value other than emergency; and

3> if the UE has no Access Class, as stored on the USIM, with a value in the range 11..15, which is valid for
the UE to use according to TS 22.011 [10] and TS 23.122 [11] :

4> if eab-PerRSRP is set to thresh0:

5> consider access to the cell as barred when in enhanced coverage as specified in TS 36.304 [4];

4> else if eab-PerRSRP is set to thresh1:

5> if the measured RSRP is less than the first entry in rsrp-ThresholdsPrachInfoList:

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first CE level are configured;

4> else if eab-PerRSRP is set to thresh2:

3GPP
Release 15 103 3GPP TS 36.331 V15.4.0 (2018-12)

5> if the measured RSRP is less than the second entry in rsrp-ThresholdsPrachInfoList:

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first and second CE levels are configured;

4> else if eab-PerRSRP is set to thresh3:

5> if the measured RSRP is less than the third entry in rsrp-ThresholdsPrachInfoList:

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first, second, and third CE levels are
configured;

2> if access to the cell is not barred due to eab-PerRSRP and eab-Param is included:

3> if the eab-Common is included in the eab-Param:

4> if the UE belongs to the category of UEs as indicated in the eab-Category contained in eab-Common;
and

4> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the
corresponding bit in the eab-BarringBitmap contained in eab-Common is set to one:

5> consider access to the cell as barred;

4> else:

5> consider access to the cell as not barred due to EAB;

3> else (the eab-PerPLMN-List is included in the eab-Param):

4> select the entry in the eab-PerPLMN-List corresponding to the PLMN selected by upper layers (see
TS 23.122 [11], TS 24.301 [35]);

4> if the eab-Config for that PLMN is included:

5> if the UE belongs to the category of UEs as indicated in the eab-Category contained in eab-
Config; and

5> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the
corresponding bit in the eab-BarringBitmap contained in eab-Config is set to one:

6> consider access to the cell as barred;

5> else:

6> consider access to the cell as not barred due to EAB;

4> else:

5> consider access to the cell as not barred due to EAB;

1> else:

2> consider access to the cell as not barred due to EAB;

5.3.3.13 Access barring check for ACDC

The UE shall:

1> if timer T302 is running:

3GPP
Release 15 104 3GPP TS 36.331 V15.4.0 (2018-12)

2> consider access to the cell as barred;

1> else if SystemInformationBlockType2 includes "ACDC barring parameter":

2> draw a random number 'rand' uniformly distributed in the range: 0 ≤ rand < 1;

2> if 'rand' is lower than the value indicated by ac-BarringFactor included in "ACDC barring parameter":

3> consider access to the cell as not barred;

2> else:

3> consider access to the cell as barred;

1> else:

2> consider access to the cell as not barred;

1> if access to the cell is barred and timer T302 is not running:

2> draw a random number 'rand' that is uniformly distributed in the range 0 ≤ rand < 1;

2> start timer "Tbarring" with the timer value calculated as follows, using the ac-BarringTime included in
"ACDC barring parameter":

"Tbarring" = (0.7+ 0.6 * rand) * ac-BarringTime.

5.3.3.14 Access Barring check for NB-IoT

The UE shall:

1> if ab-Enabled included in MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is set to TRUE and

SystemInformationBlockType14-NB is broadcast:

2> if ab-PerNRSRP is included:

3> if the establishmentCause received from higher layers is set to a value other than mo-ExceptionData; and

3> if the UE has no Access Class, as stored on the USIM, with a value in the range 11..15, which is valid for
the UE to use according to TS 22.011 [10] and TS 23.122 [11]:

4> if ab-PerNRSRP is set to thresh1:

5> if the measured RSRP is less than the first entry in rsrp-ThresholdsPrachInfoList;

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first NPRACH repetition level are configured;

4> if ab-PerNRSRP is set to thresh2:

5> if the measured RSRP is less than the second entry in rsrp-ThresholdsPrachInfoList;

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first and second NPRACH repetition levels
are configured;

2> if access to the cell is not barred due to ab-PerNRSRP and ab-Param is included:

3> if the ab-Common is included in ab-Param:

3GPP
Release 15 105 3GPP TS 36.331 V15.4.0 (2018-12)

4> if the UE belongs to the category of UEs as indicated in the ab-Category contained in ab-Common;
and

4> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the
corresponding bit in the ab-BarringBitmap contained in ab-Common is set to one:

5> if the establishmentCause received from higher layers is set to mo-ExceptionData and ab-
BarringForExceptionData is set to FALSE in the ab-Common:

6> consider access to the cell as not barred;

5> else:

6> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range
11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11] and
for at least one of these valid Access Classes for the UE, the corresponding bit in the ab-
BarringForSpecialAC contained in ab-Common is set to zero:

NOTE 1: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the
HPLMN/ EHPLMN.

7> consider access to the cell as not barred;

6> else:

7> consider access to the cell as barred;

4> else:

5> consider access to the cell as not barred;

3> else (the ab-PerPLMN-List is included in the ab-Param):

4> select the ab-PerPLMN entry in ab-PerPLMN-List corresponding to the PLMN selected by upper
layers (see TS 23.122 [11], TS 24.301 [35]);

4> if the ab-Config for that PLMN is included:

5> if the UE belongs to the category of UEs as indicated in the ab-Category contained in ab-Config;
and

5> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the
corresponding bit in the ab-BarringBitmap contained in ab-Config is set to one:

6> if the establishmentCause received from higher layers is set to mo-ExceptionData and ab-
BarringForExceptionData is set to FALSE in the ab-Config:

7> consider access to the cell as not barred;

6> else:

7> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range
11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11]
and for at least one of these valid Access Classes for the UE, the corresponding bit in the
ab-BarringForSpecialAC contained in ab-Config is set to zero:

NOTE 2: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the
HPLMN/ EHPLMN.

8> consider access to the cell as not barred;

7> else:

8> consider access to the cell as barred;

5> else:

3GPP
Release 15 106 3GPP TS 36.331 V15.4.0 (2018-12)

6> consider access to the cell as not barred;

4> else:

5> consider access to the cell as not barred;

1> else:

2> consider access to the cell as not barred;

5.3.3.15 Failure to deliver NAS information in RRCConnectionSetupComplete

message
The UE shall:

1> if the UE is a NB-IoT UE and radio link failure occurs before the successful delivery of
RRCConnectionSetupComplete message has been confirmed by lower layers:

2> inform upper layers about the possible failure to deliver the NAS information contained in the
RRCConnectionSetupComplete message;

5.3.3.16 Integrity check failure from lower layers while T300 is running for UP-EDT or
RRC_INACTIVE
The UE shall:

1> upon receiving integrity check failure indication from lower layers concerning SRB1 or SRB2 while T300 is
running for UP-EDT:

2> discard the stored UE AS context and resumeIdentity;

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'other';

1> upon receiving integrity check failure indication from lower layers while T300 is running and if the UE is
resuming the RRC connection from RRC_INACTIVE:

2> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12, with release cause 'RRC
connection failure';

5.3.3.17 Inability to comply with RRCConnectionResume

The UE shall:

1> if the UE is unable to comply with (part of) the configuration included in the RRCConnectionResume message;

2> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12 with release cause 'RRC Resume
failure'.

NOTE 1: The UE may apply above failure handling also in case the RRCConnectionResume message causes a
protocol error for which the generic error handling as defined in 5.7 specifies that the UE shall ignore the
message.

NOTE 2: If the UE is unable to comply with part of the configuration, it does not apply any part of the
configuration, i.e. there is no partial success/failure.

3GPP
Release 15 107 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.4 Initial security activation

5.3.4.1 General

UE EUTRAN

SecurityModeCommand

SecurityModeComplete

Figure 5.3.4.1-1: Security mode command, successful

UE EUTRAN

SecurityModeCommand

SecurityModeFailure

Figure 5.3.4.1-2: Security mode command, failure

The purpose of this procedure is to activate AS security upon RRC connection establishment.

5.3.4.2 Initiation
E-UTRAN initiates the security mode command procedure to a UE in RRC_CONNECTED. Moreover, E-UTRAN
applies the procedure as follows:

- when only SRB1, or for NB-IoT SRB1 and SRB1bis, is established, i.e. prior to establishment of SRB2 and/ or
DRBs.

5.3.4.3 Reception of the SecurityModeCommand by the UE

The UE shall:

1> derive the KeNB key, as specified in TS 33.401 [32] for E-UTRA/EPC, and TS 33.501 [86] for E-UTRA/5GC;

1> derive the KRRCint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand
message, as specified in TS 33.401 [32];

1> request lower layers to verify the integrity protection of the SecurityModeCommand message, using the
algorithm indicated by the integrityProtAlgorithm as included in the SecurityModeCommand message and the
KRRCint key;

1> if the SecurityModeCommand message passes the integrity protection check:

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm indicated in the
SecurityModeCommand message, as specified in TS 33.401 [32];

2> if connected as an RN:

3GPP
Release 15 108 3GPP TS 36.331 V15.4.0 (2018-12)

3> derive the KUPint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand
message, as specified in TS 33.401 [32];

2> configure lower layers to apply integrity protection using the indicated algorithm and the KRRCint key
immediately, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE,
including the SecurityModeComplete message;

2> configure lower layers to apply ciphering using the indicated algorithm, the KRRCenc key and the KUPenc key
after completing the procedure, i.e. ciphering shall be applied to all subsequent messages received and sent
by the UE, except for the SecurityModeComplete message which is sent unciphered;

2> if connected as an RN:

3> configure lower layers to apply integrity protection using the indicated algorithm and the KUPint key, for
DRBs that are subsequently configured to apply integrity protection, if any;

2> consider AS security to be activated;

2> upon RRC connection establishment, if UE does not need UL gaps during continuous uplink transmission:

3> configure lower layers to stop using UL gaps during continuous uplink transmission in FDD for
SecurityModeComplete message and subsequent uplink transmission in RRC_CONNECTED except for
UL transmissions as specified in TS 36.211 [21];

2> submit the SecurityModeComplete message to lower layers for transmission, upon which the procedure ends;

1> else:

2> continue using the configuration used prior to the reception of the SecurityModeCommand message, i.e.
neither apply integrity protection nor ciphering.

2> submit the SecurityModeFailure message to lower layers for transmission, upon which the procedure ends;

5.3.5 RRC connection reconfiguration

5.3.5.1 General

UE EUTRAN

RRCConnectionReconfiguration

RRCConnectionReconfigurationComplete

Figure 5.3.5.1-1: RRC connection reconfiguration, successful

3GPP
Release 15 109 3GPP TS 36.331 V15.4.0 (2018-12)

UE EUTRAN

RRCConnectionReconfiguration

RRC connection re-establishment

Figure 5.3.5.1-2: RRC connection reconfiguration, failure

The purpose of this procedure is to modify an RRC connection, e.g. to establish/ modify/ release RBs, to perform
handover, to setup/ modify/ release measurements, to add/ modify/ release SCells. As part of the procedure, NAS
dedicated information may be transferred from E-UTRAN to the UE.

5.3.5.2 Initiation
E-UTRAN may initiate the RRC connection reconfiguration procedure to a UE in RRC_CONNECTED. E-UTRAN
applies the procedure as follows:

- the mobilityControlInfo is included only when AS-security has been activated, and SRB2 with at least one DRB
are setup and not suspended;

- the establishment of RBs (other than SRB1, that is established during RRC connection establishment) is included
only when AS security has been activated;

- the addition of SCells is performed only when AS security has been activated;

5.3.5.3 Reception of an RRCConnectionReconfiguration not including the

mobilityControlInfo by the UE
If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply
with the configuration included in this message, the UE shall:

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection
re-establishment procedure:

2> re-establish PDCP for SRB2 configured with E-UTRA PDCP entity and for all DRBs that are established and
configured with E-UTRA PDCP, if any;

2> re-establish RLC for SRB2 and for all DRBs that are established and configured with E-UTRA RLC, if any;

2> if the RRCConnectionReconfiguration message includes the fullConfig:

3> perform the radio configuration procedure as specified in 5.3.5.8;

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

NOTE 1: Void

NOTE 2: Void

1> else:

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

3GPP
Release 15 110 3GPP TS 36.331 V15.4.0 (2018-12)

NOTE 3: If the RRCConnectionReconfiguration message includes the establishment of radio bearers other than
SRB1, the UE may start using these radio bearers immediately, i.e. there is no need to wait for an
outstanding acknowledgment of the SecurityModeComplete message.

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

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

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs configured with pdcp-Config and the received
RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release: or

1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:

2> perform EN-DC release as specified in TS 38.331 [82], clause 5.3.5.10;

1> if the received RRCConnectionReconfiguration includes the sk-Counter:

2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.7;

1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection
re-establishment procedure:

2> resume SRB2 and all DRBs that are suspended, if any, including RBs configured with NR PDCP;

NOTE 4: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the
re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling
of the SN and the HFN, is specified in TS 36.323 [8].

NOTE 5: The UE may discard SRB2 messages and data that it receives prior to completing the reconfiguration
used to resume these bearers.

1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:

2> perfom the actions upon reception of the SystemInformationBlockType1 message as specified in 5.2.2.7;

1> if the RRCConnectionReconfiguration message includes the dedicatedInfoNASList:

2> forward each element of the dedicatedInfoNASList to upper layers in the same order as listed;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> if the RRCConnectionReconfiguration message includes the otherConfig:

3GPP
Release 15 111 3GPP TS 36.331 V15.4.0 (2018-12)

2> perform the other configuration procedure as specified in 5.3.10.9;

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

2> perform the sidelink dedicated configuration procedure as specified in 5.3.10.15;

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

2> perform the V2X sidelink communication dedicated configuration procedure as specified in 5.3.10.15a;

1> if the RRCConnectionReconfiguration message includes wlan-OffloadInfo:

2> perform the dedicated WLAN offload configuration procedure as specified in 5.6.12.2;

1> if the RRCConnectionReconfiguration message includes rclwi-Configuration:

2> perform the WLAN traffic steering command procedure as specified in 5.6.16.2;

1> if the RRCConnectionReconfiguration message includes lwa-Configuration:

2> perform the LWA configuration procedure as specified in 5.6.14.2;

1> if the RRCConnectionReconfiguration message includes lwip-Configuration:

2> perform the LWIP reconfiguration procedure as specified in 5.6.17.2;

1> upon RRC connection establishment, if UE does not need UL gaps during continuous uplink transmission:

2> configure lower layers to stop using UL gaps during continuous uplink transmission in FDD for
RRCConnectionReconfigurationComplete message and subsequent uplink transmission in
RRC_CONNECTED except for UL transmissions as specified in TS36.211 [21];

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:

3> include perCC-GapIndicationList and numFreqEffective;

2> if the frequencies are configured for reduced measurement performance:

3> include numFreqEffectiveReduced;

2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new
configuration, upon which the procedure ends;

5.3.5.4 Reception of an RRCConnectionReconfiguration including the

mobilityControlInfo by the UE (handover)
If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the
configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> stop timer T370, if running;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity
indicated by the targetPhysCellId;

3GPP
Release 15 112 3GPP TS 36.331 V15.4.0 (2018-12)

1> else:

2> consider the target PCell to be one on the frequency of the source PCell with a physical cell identity indicated
by the targetPhysCellId;

1> stop timer T309, if running, for all access categories;

1> start synchronising to the DL of the target PCell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message
triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this
message.

1> if BL UE or UE in CE:

2> if sameSFN-Indication is not present in mobilityControlInfo:

3> acquire the MasterInformationBlock in the target PCell;

1> if makeBeforeBreak is configured:

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 cell(s);

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

1> reset MCG MAC and SCG MAC, if configured;

1> release uplinkDataCompression, if configured;

1> re-establish PDCP for all RBs configured with pdcp-config that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the
re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling
of the SN and the HFN, is specified in TS 36.323 [8].

NOTE 2a: At handover the pdcp-reestablish flag will be set for all RBs configured with NR PDCP in nr-
RadioBearerConfig TS 38.331 [82] which will cause the PDCP entity to be re-established also for these
RBs.

1> re-establish MCG RLC and SCG RLC, if configured, for all RBs that are established;

1> for each SCell configured for the UE other than the PSCell:

2> if the received RRCConnectionReconfiguration message includes sCellState for the SCell and indicates
activated:

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

2> else if the received RRCConnectionReconfiguration message includes sCellState 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;

1> apply the value of the newUE-Identity as the C-RNTI;

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in 5.3.5.8;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

3GPP
Release 15 113 3GPP TS 36.331 V15.4.0 (2018-12)

1> if the received RRCConnectionReconfiguration message includes the rach-Skip:

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

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the
received mobilityControlInfo;

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

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

2> perform SCG reconfiguration as specified in 5.3.10.10;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the securityConfigHO (without suffix) is included in the RRCConnectionReconfiguration:

2> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

3> update the KeNB key based on the KASME key taken into use with the latest successful NAS SMC
procedure, as specified in TS 33.401 [32];

2> else:

3> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value
indicated in the securityConfigHO, as specified in TS 33.401 [32];

2> store the nextHopChainingCount value;

2> if the securityAlgorithmConfig is included in the securityConfigHO:

3> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

3> if connected as an RN:

4> derive the KUPint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

3> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS
33.401 [32];

2> else:

3> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

3> if connected as an RN:

4> derive the KUPint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

3> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in
TS 33.401 [32];

2> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity
protection configuration shall be applied to all subsequent messages received and sent by the UE, including
the message used to indicate the successful completion of the procedure;

2> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering
configuration shall be applied to all subsequent messages received and sent by the UE, including the message
used to indicate the successful completion of the procedure;

1> else if the securityConfigHO-v1530 is included in the RRCConnectionReconfiguration:

3GPP
Release 15 114 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the nas-Container is received:

3> forward the nas-Container to upper layers;

2> if the keyChangeIndicator-r15 is received and is set to TRUE:

3> update the KeNB key based on the KAMF key, as specified in TS 33.501 [86];

2> else:

3> update the KeNB key based on the current KeNB or the NH, using the received nextHopChainingCount-r15,
as specified in TS 33.501 [86];

2> store the nextHopChainingCount-r15 value;

2> if the securityAlgorithmConfig-r15 is received:

3> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

3> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS
33.401 [32];

2> else:

3> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

3> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in
TS 33.401 [32];

1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release; or

1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE:

2> perform EN-DC release as specified in TS 38.331 [82], clause 5.3.5.10;

1> if the received RRCConnectionReconfiguration includes the sk-Counter:

2> perform key update procedure as specified in in TS 38.331 [82], clause 5.3.5.7;

1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig:

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3.

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6.

1> if connected as an RN:

2> configure lower layers to apply the integrity protection algorithm and the KUPint key, for current or
subsequently established DRBs that are configured to apply integrity protection, if any;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

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

1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:

2> perfom the actions upon reception of the SystemInformationBlockType1 message as specified in 5.2.2.7;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

3GPP
Release 15 115 3GPP TS 36.331 V15.4.0 (2018-12)

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> if the RRCConnectionReconfiguration message includes the otherConfig:

2> perform the other configuration procedure as specified in 5.3.10.9;

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

2> perform the sidelink dedicated configuration procedure as specified in 5.3.10.15;

1> if the RRCConnectionReconfiguration message includes wlan-OffloadInfo:

2> perform the dedicated WLAN offload configuration procedure as specified in 5.6.12.2;

1> if handoverWithoutWT-Change is not configured:

2> release the LWA configuration, if configured, as described in 5.6.14.3;

1> release the LWIP configuration, if configured, as described in 5.6.17.3;

1> if the RRCConnectionReconfiguration message includes rclwi-Configuration:

2> perform the WLAN traffic steering command procedure as specified in 5.6.16.2;

1> if the RRCConnectionReconfiguration message includes lwa-Configuration:

2> perform the LWA configuration procedure as specified in 5.6.14.2;

1> if the RRCConnectionReconfiguration message includes lwip-Configuration:

2> perform the LWIP reconfiguration procedure as specified in 5.6.17.2;

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

mobilityControlInfoV2X:

2> perform the V2X sidelink communication dedicated configuration procedure as specified in 5.3.10.15a;

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the
RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

3> include rlf-InfoAvailable;

2> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport and if T330 is not running:

3> include logMeasAvailableMBSFN;

2> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport:

3> include the logMeasAvailable;

2> if the UE has Bluetooth logged measurements available and if the RPLMN is included in plmn-IdentityList
stored in VarLogMeasReport:

3> include logMeasAvailableBT;

2> if the UE has WLAN logged measurements available and if the RPLMN is included in plmn-IdentityList
stored in VarLogMeasReport:

3> include logMeasAvailableWLAN;

3GPP
Release 15 116 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the UE has connection establishment failure information available in VarConnEstFailReport and if the
RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

3> include connEstFailInfoAvailable;

2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest:

3> include perCC-GapIndicationList and numFreqEffective;

2> if the frequencies are configured for reduced measurement performance:

3> include numFreqEffectiveReduced;

2> if the UE has flight path information available:

3> include flightPathInfoAvailable;

2> if the received RRCConnectionReconfiguration message included nr-SecondaryCellGroupConfig:

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure; or

1> if MAC indicates the successful reception of a PDCCH transmission addressed to C-RNTI and if rach-Skip is
configured:

2> stop timer T304;

2> release rach-Skip;

2> 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 PCell, if any;

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

NOTE 3: 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.

2> if the UE is configured to provide IDC indications:

3> if the UE has transmitted an InDeviceCoexIndication message during the last 1 second preceding
reception of the RRCConnectionReconfiguration message including mobilityControlInfo:

4> initiate transmission of the InDeviceCoexIndication message in accordance with 5.6.9.3;

2> if the UE is configured to provide power preference indications, overheating assistance information, SPS
assistance information, delay budget report or maximum bandwidth preference indications:

3> if the UE has transmitted a UEAssistanceInformation message during the last 1 second preceding
reception of the RRCConnectionReconfiguration message including mobilityControlInfo:

4> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

2> if SystemInformationBlockType15 is broadcast by the PCell:

3> if the UE has transmitted a MBMSInterestIndication message during the last 1 second preceding reception
of the RRCConnectionReconfiguration message including mobilityControlInfo:

4> ensure having a valid version of SystemInformationBlockType15 for the PCell;

4> determine the set of MBMS frequencies of interest in accordance with 5.8.5.3;

4> determine the set of MBMS services of interest in accordance with 5.8.5.3a;

3GPP
Release 15 117 3GPP TS 36.331 V15.4.0 (2018-12)

4> initiate transmission of the MBMSInterestIndication message in accordance with 5.8.5.4;

2> if SystemInformationBlockType18 is broadcast by the target PCell; and the UE transmitted a

SidelinkUEInformation message indicating a change of sidelink communication related parameters relevant
in target PCell (i.e. change of commRxInterestedFreq or commTxResourceReq, commTxResourceReqUC if
SystemInformationBlockType18 includes commTxResourceUC-ReqAllowed or
commTxResourceInfoReqRelay if PCell broadcasts SystemInformationBlockType19 including
discConfigRelay) during the last 1 second preceding reception of the RRCConnectionReconfiguration
message including mobilityControlInfo; or

2> if SystemInformationBlockType19 is broadcast by the target PCell; and the UE transmitted a

SidelinkUEInformation message indicating a change of sidelink discovery related parameters relevant in
target PCell (i.e. change of discRxInterest or discTxResourceReq, discTxResourceReqPS if
SystemInformationBlockType19 includes discConfigPS or discRxGapReq or discTxGapReq if the UE is
configured with gapRequestsAllowedDedicated set to true or if the UE is not configured with
gapRequestsAllowedDedicated and SystemInformationBlockType19 includes gapRequestsAllowedCommon)
during the last 1 second preceding reception of the RRCConnectionReconfiguration message including
mobilityControlInfo; or

2> if SystemInformationBlockType21 is broadcast by the target PCell; and the UE transmitted a

SidelinkUEInformation message indicating a change of V2X sidelink communication related parameters
relevant in target PCell (i.e. change of v2x-CommRxInterestedFreqList or v2x-CommTxResourceReq) during
the last 1 second preceding reception of the RRCConnectionReconfiguration message including
mobilityControlInfo:

3> initiate transmission of the SidelinkUEInformation message in accordance with 5.10.2.3;

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target PCell by acquiring system information from
that cell before performing RACH access in the target PCell, except for BL UEs or UEs in CE when
sameSFN-Indication is not present in mobilityControlInfo.

5.3.5.5 Reconfiguration failure

The UE shall:

1> if the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration
message:

2> continue using the configuration used prior to the reception of RRCConnectionReconfiguration message;

2> if security has not been activated:

3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause other;

2> else:

3> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the connection
reconfiguration procedure ends;

NOTE 1: The UE may apply above failure handling also in case the RRCConnectionReconfiguration message
causes a protocol error for which the generic error handling as defined in 5.7 specifies that the UE shall
ignore the message.

NOTE 2: If the UE is unable to comply with part of the configuration, it does not apply any part of the
configuration, i.e. there is no partial success/ failure.

NOTE 3: The compliance also covers the NR configuration carried within octet strings e.g. field nr-
SecondaryCellGroupConfig. I.e. the failure behaviour defined also applies in case the UE cannot comply
with the NR configuration or with the combination of (parts of) the LTE and NR configurations.

3GPP
Release 15 118 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.5.6 T304 expiry (handover failure)

The UE shall:

1> if T304 expires (handover failure):

NOTE 1: Following T304 expiry any dedicated preamble, if provided within the rach-ConfigDedicated, is not
available for use by the UE anymore.

2> revert back to the configuration used in the source PCell, excluding the configuration configured by the
physicalConfigDedicated, the mac-MainConfig and the sps-Config;

NOTE 1a: In the context above, "the configuration" includes state variables and parameters of each radio bearer.
PDCP entities associtated with RLC UM and SRB bearers are reset after the successful RRC connection
re-establishment procedure according to Section 5.2 in TS 36.323 [8]. In EN-DC, "the configuration"
includes the RB configuration using NR PDCP (i.e. as configured by nr-RadioBearerConfig1 and nr-
RadioBearerConfig2).

2> store the following handover failure information in VarRLF-Report by setting its fields as follows:

3> clear the information included in VarRLF-Report, if any;

3> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);

3> set the measResultLastServCell to include the RSRP and RSRQ, if available, of the source PCell based on
measurements collected up to the moment the UE detected handover failure and in accordance with the
following;

4> if the UE includes rsrqResult, include the lastServCellRSRQ-Type;

3> set the measResultNeighCells to include the best measured cells, other than the source PCell, ordered such
that the best cell is listed first, and based on measurements collected up to the moment the UE detected
handover failure, and set its fields as follows;

4> if the UE was configured to perform measurements for one or more EUTRA frequencies, include the
measResultListEUTRA;

4> if the UE includes rsrqResult, include the rsrq-Type;

4> if the UE was configured to perform measurement reporting for one or more neighbouring UTRA
frequencies, include the measResultListUTRA;

4> if the UE was configured to perform measurement reporting for one or more neighbouring GERAN
frequencies, include the measResultListGERAN;

4> if the UE was configured to perform measurement reporting for one or more neighbouring
CDMA2000 frequencies, include the measResultsCDMA2000;

4> for each neighbour cell included, include the optional fields that are available;

NOTE 2: The measured quantities are filtered by the L3 filter as configured in the mobility measurement
configuration. The measurements are based on the time domain measurement resource restriction, if
configured. Blacklisted cells are not required to be reported.

3> if available, set the logMeasResultListWLAN to include the WLAN measurement results, in order of
decreasing RSSI for WLAN APs;

3> if available, set the logMeasResultListBT to include the Bluetooth measurement results, in order of
decreasing RSSI for Bluetooth beacons;

3> if detailed location information is available, set the content of the locationInfo as follows:

4> include the locationCoordinates;

4> include the horizontalVelocity, if available;

3GPP
Release 15 119 3GPP TS 36.331 V15.4.0 (2018-12)

3> set the failedPCellId to the global cell identity, if available, and otherwise to the physical cell identity and
carrier frequency of the target PCell of the failed handover;

3> include previousPCellId and set it to the global cell identity of the PCell where the last
RRCConnectionReconfiguration message including mobilityControlInfo was received;

3> set the timeConnFailure to the elapsed time since reception of the last RRCConnectionReconfiguration
message including the mobilityControlInfo;

3> set the connectionFailureType to 'hof';

3> set the c-RNTI to the C-RNTI used in the source PCell;

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection
reconfiguration procedure ends;

The UE may discard the handover failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the
failure is detected, upon power off or upon detach.

NOTE 3: E-UTRAN may retrieve the handover failure information using the UE information procedure with rlf-
ReportReq set to true, as specified in 5.6.5.3.

5.3.5.7 Void

5.3.5.7a T307 expiry (SCG change failure)

The UE shall:

1> if T307 expires:

NOTE 1: Following T307 expiry any dedicated preamble, if provided within the rach-ConfigDedicatedSCG, is not
available for use by the UE anymore.

2> initiate the SCG failure information procedure as specified in 5.6.13 to report SCG change failure;

5.3.5.8 Radio Configuration involving full configuration option

The UE shall:

1> if the UE is connected to EPC:

2> release/ clear all current dedicated radio configurations except the MCG C-RNTI, the MCG security
configuration and the PDCP, RLC, logical channel configurations for the RBs and the logged measurement
configuration;

1> else if the UE is connected to 5GC:

2> release/ clear all current dedicated radio configurations except the MCG C-RNTI, the MCG security
configuration and the configurations (SDAP if configured, PDCP, RLC and logical channel) for the RBs;

NOTE 1: Radio configuration is not just the resource configuration but includes other configurations like
MeasConfig and OtherConfig. In case EN-DC is configured, this also includes the entire NR SCG
configuration. Such NR SCG configuration does not include the DRB configuration as configured by nr-
RadioBearerConfig1 and nr-RadioBearerConfig2).

1> if the RRCConnectionReconfiguration message includes the mobilityControlInfo:

2> release/ clear all current common radio configurations;

2> use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;

1> else:

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);

3GPP
Release 15 120 3GPP TS 36.331 V15.4.0 (2018-12)

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

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

1> for each srb-Identity value included in the srb-ToAddModList (SRB reconfiguration):

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

2> apply the corresponding default RLC configuration for the SRB specified in 9.2.1.1 for SRB1 or in 9.2.1.2
for SRB2;

2> apply the corresponding default logical channel configuration for the SRB as specified in 9.2.1.1 for SRB1 or
in 9.2.1.2 for SRB2;

2> if the corresponding SRB was configured with NR PDCP and the UE is connected to EPC:

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

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

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

NOTE 2: This is to get the SRBs (SRB1 and SRB2 for handover and SRB2 for reconfiguration after
reestablishment) to a known state from which the reconfiguration message can do further configuration.

2> else if the UE is connected to 5GC:

3> apply the corresponding default PDCP configuration for the SRB as specified in TS 38.331 [82], clause
9.2.1;

1> if the UE is connected to EPC:

2> for each eps-BearerIdentity value included in the drb-ToAddModList or nr-RadioBearerConfig1 or nr-
RadioBearerConfig2 that is part of the current E-UTRA and NR UE configuration:

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

3> release the RLC entity or entities;

3> release the DTCH logical channel;

3> release the drb-identity;

NOTE 3: This will retain the eps-bearerIdentity but remove the DRBs including drb-identity of these bearers from
the current UE configuration and trigger the setup of the DRBs within the AS in Section 5.3.10.3 using
the new configuration. The eps-bearerIdentity 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).

2> for each eps-BearerIdentity value that is part of the current E-UTRA and NR UE configuration but not added
with same eps-BearerIdentity in drb-ToAddModList nor in nr-RadioBearerConfig1 nor in nr-
RadioBearerConfig2:

3> perform DRB release as specified in 5.3.10.2;

1> if the UE is connected to 5GC:

2> for each pdu-Session that is part of the current NR UE configuration:

3> release the SDAP entity (clause 5.1.2 in TS 37.324 [97]);

3GPP
Release 15 121 3GPP TS 36.331 V15.4.0 (2018-12)

3> release the NR PDCP entity for each DRB associated to the pdu-Session;

3> release the RLC entity or entities for each DRB associated to the pdu-Session;

3> release the DTCH logical channel for each DRB associated to the pdu-Session;

3> release the drb-identity for each DRB associated to the pdu-Session;

NOTE 4: This will retain the pdu-Session but remove the DRBs including drb-identity of these bearers from the
current NR UE configuration and trigger the setup of the DRBs within the AS in Section 5.3.10.3 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).

2> for each pdu-Session that is part of the current NR UE configuration but not added with same pdu-Session in
nr-RadioBearerConfig1 nor in nr-RadioBearerConfig2:

3> indicate the release of the user plane resources for the pdu-Session to upper layers;

5.3.6 Counter check

5.3.6.1 General

UE EUTRAN

CounterCheck

CounterCheckResponse

Figure 5.3.6.1-1: Counter check procedure

The counter check procedure is used by E-UTRAN to request the UE to verify the amount of data sent/ received on
each DRB. More specifically, the UE is requested to check if, for each DRB, the most significant bits of the COUNT
match with the values indicated by E-UTRAN.

NOTE: The procedure enables E-UTRAN to detect packet insertion by an intruder (a 'man in the middle').

5.3.6.2 Initiation
E-UTRAN initiates the procedure by sending a CounterCheck message.

NOTE: E-UTRAN may initiate the procedure when any of the COUNT values reaches a specific value.

5.3.6.3 Reception of the CounterCheck message by the UE

Upon receiving the CounterCheck message, the UE shall:

1> for each DRB that is established:

2> if no COUNT exists for a given direction (uplink or downlink) because it is a uni-directional bearer
configured only for the other direction:

3> assume the COUNT value to be 0 for the unused direction;

2> if the drb-Identity is not included in the drb-CountMSB-InfoList:

3GPP
Release 15 122 3GPP TS 36.331 V15.4.0 (2018-12)

3> include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-
Identity, the count-Uplink and the count-Downlink set to the value of the corresponding COUNT;

2> else if, for at least one direction, the most significant bits of the COUNT are different from the value
indicated in the drb-CountMSB-InfoList:

3> include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-
Identity, the count-Uplink and the count-Downlink set to the value of the corresponding COUNT;

1> for each DRB that is included in the drb-CountMSB-InfoList in the CounterCheck message that is not
established:

2> include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-
Identity, the count-Uplink and the count-Downlink with the most significant bits set identical to the
corresponding values in the drb-CountMSB-InfoList and the least significant bits set to zero;

1> submit the CounterCheckResponse message to lower layers for transmission upon which the procedure ends;

5.3.7 RRC connection re-establishment

5.3.7.1 General

UE EUTRAN

RRCConnectionReestablishmentRequest

RRCConnectionReestablishment

RRCConnectionReestablishmentComplete

Figure 5.3.7.1-1: RRC connection re-establishment, successful

UE EUTRAN

RRCConnectionReestablishmentRequest

RRCConnectionReestablishmentReject

Figure 5.3.7.1-2: RRC connection re-establishment, failure

The purpose of this procedure is to re-establish the RRC connection, which involves the resumption of SRB1 (SRB1bis
for a NB-IoT UE for which AS security has not been activated) operation, the re-activation of security (except for a NB-
IoT UE for which AS security has not been activated) and the configuration of only the PCell.

Except for a NB-IoT UE for which AS security has not been activated, a UE in RRC_CONNECTED, for which security
has been activated, may initiate the procedure in order to continue the RRC connection. The connection re-
establishment succeeds only if the concerned cell is prepared i.e. has a valid UE context. In case E-UTRAN accepts the
re-establishment, SRB1 operation resumes while the operation of other radio bearers remains suspended. If AS security
has not been activated, the UE does not initiate the procedure but instead moves to RRC_IDLE directly.

3GPP
Release 15 123 3GPP TS 36.331 V15.4.0 (2018-12)

When AS security has not been activated, a NB-IoT UE supporting RRC connection re-establishment for the Control
Plane CIoT EPS optimisation in RRC_CONNECTED may initiate the procedure in order to continue the RRC
connection.

E-UTRAN applies the procedure as follows:

- When AS security has been activated:

- to reconfigure SRB1 and to resume data transfer only for this RB;

- to re-activate AS security without changing algorithms.

- For a NB-IoT UE supporting RRC connection re-establishment for the Control Plane CIoT EPS optimisation,
when AS security has not been activated:

- to re-establish SRB1bis and to continue data transfer for this RB.

5.3.7.2 Initiation
The UE shall only initiate the procedure either when AS security has been activated or for a NB-IoT UE supporting
RRC connection re-establishment for the Control Plane CIoT EPS optimisation. The UE initiates the procedure when
one of the following conditions is met:

1> upon detecting radio link failure, in accordance with 5.3.11; or

1> upon handover failure, in accordance with 5.3.5.6; or

1> upon mobility from E-UTRA failure, in accordance with 5.4.3.5; or

1> except for UP-EDT, upon integrity check failure indication from lower layers concerning SRB1 or SRB2; or

1> upon an RRC connection reconfiguration failure, in accordance with 5.3.5.5; or

1> upon an RRC connection reconfiguration failure, in accordance with TS38.331 [82], clause 5.3.5.5.

NOTE: For UP-EDT, integrity check failure indication from lower layers is handled in accordance with subclause
5.3.3.16.

Upon initiation of the procedure, the UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;

1> stop timer T313, if running;

1> stop timer T307, if running;

1> start timer T311;

1> stop timer T370, if running;

1> release uplinkDataCompression, if configured;

1> suspend all RBs, including RBs configured with NR PDCP, except SRB0;

1> reset MAC;

1> release the MCG SCell(s), if configured, in accordance with 5.3.10.3a;

1> apply the default physical channel configuration as specified in 9.2.4;

1> except for NB-IoT, for the MCG, apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> for NB-IoT, release schedulingRequestConfig, if configured;

1> for the MCG, apply the default MAC main configuration as specified in 9.2.2;

3GPP
Release 15 124 3GPP TS 36.331 V15.4.0 (2018-12)

1> release powerPrefIndicationConfig, if configured and stop timer T340, if running;

1> release reportProximityConfig, if configured and clear any associated proximity status reporting timer;

1> release obtainLocationConfig, if configured;

1> release idc-Config, if configured;

1> release sps-AssistanceInfoReport, if configured;

1> release measSubframePatternPCell, if configured;

1> release the entire SCG configuration, if configured, except for the DRB configuration (as configured by drb-
ToAddModListSCG);

1> if EN-DC is configured:

2> perform EN-DC release, as specified in TS 38.331[82], clause 5.3.5.10;

2> release p-MaxEUTRA, if configured;

2> release p-MaxUE-FR1, if configured;

2> release tdm-PatternConfig, if configured;

1> release naics-Info for the PCell, if configured;

1> if connected as an RN and configured with an RN subframe configuration:

2> release the RN subframe configuration;

1> release the LWA configuration, if configured, as described in 5.6.14.3;

1> release the LWIP configuration, if configured, as described in 5.6.17.3;

1> release delayBudgetReportingConfig, if configured and stop timer T342, if running;

1> perform cell selection in accordance with the cell selection process as specified in TS 36.304 [4];

1> release bw-PreferenceIndicationTimer, if configured and stop timer T341, if running;

1> release overheatingAssistanceConfig, if configured and stop timer T345, if running;

1> release ailc-BitConfig, if configured;

5.3.7.3 Actions following cell selection while T311 is running

Upon selecting a suitable E-UTRA cell, the UE shall:

1> if the UE is connected to 5GC and the selected cell is only connected to EPC; or

1> if the UE is connected to EPC and the selected cell is only connected to 5GC:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
connection failure';

1> else:

2> stop timer T311;

2> start timer T301;

2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

2> if the UE is a NB-IoT UE supporting RRC connection re-establishment for the Control Plane CIoT EPS
optimisation and AS security has not been activated; and

2> if cp-reestablishment is not included in SystemInformationBlockType2-NB:

3GPP
Release 15 125 3GPP TS 36.331 V15.4.0 (2018-12)

3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
connection failure';

2> else:

3> initiate transmission of the RRCConnectionReestablishmentRequest message in accordance with 5.3.7.4;

NOTE: This procedure applies also if the UE returns to the source PCell.

Upon selecting an inter-RAT cell, the UE shall:

1> if the selected cell is a UTRA cell, and if the UE supports Radio Link Failure Report for Inter-RAT MRO,
include selectedUTRA-CellId in the VarRLF-Report and set it to the physical cell identity and carrier frequency
of the selected UTRA cell;

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
connection failure';

5.3.7.4 Actions related to transmission of RRCConnectionReestablishmentRequest

message
Except for NB-IoT, if the procedure was initiated due to radio link failure or handover failure, the UE shall:

1> set the reestablishmentCellId in the VarRLF-Report to the global cell identity of the selected cell;

The UE shall set the contents of RRCConnectionReestablishmentRequest message as follows:

1> except for a NB-IoT UE for which AS security has not been activated, set the ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source PCell (handover and mobility from E-UTRA failure) or used
in the PCell in which the trigger for the re-establishment occurred (other cases);

2> set the physCellId to the physical cell identity of the source PCell (handover and mobility from E-UTRA
failure) or of the PCell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input (or
VarShortMAC-Input-NB in NB-IoT);

3> with the KRRCint key and integrity protection algorithm that was used in the source PCell (handover and
mobility from E-UTRA failure) or of the PCell in which the trigger for the re-establishment occurred
(other cases); and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

1> for a NB-IoT UE for which AS security has not been activated, set the ue-Identity as follows:

2> request upper layers for calculated ul-NAS-MAC and ul-NAS-Count using the cellIdentity indicated in
SystemInformationBlockType1-NB of the current cell;

2> set the s-TMSI to the S-TMSI provided by upper layers;

2> set the ul-NAS-MAC to the ul-NAS-MAC value provided by upper layers;

2> set the ul-NAS-Count to the ul-NAS-Count value provided by upper layers;

1> set the reestablishmentCause as follows:

2> if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.5 (the UE is
unable to comply with the reconfiguration):

3> set the reestablishmentCause to the value reconfigurationFailure;

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE
handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3GPP
Release 15 126 3GPP TS 36.331 V15.4.0 (2018-12)

3> set the reestablishmentCause to the value handoverFailure;

2> else:

3> set the reestablishmentCause to the value otherFailure;

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

2> if the UE supports DL channel quality reporting and cqi-Reporting is present in

SystemInformationBlockType2-NB:

3> set the cqi-NPDCCH to include the latest results of the downlink channel quality measurements of the
serving cell as specified in TS 36.133 [16];

NOTE: The downlink channel quality measurements may use measurement period T1 or T2, as defined in TS
36.133 [16]. In case period T2 is used the RRC-MAC interactions are left to UE implementation.

2> set earlyContentionResolution to TRUE;

The UE shall submit the RRCConnectionReestablishmentRequest message to lower layers for transmission.

5.3.7.5 Reception of the RRCConnectionReestablishment by the UE

NOTE 1: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> stop timer T301;

1> consider the current cell to be the PCell;

1> except for a NB-IoT UE for which AS security has not been activated:

2> if SRB1 was configured with NR PDCP and the UE is connected to EPC:

3> for SRB1, release the NR PDCP entity and establish an E-UTRA PDCP entity with the current (MCG)
security configuration;

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

2> else:

3> for SRB1, re-establish the PDCP entity;

2> re-establish RLC for SRB1;

2> perform the radio resource configuration procedure in accordance with the received
radioResourceConfigDedicated and as specified in 5.3.10;

2> resume SRB1;

NOTE 2: E-UTRAN should not transmit any message on SRB1 prior to receiving the
RRCConnectionReestablishmentComplete message.

2> if UE is connected to EPC, update the KeNB key based on the KASME key to which the current KeNB is
associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment
message, as specified in TS 33.401 [32];

2> else if UE is connected to 5GC, update the KeNB key based on the KAMF key to which the current KeNB is
associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment
message, as specified in TS 33.501 [86];

2> store the nextHopChainingCount value;

2> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401
[32];

3GPP
Release 15 127 3GPP TS 36.331 V15.4.0 (2018-12)

2> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as
specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the previously configured integrity algorithm, as specified in TS
33.401 [32];

2> configure lower layers to activate integrity protection using the previously configured algorithm and the
KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and
sent by the UE, including the message used to indicate the successful completion of the procedure;

2> if connected as an RN:

3> configure lower layers to apply integrity protection using the previously configured algorithm and the
KUPint key, for subsequently resumed or subsequently established DRBs that are configured to apply
integrity protection, if any;

2> configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenc key and the
KUPenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the
UE, including the message used to indicate the successful completion of the procedure;

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

3> if the UE is connected to EPC:

4> set the content of RRCConnectionReestablishmentComplete message as follows:

5> if the UE has radio link failure or handover failure information available in VarRLF-Report and if
the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

6> include the rlf-InfoAvailable;

5> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included
in plmn-IdentityList stored in VarLogMeasReport and if T330 is not running:

6> include logMeasAvailableMBSFN;

5> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in
plmn-IdentityList stored in VarLogMeasReport:

6> include the logMeasAvailable;

5> if the UE has Bluetooth logged measurements available and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport:

6> include the logMeasAvailableBT;

5> if the UE has WLAN logged measurements available and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport:

6> include the logMeasAvailableWLAN;

5> if the UE has connection establishment failure information available in VarConnEstFailReport and
if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

6> include the connEstFailInfoAvailable;

5> if the UE has flight path information available:

6> include flightPathInfoAvailable;

3> perform the measurement related actions as specified in 5.5.6.1;

3> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

2> else:

3GPP
Release 15 128 3GPP TS 36.331 V15.4.0 (2018-12)

3> if the UE supports serving cell idle mode measurements reporting and servingCellMeasInfo is present in
SystemInformationBlockType2-NB:

4> set the measResultServCell to include the measurements of the serving cell;

NOTE 2a: The UE includes the latest results of the serving cell measurements as used for cell selection/
reselection evaluation, which are performed in accordance with the performance requirements as
specified in TS 36.133 [16].

2> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission;

2> if SystemInformationBlockType15 is broadcast by the PCell:

3> if the UE has transmitted an MBMSInterestIndication message during the last 1 second preceding
detection of radio link failure:

4> ensure having a valid version of SystemInformationBlockType15 for the PCell;

4> determine the set of MBMS frequencies of interest in accordance with 5.8.5.3;

4> determine the set of MBMS services of interest in accordance with 5.8.5.3a;

4> initiate transmission of the MBMSInterestIndication message in accordance with 5.8.5.4;

2> if SystemInformationBlockType18 is broadcast by the PCell; and the UE transmitted a

SidelinkUEInformation message indicating a change of sidelink communication related parameters relevant
in PCell (i.e. change of commRxInterestedFreq or commTxResourceReq, commTxResourceReqUC if
SystemInformationBlockType18 includes commTxResourceUC-ReqAllowed or
commTxResourceInfoReqRelay if PCell broadcasts SystemInformationBlockType19 including
discConfigRelay) during the last 1 second preceding detection of radio link failure; or

2> if SystemInformationBlockType19 is broadcast by the PCell; and the UE transmitted a

SidelinkUEInformation message indicating a change of sidelink discovery related parameters relevant in
PCell (i.e. change of discRxInterest or discTxResourceReq, discTxResourceReqPS if
SystemInformationBlockType19 includes discConfigPS or discRxGapReq or discTxGapReq if the UE is
configured with gapRequestsAllowedDedicated set to true or if the UE is not configured with
gapRequestsAllowedDedicated and SystemInformationBlockType19 includes gapRequestsAllowedCommon)
during the last 1 second preceding detection of radio link failure; or

2> if SystemInformationBlockType21 including sl-V2X-ConfigCommon is broadcast by the PCell; and the UE

transmitted a SidelinkUEInformation message indicating a change of V2X sidelink communication related
parameters relevant in PCell (i.e. change of v2x-CommRxInterestedFreqList or v2x-CommTxResourceReq)
during the last 1 second preceding detection of radio link failure:

3> initiate transmission of the SidelinkUEInformation message in accordance with 5.10.2.3;

1> for a NB-IoT UE for which AS security has not been activated:

2> validate dl-NAS-MAC, as specified in TS 33.401 [32];

2> if dl-NAS-MAC check fails:

3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
connection failure', upon which the procedure ends;

2> except for a UE that only supports the Control Plane CIoT EPS optimisation:

3> re-establish PDCP for SRB1;

3> re-establish RLC for SRB1;

2> re-establish RLC for SRB1bis;

2> perform the radio resource configuration procedure in accordance with the received
radioResourceConfigDedicated and as specified in 5.3.10;

3GPP
Release 15 129 3GPP TS 36.331 V15.4.0 (2018-12)

2> except for a UE that only supports the Control Plane CIoT EPS optimisation:

3> resume SRB1;

2> resume SRB1bis;

NOTE 3: E-UTRAN should not transmit any message on SRB1bis prior to receiving the
RRCConnectionReestablishmentComplete message.

2> if the UE supports serving cell idle mode measurements reporting and servingCellMeasInfo is present in
SystemInformationBlockType2-NB:

3> set the measResultServCell to include the measurements of the serving cell;

NOTE 4: The UE includes the latest results of the serving cell measurements as used for cell selection/ reselection
evaluation, which are performed in accordance with the performance requirements as specified in TS
36.133 [16].

2> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission;

1> the procedure ends;

5.3.7.6 T311 expiry

Upon T311 expiry, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
connection failure';

5.3.7.7 T301 expiry or selected cell no longer suitable

The UE shall:
1> if timer T301 expires; or

1> if the selected cell becomes no longer suitable according to the cell selection criteria as specified in TS 36.304
[4]:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
connection failure';

5.3.7.8 Reception of RRCConnectionReestablishmentReject by the UE

Upon receiving the RRCConnectionReestablishmentReject message, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
connection failure';

5.3.8 RRC connection release

5.3.8.1 General

UE EUTRAN

RRCConnectionRelease

Figure 5.3.8.1-1: RRC connection release, successful

The purpose of this procedure is:

3GPP
Release 15 130 3GPP TS 36.331 V15.4.0 (2018-12)

- to release the RRC connection, which includes the release of the established radio bearers as well as all radio
resources; or

- to suspend the RRC connection for both suspended RRC connection or RRC_INACTIVE, which includes the
suspension of the established radio bearers.

- to complete the UP-EDT procedure, which includes the release or suspension of the established radio bearers.

5.3.8.2 Initiation
E-UTRAN initiates the RRC connection release procedure to a UE in RRC_CONNECTED or in RRC_INACTIVE or
to complete UP-EDT.

5.3.8.3 Reception of the RRCConnectionRelease by the UE

The UE shall:

1> except for NB-IoT, BL UEs or UEs in CE, delay the following actions defined in this sub-clause 60 ms from the
moment the RRCConnectionRelease message was received or optionally when lower layers indicate that the
receipt of the RRCConnectionRelease message has been successfully acknowledged, whichever is earlier;

1> for BL UEs or UEs in CE, delay the following actions defined in this sub-clause 1.25 seconds from the moment
the RRCConnectionRelease message was received or optionally when lower layers indicate that the receipt of the
RRCConnectionRelease message has been successfully acknowledged, whichever is earlier;

1> for NB-IoT, delay the following actions defined in this sub-clause 10 seconds from the moment the
RRCConnectionRelease message was received or optionally when lower layers indicate that the receipt of the
RRCConnectionRelease message has been successfully acknowledged, whichever is earlier.

NOTE: For BL UEs, UEs in CE and NB-IoT, when STATUS reporting, as defined in TS 36.322 [7], has not been
triggered and the UE has sent positive HARQ feedback (ACK), as defined in TS 36.321 [6], the lower
layers can be considered to have indicated that the receipt of the RRCConnectionRelease message has
been successfully acknowledged.

1> stop T380, if running;

1> if the RRCConnectionRelease message is received in response to an RRCConnectionResumeRequest for EDT:

2> indicate to upper layers that the suspended RRC connection has been resumed;

2> discard the stored UE AS context and resumeIdentity;

2> stop timer T300;

2> stop timer T302, if running;

2> stop timer T303, if running;

2> stop timer T305, if running;

2> stop timer T306, if running;

2> stop timer T308, if running;

2> perform the actions as specified in 5.3.3.7;

2> stop timer T320, if running;

2> stop timer T322, if running;

1> if the security is not activated and if UE is connected to 5GC:

2> perform the actions upon leaving RRC_CONNECTED or RRC_INACTIVE as specified in 5.3.12 with the
release cause 'other' upon which the procedure ends;

1> if the RRCConnectionRelease message includes redirectedCarrierInfo indicating redirection to geran; or

3GPP
Release 15 131 3GPP TS 36.331 V15.4.0 (2018-12)

1> if the RRCConnectionRelease message includes idleModeMobilityControlInfo including freqPriorityListGERAN:

2> if AS security has not been activated; and

2> if upper layers indicate that redirect to GERAN without AS security is not allowed:

3> ignore the content of the RRCConnectionRelease;

3> perform the actions upon leaving RRC_CONNECTED or RRC_INACTIVE as specified in 5.3.12, with
release cause 'other', upon which the procedure ends;

1> if AS security has not been activated:

2> ignore the content of redirectedCarrierInfo, if included and indicating redirection to nr;

2> ignore the content of idleModeMobilityControlInfo, if included and including freqPriorityListNR;

2> if the UE ignores the content of redirectedCarrierInfo or of idleModeMobilityControlInfo:

3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'other',
upon which the procedure ends;

1> if the RRCConnectionRelease message includes redirectedCarrierInfo indicating redirection to eutra and if UE
is connected to 5GC:

2> if cn-Type is included:

3> after the cell selection, indicate the available CN Type(s) and the received cn-Type to upper layers;

NOTE 1: Handling the case if the E-UTRA cell selected after the redirection does not support the core network type
specified by the cn-Type, is up to UE implementation.

1> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:

2> store the cell reselection priority information provided by the idleModeMobilityControlInfo;

2> if the t320 is included:

3> start timer T320, with the timer value set according to the value of t320;

1> else:

2> apply the cell reselection priority information broadcast in the system information;

1> if the RRCConnectionRelease message includes the measIdleConfig:

2> clear VarMeasIdleConfig and VarMeasIdleReport;

2> store the received measIdleDuration in VarMeasIdleConfig;

2> start T331 with the value of measIdleDuration;

2> if the measIdleConfig contains measIdleCarrierListEUTRA:

3> store the received measIdleCarrierListEUTRA in VarMeasIdleConfig;

2> else:

3> store the measIdleCarrierListEUTRA received in SIB5 in VarMeasIdleConfig;

2> start performing idle mode measurements as specified in 5.6.20;

1> for NB-IoT, if the RRCConnectionRelease message includes the redirectedCarrierInfo:

2> if the redirectedCarrierOffsetDedicated is included in the redirectedCarrierInfo:

3> store the dedicated offset for the frequency in redirectedCarrierInfo;

3GPP
Release 15 132 3GPP TS 36.331 V15.4.0 (2018-12)

3> start timer T322, with the timer value set according to the value of T322 in redirectedCarrierInfo;

1> if the releaseCause received in the RRCConnectionRelease message indicates loadBalancingTAURequired:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'load
balancing TAU required';

1> else if the releaseCause received in the RRCConnectionRelease message indicates cs-FallbackHighPriority:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'CS Fallback
High Priority';

1> else:

2> if the waitTime is present:

3> start timer T302, with the timer value set according to the waitTime;

3> inform the upper layer that access barring is applicable for all access categories except categories '0' and
'2';

2> if the extendedWaitTime is present; and

2> if the UE supports delay tolerant access or the UE is a NB-IoT UE:

3> forward the extendedWaitTime to upper layers;

2> if the extendedWaitTime-CPdata is present and the NB-IoT UE only supports the Control Plane CIoT EPS
optimisation:

3> forward the extendedWaitTime-CPdata to upper layers;

2> if the releaseCause received in the RRCConnectionRelease message indicates rrc-Suspend:

3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
suspension';

2> else if rrc-InactiveConfig is included:

3> perform the actions upon entering RRC_INACTIVE as specified in 5.3.8.7;

2> else:

3> perform the actions upon leaving RRC_CONNECTED or RRC_INACTIVE as specified in 5.3.12, with
release cause 'other';

5.3.8.4 T320 expiry

The UE shall:

1> if T320 expires:

2> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or
inherited from another RAT;

2> apply the cell reselection priority information broadcast in the system information;

5.3.8.5 T322 expiry

The UE shall:

1> if T322 expires:

2> discard the redirectedCarrierOffsetDedicated provided in RRCConnectionRelease message;

3GPP
Release 15 133 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.8.6 UE actions upon receiving the expiry of DataInactivityTimer

Upon receiving the expiry of DataInactivityTimer from lower layers while in RRC_CONNECTED, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'RRC
connection failure';

5.3.8.7 UE actions upon entering RRC_INACTIVE

Upon entering RRC_INACTIVE, the UE shall:

1> reset MAC and release the default MAC configuration if any;

1> stop all timers that are running except T320 and T325;

1> re-establish RLC entities for all SRBs and DRBs;

1> apply the received rrc-InactiveConfig;

1> if the RRCConnectionRelease message was received in response to an RRCConnectionResumeRequest:

2> in the stored UE Inactive AS context:

3> replace the KeNB and KRRCint keys with the current KeNB and KRRCint keys;

3> replace the C-RNTI with the temporary C-RNTI which the UE has used to receive the
RRCConnectionRelease message;

3> replace the cellIdentity with the cellIdentity of the PCell at the time the UE has received the
RRCConnectionRelease message;

3> replace the previously stored physical cell identity with the physical cell identity of the PCell at the time
the UE has received the RRCConnectionRelease message;

4> replace the rrc-InactiveConfig with the current rrc-InactiveConfig;

1> else:

2> in the UE Inactive AS Context, store the received rrc-InactiveConfig, all current parameters configured with
RRCConnectionReconfiguration or RRCConnectionResume, the current KeNB and KRRCint keys, the ROHC
state, the C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the source PCell;

1> if the periodic-RNAU-timer is included:

2> start timer T380, with the timer value set to the periodic-RNAU-timer;

1> suspend all SRB(s) and DRB(s), except SRB0;

1> indicate PDCP suspend to lower layers of all DRBs;

1> indicate the suspension of the RRC connection to upper layers;

1> enter RRC_INACTIVE and perform procedures as specified in TS 36.304 [4], clause 5.2.7;

Upon selecting to an inter-RAT cell or switching to another CN type, the UE shall:

1> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12, with release cause 'other';

5.3.9 RRC connection release requested by upper layers

5.3.9.1 General
The purpose of this procedure is to release the RRC connection. Access to the current PCell may be barred as a result of
this procedure.

3GPP
Release 15 134 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.9.2 Initiation
The UE initiates the procedure when upper layers request the release of the RRC connection as specified in TS 24. 301
[35] for E-UTRA/EPC and TS 24.501 [95] for E-UTRA/5GC. The UE shall not initiate the procedure for power saving
purposes.

The UE shall:

1> if the upper layers indicate barring of the PCell:

2> treat the PCell used prior to entering RRC_IDLE as barred according to TS 36.304 [4];

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'other';

5.3.10 Radio resource configuration

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;

3GPP
Release 15 135 3GPP TS 36.331 V15.4.0 (2018-12)

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 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;

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;

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 RLC bearer of this SRB with the established PDCP entity;

3> release the NR PDCP entity of this SRB;

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:

3GPP
Release 15 136 3GPP TS 36.331 V15.4.0 (2018-12)

1> for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration (DRB
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):

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 for EN-DC):

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 an MCG RLC entity or entities in accordance with the received rlc-
Config;

3GPP
Release 15 137 3GPP TS 36.331 V15.4.0 (2018-12)

3> if logicalChannelIdentity and logicalChannelConfig are received, establish an MCG DTCH logical
channel in accordance with the received logicalChannelIdentity and the received logicalChannelConfig;

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 in EN-DC
(reconfigure MCG RLC bearer for EN-DC 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, re-establish the RLC entity of this DRB;

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

4> if the logicalChannelConfig is included:

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

NOTE: Removal and addition of 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):

3GPP
Release 15 138 3GPP TS 36.331 V15.4.0 (2018-12)

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 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;

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 and the SCG DTCH logical channel;

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;

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 and the SCG DTCH logical channel to be an MCG RLC
entity or entities and an MCG DTCH logical channel;

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

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 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;

3GPP
Release 15 139 3GPP TS 36.331 V15.4.0 (2018-12)

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 MCG RLC entity and/ or the MCG DTCH logical channel in accordance with the rlc-
Config and logicalChannelConfig, if included in drb-ToAddModList;

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 and the MCG DTCH logical channel to be an SCG RLC
entity or entities and an SCG DTCH logical channel;

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

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;

3GPP
Release 15 140 3GPP TS 36.331 V15.4.0 (2018-12)

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;

3GPP
Release 15 141 3GPP TS 36.331 V15.4.0 (2018-12)

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:

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;

3GPP
Release 15 142 3GPP TS 36.331 V15.4.0 (2018-12)

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.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.

3GPP
Release 15 143 3GPP TS 36.331 V15.4.0 (2018-12)

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:

3GPP
Release 15 144 3GPP TS 36.331 V15.4.0 (2018-12)

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: 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:

3GPP
Release 15 145 3GPP TS 36.331 V15.4.0 (2018-12)

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: 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-HarwareSharingIndication 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:

3GPP
Release 15 146 3GPP TS 36.331 V15.4.0 (2018-12)

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.18;

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:

3GPP
Release 15 147 3GPP TS 36.331 V15.4.0 (2018-12)

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 SCG cell(s);

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

1> if the received scg-Configuration 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> for each drb-Identity value that is part of the current UE configuration:

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

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

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

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

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

4> 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):

5> 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 the received scg-Configuration 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 the received scg-ConfigPartMCG includes the scg-Counter:

3GPP
Release 15 148 3GPP TS 36.331 V15.4.0 (2018-12)

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 the received scg-ConfigPartSCG 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 the received scg-ConfigPartSCG includes the sCellToReleaseListSCG:

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

2> if the received scg-ConfigPartSCG 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 the received scg-ConfigPartSCG 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 the received scg-ConfigPartSCG 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;

3GPP
Release 15 149 3GPP TS 36.331 V15.4.0 (2018-12)

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 drb-ToAddModListSCG:

2> 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;

3GPP
Release 15 150 3GPP TS 36.331 V15.4.0 (2018-12)

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:

3GPP
Release 15 151 3GPP TS 36.331 V15.4.0 (2018-12)

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 for the SRB with SRB identity corresponding to srb-ToReleaseList:

3GPP
Release 15 152 3GPP TS 36.331 V15.4.0 (2018-12)

1> 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.11 Radio link failure related actions

5.3.11.1 Detection of physical layer problems in RRC_CONNECTED

The UE shall:

1> upon receiving N310 consecutive "out-of-sync" indications for the PCell from lower layers while neither T300,
T301, T304 nor T311 is running:

2> start timer T310;

1> upon receiving N313 consecutive "out-of-sync" indications for the PSCell from lower layers while T307 is not
running:

2> start T313;

NOTE: Physical layer monitoring and related autonomous actions do not apply to SCells except for the PSCell.

5.3.11.1a Early detection of physical layer problems in RRC_CONNECTED

The UE shall:

1> upon receiving N310 consecutive "early-out-of-sync" indications for the PCell from lower layers:

2> start timer T314 with the timer value set to the value of T310;

5.3.11.1b Detection of physical layer improvements in RRC_CONNECTED

The UE shall:

1> upon receiving N311 consecutive "early-in-sync" indications for the PCell from lower layers:

2> start timer T315 with the timer value set to the value of T310;

5.3.11.2 Recovery of physical layer problems

Upon receiving N311 consecutive "in-sync" indications for the PCell from lower layers while T310 is running, the UE
shall:

1> stop timer T310;

1> stop timer T312, if running;

NOTE 1: In this case, the UE maintains the RRC connection without explicit signalling, i.e. the UE maintains the
entire radio resource configuration.

NOTE 2: Periods in time where neither "in-sync" nor "out-of-sync" is reported by layer 1 do not affect the
evaluation of the number of consecutive "in-sync" or "out-of-sync" indications.

Upon receiving N314 consecutive "in-sync" indications for the PSCell from lower layers while T313 is running, the UE
shall:

3GPP
Release 15 153 3GPP TS 36.331 V15.4.0 (2018-12)

1> stop timer T313;

5.3.11.2a Recovery of early detection of physical layer problems

Upon receiving N311 consecutive "in-sync" indications for the PCell from lower layers while T314 is running, the UE
shall:

1> stop timer T314;

5.3.11.2b Cancellation of physical layer improvements in RRC_CONNECTED

Upon receiving N311 consecutive "in-sync" indications for the PCell from lower layers while T315 is running, the UE
shall:

1> stop timer T315;

5.3.11.3 Detection of radio link failure

The UE shall:

1> upon T310 expiry; or

1> upon T312 expiry; or

1> upon random access problem indication from MCG MAC while neither T300, T301, T304 nor T311 is running;
or

1> upon indication from MCG RLC, which is allowed to be send on PCell, that the maximum number of
retransmissions has been reached for an SRB or DRB:

2> consider radio link failure to be detected for the MCG i.e. RLF;

2> except for NB-IoT, store the following radio link failure information in the VarRLF-Report by setting its
fields as follows:

3> clear the information included in VarRLF-Report, if any;

3> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);

3> set the measResultLastServCell to include the RSRP and RSRQ, if available, of the PCell based on
measurements collected up to the moment the UE detected radio link failure;

3> set the measResultNeighCells to include the best measured cells, other than the PCell, ordered such that
the best cell is listed first, and based on measurements collected up to the moment the UE detected radio
link failure, and set its fields as follows;

4> if the UE was configured to perform measurements for one or more EUTRA frequencies, include the
measResultListEUTRA;

4> if the UE was configured to perform measurement reporting for one or more neighbouring UTRA
frequencies, include the measResultListUTRA;

4> if the UE was configured to perform measurement reporting for one or more neighbouring GERAN
frequencies, include the measResultListGERAN;

4> if the UE was configured to perform measurement reporting for one or more neighbouring
CDMA2000 frequencies, include the measResultsCDMA2000;

4> for each neighbour cell included, include the optional fields that are available;

NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement
configuration. The measurements are based on the time domain measurement resource restriction, if
configured. Blacklisted cells are not required to be reported.

3GPP
Release 15 154 3GPP TS 36.331 V15.4.0 (2018-12)

3> if available, set the logMeasResultListWLAN to include the WLAN measurement results, in order of
decreasing RSSI for WLAN APs;

3> if available, set the logMeasResultListBT to include the Bluetooth measurement results, in order of
decreasing RSSI for Bluetooth beacons;

3> if detailed location information is available, set the content of the locationInfo as follows:

4> include the locationCoordinates;

4> include the horizontalVelocity, if available;

3> set the failedPCellId to the global cell identity, if available, and otherwise to the physical cell identity and
carrier frequency of the PCell where radio link failure is detected;

3> set the tac-FailedPCell to the tracking area code, if available, of the PCell where radio link failure is
detected;

3> if an RRCConnectionReconfiguration message including the mobilityControlInfo was received before the
connection failure:

4> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned an

intra E-UTRA handover:

5> include the previousPCellId and set it to the global cell identity of the PCell where the last
RRCConnectionReconfiguration message including mobilityControlInfo was received;

5> set the timeConnFailure to the elapsed time since reception of the last
RRCConnectionReconfiguration message including the mobilityControlInfo;

4> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned a

handover to E-UTRA from UTRA and if the UE supports Radio Link Failure Report for Inter-RAT
MRO:

5> include the previousUTRA-CellId and set it to the physical cell identity, the carrier frequency and
the global cell identity, if available, of the UTRA Cell in which the last
RRCConnectionReconfiguration message including mobilityControlInfo was received;

5> set the timeConnFailure to the elapsed time since reception of the last
RRCConnectionReconfiguration message including the mobilityControlInfo;

3> if the UE supports QCI1 indication in Radio Link Failure Report and has a DRB for which QCI is 1:

4> include the drb-EstablishedWithQCI-1;

3> set the connectionFailureType to rlf;

3> set the c-RNTI to the C-RNTI used in the PCell;

3> set the rlf-Cause to the trigger for detecting radio link failure;

2> if AS security has not been activated:

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

4> if the UE supports RRC connection re-establishment for the Control Plane CIoT EPS optimisation:

5> initiate the RRC connection re-establishment procedure as specified in 5.3.7;

4> else:

5> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause
'RRC connection failure';

3> else:

3GPP
Release 15 155 3GPP TS 36.331 V15.4.0 (2018-12)

4> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause
'other';

2> else:

3> initiate the connection re-establishment procedure as specified in 5.3.7;

In case of DC, the UE shall:

1> upon T313 expiry; or

1> upon random access problem indication from SCG MAC; or

1> upon indication from SCG RLC, which is allowed to be sent on PSCell, that the maximum number of
retransmissions has been reached for an SCG or split DRB:

2> consider radio link failure to be detected for the SCG i.e. SCG-RLF;

2> initiate the SCG failure information procedure as specified in 5.6.13 to report SCG radio link failure;

In case of CA PDCP duplication, the UE shall:

1> upon indication from an RLC entity, which is restricted to be sent on SCell only, that the maximum number of
retransmissions has been reached:

2> initiate the failure information procedure as specified in 5.6.21 to report RLC failure of type duplication;

The UE may discard the radio link failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the
radio link failure is detected, upon power off or upon detach.

5.3.11.3a Detection of early-out-of-sync event

The UE shall:

1> upon T314 expiry;

2> consider "early-out-of-sync" event to be detected and initiate transmission of the UEAssistanceInformation
message in accordance with 5.6.10;

5.3.11.3b Detection of early-in-sync event

The UE shall:

1> upon T315 expiry;

2> consider "early-in-sync" event to be detected and initiate transmission of the UEAssistanceInformation
message in accordance with 5.6.10;

5.3.12 UE actions upon leaving RRC_CONNECTED or RRC_INACTIVE

Upon leaving RRC_CONNECTED or RRC_INACTIVE, the UE shall:

1> reset MAC;

1> if the UE is leaving RRC_INACTIVE:

2> stop the timer T320, if running;

2> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo;1> if
T302 is running and if the UE is connected to 5GC:

2> stop timer T302;

2> perform the actions as specified in 5.3.16.4;

3GPP
Release 15 156 3GPP TS 36.331 V15.4.0 (2018-12)

1> stop all timers that are running except T320, T322, T325, T330;

1> if leaving RRC_CONNECTED was triggered by suspension of the RRC:

2> re-establish RLC entities for all SRBs and DRBs, including RBs configured with NR PDCP;

2> store the UE AS Context including the current RRC configuration, the current security context, the PDCP
state including ROHC state, C-RNTI used in the source PCell, the cellIdentity and the physical cell identity
of the source PCell;

2> store the following information provided by E-UTRAN:

3> the resumeIdentity;

3> the nextHopChainingCount, if present. Otherwise discard any stored nextHopChainingCount that does
not correspond to stored key KRRCint;

3> the drb-ContinueROHC, if present. Otherwise discard any stored drb-ContinueROHC;

2> suspend all SRB(s) and DRB(s), including RBs configured with NR PDCP, except SRB0;

2> indicate the suspension of the RRC connection to upper layers;

2> configure lower layers to suspend integrity protection and ciphering;

NOTE 1: Except for UP-EDT, ciphering is not applied for the subsequent RRCConnectionResume message used to
resume the connection and an integrity check is performed by lower layers, but merely upon request from
RRC.

1> else:

2> upon leaving RRC_INACTIVE:

3> discard the UE Inactive AS context;

3> discard the KeNB, the KRRCenc key, the KRRCint and the KUPenc key;

2> release all radio resources, including release of the MAC configuration, the RLC entity and the associated
PDCP entity and SDAP (if any) for all established RBs;

2> indicate the release of the RRC connection to upper layers together with the release cause;

1> if leaving RRC_CONNECTED was triggered neither by reception of the MobilityFromEUTRACommand

message nor by selecting an inter-RAT cell while T311 was running:

2> if timer T350 is configured:

3> start timer T350;

3> apply rclwi-Configuration if configured, otherwise apply the wlan-Id-List corresponding to the RPLMN
included in SystemInformationBlockType17;

2> else:

3> release the wlan-OffloadConfigDedicated, if received;

3> if the wlan-OffloadConfigCommon corresponding to the RPLMN is broadcast by the cell:

4> apply the wlan-OffloadConfigCommon corresponding to the RPLMN included in

SystemInformationBlockType17;

4> apply steerToWLAN if configured, otherwise apply the wlan-Id-List corresponding to the RPLMN
included in SystemInformationBlockType17;

2> enter RRC_IDLE and perform procedures as specified in TS 36.304 [4], clause 5.2.7;

1> else:

3GPP
Release 15 157 3GPP TS 36.331 V15.4.0 (2018-12)

2> release the wlan-OffloadConfigDedicated, if received;

NOTE 2: BL UEs or UEs in CE verifies validity of SI when released to RRC_IDLE.

1> release the LWA configuration, if configured, as described in 5.6.14.3;

1> release the LWIP configuration, if configured, as described in 5.6.17.3;

5.3.13 UE actions upon PUCCH/ SPUCCH/ SRS release request

Upon receiving a PUCCH release request from lower layers, for an indicated serving cell the UE shall:

1> apply the default physical channel configuration for cqi-ReportConfig for the indicated serving cell as specified
in 9.2.4 and release cqi-ReportConfigSCell, for each SCell that sends HARQ feedback on the indicated serving
cell, if any;

1> apply the default physical channel configuration for schedulingRequestConfig as specified in 9.2.4, for the
concerned CG;

Upon receiving a sPUCCH release request from lower layers, the UE shall:

1> for each serving cell in the UE configuration:

2> apply the value release to the field schedulingRequest-SPUCCH;

Upon receiving an SRS release request from lower layers, for an indicated serving cell the UE shall:

1> apply the default physical channel configuration for soundingRS-UL-ConfigDedicated, as specified in 9.2.4;

NOTE: Upon PUCCH/ SRS release request, the UE does not modify the soundingRS-UL-
ConfigDedicatedAperiodic i.e. it does not apply the default for this field (release).

5.3.13a UE actions upon SR release request for NB-IoT

Upon receiving a SR release request from lower layers, the UE shall:

1> apply the value FALSE for sr-WithHARQ-ACK-Config and release sr-WithHARQ-ACK-Config, if configured;

1> apply the value release for sr-WithoutHARQ-ACK-Config and release sr-WithoutHARQ-ACK-Config, if
configured;

1> apply the value release for sr-SPS-BSR-Config and release sr-SPS-BSR-Config, if configured;

5.3.14 Proximity indication

5.3.14.1 General

UE EUTRAN

RRC connection reconfiguration

ProximityIndication

Figure 5.3.14.1-1: Proximity indication

The purpose of this procedure is to indicate that the UE is entering or leaving the proximity of one or more CSG
member cells. The detection of proximity is based on an autonomous search function as defined in TS 36.304 [4].

3GPP
Release 15 158 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.14.2 Initiation
A UE in RRC_CONNECTED shall:

1> if the UE enters the proximity of one or more CSG member cell(s) on an E-UTRA frequency while proximity
indication is enabled for such E-UTRA cells; or

1> if the UE enters the proximity of one or more CSG member cell(s) on an UTRA frequency while proximity
indication is enabled for such UTRA cells; or

1> if the UE leaves the proximity of all CSG member cell(s) on an E-UTRA frequency while proximity indication is
enabled for such E-UTRA cells; or

1> if the UE leaves the proximity of all CSG member cell(s) on an UTRA frequency while proximity indication is
enabled for such UTRA cells:

2> if the UE has previously not transmitted a ProximityIndication for the RAT and frequency during the current
RRC connection, or if more than 5 s has elapsed since the UE has last transmitted a ProximityIndication
(either entering or leaving) for the RAT and frequency:

3> initiate transmission of the ProximityIndication message in accordance with 5.3.14.3;

NOTE: In the conditions above, "if the UE enters the proximity of one or more CSG member cell(s)" includes the
case of already being in the proximity of such cell(s) at the time proximity indication for the
corresponding RAT is enabled.

5.3.14.3 Actions related to transmission of ProximityIndication message

The UE shall set the contents of ProximityIndication message as follows:

1> if the UE applies the procedure to report entering the proximity of CSG member cell(s):

2> set type to entering;

1> else if the UE applies the procedure to report leaving the proximity of CSG member cell(s):

2> set type to leaving;

1> if the proximity indication was triggered for one or more CSG member cell(s) on an E-UTRA frequency:

2> set the carrierFreq to eutra with the value set to the E-ARFCN value of the E-UTRA cell(s) for which
proximity indication was triggered;

1> else if the proximity indication was triggered for one or more CSG member cell(s) on a UTRA frequency:

2> set the carrierFreq to utra with the value set to the ARFCN value of the UTRA cell(s) for which proximity
indication was triggered;

The UE shall submit the ProximityIndication message to lower layers for transmission.

5.3.15 Void

5.3.16 Unified Access Control

5.3.16.1 General
The purpose of this procedure is to perform access barring check for an access attempt associated with a given Access
Category and one or more Access Identities upon request from upper layers according to TS 24.501 [95] or the RRC
layer.

After a handover resulting in change of PCell in RRC_CONNECTED the UE shall defer access barring checks until it
has obtained valid UAC information (from SIB25) from the target cell.

3GPP
Release 15 159 3GPP TS 36.331 V15.4.0 (2018-12)

5.3.16.2 Initiation
Upon initiation of the procedure, the UE shall:

1> if T309 is running for the Access Category:

2> consider the access attempt as barred;

1> if timer T302 is running and the Access Category is neither '2' nor '0':

2> consider the access attempt as barred;

1> else:

2> if the Access Category is '0':

3> consider the access attempt as allowed;

2> else if SystemInformationBlockType25 is not broadcasted:

3> consider the access attempt as allowed;

2> else:

3> if SystemInformationBlockType25 includes uac-BarringPerPLMN-List and the uac-BarringPerPLMN-

List contains an UAC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN
selected by upper layers (see TS 24.501 [95]):

4> select the UAC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN
selected by upper layers;

4> in the remainder of this procedure, use the selected UAC-BarringPerPLMN entry (i.e. presence or
absence of access barring parameters in this entry) irrespective of the uac-BarringForCommon
included in SystemInformationBlockType25;

3> else if SystemInformationBlockType25 includes uac-BarringForCommon:

4> in the remainder of this procedure use the uac-BarringForCommon (i.e. presence or absence of these
parameters) included in SystemInformationBlockType25;

3> else:

4> consider the access attempt as allowed;

3> if uac-BarringForCommon is applicable or the uac-AC-BarringListType indicated that uac-ExplicitAC-

BarringList is used:

4> if the corresponding UAC-BarringPerCatList contains a UAC-BarringPerCat entry corresponding to

the Access Category:

5> select the UAC-BarringPerCat entry;

5> if the uac-BarringInfoSetList contain a UAC-BarringInfoSet entry corresponding to the uac-

barringInfoSetIndex in the UAC-BarringPerCat:

6> select the UAC-BarringInfoSet entry;

6> perform access barring check for the Access Category as specified in 5.3.16.5, using the UAC-
BarringInfoSet as "UAC barring parameter";

5> else:

6> consider the access attempt as allowed;

4> else:

5> consider the access attempt as allowed;

3GPP
Release 15 160 3GPP TS 36.331 V15.4.0 (2018-12)

3> else if the uac-AC-BarringListType indicated that uac-ImplicitAC-BarringList is indicated:

4> select the uac-BarringInfoSetIndex corresponding to the Access Category in the uac-
ImplicitACBarringList;

4> if the uac-BarringInfoSetList contain the UAC-BarringInfoSet entry corresponding to the selected
uac-BarringInfoSetIndex:

5> select the UAC-BarringInfoSet entry;

5> perform access barring check for the Access Category as specified in 5.3.16.5, using the UAC-
BarringInfoSet as "UAC barring parameter";

4> else:

5> consider the access attempt as allowed;

3> else:

4> consider the access attempt as allowed;

1> if the access barring check was requested by upper layers:

2> if the access attempt is considered as barred:

3> if timer T302 is running:

4> inform the upper layer that access barring is applicable for all access categories except categories '0'
and '2', upon which the procedure ends;

3> else:

4> inform upper layers that the access attempt for the Access Category is barred, upon which the
procedure ends;

2> else:

3> inform upper layers that the access attempt for the Access Category is allowed, upon which the procedure
ends;

1> else:

2> the procedure ends;

5.3.16.3 Void

5.3.16.4 T302, T309 expiry or stop (Barring alleviation)

The UE shall:

1> if timer T302 expires or is stopped, and if timer T309 corresponding to an Access Category is not running; or

1> if timer T309 corresponding to an Access Category other than '2' expires or is stopped, and if timer T302 is not
running; or

1> if timer T309 corresponding to the Access Category '2' expires or is stopped:

2> consider the barring for this Access Category to be alleviated;

1> When barring for an access category is considered being alleviated:

2> if the Access Category was informed to upper layers as barred:

3> inform upper layers about barring alleviation for the Access Category;

2> if barring is alleviated for Access Category '8':

3GPP
Release 15 161 3GPP TS 36.331 V15.4.0 (2018-12)

3> perform actions specified in 5.3.17;

5.3.16.5 Access barring check

The UE shall:

1> if one or more Access Identities are indicated according to TS 24.501 [95], and

1> if for at least one of these Access Identities the corresponding bit in the uac-BarringForAccessIdentity contained
in "UAC barring parameter" is set to zero:

2> consider the access attempt as allowed;

1> else:

2> draw a random number 'rand' uniformly distributed in the range: 0 ≤ rand < 1;

2> if 'rand' is lower than the value indicated by uac-BarringFactor included in "UAC barring parameter":

3> consider the access attempt as allowed;

2> else:

3> consider the access attempt as barred;

1> if the access attempt is considered as barred:

2> draw a random number 'rand' that is uniformly distributed in the range 0 ≤ rand < 1;

2> start timer T309 for the Access Category with the timer value calculated as follows, using the uac-
BarringTime included in "AC barring parameter":

"Tbarring" = (0.7+ 0.6 * rand) * uac-BarringTime;

5.3.17 RAN notification area update

5.3.17.1 General
The purpose of this procedure is:

- to notify the network that a UE in RRC_INACTIVE has re-selected to a cell not belonging to the configured
RAN notification area; or

- to periodically notify the network by a UE in RRC_INACTIVE;

5.3.17.2 Initiation
When in RRC_INACTIVE state, the UE shall:

1> if T380 expires, or:

1> if RNA Update is triggered at reception of SystemInformationBlockType1, as specified in 5.2.2.7:

2> initiate RRC connection resume procedure in 5.3.3 with cause value set to 'rna-Update';

1> if barring is alleviated for Access Category '8', as specified in 5.3.16.4:

2> if upper layers do not request RRC the resumption of an RRC connection, and

2> if the variable pendingRnaUpdate is set to 'TRUE':

3> initiate RRC connection resume procedure in 5.3.3 with cause value set to 'rna-Update';

If the UE in RRC_INACTIVE state fails to find a suitable cell and camps on the acceptable cell to obtain limited
service as defined in TS 36.304 [4], the UE shall:

3GPP
Release 15 162 3GPP TS 36.331 V15.4.0 (2018-12)

1> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12 with release cause 'other'.

5.3.17.3 Inter RAT cell reselection or CN type change

Upon reselecting to an inter-RAT cell or to another CN type, the UE shall:

1> perform the actions upon leaving RRC_INACTIVE as specified in 5.3.12, with release cause 'other'.

5.4 Inter-RAT mobility

5.4.1 Introduction
The general principles of connected mode mobility are described in 5.3.1.3. The general principles of the security
handling upon connected mode mobility are described in 5.3.1.2.

For the (network controlled) inter RAT mobility from E-UTRA for a UE in RRC_CONNECTED, a single procedure is
defined that supports both handover, cell change order with optional network assistance (NACC) and enhanced CS
fallback to CDMA2000 1xRTT. In case of mobility to CDMA2000, the eNB decides when to move to the other RAT
while the target RAT determines to which cell the UE shall move.

5.4.2 Handover to E-UTRA

5.4.2.1 General

UE EUTRAN

RRCConnectionReconfiguration
(sent via other RAT)

RRCConnectionReconfigurationComplete

Figure 5.4.2.1-1: Handover to E-UTRA, successful

The purpose of this procedure is to, under the control of the network, transfer a connection between the UE and another
Radio Access Network (e.g. GERAN, UTRAN or NR) to E-UTRAN, or transfer a connection between the UE and the
E-UTRAN with one type of CN to the E-UTRAN with a different type of CN.

The handover to E-UTRA procedure applies when SRBs, possibly in combination with DRBs, are established in
another RAT or in E-UTRA connected to another type of CN. Handover from UTRAN to E-UTRAN applies only after
integrity has been activated in UTRAN. Handover to E-UTRA connected to a different type of CN applies only after
integrity has been activated in E-UTRAN. Handover from NR to E-UTRAN applies only after integrity has been
activated in NR.

5.4.2.2 Initiation
The RAN using another RAT or the E-UTRA connected to a different type of CN initiates the handover to E-UTRA
procedure, in accordance with the specifications applicable for the other RAT or for the E-UTRA connected to a
different type of CN, by sending the RRCConnectionReconfiguration message via the radio access technology from
which the inter-RAT handover is performed.

E-UTRAN applies the procedure as follows:

- to activate ciphering, possibly using NULL algorithm, if not yet activated in the other RAT or in the E-UTRA
connected to a different type of CN;

3GPP
Release 15 163 3GPP TS 36.331 V15.4.0 (2018-12)

- to establish SRB1, SRB2 and one or more DRBs, i.e. at least the DRB associated with the default EPS bearer is
established if the target CN is EPC and at least one DRB is established if the target CN is 5GC.

5.4.2.3 Reception of the RRCConnectionReconfiguration by the UE

If the UE is able to comply with the configuration included in the RRCConnectionReconfiguration message, the UE
shall:

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in 5.3.5.8;

Editor's note: It is FFS on how to handle the MCG/MN security configuration since the UE will have MCG security
configuration and for 5GC, UE will have a security configuration associated with master key.

1> else:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity
indicated by the targetPhysCellId;

1> start synchronising to the DL of the target PCell;

1> set the C-RNTI to the value of the newUE-Identity;

1> for the target PCell, apply the downlink bandwidth indicated by the dl-Bandwidth;

1> for the target PCell, apply the uplink bandwidth indicated by (the absence or presence of) the ul-Bandwidth;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the
received mobilityControlInfo;

1> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the handoverType in securityConfigHO is set to fivegc-ToEPC:

2> indicate to higher layer that the CN has changed from 5GC to EPC;

2> derive the key KeNB based on the mapped KASME key as specified for interworking between EPS and 5GS in
TS 33.501 [86];

2> store the nextHopChainingCount-r15 value;

1> else if the handoverType in securityConfigHO is set to intra5GC:

2> if the keyChangeIndicator-r15 received in the securityConfigHO is set to TRUE:

3> forward nas-Container to the upper layers, if included;

3> update the KeNB key based on the KAMF key, as specified in TS 33.501 [86];

2> else:

3> update the KeNB key based on the current KgNB or the NH, using the nextHopChainingCount-r15 value
indicated in the SecurityConfigHO, as specified in TS 33.501 [86];

2> store the nextHopChainingCount-r15 value;

3GPP
Release 15 164 3GPP TS 36.331 V15.4.0 (2018-12)

1> else if the handoverType in securityConfigHO is set to epc-To5GC:

2> forward the nas-Container to the upper layers

2> derive the KeNB key, as specified in TS 33.501 [86];

1> else:

2> forward the nas-SecurityParamToEUTRA to the upper layers;

2> derive the KeNB key, as specified in TS 33.401 [32];

1> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

Editor's note: It is FFS whether setup of EN-DC or MR-DC can be performed upon inter-RAT (inter-system or
intra-system) HO from NR, or for inter-system intra-LTE HO.

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig1:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2:

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6.

1> if the handoverType in securityConfigHO is set to fivegc-ToEPC or if the handoverType-v1530 is not present:

2> configure lower layers to apply the indicated integrity protection algorithm and the KRRCint key immediately,
i.e. the indicated integrity protection configuration shall be applied to all subsequent messages received and
sent by the UE, including the message used to indicate the successful completion of the procedure;

2> configure lower layers to apply the indicated ciphering algorithm, the KRRCenc key and the KUPenc key
immediately, i.e. the indicated ciphering configuration shall be applied to all subsequent messages received
and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition as specified in 5.3.10.3b;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> if the RRCConnectionReconfiguration message includes the otherConfig:

2> perform the other configuration procedure as specified in 5.3.10.9;

1> if the RRCConnectionReconfiguration message includes wlan-OffloadInfo:

2> perform the dedicated WLAN offload configuration procedure as specified in 5.6.12.2;

1> if the RRCConnectionReconfiguration message includes rclwi-Configuration:

2> perform the WLAN traffic steering command procedure as specified in 5.6.16.2;

1> if the RRCConnectionReconfiguration message includes lwa-Configuration:

2> perform the LWA configuration procedure as specified in 5.6.14.2;

1> if the RRCConnectionReconfiguration message includes lwip-Configuration:

2> perform the LWIP reconfiguration procedure as specified in 5.6.17.2;

1> set the content of RRCConnectionReconfigurationComplete message as follows:

3GPP
Release 15 165 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the
RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

3> include rlf-InfoAvailable;

2> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport and if T330 is not running:

3> include logMeasAvailableMBSFN;

2> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport:

3> include the logMeasAvailable;

2> if the UE has Bluetooth logged measurements available and if the RPLMN is included in plmn-IdentityList
stored in VarLogMeasReport:

3> include the logMeasAvailableBT;

2> if the UE has WLAN logged measurements available and if the RPLMN is included in plmn-IdentityList
stored in VarLogMeasReport:

3> include the logMeasAvailableWLAN;

2> if the UE has connection establishment failure information available in VarConnEstFailReport and if the
RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

3> include connEstFailInfoAvailable;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new
configuration;

1> if the RRCConnectionReconfiguration message does not include rlf-TimersAndConstants set to setup:

2> use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> 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 PCell, if any;

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

NOTE 1: 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.

2> enter E-UTRA RRC_CONNECTED, upon which the procedure ends;

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

NOTE 3: If the handover is from NR and target CN is 5GC, the delta configuration on PDCP and SDAP can be
used for intra-system inter-RAT handover.

5.4.2.4 Reconfiguration failure

The UE shall:

1> if the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration
message:

3GPP
Release 15 166 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the source RAT is E-UTRA:

3> perform the actions as specified in 5.3.5.5;

2> else:

3> perform the actions defined for this failure case as defined in the specifications applicable for the other
RAT;

NOTE 1: The UE may apply above failure handling also in case the RRCConnectionReconfiguration message
causes a protocol error for which the generic error handling as defined in 5.7 specifies that the UE shall
ignore the message.

NOTE 2: If the UE is unable to comply with part of the configuration, it does not apply any part of the
configuration, i.e. there is no partial success/ failure.

5.4.2.5 T304 expiry (handover to E-UTRA failure)

The UE shall:

1> upon T304 expiry (handover to E-UTRA failure):

2> if the source RAT is E-UTRA:

3> perform the actions as specified in 5.3.5.6;

2> else:

3> reset MAC;

3> perform the actions defined for this failure case as defined in the specifications applicable for the other
RAT;

5.4.3 Mobility from E-UTRA

5.4.3.1 General

UE EUTRAN

MobilityFromEUTRACommand

Figure 5.4.3.1-1: Mobility from E-UTRA, successful

UE EUTRAN

MobilityFromEUTRACommand

RRC connection re-establishment

Figure 5.4.3.1-2: Mobility from E-UTRA, failure

3GPP
Release 15 167 3GPP TS 36.331 V15.4.0 (2018-12)

The purpose of this procedure is to move a UE in RRC_CONNECTED to a cell using another Radio Access
Technology (RAT), e.g. GERAN, UTRA, CDMA2000 systems, NR, or handover a UE to an E-UTRA cell connected to
another type of CN. The mobility from E-UTRA procedure covers the following type of mobility:

- handover, i.e. the MobilityFromEUTRACommand message includes radio resources that have been allocated for
the UE in the target cell;

- cell change order, i.e. the MobilityFromEUTRACommand message may include information facilitating access
of and/ or connection establishment in the target cell, e.g. system information. Cell change order is applicable
only to GERAN; and

- enhanced CS fallback to CDMA2000 1xRTT, i.e. the MobilityFromEUTRACommand message includes radio
resources that have been allocated for the UE in the target cell. The enhanced CS fallback to CDMA2000 1xRTT
may be combined with concurrent handover or redirection to CDMA2000 HRPD.

NOTE: For the case of dual receiver/transmitter enhanced CS fallback to CDMA2000 1xRTT, the
DLInformationTransfer message is used instead of the MobilityFromEUTRACommand message (see TS
36.300 [9]).

5.4.3.2 Initiation
E-UTRAN initiates the mobility from E-UTRA procedure to a UE in RRC_CONNECTED, possibly in response to a
MeasurementReport message or in response to reception of CS fallback indication for the UE from MME, by sending a
MobilityFromEUTRACommand message. E-UTRAN applies the procedure as follows:

- the procedure is initiated only when AS-security has been activated, and SRB2 with at least one DRB are setup
and not suspended;

5.4.3.3 Reception of the MobilityFromEUTRACommand by the UE

The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN,
even if no prior UE measurements have been performed on the target cell.

The UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;
1> stop timer T309, if running, for all access categories;
1> if the MobilityFromEUTRACommand message includes the purpose set to handover:

2> if the targetRAT-Type is set to utra or geran:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in
the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the
target RAT;

3> if the targetRAT-Type is set to geran:

4> use the contents of systemInformation, if provided for PS Handover, as the system information to
begin access on the target GERAN cell;

NOTE 1: If there are DRBs for which no radio bearers are established in the target RAT as indicated in the
targetRAT-MessageContainer in the message, the E-UTRA RRC part of the UE does not indicate the
release of the concerned DRBs to the upper layers. Upper layers may derive which bearers are not
established from information received from the AS of the target RAT.

NOTE 2: In case of SR-VCC, the DRB to be replaced is specified in TS 23.216 [61].

2> else if the targetRAT-Type is set to eutra:

3GPP
Release 15 168 3GPP TS 36.331 V15.4.0 (2018-12)

3> consider inter-system mobility as initiated towards E-UTRA;

3> forward the nas-SecurityParamFromEUTRA to the upper layers, if included;

3> access the target cell indicated in the inter-RAT message in accordance with section 5.4.2.3;

2> else if the targetRAT-Type is set to nr:

3> consider inter-RAT mobility as initiated towards NR;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications in TS
38.331 [82];

2> else if the targetRAT-Type is set to cdma2000-1XRTT or cdma2000-HRPD:

3> forward the targetRAT-Type and the targetRAT-MessageContainer to the CDMA2000 upper layers for
the UE to access the cell(s) indicated in the inter-RAT message in accordance with the specifications of
the CDMA2000 target-RAT;

1> else if the MobilityFromEUTRACommand message includes the purpose set to cellChangeOrder:

2> start timer T304 with the timer value set to t304, as included in the MobilityFromEUTRACommand message;

2> if the targetRAT-Type is set to geran:

3> if networkControlOrder is included in the MobilityFromEUTRACommand message:

4> apply the value as specified in TS 44.060 [36];

3> else:

4> acquire networkControlOrder and apply the value as specified in TS 44.060 [36];

3> use the contents of systemInformation, if provided, as the system information to begin access on the target
GERAN cell;

2> establish the connection to the target cell indicated in the CellChangeOrder;

NOTE 3: The criteria for success or failure of the cell change order to GERAN are specified in TS 44.060 [36].

1> if the MobilityFromEUTRACommand message includes the purpose set to e-CSFB:

2> if messageContCDMA2000-1XRTT is present:

3> forward the messageContCDMA2000-1XRTT to the CDMA2000 upper layers for the UE to access the
cell(s) indicated in the inter-RAT message in accordance with the specification of the target RAT;

2> if mobilityCDMA2000-HRPD is present and is set to handover:

3> forward the messageContCDMA2000-HRPD to the CDMA2000 upper layers for the UE to access the
cell(s) indicated in the inter-RAT message in accordance with the specification of the target RAT;

2> if mobilityCDMA2000-HRPD is present and is set to redirection:

3> forward the redirectCarrierCDMA2000-HRPD to the CDMA2000 upper layers;

NOTE 4: When the CDMA2000 upper layers in the UE receive both the messageContCDMA2000-1XRTT and
messageContCDMA2000-HRPD the UE performs concurrent access to both CDMA2000 1xRTT and
CDMA2000 HRPD RAT.

NOTE 5: The UE should perform the handover, the cell change order or enhanced 1xRTT CS fallback as soon as
possible following the reception of the RRC message MobilityFromEUTRACommand, which could be
before confirming successful reception (HARQ and ARQ) of this message.

5.4.3.4 Successful completion of the mobility from E-UTRA

Upon successfully completing the handover, the cell change order or enhanced 1xRTT CS fallback, the UE shall:

3GPP
Release 15 169 3GPP TS 36.331 V15.4.0 (2018-12)

1> if the targetRAT-Type in the received MobilityFromEUTRACommand is set to eutra (intra-EUTRA inter-system
HO):

2> the procedure ends;

1> else if the UE is connected to 5GC and the targetRAT-Type in the received MobilityFromEUTRACommand is set
to nr:

2> reset MAC;

2> stop all timers that are running;

2> release ran-NotificationAreaInfo, if stored;

2> release the AS security context including the KRRCenc key, the KRRCint, the KUPint key and the KUPenc key, if
stored;

2> release all radio resources, including release of the RLC entity and the MAC configuration;

2> if delta configuration is used:

3> maintain source RAT configuration of PDCP and SDAP for applicable RBs which is used for target RAT
RBs;

2> else:

3> release the associated PDCP entity and SDAP entity for all established RBs;2> indicate the release of the
RRC connection to upper layers together with the release cause 'other'.

1> else:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause 'other';

NOTE: If the UE performs enhanced 1xRTT CS fallback along with concurrent mobility to CDMA2000 HRPD
and the connection to either CDMA2000 1xRTT or CDMA2000 HRPD succeeds, then the mobility from
E-UTRA is considered successful.

5.4.3.5 Mobility from E-UTRA failure

The UE shall:

1> if T304 configured in the MobilityFromEUTRACommand message expires (mobility from E-UTRA failure); or

1> if the UE does not succeed in establishing the connection to the target radio access technology; or

1> if the UE is unable to comply with (part of) the configuration included in the MobilityFromEUTRACommand
message; or

1> if there is a protocol error in the inter RAT information included in the MobilityFromEUTRACommand message,
causing the UE to fail the procedure according to the specifications applicable for the target RAT (i.e. according
to sub-clause 5.3.5.6 if the targetRAT-Type in the received MobilityFromEUTRACommand is set to eutra):

2> stop T304, if running;

2> if the cs-FallbackIndicator in the MobilityFromEUTRACommand message was set to TRUE or e-CSFB was
present:

3> indicate to upper layers that the CS fallback procedure has failed;

2> revert back to the configuration used in the source PCell, excluding the configuration configured by the
physicalConfigDedicated, mac-MainConfig and sps-Config;

2> initiate the connection re-establishment procedure as specified in 5.3.7;

3GPP
Release 15 170 3GPP TS 36.331 V15.4.0 (2018-12)

NOTE: For enhanced CS fallback to CDMA2000 1xRTT, the above UE behavior applies only when the UE is
attempting the enhanced 1xRTT CS fallback and connection to the target radio access technology fails or
if the UE is attempting enhanced 1xRTT CS fallback along with concurrent mobility to CDMA2000
HRPD and connection to both the target radio access technologies fails.

5.4.4 Handover from E-UTRA preparation request (CDMA2000)

5.4.4.1 General

UE EUTRAN

HandoverFromEUTRAPreparationRequest

Figure 5.4.4.1-1: Handover from E-UTRA preparation request

The purpose of this procedure is to trigger the UE to prepare for handover or enhanced 1xRTT CS fallback to
CDMA2000 by requesting a connection with this network. The UE may use this procedure to concurrently prepare for
handover to CDMA2000 HRPD along with preparation for enhanced CS fallback to CDMA2000 1xRTT. This
procedure applies to CDMA2000 capable UEs only.

This procedure is also used to trigger the UE which supports dual Rx/Tx enhanced 1xCSFB to redirect its second radio
to CDMA2000 1xRTT.

The handover from E-UTRA preparation request procedure applies when signalling radio bearers are established.

5.4.4.2 Initiation
E-UTRAN initiates the handover from E-UTRA preparation request procedure to a UE in RRC_CONNECTED,
possibly in response to a MeasurementReport message or CS fallback indication for the UE, by sending a
HandoverFromEUTRAPreparationRequest message. E-UTRA initiates the procedure only when AS security has been
activated.

5.4.4.3 Reception of the HandoverFromEUTRAPreparationRequest by the UE

Upon reception of the HandoverFromEUTRAPreparationRequest message, the UE shall:

1> if dualRxTxRedirectIndicator is present in the received message:

2> forward dualRxTxRedirectIndicator to the CDMA2000 upper layers;

2> forward redirectCarrierCDMA2000-1XRTT to the CDMA2000 upper layers, if included;

1> else:

2> indicate the request to prepare handover or enhanced 1xRTT CS fallback and forward the cdma2000-Type to
the CDMA2000 upper layers;

2> if cdma2000-Type is set to type1XRTT:

3> forward the rand and the mobilityParameters to the CDMA2000 upper layers;

2> if concurrPrepCDMA2000-HRPD is present in the received message:

3> forward concurrPrepCDMA2000-HRPD to the CDMA2000 upper layers;

2> else:

3> forward concurrPrepCDMA2000-HRPD, with its value set to FALSE, to the CDMA2000 upper layers;

3GPP
Release 15 171 3GPP TS 36.331 V15.4.0 (2018-12)

5.4.5 UL handover preparation transfer (CDMA2000)

5.4.5.1 General

UE EUTRAN

ULHandoverPreparationTransfer

Figure 5.4.5.1-1: UL handover preparation transfer

The purpose of this procedure is to tunnel the handover related CDMA2000 dedicated information or enhanced 1xRTT
CS fallback related CDMA2000 dedicated information from UE to E-UTRAN when requested by the higher layers. The
procedure is triggered by the higher layers on receipt of HandoverFromEUTRAPreparationRequest message. If
preparing for enhanced CS fallback to CDMA2000 1xRTT and handover to CDMA2000 HRPD, the UE sends two
consecutive ULHandoverPreparationTransfer messages to E-UTRAN, one per addressed CDMA2000 RAT Type. This
procedure applies to CDMA2000 capable UEs only.

5.4.5.2 Initiation
A UE in RRC_CONNECTED initiates the UL handover preparation transfer procedure whenever there is a need to
transfer handover or enhanced 1xRTT CS fallback related non-3GPP dedicated information. The UE initiates the UL
handover preparation transfer procedure by sending the ULHandoverPreparationTransfer message.

5.4.5.3 Actions related to transmission of the ULHandoverPreparationTransfer

message
The UE shall set the contents of the ULHandoverPreparationTransfer message as follows:

1> include the cdma2000-Type and the dedicatedInfo;

1> if the cdma2000-Type is set to type1XRTT:

2> include the meid and set it to the value received from the CDMA2000 upper layers;

1> submit the ULHandoverPreparationTransfer message to lower layers for transmission, upon which the
procedure ends;

5.4.5.4 Failure to deliver the ULHandoverPreparationTransfer message

The UE shall:

1> if the UE is unable to guarantee successful delivery of ULHandoverPreparationTransfer messages:

2> inform upper layers about the possible failure to deliver the information contained in the concerned
ULHandoverPreparationTransfer message;

5.4.6 Inter-RAT cell change order to E-UTRAN

5.4.6.1 General
The purpose of the inter-RAT cell change order to E-UTRAN procedure is to transfer, under the control of the source
radio access technology, a connection between the UE and another radio access technology (e.g. GSM/ GPRS) to E-
UTRAN.

3GPP
Release 15 172 3GPP TS 36.331 V15.4.0 (2018-12)

5.4.6.2 Initiation
The procedure is initiated when a radio access technology other than E-UTRAN, e.g. GSM/GPRS, using procedures
specific for that RAT, orders the UE to change to an E-UTRAN cell. In response, upper layers request the establishment
of an RRC connection as specified in subclause 5.3.3.

NOTE: Within the message used to order the UE to change to an E-UTRAN cell, the source RAT should specify
the identity of the target E-UTRAN cell as specified in the specifications for that RAT.

The UE shall:

1> upon receiving an RRCConnectionSetup message:

2> consider the inter-RAT cell change order procedure to have completed successfully;

5.4.6.3 UE fails to complete an inter-RAT cell change order

If the inter-RAT cell change order fails the UE shall return to the other radio access technology and proceed as specified
in the appropriate specifications for that RAT.

The UE shall:

1> upon failure to establish the RRC connection as specified in subclause 5.3.3:

2> consider the inter-RAT cell change order procedure to have failed;

NOTE: The cell change was network ordered. Therefore, failure to change to the target PCell should not cause the
UE to move to UE-controlled cell selection.

5.5 Measurements
5.5.1 Introduction
The UE reports measurement information in accordance with the measurement configuration as provided by E-
UTRAN. E-UTRAN provides the measurement configuration applicable for a UE in RRC_CONNECTED by means of
dedicated signalling, i.e. using the RRCConnectionReconfiguration or RRCConnectionResume message.

The UE can be requested to perform the following types of measurements:

- Intra-frequency measurements: measurements at the downlink carrier frequency(ies) of the serving cell(s).

- Inter-frequency measurements: measurements at frequencies that differ from any of the downlink carrier
frequency(ies) of the serving cell(s).

- Inter-RAT measurements of NR frequencies.

- Inter-RAT measurements of UTRA frequencies.

- Inter-RAT measurements of GERAN frequencies.

- Inter-RAT measurements of CDMA2000 HRPD or CDMA2000 1xRTT or WLAN frequencies.

- CBR measurements.

- Sensing measurements.

The measurement configuration includes the following parameters:

1. Measurement objects: The objects on which the UE shall perform the measurements.

- For intra-frequency and inter-frequency measurements a measurement object is a single E-UTRA carrier
frequency. Associated with this carrier frequency, E-UTRAN can configure a list of cell specific offsets, a
list of 'blacklisted' cells and a list of 'whitelisted' cells. Blacklisted cells are not considered in event evaluation
or measurement reporting.

3GPP
Release 15 173 3GPP TS 36.331 V15.4.0 (2018-12)

- For inter-RAT NR measurements a measurement object is a single NR carrier frequency. Associated with
this carrier frequency, E-UTRAN can configure a list of 'blacklisted' cells. Blacklisted cells are not
considered in event evaluation or measurement reporting.

- For inter-RAT UTRA measurements a measurement object is a set of cells on a single UTRA carrier
frequency.

- For inter-RAT GERAN measurements a measurement object is a set of GERAN carrier frequencies.

- For inter-RAT CDMA2000 measurements a measurement object is a set of cells on a single (HRPD or
1xRTT) carrier frequency.

- For inter-RAT WLAN measurements a measurement object is a set of WLAN identifiers and optionally a set
of WLAN frequencies.

- For CBR measurements and sensing measurements a measurement object is a set of transmission resource
pools for V2X sidelink communication.

NOTE 1: Some measurements using the above mentioned measurement objects, only concern a single cell, e.g.
measurements used to report neighbouring cell system information, PCell UE Rx-Tx time difference, or a
pair of cells, e.g. SSTD measurements between the PCell and the PSCell.

2. Reporting configurations: A list of reporting configurations where each reporting configuration consists of the
following:

- Reporting criterion: The criterion that triggers the UE to send a measurement report. This can either be
periodical or a single event description.

- Reporting format: The quantities that the UE includes in the measurement report and associated information
(e.g. number of cells to report).

3. Measurement identities: A list of measurement identities where each measurement identity links one
measurement object with one reporting configuration. By configuring multiple measurement identities it is
possible to link more than one measurement object to the same reporting configuration, as well as to link more
than one reporting configuration to the same measurement object. The measurement identity is used as a
reference number in the measurement report.

4. Quantity configurations: One quantity configuration is configured per RAT type. The quantity configuration
defines the measurement quantities and associated filtering used for all event evaluation and related reporting of
that measurement type. One filter can be configured per measurement quantity, except for NR where the network
may configure up to 2 sets of quantity configurations each comprising per measurement quantity seperate filters
for cell and RS index measurement results. The quantity configuration set that applies for a given measurement
is indicated within the NR measurement object.

5. Measurement gaps: Periods that the UE may use to perform measurements, i.e. no (UL, DL) transmissions are
scheduled.

E-UTRAN only configures a single measurement object for a given frequency (except for WLAN and except for CBR
measurements), i.e. it is not possible to configure two or more measurement objects for the same frequency with
different associated parameters, e.g. different offsets and/ or blacklists. E-UTRAN may configure multiple instances of
the same event e.g. by configuring two reporting configurations with different thresholds.

The UE maintains a single measurement object list, a single reporting configuration list, and a single measurement
identities list. The measurement object list includes measurement objects, that are specified per RAT type, possibly
including intra-frequency object(s) (i.e. the object(s) corresponding to the serving frequency(ies)), inter-frequency
object(s) and inter-RAT objects. Similarly, the reporting configuration list includes E-UTRA and inter-RAT reporting
configurations. Any measurement object can be linked to any reporting configuration of the same RAT type. Some
reporting configurations may not be linked to a measurement object. Likewise, some measurement objects may not be
linked to a reporting configuration.

The measurement procedures distinguish the following types of cells:

1. The serving cell(s) - these are the PCell and one or more SCells, if configured for a UE supporting CA or DC.
Likewise, NR serving cell(s) are the NR PSCell and SCells, if the UE is configured with EN-DC.

3GPP
Release 15 174 3GPP TS 36.331 V15.4.0 (2018-12)

2. Listed cells - these are cells listed within the measurement object(s) or, for inter-RAT WLAN, the WLANs
matching the WLAN identifiers configured in the measurement object or the WLAN the UE is connected to.

3. Detected cells - these are cells that are not listed within the measurement object(s) but are detected by the UE on
the carrier frequency(ies) indicated by the measurement object(s) or, for inter-RAT WLAN, the WLANs not
included in the measObjectWLAN but meeting the triggering requirements.

For E-UTRA, the UE measures and reports on the serving cell(s), listed cells, detected cells, transmission resource
pools for V2X sidelink communication, and, for RSSI and channel occupancy measurements, the UE measures and
reports on any reception on the indicated frequency. For inter-RAT NR, the UE measures and reports on detected cells
and, if configured with EN-DC, on NR serving cell(s). For inter-RAT UTRA, the UE measures and reports on listed
cells and optionally on cells that are within a range for which reporting is allowed by E-UTRAN. For inter-RAT
GERAN, the UE measures and reports on detected cells. For inter-RAT CDMA2000, the UE measures and reports on
listed cells. For inter-RAT WLAN, the UE measures and reports on listed cells.

NOTE 2: For inter-RAT UTRA and CDMA2000, the UE measures and reports also on detected cells for the
purpose of SON.

NOTE 3: This specification is based on the assumption that typically CSG cells of home deployment type are not
indicated within the neighbour list. Furthermore, the assumption is that for non-home deployments, the
physical cell identity is unique within the area of a large macro cell (i.e. as for UTRAN).

Whenever the procedural specification, other than contained in sub-clause 5.5.2, refers to a field it concerns a field
included in the VarMeasConfig unless explicitly stated otherwise i.e. only the measurement configuration procedure
covers the direct UE action related to the received measConfig.

5.5.2 Measurement configuration

5.5.2.1 General
E-UTRAN applies the procedure as follows:

- to ensure that, whenever the UE has a measConfig, it includes a measObject for each LTE serving frequency;

- to configure at most one measurement identity using a reporting configuration with the purpose set to
reportCGI;

- for E-UTRA serving frequencies, set the EARFCN within the corresponding measObject according to the band
as used for reception/ transmission;

- to configure at most one measurement identity using a reporting configuration with ul-DelayConfig;

- to configure at most one measurement identity using a reporting configuration with reportSFTD-Meas;

- to configure at most one MeasObjectNR with the same carrierFreq;

The UE shall:

1> if the received measConfig includes the measObjectToRemoveList:

2> perform the measurement object removal procedure as specified in 5.5.2.4;

1> if the received measConfig includes the measObjectToAddModList:

2> perform the measurement object addition/ modification procedure as specified in 5.5.2.5;

1> if the received measConfig includes the reportConfigToRemoveList:

2> perform the reporting configuration removal procedure as specified in 5.5.2.6;

1> if the received measConfig includes the reportConfigToAddModList:

2> perform the reporting configuration addition/ modification procedure as specified in 5.5.2.7;

1> if the received measConfig includes the quantityConfig:

3GPP
Release 15 175 3GPP TS 36.331 V15.4.0 (2018-12)

2> perform the quantity configuration procedure as specified in 5.5.2.8;

1> if the received measConfig includes the measIdToRemoveList:

2> perform the measurement identity removal procedure as specified in 5.5.2.2;

1> if the received measConfig includes the measIdToAddModList:

2> perform the measurement identity addition/ modification procedure as specified in 5.5.2.3;

1> if the received measConfig includes the measGapConfig or measGapConfigPerCC-List:

2> perform the measurement gap configuration procedure as specified in 5.5.2.9;

1> if the received measConfig includes the measGapConfigDensePRS:

2> perform the measurement gap configuration procedure for RSTD measurements with dense PRS
configuration as specified in 5.5.2.9a;

1> if the received measConfig includes the measGapSharingConfig:

2> perform the measurement gap sharing configuration procedure as specified in 5.5.2.12;

1> if the received measConfig includes the s-Measure:

2> set the parameter s-Measure within VarMeasConfig to the lowest value of the RSRP ranges indicated by the
received value of s-Measure;

1> if the received measConfig includes the preRegistrationInfoHRPD:

2> forward the preRegistrationInfoHRPD to CDMA2000 upper layers;

1> if the received measConfig includes the speedStatePars:

2> set the parameter speedStatePars within VarMeasConfig to the received value of speedStatePars;

1> if the received measConfig includes the allowInterruptions:

2> set the parameter allowInterruptions within VarMeasConfig to the received value of allowInterruptions;

5.5.2.2 Measurement identity removal

The UE shall:

1> for each measId included in the received measIdToRemoveList that is part of the current UE configuration in
VarMeasConfig:

2> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

2> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

2> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated
information (e.g. timeToTrigger) for this measId;

NOTE: The UE does not consider the message as erroneous if the measIdToRemoveList includes any measId
value that is not part of the current UE configuration.

5.5.2.2a Measurement identity autonomous removal

The UE shall:

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

2> if the associated reportConfig concerns an event involving a serving cell while the concerned serving cell is
not configured; or

3GPP
Release 15 176 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the associated reportConfig concerns an event involving a WLAN mobility set while the concerned WLAN
mobility set is not configured; or

2> if the associated reportConfig concerns an event involving a transmission resource pool for V2X sidelink
communication while the concerned resource pool is not configured; or

2> if the associated reportConfig concerns an event involving reportSFTD-Meas set to pSCell while the nr-
Config is not configured:

3> remove the measId from the measIdList within the VarMeasConfig;

3> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

3> stop the periodical reporting timer if running, and reset the associated information (e.g. timeToTrigger)
for this measId;

NOTE 1: The above UE autonomous removal of measId's applies only for measurement events A1, A2, A6, and
also applies for events A3 and A5 if configured for PSCell and W2 and W3 and V1 and V2 and event
involving reportSFTD-Meas set to pSCell, if configured.

NOTE 2: When performed during re-establishment, the UE is only configured with a primary frequency (i.e. the
SCell(s) and WLAN mobility set are released, if configured).

5.5.2.3 Measurement identity addition/ modification

E-UTRAN applies the procedure as follows:

- configure a measId only if the corresponding measurement object, the corresponding reporting configuration and
the corresponding quantity configuration, are configured;

The UE shall:

1> for each measId included in the received measIdToAddModList:

2> if an entry with the matching measId exists in the measIdList within the VarMeasConfig:

3> replace the entry with the value received for this measId;

2> else:

3> add a new entry for this measId within the VarMeasConfig;

2> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

2> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated
information (e.g. timeToTrigger) for this measId;

2> if the triggerType is set to periodical and the purpose is set to reportCGI in the reportConfig associated with
this measId:

3> if the measObject associated with this measId concerns E-UTRA:

4> if the si-RequestForHO is included in the reportConfig associated with this measId:

5> if the UE is a category 0 UE according to TS 36.306 [5]:

6> start timer T321 with the timer value set to 190 ms for this measId;

5> else:

6> start timer T321 with the timer value set to 150 ms for this measId;

4> else:

5> start timer T321 with the timer value set to 1 second for this measId;

3> else if the measObject associated with this measId concerns UTRA:

3GPP
Release 15 177 3GPP TS 36.331 V15.4.0 (2018-12)

4> if the si-RequestForHO is included in the reportConfig associated with this measId:

5> for UTRA FDD, start timer T321 with the timer value set to 2 seconds for this measId;

5> for UTRA TDD, start timer T321 with the timer value set to [1 second] for this measId;

4> else:

5> start timer T321 with the timer value set to 8 seconds for this measId;

3> else if the measObject associated with this measId concerns NR:

4> if the measObject associated with this measId concerns FR1:

5> start timer T321 with the timer value set to 2 seconds for this measId;

4> if the measObject associated with this measId concerns FR2:

5> start timer T321 with the timer value set to 16 seconds for this measId;

3> else:

4> start timer T321 with the timer value set to 8 seconds for this measId;

5.5.2.4 Measurement object removal

The UE shall:

1> for each measObjectId included in the received measObjectToRemoveList that is part of the current UE
configuration in VarMeasConfig:

2> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

2> remove all measId associated with this measObjectId from the measIdList within the VarMeasConfig, if any;

2> if a measId is removed from the measIdList:

3> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

3> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated
information (e.g. timeToTrigger) for this measId;

NOTE: The UE does not consider the message as erroneous if the measObjectToRemoveList includes any
measObjectId value that is not part of the current UE configuration.

5.5.2.5 Measurement object addition/ modification

The UE shall:

1> for each measObjectId included in the received measObjectToAddModList:

2> if an entry with the matching measObjectId exists in the measObjectList within the VarMeasConfig, for this
entry:

3> reconfigure the entry with the value received for this measObject, except for the fields
cellsToAddModList, blackCellsToAddModList, whiteCellsToAddModList, altTTT-CellsToAddModList,
cellsToRemoveList, blackCellsToRemoveList, whiteCellsToRemoveList, altTTT-CellsToRemoveList,
measSubframePatternConfigNeigh, measDS-Config, wlan-ToAddModList, wlan-ToRemoveList, tx-
ResourcePoolToRemoveList and tx-ResourcePoolToAddList;

3> if the received measObject includes the cellsToRemoveList:

4> for each cellIndex included in the cellsToRemoveList:

5> remove the entry with the matching cellIndex from the cellsToAddModList;

3GPP
Release 15 178 3GPP TS 36.331 V15.4.0 (2018-12)

3> if the received measObject includes the cellsToAddModList:

4> for each cellIndex value included in the cellsToAddModList:

5> if an entry with the matching cellIndex exists in the cellsToAddModList:

6> replace the entry with the value received for this cellIndex;

5> else:

6> add a new entry for the received cellIndex to the cellsToAddModList;

3> if the received measObject includes the blackCellsToRemoveList:

4> for each cellIndex included in the blackCellsToRemoveList:

5> remove the entry with the matching cellIndex from the blackCellsToAddModList;

NOTE 1: For each cellIndex included in the blackCellsToRemoveList that concerns overlapping ranges of cells, a
cell is removed from the black list of cells only if all cell indexes containing it are removed.

3> if the received measObject includes the blackCellsToAddModList:

4> for each cellIndex included in the blackCellsToAddModList:

5> if an entry with the matching cellIndex is included in the blackCellsToAddModList:

6> replace the entry with the value received for this cellIndex;

5> else:

6> add a new entry for the received cellIndex to the blackCellsToAddModList;

3> if the received measObject includes the whiteCellsToRemoveList:

4> for each cellIndex included in the whiteCellsToRemoveList:

5> remove the entry with the matching cellIndex from the whiteCellsToAddModList;

NOTE 2: For each cellIndex included in the whiteCellsToRemoveList that concerns overlapping ranges of cells, a
cell is removed from the white list of cells only if all cell indexes containing it are removed.

3> if the received measObject includes the whiteCellsToAddModList:

4> for each cellIndex included in the whiteCellsToAddModList:

5> if an entry with the matching cellIndex is included in the whiteCellsToAddModList:

6> replace the entry with the value received for this cellIndex;

5> else:

6> add a new entry for the received cellIndex to the whiteCellsToAddModList;

3> if the received measObject includes the altTTT-CellsToRemoveList:

4> for each cellIndex included in the altTTT-CellsToRemoveList:

5> remove the entry with the matching cellIndex from the altTTT-CellsToAddModList;

NOTE 3: For each cellIndex included in the altTTT-CellsToRemoveList that concerns overlapping ranges of cells, a
cell is removed from the list of cells only if all cell indexes containing it are removed.

3> if the received measObject includes the altTTT-CellsToAddModList:

4> for each cellIndex value included in the altTTT-CellsToAddModList:

5> if an entry with the matching cellIndex exists in the altTTT-CellsToAddModList:

3GPP
Release 15 179 3GPP TS 36.331 V15.4.0 (2018-12)

6> replace the entry with the value received for this cellIndex;

5> else:

6> add a new entry for the received cellIndex to the altTTT-CellsToAddModList;

3> if the received measObject includes measSubframePatternConfigNeigh:

4> set measSubframePatternConfigNeigh within the VarMeasConfig to the value of the received field

3> if the received measObject includes measDS-Config:

4> if measDS-Config is set to setup:

5> if the received measDS-Config includes the measCSI-RS-ToRemoveList:

6> for each measCSI-RS-Id included in the measCSI-RS-ToRemoveList:

7> remove the entry with the matching measCSI-RS-Id from the measCSI-RS-ToAddModList;

5> if the received measDS-Config includes the measCSI-RS-ToAddModList, for each measCSI-RS-Id
value included in the measCSI-RS-ToAddModList:

6> if an entry with the matching measCSI-RS-Id exists in the measCSI-RS-ToAddModList:

7> replace the entry with the value received for this measCSI-RS-Id;

6> else:

7> add a new entry for the received measCSI-RS-Id to the measCSI-RS-ToAddModList;

5> set other fields of the measDS-Config within the VarMeasConfig to the value of the received
fields;

5> perform the discovery signals measurement timing configuration procedure as specified in
5.5.2.10;

4> else:

5> release the discovery signals measurement configuration;

3> if the received measObject modifies fields other than cellsForWhichToReportSFTD:

4> for each measId associated with this measObjectId in the measIdList within the VarMeasConfig, if
any:

5> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

5> stop the periodical reporting timer or timer T321, whichever one is running, and reset the
associated information (e.g. timeToTrigger) for this measId;

3> if the received measObject includes the wlan-ToRemoveList:

4> for each WLAN-Identifiers included in the wlan-ToRemoveList:

5> remove the entry with the matching WLAN-Identifiers from the wlan-ToAddModList;

NOTE 3a: Matching of WLAN-Identifiers requires that all WLAN identifier fields should be same.

3> if the received measObject includes the wlan-ToAddModList:

4> for each WLAN-Identifiers included in the wlan-ToAddModList:

5> add a new entry for the received WLAN-Identifiers to the wlan-ToAddModList;

3> if the received measObject includes the tx-ResourcePoolToRemoveList:

4> for each transmission resource pool indicated in tx-ResourcePoolToRemoveList:

3GPP
Release 15 180 3GPP TS 36.331 V15.4.0 (2018-12)

5> remove the entry with the matching identity of the transmission resource pool from the tx-
ResourcePoolToAddList;

3> if the received measObject includes the tx-ResourcePoolToAddList:

4> for each transmission resource pool indicated in tx-ResourcePoolToAddList:

5> add a new entry for the received identity of the transmission resource pool to the tx-
ResourcePoolToAddList;

2> else:

3> add a new entry for the received measObject to the measObjectList within VarMeasConfig;

NOTE 4: UE does not need to retain cellForWhichToReportCGI in the measObject after reporting cgi-Info.

5.5.2.6 Reporting configuration removal

The UE shall:

1> for each reportConfigId included in the received reportConfigToRemoveList that is part of the current UE
configuration in VarMeasConfig:

2> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

2> remove all measId associated with the reportConfigId from the measIdList within the VarMeasConfig, if any;

2> if a measId is removed from the measIdList:

3> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

3> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated
information (e.g. timeToTrigger) for this measId;

NOTE: The UE does not consider the message as erroneous if the reportConfigToRemoveList includes any
reportConfigId value that is not part of the current UE configuration.

5.5.2.7 Reporting configuration addition/ modification

The UE shall:

1> for each reportConfigId included in the received reportConfigToAddModList:

2> if an entry with the matching reportConfigId exists in the reportConfigList within the VarMeasConfig, for
this entry:

3> reconfigure the entry with the value received for this reportConfig;

3> for each measId associated with this reportConfigId included in the measIdList within the
VarMeasConfig, if any:

4> remove the measurement reporting entry for this measId from in VarMeasReportList, if included;

4> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated
information (e.g. timeToTrigger) for this measId;

2> else:

3> add a new entry for the received reportConfig to the reportConfigList within the VarMeasConfig;

5.5.2.8 Quantity configuration

The UE shall:

1> for each RAT for which the received quantityConfig includes parameter(s):

3GPP
Release 15 181 3GPP TS 36.331 V15.4.0 (2018-12)

2> set the corresponding parameter(s) in quantityConfig within VarMeasConfig to the value of the received
quantityConfig parameter(s);

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

2> remove the measurement reporting entry for this measId from the VarMeasReportList, if included;

2> stop the periodical reporting timer or timer T321, whichever one is running, and reset the associated
information (e.g. timeToTrigger) for this measId;

5.5.2.9 Measurement gap configuration

The UE shall:

1> if measGapConfig is set to setup:

2> if a measurement gap configuration measGapConfig or measGapConfigPerCC-List is already setup, release

the measurement gap configuration;

2> if the gapOffset in measGapConfig indicates a non-uniform gap pattern:

3> setup the measurement gap configuration indicated by the measGapConfig in accordance with the
received gapOffset, i.e., the first subframe of the first gap of each non-uniform gap pattern occurs at an
SFN and subframe meeting the following condition (SFN and subframe of MCG cells):

SFN mod T = FLOOR(gapOffset/10);

subframe = gapOffset mod 10;

with T = LMGRP/10 as defined in TS 36.133 [16];

2> else:

3> setup the measurement gap configuration indicated by the measGapConfig in accordance with the
received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the
following condition (SFN and subframe of MCG cells):

SFN mod T = FLOOR(gapOffset/10);

subframe = gapOffset mod 10;

with T = MGRP/10 as defined in TS 36.133 [16];

2> if EN-DC is configured:

3> if the UE is configured with fr1-Gap set to TRUE:

4> apply the gap configuration for LTE serving cells and for NR serving cells on FR1;

3> else:

4> apply the gap configuration for all LTE and NR serving cells;

2> if mgta is set to TRUE, apply a timing advance value of 0.5ms to the gap occurrences calculated above
according to TS 38.133 [16];

NOTE 1: The UE applies a single gap, which timing is relative to the MCG cells, even when configured with DC.
In case of EN-DC, the UE may either be configured with a single (common) gap or with two separate
gaps i.e. a first one for FR1 (configured by E-UTRA RRC) and a second one for FR2 (configured by NR
RRC).

1> else if measGapConfig is set to release:

2> release the measurement gap configuration measGapConfig;

1> if measGapConfigPerCC-List is set to setup:

3GPP
Release 15 182 3GPP TS 36.331 V15.4.0 (2018-12)

2> if a measurement gap configuration measGapConfig is already setup, release measGapConfig;

2> if measGapConfigToRemoveList is included:

3> for each ServCellIndex included in the measGapConfigToRemoveList:

4> release measGapConfigCC for the serving cell indicated by servCellId;

2> if measGapConfigToAddModList is included:

3> for each ServCellIndex included in the measGapConfigToAddModList:

4> store measGapConfigCC for the serving cell indicated by servCellId;

2> for each serving cell with stored measGapConfigCC indicating a non-uniform gap pattern, setup the
measurement gap configuration indicated by the measGapConfigCC in accordance with the received
gapOffset, i.e., the first subframe of the first gap of each non-uniform gap pattern occurs at an SFN and
subframe meeting the following condition (SFN and subframe of MCG cells):

SFN mod T = FLOOR(gapOffset/10);

subframe = gapOffset mod 10;

with T = LMGRP/10 as defined in TS 36.133 [16];

2> for each serving cell with stored measGapConfigCC not indicating a non-uniform gap pattern, setup the
measurement gap configuration indicated by the measGapConfigCC in accordance with the received
gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition
(SFN and subframe of MCG cells):

SFN mod T = FLOOR(gapOffset/10);

subframe = gapOffset mod 10;

with T = MGRP/10 as defined in TS 36.133 [16];

NOTE 2: The UE applies gap timing relative to the MCG cells, even when configured with DC.

1> else (measGapConfigPerCC-List is set to release):

2> release the measurement gap configuration measGapConfigPerCC-List;

NOTE 3: When a SCell is released, the UE is not required to apply a per CC measurement gap configuration
associated to the SCell.

5.5.2.9a Measurement gap configuration for RSTD measurements with dense PRS
configuration
The UE shall:

1> if measGapConfigDensePRS is set to setup:

2> setup the measurement gap configuration indicated by the measGapConfigDensePRS in accordance with the
received gapOffsetDensePRS, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the
following condition:

SFN mod T = FLOOR(gapOffsetDensePRS/10);

subframe = gapOffsetDensePRS mod 10;

with T = MGRP/10 as defined in TS 36.133 [16];

3GPP
Release 15 183 3GPP TS 36.331 V15.4.0 (2018-12)

5.5.2.10 Discovery signals measurement timing configuration

The UE shall setup the discovery signals measurement timing configuration (DMTC) in accordance with the received
dmtc-PeriodOffset, i.e., the first subframe of each DMTC occasion occurs at an SFN and subframe of the PCell meeting
the following condition:

SFN mod T = FLOOR(dmtc-Offset/10);

subframe = dmtc-Offset mod 10;

with T = dmtc-Periodicity/10;

On the concerned frequency, the UE shall not consider discovery signals transmission in subframes outside the DMTC
occasion for measurements including RRM measurements.

5.5.2.11 RSSI measurement timing configuration

The UE shall setup the RSSI measurement timing configuraton (RMTC) in accordance with the received rmtc-Period,
rmtc-SubframeOffset if configured otherwise determined by the UE randomly, i.e. the first symbol of each RMTC
occasion occurs at first symbol of an SFN and subframe of the PCell meeting the following condition:

SFN mod T = FLOOR(rmtc-SubframeOffset/10);

subframe = rmtc-SubframeOffset mod 10;

with T = rmtc-Period/10;

On the concerned frequency, the UE shall not consider RSSI measurements outside the configured RMTC occasion
which lasts for measDuration for RSSI and channel occupancy measurements.

5.5.2.12 Measurement gap sharing configuration

The UE shall:

1> if measGapSharingConfig is set to setup:

2> if a measurement gap sharing configuration is already setup, release the measurement gap sharing
configuration;

2> setup the measurement gap sharing configuration indicated by the measGapSharingConfig in accordance
with the received measGapSharingScheme as defined in TS 36.133 [16];

NOTE: In case of EN-DC, the UE may either be configured with a single (common) gap sharing or with two
separate gap sharing configurations, i.e. a first one for FR1 (configured by E-UTRA RRC) and a second
one for FR2 (configured by NR RRC). For the case of per FR gap configuration, the gap sharing
configured here (i.e. E-UTRA RRC) is applicable only for FR1 gap.

1> else:

2> release the measurement gap sharing configuration;

5.5.2.13 NR measurement timing configuration

The UE shall setup the first SS/PBCH block measurement timing configuration (SMTC) in accordance with the
received periodicityAndOffset parameter in the MTC-SSB-NR configuration i.e., the first subframe of each SMTC
occasion occurs at an SFN and subframe of the PCell meeting the following condition:

SFN mod T = FLOOR(Offset/10);

if the Periodicity is larger than sf5:

subframe = Offset mod 10;

else;

3GPP
Release 15 184 3GPP TS 36.331 V15.4.0 (2018-12)

subframe = Offset or (Offset +5);

with T = CEIL(Periodicity/10).

On the concerned frequency, the UE shall not consider SS/PBCH block transmission in subframes outside the SMTC
occasion for measurements including RRM measurements.

5.5.3 Performing measurements

5.5.3.1 General
For all measurements, except for UE Rx–Tx time difference measurements, RSSI, UL PDCP Packet Delay per QCI
measurement, channel occupancy measurements, CBR measurement, sensing measurement and except for WLAN
measurements of Band, Carrier Info, Available Admission Capacity, Backhaul Bandwidth, Channel Utilization, and
Station Count, the UE applies the layer 3 filtering as specified in 5.5.3.2, before using the measured results for
evaluation of reporting criteria or for measurement reporting. When performing measurements on NR carriers, the UE
derives the cell quality as specified in 5.5.3.3 and the beam quality as specified in 5.5.3.4.

The UE shall:

1> whenever the UE has a measConfig, perform RSRP and RSRQ measurements for each serving cell as follows:

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

2> if the UE supports CRS based discovery signals measurement:

3> for each SCell in deactivated state, apply the discovery signals measurement timing configuration in
accordance with measDS-Config, if configured within the measObject corresponding to the frequency of
the SCell;

1> if the UE has a measConfig with rs-sinr-Config configured, perform RS-SINR (as indicated in the associated
reportConfig) measurements as follows:

2> perform the corresponding measurements on the frequency indicated in the associated measObject using
available idle periods or using autonomous gaps as necessary;

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

2> if the purpose for the associated reportConfig is set to reportCGI:

3> if si-RequestForHO is configured for the associated reportConfig:

4> perform the corresponding measurements on the frequency and RAT indicated in the associated
measObject using autonomous gaps as necessary;

3> else:

4> perform the corresponding measurements on the frequency and RAT indicated in the associated
measObject using available idle periods or using autonomous gaps as necessary;

NOTE 1: If autonomous gaps are used to perform measurements, the UE is allowed to temporarily abort
communication with all serving cell(s), i.e. create autonomous gaps to perform the corresponding
measurements within the limits specified in TS 36.133 [16]. Otherwise, the UE only supports the
measurements with the purpose set to reportCGI only if E-UTRAN has provided sufficient idle periods.

3> try to acquire the global cell identity of the cell indicated by the cellForWhichToReportCGI in the
associated measObject by acquiring the relevant system information from the concerned cell;

3> if an entry in the cellAccessRelatedInfoList includes the selected PLMN, acquire the relevant system
information from the concerned cell;

3> if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is an E-
UTRAN cell:

3GPP
Release 15 185 3GPP TS 36.331 V15.4.0 (2018-12)

4> try to acquire the CSG identity, if the CSG identity is broadcast in the concerned cell;

4> try to acquire the trackingAreaCode in the concerned cell;

4> try to acquire the list of additional PLMN Identities, as included in the plmn-IdentityList, if multiple
PLMN identities are broadcast in the concerned cell;

4> if cellAccessRelatedInfoList is included, use trackingAreaCode and plmn-IdentityList from the entry
of cellAccessRelatedInfoList containing the selected PLMN;

4> if the includeMultiBandInfo is configured:

5> try to acquire the freqBandIndicator in the SystemInformationBlockType1of the concerned cell;

5> try to acquire the list of additional frequency band indicators, as included in the multiBandInfoList,
if multiple frequency band indicators are included in the SystemInformationBlockType1of the
concerned cell;

5> try to acquire the freqBandIndicatorPriority, if the freqBandIndicatorPriority is included in the

SystemInformationBlockType1of the concerned cell;

4> if cellAccessRelatedInfoList-5GC is broadcast in the concerned cell and the UE is E-UTRA/5GC

capable:

5> try to acquire the cellAccessRelatedInfoList-5GC;

NOTE 2: The 'primary' PLMN is part of the global cell identity.

3> if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a UTRAN
cell:

4> try to acquire the LAC, the RAC and the list of additional PLMN Identities, if multiple PLMN
identities are broadcast in the concerned cell;

4> try to acquire the CSG identity, if the CSG identity is broadcast in the concerned cell;

3> if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a GERAN
cell:

4> try to acquire the RAC in the concerned cell;

3> if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a
CDMA2000 cell and the cdma2000-Type included in the measObject is typeHRPD:

4> try to acquire the Sector ID in the concerned cell;

3> if the cell indicated by the cellForWhichToReportCGI included in the associated measObject is a
CDMA2000 cell and the cdma2000-Type included in the measObject is type1XRTT:

4> try to acquire the BASE ID, SID and NID in the concerned cell;

3> if the cell indicated by the cellForWhichToReportCGI included in the associated MeasObject is an NR
cell:

4> if the indicated cell is broadcasting SIB1 (see TS 38.213 [88], clause 13):

5> try to acquire the plmn-IdentityInfoList including plmn-IdentityList, trackingAreaCode (if

available), ran-AreaCode (if available) and cellIdentity for each entry of the plmn-IdentityInfoList;

5> try to acquire the frequencyBandList, if multiple frequency bands are broadcasted in the concerned
cell;

2> if the ul-DelayConfig is configured for the associated reportConfig:

3> ignore the measObject;

3> configure the PDCP layer to perform UL PDCP Packet Delay per QCI measurement;

3GPP
Release 15 186 3GPP TS 36.331 V15.4.0 (2018-12)

2> else:

3> if a measurement gap configuration is setup; or

3> if the UE does not require measurement gaps to perform the concerned measurements:

4> if s-Measure is not configured; or

4> if s-Measure is configured and the PCell RSRP, after layer 3 filtering, is lower than this value; or

4> if the associated measObject concerns NR; or

4> if measDS-Config is configured in the associated measObject:

5> if the UE supports CSI-RS based discovery signals measurement; and

5> if the eventId in the associated reportConfig is set to eventC1 or eventC2, or if

reportStrongestCSI-RSs is included in the associated reportConfig:

6> perform the corresponding measurements of CSI-RS resources on the frequency indicated in
the concerned measObject, applying the discovery signals measurement timing configuration
in accordance with measDS-Config in the concerned measObject;

6> if reportCRS-Meas is included in the associated reportConfig, perform the corresponding

measurements of neighbouring cells on the frequencies indicated in the concerned measObject
as follows:

7> for neighbouring cells on the primary frequency, apply the time domain measurement
resource restriction in accordance with measSubframePatternConfigNeigh, if configured in
the concerned measObject;

7> apply the discovery signals measurement timing configuration in accordance with measDS-
Config in the concerned measObject;

5> else:

6> perform the corresponding measurements of neighbouring cells on the frequencies and RATs
indicated in the concerned measObject as follows:

7> for neighbouring cells on the primary frequency, apply the time domain measurement
resource restriction in accordance with measSubframePatternConfigNeigh, if configured in
the concerned measObject;

7> if the UE supports CRS based discovery signals measurement, apply the discovery signals
measurement timing configuration in accordance with measDS-Config, if configured in the
concerned measObject;

4> if the ue-RxTxTimeDiffPeriodical is configured in the associated reportConfig:

5> perform the UE Rx–Tx time difference measurements on the PCell;

4> if the reportSSTD-Meas is set to true or pSCell in the associated reportConfig:

5> perform SSTD measurements between the PCell and the PSCell;

4> if the reportSFTD-Meas is set to pSCell in the associated reportConfig:

5> perform SFTD measurements between the PCell and the NR PSCell;

4> if the reportSFTD-Meas is set to neighborCells in the associated reportConfig:

5> perform SFTD measurements between the PCell and NR cell(s) on the frequency indicated in the
associated measObject;

4> if the measRSSI-ReportConfig is configured in the associated reportConfig:

3GPP
Release 15 187 3GPP TS 36.331 V15.4.0 (2018-12)

5> perform the RSSI and channel occupancy measurements on the frequency indicated in the
associated measObject;

2> perform the evaluation of reporting criteria as specified in 5.5.4;

The UE capable of CBR measurement when configured to transmit non-P2X related V2X sidelink communication
shall:

1> if in coverage on the frequency used for V2X sidelink communication transmission as defined in TS 36.304 [4],
clause 11.4; or

1> if the concerned frequency is included in v2x-InterFreqInfoList in RRCConnectionReconfiguration or in v2x-

InterFreqInfoList within SystemInformationBlockType21 or SystemInformationBlockType26:

2> if the UE is in RRC_IDLE:

3> if the concerned frequency is the camped frequency:

4> perform CBR measurement on the pools in v2x-CommTxPoolNormalCommon and v2x-

CommTxPoolExceptional if included in SystemInformationBlockType21;

3> else if v2x-CommTxPoolNormal or v2x-CommTxPoolExceptional is included in v2x-InterFreqInfoList for

the concerned frequency within SystemInformationBlockType21 or SystemInformationBlockType26:

4> perform CBR measurement on pools in v2x-CommTxPoolNormal and v2x-CommTxPoolExceptional

in v2x-InterFreqInfoList for the concerned frequency in SystemInformationBlockType21 or
SystemInformationBlockType26;

3> else if the concerned frequency broadcasts SystemInformationBlockType21:

4> perform CBR measurement on pools in v2x-CommTxPoolNormalCommon and v2x-

CommTxPoolExceptional if included in SystemInformationBlockType21 broadcast on the concerned
frequency;

2> if the UE is in RRC_CONNECTED:

3> if tx-ResourcePoolToAddList is included in VarMeasConfig:

4> perform CBR measurements on each resource pool indicated in tx-ResourcePoolToAddList;

3> if the concerned frequency is the PCell's frequency:

4> perform CBR measurement on the pools in v2x-CommTxPoolNormalDedicated or v2x-

SchedulingPool if included in RRCConnectionReconfiguration, v2x-CommTxPoolExceptional if
included in SystemInformationBlockType21 for the concerned frequency and v2x-
CommTxPoolExceptional if included in mobilityControlInfoV2X;

3> else if v2x-CommTxPoolNormal, v2x-SchedulingPool or v2x-CommTxPoolExceptional is included in

v2x-InterFreqInfoList for the concerned frequency within RRCConnectionReconfiguration:

4> perform CBR measurement on pools in v2x-CommTxPoolNormal, v2x-SchedulingPool, and v2x-

CommTxPoolExceptional if included in v2x-InterFreqInfoList for the concerned frequency in
RRCConnectionReconfiguration;

3> else if the concerned frequency broadcasts SystemInformationBlockType21:

4> perform CBR measurement on pools in v2x-CommTxPoolNormalCommon and v2x-

CommTxPoolExceptional if included in SystemInformationBlockType21 for the concerned frequency;

1> else:

2> perform CBR measurement on pools in v2x-CommTxPoolList in SL-V2X-Preconfiguration for the concerned
frequency;

The UE capable of sensing measurement, with commTxResources set to scheduled, shall:

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

3GPP
Release 15 188 3GPP TS 36.331 V15.4.0 (2018-12)

2> if measSensing-Config is configured in the associated measObject

3> perform the sensing measurement in accordance with TS 36.213 [23] on the pools of v2x-SchedulingPool
and also indicated in tx-ResourcePoolToAddList in the associated measObject, using
sensingSubchannelNumber, sensingPeriodicity, sensingResourceCounter and sensingPriority.

NOTE 3: The s-Measure defines when the UE is required to perform measurements. The UE is however allowed to
perform measurements also when the PCell RSRP exceeds s-Measure, e.g., to measure cells broadcasting
a CSG identity following use of the autonomous search function as defined in TS 36.304 [4].

NOTE 4: The UE may not perform the WLAN measurements it is configured with e.g. due to connection to another
WLAN based on user preferences as specified in TS 23.402 [75] or due to turning off WLAN.

5.5.3.2 Layer 3 filtering

The UE shall:

1> for each measurement quantity that the UE performs measurements according to 5.5.3.1:

NOTE 1: This does not include quantities configured solely for UE Rx-Tx time difference, SSTD measurements
and RSSI, channel occupancy measurements, WLAN measurements of Band, Carrier Info, Available
Admission Capacity, Backhaul Bandwidth, Channel Utilization, and Station Count, CBR measurement,
sensing measurement and UL PDCP Packet Delay per QCI measurement i.e. for those types of
measurements the UE ignores the triggerQuantity and reportQuantity.

2> filter the measured result, before using for evaluation of reporting criteria or for measurement reporting, by
the following formula:

Fn  (1  a )  Fn 1  a  M n

where

Mn is the latest received measurement result from the physical layer;

Fn is the updated filtered measurement result, that is used for evaluation of reporting criteria or for
measurement reporting;

Fn-1 is the old filtered measurement result, where F0 is set to M1 when the first measurement result from
the physical layer is received; and

a = 1/2(k/4), where k is the filterCoefficient for the corresponding measurement quantity received by the
quantityConfig;

2> adapt the filter such that the time characteristics of the filter are preserved at different input rates, observing
that the filterCoefficient k assumes a sample rate equal to 200 ms;

NOTE 2: If k is set to 0, no layer 3 filtering is applicable.

NOTE 3: The filtering is performed in the same domain as used for evaluation of reporting criteria or for
measurement reporting, i.e., logarithmic filtering for logarithmic measurements.

NOTE 4: The filter input rate is implementation dependent, to fulfil the performance requirements set in TS 36.133
[16]. For further details about the physical layer measurements, see TS 36.133 [16].

5.5.3.3 Derivation of NR cell quality

The UE shall:

1> if the associated measObject includes maxRS-IndexCellQual; and

1> if there are multiple detected NR-SS beams associated to the cell; and

1> if threshRS-Index is configured and if for more than one of the NR-SS beams the measured result exceeds this
threshold:

3GPP
Release 15 189 3GPP TS 36.331 V15.4.0 (2018-12)

2> consider the cell quality to be the linear average of the power values of the, up to maxRS-IndexCellQual, best
of the detected NR-SS beams exceeding threshRS-Index;

1> else:

2> consider the cell quality to be the measurement result of the detected NR-SS beam, associated to the cell,
with the highest measurement result;

5.5.3.4 Derivation of NR beam quality

The UE shall:

1> consider the beam quality to be the value resulting after layer 3 filtering, as specified in 5.5.3.2, of the
measurement results of the concerned beam, where each result is averaged as described in TS 38.215 [89];

5.5.4 Measurement report triggering

5.5.4.1 General
If security has been activated successfully, the UE shall:

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

2> if the corresponding reportConfig includes a purpose set to reportStrongestCellsForSON:

3> consider any neighbouring cell detected on the associated frequency to be applicable;

2> else if the corresponding reportConfig includes a purpose set to reportCGI:

3> consider any neighbouring cell detected on the associated frequency/ set of frequencies (GERAN) which
has a physical cell identity matching the value of the cellForWhichToReportCGI included in the
corresponding measObject within the VarMeasConfig to be applicable;

2> else:

3> if the corresponding measObject concerns E-UTRA:

4> if the ue-RxTxTimeDiffPeriodical is configured in the corresponding reportConfig:

5> consider only the PCell to be applicable;

4> else if the reportSSTD-Meas is set to true in the corresponding reportConfig:

5> consider the PSCell to be applicable;

4> else if the eventA1 or eventA2 is configured in the corresponding reportConfig:

5> consider only the serving cell to be applicable;

4> else if eventC1 or eventC2 is configured in the corresponding reportConfig; or if reportStrongestCSI-

RSs is included in the corresponding reportConfig:

5> consider a CSI-RS resource on the associated frequency to be applicable when the concerned CSI-
RS resource is included in the measCSI-RS-ToAddModList defined within the VarMeasConfig for
this measId;

4> else if measRSSI-ReportConfig is configured in the corresponding reportConfig:

5> consider the resource indicated by the rmtc-Config on the associated frequency to be applicable;

4> else:

5> if useWhiteCellList is set to TRUE:

3GPP
Release 15 190 3GPP TS 36.331 V15.4.0 (2018-12)

6> consider any neighbouring cell detected on the associated frequency to be applicable when the
concerned cell is included in the whiteCellsToAddModList defined within the VarMeasConfig
for this measId;

5> else:

6> consider any neighbouring cell detected on the associated frequency to be applicable when the
concerned cell is not included in the blackCellsToAddModList defined within the
VarMeasConfig for this measId;

5> for events involving a serving cell on one frequency and neighbours on another frequency,
consider the serving cell on the other frequency as a neighbouring cell;

4> if the corresponding reportConfig includes alternativeTimeToTrigger and if the UE supports

alternativeTimeToTrigger:

5> use the value of alternativeTimeToTrigger as the time to trigger instead of the value of
timeToTrigger in the corresponding reportConfig for cells included in the altTTT-
CellsToAddModList of the corresponding measObject;

3> else if the corresponding measObject concerns UTRA or CDMA2000:

4> consider a neighbouring cell on the associated frequency to be applicable when the concerned cell is
included in the cellsToAddModList defined within the VarMeasConfig for this measId (i.e. the cell is
included in the white-list);

NOTE 0: The UE may also consider a neighbouring cell on the associated UTRA frequency to be applicable when
the concerned cell is included in the csg-allowedReportingCells within the VarMeasConfig for this
measId, if configured in the corresponding measObjectUTRA (i.e. the cell is included in the range of
physical cell identities for which reporting is allowed).

3> else if the corresponding measObject concerns GERAN:

4> consider a neighbouring cell on the associated set of frequencies to be applicable when the concerned
cell matches the ncc-Permitted defined within the VarMeasConfig for this measId;

3> else if the corresponding measObject concerns WLAN:

4> consider a WLAN on the associated set of frequencies, as indicated by carrierFreq or on all WLAN
frequencies when carrierFreq is not present, to be applicable if the WLAN matches all WLAN
identifiers of at least one entry within wlan-Id-List for this measId;

3> else if the corresponding measObject concerns NR:

4> if the reportSFTD-Meas is set to pSCell in the corresponding reportConfigInterRAT:

5> consider the PSCell to be applicable;

4> else if the reportSFTD-Meas is set to neighborCells in the corresponding reportConfigInterRAT:

5> if cellsForWhichToReportSFTD is configured in the corresponding measObjectNR:

6> consider any neighbouring NR cell on the associated frequency that is included in
cellsForWhichToReportSFTD to be applicable;

5> else:

6> consider up to 3 strongest neighbouring NR cells detected on the associated frequency to be

applicable when the concerned cells are not included in the blackCellsToAddModList defined
within the VarMeasConfig for this measId;

4> else:

5> if the eventB1 or eventB2 is configured in the corresponding reportConfig:

6> consider a serving cell, if any, on the associated NR frequency as neighbouring cell;

3GPP
Release 15 191 3GPP TS 36.331 V15.4.0 (2018-12)

5> consider any neighbouring cell detected on the associated frequency to be applicable when the
concerned cell is not included in the blackCellsToAddModList defined within the VarMeasConfig
for this measId;

2> if tx-ResourcePoolToAddList is configured in the measObject, and if the corresponding reportConfig

includes a purpose set to sidelink or includes eventV1 or eventV2:

3> consider the transmission resource pools indicated by the tx-ResourcePoolToAddList defined within the
VarMeasConfig for this measId to be applicable;

2> if the corresponding reportConfig includes a purpose set to reportLocation:

3> consider only the PCell to be applicable;

2> if the triggerType is set to event, and if the corresponding reportConfig does not include
numberOfTriggeringCells, and if the entry condition applicable for this event, i.e. the event corresponding
with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more
applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event
within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for
this measId (a first cell triggers the event):

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this
measId;

3> if the UE supports T312 and if useT312 is included for this event and if T310 is running:

4> if T312 is not running:

5> start timer T312 with the value configured in the corresponding measObject;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the triggerType is set to event, and if the corresponding reportConfig does not include
numberOfTriggeringCells, and if the entry condition applicable for this event, i.e. the event corresponding
with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more
applicable cells not included in the cellsTriggeredList for all measurements after layer 3 filtering taken
during timeToTrigger defined for this event within the VarMeasConfig (a subsequent cell triggers the event):

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this
measId;

3> if the UE supports T312 and if useT312 is included for this event and if T310 is running:

4> if T312 is not running:

5> start timer T312 with the value configured in the corresponding measObject;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the triggerType is set to event and if the corresponding reportConfig includes numberOfTriggeringCells,
and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the
corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all
measurements after layer 3 filtering taken during timeToTrigger defined for this event within the
VarMeasConfig:

3> If the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell
triggers the event):

4> include a measurement reporting entry within the VarMeasReportList for this measId;

3GPP
Release 15 192 3GPP TS 36.331 V15.4.0 (2018-12)

3> If the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCell:

4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this
measId;

3> else:

4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this
measId;

4> If the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCells:

5> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

5> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the triggerType is set to event and if the leaving condition applicable for this event is fulfilled for one or
more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for
all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for
this event:

3> remove the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this
measId;

3> if reportOnLeave is set to TRUE for the corresponding reporting configuration or if a6-ReportOnLeave is
set to TRUE or if a4-a5-ReportOnLeave is set to TRUE for the corresponding reporting configuration:

4> initiate the measurement reporting procedure, as specified in 5.5.5;

3> if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty:

4> remove the measurement reporting entry within the VarMeasReportList for this measId;

4> stop the periodical reporting timer for this measId, if running;

2> if the triggerType is set to event and if the entry condition applicable for this event, i.e. the event
corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one
or more applicable CSI-RS resources for all measurements after layer 3 filtering taken during timeToTrigger
defined for this event within the VarMeasConfig, while the VarMeasReportList does not include an
measurement reporting entry for this measId (i.e. a first CSI-RS resource triggers the event):

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned CSI-RS resource(s) in the csi-RS-TriggeredList defined within the
VarMeasReportList for this measId;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the triggerType is set to event and if the entry condition applicable for this event, i.e. the event
corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one
or more applicable CSI-RS resources not included in the csi-RS-TriggeredList for all measurements after
layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (i.e. a
subsequent CSI-RS resource triggers the event):

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned CSI-RS resource(s) in the csi-RS-TriggeredList defined within the
VarMeasReportList for this measId;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the triggerType is set to event and if the leaving condition applicable for this event is fulfilled for one or
more of the CSI-RS resources included in the csi-RS-TriggeredList defined within the VarMeasReportList for

3GPP
Release 15 193 3GPP TS 36.331 V15.4.0 (2018-12)

this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the
VarMeasConfig for this event:

3> remove the concerned CSI-RS resource(s) in the csi-RS-TriggeredList defined within the
VarMeasReportList for this measId;

3> if c1-ReportOnLeave is set to TRUE for the corresponding reporting configuration or if c2-
ReportOnLeave is set to TRUE for the corresponding reporting configuration:

4> initiate the measurement reporting procedure, as specified in 5.5.5;

3> if the csi-RS-TriggeredList defined within the VarMeasReportList for this measId is empty:

4> remove the measurement reporting entry within the VarMeasReportList for this measId;

4> stop the periodical reporting timer for this measId, if running;

2> if the triggerType is set to event and if the entry condition applicable for this event, i.e. the event
corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one
or more applicable transmission resource pools for all measurements taken during timeToTrigger defined for
this event within the VarMeasConfig, while the VarMeasReportList does not include an measurement
reporting entry for this measId (a first transmission resource pool triggers the event):

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned transmission resource pool(s) in the poolsTriggeredList defined within the
VarMeasReportList for this measId;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the triggerType is set to event and if the entry condition applicable for this event, i.e. the event
corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one
or more applicable transmission resource pools not included in the poolsTriggeredList for all measurements
taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent transmission
resource pool triggers the event):

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> include the concerned transmission resource pool(s) in the poolsTriggeredList defined within the
VarMeasReportList for this measId;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the triggerType is set to event and if the leaving condition applicable for this event is fulfilled for one or
more applicable transmission resource pools included in the poolsTriggeredList defined within the
VarMeasReportList for this measId for all measurements taken during timeToTrigger defined within the
VarMeasConfig for this event:

3> remove the concerned transmission resource pool(s) from the poolsTriggeredList defined within the
VarMeasReportList for this measId;

3> if the poolsTriggeredList defined within the VarMeasReportList for this measId is empty:

4> remove the measurement reporting entry within the VarMeasReportList for this measId;

4> stop the periodical reporting timer for this measId, if running;

2> if the triggerType is set to event and if the eventId is set to eventH1 or eventH2 and if the entering condition
applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig
within VarMeasConfig, is fulfilled during timeToTrigger defined within the VarMeasConfig for this event:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3GPP
Release 15 194 3GPP TS 36.331 V15.4.0 (2018-12)

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if measRSSI-ReportConfig is included and if a (first) measurement result is available:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure as specified in 5.5.5 immediately when RSSI sample values
are reported by the physical layer after the first L1 measurement duration;

2> else if the purpose is included and set to reportStrongestCells, reportStrongestCellsForSON, reportLocation
sidelink or sensing and if a (first) measurement result is available:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> if the purpose is set to reportStrongestCells and reportStrongestCSI-RSs is not included:

4> if the triggerType is set to periodical and the corresponding reportConfig includes the ul-
DelayConfig:

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first
measurement result is provided by lower layers;

4> else if the corresponding measurement object concerns WLAN:

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity
to be reported becomes available for the PCell and for the applicable WLAN(s);

4> else if the reportAmount exceeds 1:

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity
to be reported becomes available for the PCell;

4> else (i.e. the reportAmount is equal to 1):

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity
to be reported becomes available for the PCell and for the strongest cell among the applicable
cells, or becomes available for the pair of PCell and the PSCell in case of SSTD measurements, or
becomes available for each requested pair of PCell and NR cell or the maximal measurement
reporting delay as specified in TS 38.133 [84], clause 8.17.2.3 in case of SFTD measurements;

3> if the purpose is set to reportLocation, sidelink or sensing:

4> if the purpose is set to reportLocation:

5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after both the
quantity to be reported for the PCell and the location information become available;

4> else if the purpose is set to sidelink:

5> initiate the measurement reporting procedure as specified in 5.5.5 immediately after both the
quantity to be reported for the PCell and the CBR measurement result become available;

4> else if the purpose is set to sensing:

5> initiate the measurement reporting procedure as specified in 5.5.5 immediately after both the
quantity to be reported for the PCell and the sensing measurement result become available;

3> else if the purpose is not set to reportStrongestCells or reportStrongestCSI-RSs is included:

4> initiate the measurement reporting procedure, as specified in 5.5.5, when it has determined the
strongest cells on the associated frequency;

2> upon expiry of the periodical reporting timer for this measId:

3GPP
Release 15 195 3GPP TS 36.331 V15.4.0 (2018-12)

3> initiate the measurement reporting procedure, as specified in 5.5.5;

2> if the purpose is included and set to reportCGI:

3> if the UE acquired the information needed to set all fields of cgi-Info for the requested cell; or

3> if the UE detects that the requested NR cell is not transmitting SIB1:

4> include a measurement reporting entry within the VarMeasReportList for this measId;

4> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

4> stop timer T321;

4> initiate the measurement reporting procedure, as specified in 5.5.5;

2> upon expiry of the T321 for this measId:

3> include a measurement reporting entry within the VarMeasReportList for this measId;

3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0;

3> initiate the measurement reporting procedure, as specified in 5.5.5;

NOTE 2: The UE does not stop the periodical reporting with triggerType set to event or to periodical while the
corresponding measurement is not performed due to the PCell RSRP being equal to or better than s-
Measure or due to the measurement gap not being setup.

NOTE 3: If the UE is configured with DRX, the UE may delay the measurement reporting for event triggered and
periodical triggered measurements until the Active Time, which is defined in TS 36.321 [6].

5.5.4.2 Event A1 (Serving becomes better than threshold)

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A1-2, as specified below, is fulfilled;

1> for this measurement, consider the primary or secondary cell that is configured on the frequency indicated in the
associated measObjectEUTRA to be the serving cell;

Inequality A1-1 (Entering condition)

Ms  Hys  Thresh

Inequality A1-2 (Leaving condition)

Ms  Hys  Thresh

The variables in the formula are defined as follows:

Ms is the measurement result of the serving cell, not taking into account any offsets.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Thresh is the threshold parameter for this event (i.e. a1-Threshold as defined within reportConfigEUTRA for this
event).

Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

3GPP
Release 15 196 3GPP TS 36.331 V15.4.0 (2018-12)

5.5.4.3 Event A2 (Serving becomes worse than threshold)

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A2-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A2-2, as specified below, is fulfilled;

1> for this measurement, consider the primary or secondary cell that is configured on the frequency indicated in the
associated measObjectEUTRA to be the serving cell;

Inequality A2-1 (Entering condition)

Ms  Hys  Thresh

Inequality A2-2 (Leaving condition)

Ms  Hys  Thresh

The variables in the formula are defined as follows:

Ms is the measurement result of the serving cell, not taking into account any offsets.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Thresh is the threshold parameter for this event (i.e. a2-Threshold as defined within reportConfigEUTRA for this
event).

Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

5.5.4.4 Event A3 (Neighbour becomes offset better than PCell/ PSCell)

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled;

1> if usePSCell of the corresponding reportConfig is set to true:

2> use the PSCell for Mp, Ofp and Ocp;

1> else:

2> use the PCell for Mp, Ofp and Ocp;

NOTE The cell(s) that triggers the event is on the frequency indicated in the associated measObject which may
be different from the frequency used by the PCell/ PSCell.

Inequality A3-1 (Entering condition)

Mn  Ofn  Ocn  Hys  Mp  Ofp  Ocp  Off

Inequality A3-2 (Leaving condition)

Mn  Ofn  Ocn  Hys  Mp  Ofp  Ocp  Off

The variables in the formula are defined as follows:

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within
measObjectEUTRA corresponding to the frequency of the neighbour cell).

3GPP
Release 15 197 3GPP TS 36.331 V15.4.0 (2018-12)

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

Mp is the measurement result of the PCell/ PSCell, not taking into account any offsets.

Ofp is the frequency specific offset of the frequency of the PCell/ PSCell (i.e. offsetFreq as defined within
measObjectEUTRA corresponding to the frequency of the PCell/ PSCell).

Ocp is the cell specific offset of the PCell/ PSCell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the frequency of the PCell/ PSCell), and is set to zero if not configured for the PCell/ PSCell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigEUTRA for this event).

Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.

5.5.4.5 Event A4 (Neighbour becomes better than threshold)

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A4-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled;

Inequality A4-1 (Entering condition)

Mn  Ofn  Ocn  Hys  Thresh

Inequality A4-2 (Leaving condition)

Mn  Ofn  Ocn  Hys  Thresh

The variables in the formula are defined as follows:

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within
measObjectEUTRA corresponding to the frequency of the neighbour cell).

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Thresh is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigEUTRA for this
event).

Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Ofn, Ocn, Hys are expressed in dB.

Thresh is expressed in the same unit as Mn.

5.5.4.6 Event A5 (PCell/ PSCell becomes worse than threshold1 and neighbour
becomes better than threshold2)
The UE shall:

1> consider the entering condition for this event to be satisfied when both condition A5-1 and condition A5-2, as
specified below, are fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e. at least
one of the two, as specified below, is fulfilled;

3GPP
Release 15 198 3GPP TS 36.331 V15.4.0 (2018-12)

1> if usePSCell of the corresponding reportConfig is set to true:

2> use the PSCell for Mp;

1> else:

2> use the PCell for Mp;

NOTE: The cell(s) that triggers the event is on the frequency indicated in the associated measObject which may
be different from the frequency used by the PCell/ PSCell.

Inequality A5-1 (Entering condition 1)

Mp  Hys  Thresh1

Inequality A5-2 (Entering condition 2)

Mn  Ofn  Ocn  Hys  Thresh 2

Inequality A5-3 (Leaving condition 1)

Mp  Hys  Thresh1

Inequality A5-4 (Leaving condition 2)

Mn  Ofn  Ocn  Hys  Thresh 2

The variables in the formula are defined as follows:

Mp is the measurement result of the PCell/ PSCell, not taking into account any offsets.

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within
measObjectEUTRA corresponding to the frequency of the neighbour cell).

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigEUTRA for this
event).

Thresh2 is the threshold parameter for this event (i.e. a5-Threshold2 as defined within reportConfigEUTRA for this
event).

Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Ofn, Ocn, Hys are expressed in dB.

Thresh1 is expressed in the same unit as Mp.

Thresh2 is expressed in the same unit as Mn.

5.5.4.6a Event A6 (Neighbour becomes offset better than SCell)

The UE shall:

1> consider the entering condition for this event to be satisfied when condition A6-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition A6-2, as specified below, is fulfilled;

1> for this measurement, consider the (secondary) cell that is configured on the frequency indicated in the
associated measObjectEUTRA to be the serving cell;

3GPP
Release 15 199 3GPP TS 36.331 V15.4.0 (2018-12)

NOTE: The neighbour(s) is on the same frequency as the SCell i.e. both are on the frequency indicated in the
associated measObject.

Inequality A6-1 (Entering condition)

Mn  Ocn  Hys  Ms  Ocs  Off

Inequality A6-2 (Leaving condition)

Mn  Ocn  Hys  Ms  Ocs  Off

The variables in the formula are defined as follows:

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.

Ms is the measurement result of the serving cell, not taking into account any offsets.

Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the serving frequency), and is set to zero if not configured for the serving cell.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Off is the offset parameter for this event (i.e. a6-Offset as defined within reportConfigEUTRA for this event).

Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

Ocn, Ocs, Hys, Off are expressed in dB.

5.5.4.7 Event B1 (Inter RAT neighbour becomes better than threshold)

The UE shall:

1> for UTRA and CDMA2000, only trigger the event for cells included in the corresponding measurement object;

1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled;

Inequality B1-1 (Entering condition)

Mn  Ofn  Hys  Thresh

Inequality B1-2 (Leaving condition)

Mn  Ofn  Hys  Thresh

The variables in the formula are defined as follows:

Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets. For CDMA 2000
measurement result, pilotStrength is divided by -2.

Ofn is the frequency specific offset of the frequency of the inter-RAT neighbour cell (i.e. offsetFreq as defined
within the measObject corresponding to the frequency of the neighbour inter-RAT cell).

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).

Thresh is the threshold parameter for this event (i.e. b1-Threshold as defined within reportConfigInterRAT for this
event). For CDMA2000, b1-Threshold is divided by -2.

Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell.

Ofn, Hys are expressed in dB.

Thresh is expressed in the same unit as Mn.

3GPP
Release 15 200 3GPP TS 36.331 V15.4.0 (2018-12)

5.5.4.8 Event B2 (PCell becomes worse than threshold1 and inter RAT neighbour
becomes better than threshold2)
The UE shall:

1> for UTRA and CDMA2000, only trigger the event for cells included in the corresponding measurement object;

1> consider the entering condition for this event to be satisfied when both condition B2-1 and condition B2-2, as
specified below, are fulfilled;

1> consider the leaving condition for this event to be satisfied when condition B2-3 or condition B2-4, i.e. at least
one of the two, as specified below, is fulfilled;

Inequality B2-1 (Entering condition 1)

Mp  Hys  Thresh1

Inequality B2-2 (Entering condition 2)

Mn  Ofn  Hys  Thresh 2

Inequality B2-3 (Leaving condition 1)

Mp  Hys  Thresh1

Inequality B2-4 (Leaving condition 2)

Mn  Ofn  Hys  Thresh 2

The variables in the formula are defined as follows:

Mp is the measurement result of the PCell, not taking into account any offsets.

Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets. For CDMA2000
measurement result, pilotStrength is divided by -2.

Ofn is the frequency specific offset of the frequency of the inter-RAT neighbour cell (i.e. offsetFreq as defined
within the measObject corresponding to the frequency of the inter-RAT neighbour cell).

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).

Thresh1 is the threshold parameter for this event (i.e. b2-Threshold1 as defined within reportConfigInterRAT for
this event).

Thresh2 is the threshold parameter for this event (i.e. b2-Threshold2 as defined within reportConfigInterRAT for
this event). For CDMA2000, b2-Threshold2 is divided by -2.

Mp is expressed in dBm in case of RSRP, or in dB in case of RSRQ.

Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell.

Ofn, Hys are expressed in dB.

Thresh1 is expressed in the same unit as Mp.

Thresh2 is expressed in the same unit as Mn.

5.5.4.9 Event C1 (CSI-RS resource becomes better than threshold)

The UE shall:

1> consider the entering condition for this event to be satisfied when condition C1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition C1-2, as specified below, is fulfilled;

Inequality C1-1 (Entering condition)

3GPP
Release 15 201 3GPP TS 36.331 V15.4.0 (2018-12)

Mcr  Ocr  Hys  Thresh

Inequality C1-2 (Leaving condition)

Mcr  Ocr  Hys  Thresh

The variables in the formula are defined as follows:

Mcr is the measurement result of the CSI-RS resource, not taking into account any offsets.

Ocr is the CSI-RS specific offset (i.e. csi-RS-IndividualOffset as defined within measObjectEUTRA corresponding
to the frequency of the CSI-RS resource), and set to zero if not configured for the CSI-RS resource.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Thresh is the threshold parameter for this event (i.e. c1-Threshold as defined within reportConfigEUTRA for this
event).

Mcr, Thresh are expressed in dBm.

Ocr, Hys are expressed in dB.

5.5.4.10 Event C2 (CSI-RS resource becomes offset better than reference CSI-RS
resource)
The UE shall:

1> consider the entering condition for this event to be satisfied when condition C2-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition C2-2, as specified below, is fulfilled;

NOTE: The CSI-RS resource(s) that triggers the event is on the same frequency as the reference CSI-RS resource,
i.e. both are on the frequency indicated in the associated measObject.

Inequality C2-1 (Entering condition)

Mcr  Ocr  Hys  Mref  Oref  Off

Inequality C2-2 (Leaving condition)

Mcr  Ocr  Hys  Mref  Oref  Off

The variables in the formula are defined as follows:

Mcr is the measurement result of the CSI-RS resource, not taking into account any offsets.

Ocr is the CSI-RS specific offset of the CSI-RS resource (i.e. csi-RS-IndividualOffset as defined within
measObjectEUTRA corresponding to the frequency of the CSI-RS resource), and set to zero if not configured for
the CSI-RS resource.

Mref is the measurement result of the reference CSI-RS resource (i.e. c2-RefCSI-RS as defined within
reportConfigEUTRA for this event), not taking into account any offsets.

Oref is the CSI-RS specific offset of the reference CSI-RS resource (i.e. csi-RS-IndividualOffset as defined within
measObjectEUTRA corresponding to the frequency of the reference CSI-RS resource), and is set to zero if not
configured for the reference CSI-RS resource.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Off is the offset parameter for this event (i.e. c2-Offset as defined within reportConfigEUTRA for this event).

Mcr, Mref are expressed in dBm.

Ocr, Oref, Hys, Off are expressed in dB.

3GPP
Release 15 202 3GPP TS 36.331 V15.4.0 (2018-12)

5.5.4.11 Event W1 (WLAN becomes better than a threshold)

The UE shall:

1> consider the entering condition for this event to be satisfied when wlan-MobilitySet within VarWLAN-
MobilityConfig does not contain any entries and condition W1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition W1-2, as specified below, is fulfilled;

Inequality W1-1 (Entering condition)

Mn  Hys  Thresh

Inequality W1-2 (Leaving condition)

Mn  Hys  Thresh

The variables in the formula are defined as follows:

Mn is the measurement result of WLAN(s) configured in the measurement object, not taking into account any
offsets.

Hys is the hysteresis parameter for this event.

Thresh is the threshold parameter for this event (i.e. w1-Threshold as defined within reportConfigInterRAT for this
event).

Mn is expressed in dBm.

Hys is expressed in dB.

Thresh is expressed in the same unit as Mn.

5.5.4.12 Event W2 (All WLAN inside WLAN mobility set becomes worse than
threshold1 and a WLAN outside WLAN mobility set becomes better than
threshold2)
The UE shall:

1> consider the entering condition for this event to be satisfied when both conditions W2-1 and W2-2 as specified
below are fulfilled;

1> consider the leaving condition for this event to be satisfied when condition W2-3 or condition W2-4, i.e. at least
one of the two, as specified below is fulfilled;

Inequality W2-1 (Entering condition 1)

Ms  Hys  Thresh1

Inequality W2-2 (Entering condition 2)

Mn  Hys  Thresh 2

Inequality W2-3 (Leaving condition 1)

Ms  Hys  Thresh1

Inequality W2-4 (Leaving condition 2)

Mn  Hys  Thresh 2

The variables in the formula are defined as follows:

Ms is the measurement result of WLAN(s) which matches all WLAN identifiers of at least one entry within wlan-
MobilitySet in VarWLAN-MobilityConfig, not taking into account any offsets.

3GPP
Release 15 203 3GPP TS 36.331 V15.4.0 (2018-12)

Mn is the measurement result of WLAN(s) configured in the measurement object which does not match all WLAN
identifiers of any entry within wlan-MobilitySet in VarWLAN-MobilityConfig, not taking into account any
offsets.

Hys is the hysteresis parameter for this event.

Thresh1 is the threshold parameter for this event (i.e. w2-Threshold1 as defined within reportConfigInterRAT for
this event).

Thresh2 is the threshold parameter for this event (i.e. w2-Threshold2 as defined within reportConfigInterRAT for
this event).

Mn, Ms are expressed in dBm.

Hys is expressed in dB.

Thresh1 is expressed in the same unit as Ms.

Thresh2 is expressed in the same unit as Mn.

5.5.4.13 Event W3 (All WLAN inside WLAN mobility set becomes worse than a
threshold)
The UE shall:

1> consider the entering condition for this event to be satisfied when condition W3-1, as specified below, is
fulfilled;

1> consider the leaving condition for this event to be satisfied when condition W3-2, as specified below, is fulfilled;

Inequality W3-1 (Entering condition)

Ms  Hys  Thresh

Inequality W3-2 (Leaving condition)

Ms  Hys  Thresh

The variables in the formula are defined as follows:

Ms is the measurement result of WLAN(s) which matches all WLAN identifiers of at least one entry within wlan-
MobilitySet in VarWLAN-MobilityConfig, not taking into account any offsets.

Hys is the hysteresis parameter for this event.

Thresh is the threshold parameter for this event (i.e. w3-Threshold as defined within reportConfigInterRAT for this
event).

Ms is expressed in dBm.

Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

5.5.4.14 Event V1 (The channel busy ratio is above a threshold)

The UE shall:

1> consider the entering condition for this event to be satisfied when condition V1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition V1-2, as specified below, is fulfilled;

Inequality V1-1 (Entering condition)

Ms  Hys  Thresh

3GPP
Release 15 204 3GPP TS 36.331 V15.4.0 (2018-12)

Inequality V1-2 (Leaving condition)

Ms  Hys  Thresh

The variables in the formula are defined as follows:

Ms is the measurement result of channel busy ratio of the transmission resource pool, not taking into account any
offsets.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Thresh is the threshold parameter for this event (i.e. v1-Threshold as defined within ReportConfigEUTRA).

Ms is expressed in decimal from 0 to 1 in steps of 0.01.

Hys is expressed is in the same unit as Ms.

Thresh is expressed in the same unit as Ms.

5.5.4.15 Event V2 (The channel busy ratio is below a threshold)

The UE shall:

1> consider the entering condition for this event to be satisfied when condition V2-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition V2-2, as specified below, is fulfilled;

Inequality V2-1 (Entering condition)

Ms  Hys  Thresh

Inequality V2-2 (Leaving condition)

Ms  Hys  Thresh

The variables in the formula are defined as follows:

Ms is the measurement result of channel busy ratio of the transmission resource pool, not taking into account any
offsets.

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).

Thresh is the threshold parameter for this event (i.e. v2-Threshold as defined within ReportConfigEUTRA).

Ms is expressed in decimal from 0 to 1 in steps of 0.01.

Hys is expressed is in the same unit as Ms.

Thresh is expressed in the same unit as Ms.

5.5.4.16 Event H1 (The Aerial UE height is above a threshold)

The UE shall:

1> consider the entering condition for this event to be satisfied when condition H1-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition H1-2, as specified below, is fulfilled;

Inequality H1-1 (Entering condition)

Ms  Hys  Thresh  Offset

Inequality H1-2 (Leaving condition)

Ms  Hys  Thresh  Offset

3GPP
Release 15 205 3GPP TS 36.331 V15.4.0 (2018-12)

The variables in the formula are defined as follows:

Ms is the Aerial UE height, not taking into account any offsets.

Hys is the hysteresis parameter (i.e. h1-Hysteresis as defined within ReportConfigEUTRA) for this event.

Thresh is the reference threshold parameter for this event given in MeasConfig(i.e. heightThreshRef as defined
within MeasConfig).

Offset is the offset value to heightThreshRef to obtain the absolute threshold for this event. (i.e. h1-ThresholdOffset
as defined within ReportConfigEUTRA)

Ms is expressed in meters.

Thresh is expressed in the same unit as Ms.

5.5.4.17 Event H2 (The Aerial UE height is below a threshold)

The UE shall:

1> consider the entering condition for this event to be satisfied when condition H2-1, as specified below, is fulfilled;

1> consider the leaving condition for this event to be satisfied when condition H2-2, as specified below, is fulfilled;

Inequality H2-1 (Entering condition)

Ms  Hys  Thresh  Offset

Inequality H2-2 (Leaving condition)

Ms  Hys  Thresh  Offset

The variables in the formula are defined as follows:

Ms is the Aerial UE height, not taking into account any offsets.

Hys is the hysteresis parameter (i.e. h2-Hysteresis as defined within ReportConfigEUTRA) for this event.

Thresh is the reference threshold parameter for this event given in MeasConfig(i.e. heightThreshRef as defined
within MeasConfig).

Offset is the offset value to heightThreshRef to obtain the absolute threshold for this event. (i.e. h2-ThresholdOffset
as defined within ReportConfigEUTRA)

Ms is expressed in meters.

Thresh is expressed in the same unit as Ms.

5.5.5 Measurement reporting

5.5.5.1 General

UE EUTRAN

MeasurementReport

Figure 5.5.5.1-1: Measurement reporting

The purpose of this procedure is to transfer measurement results from the UE to E-UTRAN. The UE shall initiate this
procedure only after successful security activation.

3GPP
Release 15 206 3GPP TS 36.331 V15.4.0 (2018-12)

For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within
the MeasurementReport message as follows:

1> set the measId to the measurement identity that triggered the measurement reporting;

1> set the measResultPCell to include the quantities of the PCell;

1> set the measResultServFreqList to include for each E-UTRA SCell that is configured, if any, within
measResultSCell the quantities of the concerned SCell, if available according to performance requirements in TS
36.133 [16], except if purpose for the reportConfig associated with the measId that triggered the measurement
reporting is set to reportLocation;

1> if the reportConfig associated with the measId that triggered the measurement reporting includes
reportAddNeighMeas:

2> for each E-UTRA serving frequency for which measObjectId is referenced in the measIdList, other than the
frequency corresponding with the measId that triggered the measurement reporting:

3> set the measResultServFreqList to include within measResultBestNeighCell the physCellId and the
quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

1> if the triggerType is set to event; and if the corresponding measObject concerns NR; and if eventId is set to
eventB1-NR or eventB2-NR; or

1> if the triggerType is set to event; and if eventId is set to eventA3 or eventA4 or eventA5:

2> if purpose for the reportConfig or reportConfigInterRAT associated with the measId that triggered the
measurement reporting is set to a value other than reportLocation:

3> set the measResultServFreqListNR to include for each NR serving frequency that the UE is configured to
measure according to TS 38.331 [82], if any, the following:

4> set measResultSCell to include the available results of the NR serving cell, as specified in 5.5.5.2;

4> if the reportConfig associated with the measId that triggered the measurement reporting includes
reportAddNeighMeas:

5> set measResultBestNeighCell to include the available results, as specified in 5.5.5.2, of the best
non-serving cell;

3> for each (serving or neighbouring) cell for which the UE reports results according to the previous,
additionally include available beam results according to the following:

4> if maxReportRS-Index is configured, set measResultRS-IndexList to include available results, as

specified in 5.5.5.2, of up to maxReportRS-Index beams, ordered based on the quantity determined as
specified in 5.5.5.3;

1> if there is at least one applicable neighbouring cell to report:

2> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with
the following:

3> if the triggerType is set to event:

4> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this
measId;

3> else:

4> include the applicable cells for which the new measurement results became available since the last
periodical reporting or since the measurement was initiated or reset;

NOTE 1: The reliability of the report (i.e. the certainty it contains the strongest cells on the concerned frequency)
depends on the measurement configuration i.e. the reportInterval. The related performance requirements
are specified in TS 36.133 [16].

3GPP
Release 15 207 3GPP TS 36.331 V15.4.0 (2018-12)

3> for each cell that is included in the measResultNeighCells, include the physCellId;

3> if the triggerType is set to event; or the purpose is set to reportStrongestCells or to

reportStrongestCellsForSON:

4> for each included cell, include the layer 3 filtered measured results in accordance with the
reportConfig for this measId, ordered as follows:

5> if the measObject associated with this measId concerns E-UTRA:

6> set the measResult to include the quantity(ies) indicated in the reportQuantity within the
concerned reportConfig;

6> sort the included cells in order of decreasing triggerQuantity, i.e. the best cell is included first;

5> if the measObject associated with this measId concerns NR:

6> set the measResultCell to include the quantity(ies) indicated in the reportQuantityCellNR
within the concerned reportConfig;

6> if maxReportRS-Index and reportQuantityRS-IndexNR are configured, set measResultRS-

IndexList to include results of the best beam and the beams whose quantity is above threshRS-
Index defined in the VarMeasConfig for the corresponding measObject, up to maxReportRS-
Index beams in total:

7> order beams based on the sorting quantity determined as specified in 5.5.5.3;

7> for each included beam:

8> include ssbIndex;

8> if reportRS-IndexResultsNR is configured, for each quantity indicated, include the

corresponding measurement result in measResultNeighCells;

6> sort the included cells in order of decreasing sorting quantity determined as specified in
5.5.5.3;

5> if the measObject associated with this measId concerns UTRA FDD and if ReportConfigInterRAT
includes the reportQuantityUTRA-FDD:

6> set the measResult to include the quantities indicated by the reportQuantityUTRA-FDD in
order of decreasing measQuantityUTRA-FDD within the quantityConfig, i.e. the best cell is
included first;

5> if the measObject associated with this measId concerns UTRA FDD and if ReportConfigInterRAT
does not include the reportQuantityUTRA-FDD; or

5> if the measObject associated with this measId concerns UTRA TDD, GERAN or CDMA2000:

6> set the measResult to the quantity as configured for the concerned RAT within the
quantityConfig in order of either decreasing quantity for UTRA and GERAN or increasing
quantity for CDMA2000 pilotStrength, i.e. the best cell is included first;

3> else if the purpose is set to reportCGI and the corresponding measObject concerns a RAT other than NR:

4> if the mandatory present fields of the cgi-Info for the cell indicated by the cellForWhichToReportCGI
in the associated measObject have been obtained:

5> if the includeMultiBandInfo is configured:

6> include the freqBandIndicator;

6> if the cell broadcasts the multiBandInfoList, include the multiBandInfoList;

6> if the cell broadcasts the freqBandIndicatorPriority, include the freqBandIndicatorPriority;

5> if the cell broadcasts a CSG identity:

3GPP
Release 15 208 3GPP TS 36.331 V15.4.0 (2018-12)

6> include the csg-Identity;

6> include the csg-MemberStatus and set it to member if the cell is a CSG member cell;

5> if the si-RequestForHO is configured within the reportConfig associated with this measId:

6> include the cgi-Info containing all the fields other than the plmn-IdentityList that have been
successfully acquired;

6> include, within the cgi-Info, the field plmn-IdentityList in accordance with the following:

7> if the cell is a CSG member cell, determine the subset of the PLMN identities, starting from
the second entry of PLMN identities in the broadcast information, that meet the following
conditions:

a) equal to the RPLMN or an EPLMN; and

b) the CSG whitelist of the UE includes an entry comprising of the concerned PLMN
identity and the CSG identity broadcast by the cell;

7> if the subset of PLMN identities determined according to the previous includes at least one
PLMN identity, include the plmn-IdentityList and set it to include this subset of the PLMN
identities;

7> if the cell is a CSG member cell, include the primaryPLMN-Suitable if the primary PLMN
meets conditions a) and b) specified above;

7> if the cell does not broadcast csg-Identity and the UE is capable of reporting the plmn-
IdentityList from cells not broadcasting csg-Identity:

8> include in the plmn-IdentityList the list of identities starting from the second entry of
PLMN identities in the broadcast information;

5> else:

6> include the cgi-Info containing all the fields that have been successfully acquired and in
accordance with the following:

7> include in the plmn-IdentityList the list of identities starting from the second entry of
PLMN Identities in the broadcast information;

4> if the cellAccessRelatedInfoList-5GC has been acquired:

5> include cgi-Info-5GC;

NOTE 1a: The UE may include the cgi-Info-5GC even when the N1 mode is disabled.

3> else if the purpose is set to reportCGI and the corresponding measObject concerns NR RAT:

4> if the Cell information of cgi-Info for the cell indicated by the cellForWhichToReportCGI in the
associated measObject has been obtained:

5> include plmn-IdentityInfoList including plmn-IdentityList, trackingAreaCode (if available), ran-

AreaCode (if available) and cellIdentity for each entry of the plmn-IdentityInfoList;

5> include frequencyBandList if broadcasted;

4> else if MIB associated with the concerned measObject indicates that SIB1 is not broadcast:

5> include the noSIB1 field;

1> for the cells included according to the previous (i.e. covering the PCell, the SCells, the best non-serving cells on
serving frequencies as well as neighbouring EUTRA cells) include results according to the extended RSRQ if
corresponding results are available according to the associated performance requirements defined in TS 36.133
[16];

1> if there is at least one applicable CSI-RS resource to report:

3GPP
Release 15 209 3GPP TS 36.331 V15.4.0 (2018-12)

2> set the measResultCSI-RS-List to include the best CSI-RS resources up to maxReportCells in accordance with
the following:

3> if the triggerType is set to event:

4> include the CSI-RS resources included in the csi-RS-TriggeredList as defined within the
VarMeasReportList for this measId;

3> else:

4> include the applicable CSI-RS resources for which the new measurement results became available
since the last periodical reporting or since the measurement was initiated or reset;

NOTE 2: The reliability of the report (i.e. the certainty it contains the strongest CSI-RS resources on the concerned
frequency) depends on the measurement configuration i.e. the reportInterval. The related performance
requirements are specified in TS 36.133 [16].

3> for each CSI-RS resource that is included in the measResultCSI-RS-List:

4> include the measCSI-RS-Id;

4> include the layer 3 filtered measured results in accordance with the reportConfig for this measId,
ordered as follow:

5> set the csi-RSRP-Result to include the quantity indicated in the reportQuantity within the
concerned reportConfig in order of decreasing triggerQuantityCSI-RS, i.e. the best CSI-RS
resource is included first;

4> if reportCRS-Meas is included within the associated reportConfig, and the cell indicated by
physCellId of this CSI-RS resource is not a serving cell:

5> set the measResultNeighCells to include the cell indicated by physCellId of this CSI-RS resource,
and include the physCellId;

5> set the rsrpResult to include the RSRP of the concerned cell, if available according to performance
requirements in TS 36.133 [16];

5> set the rsrqResult to include the RSRQ of the concerned cell, if available according to performance
requirements in TS 36.133 [16];

1> if the ue-RxTxTimeDiffPeriodical is configured within the corresponding reportConfig for this measId;

2> set the ue-RxTxTimeDiffResult to the measurement result provided by lower layers;

2> set the currentSFN;

1> if the measRSSI-ReportConfig is configured within the corresponding reportConfig for this measId:

2> set the rssi-Result to the average of sample value(s) provided by lower layers in the reportInterval;

2> set the channelOccupancy to the rounded percentage of sample values which are beyond to the
channelOccupancyThreshold within all the sample values in the reportInterval;

1> if uplink PDCP delay results are available:

2> set the ul-PDCP-DelayResultList to include the uplink PDCP delay results available;

1> if the includeLocationInfo is configured in the corresponding reportConfig for this measId or if purpose for the
reportConfig associated with the measId that triggered the measurement reporting is set to reportLocation; and
detailed location information that has not been reported is available, set the content of the locationInfo as
follows:

2> include the locationCoordinates;

2> if available, include the gnss-TOD-msec, except if purpose for the reportConfig associated with the measId
that triggered the measurement reporting is set to reportLocation;

3GPP
Release 15 210 3GPP TS 36.331 V15.4.0 (2018-12)

2> include the verticalVelocityInfo, if available;

1> if the includeWLAN-Meas is configured in the corresponding reportConfig for this measId, set the measResults
as follows:

2> if available, include the logMeasResultListWLAN, in order of decreasing RSSI for WLAN APs;

1> if the includeBT-Meas is configured in the corresponding reportConfig for this measId, set the measResults as
follows:

2> if available, include the logMeasResultListBT, in order of decreasing RSSI for Bluetooth beacons;

1> if the reportSSTD-Meas is set to true or pSCell within the corresponding reportConfig for this measId:

2> set the measResultSSTD to the measurement results provided by lower layers;

1> if the reportSFTD-Meas is set to neighborCells or pSCell within the corresponding reportConfigInterRAT for
this measId, for each applicable cell for which results are available:

2> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers;

2> if the reportQuantityCellNR is set to ss-rsrp within the corresponding reportConfigInterRAT for this measId:

3> include rsrpResult set to the RSRP of the concerned cell;

1> if there is at least one applicable transmission resource pool to report:

2> set the measResultListCBR to include the CBR measurement results in accordance with the following:

3> if the triggerType is set to event:

4> include the transmission resource pools included in the poolsTriggeredList as defined within the
VarMeasReportList for this measId;

3> else:

4> include the applicable transmission resource pools for which the new measurement results became
available since the last periodical reporting or since the measurement was initiated or reset;

3> for each transmission resource pool to be reported:

4> set the poolIdentity to the poolReportId of this transmission resource pool;

4> if adjacencyPSCCH-PSSCH is set to TRUE for this transmission resource pool:

5> set the cbr-PSSCH to the CBR measurement result on PSSCH and PSCCH of this transmission
resource pool provided by lower layers;

4> else:

5> set the cbr-PSSCH to the CBR measurement result on PSSCH of this transmission resource pool
provided by lower layers if available;

5> set the cbr-PSCCH to the CBR measurement result on PSCCH of this transmission resource pool
provided by lower layers if available;

2> set the measResultSensing to include the sensing measurement results in accordance with the following:

3> include the applicable transmission resource pools for which the new measurement results became
available since the last periodical reporting or since the measurement was initiated or reset;

3> for each transmission resource pool to be reported:

4> set the sensingResult to the sensing measurement results provided by the lower layers;

1> if the triggerType is set to event; and if eventId is set to eventH1 or eventH2:

2> set the heightUE to include the altitude of the UE;

3GPP
Release 15 211 3GPP TS 36.331 V15.4.0 (2018-12)

1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1;

1> stop the periodical reporting timer, if running;

1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the
reportAmount as defined within the corresponding reportConfig for this measId:

2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding
reportConfig for this measId;

1> else:

2> if the triggerType is set to periodical:

3> remove the entry within the VarMeasReportList for this measId;

3> remove this measId from the measIdList within VarMeasConfig;

1> if the measured results are for CDMA2000 HRPD:

2> set the preRegistrationStatusHRPD to the UE's CDMA2000 upper layer's HRPD preRegistrationStatus;

1> if the measured results are for CDMA2000 1xRTT:

2> set the preRegistrationStatusHRPD to FALSE;

1> if the measured results are for WLAN:

2> set the measResultListWLAN to include the quantities within the quantityConfigWLAN for up to
maxReportCells WLAN(s), determined according to the following:

3> include WLAN the UE is connected to, if any;

3> if reportAnyWLAN is set to TRUE:

4> consider WLAN with any WLAN identifiers to be applicable for measurement reporting;

3> else:

4> consider only WLANs which do not match all WLAN identifiers of any entry within wlan-
MobilitySet in VarWLAN-MobilityConfig to be applicable for measurement reporting;

3> include applicable WLAN in order of decreasing WLAN RSSI, i.e. the best WLAN is included first;

2> for each included WLAN:

3> set wlan-Identifiers to include all WLAN identifiers that can be acquired for the WLAN measured;

3> set connectedWLAN to TRUE if the UE is connected to the WLAN measured;

3> if reportQuantityWLAN exists within the ReportConfigInterRAT within the VarMeasConfig for this
measId:

4> if bandRequestWLAN is set to TRUE:

5> set bandWLAN to include WLAN band of the WLAN measured;

4> if carrierInfoRequestWLAN is set to TRUE:

5> set carrierInfoWLAN to include WLAN carrier information of the WLAN measured if it can be
acquired;

4> if availableAdmissionCapacityRequestWLAN is set to TRUE:

5> set the measResult to include avaiableAdmissionCapacityWLAN if it can be acquired;

4> if backhaulDL-BandwidthRequestWLAN is set to TRUE:

3GPP
Release 15 212 3GPP TS 36.331 V15.4.0 (2018-12)

5> set the measResult to include backhaulDL-BandwidthWLAN if it can be acquired;

4> if backhaulUL-BandwidthRequestWLAN is set to TRUE:

5> set the measResult to include backhaulUL-BandwidthWLAN if it can be acquired;

4> if channelUtilizationRequestWLAN is set to TRUE:

5> set the measResult to include channelUtilizationWLAN if it can be acquired;

4> if stationCountRequestWLAN is set to TRUE:

5> set the measResult to include stationCountWLAN if it can be acquired;

1> submit the MeasurementReport message to lower layers for transmission, upon which the procedure ends;

5.5.5.2 Determination of available NR measurement results

When configured to report measurement results of the serving and the best neighbouring cells on NR serving
frequencies, the UE shall consider NR measurement results to be available as follows:

1> only SSB based results are available and only if configured to measure these for the concerned serving
frequency;

1> for the serving cell:

2> include cell quantities RSRP and RSRQ while SINR is included if the UE is configured to measure this
quantity on an NR frequency, possibly different from the concerned serving frequency, but only if configured
by NR measConfig:

2> include beam results and beam quantities if the UE is configured to measure these on an NR frequency,
possibly different from the concerned serving frequency, but only if configured by NR measConfig;

1> for a neighbouring cell:

2> include cell quantities, beam results and beam quantities if the UE is configured to measure these on an NR
frequency, possibly different from the concerned serving frequency, but only if configured by NR
measConfig.

1> filter available results according to the applicable field in NR quantityConfig:

5.5.5.3 Selection of NR sorting quality

When configured to report the best cells or beams, the UE shall determine the quantity that is used to order and select as
follows:

1> for cells on the frequency associated with the measId that triggered the measurement reporting, if the
reportTrigger is set to event, consider the quantity used in bN-ThresholdYNR to be the sorting quantity;

1> for other cases, determine the sorting quantity as follows:

2> consider the following quantities as candidate sorting quantities:

3> for cells on the frequency associated with the measId that triggered the measurement reporting (for a
triggerType set to periodical):

4> the quantities defined by reportQuantityCellNR, when used for sorting cells;

4> the quantities defined by reportQuantityRS-IndexNR, when used for sorting beams;

3> for cells, serving or non-serving (i.e. within reportAddNeighMeas), on NR serving frequencies other than
the one associated with the measId triggering reporting:

4> the available quantities of available NR measurement results as specified in 5.5.5.2;

2> if there is a single candidate sorting quantity;

3GPP
Release 15 213 3GPP TS 36.331 V15.4.0 (2018-12)

3> consider the concerned quantity to be the sorting quantity;

2> else:

3> if RSRP is one of the candidate sorting quantities;

4> consider RSRP to be the sorting quantity;

3> else:

4> consider RSRQ to be the sorting quantity;

5.5.6 Measurement related actions

5.5.6.1 Actions upon handover and re-establishment

E-UTRAN applies the handover procedure as follows:

- when performing the handover procedure, as specified in 5.3.5.4, ensure that a measObjectId corresponding to
each handover target serving frequency is configured as a result of the procedures described in this sub-clause
and in 5.3.5.4;

- when changing the band while the physical frequency remains unchanged, E-UTRAN releases the measObject
corresponding to the source frequency and adds a measObject corresponding to the target frequency (i.e. it does
not reconfigure the measObject);

E-UTRAN applies the re-establishment procedure as follows:

- when performing the connection re-establishment procedure, as specified in 5.3.7, ensure that a measObjectId
corresponding each target serving frequency is configured as a result of the procedure described in this sub-
clause and the subsequent connection reconfiguration procedure immediately following the re-establishment
procedure;

- in the first reconfiguration following the re-establishment when changing the band while the physical frequency
remains unchanged, E-UTRAN releases the measObject corresponding to the source frequency and adds a
measObject corresponding to the target frequency (i.e. it does not reconfigure the measObject);

The UE shall:

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

2> if the triggerType is set to periodical:

3> remove this measId from the measIdList within VarMeasConfig:

1> if the procedure was triggered due to a handover or successful re-establishment and the procedure involves a
change of primary frequency, update the measId values in the measIdList within VarMeasConfig as follows:

2> if a measObjectId value corresponding to the target primary frequency exists in the measObjectList within
VarMeasConfig:

3> for each measId value in the measIdList:

4> if the measId value is linked to the measObjectId value corresponding to the source primary
frequency:

5> link this measId value to the measObjectId value corresponding to the target primary frequency;

4> else if the measId value is linked to the measObjectId value corresponding to the target primary
frequency:

5> link this measId value to the measObjectId value corresponding to the source primary frequency;

2> else:

3GPP
Release 15 214 3GPP TS 36.331 V15.4.0 (2018-12)

3> remove all measId values that are linked to the measObjectId value corresponding to the source primary
frequency;

1> remove all measurement reporting entries within VarMeasReportList;

1> stop the periodical reporting timer or timer T321, whichever one is running, as well as associated information
(e.g. timeToTrigger) for all measId;

1> release the measurement gaps, if activated;

NOTE: If the UE requires measurement gaps to perform inter-frequency or inter-RAT measurements, the UE
resumes the inter-frequency and inter-RAT measurements after the E-UTRAN has setup the measurement
gaps.

5.5.6.2 Speed dependant scaling of measurement related parameters

The UE shall adjust the value of the following parameter configured by the E-UTRAN depending on the UE speed:
timeToTrigger. The UE shall apply 3 different levels, which are selected as follows:

The UE shall:

1> perform mobility state detection using the mobility state detection as specified in TS 36.304 [4] with the
following modifications:

2> counting handovers instead of cell reselections;

2> applying the parameter applicable for RRC_CONNECTED as included in speedStatePars within
VarMeasConfig;

1> if high mobility state is detected:

2> use the timeToTrigger value multiplied by sf-High within VarMeasConfig;

1> else if medium mobility state is detected:

2> use the timeToTrigger value multiplied by sf-Medium within VarMeasConfig;

1> else:

2> no scaling is applied;

5.5.7 Inter-frequency RSTD measurement indication

5.5.7.1 General

UE EUTRAN

InterFreqRSTDMeasurementIndication

Figure 5.5.7.1-1: Inter-frequency RSTD measurement indication

The purpose of this procedure is to indicate to the network that the UE is going to start/stop OTDOA inter-frequency
RSTD measurements which require measurement gaps as specified in TS 36.133 [16], clause 8.1.2.6. The procedure is
also used to indicate to the network that the UE is going to start/stop OTDOA intra-frequency RSTD measurements
which require measurement gaps. This procedure is also used to indicate to the network the measurement gap that the
category M1 or M2 UE prefers to perform RSTD measurements with dense PRS configuration, as specified in TS
36.133 [16], Table 8.1.2.1-3.

3GPP
Release 15 215 3GPP TS 36.331 V15.4.0 (2018-12)

NOTE: It is a network decision to configure the measurement gap.

5.5.7.2 Initiation
The UE shall:

1> if and only if upper layers indicate to start performing inter-frequency RSTD measurements and the UE requires
measurement gaps for these measurements while measurement gaps are either not configured or not sufficient:

2> initiate the procedure to indicate start;

NOTE 1: The UE verifies the measurement gap situation only upon receiving the indication from upper layers. If at
this point in time sufficient gaps are available, the UE does not initiate the procedure. Unless it receives a
new indication from upper layers, the UE is only allowed to further repeat the procedure in the same
PCell once per frequency if the provided measurement gaps are insufficient.

1> if and only if upper layers indicate to stop performing inter-frequency RSTD measurements:

2> initiate the procedure to indicate stop;

NOTE 2: The UE may initiate the procedure to indicate stop even if it did not previously initiate the procedure to
indicate start.

5.5.7.3 Actions related to transmission of InterFreqRSTDMeasurementIndication

message
The UE shall set the contents of InterFreqRSTDMeasurementIndication message as follows:

1> if the procedure is initiated to indicate start or stop of inter-frequency RSTD measurements:

2> set the rstd-InterFreqIndication as follows:

3> if the procedure is initiated to indicate start of inter-frequency RSTD measurements:

4> set the rstd-InterFreqInfoList according to the information received from upper layers;

4> for category M1 or M2 UE, if the procedure is initated to indicate the measurement gap that the UE
prefers to perform RSTD measurements with dense PRS configuration:

5> set the measPRS-Offset-r15 according to the UE preference;

3> else if the procedure is initiated to indicate stop of inter-frequency RSTD measurements:

4> set the rstd-InterFreqIndication to the value stop;

1> else:

2> set the rstd-InterFreqIndication as follows:

3> if the procedure is initiated to indicate start of intra-frequency RSTD measurements:

4> set the carrierFreq in the rstd-InterFreqInfoList to the carrier frequency of the serving cell;

4> for category M1 or M2 UE, if the procedure is initated to indicate the measurement gap that the UE
prefers to perform RSTD measurements with dense PRS configuration:

5> set the measPRS-Offset-r15 according to the UE preference;

3> else if the procedure is initiated to indicate stop of intra-frequency RSTD measurements:

4> set the rstd-InterFreqIndication to the value stop;

1> submit the InterFreqRSTDMeasurementIndication message to lower layers for transmission, upon which the
procedure ends;

3GPP
Release 15 216 3GPP TS 36.331 V15.4.0 (2018-12)

5.6 Other
5.6.0 General
For NB-IoT, only a subset of the procedures described in this sub-clause apply.

Table 5.6.0-1 specifies the procedures that are applicable to NB-IoT. All other procedures are not applicable to NB-IoT;
this is not further stated in the corresponding procedures.

Table 5.6.0-1: "Other″ Procedures applicable to a NB-IoT UE

Sub-clause Procedures
5.6.1 DL information transfer
5.6.2 UL information transfer
5.6.3 UE Capability transfer

5.6.1 DL information transfer

5.6.1.1 General

UE EUTRAN

DLInformationTransfer

Figure 5.6.1.1-1: DL information transfer

The purpose of this procedure is to transfer NAS, (tunnelled) non-3GPP dedicated information or time reference
information from E-UTRAN to a UE in RRC_CONNECTED.

5.6.1.2 Initiation
E-UTRAN initiates the DL information transfer procedure whenever there is a need to transfer NAS, non-3GPP
dedicated information or time reference information. E-UTRAN initiates the DL information transfer procedure by
sending the DLInformationTransfer message.

5.6.1.3 Reception of the DLInformationTransfer by the UE

Upon receiving DLInformationTransfer message, the UE shall:

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

1> if the dedicatedInfoType is present and set to dedicatedInfoNAS:

2> forward the dedicatedInfoNAS to the NAS upper layers.

1> if the dedicatedInfoType is present and set to dedicatedInfoCDMA2000-1XRTT or to dedicatedInfoCDMA2000-

HRPD:

2> forward the dedicatedInfoCDMA2000 to the CDMA2000 upper layers;

1> if timeReferenceInfo is included:

2> calculate the time reference based on the included time, timeInfoType and referenceSFN in
timeReferenceInfo;

3GPP
Release 15 217 3GPP TS 36.331 V15.4.0 (2018-12)

2> calculate the inaccuracy of the time reference based on the uncertainty and other implementation-related
inaccuracies, if uncertainty is included in timeReferenceInfo;

2> inform upper layers of the time reference and, if uncertainty is included in timeReferenceInfo, of the
inaccuracy of the time reference.

5.6.2 UL information transfer

5.6.2.1 General

UE EUTRAN

ULInformationTransfer

Figure 5.6.2.1-1: UL information transfer

The purpose of this procedure is to transfer NAS or (tunnelled) non-3GPP dedicated information from the UE to E-
UTRAN.

5.6.2.2 Initiation
A UE in RRC_CONNECTED initiates the UL information transfer procedure whenever there is a need to transfer NAS
or non-3GPP dedicated information, except at RRC connection establishment or resume in which case the NAS
information is piggybacked to the RRCConnectionSetupComplete or RRCConnectionResumeComplete message
correspondingly. The UE initiates the UL information transfer procedure by sending the ULInformationTransfer
message. When CDMA2000 information has to be transferred, the UE shall initiate the procedure only if SRB2 is
established.

5.6.2.3 Actions related to transmission of ULInformationTransfer message

The UE shall set the contents of the ULInformationTransfer message as follows:

1> if there is a need to transfer NAS information:

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

3> set the dedicatedInfoNAS to include the information received from upper layers;

2> else, set the dedicatedInfoType to include the dedicatedInfoNAS;

1> if there is a need to transfer CDMA2000 1XRTT information:

2> set the dedicatedInfoType to include the dedicatedInfoCDMA2000-1XRTT;

1> if there is a need to transfer CDMA2000 HRPD information:

2> set the dedicatedInfoType to include the dedicatedInfoCDMA2000-HRPD;

1> upon RRC connection establishment, if UE supports the Control Plane CIoT EPS optimisation and UE does not
need UL gaps during continuous uplink transmission:

2> configure lower layers to stop using UL gaps during continuous uplink transmission in FDD for
ULInformationTransfer message and subsequent uplink transmission in RRC_CONNECTED except for UL
transmissions as specified in TS 36.211 [21];

1> submit the ULInformationTransfer message to lower layers for transmission, upon which the procedure ends;

3GPP
Release 15 218 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.2.4 Failure to deliver ULInformationTransfer message

The UE shall:

1> if the UE is a NB-IoT UE, AS security is not started and radio link failure occurs before the successful delivery
of ULInformationTransfer messages has been confirmed by lower layers; or

1> if mobility (i.e. handover, RRC connection re-establishment) occurs before the successful delivery of
ULInformationTransfer messages has been confirmed by lower layers:

2> inform upper layers about the possible failure to deliver the information contained in the concerned
ULInformationTransfer messages;

5.6.2a UL information transfer for MR-DC

5.6.2a.1 General

UE EUTRAN

ULInformationTransferMRDC

Figure 5.6.2a.1-1: UL information transfer MR-DC

The purpose of this procedure is to transfer from the UE to E-UTRAN MR-DC dedicated information e.g. the NR RRC
Measurement Report message.

5.6.2a.2 Initiation
A UE in RRC_CONNECTED initiates the UL information transfer procedure whenever there is a need to transfer MR
DC dedicated information as specified in TS 38.331 [82]. I.e. the procedure is not used during an RRC connection
reconfiguration involving NR connection reconfiguration, in which case the MR DC information is piggybacked to the
RRCConnectionReconfigurationComplete message.

5.6.2a.3 Actions related to transmission of ULInformationTransferMRDC message

The UE shall set the contents of the ULInformationTransferMRDC message as follows:

1> if there is a need to transfer MR DC dedicated information:

2> set the ul-DCCH-MessageNR to include the MR DC dedicated information to be transferred;

1> submit the ULInformationTransferMRDC message to lower layers for transmission, upon which the procedure
ends;

3GPP
Release 15 219 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.2a.4 Void

5.6.3 UE capability transfer

5.6.3.1 General

UE EUTRAN

UECapabilityEnquiry

UECapabilityInformation

Figure 5.6.3.1-1: UE capability transfer

The purpose of this procedure is to transfer UE radio access capability information from the UE to E-UTRAN.

If the UE has changed its E-UTRAN radio access capabilities, the UE shall request higher layers to initiate the
necessary NAS procedures (see TS 23.401 [41]) that would result in the update of UE radio access capabilities using a
new RRC connection.

NOTE: Change of the UE's GERAN UE radio capabilities in RRC_IDLE is supported by use of Tracking Area
Update.

5.6.3.2 Initiation
E-UTRAN initiates the procedure to a UE in RRC_CONNECTED when it needs (additional) UE radio access
capability information.

5.6.3.3 Reception of the UECapabilityEnquiry by the UE

The UE shall:

1> for NB-IoT, set the contents of UECapabilityInformation message as follows:

2> include the UE Radio Access Capability Parameters within the ue-Capability;

2> include ue-RadioPagingInfo;

2> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure
ends;

1> else, set the contents of UECapabilityInformation message as follows:

2> if the ue-CapabilityRequest includes eutra:

3> include the UE-EUTRA-Capability within a ue-CapabilityRAT-Container and with the rat-Type set to
eutra;

3> if the UE supports FDD and TDD:

4> set all fields of UECapabilityInformation, except field fdd-Add-UE-EUTRA-Capabilities and tdd-Add-
UE-EUTRA-Capabilities (including their sub-fields), to include the values applicable for both FDD
and TDD (i.e. functionality supported by both modes);

4> if (some of) the UE capability fields have a different value for FDD and TDD:

3GPP
Release 15 220 3GPP TS 36.331 V15.4.0 (2018-12)

5> if for FDD, the UE supports additional functionality compared to what is indicated by the previous
fields of UECapabilityInformation:

6> include field fdd-Add-UE-EUTRA-Capabilities and set it to include fields reflecting the
additional functionality applicable for FDD;

5> if for TDD, the UE supports additional functionality compared to what is indicated by the previous
fields of UECapabilityInformation:

6> include field tdd-Add-UE-EUTRA-Capabilities and set it to include fields reflecting the
additional functionality applicable for TDD;

NOTE 1: The UE includes fields of XDD-Add-UE-EUTRA-Capabilities in accordance with the following:

- The field is included only if one or more of its sub-fields (or bits in the feature group indicators string)
has a value that is different compared to the value signalled elsewhere within UE-EUTRA-Capability;
(this value signalled elsewhere is also referred to as the Common value, that is supported for both
XDD modes)
- For the fields that are included in XDD-Add-UE-EUTRA-Capabilities, the UE sets:
- the sub-fields (or bits in the feature group indicators string) that are not allowed to be different to
the same value as the Common value;
- the sub-fields (or bits in the feature group indicators string) that are allowed to be different to a
value indicating at least the same functionality as indicated by the Common value;

3> else (UE supports single xDD mode):

4> set all fields of UECapabilityInformation, except field fdd-Add-UE-EUTRA-Capabilities and tdd-Add-
UE-EUTRA-Capabilities (including their sub-fields), to include the values applicable for the xDD
mode supported by the UE;

3> compile a list of band combinations, candidate for inclusion in the UECapabilityInformation message,
comprising of band combinations supported by the UE according to the following priority order (i.e.
listed in order of decreasing priority):

4> include all non-CA bands, regardless of whether UE supports carrier aggregation, only:

- if the UE includes ue-Category-v1020 (i.e. indicating category 6 to 8); or

- if for at least one of the non-CA bands, the UE supports more MIMO layers with TM9 and
TM10 than implied by the UE category; or

- if the UE supports TM10 with one or more CSI processes; or

- if the UE supports 1024QAM in DL;

4> if the UECapabilityEnquiry message includes requestedFrequencyBands and UE supports

requestedFrequencyBands:

5> include all 2DL+1UL CA band combinations, only consisting of bands included in
requestedFrequencyBands;

5> include all other CA band combinations, only consisting of bands included in
requestedFrequencyBands, and prioritized in the order of requestedFrequencyBands, (i.e. first
include remaining band combinations containing the first-listed band, then include remaining band
combinations containing the second-listed band, and so on);

4> else (no requested frequency bands):

5> include all 2DL+1UL CA band combinations;

5> include all other CA band combinations;

4> if UE supports maximumCCsRetrieval and if the UECapabilityEnquiry message includes the

requestedMaxCCsDL and the requestedMaxCCsUL (i.e. both UL and DL maximums are given):

3GPP
Release 15 221 3GPP TS 36.331 V15.4.0 (2018-12)

5> remove from the list of candidates the band combinations for which the number of CCs in DL
exceeds the value indicated in the requestedMaxCCsDL or for which the number of CCs in UL
exceeds the value indicated in the requestedMaxCCsUL;

5> indicate in requestedCCsUL the same value as received in requestedMaxCCsUL;

5> indicate in requestedCCsDL the same value as received in requestedMaxCCsDL;

4> else if UE supports maximumCCsRetrieval and if the UECapabilityEnquiry message includes the
requestedMaxCCsDL (i.e. only DL maximum limit is given):

5> remove from the list of candidates the band combinations for which the number of CCs in DL
exceeds the value indicated in the requestedMaxCCsDL;

5> indicate value in requestedCCsDL the same value as received in requestedMaxCCsDL;

4> else if UE supports maximumCCsRetrieval and if the UECapabilityEnquiry message includes the
requestedMaxCCsUL (i.e. only UL maximum limit is given):

5> remove from the list of candidates the band combinations for which the number of CCs in UL
exceeds the value indicated in the requestedMaxCCsUL;

5> indicate in requestedCCsUL the same value as received in requestedMaxCCsUL;

4> if the UE supports reducedIntNonContComb and the UECapabilityEnquiry message includes

requestReducedIntNonContComb:

5> set reducedIntNonContCombRequested to true;

5> remove from the list of candidates the intra-band non-contiguous CA band combinations which
support is implied by another intra-band non-contiguous CA band combination included in the list
of candidates as specified in TS 36.306 [5], clause 4.3.5.21:

4> if the UE supports requestReducedFormat and UE supports skipFallbackCombinations and

UECapabilityEnquiry message includes requestSkipFallbackComb:

5> set skipFallbackCombRequested to true;

5> for each band combination included in the list of candidates (including 2DL+1UL CA band
combinations), starting with the ones with the lowest number of DL and UL carriers, that concerns
a fallback band combination of another band combination included in the list of candidates as
specified in TS 36.306 [5]:

6> remove the band combination from the list of candidates;

6> include differentFallbackSupported in the band combination included in the list of candidates
whose fallback concerns the removed band combination, if its capabilities differ from the
removed band combination;

4> if the UE supports requestReducedFormat and diffFallbackCombReport, and UECapabilityEnquiry

message includes requestDiffFallbackCombList:

5> if the UE does not support skipFallbackCombinations or UECapabilityEnquiry message does not
include requestSkipFallbackComb:

6> remove all band combination from the list of candidates;

5> for each CA band combination indicated in requestDiffFallbackCombList:

6> include the CA band combination, if not already in the list of candidates;

6> include the fallback combinations for which the supported UE capabilities are different from
the capability of the CA band combination;

5> include CA band combinations indicated in requestDiffFallbackCombList into

requestedDiffFallbackCombList;

3GPP
Release 15 222 3GPP TS 36.331 V15.4.0 (2018-12)

3> if the UECapabilityEnquiry message includes requestReducedFormat and UE supports

requestReducedFormat:

4> include in supportedBandCombinationReduced as many as possible of the band combinations

included in the list of candidates, including the non-CA combinations, determined according to the
rules and priority order defined above;

3> else

4> if the UECapabilityEnquiry message includes requestedFrequencyBands and UE supports

requestedFrequencyBands:

5> include in supportedBandCombination as many as possible of the band combinations included in

the list of candidates, including the non-CA combinations and up to 5DL+5UL CA band
combinations, determined according to the rules and priority order defined above;

5> include in supportedBandCombinationAdd as many as possible of the remaining band

combinations included in the list of candidates, (i.e. the candidates not included in
supportedBandCombination), up to 5DL+5UL CA band combinations, determined according to
the rules and priority order defined above;

4> else

5> include in supportedBandCombination as many as possible of the band combinations included in

the list of candidates, including the non-CA combinations and up to 5DL+5UL CA band
combinations, determined according to the rules defined above;

5> if it is not possible to include in supportedBandCombination all the band combinations to be

included according to the above, selection of the subset of band combinations to be included is left
up to UE implementation;

3> indicate in requestedBands the same bands and in the same order as included in
requestedFrequencyBands, if received;

3> if the UE is a category 0, M1 or M2 UE, or supports any UE capability information in ue-

RadioPagingInfo, according to TS 36.306 [5]:

4> include ue-RadioPagingInfo and set the fields according to TS 36.306 [5];

3> if the UE supports EN-DC and if requestedFreqBandsNR-MRDC is included in the request:

4> include into featureSetsEUTRA the feature sets that are applicable for the received
requestedFreqBandsNR-MRDC as specified in TS 38.331 [82], clause 5.6.1.4.

NOTE: Even if the network requests (only) capabilities for eutra, it may include NR band numbers in the
requestedFreqBandsNR-MRDC in order to ensure that the UE includes all necessary feature sets (i.e. E-
UTRA and NR) needed for subsequently requested eutra-nr capabilities.

3> if the UECapabilityEnquiry message includes request-sTTI-sPT-Capability and if the UE supports short
TTI and/or SPT:

4> for each band combination the UE included in a field of the UECapabilityInformation message in
accordance with the previous:

4> if the UE supports short TTI, include the short TTI capabilities for each of the band combinations
using the STTI-SPT-BandCombinationParameters;

4> if the UE supports SPT, include the SPT capabilities for each of the band combinations using the
STTI-SPT-BandCombinationParameters;

NOTE: The UE may have to add/repeat the band combinations to the list of band combinations
included earlier, to include short TTI capabilities and/or SPT capabilities.

2> if the UE supports short TTI and/or SPT:

3> include in the UE radio access capabilities the IE sTTI-SPT-Supported and set to supported;

3GPP
Release 15 223 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the ue-CapabilityRequest includes geran-cs and if the UE supports GERAN CS domain:

3> include the UE radio access capabilities for GERAN CS within a ue-CapabilityRAT-Container and with
the rat-Type set to geran-cs;

2> if the ue-CapabilityRequest includes geran-ps and if the UE supports GERAN PS domain:

3> include the UE radio access capabilities for GERAN PS within a ue-CapabilityRAT-Container and with
the rat-Type set to geran-ps;

2> if the ue-CapabilityRequest includes utra and if the UE supports UTRA:

3> include the UE radio access capabilities for UTRA within a ue-CapabilityRAT-Container and with the
rat-Type set to utra;

2> if the ue-CapabilityRequest includes cdma2000-1XRTT and if the UE supports CDMA2000 1xRTT:

3> include the UE radio access capabilities for CDMA2000 within a ue-CapabilityRAT-Container and with
the rat-Type set to cdma2000-1XRTT;

2> if the ue-CapabilityRequest includes nr and if the UE supports NR:

3> include the UE radio access capabilities for NR within a ue-CapabilityRAT-Container, with the rat-Type
set to nr;

3> include band combinations and feature sets as specified in TS 38.331 [82], clause 5.6.1.4, considering the
FreqBandList included in requestedFreqBandsNR-MRDC and the eutra-nr-only flag (if present);

2> if the ue-CapabilityRequest includes eutra-nr and if the UE supports EN-DC:

3> include the UE radio access capabilities for EUTRA-NR within a ue-CapabilityRAT-Container, with the
rat-Type set to eutra-nr;

3> include band combinations and feature sets as specified in TS 38.331 [82], clause 5.6.1.4, considering the
FreqBandList included in requestedFreqBandsNR-MRDC;

1> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends;

5.6.4 CSFB to 1x Parameter transfer

5.6.4.1 General

UE EUTRAN

CSFBParametersRequestCDMA2000

CSFBParametersResponseCDMA2000

Figure 5.6.4.1-1: CSFB to 1x Parameter transfer

The purpose of this procedure is to transfer the CDMA2000 1xRTT parameters required to register the UE in the
CDMA2000 1xRTT network for CSFB support.

3GPP
Release 15 224 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.4.2 Initiation
A UE in RRC_CONNECTED initiates the CSFB to 1x parameter transfer procedure upon request from the CDMA2000
upper layers. The UE initiates the CSFB to 1x parameter transfer procedure by sending the
CSFBParametersRequestCDMA2000 message.

5.6.4.3 Actions related to transmission of CSFBParametersRequestCDMA2000 message

The UE shall:

1> submit the CSFBParametersRequestCDMA2000 message to lower layers for transmission using the current
configuration;

5.6.4.4 Reception of the CSFBParametersResponseCDMA2000 message

Upon reception of the CSFBParametersResponseCDMA2000 message, the UE shall:

1> forward the rand and the mobilityParameters to the CDMA2000 1xRTT upper layers;

5.6.5 UE Information

5.6.5.1 General

UE EUTRAN

UEInformationRequest

UEInformationResponse

Figure 5.6.5.1-1: UE information procedure

The UE information procedure is used by E-UTRAN to request the UE to report information.

5.6.5.2 Initiation
E-UTRAN initiates the procedure by sending the UEInformationRequest message. E-UTRAN should initiate this
procedure only after successful security activation.

5.6.5.3 Reception of the UEInformationRequest message

Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation:

1> if rach-ReportReq is set to true, set the contents of the rach-Report in the UEInformationResponse message as
follows:

2> set the numberOfPreamblesSent to indicate the number of preambles sent by MAC for the last successfully
completed random access procedure;

2> if contention resolution was not successful as specified in TS 36.321 [6] for at least one of the transmitted
preambles for the last successfully completed random access procedure:
3> set the contentionDetected to true;

2> else:

3GPP
Release 15 225 3GPP TS 36.331 V15.4.0 (2018-12)

3> set the contentionDetected to false;

1> if rlf-ReportReq is set to true and the UE has radio link failure information or handover failure information
available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

2> set timeSinceFailure in VarRLF-Report to the time that elapsed since the last radio link or handover failure in
E-UTRA;

2> set the rlf-Report in the UEInformationResponse message to the value of rlf-Report in VarRLF-Report;

2> discard the rlf-Report from VarRLF-Report upon successful delivery of the UEInformationResponse message
confirmed by lower layers;

1> if connEstFailReportReq is set to true and the UE has connection establishment failure information in
VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

2> set timeSinceFailure in VarConnEstFailReport to the time that elapsed since the last connection
establishment failure in E-UTRA;

2> set the connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in
VarConnEstFailReport;

2> discard the connEstFailReport from VarConnEstFailReport upon successful delivery of the
UEInformationResponse message confirmed by lower layers;

1> if the logMeasReportReq is present and if the RPLMN is included in plmn-IdentityList stored in
VarLogMeasReport:

2> if VarLogMeasReport includes one or more logged measurement entries, set the contents of the
logMeasReport in the UEInformationResponse message as follows:

3> include the absoluteTimeStamp and set it to the value of absoluteTimeInfo in the VarLogMeasReport;

3> include the traceReference and set it to the value of traceReference in the VarLogMeasReport;

3> include the traceRecordingSessionRef and set it to the value of traceRecordingSessionRef in the
VarLogMeasReport;

3> include the tce-Id and set it to the value of tce-Id in the VarLogMeasReport;

3> include the logMeasInfoList and set it to include one or more entries from VarLogMeasReport starting
from the entries logged first;

3> if the VarLogMeasReport includes one or more additional logged measurement entries that are not
included in the logMeasInfoList within the UEInformationResponse message:

4> include the logMeasAvailable;

3> if the VarLogMeasReport includes one or more additional logged Bluetooth measurement entries that are
not included in the logMeasInfoList within the UEInformationResponse message:

4> include the logMeasAvailableBT;

3> if the VarLogMeasReport includes one or more additional logged WLAN measurement entries that are
not included in the logMeasInfoList within the UEInformationResponse message:

4> include the logMeasAvailableWLAN;

1> if mobilityHistoryReportReq is set to true:

2> include the mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport;

2> include in the mobilityHistoryReport an entry for the current cell, possibly after removing the oldest entry if
required, and set its fields as follows:

3> set visitedCellId to the global cell identity of the current cell:

3GPP
Release 15 226 3GPP TS 36.331 V15.4.0 (2018-12)

3> set field timeSpent to the time spent in the current cell;

1> if the idleModeMeasurementReq is included in the UEInformationRequest and UE has stored

VarMeasIdleReport:

2> set the measResultListIdle in the UEInformationResponse message to the value of idleMeasReport in the
VarMeasIdleReport;

2> discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed
by lower layers;

1> if flightPathInfoReq field is present and the UE has flight path information available:

2> include the flightPathInfoReport and set it to include the list of waypoints along the flight path;

2> if the includeTimeStamp is set to TRUE:

3> set the field timeStamp to the time when UE intends to arrive to each waypoint if this information is
available at the UE;

1> if the logMeasReport is included in the UEInformationResponse:

2> submit the UEInformationResponse message to lower layers for transmission via SRB2;

2> discard the logged measurement entries included in the logMeasInfoList from VarLogMeasReport upon
successful delivery of the UEInformationResponse message confirmed by lower layers;

1> else:

2> submit the UEInformationResponse message to lower layers for transmission via SRB1;

5.6.6 Logged Measurement Configuration

5.6.6.1 General

UE EUTRAN

LoggedMeasurementConfiguration

Figure 5.6.6.1-1: Logged measurement configuration

The purpose of this procedure is to configure the UE to perform logging of measurement results while in RRC_IDLE
and to perform logging of measurement results for MBSFN in both RRC_IDLE and RRC_CONNECTED. The
procedure applies to logged measurements capable UEs that are in RRC_CONNECTED.

NOTE: E-UTRAN may retrieve stored logged measurement information by means of the UE information
procedure.

5.6.6.2 Initiation
E-UTRAN initiates the logged measurement configuration procedure to UE in RRC_CONNECTED by sending the
LoggedMeasurementConfiguration message.

3GPP
Release 15 227 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.6.3 Reception of the LoggedMeasurementConfiguration by the UE

Upon receiving the LoggedMeasurementConfiguration message the UE shall:

1> discard the logged measurement configuration as well as the logged measurement information as specified in
5.6.7;

1> store the received loggingDuration, loggingInterval and areaConfiguration, if included, in VarLogMeasConfig;

1> if the LoggedMeasurementConfiguration message includes plmn-IdentityList:

2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN as well as the PLMNs included in plmn-
IdentityList;

1> else:

2> set plmn-IdentityList in VarLogMeasReport to include the RPLMN;

1> store the received absoluteTimeInfo, traceReference, traceRecordingSessionRef and tce-Id in

VarLogMeasReport;

1> store the received targetMBSFN-AreaList, if included, in VarLogMeasConfig;

1> store the received bt-NameList, if included, in VarLogMeasConfig;

1> store the received wlan-Namelist, if included, in VarLogMeasConfig;

1> start timer T330 with the timer value set to the loggingDuration;

5.6.6.4 T330 expiry

Upon expiry of T330 the UE shall:

1> release VarLogMeasConfig;

The UE is allowed to discard stored logged measurements, i.e. to release VarLogMeasReport, 48 hours after T330
expiry.

5.6.7 Release of Logged Measurement Configuration

5.6.7.1 General
The purpose of this procedure is to release the logged measurement configuration as well as the logged measurement
information.

5.6.7.2 Initiation
The UE shall initiate the procedure upon receiving a logged measurement configuration in another RAT. The UE shall
also initiate the procedure upon power off or detach.

The UE shall:

1> stop timer T330, if running;

1> if stored, discard the logged measurement configuration as well as the logged measurement information, i.e.
release the UE variables VarLogMeasConfig and VarLogMeasReport;

3GPP
Release 15 228 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.8 Measurements logging

5.6.8.1 General
This procedure specifies the logging of available measurements by a UE in RRC_IDLE that has a logged measurement
configuration and the logging of available measurements by a UE in both RRC_IDLE and RRC_CONNECTED if
targetMBSFN-AreaList is included in VarLogMeasConfig.

5.6.8.2 Initiation
While T330 is running, the UE shall:

1> if measurement logging is suspended:

2> if during the last logging interval the IDC problems detected by the UE is resolved, resume measurement
logging;

1> if not suspended, perform the logging in accordance with the following:

2> if targetMBSFN-AreaList is included in VarLogMeasConfig:

3> if the UE is camping normally on an E-UTRA cell or is connected to E-UTRA; and

3> if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; and

3> if the PCell (in RRC_CONNECTED) or cell where the UE is camping (in RRC_IDLE) is part of the area
indicated by areaConfiguration if configured in VarLogMeasConfig:

4> for MBSFN areas, indicated in targetMBSFN-AreaList, from which the UE is receiving MBMS
service:

5> perform MBSFN measurements in accordance with the performance requirements as specified in
TS 36.133 [16];

NOTE 1: When configured to perform MBSFN measurement logging by targetMBSFN-AreaList, the UE is not
required to receive additional MBSFN subframes, i.e. logging is based on the subframes corresponding to
the MBMS services the UE is receiving.

5> perform logging at regular time intervals as defined by the loggingInterval in VarLogMeasConfig,
but only for those intervals for which MBSFN measurement results are available as specified in TS
36.133 [16];

2> else if:

3> if the UE is in any cell selection state (as specified in TS 36.304 [4]):

4> perform the logging at regular time intervals, as defined by the loggingInterval in VarLogMeasConfig;

3> else if the UE is camping normally on an E-UTRA cell and if the RPLMN is included in plmn-
IdentityList stored in VarLogMeasReport and, if the cell is part of the area indicated by
areaConfiguration if configured in VarLogMeasConfig:

4> perform the logging at regular time intervals, as defined by the loggingInterval in VarLogMeasConfig;

2> when adding a logged measurement entry in VarLogMeasReport, include the fields in accordance with the
following:

3> if the UE detected IDC problems during the last logging interval:

4> if measResultServCell in VarLogMeasReport is not empty:

5> include InDeviceCoexDetected;

5> suspend measurement logging from the next logging interval;

3GPP
Release 15 229 3GPP TS 36.331 V15.4.0 (2018-12)

4> else:

5> suspend measurement logging;

NOTE 1A: The UE may detect the start of IDC problems as early as Phase 1 as described in clause 23.4 of TS
36.300 [9].

3> set the relativeTimeStamp to indicate the elapsed time since the moment at which the logged
measurement configuration was received;

3> if detailed location information became available during the last logging interval, set the content of the
locationInfo as follows:

4> include the locationCoordinates;

3> if wlan-NameList is included in VarLogMeasConfig:

4> if detailed WLAN measurements are available:

5> include logMeasResultListWLAN, in order of decreasing RSSI for WLAN APs;

3> if bt-NameList is included in VarLogMeasConfig:

4> if detailed Bluetooth measurements are available:

5> include logMeasResultListBT, in order of decreasing RSSI for Bluetooth beacons;

3> if targetMBSFN-AreaList is included in VarLogMeasConfig:

4> for each MBSFN area, for which the mandatory measurements result fields became available during
the last logging interval:

5> set the rsrpResultMBSFN, rsrqResultMBSFN to include measurement results that became
available during the last logging interval;

5> include the fields signallingBLER-Result or dataBLER-MCH-ResultList if the concerned BLER

results are availble,

5> set the mbsfn-AreaId and carrierFrequency to indicate the MBSFN area in which the UE is
receiving MBSFN transmission;

4> if in RRC_CONNECTED:

5> set the servCellIdentity to indicate global cell identity of the PCell;

5> set the measResultServCell to include the layer 3 filtered measured results of the PCell;

5> if available, set the measResultNeighCells to include the layer 3 filtered measured results of
SCell(s) and neighbouring cell(s) measurements that became available during the last logging
interval, in order of decreasing RSRP, for at most the following number of cells: 6 intra-frequency
and 3 inter-frequency cells per frequency and according to the following:

6> for each cell included, include the optional fields that are available;

5> if available, optionally set the measResultNeighCells to include the layer 3 filtered measured
results of neighbouring cell(s) measurements that became available during the last logging
interval, in order of decreasing RSCP(UTRA)/RSSI(GERAN)/PilotStrength(cdma2000), for at
most the following number of cells: 3 inter-RAT cells per frequency (UTRA, cdma2000)/set of
frequencies (GERAN), and according to the following:

6> for each cell included, include the optional fields that are available;

4> if in RRC_IDLE:

5> set the servCellIdentity to indicate global cell identity of the serving cell;

5> set the measResultServCell to include the quantities of the serving cell;

3GPP
Release 15 230 3GPP TS 36.331 V15.4.0 (2018-12)

5> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell
re-selection, to include neighbouring cell measurements that became available during the last
logging interval for at most the following number of neighbouring cells: 6 intra-frequency and 3
inter-frequency neighbours per frequency and according to the following:

6> for each neighbour cell included, include the optional fields that are available;

5> if available, optionally set the measResultNeighCells, in order of decreasing ranking-criterion as

used for cell re-selection, to include neighbouring cell measurements that became available during
the last logging interval, for at most the following number of cells: 3 inter-RAT cells per frequency
(UTRA, cdma2000)/set of frequencies (GERAN), and according to the following:

6> for each cell included, include the optional fields that are available;

4> for the cells included according to the previous (i.e. covering previous and current serving cells as
well as neighbouring EUTRA cells) include results according to the extended RSRQ if corresponding
results are available according to the associated performance requirements defined in TS 36.133 [16];

4> for the cells included according to the previous (i.e. covering previous and current serving cells as
well as neighbouring EUTRA cells) include RSRQ type if the result was based on measurements
using a wider band or using all OFDM symbols;

NOTE 2: The UE includes the latest results in accordance with the performance requirements as specified in TS
36.133 [16]. E.g. RSRP and RSRQ results are available only if the UE has a sufficient number of results/
receives a sufficient number of subframes during the logging interval.

3> else:

4> if the UE is in any cell selection state (as specified in TS 36.304 [4]):

5> set anyCellSelectionDetected to indicate the detection of no suitable or no acceptable cell found;

5> set the servCellIdentity to indicate global cell identity of the last logged cell that the UE was
camping on;

5> set the measResultServCell to include the quantities of the last logged cell the UE was camping on;

4> else:

5> set the servCellIdentity to indicate global cell identity of the cell the UE is camping on;

5> set the measResultServCell to include the quantities of the cell the UE is camping on;

4> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-
selection, to include neighbouring cell measurements that became available during the last logging
interval for at most the following number of neighbouring cells: 6 intra-frequency and 3 inter-
frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of
frequencies (GERAN) per RAT and according to the following:

5> for each neighbour cell included, include the optional fields that are available;

4> for the cells included according to the previous (i.e. covering previous and current serving cells as
well as neighbouring EUTRA cells) include results according to the extended RSRQ if corresponding
results are available according to the associated performance requirements defined in TS 36.133 [16];

4> for the cells included according to the previous (i.e. covering previous and current serving cells as
well as neighbouring EUTRA cells) include RSRQ type if the result was based on measurements
using a wider band or using all OFDM symbols;

NOTE 3: The UE includes the latest results of the available measurements as used for cell reselection evaluation in
RRC_IDLE or as used for evaluation of reporting criteria or for measurement reporting according to 5.5.3
in RRC_CONNECTED, which are performed in accordance with the performance requirements as
specified in TS 36.133 [16].

2> when the memory reserved for the logged measurement information becomes full, stop timer T330 and
perform the same actions as performed upon expiry of T330, as specified in 5.6.6.4;

3GPP
Release 15 231 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.9 In-device coexistence indication

5.6.9.1 General

UE EUTRAN

RRC connection reconfiguration

InDeviceCoexIndication

Figure 5.6.9.1-1: In-device coexistence indication

The purpose of this procedure is to inform E-UTRAN about (a change of) the In-Device Coexistence (IDC) problems
experienced by the UE in RRC_CONNECTED, as described in TS 36.300 [9], and to provide the E-UTRAN with
information in order to resolve them.

5.6.9.2 Initiation
A UE capable of providing IDC indications may initiate the procedure when it is configured to provide IDC indications
and upon change of IDC problem information.

Upon initiating the procedure, the UE shall:

1> if configured to provide IDC indications:

2> if the UE did not transmit an InDeviceCoexIndication message since it was configured to provide IDC
indications:

3> if on one or more frequencies for which a measObjectEUTRA is configured, the UE is experiencing IDC
problems that it cannot solve by itself; or

3> if configured to provide IDC indications for UL CA; and if on one or more supported UL CA
combination comprising of carrier frequencies for which a measurement object is configured, the UE is
experiencing IDC problems that it cannot solve by itself; or

3> if configured to provide IDC indications for MR-DC, and if on one or more supported MR-DC
combination comprising of at least one E-UTRA carrier frequency for which a measurement object is
configured and at least one NR carrier frequency included in candidateServingFreqListNR, the UE is
experiencing IDC problems that it cannot solve by itself:

4> initiate transmission of the InDeviceCoexIndication message in accordance with 5.6.9.3;

2> else:

3> if the set of frequencies, for which a measObjectEUTRA is configured and on which the UE is
experiencing IDC problems that it cannot solve by itself, is different from the set indicated in the last
transmitted InDeviceCoexIndication message; or

3> if for one or more of the frequencies in the previously reported set of frequencies, the
interferenceDirection is different from the value indicated in the last transmitted InDeviceCoexIndication
message; or

3> if the TDM assistance information is different from the assistance information included in the last
transmitted InDeviceCoexIndication message; or

3> if configured to provide IDC indications for UL CA; and if the victimSystemType is different from the
value indicated in the last transmitted InDeviceCoexIndication message; or

3GPP
Release 15 232 3GPP TS 36.331 V15.4.0 (2018-12)

3> if configured to provide IDC indications for UL CA; and if the set of supported UL CA combinations on
which the UE is experiencing IDC problems that it cannot solve by itself and that the UE includes in
affectedCarrierFreqCombList according to 5.6.9.3, is different from the set indicated in the last
transmitted InDeviceCoexIndication message; or

3> if configured to provide IDC indications for MR-DC, and if the set of supported MR-DC combinations on
which the UE is experiencing IDC problems that it cannot solve by itself and that the UE includes in
affectedCarrierFreqCombListMRDC according to 5.6.9.3, is different from the set indicated in the last
transmitted InDeviceCoexIndication message:

4> initiate transmission of the InDeviceCoexIndication message in accordance with 5.6.9.3;

NOTE 1: The term "IDC problems" refers to interference issues applicable across several subframes/slots where not
necessarily all the subframes/slots are affected.

NOTE 2: For the frequencies on which a serving cell or serving cells is configured that is activated, IDC problems
consist of interference issues that the UE cannot solve by itself, during either active data exchange or
upcoming data activity which is expected in up to a few hundred milliseconds.
For frequencies on which a SCell or SCells is configured that is deactivated, reporting IDC problems
indicates an anticipation that the activation of the SCell or SCells would result in interference issues that
the UE would not be able to solve by itself.
For a non-serving frequency, reporting IDC problems indicates an anticipation that if the non-serving
frequency or frequencies became a serving frequency or serving frequencies then this would result in
interference issues that the UE would not be able to solve by itself.

5.6.9.3 Actions related to transmission of InDeviceCoexIndication message

The UE shall set the contents of the InDeviceCoexIndication message as follows:

1> if there is at least one E-UTRA carrier frequency, for which a measurement object is configured, that is affected
by IDC problems:

2> include the field affectedCarrierFreqList with an entry for each affected E-UTRA carrier frequency for
which a measurement object is configured;

2> for each E-UTRA carrier frequency included in the field affectedCarrierFreqList, include
interferenceDirection and set it accordingly;

2> include Time Domain Multiplexing (TDM) based assistance information, unless idc-
HardwareSharingIndication is configured and the UE has no Time Doman Multiplexing based assistance
information that could be used to resolve the IDC problems:

3> if the UE has DRX related assistance information that could be used to resolve the IDC problems:

4> include drx-CycleLength, drx-Offset and drx-ActiveTime;

3> else (the UE has desired subframe reservation patterns related assistance information that could be used to
resolve the IDC problems):

4> include idc-SubframePatternList;

3> use the MCG as timing reference if TDM based assistance information regarding the SCG is included;

1> if the UE is configured to provide UL CA information and there is a supported UL CA combination comprising
of carrier frequencies for which a measurement object is configured, that is affected by IDC problems:

2> include victimSystemType in ul-CA-AssistanceInfo;

2> if the UE sets victimSystemType to wlan or Bluetooth:

3> include affectedCarrierFreqCombList in ul-CA-AssistanceInfo with an entry for each supported UL CA

combination comprising of carrier frequencies for which a measurement object is configured, that is
affected by IDC problems;

2> else:

3GPP
Release 15 233 3GPP TS 36.331 V15.4.0 (2018-12)

3> optionally include affectedCarrierFreqCombList in ul-CA-AssistanceInfo with an entry for each

supported UL CA combination comprising of carrier frequencies for which a measurement object is
configured, that is affected by IDC problems;

1> if idc-HardwareSharingIndication is configured, and there is at least one E-UTRA carrier frequency, for which a
measurement object is configured, the UE is experiencing hardware sharing problems that it cannot solve by
itself:

2> include the hardwareSharingProblem and set it accordingly;

1> if the UE is configured to provide IDC indications for MR-DC and there is a supported MR-DC band
combination comprising of at least one E-UTRA carrier frequency for which a measurement object is configured
and at least one NR carrier frequency included in candidateServingFreqListNR, that is affected by IDC
problems; and

1> if the IDC problem does not only concern the E-UTRA band combination as the UE already included in
affectedCarrierFreqCombList:

2> for each entry of affectedCarrierFreqCombInfoListMRDC in mrdc-AssistanceInfo;

3> include victimSystemType;

3> include interferenceDirection;

3> if the UE sets victimSystemType to wlan or Bluetooth:

4> include a set of at least one NR carrier frequency included in candidateServingFreqListNR and
optionally one or more E-UTRA carrier frequency for which a measurement object is configured, that
is affected by IDC problems;

3> else:

4> optionally include a set of at least one NR carrier frequency included in candidateServingFreqListNR
and optionally one or more E-UTRA carrier frequency for which a measurement object is configured,
that is affected by IDC problems;

NOTE 1: When sending an InDeviceCoexIndication message to inform E-UTRAN the IDC problems, the UE
includes all assistance information (rather than providing e.g. the changed part(s) of the assistance
information).

NOTE 2: Upon not anymore experiencing a particular IDC problem that the UE previously reported, the UE
provides an IDC indication with the modified contents of the InDeviceCoexIndication message (e.g. by an
empty message).

The UE shall submit the InDeviceCoexIndication message to lower layers for transmission.

5.6.10 UE Assistance Information

5.6.10.1 General

UE EUTRAN

RRC connection reconfiguration

UEAssistanceInformation

Figure 5.6.10.1-1: UE Assistance Information

3GPP
Release 15 234 3GPP TS 36.331 V15.4.0 (2018-12)

The purpose of this procedure is to inform E-UTRAN of the UE's power saving preference and SPS assistance
information, maximum PDSCH/PUSCH bandwidth configuration preference, overheating assistance information, or the
UE's delay budget report carrying desired increment/decrement in the Uu air interface delay or connected mode DRX
cycle length and for BL UEs or UEs in CE of the RLM event ("early-out-of-sync" or "early-in-sync") and RLM
information. Upon configuring the UE to provide power preference indications E-UTRAN may consider that the UE
does not prefer a configuration primarily optimised for power saving until the UE explictly indicates otherwise.

5.6.10.2 Initiation
A UE capable of providing power preference indications in RRC_CONNECTED may initiate the procedure in several
cases including upon being configured to provide power preference indications and upon change of power preference. A
UE capable of providing SPS assistance information in RRC_CONNECTED may initiate the procedure in several cases
including upon being configured to provide SPS assistance information and upon change of SPS assistance information.

A UE capable of providing delay budget report in RRC_CONNECTED may initiate the procedure in several cases,
including upon being configured to provide delay budget report and upon change of delay budget preference.

A UE capable of CE mode and providing maximum PDSCH/PUSCH bandwidth preference in RRC_CONNECTED

may initiate the procedure upon being configured to provide maximum PDSCH/PUSCH bandwidth preference and/or
upon change of maximum PDSCH/PUSCH bandwidth preference.

A UE capable of providing overheating assistance information in RRC_CONNECTED may initiate the procedure if it
was configured to do so, upon detecting internal overheating, or upon detecting that it is no longer experiencing an
overheating condition.

Upon initiating the procedure, the UE shall:

1> if configured to provide power preference indications:

2> if the UE did not transmit a UEAssistanceInformation message with powerPrefIndication since it was
configured to provide power preference indications; or

2> if the current power preference is different from the one indicated in the last transmission of the
UEAssistanceInformation message and timer T340 is not running:

3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

1> if configured to provide maximum PDSCH/PUSCH bandwidth preference:

2> if the UE did not transmit a UEAssistanceInformation message with bw-Preference since it was configured to
provide maximum PDSCH/PUSCH bandwidth preference; or

2> if the current maximum PDSCH/PUSCH bandwidth preference is different from the one indicated in the last
transmission of the UEAssistanceInformation message and timer T341 is not running;

3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

1> if configured to provide SPS assistance information:

2> if the UE did not transmit a UEAssistanceInformation message with sps-AssistanceInformation since it was
configured to provide SPS assistance information; or

2> if the current SPS assistance information is different from the one indicated in the last transmission of the
UEAssistanceInformation message:

3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

1> if configured to report RLM events:

2> if "early-out-of-sync" event has been detected and T343 is not running; or

2> if "early-in-sync" event has been detected and T344 is not running:

3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

1> if configured to provide delay budget report:

3GPP
Release 15 235 3GPP TS 36.331 V15.4.0 (2018-12)

2> if the UE did not transmit a UEAssistanceInformation message with delayBudgetReport since it was
configured to provide delay budget report; or

2> if the current delay budget is different from the one indicated in the last transmission of the
UEAssistanceInformation message and timer T342 is not running:

3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

1> if configured to provide overheating assistance information:

2> if the overheating condition has been detected and T345 is not running; or

2> if the current overheating assistance information is different from the one indicated in the last transmission of
the UEAssistanceInformation message and timer T345 is not running:

3> initiate transmission of the UEAssistanceInformation message in accordance with 5.6.10.3;

5.6.10.3 Actions related to transmission of UEAssistanceInformation message

The UE shall set the contents of the UEAssistanceInformation message for power preference indications:

1> if configured to provide power preference indication and if the UE prefers a configuration primarily optimised
for power saving:

2> set powerPrefIndication to lowPowerConsumption;

1> else if configured to provide power preference indication:

2> start or restart timer T340 with the timer value set to the powerPrefIndicationTimer;

2> set powerPrefIndication to normal;

The UE shall set the contents of the UEAssistanceInformation message for SPS assistance information:

1> if configured to provide SPS assistance information:

2> if there is any traffic for V2X sidelink communication which needs to report SPS assistance information:

3> include trafficPatternInfoListSL in the UEAssistanceInformation message;

2> if there is any traffic for uplink communication which needs to report SPS assistance information:

3> include trafficPatternInfoListUL in the UEAssistanceInformation message;

The UE shall set the contents of the UEAssistanceInformation message for bandwidth preference indications:

1> start timer T341 with the timer value set to the bw-PreferenceIndicationTimer;

1> set bw-Preference to its preferred configuration;

The UE shall set the contents of the UEAssistanceInformation message for delay budget report:

1> if configured to provide delay budget report:

2> if the UE prefers an adjustment in the connected mode DRX cycle length:

3> set delayBudgetReport to type1 according to a desired value;

2> else if the UE prefers coverage enhancement configuration change:

3> set delayBudgetReport to type2 according to a desired value;

2> start or restart timer T342 with the timer value set to the delayBudgetReportingProhibitTimer;

The UE shall set the contents of the UEAssistanceInformation message for the RLM report:

1> if T314 has expired:

3GPP
Release 15 236 3GPP TS 36.331 V15.4.0 (2018-12)

2> set rlm-event to earlyOutOfSync;

2> start timer T343 with the timer value set to the rlmReportTimer:

1> if T315 has expired:

2> set rlm-event to earlyInSync;

2> start timer T344 with the timer value set to the rlmReportTimer:

2> if configured to report rlmReportRep-MPDCCH:

3> set excessRep-MPDCCH to the value indicated by lower layers;

The UE shall set the contents of the UEAssistanceInformation message for overheating assistance indication:

1> if the UE experiences internal overheating:

2> if the UE prefers to temporarily reduce its DL category and UL category:

3> include reducedUE-Category in the OverheatingAssistance IE;

3> set reducedUE-CategoryDL to the number to which the UE prefers to temporarily reduce its DL category;

3> set reducedUE-CategoryUL to the number to which the UE prefers to temporarily reduce its UL category;

2> if the UE prefers to temporarily reduce the number of maximum secondary component carriers:

3> include reducedMaxCCs in the OverheatingAssistance IE;

3> set reducedCCsDL to the number of maximum SCells the UE prefers to be temporarily configured in
downlink;

3> set reducedCCsUL to the number of maximum SCells the UE prefers to be temporarily configured in
uplink;

2> start timer T345 with the timer value set to the overheatingIndicationProhibitTimer;

1> else (if the UE no longer experiences an overheating condition):

2> do not include reducedUE-Category and reducedMaxCCs in OverheatingAssistance IE;

2> start timer T345 with the timer value set to the overheatingIndicationProhibitTimer;

The UE shall submit the UEAssistanceInformation message to lower layers for transmission.

NOTE 1: It is up to UE implementation when and how to trigger SPS assistance information.

NOTE 2: It is up to UE implementation to set the content of trafficPatternInfoListSL and trafficPatternInfoListUL.

NOTE 3: Traffic patterns for different Destination Layer 2 IDs are provided in different entries in
trafficPatternInfoListSL.

5.6.11 Mobility history information

5.6.11.1 General
This procedure specifies how the mobility history information is stored by the UE, covering RRC_CONNECTED and
RRC_IDLE.

5.6.11.2 Initiation
If the UE supports storage of mobility history information, the UE shall:

1> Upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE, to another E-
UTRA or inter-RAT cell or when entering out of service:

3GPP
Release 15 237 3GPP TS 36.331 V15.4.0 (2018-12)

2> include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary,
according to following:

3> if the global cell identity of the previous PCell/ serving cell is available:

4> include the global cell identity of that cell in the field visitedCellId of the entry;

3> else:

4> include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the
entry;

3> set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell;

1> upon entering E-UTRA (in RRC_CONNECTED or RRC_IDLE) while previously out of service and/ or using
another RAT:

2> include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary,
according to following:

3> set the field timeSpent of the entry as the time spent outside E-UTRA;

5.6.12 RAN-assisted WLAN interworking

5.6.12.1 General
The purpose of this procedure is to facilitate access network selection and traffic steering between E-UTRAN and
WLAN.

If required by upper layers (see TS 24.312 [66], the UE shall provide an up-to-date set of the applicable parameters
provided by wlan-OffloadConfigCommon or wlan-OffloadConfigDedicated to upper layers, and inform upper layers
when no parameters are configured. The parameter set from either wlan-OffloadConfigCommon or wlan-
OffloadConfigDedicated is selected as specified in subclauses 5.2.2.24, 5.3.12, 5.6.12.2 and 5.6.12.4.

5.6.12.2 Dedicated WLAN offload configuration

The UE shall:

1> if the received wlan-OffloadInfo is set to release:

2> release wlan-OffloadConfigDedicated and t350;

2> if the wlan-OffloadConfigCommon corresponding to the RPLMN is broadcast by the cell:

3> apply the wlan-OffloadConfigCommon corresponding to the RPLMN included in

SystemInformationBlockType17;

1> else:

2> apply the received wlan-OffloadConfigDedicated:

5.6.12.3 WLAN offload RAN evaluation

The UE shall:

1> if the UE is configured with either wlan-OffloadConfigCommon or wlan-OffloadConfigDedicated; and

1> if the UE is in RRC_IDLE or none of rclwi-Configuration, lwa-Configuration and lwip-Configuration is

configured:

2> provide measurement results required for the evaluation of the network selection and traffic steering rules as
defined in TS 24.312 [66] to upper layers;

3GPP
Release 15 238 3GPP TS 36.331 V15.4.0 (2018-12)

2> evaluate the network selection and traffic steering rules as defined in TS 36.304 [4] using WLAN identifiers
as indicated in other subclauses (either provided in steerToWLAN included in rclwi-Configuration or in
wlan-Id-List included in SystemInformationBlockType17);

5.6.12.4 T350 expiry or stop

The UE shall:

1> if T350 expires or is stopped:

2> release the wlan-OffloadConfigDedicated and t350;

2> release rclwi-Configuration if configured;

2> if the wlan-OffloadConfigCommon corresponding to the RPLMN is broadcast by the cell:

3> apply the wlan-OffloadConfigCommon and the wlan-Id-List corresponding to the RPLMN included in
SystemInformationBlockType17;

5.6.12.5 Cell selection/ re-selection while T350 is running

The UE shall:

1> if, while T350 is running, the UE selects/ reselects a cell which is not the PCell when the wlan-OffloadDedicated
was configured:

2> stop timer T350;

2> perform the actions as specified in 5.6.12.4;

5.6.13 SCG failure information

5.6.13.1 General

UE EUTRAN

RRC connection reconfiguration

(scg-Configuration)
SCGFailureInformation

Figure 5.6.13.1-1: SCG failure information

The purpose of this procedure is to inform E-UTRAN about an SCG failure the UE has experienced i.e. SCG radio link
failure, SCG change failure.

5.6.13.2 Initiation
A UE initiates the procedure to report SCG failures when SCG transmission is not suspended and when one of the
following conditions is met:

1> upon detecting radio link failure for the SCG, in accordance with 5.3.11; or

1> upon SCG change failure, in accordance with 5.3.5.7a; or

1> upon stopping uplink transmission towards the PSCell due to exceeding the maximum uplink transmission
timing difference when powerControlMode is configured to 1, in accordance with subclause 7.17.2 of TS 36.133
[29].

3GPP
Release 15 239 3GPP TS 36.331 V15.4.0 (2018-12)

In case of DC, upon initiating the procedure, the UE shall:

1> suspend all SCG DRBs and suspend SCG transmission for split DRBs;

1> reset SCG-MAC;

1> stop T307;

1> initiate transmission of the SCGFailureInformation message in accordance with 5.6.13.3;

5.6.13.3 Actions related to transmission of SCGFailureInformation message

The UE shall set the contents of the SCGFailureInformation message as follows:

1> if the UE initiates transmission of the SCGFailureInformation message to provide SCG radio link failure
information:

2> include failureType and set it to the trigger for detecting SCG radio link failure;

1> else if the UE initiates transmission of the SCGFailureInformation message to provide SCG change failure
information:

2> include failureType and set it to scg-ChangeFailure;

1> else if the UE initiates transmission of the SCGFailureInformation message due to exceeding maximum uplink
transmission timing difference:

2> include failureType and set it to maxUL-TimingDiff;

1> set the measResultServFreqList to include for each E-UTRA SCG cell that is configured, if any, within
measResultSCell the quantities of the concerned SCell, if available according to performance requirements in TS
36.133 [16];

1> for each E-UTRA SCG serving frequency included in measResultServFreqList, include within
measResultBestNeighCell the physCellId and the quantities of the best non-serving cell, based on RSRP, on the
concerned serving frequency;

1> set the measResultNeighCells to include the best measured cells on non-serving E-UTRA frequencies, ordered
such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the
failure, and set its fields as follows;

2> if the UE was configured to perform measurements for one or more non-serving EUTRA frequencies and
measurement results are available, include the measResultListEUTRA;

2> for each neighbour cell included, include the optional fields that are available;

NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement
configuration. The measurements are based on the time domain measurement resource restriction, if
configured. Blacklisted cells are not required to be reported.

The UE shall submit the SCGFailureInformation message to lower layers for transmission.

3GPP
Release 15 240 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.13a NR SCG failure information

5.6.13a.1 General

UE EUTRAN

RRC connection reconfiguration

(E.g. nr-Config, sk-Counter,
radioBeareConfig1)
SCGFailureInformationNR

Figure 5.6.13a.1-1: NRSCG failure information

The purpose of this procedure is to inform E-UTRAN about an SCG failure the UE has experienced (e.g. SCG radio
link failure, failure to successfully complete an SCG reconfiguration with sync), as specified in TS 38.331 [82], clause
5.7.3.2.

5.6.13a.2 Initiation
A UE initiates the procedure to report NR SCG failures when NR SCG transmission is not suspended and in accordance
with TS 38.331 [82], clause 5.7.3.2. Actions the UE shall perform upon initiating the procedure, other than related to
the transmission of the SCGFailureInformationNR message are specified in TS 38.331 [82], clause 5.7.3.2.

5.6.13a.3 Actions related to transmission of SCGFailureInformationNR message

The UE shall set the contents of the SCGFailureInformationNR message as follows:

1> include failureType within failureReportSCG-NR and set it to indicate the SCG failure in accordance with TS
38.331 [82], clause 5.7.3.3;

1> include and set measResultSCG in accordance with TS 38.331 [82], clause 5.7.3.4:

1> for each NR frequency the UE is configured to measure by measConfig for which measurement results are
available:

2> set the measResultFreqListNR to include the best measured cells, ordered such that the best cell is listed first
using RSRP to order if RSRP measurement results are available for cells on this frequency, otherwise using
RSRQ to order if RSRQ measurement results are available for cells on this frequency, otherwise using SINR
to order, and based on measurements collected up to the moment the UE detected the failure, and for each
cell that is included, include the optional fields that are available;

NOTE: Field measResultSCG is used to report available results for NR frequencies the UE is configured to
measure by NR RRC signalling.

The UE shall submit the SCGFailureInformationNR message to lower layers for transmission.

5.6.14 LTE-WLAN Aggregation

5.6.14.1 Introduction
E-UTRAN can configure the UE to connect to a WLAN and configure bearers for LWA (referred to as LWA DRBs).
The UE uses the WLAN parameters received from E-UTRAN in performing WLAN measurements. The UE also
performs WLAN connection management as described in 5.6.15 while LWA is configured.

3GPP
Release 15 241 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.14.2 Reception of LWA configuration

Upon reception of LWA configuration, the UE shall:

1> if the received lwa-Configuration is set to release:

2> release the LWA configuration as described in 5.6.14.3;

1> else:

2> if the received lwa-Config includes lwa-WT-Counter:

3> determine the S-KWT key based on the KeNB key and received lwa-WT-Counter value, as specified in TS
33.401 [32];

3> forward the S-KWT key to upper layers to be used as a PMK or PSK for WLAN authentication;

2> if the received lwa-Config includes lwa-MobilityConfig:

3> if the received lwa-MobilityConfig includes wlan-ToReleaseList:

4> for each WLAN-Identifiers included in wlan-ToReleaseList:

5> remove the WLAN-Identifiers if already part of the current wlan-MobilitySet in VarWLAN-
MobilityConfig;

3> if the received lwa-MobilityConfig includes wlan-ToAddList:

4> for each WLAN-Identifiers included in wlan-ToAddList:

5> add the WLAN-Identifiers to the current wlan-MobilitySet in VarWLAN-MobilityConfig;

3> if the received lwa-MobilityConfig includes associationTimer:

4> start or restart timer T351 with the timer value set to the associationTimer;

3> if the received lwa-MobilityConfig includes successReportRequested:

4> set successReportRequested in VarWLAN-MobilityConfig to the value of successReportRequested;

3> if the received lwa-MobilityConfig includes wlan-SuspendConfig:

4> set the field(s) in wlan-SuspendConfig within VarWLAN-MobilityConfig to the value(s) of field(s)
included in wlan-SuspendConfig;

2> start WLAN Status Monitoring as described in 5.6.15.4;

5.6.14.3 Release of LWA configuration

To release the LWA configuration, the UE shall:

1> for each LWA DRB that is part of the current UE configuration:

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

2> perform PDCP data recovery as specified in TS 36.323 [8];

1> delete any existing values in VarWLAN-MobilityConfig and VarWLAN-Status;

1> stop timer T351, if running;

1> stop WLAN status monitoring and WLAN connection attempts for LWA;

1> indicate the release of LWA configuration, if configured, to upper layers;

3GPP
Release 15 242 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.15 WLAN connection management

5.6.15.1 Introduction
WLAN connection management procedures in this section are triggered as specified in other sections where the UE is
using a WLAN connection for LWA, RCLWI or LWIP.

The UE stores the current WLAN mobility set, which is a set of one or more WLAN identifier(s) (e.g. BSSID, SSID,
HESSID) in wlan-MobilitySet in VarWLAN-MobilityConfig. This WLAN mobility set can be configured and updated by
the eNB. A WLAN is considered to be inside the WLAN mobility set if its identifiers match all WLAN identifiers of at
least one entry in wlan-MobilitySet and outside the WLAN mobility set otherwise. When the UE receives a new or
updated WLAN mobility set, it initiates connection to a WLAN inside the WLAN mobility set, if not already connected
to such a WLAN, and starts WLAN status monitoring as described in 5.6.15.4. The UE can perform WLAN mobility
within the WLAN mobility set (connect or reconnect to a WLAN inside the WLAN mobility set) without any signalling
to E-UTRAN.

The UE reports the WLAN connection status information to E-UTRAN as described in 5.6.15.2. The information in this
report is based on the monitoring of WLAN connection as described in 5.6.15.4.

5.6.15.2 WLAN connection status reporting

5.6.15.2.1 General

UE EUTRAN

WLANConnectionStatusReport

Figure 5.6.15.2.1-1: WLAN connection status reporting

The purpose of this procedure is to inform E-UTRAN about the status of WLAN connection for LWA, RCLWI, or
LWIP.

5.6.15.2.2 Initiation
The UE in RRC_CONNECTED initiates the WLAN status reporting procedure when:

1> it connects successfully to a WLAN inside WLAN mobility set while T351 is running after a WLAN mobility
set change; or

1> after a lwa-WT-Counter update or after a lwip-Counter update (if success report is requested by the eNB); or

1> its connection or connection attempts to all WLAN(s) inside WLAN mobility set fails in accordance with
WLAN Status Monitoring described in 5.6.15.4; or

1> T351 expires; or

1> its WLAN connection to all WLAN(s) inside WLAN mobility set becomes temporarily unavailable; or

1> its WLAN connection to a WLAN inside the WLAN mobility set is successfully established after its previous
WLAN Connection Status Report indicating WLAN temporary suspension;

Upon initiating the procedure, the UE shall:

1> initiate transmission of the WLANConnectionStatusReport message in accordance with 5.6.15.2.3;

3GPP
Release 15 243 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.15.2.3 Actions related to transmission of WLANConnectionStatusReport message

The UE shall set the contents of the WLANConnectionStatusReport message as follows:

1> set wlan-status to status in VarWLAN-Status;

1> submit the WLANConnectionStatusReport message to lower layers for transmission, upon which the procedure
ends;

5.6.15.3 T351 Expiry (WLAN connection attempt timeout)

Upon T351 expiry, the UE shall:

1> set the status in VarWLAN-Status to failureTimeout;

1> perform WLAN connection status reporting procedure in 5.6.15.2;

1> stop WLAN status monitoring and WLAN connection attempts;

5.6.15.4 WLAN status monitoring

To perform WLAN status monitoring, the UE shall:

1> if UE is not configured with rclwi-Configuration and WLAN connection to a WLAN inside the WLAN mobility
set is successfully established or maintained after a WLAN mobility set configuration update, after a lwa-WT-
Counter update or after a lwip-Counter update:

2> set the status in VarWLAN-Status to successfulAssociation;

2> stop timer T351, if running;

2> if successReportRequested in VarWLAN-MobilityConfig is set to TRUE:

3> perform WLAN Connection Status Reporting procedure in 5.6.15.2;

1> if WLAN connection or connection attempts to all WLAN(s) inside WLAN mobility set fails:

2> if the failure is due to WLAN radio link issues:

3> set the status in VarWLAN-Status to failureWlanRadioLink;

2> else if the failure is due to UE internal problems related to WLAN:

3> set the status in VarWLAN-Status to failureWlanUnavailable;

NOTE 1: The UE internal problems related to WLAN include connection to another WLAN based on user
preferences or turning off WLAN connection or connection rejection from WLAN or other WLAN
problems.

3> remove all WLAN related measurement reporting entries within VarMeasReportList;

2> stop timer T351, if running;

2> perform WLAN Connection Status Reporting procedure in 5.6.15.2;

2> if the UE is configured with rclwi-Configuration:

3> release rclwi-Configuration and inform upper layers of a move-traffic-from-WLAN indication (see TS
24.302 [74]);

2> stop WLAN Status Monitoring and WLAN connection attempts;

1> if wlan-SuspendResumeAllowed in wlan-SuspendConfig within VarWLAN-MobilityConfig is set to TRUE:

2> if WLAN connection to all WLAN(s) inside WLAN mobility set becomes temporarily unavailable:

3GPP
Release 15 244 3GPP TS 36.331 V15.4.0 (2018-12)

3> set the status in VarWLAN-Status to suspended;

3> if wlan-SuspendTriggersStatusReport in wlan-SuspendConfig within VarWLAN-MobilityConfig is set to

TRUE:

4> trigger PDCP Status Report as specified in TS 36.323 [8];

3> perform WLAN Connection Status Reporting procedure in 5.6.15.2;

2> if the status in VarWLAN-Status in the last WLAN Connection Status Report by this UE was suspended and
WLAN connection to a WLAN inside the WLAN mobility set is successfully established:

3> set the status in VarWLAN-Status to resumed;

3> perform WLAN Connection Status Reporting procedure in 5.6.15.2;

5.6.16 RAN controlled LTE-WLAN interworking

5.6.16.1 General
The purpose of this procedure is to perform RAN-controlled LTE-WLAN interworking (RCLWI) i.e. control access
network selection and traffic steering between E-UTRAN and WLAN.

5.6.16.2 WLAN traffic steering command

The UE shall:

1> if the received rclwi-Configuration is set to setup:

2> if the command is set to steerToWLAN:

3> inform the upper layers of a move-traffic-to-WLAN indication along with the WLAN identifier lists in
steerToWLAN (see TS 24.302 [74]);

3> store steerToWLAN in wlan-MobilitySet in VarWLAN-MobilityConfig;

3> perform the WLAN status monitoring procedure as specified in 5.6.15.4 using steerToWLAN as the
WLAN mobility set;

2> else:

3> inform the upper layers of a move-traffic-from-WLAN indication (see TS 24.302 [74]);

3> clear wlan-MobilitySet in VarWLAN-MobilityConfig;

3> stop performing the WLAN status monitoring procedure as specified in 5.6.15.4;

3> delete any existing values in VarWLAN-Status;

1> else (the rclwi-Configuration is released):

2> clear wlan-MobilitySet in VarWLAN-MobilityConfig;

2> stop performing the WLAN status monitoring procedure as specified in 5.6.15.4;

2> delete any existing values in VarWLAN-Status;

2> inform the upper layers of release of the rclwi-Configuration.

3GPP
Release 15 245 3GPP TS 36.331 V15.4.0 (2018-12)

5.6.17 LTE-WLAN aggregation with IPsec tunnel

5.6.17.1 General
The WLAN resources that are used over the LWIP tunnel as described in TS 36.300 [9] established as part of LWIP
procedures are referred to as 'LWIP resources'. The purpose of this section is to specify procedures to indicate to higher
layers to initiate the establishment/ release of the LWIP tunnel over WLAN and to indicate which DRB(s) shall use the
LWIP resources.

5.6.17.2 LWIP reconfiguration

The UE shall:

1> if the received lwip-Configuration is set to release:

2> release the LWIP configuration, if configured, as described in 5.6.17.3;

1> else:

2> if lwip-MobilityConfig is included:

3> if the received lwip-MobilityConfig includes wlan-ToReleaseList:

4> for each WLAN-Identifiers included in wlan-ToReleaseList:

5> remove the WLAN-Identifiers if already part of the current wlan-MobilitySet in VarWLAN-
MobilityConfig;

3> if the received lwip-MobilityConfig includes wlan-ToAddList:

4> for each WLAN-Identifiers included in wlan-ToAddList:

5> add the WLAN-Identifiers to the current wlan-MobilitySet in VarWLAN-MobilityConfig;

3> if the received lwip-MobilityConfig includes associationTimer:

4> start timer T351 with the timer value set according to the value of associationTimer;

3> if the received lwip-MobilityConfig includes successReportRequested:

4> set successReportRequested in VarWLAN-MobilityConfig to the value of successReportRequested;

2> if tunnelConfigLWIP is included:

3> indicate to higher layers to configure the LWIP tunnel according to the received tunnelConfigLWIP, as
specified in TS 33.401 [32];

3> if lwip-Counter is included:

4> determine the LWIP-PSK based on the KeNB key and received lwip-Counter value, as specified in TS
33.401 [32];

4> forward the LWIP-PSK to upper layers for LWIP tunnel establishment;

2> start WLAN Status Monitoring as described in 5.6.15.4;

5.6.17.3 LWIP release

The UE shall:

1> delete any existing values in VarWLAN-MobilityConfig and VarWLAN-Status;

1> stop timer T351, if running;

1> release the lwip-Configuration;

3GPP
Release 15 246 3GPP TS 36.331 V15.4.0 (2018-12)

1> indicate to higher layers to stop all DRBs from using the LWIP resources;

1> indicate to higher layers to release the LWIP tunnel, as specified in TS 33.401 [32];

1> stop WLAN status monitoring and WLAN connection attempts for LWIP;

5.6.18 Void

5.6.19 Application layer measurement reporting

5.6.19.1 General

UE EUTRAN

RRC connection reconfiguration

MeasReportAppLayer

Figure 5.6.19.1-1: Application layer measurement reporting

The purpose of this procedure is to inform E-UTRAN about application layer measurement report.

5.6.19.2 Initiation
A UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when
configured with application layer measurement, i.e. when measConfigAppLayer has been configured by E-UTRAN.

Upon initiating the procedure, the UE shall:

1> if configured with application layer measurement, and SRB4 is configured, and the UE has received application
layer measurement report information from upper layers:

2> set the measReportAppLayerContainer in the MeasReportAppLayer message to the value of the application
layer measurement report information;

2> submit the MeasReportAppLayer message to lower layers for transmission via SRB4.

5.6.20 Idle Mode Measurements

5.6.20.1 General
This procedure specifies the measurements done by a UE in RRC_IDLE when it has an IDLE mode measurement
configuration and the storage of the available measurements by a UE in both RRC_IDLE and RRC_CONNECTED.

5.6.20.2 Initiation
While T331 is running, the UE shall:

1> perform the measurements in accordance with the following:

2> for each entry in measIdleCarrierListEUTRA within VarMeasIdleConfig:

3> if UE supports carrier aggregation between serving carrier and the carrier frequency and bandwidth
indicated by carrierFreq and allowedMeasBandwidth within the corresponding entry;

3GPP
Release 15 247 3GPP TS 36.331 V15.4.0 (2018-12)

4> perform measurements in the carrier frequency and bandwidth indicated by carrierFreq and
allowedMeasBandwidth within the corresponding entry;

NOTE: The fields s-NonIntraSearch in SystemInformationBlockType3 do not affect the UE measurement

procedures in IDLE mode. How the UE performs measurements in IDLE mode is up to UE
implem