23.02.

2025 09:39 Counters Diagrams

DESCRIPTION 9/1553-LZA 701 6017-1 Uen BJ

Counters Diagrams
NR
Contents
1 Introduction
1.1 Performance Management Areas

2 Accessibility
2.1 Common Accessibility Counters
2.1.1 UE Context Establishment
2.1.2 Contention Based Random Access
2.1.3 Contention Free Random Access
2.2 NR NSA EN-DC Connection Setup
2.3 Accessibility Counters for NR SA
2.3.1 RRC Connection Establishment for NR SA
2.3.2 Signaling Connection Establishment for NR SA
2.3.3 RRC Connection Resume
2.3.4 RRC Connection Resume Fallback to RRC Connection Establishment
2.3.5 RRC Connection Reestablishment Fallback to RRC Connection Establishment
2.3.6 DRB Establishment for NR SA
2.3.7 DRB Resume

3 Retainability
3.1 Retainability Counters for NR NSA
3.1.1 EN-DC connection release initiated by eNodeB
3.1.2 EN-DC connection release initiated by gNodeB
3.2 Retainability Counters for NR SA
3.2.1 DRB Release
3.2.2 RRC Connection Reestablishment

4 Mobility
4.1 NR NSA Intra-gNodeB PSCell Change
4.2 NR NSA Inter-gNodeB PSCell Change
4.3 NR SA Intra-gNodeB Mobility
4.4 NR SA Inter-gNodeB Mobility
4.5 NR-to-LTE Inter-RAT Handover

5 Integrity
5.1 DL MAC Latency
5.2 DL Throughput, Volume and Time EBS-N Counters Details
5.3 UL Throughput, Volume and Time EBS-N Counters Details
5.4 DL MAC DRB Volume, Time and Contention Delay
5.5 UL MAC UE Volume and Time
5.6 DL PDCP Packet Integrity
5.7 UL PDCP Packet Integrity

6 Utilization
6.1 MCS Usage for PDSCH Transmissions

about:blank 1/40
23.02.2025 09:39 Counters Diagrams

1 Introduction
This description contains flowcharts, sequence diagrams and mixed flow-sequence diagrams for the main traffic sequences
that impact performance statistics counters in the gNodeB. It should be noted that the counters presented are merely a
subset of all gNodeB counters Managed Object Model "MOM".

1.1 Performance Management Areas

This document diagrams are grouped into the following performance management areas:

– Accessibility
– Retainability
– Integrity
– Mobility

The definitions of the performance management areas can be found in Key Performance Indicators.

Main traffic scenarios along with their diagrams for each performance management area are described in following
sections.

Where a flowchart shows a parent counter and a set of sub-counters, it is possible that less common sub-events are not
explicitly shown by sub-counters. Unless stated otherwise, do not assume that the sum of the sub-counters equals the
parent counter

Note: The attempt counter shown in flowchart is pegged after the procedure is completed to keep consistency in
attempt and success.

about:blank 2/40
23.02.2025 09:39 Counters Diagrams

2 Accessibility
Accessibility main traffic scenario specified:

– UE Context Establishment
– Contention Based Random Access
– Contention Free Random Access
– NR NSA EN-DC Connection Setup
– RRC Connection Establishment for NR SA
– Signaling Connection Establishment for NR SA
– RRC Connection Resume
– RRC Connection Resume Fallback to RRC Connection Establishment
– RRC Connection Reestablishment Fallback to RRC Connection Establishment
– DRB Establishment for NR SA
– DRB Resume

2.1 Common Accessibility Counters

2.1.1 UE Context Establishment

UE Context Establishment scenario.

The main gNodeB, DU counters for this scenario are the following:

– pmUeCtxtSetupAtt
– pmUeCtxtSetupSucc

DU gNodeB CU-CP

F1AP:
UE CONTEXT SETUP REQUEST

pmUeCtxtSetupAtt +

F1AP:
UE CONTEXT SETUP RESPONSE

F1AP:
UE CONTEXT MODIFICATION REQUEST
(RCI = true)

pmUeCtxtSetupSucc +

L0002929B

Figure 1 UE Context Establishment scenario

about:blank 3/40
23.02.2025 09:39 Counters Diagrams
Note: These pm counters are stepped in mobility scenarios as well.

2.1.2 Contention Based Random Access

Random Access (RA) scenarios.

The main gNodeB, DU counters for this scenario are the following:

– pmRadioRaCbPreambles
– pmRadioRaCbFailMsg1MaxMsg3Sched
– pmRadioRaCbFailMsg1Ooc
– pmRadioRaCbAttMsg2
– pmRadioRaCbFailMsg2Disc
– pmRadioRaCbFailMsg3Crc
– pmRadioRaCbFailMsg3Crnti
– pmRadioRaCbFailMsg3Dtx
– pmRadioRaCbSuccMsg3

Msg1 Preamble
for CBRA Received

pmRadioRaCbPreambles +

Are the Preambles

discarded because of a greater timing offset Yes
pmRadioRaCbFailMsg1Ooc +
than the configured distance (Out
of Coverage)?

No

Are the Preambles discarded Yes

because of reaching maximum pmRadioRaCbFailMsg1MaxMsg3Sched +
scheduled RA Msg3?

No

Attempt to schedule Msg2

pmRadioRaCbAttMsg2 +

Are the Preambles discarded

Yes
because the random access response pmRadioRaCbFailMsg2Disc +
window expired, and Msg2
was not sent?

No

A B

L0002604D

Figure 2 Contention Based Random Access Scenario, part 1

about:blank 4/40
23.02.2025 09:39 Counters Diagrams

A B

gNodeB, RRC: Msg2 Random Access Response sent toward UE

DCI 0_0 sent to the UE

gNodeB, RRC: Msg3, RRC Setup Request Expected

Yes
Is DTX detected for Msg3?

Yes No
Failure in CRC decoding?

pmRadioRaCbFailMsg3Crc* +

No

pmRadioRaCbFailMsg3Crnti** +

Yes
Is Msg3 received with
wrong CRNTI? pmRadioRaCbFailMsg3Dtx* +

No

Is the maximum number of

retransmissions reached? No
pmRadioRaCbSuccMsg3 +

Yes

End of Flow
* Either pmRadioRaCbFailMsg3Dtx or pmRadioRaCbFailMsg3Crc
are stepped for every expected msg3 transmission (or re-transmission),
which was not decoded successfully.
**in LB/MB implementation the pmRadioRaCbFailMsg3Crnti counter is stepped
after stepping pmRadioRaCbSuccMsg3.
L0002605E

Figure 3 Contention Based Random Access Scenario, part 2

2.1.3 Contention Free Random Access

Random Access (RA) scenario.

The main gNodeB, DU counters for this scenario are the following:

– pmRadioRaCfPreambles
– pmRadioRaCfAttMsg2
– pmRadioRaCfSucc

about:blank 5/40
23.02.2025 09:39 Counters Diagrams

The detected CFRA preamble is allocated to a UE

pmRadioRaCfPreambles +

Is Msg2 scheduled No
successfully?

Yes

pmRadioRaCfAttMsg2 +

Msg2 is sent towards UE

Is non-DTX reported No
for PUSCH?

Yes

pmRadioRaCfSucc +

End of Flow

L0003746A

Figure 4 Contention Free Random Access Scenario

2.2 NR NSA EN-DC Connection Setup

EN-DC connection setup scenario. The sequence diagrams covers only EN-DC setup excluding mobility and PSCell change
scenarios.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmEndcSetupUeAtt
– pmEndcSetupUeSucc
– pmEndcSetupScgUeAtt
– pmEndcSetupScgUeSucc
– pmEndcNrDrbSetupAtt
– pmEndcNrDrbSetupSucc
– pmUeCtxtSetupAtt
– pmUeCtxtSetupSucc

Note: pmEndcNrDrbSetupAtt is stepped before the procedure is completed and it might cause that
pmEndcNrDrbSetupAtt and pmEndcNrDrbSetupSucc are not pegged within the same measurement period.

about:blank 6/40
23.02.2025 09:39 Counters Diagrams

gNodeB

eNodeB DU CU-CP CU-UP UE

X2AP:
SGNB Addition Request
with Trigger Indication = “endc_setup”

pmEndcSetupUeAtt +

pmEndcSetupScgUeAtt +

E1AP:
Bearer Context Setup Request

pmEndcNrDrbSetupAtt +
E1AP:
F1AP: Bearer Context Setup Response
UE Context Setup Request

pmUeCtxtSetupAtt +

F1AP:
UE Context Setup Response

X2AP:
SGNB Addition Request Acknowledge

X2AP:
SN Status Transfer
RRC:
RRCConnectionReconfiguration

RRC:
RRCConnectionReconfigurationComplete

X2AP:
SGNB Reconfiguration Complete

Par E1AP:
Bearer Context Modification Request
E1AP:
Bearer Context Modification Response

F1AP:
UE Context Modification Request

pmUeCtxtSetupSucc +

F1AP:
UE Context Modification Response

pmEndcSetupUeSucc + pmEndcNrDrbSetupSucc +

pmEndcSetupScgUeSucc + RRC:
NR Random Access

L0002396G

Figure 5 EN-DC connection setup

about:blank 7/40
23.02.2025 09:39 Counters Diagrams

gNodeB

eNodeB DU CU-CP CU-UP UE

X2AP:
SGNB Modification Request
with Modification Type = “SCG Addition”

pmEndcSetupScgUeAtt +

E1AP:
Bearer Context Modification Request

E1AP:
F1AP: Bearer Context Modification Response
UE Context Setup Request

pmUeCtxtSetupAtt +

F1AP:
UE Context Setup Response

X2AP:
SGNB Modification Request
Acknowledge

X2AP:
SN Status Transfer

RRC:
RRCConnectionReconfiguration

RRC:
RRCConnectionReconfigurationComplete

X2AP:
SGNB Reconfiguration Complete

E1AP:
Bearer Context Modification Request

E1AP:
Bearer Context Modification Response
F1AP:
UE Context Modification Request

pmUeCtxtSetupSucc +

F1AP:
UE Context Modification Response

pmEndcSetupScgUeSucc +

RRC:
NR Random Access

L0002601G

Figure 6 SGNB Modification for SCG Addition

2.3 Accessibility Counters for NR SA

2.3.1 RRC Connection Establishment for NR SA

Scenario containing successful attempts to set up a RRC connection for an originating or terminating connection.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmRrcConnEstabAtt
– pmRrcConnEstabAttEm
– pmRrcConnEstabAttMos
– pmRrcConnEstabAttReatt
– pmRrcConnEstabAttReattEm
– pmRrcConnEstabAttReattMos
– pmRrcConnEstabSucc
– pmRrcConnEstabSuccEm
– pmRrcConnEstabSuccMos

about:blank 8/40
23.02.2025 09:39 Counters Diagrams

RRC Setup Request Received

pmRrcConnEstabAtt +

pmRrcConnEstabAttEm +
pmRrcConnEstabAttEm + step for establishmentCause emergency
pmRrcConnEstabAttMos + pmRrcConnEstabAttMos +
step for establishmentCause mo-Signalling

Is RRC Connection Yes

ongoing for the same UE identity? pmRrcConnEstabAttReatt +

No pmRrcConnEstabAttReattEm +
pmRrcConnEstabAttReattMos +

pmRrcConnEstabAttReattEm +
step for establishmentCause emergency
pmRrcConnEstabAttReattMos +
step for establishmentCause mo-Signalling

Create UE Context in RC

Yes
RRC setup request rejected?

No
pmRrcConnEstabSuccEm +
pmRrcConnEstabSucc + step for establishmentCause emergency
pmRrcConnEstabSuccMos +
step for establishmentCause mo-Signalling

pmRrcConnEstabSuccEm +
pmRrcConnEstabSuccMos +

End of the Flow

L0002603C

Figure 7 RRC connection establishment

2.3.2 Signaling Connection Establishment for NR SA

Scenario containing successful attempts to set up a Signaling Connection.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmNgSigConnEstabAtt
– pmNgSigConnEstabAttEm
– pmNgSigConnEstabAttMos
– pmNgSigConnEstabSucc
– pmNgSigConnEstabSuccEm
– pmNgSigConnEstabSuccMos

about:blank 9/40
23.02.2025 09:39 Counters Diagrams

RRC Connected

Initiation of AMF selection

pmNgSigConnEstabAttEm +
pmNgSigConnEstabAtt +
step for establishmentCause emergency
pmNgSigConnEstabAttMos +
step for establishmentCause mo-Signalling

pmNgSigConnEstabAttEm +
pmNgSigConnEstabAttMos +

NAS authentication & security

Is first message received on this UE No

associated logical NG signaling connection?

Yes

pmNgSigConnEstabSuccEm +
pmNgSigConnEstabSucc + step for establishmentCause emergency
pmNgSigConnEstabSuccMos +
step for establishmentCause mo-Signalling

pmNgSigConnEstabSuccEm +
pmNgSigConnEstabSuccMos +

End of the Flow

L0002930B

Figure 8 Signaling Connection Establishment

2.3.3 RRC Connection Resume

Scenario containing successful attempt to resume RRC Connection.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmRrcResumeAtt
– pmRrcResumeAttResume
– pmRrcResumeAttResumeEm
– pmRrcResumeAttRnaUpdate
– pmRrcResumeSuccResume
– pmRrcResumeSuccResumeEm

about:blank 10/40
23.02.2025 09:39 Counters Diagrams
gNodeB

CU-CP UE

RRC:
RRCResumeRequest

pmRrcResumeAtt +

RRCResumeRequest message
with resumeCause rna-Update
pmRrcResumeAttRnaUpdate +

RRC:
RRCResume

pmRrcResumeAttResume +

RRCResumeRequest message
with resumeCause emergency
pmRrcResumeAttResumeEm +

RRC:
RRCresumeComplete

pmRrcResumeSuccResume +

RRCResumeRequest message
with resumeCause emergency
pmRrcResumeSuccResumeEm +

L0003546A

Figure 9 RRC Connection Resume

2.3.4 RRC Connection Resume Fallback to RRC Connection Establishment

Scenario containing successful attempt to resume RRC connection with fallback to RRC connection establishment.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmRrcResumeAtt
– pmRrcResumeAttFallback
– pmRrcResumeAttFallbackEm
– pmRrcResumeAttFallbackRnaUpdate
– pmRrcResumeAttRnaUpdate
– pmRrcResumeSuccFallback
– pmRrcResumeSuccFallbackEm
– pmRrcResumeSuccFallbackRnaUpdate

about:blank 11/40
23.02.2025 09:39 Counters Diagrams
gNodeB

CU-CP UE

RRC:
RRCResumeRequest

pmRrcResumeAtt +

RRCResumeRequest message
with resumeCause rna-Update
pmRrcResumeAttRnaUpdate +

RRC:
RRCSetup

pmRrcResumeAttFallback +

RRCResumeRequest message
with resumeCause rna-Update
pmRrcResumeAttFallbackRnaUpdate +

RRCResumeRequest message
with resumeCause emergency
pmRrcResumeAttFallbackEm +

RRC:
RRCSetupComplete

pmRrcResumeSuccFallback +

RRCResumeRequest message
with resumeCause rna-Update
pmRrcResumeSuccFallbackRnaUpdate +

RRCResumeRequest message
with resumeCause emergency
pmRrcResumeSuccFallbackEm +

L0003544A

Figure 10 RRC Connection Resume Fallback to RRC Connection Establishment

2.3.5 RRC Connection Reestablishment Fallback to RRC Connection Establishment

RRC Connection Reestablishment scenario.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmRrcConnReestFallbackAtt
– pmRrcConnReestFallbackSucc
– pmUeCtxtRetrieveAttRrcReest

gNodeB

CU-CP UE

RRC:
RRCReestablishmentRequest

pmRrcConnReestFallbackAtt +

RRC:
RRCSetup

RRC:
RRCSetupComplete

pmRrcConnReestFallbackSucc +

L0003543A

Figure 11 Intra-gNB RRC Connection Reestablishment Fallback to RRC Connection Establishment

about:blank 12/40
23.02.2025 09:39 Counters Diagrams
RRC reestablishment Last serving
target gNodeB gNodeB

UE CU-CP CU-CP AMF

RRC:
RRCReestablishmentRequest

XnAP:
RETRIEVE UE CONTEXT REQUEST

pmUeCtxtRetrieveAttRrcReest +

XnAP:
RETRIEVE UE CONTEXT FAILURE

pmRrcConnReestFallbackAtt +

RRC:
RRCSetup

RRC:
RRCSetupComplete

pmRrcConnReestFallbackSucc +

NGAP:
INITIAL UE MESSAGE

Initial Context Setup

L0003852A

Figure 12 Inter-gNB RRC Connection Reestablishment Fallback to RRC Connection Establishment

2.3.6 DRB Establishment for NR SA

DRB Establishment scenario.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmDrbEstabAtt5qi
– pmDrbEstabAttArp
– pmDrbEstabAttInit5qi
– pmDrbEstabAttInitArp
– pmDrbEstabSucc5qi
– pmDrbEstabSuccArp
– pmDrbEstabSuccInit5qi
– pmDrbEstabSuccInitArp

about:blank 13/40
23.02.2025 09:39 Counters Diagrams
Establishing DRB with:
- Initial Context Setup
- PDU Session Resource Setup
- PDU Session Resource Modify

pmDrbEstabAtt5qi + Stepped for each attempt of DRB

to be established that has
the given ARP Priority Level

pmDrbEstabAttArp +

No
Is the Initial Context Setup procedure used?

Yes

pmDrbEstabAttInit5qi + Stepped for each attempt of DRB

to be established that has
the given ARP Priority Level

pmDrbEstabAttInitArp +

No
Is DRB successfully established?

Yes

pmDrbEstabSucc5qi +
Stepped for each successfully
established DRB that has
the given ARP Priority Level
pmDrbEstabSuccArp +

No
Is the Initial Context Setup procedure used?

Yes

pmDrbEstabSuccInit5qi +
Stepped for each successfully
established DRB that has
the given ARP Priority Level
pmDrbEstabSuccInitArp +

End of the Flow

L0003057B

Figure 13 DRB Establishment for NR SA

2.3.7 DRB Resume

DRB Resume scenario.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmDrbResumeAtt5qi
– pmDrbResumeAttArp
– pmDrbResumeSucc5qi
– pmDrbResumeSuccArp

about:blank 14/40
23.02.2025 09:39 Counters Diagrams

DRB Resume Attempt

pmDrbResumeAtt5qi +
Stepped for each attempt of DRB
resume that has
the given ARP Priority Level

pmDrbResumeAttArp +

No
Is DRB successfully resumed?

Yes

pmDrbResumeSucc5qi +
Stepped for each successfully
resumed DRB that has
the given ARP Priority Level

pmDrbResumeSuccArp +

End of the Flow

L0003545A

Figure 14 DRB Resume for NR SA

about:blank 15/40
23.02.2025 09:39 Counters Diagrams

3 Retainability
3.1 Retainability Counters for NR NSA
EN-DC connection release of type normal and abnormal scenarios. A normal release is a release with cause “Cell not
Available”, “User Inactivity”, “MCG Mobility” or “SCG Mobility”. An abnormal release is a release with cause "Radio
Connection With UE Lost", "E1 link down", "F1 link down", "X2 link down" or "Unspecified".

– EN-DC connection release initiated by eNodeB

– EN-DC connection release initiated by gNodeB

3.1.1 EN-DC connection release initiated by eNodeB

Mixed flow-sequence diagram to EN-DC connection release initiated by eNodeB.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmEndcRelUeNormal
– pmEndcRelUeAbnormalMenb
– pmEndcRelUeAbnormalMenbAct

about:blank 16/40
23.02.2025 09:39 Counters Diagrams

eNodeB CU-CP gNodeB UE

Trigger NR connection
release

Prepare for DRB

reconfiguration

X2AP: SGNB Release Request

(without UE Context Kept Indicator IE)
Normal With which Abnormal
cause code indicating
release?

pmEndcRelUeNormal + pmEndcRelUeAbnormalMenb +

No UE is considered in session
at the time of release?

Yes

pmEndcRelUeAbnormalMenbAct +

Suspend DRB
X2AP:
SGNB Release Request Acknowledged

RRC: RRCConnectionReconfiguration
(Release SCG and start B1)

X2AP: SN Status transfer

RRC: LTE Random Access

RRC:
RRCConnectionReconfiguration
Complete

Resume DRB
L0002606C

Figure 15 EN-DC connection release initiated by eNodeB

3.1.2 EN-DC connection release initiated by gNodeB

EN-DC connection release initiated by gNodeB scenario.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmEndcRelUeAbnormalSgnb
– pmEndcRelUeAbnormalSgnbAct
– pmEndcRelUeNormal

about:blank 17/40
23.02.2025 09:39 Counters Diagrams

gNodeB

eNodeB CU-CP UE

Trigger NR Connection Release

X2AP:
SGNB Release Required

Normal With which Abnormal

cause code indicating
release?

pmEndcRelUeAbnormalSgnb +
pmEndcRelUeNormal +

Prepare for DRB Reconfiguration No UE is considered in

session at the time
of release?
Yes

pmEndcRelUeAbnormalSgnbAct +

X2AP:
SN Release Confirm

Suspend DRB

RRC:
RRCConnectionReconfiguration
(release SCG and start B1)

X2AP:
SN Status Transfer

RRC:
LTE Random Access

RRC:
RRCConnectionReconfigurationComplete

Resume DRB

L0002608C

Figure 16 EN-DC connection release initiated by gNodeB by UE or A3

3.2 Retainability Counters for NR SA

Connection release of type normal and abnormal scenarios. There are many release causes considered normal and
abnormal in NR SA scenario. The examples are as follows:

– Normal Release

• Successful inter gNB NR handover

• o Successful NG inter-system handover
• User inactivity
• Most cases of Release with Redirection
• Authentication failure, Deregister

– Abnormal Release

• Cell not available

• Interaction with other procedure
• Handover cancelled, Handover target not allowed, Handover failure in target 5GC/ NG-RAN node or target
system
• Hardware failure, Not enough user plane processing resources
• Abstract syntax error, Message not compatible with receiver state
about:blank 18/40
23.02.2025 09:39 Counters Diagrams
Connection release of type abnormal can be initiated by either gNodeB or AMF.

– The release is considered gNodeB initiated for the following start triggers:

• gNB-CU sends NGAP message UE CONTEXT RELEASE REQUEST to AMF

• gNB-CU sends NGAP message RESET to AMF
• In case of no NG-C connection, when the UE context is released
• In case of no Xn-C connection, when the UE context is released

– The release is considered AMF initiated for the following start triggers:

• NGAP message UE CONTEXT RELEASE COMMAND is received from AMF

• NGAP message NG RESET is received from the AMF
• Successful outgoing NG handover
• NGAP message ERROR INDICATION is received from AMF

3.2.1 DRB Release

DRB Release scenario.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmDrbRelNormal5qi
– pmDrbRelNormalArp
– pmDrbRelNormalInact5qi
– pmDrbRelAbnormalAmf5qi
– pmDrbRelAbnormalAmfInact5qi
– pmDrbRelAbnormalAmfAct5qi
– pmDrbRelAbnormalAmfActArp
– pmDrbRelAbnormalAmfArp
– pmDrbRelAbnormalGnb5qi
– pmDrbRelAbnormalGnb25qi
– pmDrbRelAbnormalGnbInact5qi
– pmDrbRelAbnormalGnbAct5qi
– pmDrbRelAbnormalGnbAct25qi
– pmDrbRelAbnormalGnbActArp
– pmDrbRelAbnormalGnbArp
– pmDrbSuspend5qi

about:blank 19/40
23.02.2025 09:39 Counters Diagrams

Releasing DRB with:

- UE Context Release
- PDU Session Resource Modify
Suspending DRB with RRC Release to RRC_INACTIVE

UE is released to Yes
RRC_INACTIVE state? Suspending DRB

No

Releasing DRB

Normal With which

cause code indicating
release?

pmDrbRelNormal5qi + Abnormal

AMF What node triggered gNodeB

the release?
pmDrbRelNormalArp +
pmDrbSuspend5qi +

pmDrbRelAbnormalGnb5qi +
pmDrbRelAbnormalAmf5qi + pmDrbRelAbnormalGnb25qi + Deprecated

pmDrbRelAbnormalAmfArp + pmDrbRelAbnormalGnbArp +

Stepped for abnormal DRB Stepped for abnormal DRB

release triggered by AMF release triggered by gNodeB
for each ARP Priority level for each ARP Priority level
Yes UE is in UE is in Yes
RRC_INACTIVE state? RRC_INACTIVE state?

No No
pmDrbRelAbnormalAmfInact5qi +
pmDrbRelAbnormalGnbInact5qi +

No
UE is considered in UE is considered in No
No UE is in session at the time session at the time
RRC_INACTIVE state? of release? of release?
Yes Yes
Yes
pmDrbRelAbnormalGnbAct5qi +
pmDrbRelAbnormalAmfAct5qi + pmDrbRelAbnormalGnbAct25qi + Deprecated
pmDrbRelNormalInact5qi +

pmDrbRelAbnormalAmfActArp+ pmDrbRelAbnormalGnbActArp +

End of Flow

L0003058C

Figure 17 DRB Release

3.2.2 RRC Connection Reestablishment

RRC Connection Reestablishment scenario

The main gNodeB, CU-CP counters for this scenario are the following:

– pmRrcConnReestAtt
– pmRrcConnReestSucc
– pmUeCtxtRetrieveAttRrcReest
– pmUeCtxtRetrieveSuccRrcReest

about:blank 20/40
23.02.2025 09:39 Counters Diagrams
gNodeB

CU-CP UE

RRC:
RRCReestablishmentRequest

pmRrcConnReestAtt +

RRC:
RRCReestablishment

RRC:
RRCReestablishmentComplete

pmRrcConnReestSucc +

L0003858A

Figure 18 Intra-gNB RRC Connection Reestablishment (without fallback)

RRC reestablishment Last serving
target gNodeB gNodeB

UE CU-CP CU-CP AMF

RRC:
RRCReestablishmentRequest

XnAP:
RETRIEVE UE CONTEXT REQUEST

pmUeCtxtRetrieveAttRrcReest +

XnAP:
RETRIEVE UE CONTEXT RESPONSE

pmRrcConnReestAtt +

XnAP:
XN-U ADDRESS INDICATION

XnAP:
SN STATUS TRANSFER
RRC:
RRCReestablishment

RRC:
RRCReestablishmentComplete

pmRrcConnReestSucc +

RRC:
RRCReconfiguration

RRC:
RRCReconfigurationComplete

NGAP:
PATH SWITCH REQUEST
NGAP:
PATH SWITCH REQUEST ACKNOWLEDGE

XnAP:
UE CONTEXT RELEASE

pmUeCtxtRetrieveSuccRrcReest +

L0003550B

Figure 19 Inter-gNB RRC Connection Reestablishment (without fallback)

about:blank 21/40
23.02.2025 09:39 Counters Diagrams

4 Mobility
Mobility traffic scenarios.

– NR NSA Intra-gNodeB PSCell Change

– NR NSA Inter-gNodeB PSCell Change
– NR SA Intra-gNodeB Mobility
– NR SA Inter-gNodeB Mobility
– NR-to-LTE Inter-RAT Handover

4.1 NR NSA Intra-gNodeB PSCell Change

NR NSA Intra-gNodeB PSCell Change scenario.

The main gNodeB, CU-CP, counters for this scenario are the following:

– pmEndcPSCellChangeAttIntraSgnb
– pmEndcPSCellChangeSuccIntraSgnb

Source
GNodeB CU-CP MeNodeB UE

RRC:
ul-DCCH-Message

X2AP:
RRC Transfer (Measurement Report)

Evaluate Measurement Report

X2AP:
SgNB Modification Required
with Modification Type = “SCG mobility”

pmEndcPSCellChangeAttIntraSgnb +

RRC:
RRCConnectionReconfiguration

RRC:
RRCConnectionReconfigurationComplete

X2AP:
SgNB Modification Confirm

pmEndcPSCellChangeSuccIntraSgnb +

RRC:
NR Random Access

L0002625B

Figure 20 NR NSA Intra-gNodeB PSCell Change

4.2 NR NSA Inter-gNodeB PSCell Change

NR NSA Inter-gNodeB PSCell Change scenario.

about:blank 22/40
23.02.2025 09:39 Counters Diagrams
The main gNodeB, CU-CP counters for this scenario are the following:

– pmEndcPSCellChangeAttInterSgnb
– pmEndcPSCellChangeSuccInterSgnb
– pmEndcPSCellChangeResAllocReqInterSgnb
– pmEndcPSCellChangeResAllocSuccInterSgnb

Target Source
gNodeB CU-CP gNodeB CU-CP MeNodeB UE

RRC:
UL-DCCH Message

X2AP:
RRC Transfer
(Measurement Report)

Evaluate Measurement Report

X2AP:
SgNB Change Required

pmEndcPSCellChangeAttInterSgnb +

X2AP:
SgNB Addition Request
with Trigger = “SN Change”

pmEndcPSCellChangeResAllocReqInterSgnb +

X2AP:
SgNB Addition Request Acknowledged
with A3 measurement config

pmEndcPSCellChangeResAllocSuccInterSgnb + RRC:
RRC Connection
Reconfiguration

RRC:
RRC Connection
Reconfiguration
Complete
X2AP:
SgNB Change Confirm

pmEndcPSCellChangeSuccInterSgnb +

X2AP:
SgNB Reconfiguration Complete

L0002610B

Figure 21 NR NSA Inter-gNodeB PSCell Change

4.3 NR SA Intra-gNodeB Mobility

NR SA Intra-gNodeB Mobility scenario.

The main gNodeB, CU-CP, counters for this scenario are the following:

– pmHoPrepAttOutIntraGnb
– pmHoPrepSuccOutIntraGnb
– pmHoExeAttOutIntraGnb
– pmHoExeSuccOutIntraGnb

about:blank 23/40
23.02.2025 09:39 Counters Diagrams

Target Source
GNodeB
GNodeB GNodeB UE
CU-CP
cell cell

RRC:
Measurement report

Evaluate Measurement Report

pmHoPrepAttOutIntraGnb +

Allocated resources ?
No
Yes
End of RRC:
flow RRC Connection Reconfiguration

pmHoPrepSuccOutIntraGnb +

pmHoExeAttOutIntraGnb +

RRC:
NR Random Access
RRC:
RRC Connection Reconfiguration
Complete

pmHoExeSuccOutIntraGnb +

L0002624B

Figure 22 NR Intra-gNodeB Mobility

4.4 NR SA Inter-gNodeB Mobility

SA Inter-gNodeB Mobility scenario.

The main gNodeB, CU-CP counters for this scenario are the following:

– pmHoPrepAttOutInterGnb
– pmHoPrepSuccOutInterGnb
– pmHoExeAttOutInterGnb
– pmHoExeSuccOutInterGnb
– pmHoExeSuccOutDrbInterGnb5qi

about:blank 24/40
23.02.2025 09:39 Counters Diagrams

Target gNodeB Source gNodeB

AMF CU-CP CU-CP UE

RRC:
RRCConnectionReconfiguration

Evaluate Measurement Report

NGAP:
Handover Required

pmHoPrepAttOutInterGnb +

NGAP:
Handover Request

NGAP:
Handover Request Acknowledge

NGAP:
Handover Command

pmHoPrepSuccOutInterGnb +

RRC:
RRCConnectionReconfiguration

pmHoExeAttOutInterGnb +
NGAP:
Uplink RAN Status Transfer

NGAP:
Downlink RAN Status Transfer

RRC:
RRCConnectionReconfigurationComplete

NGAP:
Handover Notification

NGAP:
UE Context Release Command

pmHoExeSuccOutInterGnb +

Stepped for each DRB

pmHoExeSuccOutDrbInterGnb5qi + with the given 5QI
NGAP:
UE Context Release Complete

L0002609B

Figure 23 NR SA Inter-gNodeB Mobility (NG-based)

about:blank 25/40
23.02.2025 09:39 Counters Diagrams

Target gNodeB Source gNodeB

AMF CU-CP CU-CP UE

RRC:
RRCConnectionReconfiguration

Evaluate Measurement Report

XnAP:
Handover Request

pmHoPrepAttOutInterGnb +

XnAP:
Handover Request Acknowledge

pmHoPrepSuccOutInterGnb +

RRC:
RRCConnectionReconfiguration

pmHoExeAttOutInterGnb +

RRC:
RRCConnectionReconfigurationComplete

NGAP:
Path Switch Request

NGAP:
Path Switch Request Acknowlege

XnAP:
UE Context Release

pmHoExeSuccOutInterGnb +

Stepped for each DRB

pmHoExeSuccOutDrbInterGnb5qi + with the given 5QI

L0003936B

Figure 24 NR SA Inter-gNodeB Mobility (Xn--based)

4.5 NR-to-LTE Inter-RAT Handover

NR-to-LTE Inter-RAT Handover scenario

The main gNodeB, CU-CP counters for this scenario are the following:

– pmHoPrepAttOutEutran
– pmHoPrepSuccOutEutran
– pmHoExeAttOutEutran
– pmHoExeSuccOutEutran
– pmHoExeSuccOutDrbEutran5qi

about:blank 26/40
23.02.2025 09:39 Counters Diagrams

Target Source
MME AMF CU-CP UE
eNodeB gNodeB

RRC:
Measurement Report

Evaluate Measurement Report

NGAP:
Handover Required

pmHoPrepAttOutEutran +
N26:
Relocation Request

S1AP:
Handover Request

S1AP:
Handover Request Acknowledge

N26:
Relocation Response
NGAP:
Handover Command

pmHoPrepSuccOutEutran +

RRC:
MobilityFromNRCommand

pmHoExeAttOutEutran +

RRC:
RRCConnectionReconfiguration

RRC:
RRCConnectionReconfigurationComplete

S1AP:
Handover Notify

N26:
Relocation Complete Notification

NGAP:
UE Context Release Command

pmHoExeSuccOutEutran +

Stepped for each

pmHoExeSuccOutDrbEutran5qi + DRB with the
NGAP: given 5QI
UE Context Release Complete

L0002920B

Figure 25 NR-to-LTE Inter-RAT Handover

about:blank 27/40
23.02.2025 09:39 Counters Diagrams

5 Integrity
The counters are included to cover the basic integrity KPIs, for use in NR NSA and NR SA. Integrity main traffic scenarios.

– DL MAC Latency
– DL Throughput, Volume and Time PM Counters Details
– UL Throughput, Volume and Time PM Counters Details
– DL MAC DRB Volume, Time and Contention Delay
– UL MAC UE Volume and Time
– DL PDCP Packet Integrity
– UL PDCP Packet Integrity

5.1 DL MAC Latency

DL MAC latency measures MAC scheduling latency from the time when packet arrives empty DL buffer to the time when
first packet is transmitted.

The main counters for this scenario are the following:

– pmMacLatTimeDlNoDrxSyncQos
– pmMacLatTimeDlNoDrxSyncSampQos
– pmMacLatTimeDlDrxSyncQos
– pmMacLatTimeDlDrxSyncSampQos

The dependency between counters stepping is as follows: pmMacLatTimeDlNoDrxSyncSampQos is stepped by one each
time pmMacLatTimeDlNoDrxSyncQos is stepped and pmMacLatTimeDlDrxSyncSampQos is stepped by one each time
pmMacLatTimeDlDrxSyncQos is stepped.

pmMacLatTimeDlNoDrxSyncQos

Active, In-sync Active, In-sync

Any Any

New data First packet

transmitted

pmMacLatTimeDlDrxSyncQos

Active, In-sync
Inactive, In-sync Any Any

New data First packet

transmitted

L0002587A

Figure 26 DL MAC Latency

5.2 DL Throughput, Volume and Time EBS-N Counters Details

The main counters for this scenario are the following:

– pmEbsnMacDrbThpDlMbbHighVolDistr
– pmEbsnMacDrbThpDlMbbLowVolDistr
about:blank 28/40
23.02.2025 09:39 Counters Diagrams
– pmEbsnDrbExclThpDlRelativeHighVol
– pmEbsnDrbExclThpDlRelativeLowVol
– pmEbsnDrbExclThpDlShortTimeHighVol
– pmEbsnDrbExclThpDlShortTimeLowVol
– pmEbsnDrbExclThpDlSmallVol
– pmEbsnUeExclThpVoNR

Start

Low counters pegged

Yes
Session contains
pmEbsnUeExclThpVoNR + Excluded
VoNR bearer? small vol High counters pegged

No

0 1 MB 10 MB DL MAC Volume
DL session volume No
pmEbsnDrbExclThpDlSmallVol +
> 1 MB?

Yes

No Yes
DL restricted time pmEbsnDrbExclThpDlShortTimeLowVol + DL session volume pmEbsnDrbExclThpDlShortTimeHighVol +
> 50 ms? > 10 MB?

Yes No
Stop

No Yes
DL restricted volume pmEbsnDrbExclThpDlRelativeLowVol + DL session volume pmEbsnDrbExclThpDlRelativeHighVol +
ratio > 10% ? > 10 MB?

Yes No
Stop

Yes
Calculate throughput pmEbsnMacDrbThpDlMbbLowVolDistr + DL session volume pmEbsnMacDrbThpDlMbbHighVolDistr +
> 10 MB?

Low Counters (> 1 MB) No

Stop High Counters (> 10 MB)

L0003566C

Figure 27 pmEbsnMacDrbThpDlMbbHighVolDistr/ pmEbsnMacDrbThpDlMbbLowVolDistr

5.3 UL Throughput, Volume and Time EBS-N Counters Details

The main counters for this scenario are the following:

– pmEbsnMacUeThpUlMbbHighVol2Distr
– pmEbsnMacUeThpUlMbbLowVol2Distr
– pmEbsnUeExclThpUlRelativeHighVol2
– pmEbsnUeExclThpUlRelativeLowVol2
– pmEbsnUeExclThpUlShortTimeHighVol
– pmEbsnUeExclThpUlShortTimeLowVol
– pmEbsnUeExclThpUlSmallVol

about:blank 29/40
23.02.2025 09:39 Counters Diagrams

Low counters pegged

Start Excluded
small vol High counters pegged

0 100 KB 1 MB UL MAC Volume

UL session volume No
pmEbsnUeExclThpUlSmallVol +
> 100 kB?

Yes

No Yes
UL restricted time pmEbsnUeExclThpUlShortTimeLowVol DL session volume pmEbsnUeExclThpUlShortTimeHighVol +
> 10 ms? > 1 MB?

Yes No
Stop

No Yes
UL restricted volume pmEbsnUeExclThpUlRelativeLowVol2 + DL session volume pmEbsnUeExclThpUlRelativeHighVol2 +
ratio > 10% ? > 1 MB?

Yes No
Stop

Yes
Calculate throughput pmEbsnMacUeThpUlMbbLowVol2Distr + DL session volume pmEbsnMacUeThpUlMbbHighVol2Distr +
> 1 MB?

Low Counters (> 100 kB) No

Stop High Counters (> 1 MB)

L0003567D

Figure 28 pmEbsnMacUeThpUlMbbHighVol2Distr/ pmEbsnMacUeThpUlMbbLowVol2Distr

5.4 DL MAC DRB Volume, Time and Contention Delay

These PM counters are to cover the DL MAC DRB Volume, Time and Contention Delay areas for use in NR NSA and NR SA,
measured on MAC SDU level.

PM counters with same name as shown in figure but additional “Qos” suffix (not shown in figure), are the same
measurement and step in the same manner, but just for each Qos. like pmMacTimeDlDrb and pmMacTimeDlDrbQos.

– pmMacVolDlDrb
– pmMacVolDlDrbQos
– pmMacVolDlDrbLastSlot
– pmMacVolDlDrbLastSlotQos
– pmMacVolDlDrbOverlapLastSlot
– pmMacVolDlDrbOverlapLastSlotQoS
– pmMacVolDlDrbSingleBurst
– pmMacVolDlDrbSingleBurstSamp
– pmMacVolDlDrbSingleSlotShortBurst
– pmMacVolDlDrbSingleSlotShortBurstQoS
– pmMacTimeDlDrb
– pmMacTimeDlDrbQos
– pmMacTimeDlDrbSamp
– pmMacTimeDlDrbSampQos
– pmMacTimeDlDrbLastSlot
– pmMacTimeDlDrbLastSlotQos
– pmMacTimeDlDrbLastSlotSamp
– pmMacTimeDlDrbLastSlotSampQos

about:blank 30/40
23.02.2025 09:39 Counters Diagrams
– pmMacOverlapTimeDlDrbExtSCell
– pmMacOverlapTimeDlDrbExtSCellQoS
– pmMacTimeDlDrbSingleSlotShortBurst
– pmMacTimeDlDrbSingleSlotShortBurstQoS
– pmMacContentionDelayDlDistr

pmMacVolDlDrbLastSlot + Vol
pmMacTimeDlDrbLastSlot +2
pmMacTimeDlDrbLastSlotSamp +1
pmMacContentionDelayDlDistr, bin8* + 1

pmMacVolDlDrb + Vol New packet

arrives to
empty buffer

First packet
scheduled

New packet pmMacVolDlDrbSingleBurst + Vol

arrives to pmMacVolDlDrbSingleBurstSamp +1
empty buffer

pmMacTimeDlDrb +1
pmMacTimeDlDrbSamp +1

pmMacTimeDlDrb +2 pmMacTimeDlDrb +1
pmMacTimeDlDrbSamp +1 ... pmMacTimeDlDrbSamp +1
pmMacContentionDelayDlDistr,bin8* +1 pmMacContentionDelayDlDistr,bin4* +1

Note:
Duration of a data burst Bin is numberology related.
pmMacContentionDelayDlDistr
counter stepping here represents
the example for 30kHz

L0002622C

Figure 29 DL MAC Integrity

pmMacVolDlDrbOverlapLastSlot +

Burst 1 Burst Overlap

Burst 2

Slot 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

pmMacOverlapTimeDlDrbExtSCell +

L0003793A

Figure 30 pmMacVolDlDrbOverlapLastSlot / pmMacOverlapTimeDlDrbExtSCell

about:blank 31/40
23.02.2025 09:39 Counters Diagrams

pmMacVolDlDrbSingleSlotShortBurst +
pmMacTimeDlDrbSingleSlotShortBurst +

Burst 1

Data volume on Pcell

Data volume on Scell

Data volume on Scell

Data volume on Scell

L0003794A

Figure 31 pmMacVolDlDrbSingleSlotShortBurst / pmMacTimeDlDrbSingleSlotShortBurst

– Time unit for these counters is 125 microseconds.

– The volume counters increment at first transmission time. No HARQ retransmission volume is included. The time
counters however includes the time for HARQ retransmission.
– In the case of Carrier Aggregation, increment is done as a merged view across all carriers used for the DRB.
– The counters for LastSlot show volume and time for data left to send in the very last slot of a data burst. The
counters for SingleBurst show volume and time for complete data bursts if they are so small that they can be
contained in one single slot (on one or several Carrier Aggregation carriers). The PCell slot duration is used to
determine LastSlot and SingleSlot duration.
– If the burst is classified as single slot short burst, the counters pmMacVolDlDrb and pmMacTimeDlDrb are not
pegged.
– The pmMacVolDlDrbLastSlot, pmMacTimeDlDrbLastSlot, and pmMacTimeDlDrbLastSlotSamp are not pegged if the
last slot of first burst overlaps with the subsequent burst. The last slot bytes are included only in
pmMacVolDlDrbOverlapLastSlot then.
– The counter pmMacContentionDelayDlDistr provides the distribution of DL MAC contention delay measurements for
the cell. The delta-time of each measured DRB and slot will peg the bin applicable for that time duration.
– PM counters with QoS suffix are corresponding to the same measurements as main counters but for the certain QoS.

5.5 UL MAC UE Volume and Time

These PM counters are to cover the UL MAC UE Volume and Time areas for use in NR NSA and NR SA, measured on MAC
SDU level for traffic using more than one slot.

The main counters for this scenario are the following:

– pmMacVolUlResUe
– pmMacTimeUlResUe
– pmMacVolUlResUeLate
– pmMacVolUlUeLastSlot
– pmMacVolUlUnresUe

about:blank 32/40
23.02.2025 09:39 Counters Diagrams

CRC
NOT OK Grant
CRC OK CRC OK CRC OK
CRC OK CRC OK
BSR > 0 Grants ULVol>0 ULVol>0
ULVol>0 ULVol>0
ULVol>0 BSR = 0 (BSR = 0)

CRC
NOT OK

Slot nr 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 ...25 26 27 28 29 30 31

pmMacVolUlResUe +
pmMacVolUlResUeLate +
pmMacTimeUlResUe +1
pmMacVolUlUnresUe +
pmMacTimeUlResUe +2

pmMacVolUlUeLastSlot +
pmMacTimeUlResUe +1

L0002623C

Figure 32 UL MAC Integrity

– Slot 0 in the drawing is the point when the gNodeB receives Buffer Status Report (BSR) indicating that the UE has a
big buffer size. Because of that gNodeB sends multiple grants to empty UE buffer.
– Slot 8 in the drawing is when the last grant is sent, the gNodeB then suppose that the UE buffer can become empty
if using all granted transmissions.
– Slots between 9 and 16 show when the UE sends data and gNodeB decodes its successful reception (CRC OK),
except slot 10 at which point the transport block cannot be decoded (CRC-NOK) by gNodeB. BSR=0 at slot 16
means that no more data can be expected.
– The transport block is retransmitted in example slot 18, and cannot be decoded for the second time. The gNodeB
receives and successfully decodes this example transport block in slot 26.
– The received volume is considered late because of long problems with decoding of transport blocks and reported in
pmMacVolUlResUeLate.
– Slot 30 in the drawing shows when the UE sends data and gNodeB decodes its successful reception (CRC OK) with
only one grant (in slot 28) needed to empty the UE buffer. BSR=0 at slot 30 means that no more data can be
expected. BSR=0 is bracketed because there can be no BSR reported if the grant just accommodates the data
without additional resources for BSR. The grant in slot 28 can be a grant to answer a PUCCH scheduling request, a
grant after reception of BSR, or a preemptive grant.
– Time unit for these counters is 125 microseconds.
– The volume is incremented when positive feedback (HARQ-ACK ) is received for each transmission. The time
stretches from the first slot where the gNB successfully received data from the UE (CRC OK) until the slot where the
gNB successfully received the last piece of data from the UE. This includes any gaps in between due to not
scheduling the UE or due to decoding failures (CRC-NOK). Slot 9 to 15 are included in the time.

about:blank 33/40
23.02.2025 09:39 Counters Diagrams

pmMacVolUlUnresUe +
pmMacVolUlResUe + pmMacVolUlUeLastSlot +

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 82 83 84 85 86 87
Slot nr
(TDD cell)
D D D S U U D D D D D D D S U U D D D D D D D S U U D D D S U U D D
...
Slot nr 0 1 2 3 4 5 6 7 8 9 10 11 12 13 41 42 43
(FDD cell) pmMacVolUlUnresUe
U U U U U U U U U U U U U U+ U U U

pmMacVolUlResUe + pmMacVolUlUeLastSlot +

pmMacTimeUlResUe +

pmMacVolUlUnresUe +

L0003802A

Figure 33 UL MAC Integrity for Carrier Aggregation

– In the case of UL Carrier Aggregation, increment is done as a merged view across all carriers used for the UE.
– If any of the volumes overlapping in time would be pegged to pmMacVolUlUeLastSlot (or pmMacVolUlUnresUe, if it
was single UL carrier transmission), all the overlapping volumes shall be pegged to pmMacVolUlUeLastSlot (if there
are preceding volumes pegged to pmMacVolUlResUe on at least one carrier for the burst) or pmMacVolUlUnresUe (if
there is no preceding volume pegged on any carrier to pmMacVolUlResUe for the burst).

5.6 DL PDCP Packet Integrity

These PM counters are to cover the DL PDCP Packet Integrity scenario.

The main counters for this scenario are the following:

– pmPdcpPktTransDlAckQoS
– pmPdcpPktTransDlAckF1UQos
– pmPdcpPktTransDlAckX2UQci
– pmPdcpPktTransDlAckXnU5qi
– pmPdcpPktTransDlDiscAqmQos
– pmPdcpPktTransDlDiscAqmF1UQos
– pmPdcpPktTransDlDiscAqmX2UQci
– pmPdcpPktTransDlDiscAqmXnU5qi
– pmPdcpPktTransDlDiscQos
– pmPdcpPktTransDlDiscF1UQos
– pmPdcpPktTransDlDiscX2UQci
– pmPdcpPktTransDlDiscXnU5qi
– pmPdcpPktTransDlQos
– pmPdcpPktTransDlF1UQos
– pmPdcpPktTransDlX2UQci
– pmPdcpPktTransDlXnU5qi
– pmPdcpPktTransDlRetransQos
– pmPdcpPktTransDlRetransF1UQos
– pmPdcpPktTransDlRetransX2UQci
about:blank 34/40
23.02.2025 09:39 Counters Diagrams
– pmPdcpPktTransDlRetransXnU5qi

All packets transmitted to gNB-DU/eNB

pmPdcpPktTransDlQos

Packet
re-transmitted
pmPdcpPktTransDlRetransQos

All packets acknowledged by RLC Pkt Disc Loss Tot

pmPdcpPktTransDlAckQos pmPdcpPktTransDlDiscQos

Disc RLC AQM

pmPdcpPktTransDlDisc
AqmQos

L0003060B

Figure 34 DL PDCP Packet Integrity for RAN Compute Groups 1-5 (PM counters under RpUserPlaneLink)

All packets transmitted to gNB-DU/eNB

pmPdcpPktTransDlY

Packet
re-transmitted
pmPdcpPktTransDlRetransY

All packets acknowledged by RLC Pkt Disc Loss Tot

pmPdcpPktTransDlAckY pmPdcpPktTransDlDiscY

Disc RLC AQM

pmPdcpPktTransDlDisc
AqmY
Y = F1UQos for packets transmitted over F1-U
Y = X2UQci for packets transmitted over X2-U
Y = XnU5qi for packets transmitted over Xn-U
L0003844A

Figure 35 DL PDCP Packet Integrity for all RAN Compute Groups (PM counters under GNBCUUPFunction)

These EBS-N counters are to cover the DL PDCP Packet Integrity scenario.

The main counters for this scenario are the following:

– pmEbsnPdcpPktTransDlAckF1UQos
– pmEbsnPdcpPktTransDlAckX2UQci
– pmEbsnPdcpPktTransDlAckXnU5qi
– pmEbsnPdcpPktTransDlDiscAqmF1UQos
– pmEbsnPdcpPktTransDlDiscAqmX2UQci
– pmEbsnPdcpPktTransDlDiscAqmXnU5qi
– pmEbsnPdcpPktTransDlDiscF1UQos
– pmEbsnPdcpPktTransDlDiscX2UQci
– pmEbsnPdcpPktTransDlDiscXnU5qi
– pmEbsnPdcpPktTransDlF1UQos
– pmEbsnPdcpPktTransDlX2UQci
– pmEbsnPdcpPktTransDlXnU5qi
– pmEbsnPdcpPktTransDlRetransF1UQos
– pmEbsnPdcpPktTransDlRetransX2UQci
– pmEbsnPdcpPktTransDlRetransXnU5qi

about:blank 35/40
23.02.2025 09:39 Counters Diagrams

All packets transmitted to gNB-DU/eNB

pmEbsnPdcpPktTransDlY

Packet
re-transmitted
pmEsbnPdcpPktTransDlRetransY

All packets acknowledged by RLC Pkt Disc Loss Tot

pmEbsnPdcpPktTransDlAckY pmEbsnPdcpPktTransDlDiscY

Disc RLC AQM

pmEbsnPdcpPktTransDl
DiscAqmY
Y = F1UQos for packets transmitted over F1-U
Y = X2UQci for packets transmitted over X2-U
Y = XnU5qi for packets transmitted over Xn-U
L0003891A

Figure 36 DL PDCP Packet Integrity for all RAN Compute Groups (ESB-N counters under NRCellCU)

5.7 UL PDCP Packet Integrity

These PM counters are to cover the PDCP Packet Integrity scenario.

The main counters for this scenario are the following:

– pmPdcpPktLossUlQos
– pmPdcpPktLossUlF1UQos
– pmPdcpPktLossUlX2UQci
– pmPdcpPktLossUlXnU5qi
– pmPdcpPktLossUlToDiscQos
– pmPdcpPktLossUlToDiscF1UQos
– pmPdcpPktLossUlToDiscX2UQci
– pmPdcpPktLossUlToDiscXnU5qi
– pmPdcpPktLossUlToQos
– pmPdcpPktLossUlToF1UQos
– pmPdcpPktLossUlToX2UQci
– pmPdcpPktLossUlToXnU5qi
– pmPdcpPktRecUlOooQos
– pmPdcpPktRecUlOooF1UQos
– pmPdcpPktRecUlOooX2UQci
– pmPdcpPktRecUlOooXnU5qi

about:blank 36/40
23.02.2025 09:39 Counters Diagrams

All packets expected to arrive in gNB-CUUP

All packets received in gNB-CUUP Packets lost

pmPdcpPktRecUlQos out of gNB-
CUUP

Stepped on
CUCP5qi::tReorderingUl All packets either suspected
expiry or explicit discard after lost or explicitly discarded
reordering queue
pmPdcpPktLossUlQos

Suspected loss
Other prior to gNB-CUUP
pmPdcpPktLossUlToQos

Stepped on Out of Order Discard of Packets

CUCP5qi::tReorderingUl Delivery packets arriving Other lost out of
expiry too late gNB-CUUP
pmPdcpPkt- pmPdcpPktLoss-
RecUlOooQos UlToDiscQos
Packets arriving after
CUCP5qi::tReorderingUl
expiry but before
CUUP5qi:: tOooUlDelivery
expiry Packets arriving after Possible reasons:
CUCP5qi::tReorderingUl *Discarded in UE
+ CUUP5qi:: tOooUlDelivery due to tPDCPDis-card
expiry expiry
*Lost on transmissions
*Lost in gNB-DU/eNB
* Overload discard
(check GNBCUUPFunc-
tion::pmPdcpPktDisc)

L0003059B

Figure 37 UL PDCP Packet Integrity for RAN Compute Groups 1-5 (PM counters under RpUserPlaneLink)

All packets expected to arrive in gNB-CUUP

All packets received in gNB-CUUP Packets lost

pmPdcpPktRecUlY out of gNB-
CUUP

Stepped on
CUCP5qi::tReorderingUl All packets either suspected
expiry or explicit discard after lost or explicitly discarded
reordering queue
pmPdcpPktLossUlY

Suspected loss
Other prior to gNB-CUUP
pmPdcpPktLossUlToY

Stepped on Out of Order Discard of Packets

CUCP5qi::tReorderingUl Delivery packets arriving Other lost out of
expiry too late gNB-CUUP
pmPdcpPkt- pmPdcpPktLoss-
RecUlOooY UlToDiscY
Packets arriving after
CUCP5qi::tReorderingUl
expiry but before
CUUP5qi:: tOooUlDelivery
expiry Packets arriving after Possible reasons:
CUCP5qi::tReorderingUl *Discarded in UE
+ CUUP5qi:: tOooUlDelivery due to tPDCPDis-card
expiry expiry
*Lost on transmissions
*Lost in gNB-DU/eNB
* Overload discard
(check GNBCUUPFunc-
Y = F1UQos for packets received, lost, or discared over F1-U tion::pmPdcpPktDisc)
Y = X2UQci for packets received, lost, or discared over X2-U
Y = XnU5qi for packets received, lost, or discared over Xn-U
L0003843A

Figure 38 UL PDCP Packet Integrity for all RAN Compute Groups (PM counters under GNBCUUPFunction)

These EBS-N counters are to cover the PDCP Packet Integrity scenario.

The main counters for this scenario are the following:

– pmEbsnPdcpPktLossUlF1UQos
– pmEbsnPdcpPktLossUlX2UQci
– pmEbsnPdcpPktLossUlXnU5qi
– pmEbsnPdcpPktLossUlToDiscF1UQos
– pmEbsnPdcpPktLossUlToDiscX2UQci
– pmEbsnPdcpPktLossUlToDiscXnU5qi
– pmEbsnPdcpPktLossUlToF1UQos
– pmEbsnPdcpPktLossUlToX2UQci
– pmEbsnPdcpPktLossUlToXnU5qi
– pmEbsnPdcpPktRecUlOooF1UQos
about:blank 37/40
23.02.2025 09:39 Counters Diagrams
– pmEbsnPdcpPktRecUlOooX2UQci
– pmEbsnPdcpPktRecUlOooXnU5qi

All packets expected to arrive in gNB-CUUP

All packets received in gNB-CUUP Packets lost

pmEbsnPdcpPktRecUlY
out of gNB-
CUUP

Stepped on
CUCP5qi::tReorderingUl All packets either suspected
expiry or explicit discard after lost or explicitly discarded
reordering queue
pmEbsnPdcpPktLossUlY

Suspected loss
Other prior to gNB-CUUP
pmEbsnPdcpPktLossUlToY

Stepped on Out of Order Discard of Packets

CUCP5qi::tReorderingUl Delivery packets arriving Other lost out of
expiry too late gNB-CUUP
pmEbsnPdcpPkt- pmEbsnPdcpPkt
RecUlOooY LossUlToDiscY
Packets arriving after
CUCP5qi::tReorderingUl
expiry but before
CUUP5qi:: tOooUlDelivery
expiry Packets arriving after Possible reasons:
CUCP5qi::tReorderingUl *Discarded in UE
+ CUUP5qi:: tOooUlDelivery due to tPDCPDis-card
expiry expiry
*Lost on transmissions
*Lost in gNB-DU/eNB
* Overload discard

Y = F1UQos for packets received, lost, or discared over F1-U

Y = X2UQci for packets received, lost, or discared over X2-U
Y = XnU5qi for packets received, lost, or discared over Xn-U
L0003892A

Figure 39 UL PDCP Packet Integrity for all RAN Compute Groups (EBS-N counters under NRCellCU)

about:blank 38/40
23.02.2025 09:39 Counters Diagrams

6 Utilization
The counters are included to cover some utilization scenarios, for use in NR NSA and NR SA.

– MCS usage for PDSCH transmissions

6.1 MCS Usage for PDSCH Transmissions

These PM counters are to cover the MCS Usage for PDSCH Transmissions scenario.

The main counters for this scenario are the following:

– pmRadioPdschTable1McsDistr
– pmRadioPdschTable1MbsfnMcsDistr
– pmRadioPdschTable2McsDistr
– pmRadioPdschTable2MbsfnMcsDistr

Start

UE scheduling entity

Yes
mcsTable = 64 QAM? pmRadioPdschTable1McsDistr +

No

No No
mcsTable = 256 QAM? MbsfnSlot?

Yes Yes

pmRadioPdschTable2McsDistr + pmRadioPdschTable1MbsfnMcsDistr +

Yes
MbsfnSlot? pmRadioPdschTable2MbsfnMcsDistr +

No

End

L0003705A

Figure 40 MCS Usage for PDSCH Transmissions

Legal | © Ericsson AB 2020 - 2024

about:blank 39/40
23.02.2025 09:39 Counters Diagrams

Copyright © Ericsson AB 2020 - 2024. All rights reserved. No part of this document may be reproduced in any form
without the written permission of the copyright owner.

Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology,
design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the
use of this document.

Trademarks All trademarks mentioned herein are the property of their respective owners. These are shown in the document
Trademark Information.

about:blank 40/40