E-UTRAN

S-GW

The Serving Gateway (S-GW) provides user plane connectivity, the UE being on one side, and
the Packet Data Network Gateway (P-GW) on the other side of the physical S-GW element.
Depending on the network provider’s approach, these elements can be separate, or they can be
combined physically as a single element.
It should be noted that no control messaging goes between the UE and the S-GW, as the
control plane is taken care of by the MME element.

The S-GW element takes care of the following functionalities:
. S-GW is the local anchor point for the inter-eNB handover procedure;
. S-GW is also an anchor point for the inter-3GPP network mobility;
. Lawful Interception (LI);
. packet routing and forwarding;
. S-GW handles packet buffering in the E-UTRAN idle mode;
. S-GW handles the network initiated/triggered service request procedure;
. packet marking at the transport level for both DL and UL;
. Charging Data Record (CDR) collection, which can identify the UE, PDN and QCI;
. accounting on user and QCI granularity for the interoperator charging processes.

P-GW

The PDN Gateway (P-GW) provides, in the same manner as the S-GW, the user plane
connectivity between UE, S-GWand P-GW. The P-GWelement interfaces with the S-GW, and
on the other side, with the external packet data network (PDN). In addition, P-GW includes
GGSN (GPRS Gateway Support Node) functionality.

More specifically, P-GW includes the following functionalities:

. UE IP address allocation;
. Packet filtering that can be done at a user-based level. The other term for this functionality is
a deep packet inspection;
. Lawful Interception (LI);
. Packet marking in the transport level, in the DL;
. Service level charging in DL and UP, as well as gating and rate enforcement;
. Rate enforcement in DL based on APN-AMBR;
. Online charging credit control.

MME

The Mobility Management Element (MME) is meant for the control plane signaling between
the UE and other network elements like HSS. Equally, as the user plane LTE/SAE messaging
does not go through MME, the control plane signaling does not go through S-GWor the P-GW
of LTE/SAE.

MME handles the following functionalities:

. Signaling in the Non Access Stratum (NAS);
. Security of the NAS signaling;
. AS security control;
. The selection of the P-GWand S-GW elements;
. The selection of other MMEs in the handover;
. The selection of SGSN in handovers between LTE and 3GPP 2G/3G access networks;
. Inter-CN node mobility signaling between different 3GPP 2G/3G access networks;
. The management of the Tracking Area (TA) lists;
. International and national roaming;
. User authentication;
. The establishment and management of bearers;
. The support of PWS message transmission, including ETWS and CMAS;
. The management of the paging retransmission of UE and other functions related to the finding
the UE in the idle state.

Comments

Post a Comment

Popular posts from this blog

LTE Measurements Understanding

Image
There are several IEs to configure measurement control in detail, which are under measConfig IE in RRC Connection Reconfiguration message. They are not clearly described with specific picture but here is what I understand. Form the top picture, we might think of an ideal case as (neighbour) cell measured value in yellow goes up linearly. Threshold is bottom line and offset (including several kinds of sub-offset values though) and hysteresis can be applied. Entering condition in this case would mean yellow line cross over threshold (+hysteresis) with blue "x" mark. From this point, timeToTrigger and reportInterval can be applied through the blue block. Leaving condition in this case could not be applied because it never get down go threshold (-hysteresis) as grey "x" mark. If measConfig needs to be removed, it can be managed by RRC Connection Reconfiguration procedure. From the bottom one, we can think of entering and leaving condition with blue "x...
Read more

Difference between PUCCH and PUSCH

I was asked by many engineers on PUCCH and PUSCH functionality and major difference. This thread describes PUCCH functionality and PUSCH functionality. I have tried to differentiate major difference between PUCCH and PUSCH where possible.After reading entire post reader can conclude PUCCH vs PUSCH. PUCCH :  The Physical Uplink Control Channel (PUCCH) is used to transfer Uplink Control Information (UCI). UCI can also be transferred using the PUSCH.  Please refer Different Channel State Information (CSI) Reporting Types. The release 8 and 9 versions of the 3GPP specifications do not allow an individual UE to transmit both the PUCCH and PUSCH during the same sub frame. For Release 8 and 9 if UE has application data or RRC signalling than UCI information transmitted via PUSCH. The release 10 version of the 3GPP specifications introduces the option to support simultaneous PUCCH and PUSCH transmission. 3GPP specify 7 PUCCH formats.Different...
Read more

eNB Functionalities

eNodeB The eNB element of LTE is responsible for radio transmission and reception with UE. eNB  provides the required functionality for the radio resource management (RRM), including  admission control, radio bearer control, scheduling of user data, and control signaling over  the air interface. In addition, eNB takes care of the ciphering and header compression over the  air interface. The clearest difference between UTRAN and E-UTRAN can be seen in the role of the base  station. The eNodeB of LTE now includes basically all the functionalities that were previously  concentrated on the RNC of the UTRANsystem. In addition, the traditional tasks of the NodeB  are still included in the new eNodeB ( eNB ) element. eNB works thus as the counterpart of the  UE in the radio interface but includes procedures for decision making related to the connections. This solution results in the term “flat architecture” of LTE, meaning that there are le...
Read more