5.2 System information

38.3313GPPNRProtocol specificationRadio Resource Control (RRC)Release 15TS

5.2.1 Introduction

System Information (SI) is divided into the MIB and a number of SIBs 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 are carried in SystemInformation (SI) messages, which are transmitted on the DL-SCH. Only SIBs having the same periodicity can be mapped to the same SI message. 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 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 with restrictions that each SIB is contained only in a single SI message and each SIB 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 or paging.

– 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- and NAS 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 and SIB5 (if the UE supports E-UTRA).

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; and whenever the UE does not have a valid version of a stored 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, the cellIdentity, the systemInformationAreaID, if present, and the valueTag, if present, as indicated in the si-SchedulingInfo for the SIB. 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.

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

5.2.2.2.2 SI change indication and PWS notification

A modification period is used, i.e. updated SI (other than for ETWS and CMAS) 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. 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.

UEs in RRC_IDLE or in RRC_INACTIVE shall monitor for SI change indication in its 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 on the active BWP to monitor paging, as specified in TS 38.213 [13], clause 13.

ETWS or CMAS capable UEs in RRC_IDLE or in RRC_INACTIVE 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 on the active BWP to monitor paging.

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].

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 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 sub-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 sub-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 sub-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 systemInfoModification bit of Short Message is set:

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

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_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 if the UE can acquire it 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 Kth 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> 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;

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

2> 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];

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 data reception, i.e. the broadcast and unicast 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.

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

5.2.2.3.3 Request for on demand system information

The UE shall:

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

2> trigger the lower layer to initiate the Random Access procedure on supplementary uplink in accordance with [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 sub-clause 5.2.2.3.2, immediately;

1> else if SIB1 includes si-SchedulingInfo containing si-RequestConfig and criteria to select normal uplink as defined in TS 38.321[13], 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-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;

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

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

1> else:

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

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

2> apply the timeAlignmentTimerCommon included in SIB1;

2> apply the CCCH configuration as specified in 9.1.1.2;

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

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

3> acquire the requested SI message(s) as defined in sub-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.4 Actions related to transmission of RRCSystemInfoRequest message

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

1> 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.

The UE shall submit the RRCSystemInfoRequest 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:

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

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

3> if intraFreqReselection is set to notAllowed:

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

3> else:

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

2> else:

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

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

2> apply the configuration included in the servingCellConfigCommon;

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 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), and which

– is wider than or equal to the bandwidth of the initial uplink BWP, 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), and which

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

3> if trackingAreaCode is not 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> if intraFreqReselection is set to notAllowed:

5> consider cell re-selection to other cells on the same frequency as the barred cell as not allowed, as specified in TS 38.304 [20];

4> else:

5> consider cell re-selection to other cells on the same frequency as the barred cell as allowed, as specified in 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, and which

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

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, and which

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

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 PLMN 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 uac-AccessCategory1-SelectionAssistanceInfo 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 sub-clause 5.2.2.2.1, that the UE requires to operate within the cell in accordance with sub-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 sub-clause 5.2.2.2.1, of one or several required SIB(s), in accordance with sub-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 sub-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 sub-clause 5.2.2.3.3;

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 bandwith 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> 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:

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

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

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

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;

5> 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:

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

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;

5> else:

6> apply the p-Max;

4> else:

5> apply the p-Max;

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

No UE requirements related to the contents of this SIB9 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]; and

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 intraFreqReselection in MIB is set to notAllowed:

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

3> else:

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