Home ›Chapter 3 ›NSA counter families

NSA counter families

The NSA counters all live under the N.NsaDc.* family (LTE-NR dual connectivity). Learn to read the name and you can find and analyse any of them.

N.NsaDc.*

NSA DC family

Add · Rel

access · retain

PSCell

mobility

X2Split

throughput

① The NSA counter registry — live (counted from the dataset right now)

N.NsaDc.SgNB.Add.* — additions (access)

N.NsaDc.SgNB.Rel.* — releases (retainability)

N.NsaDc.PScell.* — PSCell (mobility)

159

N.NsaDc.* — everything NSA

② Decode a counter name

N.NsaDc.SgNB.Add.Fail.Radio.NoRes

N = counter · NsaDc = LTE-NR NSA dual connectivity · SgNB.Add = the SCG (secondary gNB) addition procedure · Fail.Radio = a radio-cause failure · NoRes = specifically "no radio resource". Read left→right: family → procedure → outcome → cause.

③ The NSA counter families

Family (prefix)	Domain	Measures	Example
N.NsaDc.SgNB.Add.*	Accessibility	SCG (SgNB) addition attempts / acks / success / failures	N.NsaDc.SgNB.Add.Succ
N.NsaDc.SgNB.AbnormRel.* · SgNB.Rel.*	Retainability	abnormal + normal SCG releases (drops)	N.NsaDc.SgNB.AbnormRel.Total
N.NsaDc..PSCell.Change.	Mobility	PSCell change (intra/inter-SgNB, coverage, freq, MLB…)	N.NsaDc.InterSgNB.PSCell.Change.Succ
N.NsaDc.SgNB.Mod.*	Reconfiguration	SgNB modification (SCG reconfig)	N.NsaDc.SgNB.Mod.Req.Succ
N.NsaDc.HO.NCell.*	Mobility	NSA handover neighbour-cell prep / exec	N.NsaDc.HO.NCell.ExecSuccOut
N.SNTrmt.MCGBearer..X2Split · N.NsaDc..PDCP.*.X2Split	Throughput	split-bearer PDCP volume over X2	N.SNTrmt.MCGBearer.DL.PDCP.Tx.X2Split.PDU.Volume
N.NsaDc.DRB.*	Bearer	DRB add / abnormal release at DC level	N.NsaDc.DRB.AbnormRel.Total

How to analyse any family

Every family has an attempt (denominator), a success (numerator) and failure/cause children. Ratio = success ÷ attempt; the failure children tell you why. That is the whole method — the next topics wire it up so you can click a counter and see it.

Home ›Chapter 3 ›NSA Access failure counters

NSA Access failure counters

NSA accessibility = can a UE add the NR leg (the SgNB / SCG)? Every real Huawei counter in the SgNB-addition funnel is here — click any counter to see what it means, why it degrades, how to confirm it and how to fix it.

Add.Att

denominator

Add.Succ

numerator

Fail.Radio

radio causes

Disc.FlowCtrl

gNB overload

① The SgNB-addition funnel 🎬 (watch the attempts thin out · click a stage or a ▼ loss)

Addition attempts

N.NsaDc.SgNB.Add.Att

100%

▼ admission / X2 lossesN.NsaDc.SgNB.Add.Fail.Radio.* + Fail.TNL

SgNB admitted — ACK

N.NsaDc.SgNB.Add.Ack

≈96%

▼ first RACH on NR failedN.NsaDc.SgNB.Rel.InitialAdd.RachFail

NR leg UP

N.NsaDc.SgNB.Add.Succ

≈92% · SgNB Add SR

👆 Click a stage for its counter role, or a ▼ loss for the full failure analysis — cause → solution → parameter.

Stage 3 — the UE arrived on NRN.NsaDc.SgNB.Add.Succ

What this stage counts. The UE won the NR RACH and the SGNB RECONFIGURATION COMPLETE closed the loop. Succ ÷ Att = SgNB Addition Success Rate — the ENDC access KPI.

② The X2 addition trace 📡 (every message → the counter that pegs · click a message)

EN-DC SgNB Addition — where every NSA access counter pegs

👆 Click any message for the detail, counters & failure mode

③ SgNB Add success rate — the formula

① SgNB Add success rate — the formula

SgNB Add SR = N.NsaDc.SgNB.Add.Succ ÷ N.NsaDc.SgNB.Add.Att

Att = the MeNB requested the SCG · Ack = the gNB accepted · Succ = the UE completed the SCG. Att→Ack gaps = gNB rejection; Ack→Succ gaps = the UE failed PSCell RACH.

④ The access counter map 🎬 (click any counter to analyse it)

N.NsaDc.SgNB.Add.* — the SgNB-addition access funnel (click a counter for its full analysis)

successattemptfailurecause

👆 Click any counter node → a solution card pops up with its optimization wire, recommended value & MML. (Esc or click outside to close.)

③ Complete access counter inventory (verbatim Huawei descriptions)

Counter	What it measures (verbatim)
N.NsaDc.SgNB.Add.Att	Number of SgNB addition requests in the LTE-NR NSA DC scenario
N.NsaDc.SgNB.Add.Ack	Number of SgNB addition request acknowledgments in LTE-NR NSA DC scenario
N.NsaDc.SgNB.Add.Succ	Number of successful SgNB additions in the LTE-NR NSA DC scenario
N.NsaDc.SgNB.Add.Fail.Radio	Number of SgNB addition failures caused by radio faults in LTE-NR NSA DC scenarios
N.NsaDc.SgNB.Add.Fail.Radio.NoRes	Number of SgNB addition failures caused by the unavailability of radio resources
N.NsaDc.SgNB.Add.Fail.Radio.License	Number of SgNB addition failures caused by user number or RE license insufficiency
N.NsaDc.SgNB.Add.Fail.Radio.UeCapability	Number of SgNB addition failures caused by UE capability issues
N.NsaDc.SgNB.Add.Fail.TNL	Number of SgNB addition failures caused by transmission faults
N.NsaDc.SgNB.Add.Disc.FlowCtrl	Number of times SCG addition messages are discarded due to flow control
N.NsaDc.SgNB.Add.Disc.ExceedThld	Number of times SCG addition messages are discarded due to requests exceeding the threshold
N.NsaDc.SgNB.Rel.InitialAdd.RachFail	Number of SCG releases due to random access failures during initial SCG addition

⑥ Analysis workflow

Is Att healthy?

N.NsaDc.SgNB.Add.Att vs LTE users — if low, EN-DC is not triggering (B1 / NSA switch / NR coverage).

Att → Ack gap?

if Ack ≪ Att, the gNB is rejecting → read Fail.Radio.NoRes / License / UeCapability + Disc.FlowCtrl.

Ack → Succ gap?

if Succ ≪ Ack, the UE failed to complete the SCG → N.NsaDc.SgNB.Rel.InitialAdd.RachFail (PSCell RACH / UL coverage).

Transport?

a steady N.NsaDc.SgNB.Add.Fail.TNL means the X2 between the MeNB and gNB is faulty — fix transport, not radio.

Fix the dominant cause

address the biggest failure counter, then re-check SgNB Add SR.