LTE-Advanced Interview Prep

LTE vs LTE-Advanced vs LTE-A Pro vs 5G NR (migration map)

Sample interview questions

1. In LTE-A Release 10 CA with one PCell and three SCells across two bands, which statement about PCell vs SCell roles is correct?
   • A. PCell carries RRC signaling, NAS, security, and the single PUCCH; SCells add PDSCH and PUSCH capacity but no PUCCH and no separate RRC state. ✓
   • B. Each SCell terminates its own RRC connection so the UE maintains parallel security contexts on each component carrier.
   • C. PUCCH is replicated on every configured cell to give the scheduler redundant uplink control feedback paths during handover.
   • D. SCell activation is implicit and follows the strongest measured RSRP, so the eNB cannot pin which carrier serves as SCell.

   Option A is correct because Release 10 CA places RRC signaling, NAS, AS security context, and the single PUCCH on the PCell; SCells add PDSCH and (when uplink CA is configured) PUSCH bandwidth but do not carry their own RRC connection or PUCCH. Option B is incorrect because the UE has one RRC connection and one AS security context across configured CCs — SCells inherit the PCell's security keys. Option C is incorrect because replicating PUCCH on every cell would break the single-PUCCH design. PUCCH on an SCell first appears in Release 13 PUCCH-SCell configurations for capacity-limited deployments, not in the Rel-10 baseline. Option D is incorrect because SCells are added, modified, and removed by eNB-controlled RRC reconfiguration messages — the eNB selects which carrier serves as SCell based on band combinations the UE has signalled support for.

2. A Cat-12 LTE UE reports CQI table 2 in good SNR. What lets the scheduler pick 256-QAM on the LTE downlink, and what is the common fallback driver?
   • A. SNR meets the 256-QAM BLER target at 8 bits per symbol; the dominant fallback driver is EVM degradation from a non-linear PA driven into compression at high MCS. ✓
   • B. Higher QAM order provides better performance, so 256-QAM is selected whenever the UE supports CQI table 2; fallback does not happen in good geometry.
   • C. QAM is constant-envelope like PSK and works with nonlinear PAs, so PA backoff is not a factor; fallback fires when DRX starves the UE of CSI reports.
   • D. CRS is used for MIMO transmission modes including 256-QAM, so the dominant fallback driver is CRS coverage loss in the centre RBs.

   Option A is correct because 256-QAM at 8 bits per symbol needs roughly 18-22 dB SNR at the target BLER. CQI table 2 is the explicit signalling that the UE can decode 256-QAM under its current SNR. The dominant practical fallback driver is in-band distortion at high MCS: when the PA is driven into compression, the 256-QAM constellation points smear beyond the decision boundaries and EVM exceeds the spec. Option B is incorrect because Higher QAM order provides better performance is the KB-flagged misconception. Higher M actually requires higher SNR for the same BER; the scheduler must match modulation to channel conditions. Option C is incorrect because QAM is constant-envelope like PSK and works with nonlinear PAs is the canonical false claim — QAM has varying amplitude and requires a linear PA. Clipping a 256-QAM signal causes spectral regrowth and in-band EVM that destroys the constellation. Option D is incorrect because CRS is used for MIMO transmission modes is the KB-flagged false claim: CRS supports TM1-4, but TM7-10 (the transmission modes paired with 256-QAM and advanced beamforming) use DMRS (demodulation reference signals) instead.

3. A Rel-11 interference-management deployment turns on CoMP Joint Transmission across two macro eNBs. Which CoMP cost statement is correct?
   • A. CoMP requires CSI sharing, tight synchronization, and high-capacity low-latency backhaul; practical gains are modest because backhaul delay erodes the coherent-combining advantage at the cell edge. ✓
   • B. CoMP provides capacity gains with no cost; once the X2 link is up the joint precoder is computed for free at each eNB.
   • C. ICIC eliminates co-channel interference, so CoMP JT adds value in deployments that did not deploy ICIC first.
   • D. CoMP eliminates inter-cell interference by making cells transmit orthogonally in time, identical to time-division between sectors.

   Option A is correct because CoMP JT depends on three expensive pieces working in concert: per-UE CSI shared across cooperating eNBs over the X2 (or fronthaul-class) link, tight phase and time synchronization between transmitters, and a low-latency backhaul that delivers the CSI before it goes stale. Real-world gains are more modest than simulation studies suggest precisely because backhaul delay and CSI quantization erode the coherent-combining benefit. Option B is incorrect because CoMP provides capacity gains with no cost is the KB-flagged false claim. CoMP costs CSI overhead, synchronization tightness, and backhaul capacity; the joint precoder is not free at runtime. Option C is incorrect because ICIC eliminates co-channel interference is the KB-flagged false claim. ICIC reduces edge interference by resource partitioning but sacrifices total capacity; residual interference remains, which is part of why CoMP was introduced as a complementary technique. Option D is incorrect because CoMP eliminates inter-cell interference by making cells transmit orthogonally in time is the contrast-edge false claim. CoMP JT transmits the SAME data coherently from multiple cells, exploiting constructive combining — not time-orthogonal scheduling.

4. A HetNet uses eICIC with ABS pattern 1/8 to protect range-expanded pico cells under macro coverage. Which statement about ABS operation is correct?
   • A. ABS still transmit CRS (cell-specific reference signals) and sync signals, causing residual CRS-pollution interference; macro capacity decreases proportionally to the ABS ratio. ✓
   • B. Almost Blank Subframes transmit nothing, so the pico cell sees a fully silenced macro and the ABS pattern carries no capacity cost on the macro.
   • C. eICIC helps small cells without reducing macro cell performance because ABS subframes blank PDSCH while CRS and sync are migrated to a dedicated guard band.
   • D. ABS pattern selection is unrelated to pico throughput: any non-zero ABS ratio yields the same range-expansion bias regardless of the configured 8-bit pattern.

   Option A is correct because eICIC blanks PDSCH and most of the control region in ABS subframes but still transmits CRS at the configured ports for legacy-UE measurement and synchronization signals (PSS/SSS) on their fixed time-frequency anchors. This residual transmission is called CRS pollution and it caps the achievable interference floor. The macro pays a real capacity cost equal to the ABS ratio (here 1/8 = 12.5% of subframes blanked). Option B is incorrect because Almost Blank Subframes transmit nothing is the KB-flagged false claim. ABS still carry CRS and sync signals — the term almost is doing the work. Option C is incorrect because eICIC helps small cells without reducing macro cell performance is the KB-flagged false claim. Macro capacity decreases proportionally to the ABS ratio; eICIC is a macro-sacrifice for small-cell benefit, not a free lunch. Option D is incorrect because the ABS bitmap pattern determines exactly which subframes are blanked; pico schedulers configure CRE bias and ABS-pattern-aware CSI measurements so the pattern itself does affect achievable pico throughput.

5. In a Rel-10 Type-1 inband relay node (RN), the donor-eNB backhaul shares the access carrier. What does the subframe pattern arrange?
   • A. Configured MBSFN subframes on the access carrier let the relay pause access-link TX, retune to receive donor data, and resume serving its UEs without colliding with its DL. ✓
   • B. The donor eNB and the relay transmit to the same UE simultaneously on the same subframes, so backhaul and access share TX power continuously without partitioning.
   • C. The relay duplexes backhaul and access on different carrier frequencies, so subframe partitioning is not needed and MBSFN configuration is irrelevant here.
   • D. The relay uses Type-2 inband operation, meaning the UE sees the donor eNB cell directly and the relay forwards user-plane traffic transparently.

   Option A is correct because the Release-10 inband Type-1 relay shares the same carrier for backhaul (donor-eNB-to-RN) and access (RN-to-UE) and cannot transmit on both simultaneously. The standard arranges this by reusing MBSFN subframes on the access link: during those configured subframes the RN signals legacy UEs that no PDSCH is being transmitted, retunes to receive the donor eNB on the backhaul, and then resumes access-link service. Option B is incorrect because that would require the relay to transmit and receive on the same band simultaneously, which a half-duplex inband relay cannot do; the MBSFN partitioning is the whole point of the configuration. Option C is incorrect because the Type-1 inband relay shares the carrier — Type-1a outband and Type-1b adjacent-carrier variants use separate frequencies, but the canonical Type-1 inband case is what the question targets. Option D is incorrect because Type-1 relays are standalone cells with their own physical cell ID and their own PSS/SSS — UEs camp on the relay as if it were an ordinary cell. Type-2 relays are layer-2 relays without their own cell identity, which is a different deployment model.

6. Rel-13 LAA aggregates a licensed LTE PCell with an unlicensed 5 GHz SCell. What does the LBT mechanism arrange for Wi-Fi coexistence?
   • A. The eNB runs energy-detect CCA on the 5 GHz SCell before each DL burst and backs off via a randomized contention window when busy; the licensed PCell carries control and the link falls back to licensed-only when LBT denies access. ✓
   • B. LAA blanks Wi-Fi transmissions inside the licensed cell coverage area, so the unlicensed channel becomes a private LTE resource during SCell activation.
   • C. LAA bypasses LBT on the 5 GHz channel because the licensed-carrier anchor already serializes channel access on behalf of unlicensed users in the area.
   • D. LAA replaces LBT with a fixed TDD pattern at 50% duty cycle on the unlicensed carrier, ignoring Wi-Fi activity because the duty cycle is judged sufficiently low to coexist.

   Option A is correct because LAA Cat 4 LBT runs an energy-detect CCA on the unlicensed SCell, defers when the channel is busy, draws a random backoff from a contention window that doubles after a collision, and then transmits a downlink burst with a bounded Maximum Channel Occupancy Time. The licensed PCell continues to carry control and falls back to licensed-only scheduling when LBT denies access for a configured timeout. Option B is incorrect because LAA is required by Release-13 specifications to coexist fairly with Wi-Fi — it cannot blank Wi-Fi or claim the channel. Option C is incorrect because LBT on the unlicensed carrier is the entire coexistence mechanism; the licensed PCell anchor does not authorize the eNB to skip CCA on the unlicensed SCell. Option D is incorrect because LAA Cat 4 is contention-based, not a fixed duty cycle. Fixed-duty-cycle schemes are characteristic of MulteFire prototypes that pre-dated full LAA standardization, not the LAA design.

7. A VoLTE call sets up a QCI=1 dedicated bearer for IMS voice media. What is the QCI=1 contract and why does it bound head-of-line latency?
   • A. QCI=1 is a GBR bearer with 100 ms Packet Delay Budget and a tight Packet Error Loss Rate target; the scheduler treats QCI=1 as high priority and protects voice against bursty QCI=9 queueing. ✓
   • B. QCI=1 is a Non-GBR bearer with best-effort treatment; head-of-line latency is bounded by the radio buffer occupancy with no scheduling priority.
   • C. QCI=1 has no Packet Delay Budget; the scheduler treats VoLTE the same as default-bearer traffic and depends on AMR codec resilience to absorb queueing latency.
   • D. QCI=1 is implemented in the EPC; the eNB scheduler is unaware of QCI=1 and applies the same MAC priority to DRBs from a given UE.

   Option A is correct because QCI=1 in TS 23.203 is a Guaranteed-Bit-Rate bearer with priority level 2, a 100 ms Packet Delay Budget, and a 10^-2 Packet Error Loss Rate target — the contract that VoLTE designs against. The eNB scheduler honours this by raising the MAC priority of QCI=1 DRBs above background QCI=9 default bearers, which protects head-of-line latency for the voice media plane when the radio is congested. Option B is incorrect because QCI=1 is by definition a GBR bearer, not non-GBR; scheduling priority is part of the QCI=1 contract. Option C is incorrect because QCI=1 has a 100 ms PDB by specification; AMR codec packetization (20 ms frames) and the PDB together set the latency budget the scheduler must respect. Option D is incorrect because QCI is signalled end-to-end and the eNB scheduler is the enforcement point — the QCI value drives the per-DRB scheduling priority at the MAC layer.

Frequently asked questions

What is Carrier Aggregation in LTE-Advanced?

Carrier Aggregation (CA) lets a UE simultaneously transmit and receive on multiple component carriers, each up to 20 MHz, to reach effective bandwidths beyond what a single carrier supports. The component carriers can be intra-band contiguous, intra-band non-contiguous, or inter-band, with each combination indexed by a 3GPP CA configuration code. One PCell handles RRC and PUCCH; SCells supplement throughput. CA introduced new RF challenges (filtering harmonics across bands, IM products at the antenna, increased PAPR on UL CA) and new scheduler complexity (cross-carrier scheduling, BSR aggregation). Up to 5 CCs were supported in Release 10; later releases pushed past 32, although terminal-side complexity caps the practical maximum. Sample question kY5aI8Jq drills into the PCell/SCell role separation.

What is CoMP and how does it work?

Coordinated Multi-Point (CoMP) is the LTE-Advanced umbrella for multi-cell techniques that suppress inter-cell interference or jointly serve users from multiple eNBs. The flavors are Coordinated Scheduling / Coordinated Beamforming (CS/CB), where neighboring cells coordinate scheduling decisions or null beams toward each other's edge users, and Joint Transmission (JT), where multiple cells transmit the same data to a UE coherently. CoMP requires tight backhaul (low latency, often X2 or fiber-fronthaul-class), extensive CSI feedback, and clock synchronization. It saw partial deployment because the CSI overhead and backhaul demands were heavier than initially expected; many operators implemented enhanced ICIC instead. Sample question mC4eM5Ns covers the operating-cost reality.

What is eICIC and how does it differ from CoMP?

enhanced Inter-Cell Interference Coordination (eICIC) is a Release-10 feature aimed at heterogeneous networks (HetNets) where macro cells and small cells overlap. The macro cell transmits Almost Blank Subframes (ABS) — subframes with reduced control and no data — at a configured pattern. UEs in the small-cell coverage area but suffering macro interference can be scheduled in the ABS subframes where the dominant interferer is silenced. eICIC is simpler than CoMP: no joint transmission, no per-user CSI exchange, just a coordinated time-domain blanking pattern. Further enhancements (FeICIC) added power control on cell-specific reference signals to reduce the noise floor in ABS subframes. Sample question nE7gO9Pt walks through CRS pollution and the macro-capacity tax.

What features were introduced in LTE-Advanced Release 11 and 12?

Release 11 added Enhanced PDCCH (EPDCCH) — moving control channels from the legacy first-N-symbol region into the data region for better frequency selectivity and beamforming gains — plus Coordinated Multi-Point (CoMP) finalization and improved network-controlled small cell on/off. Release 12 added 256-QAM in the downlink (a 33% peak-rate jump in good SINR), dual connectivity (UE simultaneously attached to a macro and a small cell over the X2 interface), Device-to-Device (D2D, ProSe) for public-safety, and the first MTC enhancements. Release 13 (LTE-Advanced Pro) extended into Licensed-Assisted Access (LAA) for unlicensed-band carriers and brought the first NB-IoT and Cat-M1 specifications, kicking off the IoT track that fed into 5G.

How does LTE-Advanced relate to LTE-Advanced Pro and 5G?

LTE (Releases 8-9) was the original 4G standard with up to 100 Mbps peak rates. LTE-Advanced (Releases 10-12) added Carrier Aggregation, higher-order MIMO, CoMP, eICIC, and 256-QAM, hitting "true 4G" peaks of 1+ Gbps. LTE-Advanced Pro (Releases 13-15) is the marketing brand for further LTE evolution: LAA, NB-IoT, Cat-M1, dual connectivity, vehicular communication. 5G NR (Releases 15+; see /topics/5g-nr) is a clean-slate radio that runs alongside LTE in non-standalone (NSA) mode through Release 15 and standalone (SA) from there. Many LTE-Advanced concepts (CA, MU-MIMO, MU scheduling, beamforming primitives) carried into NR with refinements; the air-interface and core, however, were redesigned.

What is the difference between LTE-Advanced and LTE-Advanced Pro?

LTE-Advanced is the marketing umbrella for 3GPP Releases 10 through 12; LTE-Advanced Pro covers Releases 13 onwards. The split is partly chronological and partly a deliberate branding decision by 3GPP and the GSMA: by Release 13 the LTE standard was layering features (LAA, NB-IoT, Cat-M1, eMBMS enhancements, V2X) that went well beyond the original LTE-Advanced feature set, and the rebrand signalled that LTE was still receiving substantive evolution while 5G NR was being defined in parallel. Engineering-wise the radio is the same air interface; LTE-A Pro just keeps adding capabilities on top of the Rel-10 baseline. Sample question pI5kS6Sw covers one of the headline Pro features (LAA on 5 GHz unlicensed).

When does 5G NR replace LTE-A versus when do they coexist (EN-DC)?

Coexistence is the default for the first half of the 5G rollout. In Non-Standalone (NSA) deployments — the Release-15 Option 3x architecture used by every early commercial 5G network — the UE attaches to an LTE eNB on the licensed anchor and adds a 5G NR gNB as a secondary node over E-UTRA-NR Dual Connectivity (EN-DC) on the X2 interface. The LTE EPC continues to handle control plane and bearer management while NR carries the bulk of the user-plane data on a high-bandwidth FR1 or FR2 carrier. Standalone (SA) deployments replace EPC with 5G Core and remove the LTE anchor entirely; SA is the long-run target for new spectrum (n78, n77, FR2) but operators keep NSA running on existing bands for years because of UE installed base and core-network migration cost. Sample question qK8mU7Tx ties this to the QCI/5QI mapping that VoLTE and VoNR have to navigate during the transition.

What is the role of TM (Transmission Mode) selection in LTE-A?

LTE defines ten downlink Transmission Modes (TM1-TM10) that bind together antenna configuration, reference-signal strategy, and CSI feedback type. TM1 is single-port, TM2 is transmit diversity, TM3 and TM4 are open-loop and closed-loop spatial multiplexing with CRS-based demodulation, and TM7-TM10 are the advanced modes that use UE-specific reference signals (DMRS) for demodulation. TM9 enables 8x8 SU-MIMO with CSI-RS-based feedback, and TM10 adds CoMP. The TM-to-feedback mapping is where many candidates get confused: TM4 uses PMI/CQI/RI feedback against the CRS-based codebook, but TM9/TM10 use CSI-RS for measurement and DMRS for demodulation, decoupling the precoder design from the cell-specific reference structure. Sample question lA1cK2Mr touches the TM-vs-RS structure when discussing why 256-QAM coexists with DMRS-based modes rather than CRS-based ones.

Related topics