Home | Reports | Technical Documents | Tech-Blog | One-Shot Gallery | Korea ICT News | Korea Communication Market Data | List of Contributors | Become a Contributor |    
 
 
Section 5G 4G LTE C-RAN/Fronthaul Gigabit Internet IPTV/Video Streaming IoT SDN/NFV Wi-Fi KT SK Telecom LG U+ Network Protocol Samsung   Korean Vendors
 
CHANNELS     HFR    |  Mobile Fronthaul Solution  |  Carrier Ethernet Solution  | Resources        
CHANNELS     ZARAM    |  XGSPON 10G SFP+ ONT  |  Use cases  | Evolution of FTTH Access Network    

 

 

EMM Procedure 3. S1 Release
January 25, 2014 | By Netmanias (tech@netmanias.com)
Online viewer:
Comments (4)
24
SUMMARY
This document, as the third of the EMM Procedure series, will explain procedures for releasing S1 connection when a UE becomes inactive, and thus not connected to any eNB, as in EMM Case 3 defined in our technical document, “Eleven EMM Cases in an EMM Scenario”. We will learn how S1 signaling connection is released in control plane, and the downlink S1 bearer connection is released in user plane during the procedures. We will also describe how information elements in EPS entities are different before and after S1 release.
Page 1 of 4
 
     

Table of Contents  

1. Introduction
2. S1 Release due to User Inactivity
3. EPS Entity Information: Before/After S1 Release

3.1 Before S1 Release
3.2 After S1 Release

4. Closing

 

 

1. Introduction

 

This document will describe procedures for releasing S1 connection when a UE becomes inactive, as in EMM Case 3 defined in our technical document, “Eleven EMM Cases in an EMM Scenario”[1]. While inactive, the UE - registered at the network, but not in use of any service – does not use any radio resources allocated by eNB. So, among the allocated resources, the network releases those associated with radio access, and deletes their related information (e.g. IDs, QoS parameters, etc.).

 

From a network’s perspective, S1 release means releasing the S1 signaling and RRC connections in control plane, and the downlink S1 bearer and DRB (Data Radio Bearer) in user plane, that are associated with a UE. However, from a UE’s perspective, it means losing its RRC connection and DRB in control and user planes, respectively. Once S1 connection is released, the ECM connection between UE and MME is lost, and all contexts associated with the UE are deleted at eNB. Then, the user transits from ECM-Connected to ECM-Idle state at the UE and MME, but remains in EMM-Registered state even after the transit.

 

This document explains the procedures for S1 release due to user inactivity in an LTE network.

 

Chapter 2 provides a description of how S1 release is performed, and

Chapter 3 summarizes what information elements are changed after the S1 release procedure.

 

 

 

Page 1 of 4
Vassilios Stefanidis 2014-04-14 22:30:06
Hello,
In this document, at chapter I. Introduction, p.3 (of the PDF), in the second paragraph it is written:
“From a network’s perspective, S1 release means releasing the S1 signaling and RRC connections in user plane, and the downlink S1 bearer and DRB (Data Radio Bearer) in user plane,”

… I think that the correct should be:
"From a network’s perspective, S1 release means releasing the S1 signaling and RRC connections in CONTROL plane, and the downlink S1 bearer and DRB (Data Radio Bearer) in user plane"

BR

Vassilis
Netmanias 2014-04-15 17:12:26
The typo has been corrected. Thank you again.
Muhammad Israr 2015-11-29 21:08:23

Very good presentation of the information 

Amol Ramdas Suryavanshi 2016-12-08 18:45:21

Very Good and in depth knowldege.

Thanks

Thank you for visiting Netmanias! Please leave your comment if you have a question or suggestion.
Related Contents
08/01/2018
Netmanias Technical Documents
04/02/2018
Netmanias Technical Documents
08/22/2014
Netmanias Technical Documents
06/11/2014
Netmanias Technical Documents
05/07/2014
Netmanias Technical Documents
04/23/2014
Netmanias Technical Documents
04/08/2014
Netmanias Technical Documents
03/21/2014
Netmanias Technical Documents
02/19/2014
Netmanias Technical Documents
View All (171)
5G (6) Backbone (2) Backhaul (3) Blockchain (1) CDN (1) Carrier Ethernet (3) Charging (1) DHCP (4) ECM (2) EMM (16) EPS (2) Google (1) HLS (1) HTTP Adaptive Streaming (3) Handover (5) IPTV (4) Initial Attach (2) IoT (2) Korea (1) LTE (39) LTE Identification (2) LTE-A (1) MPLS (2) Mobility (2) NAT (7) Netflix (1) Network Architecture (3) Network Protocol (20) New Radio (1) OTT (1) PCRF (3) QoS (3) RCS (3) SDF (2) SDN/NFV (2) SK Telecom (1) Samsung (2) Security (5) Sk Telecom (1) Transparent Cache (1) Video Streaming (4) VoLTE (2) Wi-Fi (1) YouTube (2)
Password confirmation
Please enter your registered comment password.
Password