For both the VoNR and EPS fallback solutions, the 5GC must interwork with the IMS.
True
False
The statement is true because both Voice over New Radio (VoNR) and Evolved Packet System (EPS) fallback provide voice services through the IP Multimedia Subsystem (IMS), although the radio-access and core-network procedures used to deliver the voice session differ.
In a VoNR deployment, the UE maintains its connection to the 5G Core (5GC) through NR. IMS signaling and media traffic are transported over an appropriate PDU session, with the 5GC supporting QoS-flow establishment, policy enforcement, and connectivity to the IMS network.
The Session Management Function (SMF) manages the corresponding PDU session, while the User Plane Function (UPF) provides user-plane connectivity toward the IMS data network.
EPS fallback applies when the 5G system cannot provide the required IMS voice service directly over its existing radio access.
In this case, the 5GC and NG-RAN coordinate a handover or redirection toward LTE connected to the EPC. IMS voice establishment or continuation then takes place over the EPS.
Importantly, EPS fallback does not mean that the voice-media path remains anchored in the 5GC after fallback. It means that the 5G system participates in IMS voice-service support and coordinates access to EPS when necessary.
Official Reference: 3GPP TS 23.501, Sections 5.16.3.1–5.16.3.10, IMS Support and IMS Voice Service via EPS Fallback .
Assume cell A has a primary synchronization code of 2 and a secondary synchronization code of 1. What is cell A’s PCI?
3
5
7
2
The Physical Cell Identity (PCI) is calculated using the primary and secondary synchronization identity components.
In 5G NR, the PCI identifies a radio cell at the physical layer and assists the UE with cell synchronization, reference-signal processing, and physical-channel operations.
According to 3GPP TS 38.211, the PCI is calculated using:
N_ID^cell = 3N_ID^(1) + N_ID^(2)
Here, N_ID^(1) represents the secondary synchronization identity component, while N_ID^(2) represents the primary synchronization identity component.
The question provides:
Primary synchronization code: N_ID^(2) = 2
Secondary synchronization code: N_ID^(1) = 1
Substituting these values:
PCI = 3(1) + 2 = 5
Therefore, option B is correct.
NR supports 1,008 physical cell identities, numbered from 0 to 1007. These identities are formed from 336 secondary synchronization identity groups and three primary synchronization identity values.
LTE uses the same mathematical PCI formula but supports 504 physical cell identities, corresponding to 168 groups of three identities.
This difference is important in physical-cell-identity planning because PCI collisions and unsuitable neighboring-cell identity configurations can affect synchronization, measurements, and mobility performance.
Official Reference: 3GPP TS 38.211, Section 7.4.2.1, Physical-Layer Cell Identities ; TS 36.211, Section 6.11, LTE Synchronization Signals .
A UE can report the following CSI types for CSI-RS measurement. Which of the statements below is incorrect?
CRI: used to indicate the optimal CSI-RS beam
PMI: reported precoding matrix index, used to confirm the precoding matrix. Its meaning is similar to that in LTE.
RI: used to indicate the optimal layer based on CQI and PMI measurement
CQI: channel quality indicator, used to reflect the downlink channel quality. Its meaning is similar to that in LTE.
Option C is incorrect because the Rank Indicator (RI) identifies the preferred transmission rank, corresponding to the number of spatial layers suitable for MIMO transmission. It does not select an individual optimal layer based on CQI and PMI measurements.
In NR, CSI reporting allows the gNodeB to adapt beamforming, spatial multiplexing, modulation, and coding to the prevailing radio-channel conditions.
The Channel State Information Reference Signal (CSI-RS) provides measurement resources that support these procedures.
CRI (CSI-RS Resource Indicator) identifies the preferred CSI-RS resource. When CSI-RS resources correspond to distinct transmission beams, CRI can indicate the preferred beam.
PMI (Precoding Matrix Indicator) identifies a preferred precoding matrix selected from the configured codebook. This assists the gNodeB in determining suitable spatial transmission weights.
RI (Rank Indicator) specifies the preferred number of MIMO spatial layers, considering the channel's capacity to support simultaneous data streams.
CQI (Channel Quality Indicator) represents the estimated downlink channel quality under the configured reporting assumptions and supports link adaptation.
The distinction is that RI describes transmission rank, not layer identity. In configurations that support a Layer Indicator (LI), LI provides information concerning the strongest layer associated with the reported precoder.
Consequently, option C incorrectly describes the function of RI.
Official Reference: 3GPP TS 38.214, Section 5.2.1, CSI Reporting , including CRI, RI, LI, PMI, and CQI reporting quantities.
For type 0 allocation, bitmaps are used to map resources, and this is applicable to downlink scheduling with a small amount of data because the minimum scheduling unit for this type is one RBG.
True
False
The statement is false in the intended examination context because resource allocation type 0 uses Resource Block Group (RBG) granularity, which is generally coarser than the individual Resource Block (RB) allocation granularity available through type 1.
In NR downlink scheduling, the gNodeB allocates Physical Downlink Shared Channel (PDSCH) resources according to the configured frequency-domain resource-allocation method.
According to 3GPP TS 38.214, type 0 allocation uses a bitmap in which each bit indicates whether a corresponding RBG is assigned to the scheduled UE.
An RBG normally contains multiple consecutive RBs, with its nominal size determined by the Bandwidth Part (BWP) size and the configured RBG-size parameter.
For example, standardized nominal RBG sizes include 2, 4, 8, and 16 RBs.
Type 0 supports flexible selection of adjacent or nonadjacent RBGs, making it useful for scheduling across separated frequency-domain resources.
However, it may allocate more bandwidth than necessary when only a small amount of data must be transmitted.
Type 1 allocation identifies a starting RB and a contiguous allocation length, permitting finer control of the assigned resource quantity.
Therefore, type 0 is not inherently preferable for small-data scheduling merely because its minimum normal allocation is one RBG.
Official Reference: 3GPP TS 38.214, Sections 5.1.2.2.1 and 5.1.2.2.2, Downlink Resource Allocation Types 0 and 1 .
Technical warning / qualification: Type 0 is not prohibited for small packets. The incorrect part is the conclusion that RBG-level granularity makes it particularly suitable for small-data scheduling.
Which of the following parameters determines the PRACH time-domain position?
Logic root sequence
Frequency offset
Ncs
PRACH config index
The PRACH configuration index determines the time-domain opportunities available for Physical Random Access Channel (PRACH) preamble transmission.
PRACH is used during initial network access, applicable mobility procedures, and other operations requiring uplink synchronization or random-access signaling.
In NR, random-access occasions must be configured so that the UE knows when and where it is permitted to transmit a PRACH preamble.
The prach-ConfigurationIndex parameter identifies an entry in the standardized random-access configuration tables.
These tables specify characteristics including the PRACH preamble format, applicable system-frame periodicity, subframe or slot location, starting symbol, and number of time-domain PRACH occasions.
The remaining parameters control different aspects of random access.
Option A — Logic root sequence: The logical root sequence index determines the Zadoff–Chu root sequence used for PRACH preamble generation.
Option B — Frequency offset: The frequency-domain configuration determines the placement of PRACH resources within the available uplink bandwidth.
Option C — Ncs: The cyclic-shift parameter determines the cyclic-shift spacing used to generate different preamble sequences from a common root sequence.
These parameters affect PRACH sequence generation or frequency-domain placement, rather than identifying its scheduling opportunities in time.
Therefore, option D is correct.
Official Reference: 3GPP TS 38.211, Section 6.3.3.2, PRACH Mapping to Physical Resources , Tables 6.3.3.2-2 through 6.3.3.2-4.
Which of the following physical-layer processing procedures is dedicated to the DFT-S-OFDM waveform?
Modulation
Scrambling
Layer mapping
Transformer precoding
Transform precoding is the distinguishing physical-layer processing operation associated with Discrete Fourier Transform-spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM).
In 5G NR, uplink data transmission on the Physical Uplink Shared Channel (PUSCH) can use CP-OFDM or DFT-S-OFDM, subject to the applicable configuration.
DFT-S-OFDM introduces a Discrete Fourier Transform (DFT) operation into the symbol-processing chain before resource mapping and OFDM signal generation. This spreads modulation symbols across the allocated subcarriers.
A principal benefit is the reduction of Peak-to-Average Power Ratio (PAPR) compared with conventional CP-OFDM in typical operating conditions.
Lower PAPR enables the UE power amplifier to operate more efficiently, reducing the required amplifier back-off and potentially improving uplink coverage, particularly for power-limited terminals.
Scrambling, modulation, and layer mapping are not exclusive to DFT-S-OFDM. These operations also occur in other NR physical-layer processing chains.
By contrast, transform precoding provides the characteristic DFT-spreading operation associated with DFT-S-OFDM transmission.
Accordingly, option D is correct because it identifies the processing operation that distinguishes DFT-S-OFDM from conventional CP-OFDM.
Official Reference: 3GPP TS 38.211, Sections 6.3.1.1–6.3.1.4, PUSCH Scrambling, Modulation, Layer Mapping, and Transform Precoding ; TS 38.214, Section 6.1.3.
Technical warning / qualification: The original option states Transformer precoding . The standardized term is Transform precoding . The wording should be corrected in the published question bank.
For NR coverage optimization, the principle is to preferentially optimize SS-SINR and then SS-RSRP.
True
False
Synchronization Signal Reference Signal Received Power (SS-RSRP) measures the received power of the synchronization-signal reference elements and is a fundamental indicator of NR radio coverage.
SS-RSRP optimization establishes whether the received serving-cell signal is sufficiently strong throughout the required coverage area.
Typical corrective actions include adjusting antenna azimuth, electrical downtilt, antenna height, reference-signal transmission characteristics, and site configuration.
Once acceptable signal-strength coverage has been established, the optimization process evaluates signal quality.
Synchronization Signal Signal-to-Interference-plus-Noise Ratio (SS-SINR) measures the synchronization-signal power relative to interference and noise.
Poor SS-SINR can occur even when SS-RSRP is strong, particularly in areas affected by overlapping cell coverage, excessive interference, or unsuitable beam configurations.
Interference coordination, antenna-pattern optimization, and mobility-parameter adjustments may improve SS-SINR and subsequent service performance.
The two measurements must ultimately be considered together because strong signal power does not guarantee acceptable radio quality.
However, the statement reverses the intended priority by placing SS-SINR before SS-RSRP.
Therefore, option B is correct.
Official Reference: 3GPP TS 38.215, Physical Layer Measurements ; TS 28.100, Annex A.1.3, Coverage Optimization Requirements and Measurements .
Technical warning / qualification: The sequence is a planning and optimization guideline, not an absolute 3GPP-mandated workflow. In an interference-limited network, SS-SINR may require immediate attention even when SS-RSRP is adequate.
Which of the following messages can carry NSSAI information?
Select All that Apply
RPC Setup
RPC Setup Request
Registration Request
RPC Setup Complete
Options C and D are correct because Network Slice Selection Assistance Information (NSSAI) can be conveyed through both the NAS Registration Request and the NR RRCSetupComplete message.
In 5G, NSSAI enables the network to identify the network slices requested or supported for a particular UE. Individual slices are represented by Single Network Slice Selection Assistance Information (S-NSSAI), comprising a Slice/Service Type (SST) and an optional Slice Differentiator (SD).
Option C — Registration Request: During 5G registration, the UE may include Requested NSSAI in its NAS Registration Request. This enables the Access and Mobility Management Function (AMF) to evaluate the requested slices against subscription information and network availability.
Option D — RRC Setup Complete: The NR RRCSetupComplete message includes an optional s-NSSAI-List information element. When supplied by the upper layers, this element can communicate S-NSSAI information during RRC connection establishment.
Options A and B are incorrect because RRCSetup and RRCSetupRequest do not contain the corresponding NSSAI information element.
The distinction is that the NAS Registration Request communicates slice information for core-network registration, whereas RRCSetupComplete can provide relevant slice assistance information through access-stratum signaling.
Therefore, C and D are the correct selections.
Official Reference: 3GPP TS 38.331, Section 6.2.2, RRCSetupComplete Message ; TS 24.501, Sections 4.6.2.3 and 8.2.6, Registration Request and Requested NSSAI .
Which of the following cannot be transmitted on the PDCCH?
PDSCH resource indication
PDSCH modulation
PUSCH resource indication
PMI
The Precoding Matrix Indicator (PMI) is the correct answer because PMI is primarily reported by the UE as part of Channel State Information (CSI), rather than being transmitted as a conventional Downlink Control Information (DCI) field on the Physical Downlink Control Channel (PDCCH).
In 5G NR, the PDCCH carries scheduling and control information from the gNodeB to the UE. DCI formats determine whether the signaling concerns uplink transmission, downlink transmission, or another supported control procedure.
For downlink scheduling, DCI formats 1_0 and 1_1 can specify PDSCH resource assignments, including frequency-domain and time-domain resource allocation.
The DCI also contains a Modulation and Coding Scheme (MCS) field. This identifies the modulation order and target coding rate associated with the scheduled PDSCH transmission.
For uplink scheduling, DCI formats 0_0 and 0_1 can provide PUSCH resource allocations and associated transmission parameters.
PMI serves a different purpose. Based on configured CSI-RS measurements, the UE determines a preferred precoding matrix and reports the associated PMI to the gNodeB.
This feedback is conveyed through applicable uplink reporting procedures using PUCCH or PUSCH.
Therefore, PMI is the only listed parameter that is not ordinarily carried as a PDCCH DCI field.
Official Reference: 3GPP TS 38.212, Section 7.3.1, DCI Formats ; TS 38.214, Section 5.2, Channel State Information Reporting .
What is the maximum coverage altitude for low-attitude 5G drone scenarios?
1000m
5000m
500m
100m
The expected maximum coverage altitude is 1,000 meters, according to Huawei's proposed air-to-ground cellular communication architecture for connected-drone applications.
Huawei's Low-Altitude Connected Drone Flight Safety Test Report , published in cooperation with the Civil Aviation Administration of China (CAAC), differentiates the planned aerial coverage capabilities of 4G and 5G systems.
The report describes an integrated air-to-ground communication framework supporting 4G aerial coverage below 300 meters and 5G aerial coverage below 1,000 meters.
This capability is associated with extending cellular-network coverage into the low-altitude airspace used by connected UAVs.
Aerial radio-network planning differs substantially from conventional terrestrial coverage planning. UAVs frequently experience line-of-sight propagation toward multiple base stations, increasing the probability of inter-cell interference.
Traditional antenna downtilt configurations are primarily optimized for ground-level terminals. As UAV altitude increases, serving-cell coverage may depend on antenna sidelobes, and radio-link quality can fluctuate despite relatively strong received signal power.
Technologies such as Massive MIMO, three-dimensional beamforming, antenna optimization, and interference coordination help address these challenges.
The specified 1,000-meter altitude represents the coverage target described in the cited architecture rather than a guaranteed operating height for every commercial deployment.
Official Reference: Huawei/CAAC, Low-Altitude Connected Drone Flight Safety Test Report , Section II, Concepts of Drone Flight Safety , Figure 6.
Which of the following channels or signals support closed-loop power control?
Select All that Apply
PUSCH
PRACH
PBCH
PUCCH
The Physical Uplink Shared Channel (PUSCH) and Physical Uplink Control Channel (PUCCH) support closed-loop transmit-power control in 5G NR.
Closed-loop power control enables the gNodeB to adjust UE transmission power dynamically according to radio-channel conditions, received signal quality, and interference-management requirements.
Option A — PUSCH: The PUSCH carries uplink user data and selected control information. Its transmit-power calculation combines configured open-loop parameters with closed-loop power adjustments communicated through Transmit Power Control (TPC) commands.
These adjustments help maintain reliable uplink reception while limiting unnecessary UE power consumption and inter-cell interference.
Option D — PUCCH: The PUCCH carries uplink control information, including HARQ acknowledgments, scheduling requests, and CSI reports. Its power-control procedure also incorporates TPC commands and the corresponding closed-loop adjustment state.
Option B — PRACH: PRACH uses a random-access transmit-power calculation and power-ramping mechanism. It does not use the conventional PUSCH/PUCCH closed-loop TPC procedure.
Option C — PBCH: PBCH is a downlink broadcast channel transmitted by the gNodeB, so UE uplink closed-loop power control does not apply.
Therefore, PUSCH and PUCCH are the correct selections.
Official Reference: 3GPP TS 38.213, Sections 7.1.1 and 7.2.1, PUSCH and PUCCH Transmit Power Control ; TS 38.321, Random Access Procedure .
Which SSB pattern cases are supported by Huawei NR TDD base stations?
Select All that Apply
CaseB
CaseD
CaseC
CaseA
The intended answers are Case D, Case C, and Case A, corresponding to the SSB transmission patterns identified as supported by the Huawei NR TDD implementation described in the updated question bank.
In 5G NR, Synchronization Signal/PBCH Block (SSB) patterns define the candidate time-domain positions of synchronization blocks within an SSB burst set.
The patterns depend on the SSB subcarrier spacing, operating frequency range, and applicable radio-access configuration.
Case A uses 15 kHz subcarrier spacing and is defined for applicable FR1 operating bands.
Case C uses 30 kHz subcarrier spacing and supports configurations used in applicable low-frequency NR deployments, including TDD bands.
Case D uses 120 kHz subcarrier spacing and is associated with higher-frequency NR operation.
The source material identifies Cases A and C as supported for Huawei low-frequency TDD deployments and Case D for supported high-frequency TDD deployments.
Case B also uses 30 kHz subcarrier spacing and is a valid standardized SSB pattern. Its exclusion here reflects the intended Huawei product-support subset rather than a prohibition imposed by the NR specification.
Therefore, options B, C, and D are the intended answers.
Official Reference: 3GPP TS 38.213, Section 4.1, Cell Search and Candidate SS/PBCH Block Positions ; TS 38.101-1 and TS 38.101-2, applicable band and SSB numerology requirements.
Technical warning / qualification: This is a Huawei software-version-specific question. The standards confirm that Cases A, B, C, and D exist, but do not independently establish the supported subset for every Huawei TDD base-station release. The official Huawei 5G RAN Channel Management Feature Parameter Description for the relevant release is required for final vendor verification.
Which of the following statements regarding throughput-related indicators is incorrect?
The measurement result is more accurate if the last small packet of each data transmission burst and its transmission duration are added.
The uplink/downlink average UE throughput is used to evaluate the user-perceived rate.
The average throughput of a single UE is obtained by dividing the data volume transmitted or received by the UE by the actual data transmission time.
The actual cell throughput can be obtained by dividing the total data transmission throughput within a measurement period by the time when data is transmitted in the cell.
Option A is incorrect under the standardized burst-based throughput measurement methodology because including the final small transmission interval can distort the measured throughput.
In NR performance management, throughput measurements are intended to represent radio transmission performance rather than the average application traffic rate across periods containing idle time.
The relevant measurement procedure distinguishes intervals during which the transmission buffer contains data from intervals when the buffer becomes empty.
The final transmission interval of a data burst may carry only a small residual packet. Including its duration and data volume can introduce a packet-size-dependent effect into the calculated throughput.
3GPP TS 28.554 therefore defines an extended throughput measurement method that excludes the final slot of the burst from the applicable calculation.
Option B is correct because average uplink and downlink UE throughput are used to assess radio-network performance as experienced by users.
Option C describes the general relationship between transmitted data volume and applicable active transmission time, subject to the precise measurement definitions.
Option D expresses a comparable throughput relationship at cell level, although its wording is less precise than the standardized KPI definitions.
Therefore, option A contradicts the specified throughput methodology.
Official Reference: 3GPP TS 28.554, Section 6.3.6.2, Extended Definition of Throughput , Figure 1; TS 28.552, 5G Performance Measurements .
Which of the following cause values can be carried in the SCG failure information message?
Select All that Apply
SCG reconfiguration failure
Number of RLC retransmissions reaching the maximum
T301 timeout
SRB1 integrity check failure
Options A and B are correct because both SCG reconfiguration failure and an RLC maximum-retransmission condition are defined failure causes that can be reported through the Secondary Cell Group (SCG) failure information procedure.
In NR Dual Connectivity, the SCG represents the secondary radio resources provided by the Secondary Node. When an SCG failure occurs, the UE may report the failure to the Master Node without immediately releasing the entire master connection.
Option A — SCG reconfiguration failure: This condition occurs when the UE cannot successfully apply an applicable RRC reconfiguration affecting the SCG. The standardized failure type is scg-reconfigFailure .
Option B — Maximum RLC retransmissions: When the SCG Radio Link Control (RLC) entity reaches its configured maximum retransmission threshold, the UE can initiate SCG failure reporting. The corresponding standardized failure type is rlc-MaxNumRetx .
Option C — T301 timeout: T301 is associated with RRC connection reestablishment. Its expiration is not defined as one of the listed SCG failure types.
Option D — SRB1 integrity check failure: The SCG failure procedure can report an SRB3 integrity failure, not the SRB1 condition specified in this option.
Therefore, A and B are the correct choices.
Official Reference: 3GPP TS 38.331, Section 5.7.3, SCG Failure Information Procedure , and Section 6.2.2, SCGFailureInformation Message and FailureType .
In NSA networking, which procedure is initiated by a UE when a 5G cell change fails?
RPC connection request
RPC connection reestablishment
MR
SCG failure info
The Secondary Cell Group (SCG) failure information procedure is initiated when a UE detects a qualifying failure associated with its NR secondary connection during Non-Standalone (NSA) operation.
In E-UTRA–NR Dual Connectivity (EN-DC), the LTE eNodeB functions as the Master Node, while the NR gNodeB provides secondary radio connectivity.
The NR Primary Secondary Cell (PSCell) serves as the principal serving cell within the SCG.
When a PSCell change fails, the UE may detect an SCG reconfiguration-with-synchronization failure or another relevant SCG failure condition.
Rather than immediately reestablishing the entire LTE master connection, the UE can report the SCG failure to the Master Node.
For EN-DC, the applicable reporting mechanism involves the SCGFailureInformationNR message transported using LTE RRC signaling.
The failure report can identify the failure type and provide available NR measurement information to assist diagnosis and recovery.
The Master Node may subsequently initiate SCG release, modification, or another appropriate recovery procedure.
Options A and B describe connection-establishment or reestablishment procedures rather than the specific reporting action required for an SCG failure.
Option C, MR, represents measurement reporting and is not the dedicated SCG failure notification mechanism.
Therefore, option D is correct.
Official Reference: 3GPP TS 36.331, Section 5.6.13a, NR SCG Failure Information ; TS 38.331, Section 5.7.3, SCG Failure Information .
Technical warning / qualification: The original options use RPC instead of the standardized abbreviation RRC . The wording has been preserved, but options A and B should be corrected before publication.
TESTED 22 Nov 2026