Question: In a 3GPP SAE network, when an RRC connection is suspended and later resumed by the UE, what happens to the AS security context stored in both the UE and eNB?
Option 1: The AS security context is deleted from both UE and eNB upon suspension and must be re-established at resume.
Option 2: Only the UE stores the AS security context during suspension, which it then reactivates at resume without needing the eNB to store it.
Option 3: The AS security context is transferred to a central server for storage during suspension and retrieved by both UE and eNB at resume.
Option 4: Both the UE and eNB store the AS security context during suspension, which they then reactivate together at resume.
Explanation: This correct answer reflects the procedure's design to efficiently manage security contexts for suspended RRC connections. By storing and later reactivating the AS (Access Stratum) security context in both the User Equipment (UE) and the evolved Node B (eNB), the network ensures seamless security continuity when the UE resumes the connection, whether it reconnects to the same or a different eNB. This approach minimizes overhead and enhances the overall security of the 3GPP System Architecture Evolution (SAE) network.