LTE NB-IoT Access Procedure Call Flow
LTE NB-IoT Access Procedure is the narrowband access path the UE follows when it enters an NB-IoT-capable LTE cell and moves from cell discovery toward usable access signaling.
The practical anchors are SIB1-BR r13, System Information BR r13, and the later RRC access point that leads toward NB-IoT service continuation.
Introduction
This page focuses on the NB-IoT-specific access entry rather than on ordinary LTE broadband access. The early broadcast context is narrower and more specialized, so the trace should be read through the NB-IoT broadcast chain first.
Use it when the UE can see the cell but the question is whether NB-IoT-specific broadcast and access setup were complete enough for later signaling to begin.
What Is LTE NB-IoT Access Procedure in Simple Terms?
- What starts the procedure: The UE detects an NB-IoT-capable LTE cell and needs the access-side broadcast context for narrowband service.
- What the UE and network want to achieve: A usable NB-IoT cell view followed by successful entry into NB-IoT access signaling.
- What success looks like: The UE reads the NB-IoT broadcast chain and can continue into the expected narrowband access branch.
- What failure means: The UE sees the carrier but never gets enough NB-IoT context to continue cleanly.
Why this procedure matters
NB-IoT access problems often look like generic radio issues at first, but many of them start in the narrowband broadcast and entry assumptions rather than in later NAS behavior.
Quick Fact Sheet
| Procedure name | LTE NB-IoT Access Procedure |
|---|---|
| Domain | NB-IoT access entry |
| Main trigger | Need to enter NB-IoT service on an LTE narrowband cell |
| Start state | UE detects the NB-IoT-capable cell but does not yet have usable narrowband access context |
| End state | UE has the broadcast view and entry path needed for later NB-IoT continuation |
| Main nodes | UE, eNB |
| Main protocols | RRC broadcast and access control |
| Main success outcome | NB-IoT access can continue beyond the broadcast stage |
| Main failure outcome | The UE remains blocked at the narrowband entry stage |
| Most important messages | SIB1-BR r13, System Information BR r13 |
| Main specs | TS 36.331, TS 36.304 |
Preconditions
- The UE can detect the NB-IoT-capable LTE cell.
- The eNB is broadcasting the NB-IoT-specific system-information set.
- The UE is using the NB-IoT access branch rather than an ordinary broadband LTE access path.
Nodes and Interfaces
Nodes involved
| Node | Role in this procedure |
|---|---|
| UE | Reads the NB-IoT broadcast chain and starts the narrowband access path. |
| eNB | Broadcasts the NB-IoT-specific system information and provides the narrowband access entry point. |
| Broadcast context | Defines the NB-IoT-specific cell assumptions the UE needs before later access continuation. |
Interfaces used
| Interface | Path | Role |
|---|---|---|
| LTE Uu | UE <-> eNB | Carries the NB-IoT-specific broadcast and access-side control path. |
| BCCH / DL-SCH | eNB -> UE | Carries the NB-IoT system-information chain. |
| RRC access path | UE <-> eNB | Carries the first dedicated signaling that follows NB-IoT broadcast completion. |
End-to-End Call Flow
UE eNB
|--cell detection------->|
|<--SIB1-BR r13----------|
|<--System Information BR|
|--NB-IoT access start-->| Major Phases
| Phase | What happens |
|---|---|
| 1. Detect the NB-IoT-capable cell | The UE finds the narrowband-capable LTE cell. |
| 2. Read NB-IoT broadcast anchors | The UE reads SIB1-BR and the later BR system information. |
| 3. Start narrowband access | The UE uses the acquired context to move into access signaling. |
| 4. Continue toward later service | The trace moves into the next NB-IoT branch only after the access entry looks complete. |
Step-by-Step Breakdown
Read the access anchor
Sender -> receiver: eNB -> UE
Message(s): SIB1-BR r13
Purpose: Provide the first NB-IoT-specific access-side broadcast context.
State or context change: The UE now has the first narrowband scheduling and access view.
Note: This is the first place to check when the cell is visible but later access never really starts.
Read the broader NB-IoT system information
Sender -> receiver: eNB -> UE
Message(s): System Information BR r13
Purpose: Provide the later NB-IoT broadcast blocks needed for entry and continuation.
State or context change: The UE now has the NB-IoT-specific broadcast model needed for access.
Note: Do not assume ordinary LTE broadcast interpretation is enough here.
Start the access branch
Sender -> receiver: UE -> eNB
Message(s): NB-IoT access signaling start
Purpose: Move from broadcast readiness into the first access-side dedicated signaling.
State or context change: The UE is now trying to enter the usable NB-IoT service path.
Note: This is the bridge point between broadcast analysis and later service analysis.
Verify later continuation
Sender -> receiver: UE <-> eNB
Message(s): Later RRC or NAS continuation
Purpose: Confirm the NB-IoT entry really led into the expected next branch.
State or context change: The access path is now either usable or clearly blocked.
Note: If later signaling is missing, go back to the BR broadcast chain before blaming higher layers.
Important Messages
| Message | Protocol | Direction | Purpose in this procedure | What to inspect briefly |
|---|---|---|---|---|
| SIB1-BR r13 | RRC | eNB -> UE | Starts the NB-IoT-specific broadcast entry path. | Check whether the UE read the narrowband access anchor cleanly. |
| System Information BR r13 | RRC | eNB -> UE | Carries the NB-IoT-specific later broadcast context. | Check whether the later narrowband broadcast set needed for access was actually present. |
| System Information Reference | RRC | eNB -> UE | Useful wider reference when the NB-IoT broadcast chain needs to be compared with ordinary LTE broadcast reading. | Check whether the issue is really NB-IoT-specific and not a generic LTE system-information issue. |
Important Parameters to Inspect
| Parameter | What it is | Where it appears | Why it matters | Common issues |
|---|---|---|---|---|
| NB-IoT broadcast availability | Whether the BR-specific system information is present and readable. | SIB1-BR and System Information BR | Shows whether the narrowband path was actually available to the UE. | The UE sees the cell but the NB-IoT-specific broadcast set is incomplete. |
| Access-side scheduling context | The broadcast timing and access assumptions tied to NB-IoT entry. | SIB1-BR | Explains why later access started when it did or why it never did. | The access branch is blamed while the scheduling context was never correct. |
| Transition point into access | The exact point where the trace should leave broadcast reading and start dedicated access signaling. | After the BR broadcast chain | Separates broadcast failure from access failure. | The trace mixes broadcast readiness and later signaling failure into one issue. |
| Cell identity and narrowband context | The serving-cell assumptions the UE built for this NB-IoT branch. | Across the whole entry window | Useful when the UE read a valid cell but not the intended NB-IoT context. | The UE entered the wrong cell context and later access looked inconsistent. |
| Later branch presence | Whether real NB-IoT access continuation followed after the broadcast chain. | Post-broadcast window | Validates that the entry path was truly complete. | The broadcast chain looked fine, but later continuation never appeared. |
Successful Completion
Success means the UE reads the NB-IoT broadcast chain and then reaches the expected narrowband access continuation point.
Common Failures and Troubleshooting
| Symptom | Likely cause | Where to inspect | Relevant message(s) | Relevant interface(s) | Likely next step |
|---|---|---|---|---|---|
| The cell is visible but NB-IoT access never starts | The BR-specific broadcast chain may be incomplete or unreadable. | SIB1-BR r13 and System Information BR r13 first. | SIB1-BR r13, System Information BR r13 | LTE Uu | Prove the narrowband broadcast chain before reading later access as the root problem. |
| The UE starts access but later behavior still looks wrong | The NB-IoT entry assumptions may be stale or incomplete even though some signaling started. | The final BR broadcast read and the first access-signaling step together. | System Information BR r13 | LTE Uu | Check whether the entry point was really based on the correct broadcast context. |
What to Check in Logs and Traces
- Start with SIB1-BR and the later BR system-information set.
- Find the exact point where the trace leaves broadcast reading and enters access signaling.
- Treat NB-IoT broadcast completeness as a prerequisite for later service analysis.
Related Pages
Related sub-procedures
- LTE NB-IoT System Information Acquisition
- LTE NB-IoT Measurement Procedure
- LTE System Information Acquisition Procedure
Related message reference pages
Related troubleshooting pages
Notes
This page is the NB-IoT access entry view. Use the NB-IoT system-information page when the main question is the broadcast chain itself rather than the move into access.
FAQ
What is the LTE NB-IoT Access Procedure?
It is the narrowband LTE entry path that moves the UE from cell detection through NB-IoT broadcast reading into the first usable access signaling.
Which messages matter most at NB-IoT access entry?
SIB1-BR r13 and System Information BR r13 are the main broadcast anchors before later access continuation starts.