top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Normal Release vs Unspecified CAUSE code in NAS/LTE?

+1 vote
2,703 views

Following is the list of NAS cause codes

  • Normal Release
  • Authentication Failure
  • Detach
  • Unspecified
  • CSG Subscription Expiry

Can someone provide some reference to when exactly a "Normal Release" cause is used vs a "Unspecified" cause.

posted Jun 3, 2014 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

Those NAS cause codes are provided by the S1-AP protocol, that carries among others, the NAS protocol. between the UE and the MME.

"Normal Release" in this case, indicates that the release of the UE-associated logical S1 connection is due to a normal NAS EMM or EMS successful completion.

"Unspecified" means that a particular event on the NAS protocol triggered the S1AP protocol to stop the UE -associated S1 connection from reasons NOT in the following group A:

{ Normal Release after a NAS successful completion, NAS Authentication Failure, NAS detach, NAS CSG Subscription Expiry}

Therefore, we conclude that a NAS abnormal event triggered S1AP with a cause other than one of those in group A. That cause is called Unspecified

answer Aug 27, 2014 by Avigdor Ne'eman
Similar Questions
0 votes

Here we have been using Samba (2 & 3) for years as the main file server and also as PDC (integrated with LDAP) so we have centralized account management for both Linux and Windows server and clients.

Now we intent to put most of our data on centralized storage, and are evaluating many entry-level SAN products lie HP P2000G3 and Dell MD3200. We are also intrigued with some ebtry-level NAS solutions from Iomega, EMC and IBM. Maybe someone on the list can share his/her experience
about NAS servers vs Samba3:

  • Will a NAS server provide SMB/CIFS shares, integrated with Samba domain security? Or will then need a Microsoft Active Domain Controller?
  • Moving to Samba4 (or FreeIPA) would solve those issues, if I can't use the current Samba3 PDC and BDC with a NAS server?
  • NFS access to the NAS server will be compatible with latest NFSv4 security, or will it require the "trust-based" weak security model from NFSv3 and v2?
–1 vote

Does NAS messages affected while doing Hand over procedure in LTE or 5G ?

+5 votes

Uplink NAS transport message is used between eNodeB and MME to pass NAS messages between UE and MME transparently.
Since eNodeB has already communicated TAI and E-CGI as part of "Initial UE message" and MME knows current serving (cell and tai ) of UE then why both IEs are mandatory in Uplink NAS transport. I think it should be optional and it should be included in the message when there is a change in serving (cell or tai or both).

+2 votes

I want to know what are all signalling message exchange between LTE network nodes while establishing a dedicated bearer ?

...