name: APN
full_form: Access Point Name
context: Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message the network may reject the MS initiated PDP context activation by sending an ACTIVATE PDP CONTEXT REJECT message to the MS. The message shall contain a cause code that typically indicates one of the following causes: # 8: Operator Determined Barring; # 26: insufficient resources; # 27: missing or unknown APN; # 28: unknown PDP address or PDP type; # 29: user authentication failed; # 30: activation rejected by GGSN, Serving GW or PDN GW; # 31: activation rejected, unspecified; # 32: service option not supported; # 33: requested service option not subscribed; # 34: service option temporarily out of order; # 35: NSAPI already used. The network shall not send this cause code (see note 1); # 50: PDP type IPv4 only allowed; # 51: PDP type IPv6 only allowed; # 57: PDP type IPv4v6 only allowed; # 58: PDP type non IP only allowed; # 65: maximum number of PDP contexts reached; # 66: requested APN not supported in current RAT and PLMN combination; # 95 - 111: protocol errors; #112: APN restriction value incompatible with active PDP context; or #113: Multiple accesses to a PDN connection not allowed. NOTE 1: Pre-R99 network may send this cause code. The network may include a Back-off timer value IE in the ACTIVATE PDP CONTEXT REJECT message. If the SM cause value is #26 "insufficient resources" and if the request type in the ACTIVATE PDP CONTEXT REQUEST was set to "emergency", the network shall not include a Back-off timer value IE. If the Back-off timer value IE is included and the SM cause value is different from #26 "insufficient resources", #50 "PDP type IPv4 only allowed", #51 "PDP type IPv6 only allowed", #57 "PDP type IPv4v6 only allowed", #58 "PDP type non IP only allowed" and #65 "maximum number of PDP contexts reached", the network may include the Re-attempt indicator IE to indicate whether the MS is allowed to attempt a PDN connectivity procedure in the PLMN for the same in S1 mode, and whether another attempt in A/Gb and Iu mode or in S1 mode is allowed in an equivalent PLMN. If the SM cause value is #50 "PDP type IPv4 only allowed", #51 "PDP type IPv6 only allowed", #57 "PDP type IPv4v6 only allowed" or #58 "PDP type non IP only allowed", the network may include the Re-attempt indicator IE without Back-off timer value IE to indicate whether the MS is allowed to attempt a PDP context activation procedure in an equivalent PLMN for the same APN in A/Gb or Iu mode using the same PDP type. If the SM cause value is #66 "requested APN not supported in current RAT and PLMN combination", the network may include the Re-attempt indicator IE without Back-off timer value IE to indicate whether the MS is allowed to attempt a PDP context activation procedure in an equivalent PLMN for the same APN in A/Gb or Iu mode. Upon receipt of an ACTIVATE PDP CONTEXT REJECT message, the MS shall stop timer T3380 and enter/remain in state PDP-INACTIVE. If the ACTIVATE PDP CONTEXT REQUEST message was sent with request type set to "emergency" and the MS receives an ACTIVATE PDP CONTEXT REJECT message, then the MS may inform the upper layers of the failure to establish the emergency bearer. NOTE 2: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or initiating other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ]  [95] can result in the emergency call being attempted to another IP-CAN.
description: The Access Point Name (APN) is a unique identifier used by mobile devices to connect to a specific gateway between the cellular network and the public internet or other private networks. It serves as an address for routing data packets from the device to the desired destination, ensuring that the correct services are accessed. The APN is crucial in managing PDP (Packet Data Protocol) contexts, which define the characteristics of the connection, including the type of data transmission (e.g., IPv4 or IPv6).
explanation: APN is classified as an Identifier because it uniquely identifies a specific gateway for mobile devices to access various services and networks. Its role in routing data packets and defining PDP contexts aligns with the concept of identifiers in telecommunications, which are used to distinguish between different entities, services, or configurations.
section_title: 6.1.3.1.3 Unsuccessful PDP context activation initiated by the MS 6.1.3.1.3.1 General
biotag_Context: O,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,B-Parameter,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,B-Message,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-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,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,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,B-Protocol,O,O,O,O,B-Protocol,O,B-Protocol,O,O,O,O,B-Protocol,O,B-Protocol,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Network,O,O,O,O,B-Technology,O,B-Network,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,B-Protocol,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,B-Message,O,O,O,B-Protocol,O,B-Message,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,B-Service,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,B-Parameter,O,O,O,O,O,B-Network,O,O,O,O,B-Network,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,B-Mode,I-Mode,O,O,B-Mode,I-Mode,O,O,O,O,O,O,O,O,B-Service,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,B-Message,O,O,O,O,B-Parameter,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Network,O,O,O,B-Network,O,O,O,B-Mode,I-Mode,O,O,O,B-Protocol,O,O,O,B-Service,O,O,O,O,O,B-Network,O,O,O,O,B-Technology,O,B-Network,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,B-Message,O,O,O,O,B-Parameter,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Network,O,O,O,B-Network,O,O,O,B-Interface,O,O,O,O,O,O,B-Protocol,O,B-Message,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,B-Message,I-Message,I-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Protocol,O,B-Message,O,O,O,B-Parameter,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-Mode,O,O,O,O,O,O,O,O,B-Mode,O,O,O,O,O,O,O,O,O,O,O,B-Organization,B-Specification,O,B-Protocol,O,O,O,O,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Network,I-Network,I-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,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,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O