Home | Reports | Technical Documents | Tech-Blog | One-Shot Gallery | Korea ICT News | About Us | List of Contributors | Become a Contributor | Sponsor Channel Service  
 
  KT SK Telecom LG U+ Korean Vendors Network Architectures  
 
Key Words 5G 4G LTE C-RAN/Fronthaul Gigabit Internet IPTV/Video Streaming IoT SDN/NFV Wi-Fi KT SK Telecom LG U+ Network Protocol Samsung  
 
CHANNELS HFRFRONTHAUL NetvisionMPTCP Springwave1588 PTP   Korea Communication Review      
EMM Procedure 4. Service Request
February 09, 2014 | By Netmanias (tech@netmanias.com)
Online viewer:
Comments (9)
30
SUMMARY
This document, as the fourth of the EMM Procedure series, will describe the service request procedure as defined as EMM Case 4 in our technical document, “Eleven EMM Cases in an EMM Scenario”. This procedure is used when a UE, initially attached to the network but staying inactive in Idle state, wishes to use LTE services again when there is new traffic. We will discuss how E-UTRAN resources are allocated to the UE again through this procedure, establishing an ECM connection (RRC + S1 signaling connections) in the control plane, and an E-RAB (DRB + S1 bearer) in the user plane. We will also look into how information elements in EPS entities are different before and after the procedure.
Page 1 of 6
 

 

 

1. Introduction

 

This document describes the service request procedure defined as EMM Case 4 in our technical document, “Eleven EMM Cases in an EMM Scenario” [1]. This procedure is performed when an inactive UE in Idle state wishes to get activated to handle traffic when there is new traffic. New user traffic can be uplink traffic from UE or downlink traffic from the network to UE. The UE’s E-UTRAN resources (allocated by eNB) have been released, and the UE has been in ECM/RRC-Idle state. Thus, in order for the UE to receive or send user traffic, DL or UL, it needs to transmit to ECM/RRC-Connected state through the service request procedure so that E-UTRAN resources can be allocated again.

 

This document explains the service request procedure in an LTE network.

 

Chapter 2 categorizes different cases of service request depending on where new traffic is generated.

Chapter 3 and 4 describe distinct procedures required in each service request case. Finally,

Chapter 5 summarizes how information elements in EPS entities are different before and after the procedure.

 

 

 

Page 1 of 6
Joseph 2014-04-21 08:04:47
Hi Netmanias,
I know, in the step "15) EPS Session Modification (optional)" in Figure 3, when P-GW forwards a CCR message to PCRF, IMSI and UE’s IP address are sent as well to inform whose session is sent. How does the P-GW know to which user the session belongs to when no user ID is included in the Modify Bearer Request message that S-GW is sending to the P-GW?
Netmanias 2014-04-21 16:39:46
Hi Joseph,

In control plane, there is a GTP-C tunnel (per user) established between S-GW and P-GW. This tunnel (or user of this tunnel) is identified by a TEID. The TEID value is carried in the GTP tunnel header while control message is carried in the GTP tunnel payload field.

In the Step 15), when S-GW sends a Modify Bearer Request message to P-GW through this GTP-C Tunnel, the P-GW checks the TEID in the tunnel header and learns whose session it is.
debasish 2014-05-27 16:16:03
Hi Netmanias team,

Please explain me a scenario where UE is establishing a second dedicated bearer(ofcourse network initiated).
gecuili 2015-01-26 17:34:14

 “At this time, the eNB allocates eNB UE S1AP ID, and includes it in the Initial UE Message sent to the MME. ”

eNB UE S1AP ID --》 eNB S1AP UE ID. Right?

 

azgar shaik 2015-03-22 13:40:35

Is there Any Timer defined for Inital Context Setup Request/ Response?

James 2015-06-23 21:14:29

"SGW finds out at which MME the UE is registered"  how?

Ranjith Kumar Kopperla 2015-12-14 18:51:18

Dear Netmanias team,

 

Thanks for your explanation, can you please explain what happens when the Service Request procedure is rejected. If possible please explain the behavior for different cause codes.

 

 

nitinatakg@gmail.com 2016-03-11 14:39:42

This site is the best

Gul 2016-06-24 12:13:50

I have a question , After establishing the internet connection Ue is sending SR for three times since Network is ignoring the Service request . But according to spec it should send for five times .

What could be the reason here ?

Thank you for visiting Netmanias! Please leave your comment if you have a question or suggestion.
banner
Related Contents
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
01/25/2014
Netmanias Technical Documents
01/21/2014
Netmanias Technical Documents

 

 

     
         
     

 

     
     

Subscribe FREE >>

Currently, 47,000+ subscribed to Netmanias.

  • You can get Netmanias Newsletter

    (New contents, Korea ICT News)

  • You can view all netmanias' contents

  • You can download all netmanias'

    contents in pdf file

     
     

 

     
         
     

 

 

 

 

     
         
     

 

     
     

KOREA ICT RESEARCH REPORT

SK Telecom's Massive IoT Deployment through LoRa for Small Things

 

 

SK Telecom commercialized the world’s first nationwide LoRa-based, IoT dedicated network in the end of June. This report will discuss how well SK Telecom is poised for the emerging IoST sector, and where it is heading.

 

     
     

 

     
         
     

 

     
         
     

 

     
     

How to contribute articles to Netmanias!

We always welcome contributed articles. Share your expertise and inspire others!

     
     

 

     
         
     

 

 

View All (169)
Backbone (2) Backhaul (3) CMIP (1) CPM (2) Carrier Ethernet (3) Charging (1) DHCP (4) Detach (1) ECM (2) EMM (16) EPS (2) Google (1) HLS (1) HTTP Adaptive Streaming (3) Handover (5) IGMP (1) IPTV (4) Initial Attach (2) Korea (1) LTE (37) LTE Identification (2) LTE-A (1) MPLS (2) Mobile IP (1) Mobility (2) Multicast (2) NAT (7) Netflix (1) Network Architecture (3) Network Protocol (20) OTT (1) PCC (1) PCRF (2) PIM (1) PMIP (1) Progressive Download (1) QoS (3) RCS (3) SDF (2) SIMPLE IM (2) SK Telecom (1) STUN (2) Samsung (1) Security (5) TPS (1) Transparent Cache (1) Video Streaming (4) VoLTE (1) Wi-Fi (1) YouTube (2)
Password confirmation
Please enter your registered comment password.
Password