5.2 System information

38.3313GPPNRProtocol specificationRadio Resource Control (RRC)Release 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.2.1 Introduction

System Information (SI) is divided into the MIB and a number of SIBs and posSIBs where:

– the MIB is always transmitted on the BCH with a periodicity of 80 ms and repetitions made within 80 ms (TS 38.212 [17], clause 7.1) and it includes parameters that are needed to acquire SIB1 from the cell. The first transmission of the MIB is scheduled in subframes as defined in TS 38.213 [13], clause 4.1 and repetitions are scheduled according to the period of SSB;

– the SIB1 is transmitted on the DL-SCH with a periodicity of 160 ms and variable transmission repetition periodicity within 160 ms as specified in TS 38.213 [13], clause 13. The default transmission repetition periodicity of SIB1 is 20 ms but the actual transmission repetition periodicity is up to network implementation. For SSB and CORESET multiplexing pattern 1, SIB1 repetition transmission period is 20 ms. For SSB and CORESET multiplexing pattern 2/3, SIB1 transmission repetition period is the same as the SSB period (TS 38.213 [13], clause 13). SIB1 includes information regarding the availability and scheduling (e.g. mapping of SIBs to SI message, periodicity, SI-window size) of other SIBs with an indication whether one or more SIBs are only provided on-demand and, in that case, the configuration needed by the UE to perform the SI request. SIB1 is cell-specific SIB;

– SIBs other than SIB1 and posSIBs are carried in SystemInformation (SI) messages, which are transmitted on the DL-SCH. Only SIBs or posSIBs having the same periodicity can be mapped to the same SI message. SIBs and posSIBs are mapped to the different SI messages. Each SI message is transmitted within periodically occurring time domain windows (referred to as SI-windows with same length for all SI messages). Each SI message is associated with an SI-window and the SI-windows of different SI messages do not overlap. That is, within one SI-window only the corresponding SI message is transmitted. An SI message may be transmitted a number of times within the SI-window. Any SIB or posSIB except SIB1 can be configured to be cell specific or area specific, using an indication in SIB1. The cell specific SIB is applicable only within a cell that provides the SIB while the area specific SIB is applicable within an area referred to as SI area, which consists of one or several cells and is identified by systemInformationAreaID;

– The mapping of SIBs to SI messages is configured in schedulingInfoList and schedulingInfoList2, while the mapping of posSIBs to SI messages is configured in posSchedulingInfoList and schedulingInfoList2. SIBs and posSIBs are mapped to separate SI messages even when configured using a common schedulingInfoList2. Each SIB is contained only in a single SI message. In the case of posSIB, a posSIB carrying GNSS Generic Assistance Data for different GNSS/SBAS [49] is contained in different SI messages. Each SIB and posSIB, including a posSIB carrying GNSS Generic Assistance Data for one GNSS/SBAS, is contained at most once in that SI message;

– For a UE in RRC_CONNECTED, the network can provide system information through dedicated signalling using the RRCReconfiguration message, e.g. if the UE has an active BWP with no common search space configured to monitor system information, paging, or upon request from the UE.

– For PSCell and SCells, the network provides the required SI by dedicated signalling, i.e. within an RRCReconfiguration message. Nevertheless, the UE shall acquire MIB of the PSCell to get SFN timing of the SCG (which may be different from MCG). Upon change of relevant SI for SCell, the network releases and adds the concerned SCell. For PSCell, the required SI can only be changed with Reconfiguration with Sync.

NOTE: The physical layer imposes a limit to the maximum size a SIB can take. The maximum SIB1 or SI message size is 2976 bits.

5.2.2 System information acquisition

5.2.2.1 General UE requirements

Figure 5.2.2.1-1: System information acquisition

The UE applies the SI acquisition procedure to acquire the AS, NAS- and positioning assistance data information. The procedure applies to UEs in RRC_IDLE, in RRC_INACTIVE and in RRC_CONNECTED.

The UE in RRC_IDLE and RRC_INACTIVE shall ensure having a valid version of (at least) the MIB, SIB1 through SIB4, SIB5 (if the UE supports E-UTRA), SIB11 (if the UE is configured for idle/inactive measurements), SIB12 (if UE is capable of NR sidelink communication/discovery and is configured by upper layers to receive or transmit NR sidelink communication/discovery), and SIB13, SIB14 (if UE is capable of V2X sidelink communication and is configured by upper layers to receive or transmit V2X sidelink communication), SIB15 (if UE is configured by upper layers to report disaster roaming related information), SIB16 (if the UE is capable of slice-based cell reselection and the UE receives NSAG information for cell reselection from upper layer), SIB19 (if UE is accessing NR via NTN access).

The UE capable of MBS broadcast which is receiving or interested to receive MBS broadcast service(s) via a broadcast MRB shall ensure having a valid version of SIB20 and SIB21, regardless of the RRC state the UE is in.

The UE shall ensure having a valid version of the posSIB requested by upper layers.

5.2.2.2 SIB validity and need to (re)-acquire SIB

5.2.2.2.1 SIB validity

The UE shall apply the SI acquisition procedure as defined in clause 5.2.2.3 upon cell selection (e.g. upon power on), cell-reselection, return from out of coverage, after reconfiguration with sync completion, after entering the network from another RAT, upon receiving an indication that the system information has changed, upon receiving a PWS notification, upon receiving request (e.g., a positioning request) from upper layers; and whenever the UE does not have a valid version of a stored SIB or posSIB or a valid version of a requested SIB.

When the UE acquires a MIB or a SIB1 or an SI message in a serving cell as described in clause 5.2.2.3, and if the UE stores the acquired SIB, then the UE shall store the associated areaScope, if present, the first PLMN-Identity in the PLMN-IdentityInfoList for non-NPN-only cells or the first NPN identity (SNPN identity in case of SNPN, or PNI-NPN identity in case of PNI-NPN) in the NPN-IdentityInfoList for NPN-only cells, the cellIdentity, the systemInformationAreaID, if present, and the valueTag, if present, as indicated in the si-SchedulingInfo for the SIB. If the UE stores the acquired posSIB, then the UE shall store the associated areaScope, if present, the cellIdentity, the systemInformationAreaID, if present, the valueTag, if provided in assistanceDataSIB-Element, and the expirationTime if provided in assistanceDataSIB-Element. The UE may use a valid stored version of the SI except MIB, SIB1, SIB6, SIB7 or SIB8 e.g. after cell re-selection, upon return from out of coverage or after the reception of SI change indication. The valueTag and expirationTime for posSIB is optionally provided in assistanceDataSIB-Element, as specified in TS 37.355 [49].

A L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE can inform the interested SIB(s) to the connected L2 U2N Relay UE as defined in clause 5.8.9.8.2 and receive the SIB(s) from the L2 U2N Relay UE as defined in clause 5.8.9.8.3. A L2 U2N Remote UE in RRC_CONNECTED receives SIB1 and other SIB(s) in RRCReconfiguration message and performs on-demand SI request if required, as defined in clause 5.2.2.3.5 and 5.2.2.3.6. The L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE or RRC_CONNECTED is not required to obtain SI over Uu interface, but it may decide to perform the SI acquisition procedure over Uu interface as defined in clause 5.2.2.3 by UE implementation.

NOTE: The storage and management of the stored SIBs in addition to the SIBs valid for the current serving cell is left to UE implementation.

The UE shall:

1> delete any stored version of a SIB after 3 hours from the moment it was successfully confirmed as valid;

1> for each stored version of a SIB:

2> if the areaScope is associated and its value for the stored version of the SIB is the same as the value received in the si-SchedulingInfo for that SIB from the serving cell:

3> if the UE is NPN capable and the cell is an NPN-only cell:

4> if the first NPN identity included in the NPN-IdentityInfoList, the systemInformationAreaID and the valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the NPN identity, the systemInformationAreaID and the valueTag associated with the stored version of that SIB:

5> consider the stored SIB as valid for the cell;

3> else if the first PLMN-Identity included in the PLMN-IdentityInfoList, the systemInformationAreaID and the valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the PLMN-Identity, the systemInformationAreaID and the valueTag associated with the stored version of that SIB:

4> consider the stored SIB as valid for the cell;

2> if the areaScope is not present for the stored version of the SIB and the areaScope value is not included in the si-SchedulingInfo for that SIB from the serving cell:

3> if the UE is NPN capable and the cell is an NPN-only cell:

4> if the first NPN identity in the NPN-IdentityInfoList, the cellIdentity and valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the NPN identity, the cellIdentity and the valueTag associated with the stored version of that SIB:

5> consider the stored SIB as valid for the cell;

3> else if the first PLMN-Identity in the PLMN-IdentityInfoList, the cellIdentity and valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the PLMN-Identity, the cellIdentity and the valueTag associated with the stored version of that SIB:

4> consider the stored SIB as valid for the cell;

1> for each stored version of a posSIB:

2> if the areaScope is associated and its value for the stored version of the posSIB is the same as the value received in the posSIB-MappingInfo for that posSIB from the serving cell and the systemInformationAreaID included in the si-SchedulingInfo is identical to the systemInformationAreaID associated with the stored version of that posSIB:

3> if the valueTag (see TS 37.355 [49]) for the posSIB received from the serving cell is identical to the valueTag associated with the stored version of that posSIB; or if the expirationTime (see TS 37.355 [49]) associated with the stored posSIB has not been expired:

4> consider the stored posSIB as valid for the cell;

2> if the areaScope is not present for the stored version of the posSIB and the areaScope value is not included in the posSIB-MappingInfo for that posSIB from the serving cell and the cellIdentity for the posSIB received from the serving cell is identical to the cellIdentity associated with the stored version of that posSIB:

4> consider the stored posSIB as valid for the cell;

5.2.2.2.2 SI change indication and PWS notification

A modification period is used, i.e. updated SI message (other than SI message for ETWS, CMAS, positioning assistance data, and some NTN-specific information as specified in the field descriptions ) is broadcasted in the modification period following the one where SI change indication is transmitted. 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 SIB1, and UE is configured with eDRX, modification period boundaries are defined by SFN values for which (H-SFN * 1024 + SFN) mod m = 0.

For UEs in RRC_IDLE or RRC_INACTIVE configured to use an eDRX 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 1024 = 0.

The UE receives indications about SI modifications and/or PWS notifications using Short Message transmitted with P-RNTI over DCI (see clause 6.5). Repetitions of SI change indication may occur within preceding modification period or within preceding eDRX acquisition period. SI change indication is not applicable for SI messages containing posSIBs.

UEs in RRC_IDLE or in RRC_INACTIVE while SDT procedure is not ongoing shall monitor for SI change indication in own paging occasion every DRX cycle. UEs in RRC_CONNECTED shall monitor for SI change indication in any paging occasion at least once per modification period if the UE is provided with common search space, including pagingSearchSpace, searchSpaceSIB1 and searchSpaceOtherSystemInformation, on the active BWP to monitor paging, as specified in TS 38.213 [13], clause 13.

UEs in RRC_INACTIVE while SDT procedure is ongoing shall monitor for SI change indication in any paging occasion at least once per modification period.

During a modification period where ETWS or CMAS transmission is started or stopped, the SI messages carrying the posSIBs scheduled in posSchedulingInfoList may change, so the UE might not be able to successfully receive those posSIBs in the remainder of the current modification period and next modification period according to the scheduling information received prior to the change.

ETWS or CMAS capable UEs in RRC_IDLE or in RRC_INACTIVE while SDT procedure is not ongoing shall monitor for indications about PWS notification in its own paging occasion every DRX cycle. ETWS or CMAS capable UEs in RRC_CONNECTED shall monitor for indication about PWS notification in any paging occasion at least once every defaultPagingCycle if the UE is provided with common search space, including pagingSearchSpace, searchSpaceSIB1 and searchSpaceOtherSystemInformation, on the active BWP to monitor paging.

ETWS or CMAS capable UEs in RRC_INACTIVE while SDT procedure is ongoing shall monitor for indication about PWS notification in any paging occasion at least once every defaultPagingCycle.

For Short Message reception in a paging occasion, the UE monitors the PDCCH monitoring occasion(s) for paging as specified in TS 38.304 [20] and TS 38.213 [13].

A L2 U2N Remote UE is not required to monitor paging occasion for SI modifications and/or PWS notifications. It obtains the updated system information and SIB6/7/8 from the connected L2 U2N Relay UE as defined in clause 5.8.9.9.3.

If the UE receives a Short Message, the UE shall:

1> if the UE is ETWS capable or CMAS capable, the etwsAndCmasIndication bit of Short Message is set, and the UE is provided with searchSpaceSIB1 and searchSpaceOtherSystemInformation on the active BWP or the initial BWP:

2> immediately re-acquire the SIB1;

2> if the UE is ETWS capable and si-SchedulingInfo includes scheduling information for SIB6:

3> acquire SIB6, as specified in clause 5.2.2.3.2, immediately;

2> if the UE is ETWS capable and si-SchedulingInfo includes scheduling information for SIB7:

3> acquire SIB7, as specified in clause 5.2.2.3.2, immediately;

2> if the UE is CMAS capable and si-SchedulingInfo includes scheduling information for SIB8:

3> acquire SIB8, as specified in clause 5.2.2.3.2, immediately;

NOTE: In case SIB6, SIB7, or SIB8 overlap with a measurement gap it is left to UE implementation how to immediately acquire SIB6, SIB7, or SIB8.

1> if the UE is not configured with an eDRX cycle longer than the modification period and the systemInfoModification bit of Short Message is set:

2> apply the SI acquisition procedure as defined in clause 5.2.2.3 from the start of the next modification period;

1> if the UE is configured with an RRC_IDLE eDRX cycle longer than the modification period and the systemInfoModification-eDRX bit of Short Message is set:

2> apply the SI acquisition procedure as defined in clause 5.2.2.3 from the start of the next eDRX acquisition period boundary.

5.2.2.3 Acquisition of System Information

5.2.2.3.1 Acquisition of MIB and SIB1

The UE shall:

1> apply the specified BCCH configuration defined in 9.1.1.1;

1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or

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

2> acquire the MIB, which is scheduled as specified in TS 38.213 [13];

2> if the UE is unable to acquire the MIB;

3> perform the actions as specified in clause 5.2.2.5;

2> else:

3> perform the actions specified in clause 5.2.2.4.1.

1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured by searchSpaceSIB1 and pagingSearchSpace and has received an indication about change of system information; or

1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured by searchSpaceSIB1 and the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1, and, UE has not acquired SIB1 in current modification period; or

1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured by searchSpaceSIB1, and, the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1, and, si-BroadcastStatus for the required SIB(s) or posSI-BroadcastStatus for the required posSIB(s) is set to notbroadcasting in acquired SIB1 in current modification period; or

1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or

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

2> if ssb-SubcarrierOffset indicates SIB1 is transmitted in the cell (TS 38.213 [13]) and if SIB1 acquisition is required for the UE:

3> acquire the SIB1, which is scheduled as specified in TS 38.213 [13];

3> if the UE is unable to acquire the SIB1:

4> perform the actions as specified in clause 5.2.2.5;

3> else:

4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2.

2> else if SIB1 acquisition is required for the UE and ssb-SubcarrierOffset indicates that SIB1 is not scheduled in the cell:

3> perform the actions as specified in clause 5.2.2.5.

NOTE: The UE in RRC_CONNECTED is only required to acquire broadcasted SIB1 and MBS broadcast if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e., the broadcast and unicast/MBS multicast beams are quasi co-located. The UE in RRC_INACTIVE state while SDT procedure is ongoing, is only required to acquire broadcasted SIB1 and MIB if the UE can acquire them without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located.

5.2.2.3.2 Acquisition of an SI message

For SI message acquisition PDCCH monitoring occasion(s) are determined according to searchSpaceOtherSystemInformation. If searchSpaceOtherSystemInformation is set to zero, PDCCH monitoring occasions for SI message reception in SI-window are same as PDCCH monitoring occasions for SIB1 where the mapping between PDCCH monitoring occasions and SSBs is specified in TS 38.213[13]. If searchSpaceOtherSystemInformation is not set to zero, PDCCH monitoring occasions for SI message are determined based on search space indicated by searchSpaceOtherSystemInformation. PDCCH monitoring occasions for SI message which are not overlapping with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are sequentially numbered from one in the SI window. The [x×N+K]^th PDCCH monitoring occasion (s) for SI message in SI-window corresponds to the K^th transmitted SSB, where x = 0, 1, …X-1, K = 1, 2, …N, N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 and X is equal to CEIL(number of PDCCH monitoring occasions in SI-window/N). The actual transmitted SSBs are sequentially numbered from one in ascending order of their SSB indexes. The UE assumes that, in the SI window, PDCCH for an SI message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB and thus the selection of SSB for the reception SI messages is up to UE implementation.

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:

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 schedulingInfoList in si-SchedulingInfo in SIB1;

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

3> the SI-window starts at the slot #a, where a = x mod N, in the radio frame for which SFN mod T = FLOOR(x/N), where T is the si-Periodicity of the concerned SI message and N is the number of slots in a radio frame as specified in TS 38.213 [13];

2> else if the concerned SI message is configured in the schedulingInfoList2;

3> determine the integer value x = (si-WindowPosition -1) × w, where w is the si-WindowLength;

2> else if the concerned SI message is configured in the posSchedulingInfoList and offsetToSI-Used is not configured:

3> create a concatenated list of SI messages by appending the posSchedulingInfoList in posSI-SchedulingInfo in SIB1 to schedulingInfoList in si-SchedulingInfo in SIB1;

3> for the concerned SI message, determine the number n which corresponds to the order of entry in the concatenated list;

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

3> the SI-window starts at the slot #a, where a = x mod N, in the radio frame for which SFN mod T = FLOOR(x/N), where T is the posSI-Periodicity of the concerned SI message and N is the number of slots in a radio frame as specified in TS 38.213 [13];

2> else if the concerned SI message is configured by the posSchedulingInfoList and offsetToSI-Used is configured:

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 SIB1;

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 SIB1;

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

3> the SI-window starts at the slot #a, where a = x mod N, in the radio frame for which SFN mod T = FLOOR(x/N) +8, where T is the posSI-Periodicity of the concerned SI message and N is the number of slots in a radio frame as specified in TS 38.213 [13];

1> receive the PDCCH containing the scheduling RNTI, i.e. SI-RNTI in the PDCCH monitoring occasion(s) for SI message acquisition, 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;

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 in the current modification period;

NOTE 1: The UE is only required to acquire broadcasted SI message if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e. the broadcast and unicast/MBS multicast beams are quasi co-located.

NOTE 2: The UE is not required to monitor PDCCH monitoring occasion(s) corresponding to each transmitted SSB in SI-window.

NOTE 3: If the concerned SI message was not received in the current modification period, handling of SI message acquisition is left to UE implementation.

NOTE 4: A UE in RRC_CONNECTED may stop the PDCCH monitoring during the SI window for the concerned SI message when the requested SIB(s) are acquired.

NOTE 5: A UE capable of NR sidelink communication/discovery and configured by upper layers to perform NR sidelink communication/discovery on a frequency, may acquire SIB12 or SystemInformationBlockType28 from a cell other than current serving cell (for RRC_INACTIVE or RRC_IDLE) or current PCell (for RRC_CONNECTED), if SIB12 of current serving cell (for RRC_INACTIVE or RRC_IDLE) or current PCell (for RRC_CONNECTED) does not provide configuration for NR sidelink communication/discovery for the frequency, and if the other cell providing configuration for NR sidelink communication/discovery for the frequency meets the S-criteria as defined in TS 38.304 [20] or TS 36.304 [27].

1> perform the actions for the acquired SI message as specified in clause 5.2.2.4.

5.2.2.3.3 Request for on demand system information

The UE shall, while SDT procedure is not ongoing:

1> if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL and criteria to select supplementary uplink as defined in TS 38.321[3], clause 5.1.1 is met:

2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfigSUL corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

2> if acknowledgement for SI request is received from lower layers:

3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately;

1> else if the UE is a RedCap UE and if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing si-RequestConfigRedCap and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met:

2> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfigRedcap corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

2> if acknowledgement for SI request is received from lower layers:

3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately;

1> else:

2> if the UE is not a RedCap UE and if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met; or

2> if the UE is a RedCap UE and if initialUplinkBWP-RedCap is not configured in UplinkConfigCommonSIB and if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met:

3> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in si-RequestConfig corresponding to the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

3> if acknowledgement for SI request is received from lower layers:

4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately;

2> else:

3> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1;

3> apply the default MAC Cell Group configuration as specified in 9.2.2;

3> apply the timeAlignmentTimerCommon included in SIB1;

3> apply the CCCH configuration as specified in 9.1.1.2;

3> initiate transmission of the RRCSystemInfoRequest message in accordance with 5.2.2.3.4;

3> if acknowledgement for RRCSystemInfoRequest message is received from lower layers:

4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately;

1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers:

2> reset MAC;

2> if SI request is based on RRCSystemInfoRequest message:

3> release RLC entity for SRB0.

NOTE: After RACH failure for SI request it is up to UE implementation when to retry the SI request.

5.2.2.3.3a Request for on demand positioning system information

The UE shall, while SDT procedure is not ongoing:

1> if SIB1 includes posSI-SchedulingInfo containing posSI-RequestConfigSUL and criteria to select supplementary uplink as defined in TS 38.321[3], clause 5.1.1 is met:

2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in posSI-RequestConfigSUL corresponding to the SI message(s) that the UE requires to operate within the cell, and for which posSI-BroadcastStatus is set to notBroadcasting;

2> if acknowledgement for SI request is received from lower layers:

3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately;

1> else if the UE is a RedCap UE and if initialUplinkBWP-RedCap is configured in UplinkConfigCommonSIB and if SIB1 includes posSI-SchedulingInfo containing posSI-RequestConfigRedCap and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met:

2> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in posSI-RequestConfigRedCap corresponding to the SI message(s) that the UE upper layers require for positioning operations, and for which posSI-BroadcastStatus is set to notBroadcasting;

2> if acknowledgement for SI request is received from lower layers:

3> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately;

1> else:

2> if the UE is not a RedCap UE and if SIB1 includes posSI-SchedulingInfo containing posSI-RequestConfig and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met; or

2> if the UE is a RedCap UE and if initialUplinkBWP-RedCap is not configured in UplinkConfigCommonSIB and if SIB1 includes posSI-SchedulingInfo containing posSI-RequestConfig and criteria to select normal uplink as defined in TS 38.321[3], clause 5.1.1 is met:

3> trigger the lower layer to initiate the Random Access procedure on normal uplink in accordance with TS 38.321 [3] using the PRACH preamble(s) and PRACH resource(s) in posSI-RequestConfig corresponding to the SI message(s) that the UE upper layers require for positioning operations , and for which posSI-BroadcastStatus is set to notBroadcasting;

3> if acknowledgement for SI request is received from lower layers:

4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately;

2> else:

3> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1;

3> apply the default MAC Cell Group configuration as specified in 9.2.2;

3> apply the timeAlignmentTimerCommon included in SIB1;

3> apply the CCCH configuration as specified in 9.1.1.2;

3> initiate transmission of the RRCSystemInfoRequest message with rrcPosSystemInfoRequest in accordance with 5.2.2.3.4;

3> if acknowledgement for RRCSystemInfoRequest message with rrcPosSystemInfoRequest is received from lower layers:

4> acquire the requested SI message(s) as defined in clause 5.2.2.3.2, immediately;

1> if cell reselection occurs while waiting for the acknowledgment for SI request from lower layers:

2> reset MAC;

2> if SI request is based on RRCSystemInfoRequest message with rrcPosSystemInfoRequest:

3> release RLC entity for SRB0.

NOTE: After RACH failure for SI request it is up to UE implementation when to retry the SI request.

5.2.2.3.4 Actions related to transmission of RRCSystemInfoRequest message

The UE shall set the contents of RRCSystemInfoRequest message as follows:

1> if the procedure is triggered to request the required SI message(s) other than positioning:

2> set the requested-SI-List to indicate the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting;

1> else if the procedure is triggered to request the required SI message(s) for positioning:

2> set the requestedPosSI-List to indicate the SI message(s) that the UE upper layers require for positioning operations, and for which posSI-BroadcastStatus is set to notBroadcasting.

The UE shall submit the RRCSystemInfoRequest message to lower layers for transmission.

5.2.2.3.5 Acquisition of SIB(s) or posSIB(s) in RRC_CONNECTED

The UE shall:

1> if the UE is in RRC_CONNECTED with an active BWP not configured with common search space with the field searchSpaceOtherSystemInformation and the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1, or

1> if the UE is in RRC_CONNECTED and acting as a L2 U2N Remote UE and the UE has not stored a valid version of a SIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) in accordance with clause 5.2.2.1:

2> for the SI message(s) that, according to the si-SchedulingInfo or posSI-SchedulingInfo in the stored SIB1, contain at least one required SIB or requested posSIB:

3> if onDemandSIB-Request is configured and timer T350 is not running:

4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6;

4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer;

1> else if the UE is in RRC_CONNECTED with an active BWP configured with common search space with the field searchSpaceOtherSystemInformation and the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1:

2> for the SI message(s) that, according to the si-SchedulingInfo in the stored SIB1, contain at least one required SIB and for which si-BroadcastStatus is set to broadcasting:

3> acquire the SI message(s) as defined in clause 5.2.2.3.2;

2> for the SI message(s) that, according to the si-SchedulingInfo in the stored SIB1, contain at least one required SIB and for which si-BroadcastStatus is set to notBroadcasting:

3> if onDemandSIB-Request is configured and timer T350 is not running:

4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6;

4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer;

4> acquire the requested SI message(s) corresponding to the requested SIB(s) as defined in clause 5.2.2.3.2.

2> for the SI message(s) that, according to the posSI-SchedulingInfo in the stored SIB1, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to broadcasting:

3> acquire the SI message(s) as defined in clause 5.2.2.3.2;

2> for the SI message(s) that, according to the posSI-SchedulingInfo in the stored SIB1, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to notBroadcasting:

3> if onDemandSIB-Request is configured and timer T350 is not running:

4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6;

4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer;

4> acquire the requested SI message(s) corresponding to the requested posSIB(s) as defined in clause 5.2.2.3.2.

NOTE: UE may include on demand request for SIB and/or posSIB(s) in the same DedicatedSIBRequest message.

5.2.2.3.6 Actions related to transmission of DedicatedSIBRequest message

The UE shall set the contents of DedicatedSIBRequest message as follows:

1> if the procedure is triggered to request the required SIB(s):

2> include requestedSIB-List in the onDemandSIB-RequestList to indicate the requested SIB(s);

1> if the procedure is triggered to request the required posSIB(s):

2> include requestedPosSIB-List in the onDemandSIB-RequestList to indicate the requested posSIB(s).

The UE shall submit the DedicatedSIBRequest message to lower layers for transmission.

5.2.2.4 Actions upon receipt of System Information

5.2.2.4.1 Actions upon reception of the MIB

Upon receiving the MIB the UE shall:

1> store the acquired MIB;

1> if the UE is in RRC_IDLE or in RRC_INACTIVE, or if the UE is in RRC_CONNECTED while T311 is running; and

1> if the access is not for NTN or the UE is not capable of NTN:

2> if the cellBarred in the acquired MIB is set to barred:

3> if the UE is a RedCap UE and ssb-SubcarrierOffset indicates SIB1 is transmitted in the cell (TS 38.213 [13]):

4> acquire the SIB1, which is scheduled as specified in TS 38.213 [13];

3> consider the cell as barred in accordance with TS 38.304 [20];

3> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304 [20];

2> else:

3> apply the received systemFrameNumber, pdcch-ConfigSIB1, subCarrierSpacingCommon, ssb-SubcarrierOffset and dmrs-TypeA-Position.

NOTE: A UE capable of NTN access should acquire SIB1 to determine whether the cell is an NTN cell.

5.2.2.4.2 Actions upon reception of the SIB1

Upon receiving the SIB1 the UE shall:

1> store the acquired SIB1;

1> if the UE is a RedCap UE and it is in RRC_IDLE or in RRC_INACTIVE, or if the RedCap UE is in RRC_CONNECTED while T311 is running:

2> if intraFreqReselectionRedCap is not present in SIB1:

3> consider the cell as barred in accordance with TS 38.304 [20];

3> perform barring as if intraFreqReselectionRedCap is set to allowed;

2> else:

3> if the cellBarredRedCap1Rx is present in the acquired SIB1 and is set to barred and the UE is equipped with 1 Rx branch; or

3> if the cellBarredRedCap2Rx is present in the acquired SIB1 and is set to barred and the UE is equipped with 2 Rx branches; or

3> if the halfDuplexRedCapAllowed is not present in the acquired SIB1 and the UE supports only half-duplex FDD operation:

4> consider the cell as barred in accordance with TS 38.304 [20];

4> perform barring based on intraFreqReselectionRedCap as specified in TS 38.304 [20];

1> if the cellAccessRelatedInfo contains an entry of a selected SNPN or PLMN and in case of PLMN the UE is either allowed or instructed to access the PLMN via a cell for which at least one CAG ID is broadcast:

2> in the remainder of the procedures use npn-IdentityList, trackingAreaCode, and cellIdentity for the cell as received in the corresponding entry of npn-IdentityInfoList containing the selected PLMN or SNPN;

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

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

1> if in RRC_CONNECTED while T311 is not running:

2> disregard the frequencyBandList, if received, while in RRC_CONNECTED;

2> forward the cellIdentity to upper layers;

2> forward the trackingAreaCode to upper layers, if included;

2> forward the trackingAreaList to upper layers, if included;

2> forward the received posSIB-MappingInfo to upper layers, if included;

2> apply the configuration included in the servingCellConfigCommon;

2> if the UE has a stored valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, that the UE requires to operate within the cell in accordance with clause 5.2.2.1:

3> use the stored version of the required SIB or posSIB;

2> else:

3> acquire the required SIB or posSIB requested by upper layer as defined in clause 5.2.2.3.5;

NOTE: Void.

1> else:

2> if the UE supports one or more of the frequency bands indicated in the frequencyBandList for downlink for TDD, or one or more of the frequency bands indicated in the frequencyBandList for uplink for FDD, and they are not downlink only bands, and

2> if the UE is IAB-MT or supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for a supported band in the downlink for TDD, or a supported band in uplink for FDD, and

2> if the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1 [15] and TS 38.101-2 [39]) which

– is smaller than or equal to the carrierBandwidth (indicated in uplinkConfigCommon for the SCS of the initial uplink BWP or, for RedCap UE, of the RedCap-specific initial uplink BWP if configured), and which

– is wider than or equal to the bandwidth of the initial uplink BWP or, for RedCap UE, of the RedCap-specific initial uplink BWP if configured, and

2> if the UE supports a downlink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1 [15] and TS 38.101-2 [39]) which

– is smaller than or equal to the carrierBandwidth (indicated in downlinkConfigCommon for the SCS of the initial downlink BWP or, for RedCap UE, of the RedCap-specific initial downlink BWP if configured), and which

– is wider than or equal to the bandwidth of the initial downlink BWP or, for RedCap UE, of the RedCap-specific initial downlink BWP if configured, and

2> if frequencyShift7p5khz is present and the UE supports corresponding 7.5kHz frequency shift on this band; or frequencyShift7p5khz is not present:

3> if neither trackingAreaCode nor trackingAreaList is provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list:

4> consider the cell as barred in accordance with TS 38.304 [20];

4> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304 [20];

3> else if UE is IAB-MT and if iab-Support is not provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list nor the selected SNPN nor the registered SNPN:

4> consider the cell as barred for IAB-MT in accordance with TS 38.304 [20];

3> else:

4> apply a supported uplink channel bandwidth with a maximum transmission bandwidth which

– is contained within the carrierBandwidth indicated in uplinkConfigCommon for the SCS of the initial uplink BWP or, for RedCap UEs, RedCap-specific initial uplink BWP, if configured, and which

– is wider than or equal to the bandwidth of the initial BWP for the uplink or, for a RedCap UE, of the RedCap-specific initial uplink BWP if configured;

4> apply a supported downlink channel bandwidth with a maximum transmission bandwidth which

– is contained within the carrierBandwidth indicated in downlinkConfigCommon for the SCS of the initial downlink BWP or, for RedCap UEs, RedCap-specific initial downlink BWP, if configured, and which

– is wider than or equal to the bandwidth of the initial BWP for the downlink or, for a RedCap UE, of the RedCap-specific initial downlink BWP if configured;

4> select the first frequency band in the frequencyBandList, for FDD from frequencyBandList for uplink, or for TDD from frequencyBandList for downlink, which the UE supports and for which the UE supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxList, if present;

4> forward the cellIdentity to upper layers;

4> forward the trackingAreaCode to upper layers;

4> forward the trackingAreaList to upper layers, if included;

4> forward the received posSIB-MappingInfo to upper layers, if included;

4> forward the PLMN identity or SNPN identity or PNI-NPN identity to upper layers;

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

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

6> initiate an RNA update as specified in 5.3.13.8;

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

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

4> forward the UAC-AccessCategory1-SelectionAssistanceInfo or UAC-AC1-SelectAssistInfo for the selected PLMN/SNPN to upper layers, if present and set to a, b or c;

4> if the UE is in SNPN access mode:

5> forward the imsEmergencySupportForSNPN indicators with the corresponding SNPN identities to upper layers, if present;

4> apply the configuration included in the servingCellConfigCommon;

4> apply the specified PCCH configuration defined in 9.1.1.3;

4> if the UE has a stored valid version of a SIB, in accordance with clause 5.2.2.2.1, that the UE requires to operate within the cell in accordance with clause 5.2.2.1:

5> use the stored version of the required SIB;

4> if the UE has not stored a valid version of a SIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s), in accordance with clause 5.2.2.1:

5> for the SI message(s) that, according to the si-SchedulingInfo, contain at least one required SIB and for which si-BroadcastStatus is set to broadcasting:

6> acquire the SI message(s) as defined in clause 5.2.2.3.2;

5> for the SI message(s) that, according to the si-SchedulingInfo, contain at least one required SIB and for which si-BroadcastStatus is set to notBroadcasting:

6> trigger a request to acquire the SI message(s) as defined in clause 5.2.2.3.3;

4> if the UE has a stored valid version of a posSIB, in accordance with clause 5.2.2.2.1, of one or several required posSIB(s), in accordance with clause 5.2.2.1:

5> use the stored version of the required posSIB;

4> if the UE has not stored a valid version of a posSIB, in accordance with clause 5.2.2.2.1, of one or several posSIB(s) in accordance with clause 5.2.2.1:

5> for the SI message(s) that, according to the posSI-SchedulingInfo, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to broadcasting:

6> acquire the SI message(s) as defined in clause 5.2.2.3.2;

5> for the SI message(s) that, according to the posSI-SchedulingInfo, contain at least one requested posSIB for which posSI-BroadcastStatus is set to notBroadcasting:

6> trigger a request to acquire the SI message(s) as defined in clause 5.2.2.3.3a;

4> apply the first listed additionalSpectrumEmission which it supports among the values included in NR-NS-PmaxList within frequencyBandList in uplinkConfigCommon for FDD or in downlinkConfigCommon for TDD;

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

5> apply the additionalPmax for UL;

4> else:

5> apply the p-Max in uplinkConfigCommon for UL;

4> if supplementaryUplink is present in servingCellConfigCommon; and

4> if the UE supports one or more of the frequency bands indicated in the frequencyBandList for the supplementaryUplink; and

4> if the UE supports at least one additionalSpectrumEmission in the NR-NS-PmaxList for a supported supplementary uplink band; and

4> if the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101-1 [15] and TS 38.101-2 [39]) which

– is smaller than or equal to the carrierBandwidth (indicated in supplementaryUplink for the SCS of the initial uplink BWP), and which

– is wider than or equal to the bandwidth of the initial uplink BWP of the SUL:

5> consider supplementary uplink as configured in the serving cell;

5> select the first frequency band in the frequencyBandList for the supplementaryUplink which the UE supports and for which the UE supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxList, if present;

5> apply a supported supplementary uplink channel bandwidth with a maximum transmission bandwidth which

– is contained within the carrierBandwidth (indicated in supplementaryUplink for the SCS of the initial uplink BWP), and which

– is wider than or equal to the bandwidth of the initial BWP of the SUL;

5> apply the first listed additionalSpectrumEmission which it supports among the values included in NR-NS-PmaxList within frequencyBandList for the supplementaryUplink;

5> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within NR-NS-PmaxList for the supplementaryUplink:

6> apply the additionalPmax in supplementaryUplink for SUL;

5> else:

6> apply the p-Max in supplementaryUplink for SUL;

2> else:

3> consider the cell as barred in accordance with TS 38.304 [20]; and

3> perform barring as if intraFreqReselection is set to notAllowed;

5.2.2.4.3 Actions upon reception of SIB2

Upon receiving SIB2, the UE shall:

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

2> if, for the entry in frequencyBandList with the same index as the frequency band selected in clause 5.2.2.4.2, the UE supports at least one additionalSpectrumEmission in the NR-NS-PmaxList within the frequencyBandList:

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

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

4> apply the additionalPmax;

3> else:

4> apply the p-Max;

3> if the UE selects a frequency band (from the procedure in clause 5.2.2.4.2) for the supplementary uplink:

4> if, for the entry in frequencyBandListSUL with the same index as the frequency band selected in clause 5.2.2.4.2, the UE supports at least one additionalSpectrumEmission in the NR-NS-PmaxList within the frequencyBandListSUL:

5> apply the first listed additionalSpectrumEmission which it supports among the values included in NR-NS-PmaxList within frequencyBandListSUL;

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

6> apply the additionalPmax;

5> else:

6> apply the p-Max;

4> else:

5> apply the p-Max.

2> else:

3> apply the p-Max;

5.2.2.4.4 Actions upon reception of SIB3

No UE requirements related to the contents of this SIB3 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.4.5 Actions upon reception of SIB4

Upon receiving SIB4 the UE shall:

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

2> for each entry in the interFreqCarrierFreqList:

3> if the UE is not a RedCap UE; or

3> if the UE is a RedCap UE and the interFreqCarrierFreqList-v1700 is absent; or

3> if the UE is a RedCap UE and redCapAccessAllowed is present in interFreqCarrierFreqList-v1700:

4> select the first frequency band in the frequencyBandList, and frequencyBandListSUL, if present, which the UE supports and for which the UE supports at least one of the additionalSpectrumEmission values in NR-NS-PmaxList, if present:

4> if, the frequency band selected by the UE in frequencyBandList to represent a non-serving NR carrier frequency is not a downlink only band:

5> if, for the selected frequency band, the UE supports at least one additionalSpectrumEmission in the NR-NS-PmaxList within the frequencyBandList:

6> apply the first listed additionalSpectrumEmission which it supports among the values included in NR-NS-PmaxList within frequencyBandList;

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

7> apply the additionalPmax;

6> else:

7> apply the p-Max;

6> if frequencyBandListSUL is present in SIB4 and, for the frequency band selected in frequencyBandListSUL, the UE supports at least one additionalSpectrumEmission in the NR-NS-PmaxList within FrequencyBandListSUL:

7> apply the first listed additionalSpectrumEmission which it supports among the values included in NR-NS-PmaxList within frequencyBandListSUL;

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

8> apply the additionalPmax;

7> else:

8> apply the p-Max;

6> else:

7> apply the p-Max;

5> else:

6> apply the p-Max;

1> if in RRC_IDLE or RRC_INACTIVE, and T331 is running:

2> perform the actions as specified in 5.7.8.1a;

5.2.2.4.6 Actions upon reception of SIB5

No UE requirements related to the contents of this SIB5 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.4.7 Actions upon reception of SIB6

Upon receiving the SIB6 the UE shall:

1> forward the received warningType, messageIdentifier and serialNumber to upper layers;

5.2.2.4.8 Actions upon reception of SIB7

Upon receiving the SIB7 the UE shall:

1> if there is no current value for messageIdentifier and serialNumber for SIB7; or

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

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

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(s);

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

3> stop reception of SIB7;

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

2> else:

3> store the received warningMessageSegment;

3> continue reception of SIB7;

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

2> assemble the warning message from the received warningMessageSegment(s);

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

2> stop reception of SIB7;

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

1> else:

2> store the received warningMessageSegment;

2> continue reception of SIB7;

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

5.2.2.4.9 Actions upon reception of SIB8

Upon receiving the SIB8 the UE shall:

1> if the SIB8 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 SIB8;

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 geographical area coordinates (if any) for this messageIdentifier and serialNumber and delete all stored information held for it;

3> continue reception of SIB8;

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 SIB8;

The UE should discard warningMessageSegment and warningAreaCoordinatesSegment (if any) and the associated values of messageIdentifier and serialNumber for SIB8 if the complete warning message and the geographical 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.4.10 Actions upon reception of SIB9

Upon receiving SIB9 with referenceTimeInfo, the UE may perform the related actions except for the action of ignoring all further referenceTimeInfo received in SIB9 as specified in clause 5.7.1.3.

5.2.2.4.11 Actions upon reception of SIB10

Upon receiving SIB10, the UE shall:

1> Forward the HRNN-list entries with the corresponding PNI-NPN and SNPN identities to upper layers;

5.2.2.4.12 Actions upon reception of SIB11

Upon receiving SIB11, the UE shall:

1> if in RRC_IDLE or RRC_INACTIVE, and T331 is running:

2> perform the actions as specified in 5.7.8.1a;

5.2.2.4.13 Actions upon reception of SIB12

Upon receiving SIB12, the UE shall:

1> if the UE has stored at least one segment of SIB12 and the value tag of SIB12 has changed since a previous segment was stored:

2> discard all stored segments;

1> store the segment;

1> if all segments have been received:

2> assemble SIB12-IEs from the received segments;

2> if sl-FreqInfoList is included in sl-ConfigCommonNR:

3> if configured to receive NR sidelink communication:

4> use the resource pool(s) indicated by sl-RxPool for NR sidelink communication reception, as specified in 5.8.7;

3> if configured to transmit NR sidelink communication:

4> use the resource pool(s) indicated by sl-TxPoolSelectedNormal, or sl-TxPoolExceptional for NR sidelink communication transmission, as specified in 5.8.8;

4> perform CBR measurement on the transmission resource pool(s) indicated by sl-TxPoolSelectedNormal or sl-TxPoolExceptional for NR sidelink communication transmission, as specified in 5.5.3.1;

4> use the synchronization configuration parameters for NR sidelink communication on frequencies included in sl-FreqInfoList, as specified in 5.8.5;

3> if configured to receive NR sidelink discovery:

4> use the resource pool(s) indicated by sl-DiscRxPool or sl-RxPool for NR sidelink discovery reception, as specified in 5.8.13.2;

3> if configured to transmit NR sidelink discovery:

4> use the resource pool(s) indicated by sl-DiscTxPoolSelected, sl-TxPoolExceptional or sl-TxPoolSelectedNormal for NR sidelink discovery transmission, as specified in 5.8.13.3;

4> perform CBR measurement on the transmission resource pool(s) indicated by sl-TxPoolSelectedNormal, sl-DiscTxPoolSelected or sl-TxPoolExceptional for NR sidelink discovery transmission, as specified in 5.5.3.1;

4> use the synchronization configuration parameters for NR sidelink discovery on frequencies included in sl-FreqInfoList, as specified in 5.8.5;

2> if sl-RadioBearerConfigList or sl-RLC-BearerConfigList is included in sl-ConfigCommonNR:

3> perform sidelink DRB addition/modification/release as specified in 5.8.9.1a.1/5.8.9.1a.2;

2> if sl-MeasConfigCommon is included in sl-ConfigCommonNR:

3> store the NR sidelink measurement configuration.

2> if sl-DRX-ConfigCommonGC-BC is included in SIB12-IEs:

3> store the NR sidelink DRX configuration and configure lower layers to perform sidelink DRX operation for groupcast and broadcast as specified in TS 38.321 [3].

1> if the UE is acting as L2 U2N Remote UE:

2> if the ue-TimersAndConstantsRemoteUE is included in SIB12:

3> use values for timers T300, T301 and T319 as included in the ue-TimersAndConstantsRemoteUE received in SIB12;

2> else:

3> use values for timers T300, T301 and T319 as included in the ue-TimersAndConstants received in SIB1;

The UE should discard any stored segments for SIB12 if the complete SIB12 has not been assembled within a period of 3 hours. The UE shall discard any stored segments for SIB12 upon cell (re-)selection.

5.2.2.4.14 Actions upon reception of SIB13

Upon receiving SIB13, the UE shall perform the actions upon reception of SystemInformationBlockType21 as specified in 5.2.2.28 in TS 36.331 [10].

5.2.2.4.15 Actions upon reception of SIB14

Upon receiving SIB14, the UE shall perform the actions upon reception of SystemInformationBlockType26 as specified in 5.2.2.33 in TS 36.331 [10].

5.2.2.4.16 Actions upon reception of SIBpos

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

5.2.2.4.17 Actions upon reception of SIB15

Upon receiving SIB15, the UE shall:

1> forward the applicable disaster roaming information for each PLMN sharing the cell to upper layers.

5.2.2.4.18 Actions upon reception of SIB16

Upon receiving SIB16 with cell reselection priorities for slicing, the UE shall perform the actions as specified in TS 38.304 [20].

5.2.2.4.19 Actions upon reception of SIB17

Upon receiving SIB17, the UE shall:

1> if the UE has stored at least one segment of SIB17 and the value tag of SIB17 has changed since a previous segment was stored:

2> discard all stored segments;

1> store the segment;

1> if all segments have been received:

2> assemble SIB17-IEs from the received segments.

The UE should discard any stored segments for SIB17 if the complete SIB17 has not been assembled within a period of 3 hours. The UE shall discard any stored segments for SIB17 upon cell (re-) selection.

5.2.2.4.20 Actions upon reception of SIB18

Upon receiving SIB18, the UE shall:

1> forward the Group IDs for Network selection (GINs) in SIB18 with the corresponding SNPN identities to upper layers;

5.2.2.4.21 Actions upon reception of SIB19

Upon receiving SIB19, the UE shall:

1> start or restart T430 for serving cell with the timer value set to ntn-UlSyncValidityDuration from the subframe indicated by epochTime;

NOTE: UE should attempt to re-acquire SIB19 before the end of the duration indicated by ntn-UlSyncValidityDuration and epochTime by UE implementation.

5.2.2.4.22 Actions upon reception of SIB20

No UE requirements related to the contents of SIB20 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.4.23 Actions upon reception of SIB21

No UE requirements related to the contents of SIB21 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.5 Essential system information missing

The UE shall:

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

2> if the UE is unable to acquire the MIB:

3> consider the cell as barred in accordance with TS 38.304 [20];

3> perform barring as if intraFreqReselection is set to allowed;

2> else if the UE is unable to acquire the SIB1:

3> consider the cell as barred in accordance with TS 38.304 [20];

3> if the UE is a RedCap UE:

4> peform barring as if intraFreqReselectionRedCap is set to allowed;

3> else:

4> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304 [20].

5.2.2.6 T430 expiry

The UE shall:

1> if T430 for serving cell expires and if in RRC_CONNECTED:

2> inform lower layers that UL synchronisation is lost;

2> acquire SIB19 as defined in clause 5.2.2.3.2;

2> upon successful acquisition of SIB19:

3> inform lower layers that UL synchronisation is obtained;