Which of the following parameters are included in the measurement target IE of the 5G measurement configuration message?
Select All that Apply
Cell frequency
Serving cell offset
SMTC
SSB frequency
In 5G NR, Radio Resource Control (RRC) measurement configuration enables the UE to evaluate serving and neighboring cells for mobility, beam management, and radio-resource optimization.
Option A — Cell frequency: The intended parameter identifies the carrier frequency associated with the target cell or measurement configuration. This information allows the UE to determine the applicable frequency resources.
Option C — SMTC: SSB Measurement Timing Configuration specifies when the UE should perform SSB-based measurements. It defines the measurement-window periodicity, timing offset, and duration.
Option D — SSB frequency: The SSB frequency identifies the frequency location of synchronization signals that the UE must detect and measure.
Option B — Serving cell offset: Serving-cell offsets are used in measurement-event evaluation and reporting criteria. They are not part of the target-identification fields described by the intended question.
The standardized NR MeasObjectNR information element explicitly includes ssbFrequency and smtc1 , but does not define a separate field literally named Cell frequency within that structure.
Therefore, A, C, and D represent the intended Huawei-oriented answer.
Official Reference: 3GPP TS 38.331, Section 6.3.2, MeasObjectNR Information Element ; Section 5.5, Measurements .
Technical warning / qualification: The exact measurement target IE referenced by the question is not identified. While C and D are directly supported by the NR measurement-object specification, option A requires confirmation against the intended Huawei signaling definition. The answer is provisional rather than fully verified.
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 parameters relate to open-loop power control for PUCCH power control?
Select All that Apply
PUCCH SCS
UCI format
Number of RBs configured for the PUCCH
PUCCH MCS
Options A, B, and C are the intended answers because the 5G NR Physical Uplink Control Channel (PUCCH) transmit-power calculation depends on subcarrier spacing, allocated radio resources, and format-dependent control-information characteristics.
PUCCH carries Uplink Control Information (UCI), including HARQ acknowledgments, Scheduling Requests (SR), and Channel State Information (CSI).
PUCCH power control combines open-loop parameters with dynamically accumulated closed-loop Transmit Power Control (TPC) adjustments.
The open-loop component establishes a transmission-power baseline using configured power offsets, downlink path-loss estimation, and the transmission-resource configuration.
Option A — PUCCH SCS: Subcarrier spacing contributes to the bandwidth-dependent term of the PUCCH transmit-power formula.
Option B — UCI format: The intended concept concerns PUCCH format and UCI payload-dependent adjustments. Different PUCCH formats have different symbol structures, payload capacities, and associated power-adjustment requirements.
Option C — Number of RBs: The allocated PUCCH Resource Blocks affect transmission bandwidth and the corresponding power calculation.
Option D — PUCCH MCS: Unlike PUSCH, PUCCH power control does not use a conventional PUCCH MCS index as an independent open-loop power-control parameter.
Consequently, options A, B, and C correctly identify the relevant factors in the intended examination context.
Official Reference: 3GPP TS 38.213, Section 7.2.1, PUCCH Transmit Power ; TS 38.331, PUCCH-PowerControl Configuration .
Technical warning / qualification: The original option B states UCI format . The standards use the more precise concepts of PUCCH format and UCI payload-dependent adjustments. For technical accuracy, this option should be revised before publication. The original wording has been preserved above.
In NSA networking, which of the following counters measure the number of abnormal SgNB releases caused by their respective causes?
Select All that Apply
N.NsaDc.SgNB.Rel.Coverage
N.NsaDc.SgNB.AbnormRel.Radio.UeLost
N.NsaDc.SgNB.AbnormRel.NoReply
N.NsaDc.SgNB.AbnormRel.Trans
Options B, C, and D are the intended answers because their counter names explicitly identify abnormal Secondary gNodeB (SgNB) release events and distinguish the associated failure causes.
In Non-Standalone (NSA) E-UTRA–NR Dual Connectivity, the SgNB provides NR secondary connectivity while the LTE eNodeB maintains the master connection.
Abnormal SgNB releases can occur because of radio-link failures, UE communication failures, transmission-network faults, or unsuccessful signaling procedures.
Option B — N.NsaDc.SgNB.AbnormRel.Radio.UeLost identifies abnormal release events associated with loss of UE communication at the radio layer.
This counter is relevant when investigating coverage deterioration, radio-link instability, or unexpected UE disappearance from the secondary connection.
Option C — N.NsaDc.SgNB.AbnormRel.NoReply identifies abnormal releases associated with missing expected responses during applicable procedures.
Option D — N.NsaDc.SgNB.AbnormRel.Trans identifies abnormal releases attributable to transmission-layer problems, such as faults affecting transport connectivity or associated signaling paths.
Option A — N.NsaDc.SgNB.Rel.Coverage identifies coverage-related SgNB releases, but its name does not classify those events as abnormal releases.
The key distinction is between general release counters and counters explicitly classified under abnormal-release causes.
Therefore, B, C, and D are the intended selections.
Official Reference: 3GPP TS 37.340, E-UTRA and NR Multi-Connectivity , Secondary Node Release procedures; TS 28.552, 5G Performance Measurements .
Technical warning / qualification: The precise N.NsaDc counter names are Huawei-specific. Their interpretations are consistent with the updated question bank, but the official Huawei performance-counter dictionary has not been supplied or independently verified. The 3GPP references establish the procedure, not these exact counter definitions.
Which of the following slot configurations has a relatively large E2E delay?
8:2 (5 ms single-period DDDDDDDSUU)
7:3 (2.5 ms dual-period DDDSUDDSUU)
4:1 (2.5 ms single-period DDDSU)
3:1 (2 ms single-period DDSU)
Option A is the expected answer because its slot configuration creates a relatively long interval between uplink transmission opportunities, increasing the scheduling-related latency experienced by applicable traffic.
In Time Division Duplex (TDD) operation, uplink and downlink transmissions share the same carrier-frequency resources but occur in different time-domain intervals.
The configured slot pattern determines the distribution of downlink slots, uplink slots, and special slots.
In the 8:2 configuration, the sequence DDDDDDDSUU contains seven consecutive downlink slots, followed by a special slot and two uplink slots.
For 30 kHz subcarrier spacing, a normal slot lasts 0.5 ms, producing a 5 ms configuration period.
Consequently, uplink packets arriving shortly after the available uplink opportunities may experience substantial waiting time before the next usable uplink slot.
The other configurations provide more frequent uplink opportunities, which generally reduces waiting time for uplink transmissions and selected feedback procedures.
Such delays can influence uplink scheduling requests, HARQ timing, and application-level responsiveness.
However, actual end-to-end latency also depends on traffic direction, processing delays, network congestion, retransmissions, and transport-network conditions.
Therefore, option A is the best answer when comparing the scheduling-related latency implications of the listed TDD patterns.
Official Reference: 3GPP TS 38.213, Section 11.1, UE Procedures for Determining Slot Format ; TS 38.331, TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated .
Technical warning / qualification: The comparison assumes similar operating conditions and emphasizes uplink opportunity waiting time. The slot pattern alone does not establish a universally highest end-to-end latency for every traffic flow.
Different TDD slot configurations influence the network’s downlink coverage, service rate, and air-interface RTT delay. Therefore, these factors must be considered during planning.
True
False
The statement is true because Time Division Duplex (TDD) slot configuration determines the distribution and timing of uplink and downlink transmission opportunities, affecting service capacity, radio performance, and scheduling-related latency.
In 5G NR TDD, a carrier uses different time-domain resources for downlink and uplink communication.
The configured pattern defines downlink slots, uplink slots, and special slots containing a combination of downlink, uplink, or flexible symbols.
A configuration allocating a greater proportion of resources to the downlink generally provides more downlink transmission capacity, assuming comparable radio conditions and scheduling efficiency.
However, reducing uplink opportunities may increase uplink waiting time and affect the timing of uplink control information, HARQ feedback, and associated application transactions.
TDD configuration also influences downlink service performance at cell boundaries.
Although slot configuration does not directly change propagation loss or the fundamental RF link budget, the available downlink time resources can affect the achievable service rate and service-coverage boundary.
Air-interface round-trip time is influenced by the interval between transmission and the corresponding feedback or return-transmission opportunity.
Therefore, TDD planning must balance service-rate requirements, uplink capacity, downlink capacity, synchronization constraints, and latency objectives.
Consequently, the statement correctly identifies TDD slot configuration as a significant planning consideration.
Official Reference: 3GPP TS 38.213, Section 11.1, Slot Configuration ; TS 38.331, TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated .
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 .
Only one codeword is needed when four streams are transmitted over the air interface.
True
False
The statement is true because 5G NR supports mapping a single codeword to as many as four spatial transmission layers in the standard downlink spatial-multiplexing configuration.
A codeword represents a sequence of encoded data bits generated through channel coding and associated processing before modulation and layer mapping.
Spatial layers are logical MIMO transmission streams used to transport data across multiple spatial dimensions of the radio channel.
The number of codewords is not necessarily equal to the number of MIMO layers.
According to 3GPP TS 38.211, the PDSCH codeword-to-layer mapping procedure supports one codeword for transmissions using one, two, three, or four layers.
For example, when four layers are scheduled, modulation symbols from the single codeword are distributed across four layers according to the specified mapping procedure.
When the configured downlink transmission uses five to eight spatial layers, two codewords are supported, with the corresponding layer allocation determined by the applicable mapping table.
This distinction is essential when evaluating MIMO transmission rank, transport-block processing, HARQ operation, and channel-coding requirements.
Consequently, a four-layer spatial-multiplexing transmission requires only one codeword under the standardized NR mapping configuration.
Official Reference: 3GPP TS 38.211, Section 7.3.1.3, Table 7.3.1.3-1, Codeword-to-Layer Mapping for Spatial Multiplexing .
A gNodeB can collect the causes of handover-preparation and handover-execution failures.
True
False
The statement is true because 5G NR performance-management procedures support the collection of handover failure statistics, including information that identifies failures during both handover preparation and handover execution.
The handover procedure contains distinct preparation and execution phases.
During handover preparation , the source gNodeB coordinates with the target gNodeB or the core network to prepare the necessary radio and session resources.
Preparation can fail because of resource-admission restrictions, incompatible configuration, transport-signaling problems, or other procedural errors.
Applicable NGAP and XnAP handover failure messages include cause information that can be recorded for network performance analysis.
During handover execution , the UE attempts to access the target cell and complete the required radio-connection reconfiguration.
Execution failures can occur because of radio-link problems, random-access failures, timer expiration, or unsuccessful completion of the mobility procedure.
The gNodeB can collect relevant failure statistics through standardized performance measurements and applicable signaling or UE failure reports.
3GPP TS 28.552 defines separate counters for unsuccessful handover preparation and execution, including failure-cause-specific subcounters.
These measurements assist operators in distinguishing admission-control problems from radio-mobility and execution problems.
Therefore, option A is correct.
Official Reference: 3GPP TS 28.552, Sections 5.1.1.6.1.3 and 5.1.1.6.1.9, Number of Failed Handover Preparations and Executions ; TS 38.423, XnAP Handover Procedures .
Which of the following timers is specific to 5G networks?
T311
T310
T300
T319
T319 is the correct answer because it is defined in the 5G New Radio (NR) Radio Resource Control (RRC) specification to supervise the RRC connection resume procedure.
5G NR supports three principal RRC states: RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE. The RRC_INACTIVE state allows a UE to retain its Access Stratum (AS) context while reducing signaling overhead and power consumption.
When a UE in RRC_INACTIVE needs to resume communication, it initiates the RRC connection resume procedure by transmitting an RRCResumeRequest or RRCResumeRequest1 message. Timer T319 supervises this procedure.
If the UE receives an appropriate RRCResume message, T319 is stopped, and the UE restores the relevant radio-bearer configuration and transitions to RRC_CONNECTED.
If T319 expires before successful completion, the UE performs RRC resume failure handling and enters RRC_IDLE.
The remaining timers are also present in LTE:
T300: Supervises RRC connection establishment.
T310: Supports radio-link failure detection.
T311: Supervises cell selection during RRC connection reestablishment.
Therefore, among the listed options, T319 is specifically associated with the NR RRC connection resume procedure.
Official Reference: 3GPP TS 38.331, Sections 5.3.13.3–5.3.13.5, RRC Connection Resume , and Section 7.1.1, RRC Timers .
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.
How many narrow beams are transmitted when the 4:1 slot configuration and 30-kHz subcarrier spacing are used, the SSB pattern is case C, and the maximum number of SSBs is 8?
8
4
7
1
The expected answer is eight narrow beams because the described configuration permits up to eight Synchronization Signal/PBCH Blocks (SSBs) within an applicable SSB burst set.
In 5G NR, beam sweeping enables the gNodeB to transmit synchronization information in different spatial directions, allowing UEs to identify suitable beams during cell search and initial access.
An SSB contains the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Physical Broadcast Channel (PBCH), and associated demodulation reference signals.
SSB pattern Case C uses 30 kHz subcarrier spacing and specifies candidate SSB transmission locations within the applicable half-frame.
For a configuration supporting a maximum of eight SSBs, the network can associate eight transmitted SSBs with eight distinct beam directions.
The specified 4:1 TDD slot configuration influences the available downlink transmission occasions, while the SSB pattern defines the candidate synchronization-block positions.
When all eight candidate SSB positions are configured for transmission, the gNodeB can sweep eight narrow beams during the SSB burst set.
However, the maximum supported SSB count and the number actually transmitted are not necessarily identical. The network can configure a smaller active subset.
Therefore, eight is the intended answer under the assumption that all eight SSB positions are enabled.
Official Reference: 3GPP TS 38.213, Section 4.1, Cell Search and SS/PBCH Block Candidate Positions ; TS 38.211, Section 7.4.3, SS/PBCH Block Structure .
Technical warning / qualification: The question specifies a maximum of eight SSBs but does not explicitly state that all eight are transmitted. The correct choice is A under the intended full-beam configuration.
Which of the following channels or signals uses the same transmit power as the PUSCH?
PRACH
PDSCH
SRC
PUCCH
In NR, SRS is transmitted by the UE to provide uplink channel-sounding information for scheduling, channel estimation, beam management, and MIMO-related procedures.
The SRS transmission-power calculation follows the uplink power-control principles specified in 3GPP TS 38.213.
These principles include configured target-power parameters, transmission bandwidth, estimated path loss, path-loss compensation, and applicable closed-loop adjustments.
Under certain configurations, SRS may share a power-control adjustment state with PUSCH. Under other configurations, separate adjustment states and SRS-specific parameters are used.
Consequently, SRS transmission power is related to the PUSCH power-control mechanism but is not necessarily numerically identical to PUSCH transmit power .
PRACH has its own random-access transmit-power and power-ramping procedures.
PUCCH uses a separate uplink power-control calculation, while PDSCH is a downlink physical channel.
The intended comparison therefore points toward SRS, represented incorrectly as SRC in the original choices.
Official Reference: 3GPP TS 38.213, Sections 7.1 and 7.3, PUSCH and SRS Transmit Power Control .
Technical warning / qualification: Replace option C, SRC , with SRS . The question should also state uses a related power-control mechanism rather than uses the same transmit power , because the latter is not universally correct.
TESTED 21 Nov 2026
Copyright © 2014-2026 DumpsTool. All Rights Reserved