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.
Submit