Apply 1 suggestion(s) to 1 file(s)

- 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*. Each SIB and each posSIB is mapped to a single SI message. posSIBs of the same *posSibType* carrying GNSS Generic Assistance Data for different GNSS/SBAS (identified by *gnss-id/sbas-id*, see TS 37.355 \[49\]) are mapped to different SI messages. Each SIB and posSIB is contained at most once in an SI message. For SIBs and posSIBs with segments, the segments contained in SI messages are transmitted according to the SI message periodicity, with one segment of a particular *sibType*/*posSibType* in each 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 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 the *MIB* of the PSCell to get SFN timing of the SCG (which may be different from MCG). Upon change of relevant SI for an SCell, the network releases and adds the concerned SCell. For the PSCell, the required SI can only be changed with Reconfiguration with Sync.