LTE EMM Cause #15: No Suitable Cells in Tracking Area — Coverage Edge Diagnosis

LTE EMM cause #15 (“No suitable cells in tracking area”) is returned by the MME when the UE attempts to register in a tracking area where no suitable cell exists for its subscription or access type. Unlike cause #12 which makes the TAI forbidden, cause #15 is less severe: the TAI is added to the forbidden roaming list but the UE may remain camped on the cell in limited service mode for emergency calls.

This cause code is most commonly encountered at coverage boundaries, in roaming scenarios with partial TA-level agreements, and in deployments with subscriber-group-specific TA restrictions.

Technical Reference

UE Behavior After Receiving Cause #15

Per 3GPP TS 24.301 §5.5.1.2.5:

• Set EPS update status to EU3 ROAMING NOT ALLOWED
• Delete stored GUTI, last visited registered TAI, and TAI list
• Store the current TAI in the “forbidden tracking areas for roaming” list — the UE will not initiate registration in this TA for normal services
• Enter state EMM-DEREGISTERED and begin a new cell selection procedure
• May camp on cells in the forbidden TA in limited service mode — emergency calls (via Attach with CSFB fallback or emergency IMS) remain possible
• Perform PLMN/cell reselection to find a cell in a different, acceptable TA

Key distinction from cause #12: Cause #12 (Tracking area not allowed) also adds the TAI to the forbidden list, but with a broader interpretation: the TA is disallowed. Cause #15 is more nuanced — “no suitable cells” implies the TA itself may be valid but no cell within it currently satisfies the UE’s access requirements. The network-side reason is typically a configuration issue rather than an outright barring policy.

Field Scenarios

Coverage boundary between LTE zones. At the edge of an operator’s LTE coverage area, the UE may camp on a cell that belongs to a TA configured in the MME as a “limited access” area — accessible for registration only by specific subscriber groups (e.g., emergency services, IoT devices with restricted TA lists). A general subscriber’s attach attempt receives cause #15.

Roaming with partial TA-level agreement. An inter-operator roaming agreement may cover the visited PLMN but exclude specific tracking areas (e.g., rural TAs not included in the tariff plan). The visited MME returns cause #15 for attach attempts from subscribers whose profiles exclude those TAs.

Enterprise or private LTE TA. Closed enterprise LTE networks deployed as a dedicated TA (with unique TAI distinct from the public network) return cause #15 to any USIM not in the enterprise subscriber whitelist. This is a standard access control mechanism for campus-level private LTE.

Test TA during network rollout. During LTE rollout, engineers sometimes configure new eNBs with a test TAI not yet included in the commercial MME’s accepted TA list. Field test SIMs receive cause #15 on every attach attempt until the TAI is activated in the MME configuration.

Step-by-Step Field Diagnosis

Step 1 — Confirm cause #15 in the NAS log. Locate the Attach Reject or TAU Reject carrying EMM cause IE value 0x0F. Note the TAI of the cell on which the rejection was received — this TAI will be stored in the forbidden TA list.

Step 2 — Verify the UE camps in limited service. After cause #15, the UE should remain on the cell (or nearby cells of the same TA) in limited service state, not execute a full PLMN search like it would after cause #11. In the RRC log, limited service is visible as EMM-DEREGISTERED state with no new PLMN search initiated immediately.

Step 3 — Attempt registration on a cell in a different TA. Move the device to a cell belonging to a different TAI. A successful attach confirms the issue is TA-specific, not PLMN-wide (which would indicate cause #11).

Step 4 — Map the TA boundary. Using GPS-correlated drive test data, plot the cells returning cause #15 against a TA map. A clear boundary between cause #15 cells and successful attach cells identifies the TA where the restriction applies.

Step 5 — Verify the MME’s TA configuration. On the operator side, confirm whether the TAI is included in the MME’s list of accepted tracking areas for the subscriber’s Home Subscriber Server profile. A TAI absent from the subscriber’s Allowed TA list in the HSS triggers cause #15.

Capturing Cause #15 in the Field

DIAG log code 0x713A (LTE NAS EMM plain OTA incoming) captures the Attach Reject with cause #15. In the decoded message, the TAI of the cell is visible in the NAS header’s public land mobile network identity and tracking area code fields. Cross-reference with the GPS coordinates logged at the same timestamp to map the exact geographic boundary of the restriction.

The subsequent UE behavior (limited service camp vs. full PLMN search) is visible in NAS state log code 0xB0EE, which tracks the EMM state machine transitions.

Related Cause Codes

• Cause #12 — Tracking area not allowed (stricter TA restriction, no limited service allowed)
• Cause #13 — Roaming not allowed in this tracking area (roaming-specific TA restriction)
• Cause #11 — PLMN not allowed (PLMN-level restriction, not TA-level)
• Cause #15 in 5GS NAS — 5GS MM cause #15, TS 24.501 §9.11.3.2 (same semantics, 5GS context)