PDN Connection Reject: Cause Value (32) - Service Option Not Supported

PDN Connection Reject: Cause Value (32) - Service Option Not Supported.

What can be the reason of this?

This ESM cause is used by the network when the UE requests a service which is not supported by the PLMN.

Thanks.

Device is trying to attach a packet session, so is it a network side issue?

Any specific device or all the devices?

NB-IoT testing device.

May be need to check from the Core end if all the services are enabled or not.

Can you share attach request message as well please?

Let’s see what was requested?

Attach request message.

That should come before attach reject.

L3 MSG NBIOT.xlsx (107.3 KB)

PDN type is iPv4 only.

Try changing to dual stack and try again.

Possible cause : We have listed the possible reasons below, but the second one, that is, unsupported feature, is the situation that you can check on the ran side.

  1. Protocol Mismatch
  2. Unsupported Feature ( Check the FGI numerator and compare with your current network feature activation state and secondarily compare with your software relase and any kind board support these activated feature or not. ( FGI : UE LTE capability includes VoLTE-related capability information and Feature Group Indicator (FGI) bits exchange - Note This FGI mentioned because of just an example may NBIOT L3 not including same values or structure just giving an idea / For detailed information about FGI bits, refer to 3GPP TS 36.331, Release-9, Annex B )
  3. Interoperability Problems
  4. Network Policy Restrictions
  5. Upgrade or Update Required:
  6. Misconfiguration
    ** UE sends PDN Connectivitiy request again to be attached to Lte network, PDN Type can be seen as IPV4 and IPV6, and it is of great importance that both IP types, especially IPV6, are supported here. It is mandatory that VOLTE UE supports IPV6.

The APN name appears as IMS and is a universal value. This name is assigned by default, even if the UE does not request any APN name.
Configuration protocols appear in the PDN Connectivitiy Request, from 1 to 5, each of them has a different meaning and the contents values are always seen as zero because the request has not yet come from the UE and the UE does not know some parameter values, because NW has not yet responded to the UE.
Activate_Default_EPS_Bearer_Context_Request contains PDN type information (IPV6) and IP address information allocated to the User.

The “selected bearer control mode” parameter is basically used by the network to tell the UE whether carrier creation and replacement can be triggered by the UE alone, or whether both the UE and the network can trigger carrier creation and switching together.
The contents values in Protocol ID 2 and 3 are the decoded version of the P-CSCF IP address information. When converted to IPV6, it gives the IP shown in red.

I was thinking could this be the problem but probably not since this is only indication of feature support.