name: EMM cause #11
full_form: EPS Mobility Management cause #11
context: Cause #5 â IMEI not accepted
  This cause is sent to the UE if the network does not accept an attach procedure for emergency bearer services using an IMEI.
  Cause #7 â EPS services not allowed
  This EMM cause is sent to the UE when it is not allowed to operate EPS services.
  Cause #8 â EPS services and non-EPS services not allowed
  This EMM cause is sent to the UE when it is not allowed to operate either EPS or non-EPS services.
  Cause #11 â PLMN not allowed
  This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a PLMN where the UE, by subscription or due to operator determined barring, is not allowed to operate.
  Cause #12 â Tracking area not allowed
  This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the HPLMN determines that the UE, by subscription, is not allowed to operate.
  NOTEÂ 1:	If EMM cause #12 is sent to a roaming subscriber the subscriber is denied service even if other PLMNs are available on which registration was possible.
  Cause #13 â Roaming not allowed in this tracking area
  This EMM cause is sent to an UE which requests service, or if the network initiates a detach request, in a tracking area of a PLMN which by subscription offers roaming to that UE but not in that tracking area.
  Cause #14 â EPS services not allowed in this PLMN
  This EMM cause is sent to the UE which requests service, or if the network initiates a detach request, in a PLMN which does not offer roaming for EPS services to that UE.
  NOTEÂ 2:	Since only one list of forbidden PLMNs for packet services is maintained in the UE, then the "forbidden PLMNs for GPRS service" is the maintained list and the forbidden PLMNs for EPS service is equivalent to it.
  Cause #15 â No suitable cells in tracking area
  This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking area or location area in the same PLMN or an equivalent PLMN.
  NOTEÂ 3:	Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the UE to search for another allowed tracking area on the same PLMN.
  Cause #25 â Not authorized for this CSG
  This EMM cause is sent to the UE if it requests access, or if the network initiates a detach request, in a CSG cell with CSG ID where the UE either has no subscription to operate or the UE's subscription has expired and it should find another cell in the same PLMN or an equivalent PLMN.
  Cause #35 â Requested service option not authorized in this PLMN
  This EMM cause is sent to the UE if it requests in a PLMN a service option for which it is not authorized, e.g. if it attempts to attach for relay node operation in a PLMN with a USIM which does not belong to a relay node-specific subscription.
  Cause #36 â IAB-node operation not authorized
  This EMM cause is sent to the UE if a UE operating as an IAB-node requests service, or if the network initiates a detach request, in a PLMN where the UE, by subscription, is not authorized for IAB operation.
  Cause #40 â No EPS bearer context activated
  This EMM cause is sent to the UE, if during a tracking area updating procedure or a service request, the MME detects that there is no active EPS bearer context in theÂ network.
  Cause #31 â Redirection to 5GCN required
  This EMM cause is sent to the UE if it requests service in a PLMN where the UE by operator policy, is not allowed in EPC and redirection to 5GCN is required.
description: PLMN not allowed
explanation: Categorized as a Cause Code because it specifies the reason for an action in EPS services.
biotag_Context: O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,B-Network,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Cause Code,I-Cause Code,I-Cause Code,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,B-Network,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,B-Parameter,B-Parameter,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,B-Device,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,B-State,I-State,I-State,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-State,I-State,I-State,O,O,O,O,O,O,O,O,B-Network,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Network,O,O,B-Device,O,O,O,O,O,O,O,B-Network,O,O,O,B-Network,O,O
biotag_Description: B-Network,O,O