Remaining Minimum System Information

In Release 15, the foundational procedures for RMSI (Remaining Minimum System Information) were introduced, defining its transmission multiplexing and timing relative to SS/PBCH blocks. Specifically, RMSI transmission was configured to be time-division multiplexed (TDMed) with SS/PBCH blocks in FR1 and could be frequency-division multiplexed (FDMed) in FR2, with a defined periodicity and a set of time offsets for its transmission. The release also established the concept of CORESET#0 for the necessary control resource set to decode the RMSI.

• Slicing assistance information TS 38.300CR0024
• System Information Handling in TS38.300 TS 38.300CR0071
• Corrections to System Information TS 38.300CR0074
• Correction to the system information in Handover Request message TS 38.300CR0086
• System Information Provisioning TS 38.300CR0089
• CORESET#0 TS 38.300CR0111

+ 1 more changes

In Release 16, the enhancements for RMSI (Remaining Minimum System Information) were not detailed in the provided grounding context. The context only describes the baseline transmission mechanisms for RMSI, such as its periodicity and multiplexing with SS/PBCH blocks, which were established prior to Release 16. The associated Change Request title indicates a separate, network-focused update for propagating roaming and access restriction information in non-homogeneous NG-RAN deployments, which is not a direct modification to the RMSI function itself.

• Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments TS 38.300CR0207

In Release 17, specific clarifications were made regarding RMSI transmission mechanisms. The grounding context details that RMSI is multiplexed with SS/PBCH blocks, being time-division multiplexed in FR1 and potentially frequency-division multiplexed in FR2, with its periodicity tied to the SSB set period. Furthermore, one of the associated Change Requests focused on the removal of an editor's note concerning sequence length 1151 for PRACH usage, which relates to the random-access procedures used to acquire RMSI.

• Correction of UE History Information for CHO TS 38.300CR0607
• Clarification on slice group information provided by NAS TS 38.300CR0610
• Removal of editor's note on sequence length 1151 for PRACH usage TS 38.300CR0621

In Release 18, there were no specific new features or changes introduced for the RMSI (Remaining Minimum System Information) function, as none of the provided Change Requests pertain to RMSI, and the grounding context only describes the pre-existing transmission mechanisms for it. The listed corrections and clarifications for Release 18 focus on other areas such as Xn handover data forwarding, UE assistance information for XR, and NTN OAM information. Therefore, the RMSI procedures, including its periodicity and multiplexing with SS/PBCH blocks, remain as defined prior to this release.

• Transfer PDU Set Information during data forwarding for Xn handover TS 38.300CR0828
• Correction on UE assistance information for XR TS 38.300CR0964
• Clarification of the chapter title to match the description of the UE History Information TS 38.300CR0969
• Stage 2 correction on DL LBT failure information TS 38.300CR0971
• Correction of NTN OAM Assistance information TS 38.300CR1001

In Release 19, the key new development for the RMSI (Remaining Minimum System Information) function is the introduction of features to **Support Aerial UE Flight Information Reporting**. This enhancement, indicated by the provided Change Request title, builds upon the existing RMSI framework where RMSI transmissions are multiplexed with SS/PBCH blocks and follow defined periodicities and offset patterns to enable UE network access. The update specifically extends RMSI's role in system information delivery to accommodate the reporting and potentially the related configuration for aerial user equipment.

• Support Aerial UE Flight Information Reporting TS 38.300CR1031