Professional Documents
Culture Documents
Interview Q 1
Interview Q 1
Ans: LTE provides downlink peak rates of at least 100Mbit/s, 50 Mbit/s in the uplink
and RAN (Radio Access Network) round-trip times of less than 10 ms.
Ans: The goals for LTE include improving spectral efficiency, lowering costs,
improving services, making use of new spectrum and reformed spectrum
opportunities, and better integration with other open standards.
Ans: LTE standards are in matured state now with release 8 frozen. While LTE
Advanced is still under works. Often the LTE standard is seen as 4G standard which
is not true. 3.9G is more acceptable for LTE. So why it is not 4G? Answer is quite
simple - LTE does not fulfill all requirements of ITU 4G definition.
Brief History of LTE Advanced: The ITU has introduced the term IMT Advanced to
identify mobile systems whose capabilities go beyond those of IMT 2000. The IMT
Advanced systems shall provide best-in-class performance attributes such as peak
and sustained data rates and corresponding spectral efficiencies, capacity, latency,
overall network complexity and quality-of-service management. The new capabilities
of these IMT-Advanced systems are envisaged to handle a wide range of supported
data rates with target peak data rates of up to approximately 100 Mbit/s for high
mobility and up to approximately 1 Gbit/s for low mobility.
Ans: The E-UTRAN (Evolved UTRAN) consists of eNBs, providing the E-UTRA user
plane (PDCP/RLC/MAC/PHY) and control plane (RRC) protocol terminations
towards the UE. The eNBs are interconnected with each other by means of the X2
interface. The eNBs are also connected by means of the S1 interface to the EPC
(Evolved Packet Core), more specifically to the MME (Mobility Management Entity)
by means of the S1-MME and to the Serving Gateway (S-GW) by means of the S1-
U.
S1-MME :- Reference point for the control plane protocol between E-UTRAN
and MME.
S1-U:- Reference point between E-UTRAN and Serving GW for the per
bearer user plane tunnelling and inter eNodeB path switching during handover.
S3:- It enables user and bearer information exchange for inter 3GPP access
network mobility in idle and/or active state.
S4:- It provides related control and mobility support between GPRS Core and
the 3GPP Anchor function of Serving GW. In addition, if Direct Tunnel is not
established, it provides the user plane tunnelling.
S5:- It provides user plane tunnelling and tunnel management between
Serving GW and PDN GW. It is used for Serving GW relocation due to UE mobility
and if the Serving GW needs to connect to a non-collocated PDN GW for the
required PDN connectivity.
S6a:- It enables transfer of subscription and authentication data for
authenticating/authorizing user access to the evolved system (AAA interface)
between MME and HSS.
Gx:- It provides transfer of (QoS) policy and charging rules from PCRF to
Policy and Charging Enforcement Function (PCEF) in the PDN GW.
S8:- Inter-PLMN reference point providing user and control plane between the
Serving GW in the VPLMN and the PDN GW in the HPLMN. S8 is the inter PLMN
variant of S5.
S9:- It provides transfer of (QoS) policy and charging control information
between the Home PCRF and the Visited PCRF in order to support local breakout
function.
S10:- Reference point between MMEs for MME relocation and MME to MME
information transfer.
S11:- Reference point between MME and Serving GW.
S12:- Reference point between UTRAN and Serving GW for user plane
tunnelling when Direct Tunnel is established. It is based on the Iu-u/Gn-u reference
point using the GTP-U protocol as defined between SGSN and UTRAN or
respectively between SGSN and GGSN. Usage of S12 is an operator configuration
option.
S13:- It enables UE identity check procedure between MME and EIR.
SGi:- It is the reference point between the PDN GW and the packet data
network. Packet data network may be an operator external public or private packet
data network or an intra operator packet data network, e.g. for provision of IMS
services. This reference point corresponds to Gi for 3GPP accesses.
Rx:- The Rx reference point resides between the AF and the PCRF in the TS
23.203.
SBc:- Reference point between CBC and MME for warning message delivery
and control functions.
Ans: LTE technology supports packet based services only, however 3GPP does
specifies fallback for circuit switched services as well. To achieve this LTE
architecture and network nodes require additional functionality, this blog is an
attempt to provide overview for same.
In LTE architecture, the circuit switched (CS) fallback in EPS enables the
provisioning of voice and traditional CS-domain services (e.g. CS UDI video/ SMS/
LCS/ USSD). To provide these services LTE reuses CS infrastructure when the UE
is served by E UTRAN.
Q9. Why sub carrier spacing is more for wifi than LTE
Ans: I think LTE support high mobility support compare to WiFi, which means LTE
technology support you service even when you are moving with very high speed of
the order of around 300Km/h. as we know as the high the mobility of channel less
will be the coherence time ( high doppler shift), due to which we have keep sub-
carrier spacing small for LTE.
Ans: Basically while asking this question they know that guy must be knowing
OFDM but can he differentiate OFDMA.
So without giving details of OFDM (go to my webpage for details) the OFDMA is
multiple access technique in which individual users are assigned subsets of available
subcarriers within one OFDM symbol and hence multiple users can access the link
at the same time.
Q11. What are LTE Network elements?
Ans:
eNB
eNB interfaces with the UE and hosts the PHYsical (PHY), Medium Access
Control (MAC), Radio Link Control (RLC), and Packet Data Control
Protocol (PDCP) layers. It also hosts Radio Resource Control (RRC)
functionality corresponding to the control plane. It performs many
functions including radio resource management, admission control,
scheduling, enforcement of negotiated UL QoS, cell information
broadcast, ciphering/deciphering of user and control plane data, and
compression/decompression of DL/UL user plane packet headers.
Serving Gateway
The SGW routes and forwards user data packets, while also acting as the mobility
anchor for the user plane during inter-eNB handovers and as the anchor for mobility
between LTE and other 3GPP technologies (terminating S4 interface and relaying
the traffic between 2G/3G systems and PDN GW).
DISADVANTAGE:
Ans: VoLGA stands for "Voice over LTE via Generic Access". The VoLGA service
resembles the 3GPP Generic Access Network (GAN). GAN provides a controller
node - the GAN controller (GANC) - inserted between the IP access network (i.e.,
the EPS) and the 3GPP core network.
The GAN provides an overlay access between the terminal and the CS core without
requiring specific enhancements or support in the network it traverses. This provides
a terminal with a 'virtual' connection to the core network already deployed by an
operator. The terminal and network thus reuse most of the existing mechanisms,
deployment and operational aspects.
Ans:
ADVANTAGE:
DISADVANTAGE:
Ans: LTE technology supports packet based services only, however 3GPP does
specifies fallback for circuit switched services as well. To achieve this LTE
architecture and network nodes require additional functionality, this blog is an
attempt to provide overview for same.
In LTE architecture, the circuit switched (CS) fallback in EPS enables the
provisioning of voice and traditional CS-domain services (e.g. CS UDI video/ SMS/
LCS/ USSD). To provide these services LTE reuses CS infrastructure when the UE
is served by E UTRAN.
Ans: The following are some of the principles of 3GPP E-UTRAN security based on
3GPP Release 8 specifications:
The keys used for NAS and AS protection shall be dependent on the
algorithm with which they are used.
The eNB keys are cryptographically separated from the EPC keys used for
NAS protection (making it impossible to use the eNB key to figure out an EPC key).
The AS (RRC and UP) and NAS keys are derived in the EPC/UE from key
material that was generated by a NAS (EPC/UE) level AKA procedure (KASME) and
identified with a key identifier (KSIASME).
The eNB key (KeNB) is sent from the EPC to the eNB when the UE is
entering ECM-CONNECTED state (i.e. during RRC connection or S1 context setup).