Telecom engineering reference for protocols, messages, call flows, troubleshooting, releases, and tools.
Menu
RRC5GgNB -> UE3GPP TS 38.331
5G NR - System Information Block 7 (SIB7)
System Information Block 7 (SIB7) is an NR broadcast system information block used for inter-RAT mobility context toward GERAN, helping the UE evaluate reselection from NR toward GSM where that legacy mobility path still exists.
Message Fact Sheet
Protocol
rrc
Network
5g
Spec
3GPP TS 38.331
Spec Section
5.2.1, 5.2.2, 5.4.3, 6.3.1
Direction
gNB -> UE
Message Type
Broadcast System Information
Full message name
5G NR - System Information Block 7 (SIB7)
Protocol
RRC
Technology
5G
Direction
gNB -> UE
Interface
Uu
Signaling bearer / channel
Broadcast transport / BCCH-DL-SCH
Typical trigger
Broadcast by the cell as additional system information so camped UEs can apply inter-RAT reselection policy toward GSM where that legacy mobility path still matters.
Main purpose
Provides GERAN-related reselection information so the UE can make correct idle or inactive mobility decisions when neighboring GSM systems remain part of the operator mobility design.
Main specification
3GPP TS 38.331, 5.2.1, 5.2.2, 5.4.3, 6.3.1
Release added
Release 15
Procedures where used
System Information Acquisition, Inter-RAT Cell Reselection, Idle Mobility, Inactive Mobility
Related timers
Reselection timing is driven by broadcast mobility parameters rather than a dedicated UE-specific RRC transaction timer
Related cause values
SIB7 does not carry reject causes, Problems are inferred from missing SI acquisition or inter-RAT behavior that does not match the configured GERAN mobility policy
What is System Information Block 7 (SIB7) in simple terms?
System Information Block 7 (SIB7) is an NR broadcast system information block used for inter-RAT mobility context toward GERAN, helping the UE evaluate reselection from NR toward GSM where that legacy mobility path still exists.
Provides GERAN-related reselection information so the UE can make correct idle or inactive mobility decisions when neighboring GSM systems remain part of the operator mobility design.
Why this message matters
SIB7 is the NR broadcast block that mainly tells the UE how to behave with GSM targets when that legacy RAT is still part of the mobility design.
Where this message appears in the call flow
System Information Acquisition
Call flow position: Read as additional broadcast information after the essential access layer is already available.
Typical state: UE is camped and building the broader mobility view across legacy radio technologies.
Preconditions:
MIB and SIB1 have been acquired.
The UE knows the scheduling for additional system information.
Next likely message: GERAN reselection evaluation
Inter-RAT Cell Reselection to GERAN
Call flow position: Used when the UE evaluates mobility from NR toward GSM.
Typical state: UE is not in dedicated connected-mode signaling.
Preconditions:
The serving-cell broadcast information is valid.
GERAN neighbors are part of the mobility design.
Next likely message: Stay on NR or reselect to GERAN
Idle / Inactive Mobility
Call flow position: Provides broadcast rules for mobility decisions from NR toward GERAN.
Typical state: UE is camped or inactive and monitoring mobility-related broadcast information.
Preconditions:
The UE is already operating with valid serving-cell system information.
Next likely message: Paging monitoring, RAT search, or reselection depending on conditions
Next message(s): GERAN reselection evaluation, Idle mobility decisions toward GSM, Later access on a reselected GERAN cell
Message direction and transport
Sender and receiver: gNB -> UE
Interface: Uu
Domain: Access-side radio control and broadcast mobility information
Signaling bearer: Broadcast transport
Logical channel: BCCH-DL-SCH
Transport / encapsulation: RRC system information carried on BCCH-DL-SCH after the UE has acquired the essential system information and the scheduling for additional SI
Security context: Broadcast information. It is cell-common and not protected by dedicated AS security.
Message Structure Overview
SIB7 focuses on NR-to-GERAN mobility rather than NR-only mobility or NR-to-LTE/UTRA mobility.
For engineering work, the main question is whether the legacy GSM mobility policy matches the intended deployment strategy.
SIB7 matters mostly in networks where GSM still exists as part of coverage, fallback, or continuity planning.
ASN.1 for 5G NR - System Information Block 7 (SIB7)
SIB7 is typically carried inside the broader SystemInformation container. In practice, engineers care most about whether the GERAN target list and thresholds explain the observed legacy inter-RAT mobility behavior.
The key practical block is the GERAN carrier list.
ARFCN and band indicator tell you whether GSM is really part of the mobility strategy.
Thresholds and offsets help explain why the UE stays on NR or moves toward GERAN.
Important Information Elements
IE
Required
Description
geran carrier list
Yes
The main SIB7 content. It defines the candidate GERAN carriers or neighbor information relevant for mobility from NR toward GSM.
priority and threshold-related parameters
Optional
Help explain when GERAN should become attractive enough to be considered for reselection.
q-Offset or equivalent biasing information
Optional
Changes how favorable or unfavorable the GSM target appears in idle mobility decisions.
search and timing controls
Optional
Operationally important parameters that affect when the UE searches and when it commits to a move toward GERAN.
Detailed field explanation
geran carrier list
The main SIB7 content. It defines the candidate GERAN carriers or neighbor information relevant for mobility from NR toward GSM.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
priority and threshold-related parameters
Help explain when GERAN should become attractive enough to be considered for reselection.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
q-Offset or equivalent biasing information
Changes how favorable or unfavorable the GSM target appears in idle mobility decisions.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
search and timing controls
Operationally important parameters that affect when the UE searches and when it commits to a move toward GERAN.
Presence: Optional
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
What to check in logs and traces
Confirm MIB and SIB1 were decoded successfully before reviewing SIB7 behavior.
Verify that the UE actually acquired the additional SI carrying SIB7.
Check the configured GERAN targets against the expected legacy mobility plan.
Inspect thresholds, offsets, and priorities against the observed leave-NR or stay-on-NR behavior.
Compare NR serving conditions with GERAN attractiveness rather than reviewing one side only.
If users report missing or unexpected GSM-directed mobility, correlate SIB7 with RF measurements and broadcast versions.
Common Issues and Troubleshooting
The UE does not reselect to GSM when legacy continuity is expected.
Likely cause: GERAN thresholds or priorities may not make GSM attractive enough.
What to inspect: Check SIB7 carrier list, threshold values, and priority settings.
Next step: Compare the configured GSM continuity strategy with real radio conditions and neighbor planning.
The UE leaves NR unexpectedly for GSM.
Likely cause: The GERAN target may be too highly prioritized or insufficiently penalized.
What to inspect: Check priority and q-Offset related values for the GERAN target.
Next step: Correlate SIB7 with field logs to see whether the mobility policy is too aggressive.
LTE or UMTS-related fallback is fine, but GSM-directed mobility is wrong.
Likely cause: The issue may sit specifically in SIB7 rather than in SIB5 or SIB6.
What to inspect: Separate NR-to-LTE, NR-to-UTRA, and NR-to-GERAN behavior clearly in the trace analysis.
Next step: Analyze SIB5, SIB6, and SIB7 only after separating the target RAT path.
LTE / 5G / Variant Comparison
SIB7 versus SIB6
SIB6 covers NR-to-UTRA mobility. SIB7 is more specific to NR-to-GERAN mobility.
SIB7 versus dedicated RRC
SIB7 is broadcast cell-common mobility information, not UE-specific connected-mode configuration.
FAQ
What is SIB7 in 5G NR?
SIB7 is System Information Block 7, an NR broadcast block used mainly for inter-RAT reselection toward GERAN.
Who sends SIB7?
The gNB broadcasts SIB7 as additional system information.
What is the main purpose of SIB7?
To provide inter-RAT reselection parameters for idle and inactive mobility toward GSM.
On which channel is SIB7 sent?
SIB7 is carried in system information on BCCH-DL-SCH.
Why is SIB7 useful in troubleshooting?
Because it helps explain why the UE does or does not move from NR to GSM where that legacy path still exists.
Decode this message with the 3GPP Decoder, inspect the related message database, or open the matching call flow to see where this signaling step fits in the full procedure.