top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration Why to Join

Facebook Login
Site Registration

Why do we have these EPS security context: Native and mapped contexts?

+1 vote
492 views
Why do we have these EPS security context: Native and mapped contexts?
posted May 20, 2014 by Kapil Kapoor

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

2 Answers

+2 votes

There are different types of EPS security context, namely 'native and mapped'.

These types point to the origin of the context: a native EPS security context is a context whose Kasme was created during a run of EPS AKA, while a mapped EPS security context is converted from a UMTS security context when the UE moves to LTE from UTRAN or GERAN.

A mapped EPS security context is always 'full' while a native EPS security context may be full or partial.
A partial native EPS security context is created by an EPS AKA tun, for which no corresponding successful NAS SMC procedure has been run; in other words, a partial native EPS security context is always in state 'non-current'.

After having been put into use by running a NAS SMC procedure, a partial native EPS security context becomes full as the NAS security algorithms and the NAS keys have been agreed between the UE and the MME.

answer May 21, 2014 by Hiteshwar Thakur
+1 vote

These are used during combined 3G 4G attach for MME to SGSM context mapping in case of switchover .

answer May 20, 2014 by Shyam Purkayastha
Similar Questions
+3 votes

I am looking at the EPS authentication, can someone please explain in detail?

+2 votes

Why can't we just calculate total the amount of data, which is to be send using amount of available REs for data transmission, code rate and modulation?

Contact Us
+91 9880187415
sales@queryhome.net
support@queryhome.net
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Bangalore-560102
Karnataka INDIA.
QUERY HOME
...