Content for TS 38.331 Word version: 17.3.0

1… 4… 5… 5.2.2.4… 5.3… 5.3.3… 5.3.5… 5.3.5.5… 5.3.5.6… 5.3.5.7… 5.3.5.13… 5.3.6… 5.3.8… 5.3.13… 5.3.14… 5.4… 5.5… 5.5.3… 5.5.4… 5.5.5… 5.5a… 5.7… 5.7.4… 5.7.8… 5.8… 5.8.9… 5.8.10… 5.8.11… 5.9… 6… 6.2.2… 6-2-2-25… 6.3… 6.3.2… 6-3-2-27… 6-3-2-49… 6-3-2-73… 6-3-2-95… 6-3-2-108… 6-3-2-134… 6-3-2-162… 6-3-2-188… 6-3-2-213… 6-3-2-243… 6-3-2-271… 6-3-2-297… 6.3.3… 6-3-3-25… 6-3-3-51… 6.3.4… 6.3.5… 6-3-5-25… 6.3.6… 6.4… 7… 9… 11… A… A.4… B…

5.1 General 5.1.1 Introduction 5.1.2 General requirements 5.1.3 Requirements for UE in MR-DC 5.2 System information 5.2.1 Introduction 5.2.2 System information acquisition 5.2.2.1 General UE requirements 5.2.2.2 SIB validity and need to (re)-acquire SIB 5.2.2.2.1 SIB validity 5.2.2.2.2 SI change indication and PWS notification 5.2.2.3 Acquisition of System Information 5.2.2.3.1 Acquisition of MIB and SIB1 5.2.2.3.2 Acquisition of an SI message 5.2.2.3.3 Request for on demand system information 5.2.2.3.3a Request for on demand positioning system information 5.2.2.3.4 Actions related to transmission of RRCSystemInfoRequest message 5.2.2.3.5 Acquisition of SIB(s) or posSIB(s) in RRC_CONNECTED 5.2.2.3.6 Actions related to transmission of DedicatedSIBRequest message
...

5 Procedures p. 37

5.1 General p. 37

5.1.1 Introduction p. 37

This clause covers the general requirements.

5.1.2 General requirements p. 37

The UE shall:

1 >

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

1 >

within a clause execute the steps according to the order specified in the procedural description;

1 >

consider the term 'radio bearer' (RB) to cover SRBs, DRBs and MRBs unless explicitly stated otherwise;

1 >

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

1 >

upon receiving a choice value set to setup:

2 >

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

1 >

upon receiving a choice value set to release:

2 >

clear the corresponding configuration and stop using the associated resources;

1 >

in case the size of a list is extended, upon receiving an extension field comprising the entries in addition to the ones carried by the original field (regardless of whether the network signals more entries in total); apply the following generic behaviour unless explicitly stated otherwise:

2 >

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

2 >

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

5.1.3 Requirements for UE in MR-DC p. 38

In this specification, the UE considers itself to be in:

EN-DC, if and only if it is configured with nr-SecondaryCellGroupConfig according to TS 36.331, and it is connected to EPC,
NGEN-DC, if and only if it is configured with nr-SecondaryCellGroupConfig according to TS 36.331, and it is connected to 5GC,
NE-DC, if and only if it is configured with mrdc-SecondaryCellGroup set to eutra-SCG,
NR-DC, if and only if it is configured with mrdc-SecondaryCellGroup set to nr-SCG,
MR-DC, if and only if it is in (NG)EN-DC, NE-DC or NR-DC.

The UE in (NG)EN-DC only executes a subclause of clause 5 in this specification when the subclause:

is referred to from a subclause under execution, either in this specification or in TS 36.331; or
applies to a message received on SRB3 (if SRB3 is established); or
applies to field(s), IE(s), UE variable(s) or timer(s) in this specification that the UE is configured with.

When executing a subclause of clause 5 in this specification, the UE follows the requirements in clause 5.1.2 and in all subclauses of this specification applicable to the messages (including processing time requirements), fields, IEs, timers and UE variables indicated in the subclause under execution.

5.2 System information p. 38

5.2.1 Introduction p. 38

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, clause 7.1 and repetitions are scheduled according to the period of SSB;TS 38.213, clause 4.1 and repetitions are scheduled according to the period of SSB;

NOTE 1:
If the period of SSB is larger than 80 ms, the MIB is transmitted with the same periodicity as that 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 clause 13 of TS 38.213. 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 (clause 13 of TS 38.213). 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.

5.2.2 System information acquisition p. 39

5.2.2.1 General UE requirements p. 39

Reproduction of 3GPP TS 38.331, Fig. 5.2.2.1-1: System information acquisition

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 p. 39

5.2.2.2.1 SIB validity p. 39

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.

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.

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

3 >

4 >

consider the stored posSIB as valid for the cell;

5.2.2.2.2 SI change indication and PWS notification p. 41

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 clause 13 of TS 38.213.

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 and TS 38.213.

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;

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 p. 42

5.2.2.3.1 Acquisition of MIB and SIB1 p. 42

The UE shall:

1 >

apply the specified BCCH configuration defined in clause 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;

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) and if SIB1 acquisition is required for the UE:

3 >

acquire the SIB1, which is scheduled as specified in TS 38.213;

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.

5.2.2.3.2 Acquisition of an SI message p. 43

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

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;

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;

3 >

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;

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;

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;

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 p. 45

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, 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 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, 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 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, 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, 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 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 clause 9.2.2;

3 >

apply the timeAlignmentTimerCommon included in SIB1;

3 >

apply the CCCH configuration as specified in clause 9.1.1.2;

3 >

initiate transmission of the RRCSystemInfoRequest message with rrcSystemInfoRequest in accordance with clause 5.2.2.3.4;

3 >

if acknowledgement for RRCSystemInfoRequest message with rrcSystemInfoRequest 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 rrcSystemInfoRequest:

3 >

release RLC entity for SRB0.

5.2.2.3.3a Request for on demand positioning system information |R16| p. 46

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, 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 using the PRACH preamble(s) and PRACH resource(s) in posSI-RequestConfigSUL 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 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, 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 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, 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, 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 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 clause 9.2.2;

3 >

apply the timeAlignmentTimerCommon included in SIB1;

3 >

apply the CCCH configuration as specified in clause 9.1.1.2;

3 >

initiate transmission of the RRCSystemInfoRequest message with rrcPosSystemInfoRequest in accordance with clause 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.

5.2.2.3.4 Actions related to transmission of RRCSystemInfoRequest message p. 47

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 |R16| p. 47

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

5.2.2.3.6 Actions related to transmission of DedicatedSIBRequest message |R16| p. 48

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.