H35-581_V2.0 HCIP-5G-RNP&RNO Questions and Answers

The NR Master Information Block (MIB) has a nominal broadcast scheduling periodicity of 80 milliseconds, with repetitions transmitted within the applicable MIB scheduling period.

The MIB is an essential component of 5G NR system-information acquisition. It is carried on the Broadcast Channel (BCH), physically transmitted through the Physical Broadcast Channel (PBCH) within a Synchronization Signal/PBCH Block (SSB).

The MIB contains information required for the UE to acquire System Information Block 1 (SIB1), including essential system-frame and control-channel configuration parameters.

Its information elements include the system frame number components, subcarrier spacing indication, SSB subcarrier offset, and parameters associated with the initial PDCCH configuration.

A distinction must be made between the MIB's nominal 80 ms scheduling periodicity and the repetition periodicity associated with SSB transmission.

An SSB burst may repeat at intervals such as 5, 10, 20, 40, 80, or 160 ms, depending on the applicable configuration and operating procedure.

For typical deployments, the UE may therefore receive repeated PBCH transmissions more frequently than every 80 ms.

The question concerns the standardized nominal MIB scheduling period rather than the interval between every PBCH transmission.

Therefore, 80 ms is the correct answer.

Official Reference: 3GPP TS 38.331, Section 5.2.1.2, System Information Scheduling ; TS 38.212, Section 7.1, Broadcast Channel .

Sounding Reference Signals (SRS) enable a gNodeB to estimate uplink channel characteristics and use the resulting information for beamforming and spatial transmission optimization in Time Division Duplex (TDD) networks.

In TDD operation, uplink and downlink transmissions occupy the same carrier-frequency band at different times.

Under appropriate channel conditions and with suitable radio-frequency calibration, the system can exploit uplink/downlink channel reciprocity.

The UE transmits configured SRS resources, which the gNodeB receives through its antenna array.

By processing these reference signals, the gNodeB estimates channel characteristics associated with different antenna elements and spatial directions.

The resulting Channel State Information can be used to derive downlink precoding weights, identify suitable transmission beams, and support multi-user MIMO scheduling.

SRS-based channel estimation is particularly valuable in Massive MIMO deployments because it reduces dependence on extensive downlink CSI feedback.

The other reference signals have different primary functions.

CSI-RS supports downlink channel-state measurement and CSI reporting.

PT-RS assists with phase-noise estimation and compensation.

DMRS supports channel estimation for demodulating the associated physical-channel transmission.

Therefore, SRS is the correct answer because it supplies uplink sounding information that can be exploited for reciprocity-based downlink beamforming.

Official Reference: 3GPP TS 38.211, Section 6.4.1.4, Sounding Reference Signal ; TS 38.214, Section 6.2.1, SRS Transmission Procedures ; TR 38.922, discussion of TDD channel reciprocity.

Technical warning / qualification: The phrase infinite set of beams is not precise. Actual base stations have finite antenna dimensions and practical implementation constraints. SRS supports channel-based beam and precoder optimization; it does not guarantee selection from a mathematically infinite set of orthogonal beams.

The Medium Access Control (MAC) layer is responsible for multiplexing multiple RLC PDUs into a MAC PDU for transmission over the physical transport channel.

In the 5G NR protocol architecture, the Radio Link Control (RLC) layer processes data received from upper protocol layers and constructs RLC PDUs.

RLC supports segmentation and reassembly of RLC Service Data Units (SDUs), depending on the configured RLC operating mode.

However, the NR RLC layer does not perform concatenation of multiple independent RLC SDUs into one RLC PDU in the manner associated with earlier LTE RLC processing.

Instead, each RLC SDU is used to construct an RLC PDU, or is segmented into multiple RLC PDUs when necessary.

These RLC PDUs are subsequently delivered to the MAC layer.

From the MAC perspective, an RLC PDU is received as a MAC SDU. The MAC multiplexing procedure can combine MAC SDUs belonging to one or several logical channels into a single MAC PDU.

The MAC PDU is then transferred to the physical layer through the corresponding transport channel.

PDCP performs functions such as sequence numbering, ciphering, and header compression where applicable.

PHY performs physical-channel processing, modulation, and transmission.

Therefore, option C correctly identifies the layer responsible for combining multiple RLC PDUs for transmission.

Official Reference: 3GPP TS 38.321, Section 4.4, MAC Functions ; TS 38.322, Sections 4.2 and 5, RLC Sublayer and Data Transfer Procedures .

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 .

Options A, B, and D represent the intended downlink scheduling principles described in the updated question bank.

Downlink scheduling is controlled by the gNodeB, which assigns radio resources and selects transmission parameters according to channel conditions, traffic demand, interference, and retransmission requirements.

Option A: Interference randomization can be used as an interference-management technique in heavily loaded radio networks. Its purpose is to reduce persistent interference effects by varying the relevant transmission or resource-allocation characteristics. However, enabling a particular Huawei interference-randomization feature at high PRB utilization is an implementation-specific recommendation.

Option B: The gNodeB uses HARQ acknowledgment information reported by the UE to determine whether transmitted downlink data has been successfully decoded or whether retransmission may be required.

Option D: Channel Quality Indicator (CQI) feedback provides information about the radio channel and supports Modulation and Coding Scheme (MCS) selection. Higher-quality conditions generally permit higher-order modulation and more efficient coding.

Option C is incorrect because downlink scheduling does not universally require an explicit scheduling request initiated by the UE.

The gNodeB already manages downlink data queues and can schedule available downlink traffic according to the configured scheduling mechanism.

Therefore, A, B, and D are the intended selections.

Official Reference: 3GPP TS 38.214, Sections 5.1 and 5.2, PDSCH Procedures and CSI Reporting ; TS 38.321, Section 5.3.2, Downlink HARQ Operation .

Technical warning / qualification: Options B and D are supported by standardized mechanisms. Option A is a vendor-specific optimization recommendation and requires confirmation against the Huawei scheduling feature documentation for the relevant release.

N310 is the correct answer because it defines the threshold number of consecutive out-of-synchronization indications received from lower protocol layers before the UE starts the applicable radio-link failure detection timer.

In 5G NR, Radio Link Monitoring (RLM) evaluates the quality of the serving radio connection using configured reference signals and associated detection thresholds.

The physical layer continuously evaluates the radio-link condition and reports in-sync or out-of-sync indications to the RRC layer when the applicable requirements are met.

When radio conditions deteriorate sufficiently, the physical layer provides out-of-sync indications.

If the UE receives N310 consecutive out-of-sync indications , the RRC layer starts timer T310, subject to the relevant procedural conditions.

The UE then monitors whether the serving radio link recovers before T310 expires.

If the UE receives N311 consecutive in-sync indications while T310 is running, the timer can be stopped, indicating recovery from the degraded radio-link condition.

If T310 expires without the required recovery, the UE performs radio-link failure handling, which may result in RRC connection reestablishment or transition to RRC_IDLE.

N312 is associated with a separate configured radio-link monitoring mechanism.

The critical distinction is that N310 specifies the consecutive indication threshold, whereas T310 represents the monitoring duration.

Official Reference: 3GPP TS 38.331, Section 5.3.10, Radio Link Failure Related Actions , and Section 7.2, Counters .

System Information Block 5 (SIB5) contains the inter-Radio Access Technology (inter-RAT) cell-reselection parameters required when a UE evaluates a transition from 5G NR to LTE E-UTRA.

In NR, cell reselection is performed primarily while the UE operates in RRC_IDLE or RRC_INACTIVE.

The UE evaluates serving-cell and neighboring-cell measurements according to broadcast frequency priorities, signal-level thresholds, and applicable reselection timers.

SIB5 provides information about E-UTRA carrier frequencies and their associated reselection parameters.

A particularly important parameter is t-ReselectionEUTRA , which specifies the timer associated with inter-RAT reselection toward LTE.

The UE applies this parameter when determining whether the configured reselection conditions have remained satisfied for the required duration.

This mechanism helps prevent excessive movement between NR and LTE cells caused by short-term radio-signal fluctuations.

SIB5 can also contain E-UTRA carrier-frequency lists, reselection priorities, signal thresholds, and speed-dependent reselection scaling factors.

The other listed SIBs are not responsible for carrying the standard NR-to-E-UTRA reselection timer.

Consequently, SIB5 is the correct answer because its information elements explicitly include the E-UTRA reselection configuration.

Official Reference: 3GPP TS 38.331, Section 6.3.1, SIB5 Information Element ; TS 38.304, Cell Reselection Procedures .

The statement is true because Notification Control is an optional Quality of Service (QoS) parameter applicable to Guaranteed Bit Rate (GBR) QoS flows in the 5G system architecture.

In 5G, QoS flows enable differentiated treatment of traffic according to service requirements such as guaranteed throughput, packet delay, reliability, and priority.

GBR QoS flows are characterized by Guaranteed Flow Bit Rate (GFBR) and Maximum Flow Bit Rate (MFBR) parameters.

Notification Control allows the NG-RAN to report when the guaranteed QoS requirements associated with a GBR QoS flow can no longer be satisfied.

According to 3GPP TS 23.501, the Session Management Function (SMF) enables Notification Control when the corresponding QoS Notification Control parameter is present in the Policy and Charging Control (PCC) rule received from the Policy Control Function (PCF).

The parameter is subsequently communicated to the NG-RAN as part of the QoS profile.

When Notification Control is active, the NG-RAN monitors whether the required GFBR, Packet Delay Budget (PDB), and Packet Error Rate (PER) conditions remain achievable.

If these requirements cannot be fulfilled, the NG-RAN sends the appropriate notification toward the SMF.

Notification Control is not mandatory for every GBR QoS flow and is not a standard parameter applied to ordinary non-GBR flows.

Therefore, option A is correct.

Official Reference: 3GPP TS 23.501, Section 5.7.2.4, Notification Control .

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.

All four conditions can prevent a UE from generating or transmitting a valid B1 measurement report during Non-Standalone (NSA) E-UTRA–NR Dual Connectivity (EN-DC) access.

In NSA architecture, the LTE eNodeB acts as the Master Node and configures NR inter-RAT measurements to determine whether an eligible 5G NR cell can be added as a Secondary Node.

Event B1 is triggered when the measured quality of an inter-RAT neighboring cell exceeds the configured threshold, subject to hysteresis and time-to-trigger requirements.

Option A: Excessive received signal power may saturate the UE receiver, degrading synchronization-signal detection and preventing successful NR cell measurements.

Option B: If the LTE-side measurement configuration identifies a frequency that does not correspond to the intended NR SSB carrier, the UE may be unable to detect the target NR synchronization signals.

Option C: If the measured NR signal does not satisfy the configured B1 entry condition, the reporting event is not triggered.

Option D: An abnormal NR cell may fail to transmit the required synchronization signals correctly or provide measurable radio coverage, preventing a valid measurement result.

Therefore, all four conditions are plausible causes of missing B1 measurement reports.

Official Reference: 3GPP TS 36.331, Inter-RAT Measurement Reporting — Event B1 ; TS 38.533, Section 8.4.2, NR Inter-RAT Event-Triggered Reporting Requirements .

MCS index 27 is the expected answer because it represents the highest non-reserved spectral-efficiency entry in the conventional NR PDSCH MCS table supporting 256QAM.

The Modulation and Coding Scheme (MCS) determines the modulation order and target coding rate used for scheduled data transmission.

For 256QAM, the modulation order is Q_m=8, meaning eight coded bits are mapped to each modulation symbol.

According to 3GPP TS 38.214, Table 5.1.3.1-2, MCS index 27 uses modulation order 8 and a target coding-rate parameter of 948/1024.

Its spectral efficiency is approximately 7.4063 bits per resource element before applicable resource overheads.

This makes index 27 particularly relevant when evaluating maximum downlink throughput under favorable radio conditions.

However, an important distinction exists between enabling 256QAM and achieving maximum spectral efficiency.

MCS index 23 also uses 256QAM, with a target coding-rate parameter of 797/1024 and a lower spectral efficiency of approximately 6.2266.

Therefore, both indices 23 and 27 can represent 256QAM modulation, but index 27 provides the higher nominal spectral efficiency.

MCS index 28 is reserved in the referenced table, while index 32 is outside the five-bit MCS index range.

Consequently, B is correct for maximum peak-rate testing.

Official Reference: 3GPP TS 38.214, Section 5.1.3.1, Table 5.1.3.1-2, MCS Index Table 2 for PDSCH .

Technical warning / qualification: Option D also represents 256QAM. The question is unambiguous only if peak-rate testing means selecting the highest non-reserved spectral-efficiency entry. The wording should explicitly state this condition.

Block Error Rate (BLER) is the intended answer because outer-loop power-control algorithms use error-performance feedback to adjust the target received signal quality required for reliable control-channel reception.

PUCCH carries essential Uplink Control Information (UCI), including HARQ acknowledgments, scheduling requests, and configured channel-state reports.

Errors in these transmissions can produce unnecessary retransmissions, incorrect scheduling decisions, and reduced radio-network efficiency.

The distinction between inner-loop and outer-loop power control is important.

Inner-loop power control adjusts transmission power according to the difference between measured signal quality, commonly expressed through SINR, and a configured target.

The gNodeB can issue Transmit Power Control (TPC) commands to modify the UE's PUCCH transmit power.

Outer-loop power control adjusts the target signal-quality requirement according to observed error performance. When reception reliability deteriorates, the target SINR can be increased to improve decoding probability. Conversely, consistently satisfactory error performance can permit a reduction in the target.

RSRP measures received reference-signal power, while power spectral density expresses signal or noise power per unit bandwidth. Neither directly represents the error-performance feedback used in the intended outer-loop mechanism.

Therefore, BLER is the expected examination answer, with implementation-specific qualifications.

Official Reference: 3GPP TS 38.213, Section 7.2.1, PUCCH Transmit Power Control .

Technical warning / qualification: 3GPP specifies the PUCCH power-control signaling and calculations but does not mandate one universal BLER-based outer-loop algorithm. Huawei implementations may use BER or another error-performance measure depending on the radio technology and PUCCH configuration.

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 .

The Physical Downlink Control Channel (PDCCH) is the closest applicable choice for the HARQ control mechanism associated with 5G NR uplink data transmissions.

In NR, uplink user data is transmitted through PUSCH. The gNodeB receives and decodes the transmitted transport block and determines whether retransmission is necessary.

Unlike LTE, NR does not define the Physical Hybrid ARQ Indicator Channel (PHICH) for explicit acknowledgment of uplink transmissions.

Instead, NR employs asynchronous uplink HARQ operation controlled through scheduling information provided by the gNodeB.

The PDCCH carries Downlink Control Information (DCI), including uplink grants specifying the HARQ process identifier, New Data Indicator (NDI), and redundancy version.

When retransmission is required, the gNodeB can schedule the corresponding HARQ process again without toggling its NDI.

When new data is scheduled for the same process, the NDI toggles, allowing the UE to distinguish new transmission from retransmission.

PUCCH , by contrast, carries HARQ-ACK feedback transmitted by the UE for downlink PDSCH reception. It does not carry acknowledgment information from the gNodeB for uplink PUSCH reception.

Therefore, PDCCH is the closest answer, but it carries uplink HARQ scheduling instructions rather than an explicit standalone ACK/NACK indication.

Official Reference: 3GPP TS 38.321, Sections 5.4.1–5.4.2, UL Grant Reception and HARQ Operation ; TS 38.212, Section 7.3.1, DCI Formats .

Technical warning / qualification: The document's explanation selects PUCCH, but this confuses feedback transmitted on the uplink for downlink data with feedback concerning uplink data . A technically correct version should ask: Which physical channel carries DCI used to control HARQ retransmissions for 5G NR uplink data? The answer would then be C.

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 .