Samsung Galaxy S6 has your Bloatware Problem Solved

Samsung Galaxy S6 the Latest in the Galaxy series has your bloatware software problems solved as far as Keeping the device from running too many background applications. The Galaxy S6 and The S6 edge has an Option that let users to remove the Bloatware that has been pre loaded on the phone .

Samsung Galaxy S6 app removal option
Samsung Galaxy S6 Edge app removal options – image XDA Developers Forum
How does it Work 

Well simply there is an option on the top right  on the screen Once you launch All applications icon on the home screen, The 'Edit' Option lets you to remove or disable the apps that have been pre loaded with the Samsung Galaxy S6 and the S6 edge.  The news has been revealed by one of the members of the popular xda developers form.
Samsung Galaxy S6 EDGE
Samsung Galaxy S6 and S6 edge
There will be lot more to be known about the device, I will updated this post once I get to know more about the device and post some hands on review of the Smartphone.


Architecture of LTE

There are three main components in the Architecture of LTE, UE, EUTRAN and EPC. The evolved packet core communicates with the external Internet entities such as IMS, Private and corporate networks. The UE, EUTRAN and EPC have their own internal architectures that will be explained in detail in the later sections. The interfaces between different parts of the system are denoted as, interface between UE and eNB as Uu, Interface between eNB and EUTRAN as S1 and interface between EPC and external network as SGi.

Architecture of LTE 

  • User Equipment (UE)
  • Evolved UMTS terrestrial radio access network  (E-UTRAN)
  • Evolved Packed Core (EPC)



User Equipment (UE)
User equipment is typically divided into two components Mobile termination (MT) and Terminal equipment(TM).  The mobile termination handles all the communication functions and the terminal equipment handles all the data. All the communication between the UE and EUTRAN occurs with the help of the SIM card module inside the UE. The SIM card runs an application that is known as Universal subscriber identity module (USIM). The USIM stores user’s data such as Phone number, Mobile country code and the Mobile radio network operator information. The USIM also supports various security related features that help UE to connect to LTE networks. For example during the Initial LTE attach procedure the UE generate keys that help to authenticate the UE in LTE network.
LTE network supports both IPv4 and IPv6 or dual stack IP versions (Both IPv4 and IPv6 simultaneously). In LTE, UE can have either IPv4 or IPv6 for different networks it connects. A mobile can have both IPv4 and IPv6 address simultaneously if the mobile operator and the UE support both address. The Mobile units can have wide ranges of radio capabilities such as Maximum data rates, number of frequencies supported, Carrier aggregation etc. A UE category has been developed that helps to differentiate different versions of radios capabilities in UE’s. It mainly covers the Maximum data rate that a mobile can send and receive.

UE catageories


These high data rates are achieved using combining different spectrum's to achieve maximum bandwidth which is also known as Carrier aggregation. The process of CA will be explained in upcoming posts.

Telecom 4G and LTE Posters

Telecom Posters



Please Click on the links below to view/Download the Posters .

Telecom Networks Posters by Nexus : Click Here

LTE Evolved Packet System Architecture by Alcatel Lucent  : Click Here

Next Generation Mobile Network – The Evolution to 4G : Click Here

LTE-Advanced by  Rohde-schwarz : Click Here

WIMAX poster by Aniritsu : Click Here

KPIs for LTE

Lits of KPI's for LTE optimization.

These are  just a list of KPI's for LTE optimization, Please let us know if you know more so we can update it here.
  • eRAB Establishment Success Rate (%) 
  • Abnormal eRAB Release (%) 
  • Total number of eRABs (per cell) 
  • RRC establishment Success Rate (%) 
  • Intra LTE mobility Success Rate (%) 
  • Connected Users License capacity limit (per RBS) 
  • Average percentile of Connected Users License utilization (per RBS) 
  • Connected Users License (CUL) Time Congestion (per cell) 
  • RRC Failure Rate due to CUL (per cell) 
  • Peak number of Connected Users (per cell) 
  • DL Baseband Capacity utilization per RBS (%) 
  • UL Baseband Capacity utilization per RBS (%) 
  • Average DUL main Processor Load (%) 
  • Peak number of UE in RRC_CONNECTED mode 
  • Number of neighbour relations added by the ANR function 
  • Number of neighbour relations removed by the ANR function 
  • PDCCH utilization per cell (%) 
  • Average UE DL Throughput (Mbps) 
  • Average UE UL Throughput (Mbps) 
  • DL PDCP volume per cell (kilobits) 
  • UL PDCP volume per cell (kilobits) 
  • Average cell throughput (PDCP DRB) DL (kbps) 
  • Average cell throughput (PDCP DRB) UL (kbps) 
  • Max UE DL Latency (ms) 
  • Physical Resource Block (PRB) 
  • DL Physical Resource Block (PRB) utilization (per cell) 
  • UL Physical Resource Block (PRB) utilization (per cell) 
  • Average Noise and Interference Power on PUSCH 
  • Average Noise and Interference Power on PUCCH

LTE Initial Attach Call Flow ( Part 1 )

In this case we will look initial attach procedure of an unknown UE to a LTE network for the first time.

1)  Radio Link synchronization:
In order for the UE to connect to eNB it needs to establish a radio connection with eNB. UE selects the eNB through PLMN selection and cell search procedure. After an RRC signalling connection the UE can then communicate with the eNB. UE is in EMM-De-registered state at this point of time.

2) ECM connection establishment:
UE sends an attach Request (IMSI, UE capability) message to MME via eNB through NAS layer.In order for the attach request message to  be delivered to MME, ECM connection between UE and MME is required.At the end of ECM connection, RRC connection between UE and eNB  and S1 signalling  connection between eNB and MME is required.NAS messages are send as RRC messages when passing through RRC connection and SI AP when passing through S1 signalling collection.

3) RRC Connection Establishment:
An RRC connection is established between the RRC layers of UE and eNB.
The procedure of RRC connection between UE and eNB is as follows.

UE--->eNB [ RRC connection request ]
UE sends an 'RRC connection request' to eNB  ( Establishment Cause=“Mobile Originating Signalling”). The message sent by UE is  delivered to eNB through SRB 0 and  CCCH ( Common control channel )
SRB 0 is used by all UE's in a cell.

eNB --> UE [ RCC connection setup ]
The eNB allocates SRB1 to UE by sending an RRC connection setup message, which is delivered through SRB 0 and CCCH.Now the uplink/downlink resources of the UE are controlled by eNB.UE can now use the resources allocated to UE by eNB through SRB configuration.

UE --> eNB [ RRC Connection Setup Complete ]
The UE notifies the eNB that the RRC connection setup is completed by sending it an RRC Connection Setup Complete message through SRB 1 and DCCH (Dedicated Control Channel).The attach request message that was delivered to the NAS layer is sent to eNB along with RRC connection setup complete message.


4) S1 Signalling connection establishment:

Control messages between eNB and MME are sent Over S1-MME interface as embedded in S1 AP messages. S1-AP messages are delivered through S1 signalling connections dedicatedly for each user.S1 Signalling connections are defined by an ID pair ( eNB UE  S1 AP ID , MME UE S1 AP ID). These are allocated by eNB and MME for identifying UE's .The eNB allocates an eNB UE S1 AP ID for establishment of S1 signalling connection and sends the MME an attach request as embedded in  an ' initial UE message'. The Attach Request message is delivered as embedded in the NAS-PDU field of the Initial UE Message. The Initial UE Message consists of the following information elements:
Initial UE Message (eNB UE S1AP ID, NAS-PDU, TAI, ECGI, RRC Establishment Cause) 

  • eNB UE S1AP ID: ID identifying UEs in an eNB over S1-MME interface (Uplink) 
  • NAS-PDU: a NAS message (Attach Request) 
  • TAI: shows the TA a UE is located in 
  • ECGI: shows the cell a UE is located in 
  • RRC Establishment Cause = mo-Signalling: indicates the signalling was generated by a UE

Now MME received the UE intial context message and assigns an  MME SI AP UE ID. After the allocation the signalling connection between the eNB and MME is established. MME S1 AP UE ID is used later when MME identifies UE over S1-MME interface.

5) IMSI Acquisition 
The NAS layer of the MME acquires the IMSI of  the UE from the intial message and also determines the network capability of the UE and the security algorithms it supports.Now the MME performs authentication and NAS security keys setup procedures for secured delivery of NAS messages.

An Overview Till Now :

  • UE Has sent an RRC connection request.
  • eNB Receives RRC connection request and sends UE RRC connection setup message and allocates resources to UE
  • UE sends an 'Attach Request' along with RRC connection complete message to eNB 
  • eNB initiates S1 Signalling connection  between eNB and MME for the UE 
  • MME recives Attach request from UE
  • MME knows UE IMSI and network capability.

The next will be Available here soon

Please Refer to the List of other topics in LTE tutorials

LTE Attach in Bullet Points

UE switched ON - Cell selection

UE > eNB - RRC connection request

eNB > UE - RRC connection set-up

UE > eNB - RRC Connection complete+ Attach request + PDN conn request

eNB > MME - Initial UE message + NAS-PDU ( Attach request + PDN conn request )

MME > HSS - Authentication request ( Acquisition of Authentication vector )

HSS > MME - Authentication information Answer ( RAND, AUTN, XRES, Kasme )

MME > UE -  Authentication request ( RAND, AUTN )

UE - UE generates Auth response from the information received and uses the same algorithm HSS used to generate AV

UE > MME - Authentication response ( RES )

MME - Authenticates UE if RES = XRES (  UE authenticated )

MME - Generates Security keys 

MME > UE -  Security Mode  command

UE - Generates NAS keys

UE > MME - Security mode Complete. 

MME > HSS - Location update request

HSS - Registers UE IMSI , MME ID.

HSS > MME -  Update location answer  ( Subscriber profile + APN + P-GW + QoS )

MME - MME stores APN & subscriber profile 

MME - Assigns EPS bearer ID & P-GW selection by HSS or MME

MME > S-GW - Create session request 

S-GW > P-GW - Create session request

P-GW - Assigns IP address to UE 

P-GW > PCRF -  Notification of EPS session set-up

PCRF - Determines PCC ( Policy charging & control ) policies for the EPS session to established

PCRF > P-GW - Acknowledging EPS Session Establishment

P-GW - Policy Enforcement (Install Policy Rule)

P-GW > S-GW - Create session response

S-GW > MME - Create session Response

MME - Generates Various parameters ( UE AMBR  )

MME - eNB - Initial context set-up request ( Attach accept in NAS-PDU )

eNB - Receives S-GW address and generates keys 

eNB > UE -  Security mode command

UE - UE generates Kenb and AS keys

UE > eNB - Security mode complete

eNB > UE - RRC connection reconfiguration + Attach Accept

UE - DRB is created between UE and eNB

UE > MME - Attach complete ( via eNB )

eNB > MME - Initial context set-up response

MME > S-GW -  - Modify bearer request + eNB address + EPS bearer ID

S-GW > MME -  Modify bearer response

S1 bearer is established between eNB and S-GW. EPS default bearer is UP and user can exchange data.

 

Copyright @ 2013 Telecom .

Designed by Mr.X & Sponsored By Telecom 4