Professional Documents
Culture Documents
This counter counts the number of data chunks sent to the SCTP peer on the S1 interface per SCTP association. Resent SCTP
This counter counts the number of data chunks received from the SCTP peer on the S1 interface per SCTP association
This counter counts the number of data chunks resent to the SCTP peer on the S1 interface per SCTP association.
This counter is the cumulative duration of congested periods of a single SCTP association on the S1 interface. The counter sta
This counter counts the number of occurences when the SCTP association on the S1 interface state changes from "not conges
This counter is the cumulative duration of unavailable periods of a single SCTP association on the S1 interface. The counter sta
The counter counts the number of occurences when the SCTP association on the S1 interface state changes from "connected"
This counter counts the number of data chunks sent to the SCTP peer on the X2 interface per SCTP association. Resent SCTP
This counter counts the number of data chunks received from the SCTP peer on the X2 interface per SCTP association
This counter counts the number of data chunks resent to the SCTP peer on the X2 interface per SCTP association.
This counter is the cumulative duration of congested periods of a single SCTP association on the X2 interface. The counter sta
This counter counts the number of occurences when the SCTP association on the X2 interface state changes from "not conges
This counter is the cumulative duration of unavailable periods of a single SCTP association on the X2 interface. The counter sta
The counter counts the number of occurences when the SCTP association on the X2 interface state changes from "connected"
This counter counts the number of data chunks sent to the SCTP peer on the M3 interface per SCTP association. Resent SCTP
This counter counts the number of data chunks received from the SCTP peer on the M3 interface per SCTP association
This counter counts the number of data chunks resent to the SCTP peer on the M3 interface per SCTP association.
This counter is the cumulative duration of congested periods of a single SCTP association on the M3 interface. The counter sta
This counter counts the number of occurences when the SCTP association on the M3 interface state changes from "not conges
This counter is the cumulative duration of unavailable periods of a single SCTP association on the M3 interface. The counter st
The counter counts the number of occurences when the SCTP association on the M3 interface state changes from "connected"
The number of packets received on the plain IP interface that were delivered to higher-layer protocols.
The total number of kilo-bytes received on the plain IP interface, including framing characters.
The number of packets that were successfully transmitted over the plain IP interface
The total number of kilo-bytes transmitted over the plain IP the interface, including framing characters.
_x000D_
Fragments
Note: In caseshall be counted
of FZM: LNF5.0 asrelease,
individualthisIPcounter
packets.
does not work for the plain (untagged) IP interface, however it works for th
_x000D_
In case
The of FZM:
number of IPLNF5.0 release,
Multicast packetsthisorcounter
fragments doesreceived
not workat for
thethe plain (untagged)
IP network IP interface, however it works for the plain
interface._x000D_
Fragments
The shall be
total number of counted
kilo-bytesasreceived
individual in packets.
IP Multicast packets or fragments at IP network interface. _x000D_
Fragments
The numbershall
of IPbeMulticast
countedpackets
as individual packets.transmitted at the IP network interface._x000D_
or fragments
Fragments
The shall be
total number of counted
kilo-bytesas transmitted
individual packets.
in IP Multicast packets or fragments at the IP network interface._x000D_
Fragments shall be counted as individual packets.
_x000D_
- No IPsec for multicast traffic, so decryption does not need to be taken into account._x000D_
The total number of kilo-bytes transmitted over the plain IP interface, including framing characters, using Expedited Forwarding
The total number of outbound packets that were successfully transmitted over the plain IP interface within the Expedited Forwa
The number of outbound kilo-bytes within the Expedited Forwarding PHB class that were dropped in the IP scheduler due to co
The number of outbound packets within the Expedited Forwarding PHB class that were dropped in the IP scheduler due to con
The total number of kilo-bytes transmitted over the plain IP interface, including framing characters, using the Assured Forwardin
The total number of outbound packets that were successfully transmitted over the plain IP interface within the Assured
The number of outbound kilo-bytes within the Assured Forwarding 4 PHB class that were dropped in the IP scheduler due to co
The number of outbound packets within the Assured Forwarding 4 PHB class that were dropped in the IP scheduler due to con
The total number of kilo-bytes transmitted over the plain IP interface out of the interface, including framing characters, using the
The total number of outbound packets that were successfully transmitted over the plain IP interface within the Assured Forward
The number of outbound kilo-bytes within the Assured Forwarding 3 PHB class that were dropped in the IP scheduler due to co
The number of outbound packets within the Assured Forwarding 3 PHB class that were dropped in the IP scheduler due to con
The total number of kilo-bytes transmitted over the plain IP interface out of the interface, including framing characters, using the
The total number of outbound packets that were successfully transmitted over the plain IP interface within the Assured Forward
The number of outbound kilo-bytes within the Assured Forwarding 2 PHB class that were dropped in the IP scheduler due to co
The number of outbound packets within the Assured Forwarding 2 PHB class that were dropped in the IP scheduler due to con
The total number of kilo-bytes transmitted over the plain IP interface, including framing characters, using the Assured Forwardin
The total number of outbound packets that were successfully transmitted over the plain IP interface within the Assured Forward
The number of outbound kilo-bytes within the Assured Forwarding 1 PHB class that were dropped in the IP scheduler due to co
The number of outbound packets within the Assured Forwarding 1 PHB class that were dropped in the IP scheduler due to con
The total number of kilo-bytes transmitted over the plain IP interface, including framing characters, using the Best Effort PHB cl
The total number of outbound packets that were successfully transmitted over the plain IP interface within the Best Effort PHB c
kilo-byteswithin
The number of outbound packets withinthe
theBest
BestEffort
EffortPHB
PHBclass
classthat
thatwere
weredropped
droppedininthe
theIPIPscheduler
schedulerdue
duetotocongestion.
congestion.
counter
The total is available
number for both
of kilo-bytes the Ethernet-based
received over the plainIPIPinterface
interface,and for each
including VLAN characters, using Expedited Forwarding PH
framing
The counter
number is
of available for both that
inbound packets the Ethernet-based
were successfully IP received
interface within
and forthe
each VLAN Forwarding PHB class.
Expedited
The counter is available for both the Ethernet-based IP interface and for each VLAN
total number of kilo-bytes received out of the interface, including framing characters, using the Assured Forwarding 4 PHB
The counter is available for both the Ethernet-based IP interface and for
number of inbound packets that were successfully received within the Assured each VLANForwarding 4 PHB class.
counter
The total is available
number for both
of kilo-bytes the Ethernet-based
received IP interface
out of the interface, and framing
including for eachcharacters,
VLAN using the Assured Forwarding 3 PHB
counter is
The number of available for both that
inbound packets the Ethernet-based
were successfully IP received
interface within
and forthe
each VLANForwarding 3 PHB class.
Assured
The counter is available for both the Ethernet-based IP interface and for each VLAN
The total number of kilo-bytes received out of the interface, including framing characters, using the Assured Forwarding 2 PHB
The number of inbound packets that were successfully received within the Assured Forwarding 2 PHB class.
The total number of kilo-bytes received out of the interface, including framing characters, using the Assured Forwarding 1 PHB
The number of inbound packets that were successfully received within the Assured Forwarding 1 PHB class.
The total number of kilo-bytes received out of the interface, including framing characters, using the Best Effort PHB class.
The number of inbound packets that were successfully received within the Best Effort PHB class.
NOTE: _15 is just a string and has no special relevance in counter name.
NOTE: _15 is just a string and has no special relevance in counter name.
NOTE: _15 is just a string and has no special relevance in counter name.
NOTE: _15 is just a string and has no special relevance in counter name.
NOTE: _15 is just a string and has no special relevance in counter name.
The number of ingress Ethernet frames discarded due to rate limiting.
Number of Ethernet discarded recieved packets not matching the VLAN membership configuration for that switch-port.
Number of Ethernet TX frames discarded due to egress shaping per queue per interface.
Number of Ethernet TX frames discarded due to egress shaping per queue per interface.
Number of Ethernet TX frames discarded due to egress shaping per queue per interface.
Number of Ethernet TX frames discarded due to egress shaping per queue per interface.
Number of Ethernet TX frames discarded due to egress shaping per queue per interface.
Number of Ethernet TX frames discarded due to egress shaping per queue per interface.
The number of successfully sent ESP packets which are are related to a protect policy.
The counter._x000D_
this number of received ESP packets addressed to a local tunnel endpoint which where received with a SPI which is related to
Note 2: Discarded
NOTE: The defaultpacket
policymatching
is DISCARD until IPSec
the default policies
policy arebe
shall not configured.
counted with this counter._x000D_
Note 2: The default policy is DISCARD until IPSec policies are configured.
The number of bypassed ESP packets in egress direction.
The number of received packets not addressed to an local tunnel endpoint or packets which do not have an ESP or AH header
The number of dropped packets due to ingress rate limiting. Packets are counted per BTS, e
The number of packets discarded due to ingress packet filtering violations. Packets are counted per BTS, e.
The number of packets received on the plain IP interface that were delivered to higher-layer protocols.
The total number of kilo-bytes received on the plain IP interface, including framing characters.
The number of packets that were successfully transmitted over the VLAN IP interface.
The total number of kilo-bytes transmitted over the VLAN IP the interface, including framing characters.
_x000D_
Fragments shall be counted as individual IP packets.
The number of total outbound packets that were dropped in the IP scheduler due to congestion.
The number of total outbound
IP Multicast kilo-bytes
packets that werereceived
or fragments droppedatinthe
theIP
IPnetwork
scheduler due to congestion.
interface._x000D_
Fragments
The shall be
total number of counted
kilo-bytes asreceived
individual
in packets.
IP Multicast packets or fragments at IP network interface. _x000D_
Fragments
The numbershall
of IPbeMulticast
countedpackets
as individual packets.transmitted at the IP network interface._x000D_
or fragments
Fragments
The numbershall be counted
of kilo-bytes as individual
transmitted at thepackets.
IP network interface._x000D_
-Fragments shall be
Counted before counted as individual packets.
reassembly._x000D_
No IPsecbefore
- Counted for multicast traffic, so decryption does not need to be taken into account.
reassembly._x000D_
- No IPsec for multicast traffic, so decryption does not need to be taken into account.
The number of outbound kilo-bytes that were successfully transmitted over the VLAN interface within the Expedited Forwarding
The number of outbound packets that were successfully transmitted over the VLAN interface within the Expedited Forwarding P
The number of outbound kilo-bytes within the Expedited Forwarding PHB class that were dropped in the IP scheduler due to co
The number of outbound packets within the Expedited Forwarding PHB class that were dropped in the IP scheduler due to con
The number of outbound kilo-bytes that were successfully transmitted over the VLAN interface within the Assured Forwarding 4
The number of outbound packets that were successfully transmitted over the VLAN interface within the Assured Forwarding 4 P
The number of outbound kilo-bytes within the Assured Forwarding 4 PHB class that were dropped in the IP scheduler due to co
The number of outbound packets within the Assured Forwarding 4 PHB class that were dropped in the IP scheduler due to con
The number of outbound kilo-bytes within the Assured Forwarding 3 PHB class that were successfully transmitted over the VLA
The number of outbound packets within the Assured Forwarding 3 PHB class that were successfully transmitted over the VLAN
The number of outbound kilo-bytes within the Assured Forwarding 3 PHB class that were dropped in the IP scheduler due to co
The number of outbound packets within the Assured Forwarding 3 PHB class that were dropped in the IP scheduler due to con
The number of outbound kilo-bytes within the Assured Forwarding 2 PHB class that were successfully transmitted over the VLA
The number of outbound packets within the Assured Forwarding 2 PHB class that were successfully transmitted over the VLAN
The number of outbound kilo-bytes within the Assured Forwarding 2 PHB class that were dropped in the IP scheduler due to co
The number of outbound packets within the Assured Forwarding 2 PHB class that were dropped in the IP scheduler due to con
The number of outbound kilo-bytes within the Assured Forwarding 1 PHB class that were successfully transmitted over the VLA
The number of outbound packets within the Assured Forwarding 1 PHB class that were successfully transmitted over the VLAN
The number of outbound kilo-bytes within the Assured Forwarding 1 PHB class that were dropped in the IP scheduler due to co
The number of outbound packets within the Assured Forwarding 1 PHB class that were dropped in the IP scheduler due to con
The number of outbound kilo-bytes within the Best Effort PHB class that were successfully transmitted over the VLAN interface
The number of outbound packets within the Best Effort PHB class that were transmitted over the VLAN interface within the Bes
The number of outbound kilo-bytes within the Best Effort PHB class that were dropped in the IP scheduler due to congestion.
The number of outbound packets within the Best Effort PHB class that were dropped in the IP scheduler due to congestion.
The total number of kilo-bytes received on the VLAN interface for the Expedited Forwarding PHB class. The counter includes fr
The total number of packets received on the VLAN interface for the Expedited Forwarding PHB class. The counter includes fram
The total number of kilo-bytes received on the VLAN interface for the Assured Forwarding 4 PHB class. The counter includes fr
The total number of packets received on the VLAN interface for the Assured Forwarding 4 PHB class. The counter includes fram
The total number of kilo-bytes received on the VLAN interface for the Assured Forwarding 3 PHB class. The counter includes fr
The total number of packets received on the VLAN interface for the Assured Forwarding 3 PHB class. The counter includes fram
The total number of kilo-bytes received on the VLAN interface for the Assured Forwarding 2 PHB class. The counter includes fr
The total number of packets received on the VLAN interface for the Assured Forwarding 2 PHB class. The counter includes fram
The total number of kilo-bytes received on the VLAN interface for the Assured Forwarding 1 PHB class. The counter includes fr
The total number of packets received on the VLAN interface for the Assured Forwarding 1 PHB class. The counter includes fram
The total number of kilo-bytes received on the VLAN interface for the Best Effort PHB class. The counter includes framing char
The total number of packets received on the VLAN interface for the Best Effort PHB class. The counter includes framing charac
The number of ethernet framesreceived on the interface.
_x000D_
Note: In FlexiZone Micro the system reports the number of bytes of received frames at a VLAN interface with an offset of -14 by
The number of ethernet frames transmitted on the interface.
The number of ethernet Bytes transmitted on the interface
The number
Number of ethernet
of kilo-bytes frames
in valid received
frames on the
received oninterface. Thisinterface
the Ethernet includes layer._x000D_
those that may be subsequently discarded due to errors
Per interface.
The number of ethernet frames transmitted on the interface.
The number of ethernet bytes transmitted on the interface.
Note 2:
Note: This
Link counter
OAM, is notOAM,
Service supported in RL50FZ
IEEE1588v2, for FZM.
SyncE, RSTP multicast frames do not convey IP payload and thus are not include
Note 2: Ethernet Multicast Frames which are switched from one external Ethernet port to another are not included in this counte
This is the calculated average Round trip time (RTT) for TWAMP messages that the BTS has sent to its remote peer during the
This is the maximum detected Round trip time (RTT) for TWAMP messages that the BTS has sent to its remote peer during the
This is the minimum detected Round trip time (RTT) for TWAMP messages that the BTS has sent to its remote peer during the
This is the number of measurements packets lost when no reply packet is received within timeout period or a reply-packet with
This is the number of transmitted TWAMP messages for the TWAMP session.
The number of normal GBR connection requests which had been accepted by Tranport Admission Control.
The number of Handover connection requests which had been accepted by Tranport Admission Control.
The number of Emergency connection requests which had been accepted by Tranport Admission Control.
The number of normal GBR connection requests which had been rejected by Tranport Admission Control due to insufficient tra
the number of Handover connection requests which had been rejected by Tranport Admission Control due to insufficient transp
The number of Emergency connection requests which had been rejected by Tranport Admission Control due to insufficient tran
The mean value of UL total GBR rate.
The maximum value of UL total GBR rate.
The mean value of DL total GBR rate
The maximum value of DL total GBR rate.
The number of received ToP sync event messages. Event messages are time stamped and used for clock recovery.
The minimum value of the estimated phase error, between the current phase of the network element and the estimated phase b
The average value of the estimated phase error, between the current phase of the network element and the estimated phase b
The maximum value of the estimated phase error, between the current phase of the network element and the estimated phase
The number of seconds during this interval while the timing over packet phase synchronisation service was in locked state.
The number of EPS bearer setup failures due to any Radio Network Layer cause except "radio resources not available". Each b
The number of EPS bearer setup failures due to Transport Layer. Each bearer of the "E-RAB Failed to Setup List" IE is counted
The number of EPS bearer setup failures due to Radio Resource reasons. Each bearer of the "E-RAB Failed to Setup List" IE h
The number of EPS bearer setup failures due to Other reasons. Each bearer of the "E-RAB Failed to Setup List" IE is counted.
The number of released E-RABs initiated by the eNB due to user inactivity.
The number of released E-RABs initiated by the eNB due to Radio Link Failure.
The number of released E-RABs initiated by the eNB due to other reasons.
The number of released E-RABs initiated by the eNB due to Redirect.
The number of released QCI1 E-RABs initiated by the eNB due to user inactivity.
The number of released QCI1 E-RABs initiated by the eNB due to Radio Link Failure.
The number of released QCI1 E-RABs initiated by the eNB due to other reasons.
The number
This of released
measurement QCI1
provides theE-RABs
numberinitiated
of GBRby the eNB due to Redirect.
E-RABs
(Guaranteed
This Bit Rate
measurement bearers,
provides the3GPP TS of
number 23.203) being
non-GBR released due to lack of radio resources.
E-RABs
(non-Guaranteed Bit Rate bearers, 3GPP TS 23.203) being released due to lack of radio resources.
It comprises also the released Data Radio Bearers originally setup due to an incoming Handover.
It comprises also the release of Data Radio Bearers originally setup due to an incoming Handover.
It comprises also the release of Data Radio Bearers originally setup due to an incoming Handover.
The number of released Data Radio Bearers due to Radio Network Layer cause Redirect.
The measurement gives indication of the eUu interface traffic load by reporting Minimum UL PDCP traffic throughput.
The measurement gives indication of the eUu interface traffic load by reporting Minimum DL PDCP traffic throughput.
The number of Signaling Connection Establishment failures due to Rejection by RRM RAC. The UE has not reached the ECM-
The number of Signaling Connection Establishment attempts due to other reasons. From UE's point of view, the transition from
Measure NE
ment_na counter Related to
me name Feature Updated
8000: LTE • LTE770: B
This counter is updated when eNB transmits an S1AP:S1 Setup Request message to MME.
8000: LTE • LTE770: B
This counter is updated when eNB receives an S1AP:S1 Setup Response message sent by M
8000: LTE • LTE770: B
This counter is updated when the timer expires.
8000: LTE • LTE770: B
This counter is updated when eNB receives an S1AP:S1 Setup Failure message sent by MME
8000: LTE • LTE770: B
This counter is updated when eNB receives an S1AP:Paging message sent by MME.
8000: LTE • LTE522: S
Transmission of a global S1AP: RESET Message
8000: LTE • LTE522: S
Reception of a global S1AP:RESET Message sent by MME to the eNB.
8000: LTE • LTE522: S
Transmission of a partial S1AP: RESET Message
8000: LTE • LTE522: S
Reception of a partial S1AP:RESET Message sent by MME to the eNB.
8000: LTE • LTE562: Reception of an S1AP:UE CONTEXT MODIFICATION REQUEST message sent by MME to th
8000: LTE S1AP The counter is incremented when an S1AP:WRITE-REPLACE WARNING RESPONSE messa
8000: LTE S1AP The counter is incremented when an S1AP:KILL RESPONSE message is sent to the MME and
8000: LTE • LTE805: P
This counter is updated at the transmission of an S1AP: UPLINK NAS TRANSPORT message
8000: LTE • LTE572:
LTE805: IMS
P
This emergency
counter is updated
sessionsfollowing the reception of an S1AP: DOWNLINK NAS TRANSPORT m
8000: LTE • LTE7: Support
Reception
of multiple
of the EPS
LTE572: IMS emergency sessionsS1AP:
bearer
E-RAB SETUP REQUEST message (eNB <- MME) in case that this m
8000: LTE • LTE572: Transmission
LTE7: Support of the
EPS bearerE-RAB SETUP RESPONSE message (eNB -> MME) in case that t
S1AP:
of multiple sessions
IMS emergency
8000: LTE • LTE7: Support
Transmission
of multiple of the
EPSS1AP:
bearerE-RAB SETUP RESPONSE message (eNB -> MME) in case that
8000: LTE • LTE68: Su
Reception of an S1AP:LOCATION REPORTING CONTROL message sent by MME to the eNB
8000: LTE • LTE68: Su
Transmission
Reception of an S1AP:LOCATION
of S1AP:MME CONFIGURATIONREPORT message including
TRANSFER to the MME.
'SON Information Reply' w
8000: LTE • LTE782: Transmission
- (3GPP TS 36.413)of S1AP:ENB CONFIGURATION TRANSFER including 'SON Information Reque
8000: LTE • LTE494:
LTE782: Commercial
- (3GPP TS 36.413)
Mobile Alert System
8000: LTE • LTE843: ETWS
The counter
broadcast
is updated
LTE494: Commercial Mobile Alertwhen an S1AP:WRITE-REPLACE WARNING REQUEST message is r
System
8000: LTE • LTE843: ETWS
The counter
broadcast
is updated when an S1AP:WRITE-REPLACE WARNING RESPONSE message is
8000: LTE • LTE494: The counter is updated when an S1AP:KILL REQUEST message is received from MME.
8000: LTE • LTE494: The counter is updated when an S1AP:KILL RESPONSE message is sent to MME.
8000: LTE • LTE951: E
This counter is updated upon the reception of an S1AP:DOWNLINK UE ASSOCIATED LPPA T
8000: LTE • LTE951: E
This counter is updated upon the transmission of an S1AP:UPLINK UE ASSOCIATED LPPA T
8000: LTE • LTE951: E
This counter is updated upon the transmission of an S1AP:UPLINK UE ASSOCIATED LPPA T
8000: LTE • LTE951: E
This counter is updated upon the transmission of an S1AP:UPLINK UE ASSOCIATED LPPA T
8001: LTE • LTE651: At the first transmission of a TB containing a segment of the SDU.
8001: LTE • LTE651: At the first transmission of a TB containing a segment of the SDU.
8001: LTE • LTE651: At the first transmission of a TB containing a segment of the SDU.
8001: LTE • LTE651: The counter is updated if the current minimum is greater than the last detected delay value at t
8001: LTE • LTE651: The counter is updated if the current maximum is less than the last detected delay value at the
8001: LTE • LTE651: The counter is updated based on currently calculated mean delay value at the transmission of
8001: LTE • LTE651: The reception of an RA preamble group A sent by the UE to the eNB.
8001: LTE • LTE651: The reception of an RA preamble group B sent by the UE to the eNB.
8001: LTE • LTE651: The transmission of a RA preamble response sent by the eNB to the UE.
8001: LTE • LTE651: The transmission of a TB on PCH.
8001: LTE • LTE651: The transmission of a TB on BCH.
8001: LTE • LTE651: The transmission of a TB for the first time on DL-SCH.
8001: LTE • LTE651: HARQ retransmission of a TB on DL-SCH.
8001: LTE • LTE651: A correctly received TB by original transmission
8001: LTE • LTE651: A correctly received TB with retransmission.
8001: LTE • LTE651: An erroneous TB reception
8001: LTE • LTE651: When MCS0 is used for transmission.
8001: LTE • LTE651: When MCS1 is used for transmission.
8001: LTE • LTE651: When MCS2 is used for transmission.
8001: LTE • LTE651: When MCS3 is used for transmission.
8001: LTE • LTE651: When MCS4 is used for transmission.
8001: LTE • LTE651: When MCS5 is used for transmission.
8001: LTE • LTE651: When MCS6 is used for transmission.
8001: LTE • LTE651: When MCS7 is used for transmission.
8001: LTE • LTE651: When MCS8 is used for transmission.
8001: LTE • LTE651: When MCS9 is used for transmission.
8001: LTE • LTE651: When MCS10 is used for transmission.
8001: LTE • LTE651: When MCS11 is used for transmission.
8001: LTE • LTE651: When MCS12 is used for transmission.
8001: LTE • LTE651: When MCS13 is used for transmission.
8001: LTE • LTE651: When MCS14 is used for transmission.
8001: LTE • LTE651: When MCS15 is used for transmission.
8001: LTE • LTE651: When MCS16 is used for transmission.
8001: LTE • LTE651: When MCS17 is used for transmission.
8001: LTE • LTE651: When MCS18 is used for transmission.
8001: LTE • LTE651: When MCS19 is used for transmission.
8001: LTE • LTE651: Performance
When MCS20Monitoring
is used forI transmission.
8001: LTE • LTE651:
LTE829: Performance
Increased
When MCS21
uplink
is MCS
used range
MonitoringforI transmission.
8001: LTE • LTE829: When MCS22
Increased is
uplink used
MCS
LTE651: Performance Monitoring forI transmission.
range
8001: LTE • LTE829: Increased
When MCS23
uplink
is MCS
used
LTE651: Performance Monitoring range
forI transmission.
8001: LTE • LTE829: Increased
When MCS24
uplink
is MCS
used
LTE651: Performance Monitoring range
forI transmission.
8001: LTE • LTE651:
LTE44: 64When
QAMMCS25
in UL Monitoring
Performance is used forI transmission.
8001: LTE • LTE651:
LTE44: 64When
QAMMCS26
in UL Monitoring
Performance is used forI transmission.
8001: LTE • LTE651:
LTE44: 64When
QAMMCS27
in UL Monitoring
Performance is used forI transmission.
8001: LTE • LTE44: 64When
QAMMCS28
in UL is used for transmission.
8001: LTE • LTE651: When MCS0 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS1 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS2 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS3 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS4 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS5 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS6 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS7 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS8 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS9 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS10 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS11 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS12 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: Performance
When MCS13Monitoring
is used forI transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651:
LTE939: Performance
Usage
When MCS14
based Monitoring
PDCCH
is used adaptation
forI transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS15
LTE939: Performance
Usage is used adaptation
based Monitoring
PDCCH forI transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE939: Usage
When MCS16
based PDCCH
is used adaptation
for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS17 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS18 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS19 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS20 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS21 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS22 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS23 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS24 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS25 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS26 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS27 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS28 is used for transmission. SIB, Paging and RA response excluded.
8001: LTE • LTE651: When MCS0 is used for transmission.
8001: LTE • LTE651: When MCS1 is used for transmission.
8001: LTE • LTE651: When MCS2 is used for transmission.
8001: LTE • LTE651: When MCS3 is used for transmission.
8001: LTE • LTE651: When MCS4 is used for transmission.
8001: LTE • LTE651: When MCS5 is used for transmission.
8001: LTE • LTE651: When MCS6 is used for transmission.
8001: LTE • LTE651: When MCS7 is used for transmission.
8001: LTE • LTE651: When MCS8 is used for transmission.
8001: LTE • LTE651: When MCS9 is used for transmission.
8001: LTE • LTE651: When MCS10 is used for transmission.
8001: LTE • LTE651: When MCS11 is used for transmission.
8001: LTE • LTE651: When MCS12 is used for transmission.
8001: LTE • LTE651: When MCS13 is used for transmission.
8001: LTE • LTE651: When MCS14 is used for transmission.
8001: LTE • LTE651: When MCS15 is used for transmission.
8001: LTE • LTE651: When MCS16 is used for transmission.
8001: LTE • LTE651: When MCS17 is used for transmission.
8001: LTE • LTE651: When MCS18 is used for transmission.
8001: LTE • LTE651: When MCS19 is used for transmission.
8001: LTE • LTE651: Performance
When MCS20Monitoring
is used forI transmission.
8001: LTE • LTE651:
LTE829: Performance
Increased
When MCS21
uplink
is MCS
used range
MonitoringforI transmission.
8001: LTE • LTE651:
LTE829: Performance
Increased
When MCS22
uplink
is MCS
used range
MonitoringforI transmission.
8001: LTE • LTE651:
LTE829: Performance
Increased
When MCS23
uplink
is MCS
used range
MonitoringforI transmission.
8001: LTE • LTE651:
LTE829: Performance
Increased
When MCS24
uplink
is MCS
used range
MonitoringforI transmission.
8001: LTE • LTE651:
LTE44: 64When
QAMMCS25 is used forI transmission.
in UL Monitoring
Performance
8001: LTE • LTE651:
LTE44: 64When
QAMMCS26
in UL Monitoring
Performance is used forI transmission.
8001: LTE • LTE44: 64When
QAM MCS27
in UL is used forI transmission.
LTE651: Performance Monitoring
8001: LTE • LTE44: 64When
QAMMCS28
in UL is used for transmission.
8001: LTE • LTE651: When MCS0 is used for transmission.
8001: LTE • LTE651: When MCS1 is used for transmission.
8001: LTE • LTE651: When MCS2 is used for transmission.
8001: LTE • LTE651: When MCS3 is used for transmission.
8001: LTE • LTE651: When MCS4 is used for transmission.
8001: LTE • LTE651: When MCS5 is used for transmission.
8001: LTE • LTE651: When MCS6 is used for transmission.
8001: LTE • LTE651: When MCS7 is used for transmission.
8001: LTE • LTE651: When MCS8 is used for transmission.
8001: LTE • LTE651: When MCS9 is used for transmission.
8001: LTE • LTE651: When MCS10 is used for transmission.
8001: LTE • LTE651: When MCS11 is used for transmission.
8001: LTE • LTE651: When MCS12 is used for transmission.
8001: LTE • LTE651: When MCS13 is used for transmission.
8001: LTE • LTE651: When MCS14 is used for transmission.
8001: LTE • LTE651: When MCS15 is used for transmission.
8001: LTE • LTE651: When MCS16 is used for transmission.
8001: LTE • LTE651: When MCS17 is used for transmission.
8001: LTE • LTE651: When MCS18 is used for transmission.
8001: LTE • LTE651: When MCS19 is used for transmission.
8001: LTE • LTE651: When MCS20 is used for transmission.
8001: LTE • LTE651: When MCS21 is used for transmission.
8001: LTE • LTE651: When MCS22 is used for transmission.
8001: LTE • LTE651: When MCS23 is used for transmission.
8001: LTE • LTE651: When MCS24 is used for transmission.
8001: LTE • LTE651: When MCS25 is used for transmission.
8001: LTE • LTE651: When MCS26 is used for transmission.
8001: LTE • LTE651: When MCS27 is used for transmission.
8001: LTE • LTE651: When MCS28 is used for transmission.
8001: LTE • LTE651: The counter is updated when RLC SDU on DL DTCH is sent
8001: LTE • LTE651: The counter is updated when RLC SDU on DL DCCH is sent
8001: LTE • LTE651: The counter is updated when RLC SDU on UL DTCH is received
8001: LTE • LTE651: The counter is updated when RLC SDU on UL DCCH is received
8001: LTE • LTE651: The counter is updated when RLC AM/UM data PDU is transmitted for the first time on the RL
8001: LTE • LTE651: The counter is updated when a RLC AM data PDU is retransmitted on the RLC level.
8001: LTE • LTE651: The counter is updated when a non-duplicate RLC AM/UM data PDU is received
8001: LTE • LTE770: B
The counter is updated when RLC Control PDU related to DCCH or DTCH is transmitted first t
8001: LTE • LTE770: B
The counter is updated when RLC Data PDU related to DTCH is transmitted first time on the R
8001: LTE • LTE770: B
The counter is updated when an UL RLC PDU is received.
8001: LTE • LTE770: B
The counter is updated when a duplicate UL RLC PDU is received. Valid for duplicate AMD PD
8001: LTE • LTE770: B
This counter is updated when a retransmission is requested on the RLC level for a UL RLC PD
8001: LTE • LTE770: B
This counter is updated when a UL RLC PDU has been discarded. Duplicate RLC PDU's recei
8001: LTE • LTE770: B
This counter is updated when RLC SDU is received from the PDCP layer.
8001: LTE • LTE770: B
The arithmetical average number of UE contexts per TTI with buffered DL RLC data is updated
8001: LTE • LTE770: B
The maximum number of UE contexts with UP data on DL RLC buffer is updated to this counte
8001: LTE • LTE1047:The aggregation is started when Control Plane enters Overload level 1 and it is stopped when
8001: LTE • LTE770: B
This counter is updated based on the buffer status reports. The value is the arithmetical averag
8001: LTE • LTE770: B
This counter is updated based on the buffer status reports. The maximum number of UE conte
8001: LTE • LTE770:
LTE1047:The
Basicaggregation
Performanceis started
Counterwhen Control
Collection II Plane enters Overload level 2 and it is stopped when
8001: LTE • LTE770:
LTE2054:Basic
This
Measurement
counter is updated
Report
Performance addition
on the
Counter reception
with PDCP
Collection II ofKPI
an PDCP
counter
SDU
subset
from UE.
8001: LTE • LTE770: This
LTE2054:Basiccounter
Measurement is updated
Report
Performance for successful
addition
Counter PDCP
II KPISDU
with PDCP
Collection transmissions
counter subset during the measurement peri
8001: LTE • LTE2054:This
Measurement
counter is updated
Report addition
when awith
PDCPPDCP
SDUKPI is removed
counter subset
from the eNB without having started th
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: B
This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE1402:This counter is updated by the number of UEs using UL intra-eNB CoMP in each TTI when PU
8001: LTE • LTE805: PThis counter is updated after each sampling interval with the arithmetical average of samples e
8001: LTE • LTE805: PThis counter is updated after each sampling interval with the peak number of UEs in RRC_CO
8001: LTE • LTE1545 The counter is updated per TTI by the average number of UEs, which are paired by UL MU-M
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE770: BThis counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE805: PThe counter is updated when the size of the RLC buffer changes, except when there is no data
8001: LTE • LTE805: PThe counter is updated when the size of the RLC buffer changes, except when there is no data
8001: LTE • LTE805: PThe counter is updated when the size of the RLC buffer changes, except when there is no data
8001: LTE • LTE805: PThe counter is updated when the size of the RLC buffer changes, except when there is no data
8001: LTE • LTE805: PThe counter is updated when the size of the RLC buffer changes, except when there is no data
8001: LTE • LTE805: PThe counter is updated when the size of the RLC buffer changes, except when there is no data
8001: LTE • LTE497: The counter is updated after the end of the sampling period by the average number of PRBs a
8001: LTE • LTE497: The counter is updated after the end of the sampling period by the average number of PRBs a
8001: LTE • LTE770: BThis counter is updated on the transmission of an RLC data block on BCCH towards the UE.
8001: LTE • LTE770: BThis counter is updated on the transmission of an RLC SDU on CCCH towards the UE.
8001: LTE • LTE770: BThis counter is updated on the transmission of an RLC SDU on PCCH towards the UE.
8001: LTE • LTE770: BThis counter is updated on the reception of an RLC SDU on CCCH from UE.
8001: LTE Cell Load The arithmetical average of samples taken from the number of active UEs.
8001: LTE • LTE770: BThe maximum value of the samples of active UEs during a measurement period.
8001: LTE • LTE9: SerThe arithmetical average number of UE contexts per TTI with buffered DL RLC data for QCI1 b
8001: LTE • LTE496: The arithmetical average number of UE contexts per TTI with buffered DL RLC data for QCI2 b
8001: LTE • LTE496: The arithmetical average number of UE contexts per TTI with buffered DL RLC data for QCI3 b
8001: LTE • LTE496: The arithmetical average number of UE contexts per TTI with buffered DL RLC data for QCI4 b
8001: LTE • LTE843: The counter is updated when the primary ETWS
secondary ETWS notification is sent
notification viavia
is sent SIB10.
SIB11.
8001: LTE • LTE843: The
In case of segmented
counter is updatedwarning message
when the CMAS contents theiscounter
notification sent viaisSIB12.
updated when the last segmen
8001: LTE • LTE494: In case of segmented warning message contents the counter is updated when the last segmen
8001: LTE • LTE569: The eNB-internal average calculation of the number of active UEs with UE Category 8 (3GPP
8001: LTE • LTE9: SerThe arithmetical average number of UE contexts per TTI with buffered DL RLC data for non-G
8001: LTE • LTE541: The counter is updated when MCS29 is used for transmission. SIB, Paging and RA response e
8001: LTE • LTE541: The counter is updated when MCS30 is used for transmission. SIB, Paging and RA response e
8001: LTE • LTE541: The counter is updated when MCS31 is used for transmission. SIB, Paging and RA response e
8001: LTE • LTE541: The counter is updated when NACK without bundle is received for PDSCH transmission using
8001: LTE • LTE541: The counter is updated when NACK without bundle is received for PDSCH transmission using
8001: LTE • LTE541: The counter is updated when NACK without bundle is received for PDSCH transmission using
8001: LTE • LTE541: This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE541: This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE541: This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE541: The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE541: The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE541: The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE541: The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE541: The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE541: The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE541: The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE541: The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE541: The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE Cell Load This counter is updated after each sampling interval with the sample taken from the number of
8001: LTE Cell Load This counter is updated by value 1 when the number of Active UEs is summed to counter SUM
8001: LTE Cell Load This counter is updated after each sampling interval with the sample taken from the number of
8001: LTE Cell Load This counter is updated by value 1 when the number of Active UEs is summed to counter SUM
8001: LTE • LTE2128:This counter
The time is at
ends updated
the firstintransmission
each active TTI
of aby
TBthe number a
containing ofsegment
UEs thatof are
thepre-selected
SDU. by L3 R
8001: LTE • LTE9: SerDiscarded SDUs will be excluded from the measurement.
The time ends at the first transmission of a TB containing a segment of the SDU.
8001: LTE • LTE9: SerDiscarded
The time endsSDUsat will
the be
firstexcluded from of
transmission thea measurement.
TB containing a segment of the SDU.
8001: LTE • LTE496: The
Discarded SDUs
time ends at will
the be
firstexcluded from of
transmission thea measurement.
TB containing a segment of the SDU.
8001: LTE • LTE496: The
Discarded SDUs
time ends at will
the be
firstexcluded from of
transmission thea measurement.
TB containing a segment of the SDU.
8001: LTE • LTE496: Discarded SDUs will be excluded from the measurement.
8001: LTE • LTE44: 6 This counter is updated when 1st transmission on PUSCH using MCS25 is received.
8001: LTE • LTE44: 6 This counter is updated when 1st transmission on PUSCH using MCS26 is received.
8001: LTE • LTE44: 6 This counter is updated when 1st transmission on PUSCH using MCS27 is received.
8001: LTE • LTE44: 6 This counter is updated when 1st transmission on PUSCH using MCS28 is received.
8001: LTE • LTE44: 6 This counter is updated when 1st transmission on PUSCH using MCS25 is nacked.
8001: LTE • LTE44: 6 This counter is updated when 1st transmission on PUSCH using MCS26 is nacked.
8001: LTE • LTE44: 6 This counter is updated when 1st transmission on PUSCH using MCS27 is nacked.
8001: LTE • LTE44: 6 The
This reception
counter isofupdated whenRA
a dedicated 1stpreamble
transmission
sentonbyPUSCH
the UE tousing
the MCS28
eNB. is nacked.
8001: LTE • LTE651: (cf. 3GPP TS 36.300)
8001: LTE • LTE44: 6 This counter is updated when the maximum number of HARQ retransmissions was exceeded
8001: LTE • LTE44: 6 This counter is updated when the maximum number of HARQ retransmissions was exceeded
8001: LTE • LTE44: 6 This counter is updated when the maximum number of HARQ retransmissions was exceeded
8001: LTE • LTE44: 6 This
- Thecounter is for
UL grant updated when the
RA msg3/1st maximumUL
scheduled number of HARQ
transmission retransmissions
after was exceeded
RA response/msg2;or
8001: LTE Cell Load - The UL grant for SR if a UL SRB message is expected.
8001: LTE Cell Load This counter is incremented by 1 in each TTI when the eNB is "on air" in uplink.
8001: LTE Cell Load This counter is updated in each TTI with the number of active UEs that had data scheduled in
8001: LTE Cell Load This counter is incremented by 1 in each TTI when the eNB is "on air" in downlink.
8001: LTE • LTE2023:The accumulation is started when the user plane enters Overload level 1 and it is stopped whe
8001: LTE • LTE9:
LTE2023:The
Serviceaccumulation
differentiationis started when the user plane enters Overload level 2 and it is stopped whe
8001: LTE • LTE2054:
LTE651: Performance is
This
Measurement
counter updated
Report addition
Monitoring when
I awith
PDCP PDCP
SDUKPIfor counter
a QCI 1subset
bearer is delivered to higher layers.
8001: LTE • LTE2054: This
Measurement
counter is updated
Report
LTE651: Performance Monitoring I addition
when awith
PDCP PDCP
SDU KPI
for counter
a QCI 2 subset
bearer is delivered to higher layers.
8001: LTE • LTE2054: This
Measurement
counter is updated
Report
LTE651: Performance Monitoring I addition
when awith
PDCP PDCP
SDU KPI
for counter
a QCI 3 subset
bearer is delivered to higher layers.
8001: LTE • LTE2054:The
This
Measurement
counter
time is at
ends updated
Report addition
the firstwhen awith
PDCP
transmissionPDCP
SDU
of a KPI
forcontaining
TB counter
a QCI 4subset
bearer is delivered
a segment to higher layers.
of the SDU.
8001: LTE Cell Load The
Discarded SDUs
time ends at will
the be
firstexcluded from of
transmission thea measurement.
TB containing a segment of the SDU.
8001: LTE Cell Load The
Discarded SDUs
time ends at will
the be
firstexcluded from of
transmission thea measurement.
TB containing a segment of the SDU.
8001: LTE Cell Load The
Discarded SDUs
time ends at will
the be
firstexcluded from of
transmission thea measurement.
TB containing a segment of the SDU.
8001: LTE Cell Load The
Discarded SDUs
time ends at will
the be
firstexcluded from of
transmission thea measurement.
TB containing a segment of the SDU.
8001: LTE •Cell Load
LTE9: Discarded
Service SDUs will be excluded from the measurement.
differentiation
8001: LTE • LTE2054: The
Measurement
number
LTE496: Support of transmitted
of QCI Report
2, 3 andaddition
4 PDCP with
SDUs
PDCPin downlink
KPI counterfor subset
QCI 1
8001: LTE • LTE2054: This
Measurement
counter is updated
Report
LTE496: Support of QCI 2, 3 and 4 addition
when awith
PDCP PDCP
SDU KPI
of a
counter
QCI2 bearer
subset is sent to the UE.
8001: LTE • LTE496: This
LTE2054:Supportcounter
Measurement is updated
of QCI Report when
2, 3 andaddition
4 awith PDCP KPI counter subsetis sent to the UE.
PDCP SDU of a QCI3 bearer
8001: LTE • LTE2054:This
Measurement
counter is updated
Report addition
when awithPDCP PDCP
SDUKPIof acounter
QCI4 bearer
subsetis sent to the UE.
8001: LTE Cell Load This counter is updated after each sampling interval with the sample taken from the number of
8001: LTE Cell Load This counter is updated by value 1 when the number of RRC Connected UEs is summed to co
8001: LTE Cell Load This counter is updated after each sampling interval with the sample taken from the number of
8001: LTE Cell Load This counter is updated by value 1 when the number of Active UEs is summed to counter SUM
8001: LTE • LTE9:
LTE1788:The
Serviceaccumulation
differentiationis started when the broadcast of the automatic Access Class Barring informa
8001: LTE • LTE496: This counter
LTE2054:Support
Measurement is updated
of QCI Report when
2, 3 andaddition
4 awith
PDCP SDUKPI
PDCP of acounter
QCI1 bearer
subsetis removed from the eNB withou
8001: LTE • LTE496:
LTE2054:Support
This
Measurement
counter is updated
of QCI Report
2, 3 andaddition
when
4 awith
PDCPPDCP
SDUKPI
of acounter
QCI2 bearer
subsetis removed from the eNB withou
8001: LTE • LTE496:
LTE2054:Support
This
Measurement
counter is updated
of QCI Report
2, 3 andaddition
when
4 awith
PDCPPDCP
SDUKPI
of acounter
QCI3 bearer
subsetis removed from the eNB withou
8001: LTE • LTE2054:This
Measurement
counter is updated
Report addition
when awith
PDCPPDCP
SDUKPI
of acounter
QCI4 bearer
subsetis removed from the eNB withou
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: B
The counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE770: BThe counter is updated in each TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE10:
LTE770:EPS
B
Thebearers
counterforis updated in eachvoice
conversational TTI scheduling period when bundle NACK received on PDSCH
8001: LTE • LTE496:
LTE10: EPS bearers for conversational voice of samples taken from the number of UE contexts with bu
Support
The value
of is
QCI
the2,
arithmetical
3 and 4 average
8001: LTE • LTE496: Support
The value
of is
QCI
the2,arithmetical
3 and 4 average of samples taken from the number of UE contexts with bu
8001: LTE • LTE473: Transmission of a PDCCH order (eNB -> UE; 3GPP TS 36.321, TS 36.212) to initiate a UE Ra
8001: LTE • LTE473: Transmission of an initial PDCCH order (eNB -> UE; 3GPP TS 36.321, TS 36.212) to initiate a
8001: LTE • LTE473: The counter is updated when the Random Access Response (eNB -> UE; 3GPP TS 36.300) w
her a dedicated pre 8001: LTE • LTE473: eNB-internal trigger
8001: LTE • LTE473: eNB-internal trigger
8001: LTE • LTE473: eNB-internal trigger
8001: LTE • LTE473: eNB-internal trigger
8001: LTE • LTE473: eNB-internal average calculation of the number of UEs in Uplink-In-Sync; the average is calcul
P TS 36.331, TS 36.306),
8001:
thaLTE • LTE473: eNB-internal
This counter isaverage
updated calculation
when theof the number
measured of RRC connected
Uplink-Out-Of-Sync UEs
time which
T of a UEhave
wasset the ran
in the "de
8001: LTE • LTE473: 0 seconds < T <= 0.5 seconds.
This counter is updated when the measured Uplink-Out-Of-Sync time T of a UE was in the ran
8001: LTE • LTE473: 0.5
Thisseconds
counter <is Tupdated
<= 2.5 seconds.
when the measured Uplink-Out-Of-Sync time T of a UE was in the ran
8001: LTE • LTE473: 2.5 seconds < T <= 10 seconds.
This counter is updated when the measured Uplink-Out-Of-Sync time T of a UE was in the ran
8001: LTE • LTE473: 10 seconds < T <= 100 seconds.
8001: LTE • LTE473: This counter is updated when the measured Uplink-Out-Of-Sync time T of a UE was larger tha
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is received for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: When 1st transmission on PUSCH is nacked for used MCS
8001: LTE • LTE829: This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE829: This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE829: This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE829: This counter is updated when the maximum number of HARQ retransmissions has been excee
8001: LTE • LTE1089:
LTE569: eNB-internal average
Downlink carrier calculation of the number of active UEs with UE Category 5 (3GPP TS 3
aggregation
8001: LTE • LTE1089:
LTE1558:The
TDDcounter is updated
Downlink
Downlink carriercarrier by the arithmetical average of samples taken from the number of UEs
aggregation
aggregation
8001: LTE • LTE1089:
LTE1558:The
TDDarithmetical
Downlink
Downlink carriercarrier
averageaggregation
of samples taken from the number of UEs with a configured SCell.
aggregation
8001: LTE • LTE1803:
LTE1558:The
TDDarithmetical
Downlink
Downlink carriercarrier
averageaggregation
of samples
aggregation 3 CC - taken from the number of UEs with an activated SCell.
40 MHz
8001: LTE • LTE1836:The
TDD counter
downlink
is updated
carrier aggregation
by the arithmetical
- 60
LTE1803: Downlink carrier aggregation 3 CC - 40 MHz Mhzaverage of samples taken from the number of UEs
8001: LTE • LTE1836:This
TDD counter
downlinkis updated
carrier by the arithmetical
aggregation - 60
LTE1803: Downlink carrier aggregation 3 CC - 40 MHz Mhzaverage of samples taken from the number of UEs
8001: LTE • LTE1836:The
TDDarithmetical
downlink carrier
averageaggregation
of samples - 60
taken
Mhzfrom the number of UEs with two activated SCells.
8001: LTE • LTE1929:The counter is updated when first HARQ transmission on PUSCH is received for periodical res
8001: LTE • LTE1929:The counter is updated when first HARQ transmission on PUSCH is negatively acknowledged
8004: LTE • LTE770: B
This counter is updated when an X2AP message has been received from any source eNB.
8004: LTE • LTE770: B
This counter is updated when an X2AP message is transmitted towards any target eNB.
8004: LTE • LTE770: B
This counter is updated on the reception of an DL Data Forwarding GTP-U: G-PDU from any s
8004: LTE • LTE770: B
This counter is updated on the transmission of DL Data Forwarding GTP-U: G-PDU towards an
8005: LTE • LTE651: The counter is updated when the UE-related RSSI for PUCCH minimum value is detected
8005: LTE • LTE651: The counter is updated when the UE-related RSSI for PUCCH maximum value is detected
8005: LTE • LTE651: The counter is updated with the average value of the UE-related RSSI for PUCCH over the me
8005: LTE • LTE651: The counter is updated when the UE-related RSSI for PUSCH minimum value is detected
8005: LTE • LTE651: The counter is updated when the UE-related RSSI for PUSCH maximum value is detected
8005: LTE • LTE651: The counter is updated with the average value of UE-related RSSI for PUSCH over the measu
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value <= -120 dBm is detected.
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -120 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -118 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -116 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -114 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -112 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -110 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -108 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -106 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -104 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -102 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -100 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -98 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -96 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -94 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -92 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -90 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -88 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -86 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -84 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of -82 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUCCH value in the range of RssiPucchU
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value <= -120 dBm is detected.
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -120 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -118 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -116 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -114 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -112 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -110 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -108 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -106 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -104 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -102 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -100 dBm <
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -98 dBm < R
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -96 dBm < R
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -94 dBm < R
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -92 dBm < R
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -90 dBm < R
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -88 dBm < R
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -86 dBm < R
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -84 dBm < R
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of -82 dBm < R
8005: LTE • LTE798: The counter is updated when a UE-related RSSI for PUSCH value in the range of RssiPUSCH
8005: LTE • LTE798: When UE Power Headroom value in the range of -23dB <= PHR < -21dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -21dB <= PHR < -19dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -19dB <= PHR < -17dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -17dB <= PHR < -15dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -15dB <= PHR < -13dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -13dB <= PHR < -11dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -11dB <= PHR < -9dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -9dB <= PHR < -7dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -7dB <= PHR < -5dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -5dB <= PHR < -3dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -3dB <= PHR < -1dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of -1dB <= PHR < 1dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 1dB <= PHR < 3dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 3dB <= PHR < 5dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 5dB <= PHR < 7dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 7dB <= PHR < 9dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 9dB <= PHR < 11dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 11dB <= PHR < 13dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 13dB <= PHR < 15dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 15dB <= PHR < 17dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 17dB <= PHR < 19dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 19dB <= PHR < 21dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 21dB <= PHR < 23dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 23dB <= PHR < 25dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 25dB <= PHR < 27dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 27dB <= PHR < 29dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 29dB <= PHR < 31dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 31dB <= PHR < 33dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 33dB <= PHR < 35dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 35dB <= PHR < 37dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 37dB <= PHR < 39dB is detected.
8005: LTE • LTE798: When UE Power Headroom value in the range of 39 dB <= PHR is detected.
8005: LTE • LTE651: When the minimum UE power headroom value is detected.
8005: LTE • LTE651: When the maximum UE power headroom value is detected.
8005: LTE • LTE651: Updated for each TTI.
8005: LTE • LTE651: The counter is updated when the signal-to-interference-and-noise ratio (SINR) minimum value
8005: LTE • LTE651: The counter is updated when the signal-to-interference-and-noise ratio (SINR) maximum value
8005: LTE • LTE651: The counter is updated with the average value of signal-to-interference-and-noise ratio (SINR)
8005: LTE • LTE651: The counter is updated when the signal-to-interference-and-noise ratio (SINR) minimum value
8005: LTE • LTE651: The counter is updated when the signal-to-interference-and-noise ratio (SINR) maximum value
8005: LTE • LTE651: The counter is updated with the average value of signal-to-interference-and-noise ratio (SINR)
8005: LTE • LTE798: When SINR PUCCH value in the range of <= -10dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of -10dB < SINR <= -8dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of -8dB < SINR <= -6dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of -6dB < SINR <= -4dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of -4dB < SINR <= -2dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of -2dB < SINR <= 0dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 0dB < SINR <= 2dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 2dB < SINR <= 4dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 4dB < SINR <= 6dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 4dB < SINR <= 6dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 8dB < SINR <= 10dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 10dB < SINR <= 12dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 12dB < SINR <= 14dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 14dB < SINR <= 16dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 16dB < SINR <= 18dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 18dB < SINR <= 20dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 20dB < SINR <= 22dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 22dB < SINR <= 24dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 24dB < SINR <= 26dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 26dB < SINR <= 28dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of 28dB < SINR <= 30dB is detected
8005: LTE • LTE798: When SINR PUCCH value in the range of > 30dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of <= -10dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of -10dB < SINR <= -8dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of -8dB < SINR <= -6dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of -6dB < SINR <= -4dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of -4dB < SINR <= -2dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of -2dB < SINR <= 0dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 0dB < SINR <= 2dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 2dB < SINR <= 4dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 4dB < SINR <= 6dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 6dB < SINR <= 8dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 8dB < SINR <= 10dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 10dB < SINR <= 12dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 12dB < SINR <= 14dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 14dB < SINR <= 16dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 16dB < SINR <= 18dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 18dB < SINR <= 20dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 20dB < SINR <= 22dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 22dB < SINR <= 24dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 24dB < SINR <= 26dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 26dB < SINR <= 28dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of 28dB < SINR <= 30dB is detected
8005: LTE • LTE798: When SINR PUSCH value in the range of > 30dB is detected
8005: LTE • LTE770: B
This counter is updated every time UL AMC recommended MCS is upgraded. Both Outer Loop
8005: LTE • LTE770: B
This counter is updated every time UL AMC recommended MCS is downgraded. Both Outer L
8005: LTE Power andThis counter is updated if the current cell-wide RSSI value on PUCCH is smaller than the last c
8005: LTE Power andThis counter is updated if the current cell-wide RSSI value on PUCCH is greater than the last c
8005: LTE Power andThe counter is updated after every TTI. Mean value is calculated as follows: conversion from d
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is <= -120 dBm.
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -120 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -118 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -116 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -114 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -112 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -110 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -108 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -106 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -104 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -102 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -100 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -98 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -96 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -94 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -92 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -90 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -88 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -86 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -84 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is -82 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUCCH is greater than -8
8005: LTE Power andThis counter is updated if the current cell-wide RSSI value on PUSCH is smaller than the last c
8005: LTE Power andThis counter is updated if the current cell-wide RSSI value on PUSCH is greater than the last c
8005: LTE Power andThe counter is updated after every TTI. Mean value is calculated as follows: conversion from d
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is <= -120 dBm.
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -120 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -118 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -116 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -114 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -112 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -110 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -108 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -106 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -104 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -102 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -100 dBm < x
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -98 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -96 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -94 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -92 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -90 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -88 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -86 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -84 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is -82 dBm < x <
8005: LTE Power andThe counter is updated after every TTI if the cell-wide RSSI value on PUSCH is greater than -8
8005: LTE Power andThis counter is updated if the current cell-wide SINR value on PUCCH is smaller than the last c
8005: LTE Power andThis counter is updated if the current cell-wide SINR value on PUCCH is greater than the last c
8005: LTE Power andThe counter is updated after every TTI. Mean value is calculated as follows: SINR mean value
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is <= -10 dB.
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is -10 dB < x <=
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is -8 dB < x <= -
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is -6 dB < x <= -
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is -4 dB < x <= -
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is -2 dB < x <= 0
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 0 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 2 dB < x <= 4
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 4 dB < x <= 6
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 6 dB < x <= 8
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 8 dB < x <= 10
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 10 dB < x <= 1
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 12 dB < x <= 1
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 14 dB < x <= 1
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 16 dB < x <= 1
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 18 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 20 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 22 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 24dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 26 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is 28 dB < x <= 3
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUCCH is greater than 3
8005: LTE Power andThis counter is updated if the current cell-wide SINR value on PUSCH is smaller than the last c
8005: LTE Power andThis counter is updated if the current cell-wide SINR value on PUSCH is greater than the last c
8005: LTE Power andThe counter is updated after every TTI. Mean value is calculated as follows: SINR mean value
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is <= -10 dB.
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is -10 dB < x <=
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is -8 dB < x <= -6
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is -6 dB < x <= -4
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is -4 dB < x <= -2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is -2 dB < x <= 0
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 0 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 2 dB < x <= 4
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 4 dB < x <= 6
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 6 dB < x <= 8
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 8 dB < x <= 10
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 10 dB < x <= 1
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 12 dB < x <= 1
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 14 dB < x <= 1
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 16 dB < x <= 1
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 18 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 20 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 22 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 24 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 26 dB < x <= 2
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is 28 dB < x <= 3
8005: LTE Power andThe counter is updated after every TTI if the cell-wide SINR value on PUSCH is greater than 3
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 1 from e
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 2 from e
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 3 from e
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 4 from e
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 5 from e
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 6 from e
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 7 from e
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 8 from e
8005: LTE • LTE1491:This measurement is updated by collecting the individual antenna RTWP values in milliwatts e
8005: LTE • LTE1491:This measurement is updated by calculating the IoT every sample period the noise measurem
8005: LTE • LTE1491:This measurement is updated by calculating the IoT every sample period the noise measurem
8005: LTE • LTE1491:This measurement is updated by calculating the IoT every sample period the noise measurem
8005: LTE • LTE1491:This measurement is updated by calculating the IoT every sample period the noise measurem
8005: LTE • LTE1491:This measurement is updated by calculating the IoT every sample period the noise measurem
8005: LTE • LTE1491:This measurement is updated by calculating the IoT every sample period the noise measurem
8005: LTE • LTE1491:This measurement is updated by calculating the IoT every sample period the noise measurem
8005: LTE • LTE1491:This measurement is updated by calculating the IoT every sample period the noise measurem
8005: LTE • LTE1491:This measurement is updated by calculating the IoT every sample period the noise measurem
8005: LTE • LTE1491:This measurement is updated by calculating the SIR for each of the in-use PUSCH PRBs ever
8005: LTE • LTE1491:This measurement is updated by calculating the SIR for each of the in-use PUSCH PRBs ever
8005: LTE • LTE1491:This measurement is updated by calculating the SIR for each of the in-use PUSCH PRBs ever
8005: LTE • LTE1491:This measurement is updated by calculating the SIR for each of the in-use PUSCH PRBs ever
8005: LTE • LTE1491:This measurement is updated by calculating the SIR for each of the in-use PUSCH PRBs ever
8005: LTE • LTE1491:This measurement is updated by calculating the SIR for each of the in-use PUSCH PRBs ever
8005: LTE • LTE1491:This measurement is updated by calculating the SIR for each of the in-use PUSCH PRBs ever
8005: LTE • LTE1491:This measurement is updated by calculating the SIR for each of the in-use PUSCH PRBs ever
8005: LTE • LTE1491:This measurement is updated by calculating the SIR for each of the in-use PUSCH PRBs ever
8005: LTE • LTE1491:This measurement is updated by calculating the SIR for each of the in-use PUSCH PRBs ever
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 9 from e
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 10 from
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 11 from
8005: LTE • LTE1491:This measurement is updated by accumulating the RTWP in milliwatts for Rx antenna 12 from
8006: LTE • LTE651: The reception of an S1AP:Initial Context Setup Request or an S1AP:E-RAB SETUP REQUES
8006: LTE • LTE651: The transmission of an S1AP:Initial Context Setup Response or an S1AP:E-RAB SETUP RES
8006: LTE • LTE651: Reception of an S1AP:E-RAB RELEASE COMMAND or an S1AP:UE CONTEXT RELEASE C
8006: LTE • LTE651: Reception of an S1AP:E-RAB RELEASE COMMAND or an S1AP:UE CONTEXT RELEASE C
8006: LTE • LTE651: Reception of an S1AP:E-RAB RELEASE COMMAND or an S1AP:UE CONTEXT RELEASE C
8006: LTE • LTE761:
LTE651: Advanced
The counter is updated
target if the release
cell selection and HOcause does
retry for not freq
intra- match
HOany other failure counter.
8006: LTE • LTE1899:This
Dedicated
counterPM-counters
is updated following
for E-RAB
theManagement
transmissionfailure
of an S1AP:UE
causes CONTEXT RELEASE REQ
8006: LTE • LTE1361:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI 1 ch
8006: LTE • LTE1361:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI 2 ch
8006: LTE • LTE1361:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI 3 ch
8006: LTE • LTE1361:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI 4 ch
8006: LTE • LTE1361:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI 5 ch
8006: LTE • LTE1361:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI 6 ch
8006: LTE • LTE1361:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI 7 ch
8006: LTE • LTE1361:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI 8 ch
8006: LTE • LTE1361:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI 9 ch
8006: LTE • LTE1361:This counter is incremented when the check for the respective sampling counters for the numb
8006: LTE • LTE1740:Reception of an S1AP:E-RAB MODIFY REQUEST message sent by MME to the eNB. The co
8006: LTE • LTE1740:Reception of an S1AP:E-RAB MODIFY REQUEST message sent by MME to the eNB. The co
8006: LTE • LTE1740:Reception of an S1AP:E-RAB MODIFY REQUEST message sent by MME to the eNB. The co
8006: LTE • LTE1740:Reception of an S1AP:E-RAB MODIFY REQUEST message sent by MME to the eNB. The co
8006: LTE • LTE1740:Reception of an S1AP:E-RAB MODIFY REQUEST message sent by MME to the eNB. The co
8006: LTE • LTE1740:Reception of an S1AP:E-RAB MODIFY REQUEST message sent by MME to the eNB. The co
8006: LTE • LTE1740:Reception of an S1AP:E-RAB MODIFY REQUEST message sent by MME to the eNB. The co
8006: LTE • LTE1740:Reception of an S1AP:E-RAB MODIFY REQUEST message sent by MME to the eNB. The co
8006: LTE • LTE1740:Reception of an S1AP:E-RAB MODIFY REQUEST message sent by MME to the eNB. The co
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
8006: LTE • LTE1740:Transmission of an S1AP:E-RAB MODIFY RESPONSE message sent by eNB to the MME. Th
• LTE9: Service differentiation
8006: LTE • LTE7:
LTE9: Support
The reception
Service of multiple
of EPS
an S1AP:E-RAB
differentiation bearer Release Command or an S1AP:UE Context Release Comm
8006: LTE • LTE7: Support
The reception
of multiple
of EPS
an
LTE9: Service differentiation S1AP:E-RAB
bearer Release Command or an S1AP:UE Context Release Comm
8006: LTE • LTE9:
LTE7: Service
Support
The reception
of multiple
of EPS
an S1AP:E-RAB
differentiation bearer Release Command or an S1AP:UE Context Release Comm
8006: LTE • LTE7: Support
The reception of EPS
of multiple an S1AP:E-RAB
bearer Release Command or an S1AP:UE Context Release Comm
8006: LTE • LTE1899:This
Dedicated
counterPM-counters
is updated following
for E-RABtheManagement
transmissionfailure
of an S1AP:UE
causes CONTEXT RELEASE REQ
8006: LTE • LTE651: The counters must be updated in case that user data are buffered (UL/DL) for an E-RAB with Q
8006: LTE • LTE651: The counters must be updated in case that user data are buffered (UL/DL) for an E-RAB with Q
8006: LTE • LTE651: The counters must be updated in case that user data are buffered (UL/DL) for an E-RAB with Q
8006: LTE • LTE651: The counters must be updated in case that user data are buffered (UL/DL) for an E-RAB with Q
8006: LTE • LTE651: The counters must be updated in case that user data are buffered (UL/DL) for an E-RAB with n
8006: LTE • LTE651: When user data are transferred the in-session activity time is aggregated during the E-RAB life
8006: LTE • LTE651: When user data are transferred the in-session activity time is aggregated during the E-RAB life
8006: LTE • LTE651: When user data are transferred the in-session activity time is aggregated during the E-RAB life
8006: LTE • LTE651: When user data are transferred the in-session activity time is aggregated during the E-RAB life
8006: LTE • LTE651: When user data are transferred the in-session activity time is aggregated during the E-RAB life
8006: LTE • LTE1074:The reception of an S1AP:INITIAL CONTEXT SETUP message or of an S1AP:E-RAB SETUP
8006: LTE • LTE1074:The transmission of the S1AP:E-RAB SETUP RESPONSE or S1AP:INITIAL CONTEXT RESP
8006: LTE EPS BeareReception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to th
8006: LTE EPS BeareReception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to th
8006: LTE EPS BeareReception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to th
8006: LTE EPS BeareReception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to th
8006: LTE • LTE1960:Reception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to th
8006: LTE • LTE1960:Reception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to th
8006: LTE • LTE1960:Reception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to th
8006: LTE • LTE1960:Reception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to th
8006: LTE • LTE1960:Reception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by the MME to th
8006: LTE EPS BeareReception of an S1AP:E-RAB SETUP REQUEST message sent by the MME to the eNB. The
8006: LTE EPS BeareReception of an S1AP:E-RAB SETUP REQUEST message sent by the MME to the eNB. The
8006: LTE EPS BeareReception of an S1AP:E-RAB SETUP REQUEST message sent by the MME to the eNB. The
8006: LTE EPS BeareReception of an S1AP:E-RAB SETUP REQUEST message sent by the MME to the eNB. The
8006: LTE • LTE1960:Reception of an S1AP:E-RAB SETUP REQUEST message sent by the MME to the eNB. The
8006: LTE • LTE1960:Reception of an S1AP:E-RAB SETUP REQUEST message sent by the MME to the eNB. The
8006: LTE • LTE1960:Reception of an S1AP:E-RAB SETUP REQUEST message sent by the MME to the eNB. The
8006: LTE • LTE1960:Reception of an S1AP:E-RAB SETUP REQUEST message sent by the MME to the eNB. The
8006: LTE • LTE1960:Reception
Transmissionof an
of S1AP:E-RAB SETUP
an S1AP:INITIAL REQUEST
CONTEXT message
SETUP sent bymessage
RESPONSE the MME sent
to the
byeNB.
eNB The
to th
8006: LTE EPS BeareThe
Transmission of an S1AP:INITIAL CONTEXT SETUP RESPONSE message sent by eNBList"
counter is updated with the number of QCI1 bearers contained in the "E-RAB Setup to thI
8006: LTE EPS BeareTransmission
The counter isofupdated with the number
an S1AP:INITIAL of QCI2
CONTEXT bearers
SETUP contained message
RESPONSE in the "E-RAB Setup
sent by eNBList"
to thI
8006: LTE EPS BeareTransmission
The counter isofupdated with the number
an S1AP:INITIAL of QCI3
CONTEXT bearers
SETUP contained message
RESPONSE in the "E-RAB Setup
sent by eNBList"
to thI
8006: LTE EPS BeareTransmission
The counter isofupdated with the number
an S1AP:INITIAL of QCI4
CONTEXT bearers
SETUP contained message
RESPONSE in the "E-RAB Setup
sent by eNBList"
to thI
8006: LTE • LTE1960:Transmission
The counter isofupdated with the number
an S1AP:INITIAL of QCI5
CONTEXT bearers
SETUP contained message
RESPONSE in the "E-RAB Setup
sent by eNBList"
to thI
8006: LTE • LTE1960:Transmission
The counter isofupdated with the number
an S1AP:INITIAL of QCI6
CONTEXT bearers
SETUP contained message
RESPONSE in the "E-RAB Setup
sent by eNBList"
to thI
8006: LTE • LTE1960:The
Transmission of an S1AP:INITIAL CONTEXT SETUP RESPONSE message sent by eNB to thI
counter is updated with the number of QCI7 bearers contained in the "E-RAB Setup List"
8006: LTE • LTE1960:The counter isofupdated
Transmission with the number
an S1AP:INITIAL of QCI8
CONTEXT bearers
SETUP contained message
RESPONSE in the "E-RAB Setup
sent by eNBList"
to thI
8006: LTE • LTE1960:The counter is updated with the number of QCI9 bearers contained in the "E-RAB Setup List" I
8006: LTE EPS BeareTransmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The
8006: LTE EPS BeareTransmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The
8006: LTE EPS BeareTransmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The
8006: LTE EPS BeareTransmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The
8006: LTE • LTE1960:Transmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The
8006: LTE • LTE1960:Transmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The
8006: LTE • LTE1960:Transmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The
8006: LTE • LTE1960:Transmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The
8006: LTE • LTE1960:Transmission of an S1AP:E-RAB SETUP RESPONSE message sent by eNB to the MME. The
8006: LTE • LTE1960:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI1 cha
8006: LTE • LTE1960:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI2 cha
8006: LTE • LTE1960:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI3 cha
8006: LTE • LTE1960:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI4 cha
8006: LTE • LTE1960:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI5 cha
8006: LTE • LTE1960:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI6 cha
8006: LTE • LTE1960:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI7 cha
8006: LTE • LTE1960:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI8 cha
8006: LTE • LTE1960:This measurement is obtained by sampling the number of simultaneous E-RABs with QCI9 cha
8006: LTE • LTE1042:The counter is updated by the arithmetic mean of the samples at the pre-defined interval (1 se
8006: LTE • LTE1042:The counter is updated by the arithmetic mean of the samples at the pre-defined interval (1 se
8006: LTE • LTE1042:The counter is updated by the arithmetic mean of the samples at the pre-defined interval (1 se
8006: LTE • LTE1042:The counter is updated by the arithmetic mean of the samples at the pre-defined interval (1 se
8006: LTE • LTE1321:This counter is updated following the transmission of an S1AP:E-RAB MODIFY RESPONSE m
8006: LTE • LTE1321:This counter is updated following the transmission of an S1AP:E-RAB MODIFY RESPONSE m
8006: LTE • LTE2175:The counter is updated in case that user data are buffered (UL/DL) for an E-RAB with QCI5 ch
8006: LTE • LTE2175:The counter is updated in case that user data are buffered (UL/DL) for an E-RAB with QCI6 ch
8006: LTE • LTE2175:The counter is updated in case that user data are buffered (UL/DL) for an E-RAB with QCI7 ch
8006: LTE • LTE2175:The counter is updated in case that user data are buffered (UL/DL) for an E-RAB with QCI8 ch
8006: LTE • LTE2175:The counter is CONTEXT
S1AP:INITIAL updated in SETUP
case thatFAILURE:
user data are buffered (UL/DL) for an E-RAB with QCI9 ch
8006: LTE • LTE1899:This
The counter
counter is
is incremented by thethe
updated following number of bearers
transmission contained
of an in the "E-RAB
S1AP:INITIAL CONTEXT to Be SetupFAI
SETUP Lis
8006: LTE • LTE1899:This
The counter
counter is
is incremented by thethe
updated following number of bearers
transmission contained
of an in the "E-RAB
S1AP:INITIAL CONTEXT to Be SetupFAI
SETUP Lis
8006: LTE • LTE1899:This
The counter
counter is
is incremented by thethe
updated following number of bearers
transmission contained
of an in the "E-RAB
S1AP:INITIAL CONTEXT to Be SetupFAI
SETUP Lis
8006: LTE • LTE1899:The counter is incremented by the number of bearers contained in the "E-RAB to Be Setup Lis
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:E-RAB SETUP RESPONSE me
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:E-RAB SETUP RESPONSE m
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:E-RAB SETUP RESPONSE me
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:E-RAB SETUP RESPONSE me
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:E-RAB SETUP RESPONSE me
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:E-RAB SETUP RESPONSE me
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP: E-RAB RELEASE INDICATION
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:UE CONTEXT RELEASE REQ
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:UE CONTEXT RELEASE REQ
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:E-RAB RELEASE INDICATION
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:UE CONTEXT RELEASE REQ
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:UE CONTEXT RELEASE REQ
8006: LTE • LTE1899:This counter
Inter-eNB HOisvia updated following the
S1/Inter-system HOtransmission of an S1AP:E-RAB
to UTRAN/SRVCC to UTRAN/SRVCCRELEASE INDICATION
to GSM:
ot admitted by the HO targ
8006: LTE • LTE1899:Inter-eNB
Following the
HO reception of the S1AP:UE
via S1/Inter-system HO to CONTEXT
UTRAN/SRVCCRELEASE COMMAND message
to UTRAN/SRVCC to GSM:with the c
8006: LTE • LTE1899:Inter-eNB
The counter
HOisviaincremented with the
S1/Inter-system HOnumber of bearers admitted
to UTRAN/SRVCC by the HO target
to UTRAN/SRVCC to GSM:during the p
8006: LTE • LTE1899:Inter-eNB
Following the
HO reception of the S1AP:UE
via S1/Inter-system HO to CONTEXT
UTRAN/SRVCCRELEASE COMMAND message
to UTRAN/SRVCC to GSM:with the c
8006: LTE • LTE1899:Upon the transmission of the S1AP:UE CONTEXT RELEASE REQUEST message to the MME
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:E-RAB RELEASE RESPONSE
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:E-RAB RELEASE INDICATION
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:UE CONTEXT RELEASE REQ
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:UE CONTEXT RELEASE REQ
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:E-RAB RELEASE INDICATION
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:UE CONTEXT RELEASE REQ
8006: LTE • LTE1899:This counter is updated following the transmission of an S1AP:UE CONTEXT RELEASE REQ
8006: LTE • LTE1899:This counter
Inter-eNB HOisvia updated following the
S1/Inter-system HOtransmission of an S1AP:E-RAB
to UTRAN/SRVCC RELEASE
to UTRAN /SRVCC INDICATION
to GSM:
1 E-RABs not admitted 8006:
by LTE • LTE1899:Inter-eNB
Following the
HO reception of the S1AP:UE
via S1/Inter-system HO to CONTEXT
UTRAN/SRVCCRELEASE COMMAND message
to UTRAN/SRVCC to GSM:with the c
8006: LTE • LTE1899:Inter-eNB
The counter
HOisviaincremented with the
S1/Inter-system HOnumber of QCI1 bearers
to UTRAN/SRVCC admitted by the to
to UTRAN/SRVCC target
GSM:eNB durin
8006: LTE • LTE1899:Following
Inter-eNB HO via S1/Inter-system HO to UTRAN/SRVCC to UTRAN/SRVCC to GSM:with the c
the reception of the S1AP:UE CONTEXT RELEASE COMMAND message
8006: LTE • LTE1899:Upon the transmission of the S1AP:UE CONTEXT RELEASE REQUEST message to the MME
8007: LTE • LTE651: 3GPP TS36.331 (RRC CONNECTION RECONFIGURATION)
8007: LTE • LTE651: 3GPP TS36.331 (RRC CONNECTION RECONFIGURATION COMPLETE)
8007: LTE • LTE651: RRC Guard Timer expirations of RRC Reconfiguration procedures for other purposes than DR
8007: LTE • LTE651: Transmission
This counter isofupdated
an RRCon CONNECTION RELEASE
the transmission message
of an RRC due to reception
CONNECTION SETUPofmessage
S1AP:UE CO
sent
8007: LTE • LTE770: B
Note: If a UE (erroneously) sends RRC CONNECTION REQUEST message several times in a
8007: LTE • LTE770: B
This counter is updated on the reception of an RRC CONNECTION SETUP COMPLETE mess
8007: LTE • LTE770: B
This counter is updated upon the expiration of the RRC Guard Timer used for the supervision o
8007: LTE • LTE770: B
This counter is updated at the transmission of an RRC CONNECTION RECONFIGURATION m
8007: LTE • LTE770: B
This counter is updated at the reception of an RRC CONNECTION RECONFIGURATION COM
8007: LTE • LTE770: B
Also the expiration during bearer setup due to incoming HO will not be counted.
Note:
8007: LTE • LTE1935:The
Note:measurement is initialized with "0" at the beginning of each granularity period. A measurem
8007: LTE • LTE1935:The measurement is initialized with "0" at the beginning of each granularity period. A measurem
8008: LTE • LTE651: The transmission of an RRC Connection Re-establishment Reject message, sent by the eNB t
8008: LTE • LTE770: B
Updated
This for each
counter pagingwhen
is updated record
theofmaximum
an RRC paging
numbermessage
of paging(excluding
records ispure SysInfo
reached message
for the next p
8008: LTE • LTE770: B
=> UU (RRC allows up to 16 paging records per paging occasion)
8008: LTE • LTE770: B
Transmission of an RRC: Paging message sent by eNB to UE.
8008: LTE • LTE735: This counter is updated following the reception of an RRC: RRCConnectionReestablishmentR
8008: LTE • LTE735: This counter is updated following the reception of an RRC: RRCConnectionReestablishmentC
8008: LTE • LTE735: Updated when an RRCConnectionReestablishmentRequest message is received with cause "
8008: LTE • LTE735: Updated when an RRCConnectionReestablishmentComplete message is received in case tha
8008: LTE • LTE735: Updated when an RRCConnectionReestablishmentRequest message is received with cause "
8008: LTE • LTE735: including
Updated when an RRCConnectionReestablishmentComplete
'reportCGI' measurement configuration to the UE. message is received in case tha
8008: LTE • LTE782: Reception
- (3GPP TSof36.331)
RRC: Measurement Report message including a 'reportCGI' measurement result
8008: LTE • LTE782: - (3GPP TS 36.331)
8008: LTE • LTE908: Transmission of RRCConnectionReconfiguration message including a "reportCGI" measureme
8008: LTE • LTE908: Reception of RRC Measurement Report message including a "reportCGI" measurement result
8008: LTE • LTE908: Reception of RRC Measurement Report message including a "reportCGI" measurement result
8008: LTE • LTE494:
LTE1442:This counterMobile
Commercial
The counter is updated
is updated following
Alertwhen
System the transmission
a paging campaign forof the
an RRC Connection
broadcast Release message
of ETWS/CMAS (s
warning m
8008: LTE • LTE843: ETWS
Note
Note: that
broadcast
a paging campaign is not started, for example when the Warning Area List IE does n
8008: LTE • LTE1935:Note:
The measurement is initialized with "0" at the beginning of each granularity period. A measurem
8008: LTE • LTE1935:The measurement is initialized with "0" at the beginning of each granularity period. A measurem
8009: LTE • LTE651: The reception of an RRC Measurement Report message sent by the UE to eNB and of the RR
8009: LTE • LTE651: The reception of an RRC Measurement Report message sent by the UE to eNB and of an RRM
8009: LTE • LTE651: An internal eNB trigger. The eNB MM receives a list with the target cells from RRM and decide
8009: LTE • LTE651: An internal eNB trigger. The eNB MM receives a list with the target cells from the RRM. The M
8009: LTE • LTE651: An internal eNB trigger. The eNB MM receives a list with the target cells from RRM. The MM o
8009: LTE • LTE651: The transmission of an RRC Connection Reconfiguration message sent by the eNB to UE, wh
8009: LTE • LTE651: The reception of an internal UE Context Release Request for the handover on the source side
8009: LTE • LTE651: The counter is updated to the source cell when timer THOoverall expires.
8010: LTE • LTE798: The counter is updated when CQI value 0 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 1 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 2 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 3 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 4 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 5 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 6 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 7 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 8 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 9 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 10 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 11 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 12 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 13 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 14 is received from the UE.
8010: LTE • LTE798: The counter is updated when CQI value 15 is received from the UE.
8010: LTE • LTE651: The counter is updated when the minimum assumed CQI in LA process is obtained from CQI r
8010: LTE • LTE651: The counter is updated when the maximum assumed CQI in LA process is obtained from CQI
8010: LTE • LTE651: The counter is updated when the mean assumed CQI in LA process is obtained from CQI repo
8010: LTE • LTE770: B
The counter is updated when diversity MIMO mode is selected for the transmission. It counts t
8010: LTE • LTE703:
LTE770: Downlink
B
The counter is updated
adaptive when
closed loopspatial
MIMO multiplexing MIMO mode is selected for the transmission.
for two antennas
8010: LTE • LTE703:
LTE569: Downlink
The counter is updated
adaptive when
closed loopMIMO
SU MIMO
MIMO Closed4x4Loop
for two - TMSingle
4
antennas Codeword mapping to single layer mo
8010: LTE • LTE569: Downlink
The counter is updated
adaptive when
closed loopMIMO
SU MIMOClosed4x4Loop
- TMDouble
4 Codeword mapping to dual layers m
8010: LTE • LTE770: B
This counter is updated when MIMO mode control is changed between the diversity mode and
8010: LTE • LTE703: The counter is updated when MIMO mode control is changed between the single codeword mo
sources which are used8010: LTE • LTE1035:The counter is updated when PDCCH is allocated for PDSCH transmission.
ns by which the eNB i 8010: LTE • LTE1035:The counter is updated when DTX is received for PDSCH transmission.
8010: LTE • LTE541: The counter is incremented on each PDSCH transmission with dual stream beamforming mod
8010: LTE • LTE541: The counter is incremented on each PDSCH transmission with single stream beamforming mo
8010: LTE • LTE541: The counter is incremented on each PDSCH transmission with transmit diversity mode in TM8
8010: LTE • LTE1169:The counter is incremented on each PDSCH transmission with dual-user single-stream beamfo
8010: LTE • LTE1740:The counter is incremented on each PDSCH transmission in TM7 (single-stream beamforming
8010: LTE • LTE1740:The counter is incremented on each PDSCH transmission in TM7 (TxDiv mode).
8010: LTE • LTE1787:The counter is incremented on each PDSCH transmission with dual-user single-stream mode i
8010: LTE • LTE569: The counter is updated when MIMO Closed Loop Double Codeword mapping to 3-layer mode
8010: LTE • LTE569: The counter is updated when MIMO Closed Loop Double Codeword mapping to 4-layer mode
8010: LTE • LTE569: The counter is updated when MIMO Closed Loop Single Codeword mapping to 2-layer mode i
8010: LTE • LTE1491:This measurement calculates the estimated transmitted power (in milliwatts) every sample peri
8010: LTE • LTE1491:This measurement calculates the estimated transmitted power (in milliwatts) every sample peri
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 0 for codeword 1 is received by the eNB fr
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 1 for codeword 1 is received by the eNB fr
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 2 for codeword 1 is received by the eNB fr
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 3 for codeword 1 is received by the eNB fr
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 4 for codeword 1 is received by the eNB fr
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 5 for codeword 1 is received by the eNB fr
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 6 for codeword 1 is received by the eNB fr
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 7 for codeword 1 is received by the eNB fr
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 8 for codeword 1 is received by the eNB fr
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 9 for codeword 1 is received by the eNB fr
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 10 for codeword 1 is received by the eNB
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 11 for codeword 1 is received by the eNB
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 12 for codeword 1 is received by the eNB
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 13 for codeword 1 is received by the eNB
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 14 for codeword 1 is received by the eNB
8010: LTE • LTE2175:The counter is updated when a wideband CQI level 15 for codeword 1 is received by the eNB
8010: LTE • LTE569: This counter counts the time distribution in case TxDiv Fallback is activated (by default is yes).
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE651: Updated per TTI.
8011: LTE • LTE651: Updated per TTI.
8011: LTE • LTE651: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE798: Updated per TTI.
8011: LTE • LTE651: Updated when the minimum value of an allocated DL PRB is detected.
8011: LTE • LTE651: Updated when the maximum value of an allocated DL PRB is detected.
8011: LTE • LTE651: Updated with the average rate value of an allocated DL PRB over the measurement period.
8011: LTE • LTE805: P In PDCCH scheduling over the measurement period.
8011: LTE • LTE805: P When Aggregation Group1 is used for PDCCH scheduling.
8011: LTE • LTE805: P When Aggregation Group2 is used for PDCCH scheduling.
8011: LTE • LTE805: P When Aggregation Group4 is used for PDCCH scheduling.
8011: LTE • LTE805: P When Aggregation Group8 is used for PDCCH scheduling.
8011: LTE • LTE805: P When Aggregation Group1 is blocked for PDCCH scheduling. A DCI with required AGG1, whic
8011: LTE • LTE805: P When Aggregation Group2 is blocked for PDCCH scheduling. A DCI with required AGG2, whic
8011: LTE • LTE805: P When Aggregation Group4 is blocked for PDCCH scheduling. A DCI with required AGG4, whic
8011: LTE • LTE805: P This counter is updated when Aggregation Group8 is blocked for PDCCH scheduling. A DCI w
8011: LTE • LTE805: P This counter is updated in each scheduling for the measurement period.
8011: LTE • LTE805: P This counter is updated in each scheduling for the measurement period.
8011: LTE • LTE805: P This counter is updated in each scheduling for the measurement period.
8011: LTE • LTE805: P This counter is updated in each scheduling for the measurement period.
8011: LTE • LTE805: P This counter is updated in each scheduling for the measurement period.
8011: LTE • LTE805: P The mean value over the measurement period is updated to this counter. The mean value is th
8011: LTE • LTE805: P This counter is updated when the maximum value of the served UEs in UL per TTI has been re
8011: LTE • LTE805: P Note: The number of TTIs to calculate the mean value includes all DL and special subframes (
8011: LTE • LTE805: P This counter is updated when the maximum value of the served UEs in DL per TTI has been re
8011: LTE • LTE616: This counter is updated with every subframe for which only 1 OFDM symbol is allocated to the
8011: LTE • LTE616: This counter is updated with every subframe for which 2 OFDM symbols are allocated to the P
8011: LTE
rval, all of the three instances • LTE616:
will be includedThis counter
in the is updated with every subframe for which 3 OFDM symbols are allocated to the P
average.
8011: LTE • LTE907: This counter is updated after each sampling interval with the arithmetical average of samples e
8011: LTE • LTE907: The counter is incremented each time a UE is entitled a grant to send a "TTI Bundle".
8011: LTE • LTE907: The counter is incremented when the UE is switched back from TTI Bundling mode earlier than
8011: LTE • LTE907: The counter is incremented when the UE is switched back from TTI Bundling mode within this
8011: LTE • LTE1089:
LTE907: The counter
Downlink is incremented
carrier aggregationwhen the UE is switched back from TTI Bundling later than t2 seco
8011: LTE • LTE1089:
LTE1558:Transmission
TDD Downlink
Downlink of carrier
carrier an RRC:RRCConnectionReconfiguration
aggregation
aggregation message, which includes a "SCellTo
8011: LTE • LTE1558:Reception of an carrier
TDD Downlink RRC:RRCConnectionReconfigurationComplete
aggregation message related to a precedin
8011: LTE • LTE1170:Every 1 second the eNB checks whether the cell is in the active Load Balancing state for inter-
8011: LTE • LTE1382:The counter is updated whenever a UL TTI is assigned to CRG 1.
8011: LTE • LTE1382:The counter is updated whenever a UL TTI is assigned to CRG 2.
8011: LTE • LTE1382:The counter is updated whenever a UL TTI is assigned to CRG 3.
8011: LTE • LTE1382:The counter is updated whenever a UL TTI is assigned to CRG 4.
8011: LTE • LTE1382:The counter is updated whenever a TTI could potentially be used for PUSCH data. (In case no
8011: LTE • LTE1382:The counter is updated whenever a DL TTI is assigned to CRG 1.
8011: LTE • LTE1382:The counter is updated whenever a DL TTI is assigned to CRG 2.
8011: LTE • LTE1382:The counter is updated whenever a DL TTI is assigned to CRG 3.
8011: LTE • LTE1382:The counter is updated whenever a DL TTI is assigned to CRG 4.
8011: LTE • LTE1382:The counter is updated whenever a TTI could potentially be used for PDSCH data. (In case no
8011: LTE • LTE1545 The counter is updated per each TTI by the average use ratio of PUSCH PRBs, which are sha
8011: LTE • LTE1140:Every second the Cell DL Composite Available Capacity (CAC) is measured by an eNB interna
8011: LTE • LTE1140:Every second the Cell DL Composite Available Capacity (CAC) is measured by an eNB interna
8011: LTE • LTE1140:Every second the Cell DL Composite Available Capacity (CAC) is measured by an eNB interna
8011: LTE • LTE1140:Every second the Cell DL Composite Available Capacity (CAC) is measured by an eNB interna
8011: LTE • LTE1140:Every second the Cell DL Composite Available Capacity (CAC) is measured by an eNB interna
8011: LTE • LTE1140:Every second the Cell DL Composite Available Capacity (CAC) is measured by an eNB interna
8011: LTE • LTE1800:The counter is updated in every TTI when the interference shaping is applied.
8011: LTE • LTE1800:The counter is updated in every TTI when the interference shaping is applied.
8011: LTE • LTE1800:The counter is incremented when the preferred resources are changed.
see 3GPP TS 36.423). 8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for PDCCH is measured by an eNB internal
see 3GPP TS 36.423). 8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for PDCCH is measured by an eNB internal
see 3GPP TS 36.423). 8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for PDCCH is measured by an eNB internal
see 3GPP TS 36.423). 8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for PDCCH is measured by an eNB internal
see 3GPP TS 36.423). 8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for PDCCH is measured by an eNB internal
see 3GPP TS 36.423). 8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for PDCCH is measured by an eNB internal
(see 3GPP TS 36.423).8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for GBR bearers is measured by an eNB int
(see 3GPP TS 36.423).8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for GBR bearers is measured by an eNB int
(see 3GPP TS 36.423).8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for GBR bearers is measured by an eNB int
(see 3GPP TS 36.423).8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for GBR bearers is measured by an eNB int
(see 3GPP TS 36.423).8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for GBR bearers is measured by an eNB int
(see 3GPP TS 36.423).8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for GBR bearers is measured by an eNB int
the cell (see 3GPP TS8011:
36.423).
LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for non-GBR bearers is measured by an eN
the cell (see 3GPP TS8011:
36.423).
LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for GBR bearers is measured by an eNB int
the cell (see 3GPP TS8011:
36.423).
LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for GBR bearers is measured by an eNB int
the cell (see 3GPP TS8011:
36.423).
LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for non-GBR bearers is measured by an eN
the cell (see 3GPP TS8011:
36.423).
LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for non-GBR bearers is measured by an eN
the cell (see 3GPP TS8011: LTE Cell ResouEvery second the Cell DL Available Capacity (AC) for non-GBR bearers is measured by an eN
36.423).
8011: LTE • LTE1929:The uses DCIdata
The counter is updated when the eNB receives 0 onfor
PDCCH fortime
the first UL on
SPS activation
PUSCH or reactiva
(non-DTX rec
8011: LTE • LTE1929:The PUSCH data transmissions received afterwards with pre-configured periodicity
counter is updated every TTI by the number of UEs using SPS allocated resources. for the SPS
8011: LTE • LTE1929:Note: The number of those allocated PUSCH PRBs does not matter.
8011: LTE • LTE1929:The counter is incremented by the number of PRBs, which are statically allocated by SPS.
8011: LTE • LTE1113:This counter is updated every 500 ms when the muting pattern 1 is active.
8011: LTE • LTE1113:This counter is updated every 500 ms when the muting pattern 2 is active.
8011: LTE • LTE1113:This counter is updated every 500 ms when the muting pattern 3 is active.
8011: LTE • LTE1113:This counter is updated every 500 ms when the muting pattern 4 is active.
8011: LTE • LTE1113:This counter is updated every 500 ms when the muting pattern 5 is active.
8011: LTE • LTE1113:This counter is updated every 500 ms when the muting pattern 6 is active.
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if there is no user plane traffic, that is, the PR
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if there is no user tplane traffic, that is, the PR
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the r
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the ra
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the ra
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the ra
8011: LTE • LTE1496:This counter is incremented per ABS sub-frame if the PRB utilization of the CRE UE is in the ra
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (i.e. the sum of c
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (i.e. the sum of c
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (i.e. the sum of c
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (i.e. the sum of c
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (i.e. the sum of c
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (i.e. the sum of c
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (i.e. the sum of c
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (i.e. the sum of c
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (i.e. the sum of c
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (that is, the sum
8011: LTE • LTE1491:This measurement is determined by accumulating the number of uplink PRBs (i.e. the sum of c
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (i.e. the sum
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (i.e. the sum
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (i.e. the sum
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (i.e. the sum
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (i.e. the sum
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (i.e. the sum
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (i.e. the sum
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (i.e. the sum
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (i.e. the sum
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (that is, the s
8011: LTE • LTE1491:This measurement is determined by accumulating the number of downlink PRBs (i.e. the sum
8011: LTE • LTE1929:The counter is incremented in those TTIs where resources (PRBs) were statically allocated by
8011: LTE • LTE1113:This counter is updated every 500 ms when the muting pattern 0 is active, i.e. when no muting
8011: LTE • LTE1804:
LTE2006:This counter
Downlink is updated
carrier upon the
aggregation reception
3 CC - 60 MHzof an RRC:RRCConnectionReconfigurationComple
8011: LTE • LTE1804:
LTE1921:This counter
eICIC is updated
- micro
Downlink carrier whenever
aggregation 3 CCscheduling
- 60 MHz of PUCCH format 1bwcs is attempted.
8011: LTE • LTE1921:This
eICIC
counter
- micro
is updated whenever scheduling of PUCCH format 3 is attempted.
8012: LTE • LTE651: The transmission of a MAC PDU for the first time
8012: LTE • LTE651: A correctly received MAC PDU with retransmission.
8012: LTE • LTE651: Th re-transmission of a MAC PDU
8012: LTE • LTE651: A correctly received MAC PDU by original transmission
8012: LTE • LTE770: B
This counter is updated on the transmission of an RLC SDU on DL DCCH towards the UE
8012: LTE • LTE770: B
This counter is updated on the reception of an RLC SDU on DCCH from UE
8012: LTE • LTE770: B
This counter is updated when RLC PDU is received from UE
8012: LTE • LTE770: B
This counter is updated when RLC PDU is transmitted to UE
8012: LTE • LTE770: B
This counter is updated when a PDCP SDU is received from UE.
8012: LTE • LTE770: B
This counter is updated when a PDCP SDU is transmitted towards the UE.
8012: LTE • LTE770: B
This counter is updated when a PDCP SDU is received from UE.
8012: LTE • LTE770: B
This counter is updated when a PDCP SDU is received from UE.
8012: LTE • LTE770: B
This counter is updated when a PDCP SDU is transmitted towards the UE.
8012: LTE • LTE770: B
This counter is updated when a PDCP SDU is transmitted towards the UE.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: B
This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThe counter is updated when MAC SDU is received. The size of received MAC SDU data is ad
8012: LTE • LTE770: BThe counter is updated when MAC SDU is received. Size of received MAC SDU data is added
8012: LTE • LTE770: BThe counter is updated when MAC SDU is received. Size of received MAC SDU data is added
8012: LTE • LTE770: BThe counter is updated when MAC SDU is sent. Size of sent MAC SDU data is added to this c
8012: LTE • LTE770: BThe counter is updated when MAC SDU is sent. Size of sent MAC SDU data is added to this c
8012: LTE • LTE770: BThe counter is updated when MAC SDU is sent. Size of sent MAC SDU data is added to this c
8012: LTE • LTE770: BThe counter is updated when an RRC data block from UE is received. Size of UL RLC PDU's m
8012: LTE • LTE770: BThe counter is updated when an RRC data block is transmitted towards the UE. Size of DL RL
8012: LTE • LTE770: BThe counter is updated on the reception of an RLC SDU on UL-DTCH from UE
8012: LTE • LTE770: BThe counter is updated on the transmission of an RLC SDU on DL-DTCH towards the UE
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE770: BThis counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE Cell Throu This counter is incremented with every TTI, in which at least one UE is scheduled to transmit u
8012: LTE Cell Throu This counterof
The volume is aincremented with everythe
data burst excluding TTI,
datain which at least
transmitted in one UE when
the TTI is scheduled to receive
the buffer is emptieus
8012: LTE Cell Throu of data emptying the buffer).
8012: LTE Cell Throu The time to transmit
volume of a dataaburst
data burst excluding
excluding thetransmitted
the data data transmitted
in the in thewhen
TTI TTI when the buffer
the buffer is e
is emptie
8012: LTE Cell Throu of data emptying the buffer).
8012: LTE Cell Throu The time to transmit
volume of a dataaburst
data burst excluding
excluding thetransmitted
the data data transmitted
in the in thewhen
TTI TTI when the buffer
the buffer is e
is emptie
8012: LTE Cell Throu of data emptying the buffer).
8012: LTE Cell Throu The volume
time to transmit
of a dataaburst
data burst excluding
excluding thetransmitted
the data data transmitted
in the in thewhen
TTI TTI when the buffer
the buffer is e
is emptie
8012: LTE Cell Throu of data emptying the buffer).
8012: LTE Cell Throu The volume
time to transmit
of a dataaburst
data burst excluding
excluding thetransmitted
the data data transmitted
in the in thewhen
TTI TTI when the buffer
the buffer is e
is emptie
8012: LTE Cell Throu of data emptying the buffer).
8012: LTE Cell Throu The volume
time to transmit
of a dataaburst
data burst excluding
excluding thetransmitted
the data data transmitted
in the in thewhen
TTI TTI when the buffer
the buffer is e
is emptie
8012: LTE Cell Throu of data emptying the buffer).
8012: LTE Cell Throu The time to transmit
volume of a dataaburst
data burst excluding
excluding thetransmitted
the data data transmitted
in the in thewhen
TTI TTI when the buffer
the buffer is e
is emptie
8012: LTE Cell Throu of data emptying the buffer).
8012: LTE Cell Throu The volume
time to transmit
of a dataaburst
data burst excluding
excluding thetransmitted
the data data transmitted
in the in thewhen
TTI TTI when the buffer
the buffer is e
is emptie
8012: LTE Cell Throu of data emptying the buffer).
8012: LTE Cell Throu The volume
time to transmit
of a dataaburst
data burst excluding
excluding thetransmitted
the data data transmitted
in the in thewhen
TTI TTI when the buffer
the buffer is e
is emptie
8012: LTE Cell Throu of data emptying the buffer).
8012: LTE Cell Throu The time to transmit a data burst excluding the data transmitted in the TTI when the buffer is e
8012: LTE • LTE9: SerUE)
Reception of aone
in DL for PDCP
E-RABdataduring
block afrom UE of ThpTimeDl. It must exclude the volume of the las
sample
8012: LTE Cell Throu the buffer.
The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu A sample
UE) in DL of
for"ThpTimeDl" for each
one E-RAB during time theofDL
a sample buffer for one
ThpTimeDl. E-RAB
It must is emptied.
exclude the volume of the las
8012: LTE Cell Throu the buffer.
The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu UE)
A sample
in DL of
for"ThpTimeDl" for each
one E-RAB during time theofDL
a sample buffer for one
ThpTimeDl. E-RAB
It must is emptied.
exclude the volume of the las
8012: LTE Cell Throu The
the buffer.
time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu UE)
A sample
in DL of
for"ThpTimeDl" for each
one E-RAB during time theofDL
a sample buffer for one
ThpTimeDl. E-RAB
It must is emptied.
exclude the volume of the las
8012: LTE Cell Throu The
the buffer.
time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu UE)
A sample
in DL of
for"ThpTimeDl" for each
one E-RAB during time theofDL
a sample buffer for one
ThpTimeDl. E-RAB
It must is emptied.
exclude the volume of the las
8012: LTE Cell Throu The
the buffer.
time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu A sample
UE) in DL of
for"ThpTimeDl" for each
one E-RAB during time theofDL
a sample buffer for one
ThpTimeDl. E-RAB
It must is emptied.
exclude the volume of the las
8012: LTE Cell Throu the buffer.
The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu UE)
A sample
in DL of
for"ThpTimeDl" for each
one E-RAB during time theofDL
a sample buffer for one
ThpTimeDl. E-RAB
It must is emptied.
exclude the volume of the las
8012: LTE Cell Throu The
the buffer.
time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu UE)
A sample
in DL of
for"ThpTimeDl" for each
one E-RAB during time theofDL
a sample buffer for one
ThpTimeDl. E-RAB
It must is emptied.
exclude the volume of the las
8012: LTE Cell Throu The
the buffer.
time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu UE)
A sample
in DL of
for"ThpTimeDl" for each
one E-RAB during time theofDL
a sample buffer for one
ThpTimeDl. E-RAB
It must is emptied.
exclude the volume of the las
8012: LTE Cell Throu The
the buffer.
time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu A sample of "ThpTimeDl" for each time the DL buffer for one E-RAB is emptied.
8012: LTE • LTE9: SerTransmission of an PDCP data block towards the UE
8012: LTE • LTE829: This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE829: This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE829: This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE829: This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE541: This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE541: This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE1089:
LTE541: This counter
Downlink is updated
carrier when MAC PDU is scheduled. Retransmissions are included.
aggregation
8012: LTE • LTE1558:Transmission
TDD Downlink of carrier
an RLC aggregation
PDU towards the UE.
8012: LTE • LTE44: 6 This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE44: 6 This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE44: 6 This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE • LTE44: 6 This counter is updated when MAC PDU is scheduled. Retransmissions are included.
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8012: LTE Cell Throu The time to transmit a data burst excluding the last piece of data transmitted in the TTI when th
8013: LTE • LTE651: The reception of an RRC Connection Setup Complete message sent by the UE to eNB.
8013: LTE • LTE651: Timer expiration
8013: LTE • LTE651: The reception of an erroneous or incomplete RRC Connection Setup Complete message.
8013: LTE • LTE651: The reception of an S1AP:UE Context Release Command message sent by the MME to eNB.
8013: LTE • LTE651: The reception of an S1AP:UE Context Release Command message sent by the MME to eNB.
8013: LTE • LTE651: The reception of an S1AP:UE Context Release Command message sent by the MME to the eN
8013: LTE • LTE651: The reception
- RNL Inter-RAT of Redirection
an S1AP:UE Context Release Command message sent by the MME to eNB.
8013: LTE • LTE651: - RNL Redirection towards
UE not available 1xRTT
for PS service
8013: LTE • LTE651: - TNL
RNL Transport
Unspecified Resources Unavailable
8013: LTE • LTE651: This
- TNLcounter
Unspecified
is updated following the reception of an RRC Connection Request message sent
8013: LTE • LTE651: The
Note:reception
If a UE (erroneously) sends thisRequest
of an RRC Connection messagemessage
several times in a
sent by therow
UEwithout
to eNB.waiting the prop
8013: LTE • LTE651: The
Note:reception
If a UE (erroneously) sends thisRequest
of an RRC Connection messagemessage
several times in a
sent by therow
UEwithout
to eNB.waiting the prop
8013: LTE • LTE572:
LTE651: IMS
Note:emergency
If a UE
Reception (erroneously)
of the sessions sends this message several
RRC: RRCConnectionRequest message times in <-
(eNB a row
UE)without
in casewaiting
that thisthe prop
messa
8013: LTE • LTE22: Emergency
Note: If a UE
call(erroneously)
handling sends this message several times in a row without waiting the prop
8013: LTE • LTE42: DThis counter is updated at each subframe when UE is DRX Active.
8013: LTE • LTE572:
LTE42: DThis counter is updated
IMS emergency sessionsat each subframe when UE is DRX Sleep (that is not DRX Active).
8013: LTE • LTE572: Reception
LTE22: Emergency
IMS of the
call
emergency RRC:RRCConnectionSetupComplete message (eNB <- UE) in case that this
handling
sessions
8013: LTE • LTE22: Emergency
Transmissioncall of
handling
the RRC:RRCConnectionReject message (eNB -> UE) because of missing RB
8013: LTE • LTE534: Transmission of an S1AP:UE CONTEXT RELEASE REQUEST message (eNB -> MME; 3GPP
8013: LTE • LTE1047:Transmission of an RRCConnectionReject message (eNB -> UE) in case that this message is
8013: LTE • LTE1047:Transmission of an RRCConnectionReject message (eNB -> UE) in case that this message is
8013: LTE • LTE1074:Note: If a UE (erroneously) sends this message several times in a row without waiting the prop
8013: LTE • LTE1074:The reception of the RRCConnectionSetupComplete message (UE -> eNB) in case that this m
8013: LTE • LTE1074:The transmission of an RRCConnectionReject message (eNB -> UE) in case that this messag
8013: LTE • LTE1361:Note: If a UE (erroneously) sends this message several times in a row without waiting the prop
8013: LTE • LTE1361:Note: If a UE (erroneously) sends this message several times in a row without waiting the prop
8013: LTE • LTE1361:Note: If a UE (erroneously) sends this message several times in a row without waiting the prop
8013: LTE • LTE1361:Note: If a UE (erroneously) sends this message several times in a row without waiting the prop
8013: LTE • LTE1361:Note: If a UE (erroneously) sends this message several times in a row without waiting the prop
8013: LTE • LTE1361:The transmission of an RRCConnectionReject message (eNB -> UE) in case that this messag
8013: LTE • LTE1361:The transmission of an RRCConnectionReject message (eNB -> UE) in case that this messag
8013: LTE • LTE1361:The transmission of an RRCConnectionReject message (eNB -> UE) in case that this messag
8013: LTE • LTE1361:The transmission of an RRCConnectionReject message (eNB -> UE) in case that this messag
8013: LTE • LTE1740:Transmission of an S1AP:INITIAL UE message (eNB->MME) that contains the first NAS signa
8013: LTE • LTE1740:Reception of the first S1AP message (MME->eNB) containing NAS signaling, which was receiv
8013: LTE • LTE1740:Reception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by MME to the eN
8013: LTE • LTE1740:Reception of an S1AP:INITIAL CONTEXT SETUP REQUEST message sent by MME to the eN
8013: LTE • LTE1740:Transmission
Transmission of an S1AP:INITIAL CONTEXT SETUP RESPONSE message sent by eNB to th
8013: LTE • LTE1740:The counter is updated only in case that the preceding received S1AP:INITIAL CONTEXT SET
8013: LTE • LTE1740:Transmission of an S1AP:INITIAL CONTEXT SETUP FAILURE message sent by eNB to the M
8013: LTE • LTE1740:Reception of an S1AP:UE CONTEXT MODIFICATION REQUEST message sent by MME to th
8013: LTE • LTE1740:Reception of an S1AP:UE CONTEXT MODIFICATION REQUEST message sent by MME to th
8013: LTE • LTE1740:Transmission of an S1AP:UE CONTEXT MODIFICATION RESPONSE message sent by eNB
Transmission of an S1AP:UE CONTEXT MODIFICATION RESPONSE message sent by eNB
8013: LTE • LTE1740:The counter is updated only by
incremented in case that the
one upon the preceding
transmission received S1AP:UE
of an S1AP: UE CONTEXT
CONTEXT MODIFIC
RELEAS
8013: LTE UE State The counter is updated for all transport network layer causes used by the eNB initiated UE CO
8013: LTE UE State The counter is incremented by one upon the transmission of an S1AP: UE CONTEXT RELEAS
8013: LTE UE State The counter is incremented by one upon the transmission of an S1AP: UE CONTEXT RELEAS
8013: LTE UE State The counter is incremented by one upon the transmission of an S1AP: UE CONTEXT RELEAS
8013: LTE UE State The counter is incremented by one upon the transmission of an S1AP: UE CONTEXT RELEAS
8013: LTE UE State The counter is incremented by one upon the transmission of an S1AP: UE CONTEXT RELEAS
8013: LTE UE State The counter is incremented by one upon the transmission of an S1AP: UE CONTEXT RELEAS
8013: LTE UE State TheThis counter
counter is is incremented by one
updated following upon
the the transmission
transmission of an S1AP: UE
of an S1AP:INITIAL CONTEXT
CONTEXT RELEAS
SETUP RES
(3GPP TS 36.331). 8013: LTE • LTE1749 This counter is only updated for 3GPP Release 11 (or higher) UEs.
8013: LTE • LTE1912:The transmission of an RRCConnectionReject message (eNB -> UE) in case that this messag
8013: LTE • LTE1912:The transmission of an RRCConnectionReject message (eNB -> UE) in case that this messag
8013: LTE • LTE1912:The transmission of an RRCConnectionReject message (eNB -> UE) in case that this messag
8013: LTE • LTE1912:The transmission of an RRCConnectionReject message (eNB -> UE) in case that this messag
8013: LTE • LTE1912:The transmission of an RRCConnectionReject message (eNB -> UE) in case that this messag
8014: LTE • LTE651: The transmission of an X2AP: Handover Request to the target eNB.
8014: LTE • LTE651: The expiration of timer TX2RELOCprep
8014: LTE • LTE651: The reception of an X2AP: Handover Preparation Failure message from the target eNB.
8014: LTE • LTE651: The counter is updated if the failure detected does not match any other failure counter.
8014: LTE • LTE651: The reception of an X2AP: Handover Request Acknowledge message from the target eNB.
8014: LTE • LTE651: The reception of an X2AP:Release Resource message sent by the target eNB.
8014: LTE • LTE651: The expiration of timer TX2RELOCoverall.
8014: LTE • LTE54: I This counter is updated following the transmission of an S1AP: HANDOVER REQUIRED mess
8014: LTE • LTE54: I This counter is updated at the expiry of the guarding timer TS1RELOCprep if the timer was sta
8014: LTE • LTE54: I This counter is updated following the reception of an S1AP: HANDOVER PREPARATION FAIL
8014: LTE • LTE54: I This counter is updated following the reception of an S1AP: HANDOVER PREPARATION FAIL
8014: LTE • LTE54: I This counter is updated following the reception of an S1AP: HANDOVER COMMAND messag
8014: LTE • LTE54: I This counter is updated following the reception of an S1AP: UE CONTEXT RELEASE COMMA
8014: LTE • LTE54: I -This counter is updated
if TS1RELOCprep following the
consecutively expiryforofmore
expires the guarding
than the timer TS1RELOCoverall
pre-configured number ofintimes.
case th
8014: LTE • LTE797:
LTE1944:Performance
- if TX2RELOCprep Counter consecutively
Plus Package expires for moreI than the pre-configured number of times.
for Handover
8015: LTE • LTE797:
LTE1708:Performance
This
Extend
counter
maximum
is updated
Counter numberwhen
Plus of X2
an links
Package Intra-eNB Handover
for Handover I preparation fails for any reason. This cou
8015: LTE • LTE797:
LTE1708:Performance
This
Extend
counter
maximum
is updated
Counter numberwhen
Plus of X2
an links
Package RRC forCONNECTION
Handover I RECONFIGURATION message is sent
8015: LTE • LTE54:
LTE1708: This
Extend
Intra-LTE counter
maximum
is updated
handover number
via S1when of X2
an links
Intra-eNB Handover succeeds. This counter is updated in the
8015: LTE • LTE1708: This
Extend
LTE54: Intra-LTE
HO counter
via maximum
X2: is updated
handover
This number
S1following
counter
via of X2 links
is updated any failure in
following thethe HO preparation
expiration phase intimer
of the guarding the target cell apa
TX2RELOCp
8015: LTE • LTE1708: HOExtend
via
LTE54: Intra-LTEX2: S1:
maximum
This counter
number
handover via S1 is updated
of X2 links
following the expiration of the guarding timer
reception of an X2AP:HANDOVER PREPARA TS1RELOCp
8015: LTE • LTE1708: HOExtend
LTE54: Intra-LTEvia S1:
maximum
This counter
handover number
via S1is updated
of X2 linksfollowing the reception of an S1AP:HANDOVER PREPARA
8015: LTE • LTE54:
LTE1708: This
Extend
Intra-LTE counter
maximum
is updated
handover number
via S1following
of X2 links
the reception of an S1AP:HANDOVER COMMAND message
8015: LTE • LTE54:
LTE1708: HOExtend
Intra-LTEvia S1:
maximum
This counter
handover number
via S1is updated
of X2 linksfollowing the reception of an S1AP:UE CONTEXT RELEAS
8015: LTE • LTE797: This counter
LTE1708:Performance
Extend is
maximum updated
Counter numberfollowing
Plus thefor
of X2 links
Package expiry of a guarding
Handover I timer, either TX2RELOCoverall or TS
8015: LTE • LTE533:
LTE1708:Mobility
This
Extend
The counter
case maximum
is updated
Robustness number
of reestablishmentfollowing
ofcauses
X2 links
the that
expiration of a guarding
"ReconfigFailure" timer THOoverall
is excluded in caseThe
from counting. thatcas
the
8015: LTE • LTE533:
LTE1708:Mobility
InExtend
the source
Note: maximumcell ofnumber
Robustness missedof HO X2attempt,
links a HO preparation for the considered UE context migh
8015: LTE • LTE1708: The
Extend
LTE533: Mobility
"short RRCConnectionReestablishmentRequest
maximum
time"
Robustness
is definednumber
as time of X2 linksno longerafter
period than aexpiration
failed HOvalue
is recognized by reestablishme
of Tstore_UE_cntxt timer
8015: LTE • LTE1708:For Extend
the sequence
maximumofnumberCase2 of theX2reestablishment
links request (with cause "handoverFailure") receiv
ounter is incremented for
8015:
successive
LTE • LTE1768
handoverThe events
counterwhich
is updated
occur after
in cell
theAfirst
whenhandover
a UE finally
event. returns to the cell A within a short time perio
8015: LTE Neighbor ce This counter is updated following the transmission of an RRC Connection Reconfiguration mes
8015: LTE •Neighbor
LTE562:ce Inter-eNB
CSFB
or HO - via
to UTRAN orS1:
GSMThis viacounter
redirectis updated following the reception of an S1AP: UE CONTE
8016: LTE • LTE562:
LTE874: CSFB
following CDMA/1xRTT
the transmission
to UTRAN or GSMforviaof
dualan RX
RRC:RRCConnectionRelease
redirectUEs message (source eNB -> UE) in
8016: LTE • LTE22:
LTE874:Emergency
CSFB
This counter
or to CDMA/1xRTT
callishandling
updatedforfollowing
dual RX the
UEstransmission of an RRC:RRCConnectionRelease messag
8016: LTE • LTE874: CSFB
followingto CDMA/1xRTT
the transmission for ofdualan RX
RRC:RRCConnectionRelease
UEs message (source eNB -> UE) in
8016: LTE • LTE56: I Transmission of an S1AP:HANDOVER REQUIRED message to source MME for an Inter Syste
8016: LTE • LTE56: I Updated when Inter System Handover preparation fails due to expiration of guarding timer TS1
8016: LTE • LTE56: I Updated when an S1AP:HANDOVER PREPARATION FAILURE message is received from MM
8016: LTE • LTE56: I Updated when an S1AP:HANDOVER PREPARATION FAILURE message is received from MM
8016: LTE • LTE56: I Updated when an S1AP:HANDOVER COMMAND message is received from MME for a PS-HO
8016: LTE • LTE56: I Updated when an S1AP:UE CONTEXT RELEASE COMMAND message is received from MME
8016: LTE • LTE56: I Updated when PS-HO to UTRAN fails due to expiration of guarding timer TS1RELOCoverall. T
8016: LTE • LTE442: Transmission of the RRC: MobilityFromEUTRANCommandmessage (with cell change order to
8016: LTE • LTE872: Reception of an S1AP:HANDOVER COMMAND message (source eNB <- MME; 3GPP TS 36.
8016: LTE • LTE872: Reception of an S1AP:UE CONTEXT RELEASE COMMAND message (source eNB <- MME;
8016: LTE • LTE872: Expiration of the guarding timer TS1RELOCoverall (3GPP TS 36.413) in case that this timer w
8016: LTE • LTE736: Transmission of an RRC:MobilityFromEUTRACommand message (source eNB -> UE; 3GPP T
8016: LTE • LTE873: Reception of an S1AP:HANDOVER COMMAND message (source eNB <- MME; 3GPP TS 36.
8016: LTE • LTE873: Reception of an S1AP:UE CONTEXT RELEASE COMMAND message (source eNB <- MME;
8016: LTE • LTE873: Expiration of the guarding timer TS1RELOCoverall (3GPP TS 36.413) in case this timer was s
8016: LTE • LTE738: This counter is updated following the transmission of an RRC:HandoverFromEUTRAPreparatio
8016: LTE • LTE738: This counter is updated following the expiration of the guarding timer TUlHoPrepTransfer1xSrv
8016:
s a failed HO preparation LTE • LTE738:
to 1xRTT This counter is updated following the expiration of the guarding timer TC2KRelocPrep1xSrvcc
with SRVCC.
8016: LTE • LTE738: This counter is updated following the reception of an S1AP:DOWNLINK S1 CDMA2000 TUNN
8016: LTE • LTE738: This counter is updated following the reception of an S1AP:DOWNLINK S1 CDMA2000 TUNN
8016: LTE • LTE738: This counter is updated following the transmission of an RRC:MobilityFromEUTRACommand m
8016: LTE • LTE738: This counter is updated following the transmission of an S1AP:UE CONTEXT RELEASE REQ
the CDMA2000 1xRTT 8016:parameters
LTE • LTE2175:This
to the UE so that
counter
the UEis updated
can register
following
with the
theCDMA2000
reception of1xRTT
an RRC:network
CSFBParametersRequestCDMA20
to support CS Fallback to CD
the CDMA2000 1xRTT 8016:parameters
LTE • LTE2175:This
to the UE so that
counter
the UEis updated
can register
following
with the
theCDMA2000
transmission1xRTT
of an RRC:
networkCSFBParametersResponseCDM
to support CS Fallback to CD
8016: LTE • LTE2175:This counter is updated following the transmission of an RRC:HandoverFromEUTRAPreparatio
8016: LTE • LTE2175:This counter is updated following the reception of an RRC: ULHandoverPreparationTransfer m
8016: LTE • LTE56:
LTE2175:This counter
Inter RAT is updated
handover following the reception of an S1AP:DOWNLINK S1 CDMA2000 TUNN
to WCDMA
8017: LTE • LTE56:
LTE1708: Updated
Extend
Inter RAT maximum
when Interto
handover number
System
WCDMA ofHandover
X2 links preparation to UTRAN fails due to expiration of guardin
8017: LTE • LTE56:
LTE1708: Updated
Extend
Inter when an S1AP:HANDOVER
RAT maximum
handover number
to WCDMA of X2 links PREPARATION FAILURE message is received from MM
8017: LTE • LTE56:
LTE1708: Updated
Extend
Inter RAT maximum
when an S1AP:HANDOVER
handover number
to WCDMA of X2 links PREPARATION FAILURE message is received from MM
8017: LTE • LTE1708: Updated
Extend maximum
when an S1AP:HANDOVER
number
LTE56: Inter RAT handover to WCDMA of X2 links COMMAND message is received from MME for a PS-HO
8017: LTE • LTE1708: Updated
Extend maximum
when an S1AP:UE
number
LTE56: Inter RAT handover to WCDMA ofCONTEXT
X2 links RELEASE COMMAND message is received from MME
8017: LTE • LTE56:
LTE1708: Updated
Extend
Inter when a PS-HO
RAT maximum
handover number
to to of
WCDMA UTRAN fails due to expiration of guarding timer TS1RELOCoverall
X2 links
8017: LTE • LTE872:
LTE1708:SRVCC
Transmission
Extend to
maximum
WCDMAof annumber
S1AP:HANDOVER
of X2 links REQUIRED message to source MME for an Inter Syste
8017: LTE • LTE872:
LTE1708:SRVCC
Reception
Extend to
maximum
of an S1AP:HANDOVER
WCDMA number of X2 links COMMAND message (source eNB <- MME; 3GPP TS 36.
8017: LTE • LTE872:
LTE1708:SRVCC
Reception
Extend to
maximum
of an S1AP:UE
WCDMA numberCONTEXT
of X2 links RELEASE COMMAND message (source eNB <- MME;
8017: LTE • LTE1708:Expiration
Extend maximum
of the guarding
numbertimer
of X2TS1RELOCoverall
links (3GPP TS 36.413) in case that this timer w
8018: LTE eNB Load The arithmetical average of samples taken from the number of UEs, having one SRB and at le
8018: LTE • LTE770: B The maximum value of the samples of UEs having one SRB and at least one DRB established
8018: LTE • LTE522: S Transmission of an S1AP:RESET Message (partial or global).
8018: LTE • LTE522: S Transmission of an S1AP:RESET Message (partial or global).
8018: LTE • LTE522: S Reception of an S1AP:RESET Message (partial or global) sent by MME to the eNB.
8018: LTE • LTE522: S Reception of an S1AP:RESET Message (partial or global) sent by MME to the eNB.
8018: LTE eNB Load This counter is updated after each sampling interval with the sample taken from the number of
8018: LTE •eNB Load Network
LTE442: This counter is updated
Assisted by value
Cell Change to 1GSM
when the number of Active UEs is summed to counter SUM
8019: LTE • LTE873:
LTE1708:Relationship
Transmission
Extend maximum of thenumber
Model RRC:MobilityFromEUTRANCommand
GERAN ofchanges
X2 linksin eNB message (with cell change order to
8019: LTE • LTE1708: Reception
Extend maximum
of an S1AP:HANDOVER
number of X2
LTE873: Relationship Model GERAN changes in eNB links
COMMAND message (source eNB <- MME; 3GPP TS 36.
8019: LTE • LTE1708: Reception
Extend maximum
of an S1AP:UE
number CONTEXT
of X2
LTE873: Relationship Model GERAN changes in eNB links RELEASE COMMAND message (source eNB <- MME;
8019: LTE • LTE1708:Expiration
Extend maximum
of the guarding
numbertimer
of X2TS1RELOCoverall
links (3GPP TS 36.413) in case this timer was s
8020: LTE •CLTE770: B The counter is updated with value 1 when cell state changes to Cell Operational is enabled.
8020: LTE •CLTE1103:The counter is incremented with value 1 when cell "Administrative State transitions to locked" o
8020: LTE •CLTE1103:The counter is incremented with value 1 when cell "Operational State changes to disabled" and
8020: LTE •CLTE432: The counter is incremented by 1 approximately every 10 seconds when "Cell Operational State
8020: LTE •CLTE1103:The counter is incremented with value 1 approximately every 10 seconds when cell "Administr
8020: LTE •CLTE1103:The counter is incremented with value 1 approximately every 10 seconds when cell "Operation
8020: LTE •CLTE432: The counter is updated with value 1 approximately every 10 seconds.
8020: LTE •CLTE1103:The counter is incremented with value 1 approximately every 10 seconds when the cell "Opera
8020: LTE •CLTE1103:The counter is incremented with value 1 when the cell "Operational State changes to disabled"
8021: LTE • LTE55: Ininter-eNB HO - via S1: This counter is updated following the reception of an S1AP:HANDOVER
8021: LTE • LTE55: Ininter-eNB HO - via S1: This counter is updated following the reception of an S1AP:HANDOVER
8021: LTE • LTE55: Ininter-eNB HO - via S1: This counter is updated following the reception of an S1AP:UE CONTE
8021: LTE • LTE55: Ininter
inter-eNB
eNB HO - via X2: S1: Expiration
This counter of is
theupdated following the reception
timer TX2RELOCoverall (3GPP ofTS36.423)
an S1AP:UE CONTE
in case tha
8021: LTE • LTE55: Ininter eNB HO - via X2: S1: This
Expiry of the is
counter guarding
updatedtimer TS1RELOCoverall
following the expiration (3GPP TS 36.413)
of the timer TX2RELOC in c
8021: LTE • LTE55: Ininter eNB HO - via S1: This counter is updated following the expiration of the guarding timer TS
8021: LTE • LTE572: Transmission of the S1AP:HANDOVER REQUIRED message (source eNB -> MME; 3GPP TS
re not counted. Load-based
8021:handover
LTE • LTE1127:
eventsThis
are counter
not counted.
is updated following the transmission of an RRC Connection Reconfiguration mes
re not counted. Load-based
8021:handover
LTE • LTE1127:
eventsor
Inter-eNB
are not counted.
HO - via S1: This counter is updated following the reception of an S1AP:UE CONTE
8021: LTE • LTE572: Reception
Inter-eNB HOof the
viaS1AP:HANDOVER
S1: PREPARATION FAILURE message (source eNB <- MME
8021: LTE • LTE572: Trigger Event: Reception
Inter eNB HO via S1: of the S1AP:HANDOVER COMMAND message (source eNB <- MME
8021: LTE • LTE572: or
Trigger Event: Reception of the S1AP:UE CONTEXT RELEASE COMMAND message (source
8021: LTE • LTE42: Dor
Inter-eNB HO via S1: Trigger Event: Reception of the S1AP:HANDOVER COMMAND messag
8021: LTE • LTE42: DThe
Intercase
eNB of
HOreestablishment
via S1:Trigger Event: Reception of the is
cause 'ReconfigFailure' S1AP: UE CONTEXT
excluded RELEASE
from counting. COMMA
The case of re
8021: LTE • LTE533: Note:
In the source cell of missed HO attempt, a HO preparation for the considered UE context may
8021: LTE • LTE533: 'short
The RRCConnectionReestablishmentRequest
time' is defined as time period no longer than after expiration
a failed HOvalue
is recognized by reestablishme
of Tstore_UE_cntxt timer u
8021: LTE • LTE1170:
LTE533: For the sequenceload
Inter-frequency of Case2 the reestablishment request (cause 'HOfailure') received at cell pre
balancing
8021: LTE • LTE1841:
LTE1170:This counter is updated
Inter-Frequency
Inter-frequency following the transmission of an RRC Connection Reconfiguration mes
Loadbalancing
load Equalization
8021: LTE • LTE1841:Inter-eNB
Inter-Frequency
HO - viaLoadS1: This
Equalization
counter is updated following the reception of an S1AP: UE CONTE
8021: LTE • LTE1935:Inter-RAT HO: This counter is updated following the reception of an S1AP: HANDOVER REQU
8021: LTE • LTE1935:Inter-eNB HO - via S1: This counter is updated following the reception of an S1AP: HANDOVE
8021: LTE • LTE1935:Inter-eNB HO - via S1: This counter is updated following the reception of an S1AP: HANDOVE
8021: LTE • LTE1935:Inter-eNB HO - via S1: This counter is updated following the reception of an S1AP: HANDOVE
8021: LTE • LTE1935:Inter-eNB HO - via S1: This counter is updated following the reception of an S1AP: HANDOVE
8021: LTE • LTE1935:Inter-RAT HO: This counter is updated following the transmission of an S1AP: HANDOVER RE
8021: LTE • LTE1935:Inter-eNB HO - via S1: This counter is updated following the transmission of an S1AP: HANDO
8021: LTE • LTE1935:Inter-eNB HO - via S1: This counter is updated following the transmission of an S1AP: HANDO
8021: LTE • LTE1935:Inter-eNB HO - via S1: This counter is updated following the transmission of an S1AP: HANDO
8021: LTE • LTE1935:Inter-eNB HO - via S1: This counter is updated following the transmission of an S1AP: HANDO
8021: LTE • LTE1935:Inter-RAT HO: This counter is updated following the transmission of an S1AP: HANDOVER FA
8021: LTE • LTE1935:Inter-RAT HO: This counter is updated following the transmission of an S1AP: HANDOVER FA
8021: LTE • LTE64: SThis counter is updated following the transmission of an RRC Connection Reconfiguration mes
8021: LTE • LTE64: STransmission
Inter-eNB HO of - via S1: This
X2AP: counterREQUEST
X2 SETUP is updatedmessage
following to
thethe
reception
neighborofeNB
an S1AP: UE CONTE
_x000D_
8022: LTE • LTE782: Reception
(3GPP TS of 36.423)
X2AP: X2 SETUP FAILURE message or expiration of Timer (wait for X2 SETUP
8022: LTE • LTE782: - (3GPP TS 36.423)
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is received from a UE assigned to QCI Counter G
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is received from a UE assigned to QCI Counter G
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is received from a UE assigned to QCI Counter G
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is received from a UE assigned to QCI Counter G
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is received from a UE assigned to QCI Counter G
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is received from a UE assigned to QCI Counter G
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is transmitted towards a UE assigned to QCI Coun
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is transmitted towards a UE assigned to QCI Coun
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is transmitted towards a UE assigned to QCI Coun
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is transmitted towards a UE assigned to QCI Coun
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is transmitted towards a UE assigned to QCI Coun
8023: LTE •ULTE518: OThis counter is updated when a PDCP SDU is transmitted towards a UE assigned to QCI Coun
8023: LTE •ULTE490: SThe average of samples taken from the number of active UEs, having one SRB and at least on
8023: LTE •ULTE490: SThe average of samples taken from the number of active UEs, having one SRB and at least on
8023: LTE •ULTE490: SThe average of samples taken from the number of active UEs, having one SRB and at least on
8023: LTE •ULTE490: SThe average of samples taken from the number of active UEs, having one SRB and at least on
8023: LTE •ULTE490: SThe average of samples taken from the number of active UEs, having one SRB and at least on
8023: LTE •ULTE490: SThe average of samples taken from the number of active UEs, having one SRB and at least on
8023: LTE •ULTE490: SThe average of samples taken from the number of active UEs, having one SRB and at least on
8023: LTE •ULTE490: SThe average of samples taken from the number of active UEs, having one SRB and at least on
8023: LTE •ULTE490: SThe average of samples taken from the number of active UEs, having one SRB and at least on
8023: LTE •ULTE518: OThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE518: OThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE518: OThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE518: OThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE518: OThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE518: OThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE518: OThis counter is incremented if the operator-specific QCIs of the DRBs for a UE do not share th
8023: LTE •ULTE487: IThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE487: IThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE487: IThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE487: IThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE487: IThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE487: IThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE487: IThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8023: LTE •ULTE487: IThe arithmetical average of samples taken from the number of active UEs, having one SRB an
8025: LTE • LTE60: I This counter is updated following the transmission of an RRC:HandoverFromEUTRAPreparatio
8025: LTE • LTE60: I This counter is updated following the expiration of the guarding timer TUlHoPrepTransferHrpd
8025: LTE • LTE60: I This counter is updated following the expiration of the guarding timer TC2KRelocPrepHrpd in c
8025: LTE • LTE60: I This counter is updated following the reception of an S1AP:DOWNLINK S1 CDMA2000 TUNN
8025: LTE • LTE60: I This counter is updated following the reception of an S1AP:DOWNLINK S1 CDMA2000 TUNN
8025: LTE • LTE60: I This counter is updated following the transmission of an RRC:MobilityFromEUTRACommand m
8025: LTE • LTE60: I This counter is updated following the expiration of the guarding timer TC2KRelocOverallHRPD
8025: LTE • LTE1361:
LTE60: I This counterQoS
Additional is updated
performancefollowing the reception of an S1AP:UE CONTEXT RELEASE COMMA
measurements
8026: LTE • LTE1361:
LTE2054:The
Measurement
counterQoS
Additional is updated
Report addition
when ameasurements
performance with
missing
PDCP UL KPI
PDCP counter
sequence
subsetnumber is detected.
8026: LTE • LTE2054: The
Measurement
counter is updated
Report addition
when
LTE1361: Additional QoS performance measurementsa with
missing
PDCP UL KPI
PDCP counter
sequence
subsetnumber is detected.
8026: LTE • LTE2054: The
Measurement
counter is updated
Report addition
when
LTE1361: Additional QoS performance measurementsa with
missing
PDCP UL KPI
PDCP counter
sequence
subsetnumber is detected.
8026: LTE • LTE1361:
LTE2054:The counterQoS
Measurement
Additional is updated
Report when ameasurements
addition
performance missing
with PDCP UL KPI
PDCP sequence
counter subsetnumber is detected.
8026: LTE • LTE1361:
LTE2054:If
The
Measurement
thecounter
Additional is updated
transmission
QoS Report
of a addition
when ameasurements
performance
packet with
missing
might PDCP UL KPI
PDCP counter
sequence
subsetnumber is detected.
8026: LTE • LTE1361:
LTE2054:If
continue
Measurement
Additionalin QoS
another
the transmission Report
ofcell,
a addition
performance it shallmeasurements
packet with
not be
might PDCP
included
KPI counter
in this count.
subset(HO case)
8026: LTE • LTE1361:
LTE2054:If
continue
Measurement
Additionalin QoS
another
the transmission Report
ofcell,
a addition
performance it shallmeasurements
packet with
not be
might PDCP
included
KPI counter
in this count.
subset(HO case)
8026: LTE • LTE1361:
LTE2054:If
continue
Measurement
Additionalin QoS
another
the transmission Report
ofcell,
a addition
performance it shallmeasurements
packet with
not be
might PDCP
included
KPI counter
in this count.
subset(HO case)
8026: LTE • LTE1361:
LTE2054:If
continue
Measurement
Additionalin QoS
another
the transmission Report
ofcell,
a addition
performance it shallmeasurements
packet with
not be
might PDCP
included
KPI counter
in this count.
subset(HO case)
8026: LTE • LTE2054: continue
Measurement
in another
Reportcell,
addition
it shall
LTE1361: Additional QoS performance measurements with
not be
PDCP
included
KPI counter
in this count.
subset(HO case)
8026: LTE • LTE2054: This counter
Measurement is updated
Report when
addition
LTE1361: Additional QoS performance measurements a PDCP
with PDCPSDU of
KPI a QCI
counter5 bearer
subset is sent to the UE.
8026: LTE • LTE2054: This
Measurement
counter is updated
Report addition
when
LTE1361: Additional QoS performance measurements a with
PDCP PDCPSDU KPI
of acounter
QCI 6 bearer
subset is sent to the UE.
8026: LTE • LTE1361:
LTE2054:This
Measurement
counterQoS
Additional is updated
Report addition
performancewhen measurements
awith
PDCP PDCPSDUKPIof acounter
QCI 7 bearer
subset is sent to the UE.
8026: LTE • LTE1361:
LTE2054:This
Measurement
counterQoS
Additional is updated
Report addition
performancewhen measurements
awith
PDCP PDCPSDUKPIof acounter
QCI 8 bearer
subset is sent to the UE.
8026: LTE • LTE1361:
LTE2054:This counterQoS
Measurement
Additional is updated
Report when measurements
addition
performance awith
PDCP PDCPSDUKPIof acounter
QCI 9 bearer
subset is sent to the UE.
8026: LTE • LTE1361:
LTE2054:This
Measurement
counterQoS
Additional is updated
Report addition
performancewhen measurements
awith
PDCP PDCPSDUKPIfor counter
a QCI 5subset
bearer is delivered to higher layers.
8026: LTE • LTE1361:
LTE2054:This
Measurement
counterQoS
Additional is updated
Report addition
performancewhen measurements
awith
PDCP PDCPSDUKPIfor counter
a QCI 6subset
bearer is delivered to higher layers.
8026: LTE • LTE2054: This
Measurement
counter is updated
Report addition
when
LTE1361: Additional QoS performance measurements a with
PDCP PDCPSDU KPI
for counter
a QCI 7subset
bearer is delivered to higher layers.
8026: LTE • LTE2054: This
Measurement
counter is updated
Report addition
when
LTE1361: Additional QoS performance measurements a with
PDCP PDCPSDU KPI
for counter
a QCI 8subset
bearer is delivered to higher layers.
8026: LTE • LTE2054:This
Measurement
counter is updated
Report addition
when a with
PDCP PDCPSDU KPI
The counter is incremented when the eNB received feedback for counter
a QCI 9subset
bearer(ACK/NACK)
is delivered to higher
from layers.
the UE for an
8026: LTE QoS Round
The trip times
counter for PDCP SDUs
is incremented when (or
theparts
eNB thereof),
received which could
feedback not be completely
(ACK/NACK) from thesent,
UE must
for ann
8026: LTE QoS Round
The trip times
counter for PDCP SDUs
is incremented when (or
theparts
eNB thereof),
received which could
feedback not be completely
(ACK/NACK) from thesent,
UE must
for ann
8026: LTE QoS Round
The trip times
counter for PDCP SDUs
is incremented when (or
theparts
eNB thereof),
received which could
feedback not be completely
(ACK/NACK) from thesent,
UE must
for ann
8026: LTE QoS Round
The trip times
counter for PDCP SDUs
is incremented when (or
theparts
eNB thereof),
received which could
feedback not be completely
(ACK/NACK) from thesent,
UE must
for ann
8026: LTE QoS Round
The trip times
counter for PDCP SDUs
is incremented when (or
theparts
eNB thereof),
received which could
feedback not be completely
(ACK/NACK) from thesent,
UE must
for ann
8026: LTE QoS Round
The trip times
counter for PDCP SDUs
is incremented when (or
theparts
eNB thereof),
received which could
feedback not be completely
(ACK/NACK) from thesent,
UE must
for ann
8026: LTE QoS Round
The counter is incremented when the eNB received feedback (ACK/NACK) from the UE for ann
trip times for PDCP SDUs (or parts thereof), which could not be completely sent, must
8026: LTE QoS Round trip times
The counter for PDCP SDUs
is incremented when (or
theparts
eNB thereof),
received which could
feedback not be completely
(ACK/NACK) from thesent,
UE must
for ann
8026: LTE •QoS
LTE1361:Round trip times
Additional for PDCP SDUs
QoS performance (or parts thereof), which could not be completely sent, must n
measurements
8026: LTE • LTE2054:The
Measurement
counter is updated
Report addition
when a withmissing
PDCP UL KPI
PDCP counter
sequence
subsetnumber is detected.
• LTE1361: Additional QoS performance measurements
8026: LTE • LTE2054:
LTE1361:The
Measurement
counterQoS
Additional is updated
Report addition
when ameasurements
performance with
missingPDCPUL KPI
PDCPcounter
sequence
subsetnumber is detected.
8026: LTE • LTE2054:The
Measurement
counter is updated
Report addition
when a with
missing
LTE1361: Additional QoS performance measurements PDCPUL KPI
PDCPcounter
sequence
subsetnumber is detected.
8026: LTE • LTE1361:
LTE2054:The
Measurement
counterQoS
Additional is updated
Report addition
when ameasurements
performance with
missingPDCPUL KPI
PDCPcounter
sequence
subsetnumber is detected.
8026: LTE • LTE1361:
LTE2054:If
The
Measurement
thecounter
Additional is updated
Report
transmission
QoS of a addition
when ameasurements
performance
packet with
missing
might PDCPUL KPI
PDCPcounter
sequence
subsetnumber is detected.
8026: LTE • LTE1361:
LTE2054:If
continue
Measurement
in QoS
Additional another
Report
the transmission ofcell,
a addition
it shallmeasurements
performance
packet with
not be
might PDCP
included
KPI counter
in this count.
subset(HO case)
8026: LTE • LTE1361:
LTE2054:If
continue
Measurement
in QoS
Additional another
Report
the transmission ofcell,
a addition
it shallmeasurements
performance
packet with
not be
might PDCP
included
KPI counter
in this count.
subset(HO case)
8026: LTE • LTE1361:
LTE2054:If
continue
Measurement
in QoS
Additional another
Report
the transmission ofcell,
a addition
it shallmeasurements
performance
packet with
not be
might PDCP
included
KPI counter
in this count.
subset(HO case)
8026: LTE • LTE1361:
LTE2054:If
continue
Measurement
in QoS
Additional another
Report
the transmission ofcell,
a addition
it shallmeasurements
performance
packet with
not be
might PDCP
included
KPI counter
in this count.
subset(HO case)
8026: LTE • LTE2054:continue
Measurement
in another
Report
Inter-eNB HO via X2: cell,
addition
it shall with
not be
PDCP
included
KPI counter
in this count.
subset(HO case)
8027: LTE • LTE1617:Trigger Event: Sending
Inter-eNB HO via X2: of the X2AP:HANDOVER REQUEST message to the requesting eNB t
8027: LTE • LTE1617:Inter-eNB
Trigger Event:
HO viaReception
X2: of the X2AP:HANDOVER REQUEST ACKNOWLEDGE message fro
8027: LTE • LTE1617:Trigger Event: Sending
Reception ofof the X2AP:UE
X2AP:RLF CONTEXT
INDICATION RELEASE
message message
to the servingfrom
eNBthe requesting
after the susp
8027: LTE • LTE1617:inter-eNB
In case thatHO multiple
via X2:X2AP:RLF INDICATION messages are sent, for example, because the or
8027: LTE • LTE1617:Trigger Event: Sending of X2AP:HANDOVER REQUEST ACKNOWLEDGE message after the
8027: LTE • LTE1617:Expiration of the guard timer for the UE context retrieval during RLF-triggered Handover proce
8029: LTE • LTE1697:This
1. oncounter
randomisaccess
set at the end ofitthe
response measurement
is incremented byperiod
1 with the value of the parameter "LNC
8029: LTE • LTE1697:2.
1. on TA command by the time difference
random access response it is incremented by 1(in seconds) to the last counter update (either initial
8029: LTE • LTE1697:2.
1. on TA command by the time difference
random access response it is incremented by 1(in seconds) to the last counter update (either initial
8029: LTE • LTE1697:2.
1. on TA command by the time difference
random access response it is incremented by 1(in seconds) to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:2.
1. on TA
random access response it is incremented by 1 to the last counter update (either initial
command by the time difference (in seconds)
8029: LTE • LTE1697:2.
1. on TA command
random accessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:2.
1. on TA
random access response it is incremented by 1 to the last counter update (either initial
command by the time difference (in seconds)
8029: LTE • LTE1697:2.
1. on TA command
random accessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:2.
1. on TA
random access response it is incremented by 1 to the last counter update (either initial
command by the time difference (in seconds)
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:2.
1. on TA
random access response it is incremented by 1 to the last counter update (either initial
command by the time difference (in seconds)
8029: LTE • LTE1697:2.
1. on TA command
random accessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:2.
1. on TA
random access response it is incremented by 1 to the last counter update (either initial
command by the time difference (in seconds)
8029: LTE • LTE1697:1.
2. on random
TA commandaccessbyresponse
the time difference (in seconds)
it is incremented by 1 to the last counter update (either initial
8029: LTE • LTE1697:2. on TA command by the time difference (in seconds) to the last counter update (either initial
8029: LTE MAC The counter is updated when the eNB receives the msg3 in case of a contention-based RACH
8029: LTE MAC The counter is updated when the eNB receives the msg3 in case of any kind of contention-bas
8030: LTE • LTE1117 This
eNB-internal
counter isaverage
updated calculation
when MBMS of the number
user of transmitted.
data is activated MBMS sessions in the cell (Multim
8030: LTE • LTE1117 Only MBMS user data are taken into account; signalling data are not taken into account (Multim
8030: LTE • LTE1117 This counter is updated when MBMS user data is received.
sing packet sequence 8030: LTE • LTE1117 The counter is updated when MBMS user data is lost.
8030: LTE • LTE1117 The counter is updated when MBMS user data is dropped.
(3GPP TS 25.446) pack8030: LTE • LTE1117 The counter is updated when MBMS user data is dropped.
10 MHz refers to PRB#0 to PRB#5
8031: LTE • LTE1491:15
10 MHz and 20toMHz
refers refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to
refers to PRB#0 to PRB#5PRB#0 to PRB#7
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to
refers to PRB#0 to PRB#5PRB#0 to PRB#7
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to
refers to PRB#0 to PRB#5PRB#0 to PRB#7
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to
refers to PRB#0 to PRB#5PRB#0 to PRB#7
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to
refers to PRB#0 to PRB#5PRB#0 to PRB#7
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to
refers to PRB#0 to PRB#5PRB#0 to PRB#7
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#0 to PRB#7
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#8 to PRB#15
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#8 to PRB#15
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#8 to PRB#15
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#8 to PRB#15
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#8 to PRB#15
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#8 to PRB#15
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:15 MHz and 20 MHz refers to PRB#16 to PRB#23
10 MHz refers to PRB#12 to PRB#17
8031: LTE • LTE1491:15
10 MHz and 20toMHz
refers referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#18 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#18 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#18 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#18 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#18 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:15 MHz and 20 MHz refers to PRB#40 to PRB#47
10 MHz refers to PRB#30 to PRB#35
8031: LTE • LTE1491:15
10 MHz and 20toMHz
refers referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#48 to PRB#55
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#48 to PRB#55
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#48 to PRB#55
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#48 to PRB#55
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#48 to PRB#55
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:15 MHz and 20 MHz refers to PRB#64 to PRB#71
10 MHz refers to PRB#48 to PRB#49
8031: LTE • LTE1491:15
10 MHz and 20toMHz
refers referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#64 to PRB#71
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#64 to PRB#71
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#64 to PRB#71
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#64 to PRB#71
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:15 MHz and 20 MHz refers to PRB#64 to PRB#71
refers to PRB#72 to PRB#74
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:20 MHz refers to PRB#72 to PRB#79
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement
10 MHz is updated
refers to PRB#0 for each UE every TTI by using the UE's most recent subband C
to PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#0 to PRB#7
refers to PRB#0 to PRB#5
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#0 to PRB#7
refers to PRB#0 to PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:15 MHz and 20 MHz refers to PRB#0 to PRB#7
10 MHz refers to PRB#0 to PRB#5
8031: LTE • LTE1491:15
10 MHz and 20toMHz
refers refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to
refers to PRB#0 to PRB#5PRB#0 to PRB#7
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#0 to to PRB#0 to PRB#7
PRB#5
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to
refers to PRB#0 to PRB#5PRB#0 to PRB#7
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#0 to PRB#7
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#8 to PRB#15
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#8 to PRB#15
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#8 to PRB#15
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#8 to PRB#15
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#8 to PRB#15
refers to PRB#6 to PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz refers
PRB#6 to to PRB#8 to PRB#15
PRB#11
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#8 to PRB#15
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#16 to PRB#23
refers to PRB#12 to PRB#17
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#17
PRB#12 PRB#16 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#16 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#18 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#18 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:15 MHz and 20 MHz refers to PRB#24 to PRB#31
10 MHz refers to PRB#18 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20toMHz
refers referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#18 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#18 to PRB#23
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#24 to PRB#31
refers to PRB#18 to PRB#23
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#23
PRB#18 PRB#24 to PRB#31
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#24 to PRB#31
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#29
PRB#24 PRB#32 to PRB#39
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#24 to PRB#29
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#32 to PRB#39
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#30 to PRB#35
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:15 MHz and 20 MHz refers to PRB#40 to PRB#47
10 MHz refers to PRB#30 to PRB#35
8031: LTE • LTE1491:15
10 MHz and 20toMHz
refers referstotoPRB#35
PRB#30 PRB#40 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#40 to PRB#47
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#48 to PRB#55
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#48 to PRB#55
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#48 to PRB#55
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#48 to PRB#55
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#48 to PRB#55
refers to PRB#36 to PRB#41
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#41
PRB#36 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#48 to PRB#55
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#42 to PRB#47
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#47
PRB#42 PRB#56 to PRB#63
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#56 to PRB#63
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#64 to PRB#71
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#64 to PRB#71
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#64 to PRB#71
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#64 to PRB#71
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:15 MHz and 20 MHz refers to PRB#64 to PRB#71
10 MHz refers to PRB#48 to PRB#49
8031: LTE • LTE1491:15
10 MHz and 20toMHz
refers referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:15
10 MHz and 20 MHz refers to PRB#64 to PRB#71
refers to PRB#48 to PRB#49
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:10
15 MHz refers
and 20toMHz referstotoPRB#49
PRB#48 PRB#64 to PRB#71
8031: LTE • LTE1491:15 MHz refers
and 20toMHz referstotoPRB#74
PRB#72 PRB#64 to PRB#71
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:15
20 MHz refers to PRB#72 to PRB#74
PRB#79
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:20
15 MHz refers to PRB#72 to PRB#79
PRB#74
8031: LTE • LTE1491:20 MHz refers to PRB#72 to PRB#79
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent subband C
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This measurement is updated for each UE every TTI by using the UE's most recent wideband
8031: LTE • LTE1491:This
- Cellmeasurement is updated for each UE every TTI by using the UE's most recent wideband
- RLF-Report.failedPCellId
8032: LTE • LTE1749 - Cell
UTRAN frequency - UTRAN (WCDMA or TD-SCDMA) frequency associated with RLF-Repor
- RLF-Report.failedPCellId
8032: LTE • LTE1749 - Cell
UTRAN frequency
- source - UTRAN
handover cell (WCDMA) frequency associated with RLF-Report.selectedUTRA
8032: LTE • LTE1749 - Cell
UTRAN frequency
- source - UTRAN
handover cell (WCDMA or TD-SCDMA) frequency associated with the target U
8032: LTE • LTE1749 The
- UTRAN frequency
configured B2T1- UTRAN
threshold(WCDMA)
for PSHOfrequency associated
was met based on thewith
lastthe target UTRAN
reported cell RSR
serving cell
8032: LTE • LTE1749 The
last reported
configured serving
B2T1cell RSRP for
threshold measurement
VoLTE was<met
b2Threshold1Utra
based on the last- (hysB2ThresholdUtra*2)
reported serving cell RSR (
8032: LTE • LTE1749 last reported serving
- LTE55 is activated cell RSRP measurement < b2Threshold1UtraQci1 - (hysB2ThresholdUtra
8033: LTE • LTE1879:- The reported measResults.measResultPCell.rsrpResult
LTE2112/LTE64 is activated value is less than or equal to the con
8033: LTE • LTE1879:- LTE56
The reported measResults.measResultPCell.rsrpResult value is less than or equal to the con
is activated
8033: LTE • LTE1879:- LTE2112/LTE64
The reported measResults.measResultPCell.rsrpResult
is activated value is less than or equal to the con
8033: LTE • LTE1879:- LTE1198
The reported measResults.measResultPCell.rsrpResult value is less than or equal to the con
is activated
8033: LTE • LTE1879:- LTE423
The reported measResults.measResultPCell.rsrqResult value is less than or equal to the con
is activated
8033: LTE • LTE1879:- LTE1407
The reported measResults.measResultPCell.rsrpResult value is less than or equal to the con
is activated
8033: LTE • LTE1879:This
- Thecounter
reported is measResults.measResultPCell.rsrqResult value is less RRC
updated following the reception of an A2 event-related than or equal to the Rep
Measurement con
8033: LTE • LTE1879:- The reported measResults.measResultPCell.rsrpResult
LTE2112/LTE64 is activated value is greater than or equal to the c
8033: LTE • LTE1879:- The reported measResults.measResultPCell.rsrpResult value is greater than or equal to the c
sent by
elease. 8034: LTE • LTE2051:This counter is updated following the transmission of RRC Connection Reconfiguration messa
hich event A4 is reported.
8034: LTE • LTE2051:This counter is updated following a positive evaluation of the received RRC Measurement Rep
8035: LTE • LTE1559 The eNB continuously counts the sent chunks but updates the statistics every 5 seconds.
8035: LTE • LTE1559 The eNB continuously counts the received chunks but updates the statistics every 5 seconds.
8035: LTE • LTE1559 The eNB continuously counts the resent chunks but updates the statistics every 5 seconds.
ata and the SCTP layer8035: LTE • LTE1559 The eNB continuously monitors the state of the SCTP association but updates the statistics ev
8035: LTE • LTE1559 The eNB continuously monitors the state changes of the SCTP association but updates the st
8035: LTE • LTE1559 The eNB continuously monitors the state of the SCTP association but updates the statistics ev
8035: LTE • LTE1559 The eNB continuously monitors the state changes of the SCTP association but updates the sta
8036: LTE • LTE1559 The eNB continuously counts the sent chunks but updates the statistics every 5 seconds.
8036: LTE • LTE1559 The eNB continuously counts the received chunks but updates the statistics every 5 seconds.
8036: LTE • LTE1559 The eNB continuously counts the resent chunks but updates the statistics every 5 seconds.
ata and the SCTP layer8036: LTE • LTE1559 The eNB continuously monitors the state of the SCTP association but updates the statistics ev
8036: LTE • LTE1559 The eNB continuously monitors the state changes of the SCTP association but updates the st
8036: LTE • LTE1559 The eNB continuously monitors the state of the SCTP association but updates the statistics ev
8036: LTE • LTE1559 The eNB continuously monitors the state changes of the SCTP association but updates the sta
8037: LTE • LTE1559 The eNB continuously counts the sent chunks but updates the statistics every 5 seconds.
8037: LTE • LTE1559 The eNB continuously counts the received chunks but updates the statistics every 5 seconds.
8037: LTE • LTE1559 The eNB continuously counts the resent chunks but updates the statistics every 5 seconds.
ata and the SCTP layer8037: LTE • LTE1559 The eNB continuously monitors the state of the SCTP association but updates the statistics ev
8037: LTE • LTE1559 The eNB continuously monitors the state changes of the SCTP association but updates the sta
8037: LTE • LTE1559 The eNB continuously monitors the state of the SCTP association but updates the statistics ev
8037: LTE • LTE770:
LTE1559Basic
The eNB continuously
Performance monitors
Counter the state
Collection II changes of the SCTP association but updates the st
51120: LTE• LTE770:
LTE125: Basic
IPv6
The counter
for U/C-Plane
is updated
Performance whenCollection
Counter an inboundII packet has been delivered to higher-layer protocols.
51120: LTE• LTE770: The counter
LTE125: Basic
IPv6 for is updated
U/C-Plane
Performance whenever
Counter a kilo-byte
Collection II is received on the plain IP interface.
51120: LTE• LTE770:
LTE125: Basic
IPv6
The counter
for U/C-Plane
is updated
Performance whenever
Counter a packet
Collection II has been transmitted successfully over the plain IP
51120: LTE• LTE125: IPv6
The counter
for U/C-Plane
is updated whenever a kilo-byte is transmitted over the plain IP interface.
51120: LTE• LTE770:
IP StatistiThe counter is updated
Basic Performance whenever
Counter an erroneous
Collection II packets is received on the plain IP interface.
51120: LTE• LTE125: IPv6
The counter is updated when an outbound packet needs to be dropped due to congestion.
for U/C-Plane
51120: LTE IP StatistiThe counter is updated when a kilo-byte of outbound data needs to be dropped due to conges
51120: LTE IP StatistiThe counter is updated when an IP multicast packet or fragment has been received.
51120: LTE IP StatistiThe counter is updated whenever a kilo-byte of data is received in IP Multicast packets or fragm
51120: LTE IP StatistiThe counter is updated when an IP Multicast packet or fragment has been transmitted.
51120: LTE IP StatistiThe
- Thecounter
NE didisnot
updated
join thewhenever a kilo-byte
corresponding of data group
IP multicast is transmitted in IP multicast
on the interface on whichpackets or fr
this packe
51120: LTE IP Statisti- The NE
destination MAC
did not join address
the does notIPmatch
corresponding with group
multicast the destination MAC address
on the interface on which calculated
this packefr
51120: LTE IP Statisti- The destination MAC address does not match with the destination MAC address calculated fr
51121: LTE• LTE806: The counter is updated when a kilo-byte of outbound data is transmitted over the plain IP inter
51121: LTE• LTE806: The counter is updated when a packet is transmitted over the plain IP interface within the PHB
51121: LTE• LTE806: The counter is updated when a kilo-byte of outbound data needs to be dropped due to conges
51121: LTE• LTE806: The counter is updated when an outbound packet needs to be dropped due to congestion with
51121: LTE• LTE806: The counter is updated when a kilo-byte is transmitted over the plain IP interface within the PH
51121: LTE• LTE806: The counter is updated when a packet is transmitted over the plain IP interface within the PHB
51121: LTE• LTE806: The counter is updated when a kilo-byte of outbound data needs to be dropped due to conges
51121: LTE• LTE806: The counter is updated when an outbound packet needs to be dropped due to congestion with
51121: LTE• LTE806: The counter is updated when a kilo-byte is transmitted over the plain IP interface within the PH
51121: LTE• LTE806: The counter is updated when a packet is transmitted over the plain IP interface within the PHB
51121: LTE• LTE806: The counter is updated when a kilo-byte of outbound data needs to be dropped due to conges
51121: LTE• LTE806: The counter is updated when an outbound packet needs to be dropped due to congestion with
51121: LTE• LTE806: The counter is updated when a kilo-byte is transmitted over the plain IP interface within the PH
51121: LTE• LTE806: The counter is updated when a packet is transmitted over the plain IP interface within the PHB
51121: LTE• LTE806: The counter is updated when a kilo-byte of outbound data needs to be dropped due to conges
51121: LTE• LTE806: The counter is updated when an outbound packet needs to be dropped due to congestion with
51121: LTE• LTE806: The counter is updated when a kilo-byte is transmitted over the plain IP interface within the PH
51121: LTE• LTE806: The counter is updated when a packet is transmitted over the plain IP interface within the PHB
51121: LTE• LTE806: The counter is updated when a kilo-byte of outbound data needs to be dropped due to conges
51121: LTE• LTE806: The counter is updated when an outbound packet needs to be dropped due to congestion with
51121: LTE• LTE806: The counter is updated when a kilo-byte is transmitted over the plain IP interface within the PH
51121: LTE• LTE806: The counter is updated when a packet is transmitted over the plain IP interface within the PHB
51121: LTE• LTE806: The counter is updated when a kilo-byte of outbound data needs to be dropped due to conges
51121: LTE• LTE806: The counter is updated when an outbound packet needs to be dropped due to congestion with
51121: LTE• LTE806: The counter is updated when a kilo-byte is received on the plain IP interface within the PHB cla
51121: LTE• LTE806: The counter is updated when a packet is received on the plain IP interface within the PHB cla
51121: LTE• LTE806: The counter is updated when a kilo-byte is received on the plain IP interface within the PHB cl
51121: LTE• LTE806: The counter is updated when a packet is received on the plain IP interface within the PHB cla
51121: LTE• LTE806: The counter is updated when a kilo-byte is received on the plain IP interface within the PHB c
51121: LTE• LTE806: The counter is updated when a packet is received on the plain IP interface within the PHB cla
51121: LTE• LTE806: The counter is updated when a kilo-byte is received on the plain IP interface within the PHB cla
51121: LTE• LTE806: The counter is updated when a packet is received on the plain IP interface within the PHB cla
51121: LTE• LTE806: The counter is updated when a kilo-byte is received on the plain IP interface within the PHB cl
51121: LTE• LTE806: The counter is updated when a packet is received on the plain IP interface within the PHB cla
51121: LTE• LTE806: The counter is updated when a kilo-byte is received on the plain IP interface within the PHB cl
51121: LTE• LTE806: The counter is updated when a packet is received on the plain IP interface within the PHB cla
51123: LTE• LTE770: B The counter is incremented every second by the number of kilo-bytes received in valid Etherne
51123: LTE• LTE770: BThe counter is incremented every second by the number of kilo-bytes transmitted in valid Ethe
51123: LTE• LTE770: BThe counter is incremented every second by the number of Ethernet frames received by the in
51123: LTE• LTE770: BThe counter is incremented every second by the number of Ethernet frames transmitted by the
51123: LTE• LTE770: BThe counter is incremented every second by the number of errored Ethernet frames received b
51123: LTE• LTE649: The counter is incremented for every ingress Ethernet frames that is discarded due to rate limi
51123: LTE Ethernet The counter is incremented every second by the number of Ethernet packets to be received th
51123: LTE• LTE649: The counter is incremented every second by the number of Ethernet frames to be transmitted
51123: LTE• LTE649: The counter is incremented every second by the number of Ethernet frames to be transmitted
51123: LTE• LTE649: The counter is incremented every second by the number of Ethernet frames to be transmitted
51123: LTE• LTE649: The counter is incremented every second by the number of Ethernet frames to be transmitted
51123: LTE• LTE649: The counter is incremented every second by the number of Ethernet frames to be transmitted
51123: LTE• LTE649: The counter is incremented every second by the number of Ethernet frames to be transmitted
51125: LTE• LTE689: LThe counter is updated when an outbound packet related to a protect policy is transmitted suc
51125: LTE• LTE689: LNOTE:
The counter is updated
Discarded packetwhen an received
matching the defaultESPpolicy
packetswilladdressed to a local
not be counted with tunnel endpoint w
this counter._x00
51125: LTE• LTE689: LNote 2: The default policy is DISCARD until IPSec policies are configured.
51125: LTE• LTE689: LThe counter is updated when a packets not addressed to an local tunnel endpoint or packets w
51125: LTE• LTE689: LThe counter is updated for every packet that is bypassed in egress direction.
51125: LTE• LTE689: LThe counter is updated for every packet not addressed to an local tunnel endpoint or packets w
51126: LTE• LTE692: The counter is updated for every packet that is dropped due to ingress rate limiting.
51126: LTE• LTE132:
LTE692: VLAN
The counter
based is updated
traffic for every packet that is discarded due to filter violations.
separation
51127: LTE• LTE132:
LTE125: VLAN
IPv6
The counter
for U/C-Plane
based is updated
traffic when an inbound packet has been delivered to higher-layer protocols.
separation
51127: LTE• LTE132:
LTE125: VLAN
IPv6
The counter
for U/C-Plane
based is updated
traffic whenever a kilo-octet is received on the VLAN IP interface.
separation
51127: LTE• LTE132:
LTE125: VLAN
IPv6
The counter
for U/C-Plane
based is updated
traffic whenever a packet has been transmitted successfully over the VLAN i
separation
51127: LTE• LTE125: IPv6
The counter is updated whenever a kilo-byte is transmitted over the VLAN IP interface.
for U/C-Plane
51127: LTE• LTE132:
VLAN IP VLAN
St
The counter
based is updated
traffic whenever an erroneous packets is received on the VLAN IP interface.
separation
51127: LTE• LTE125: IPv6
The counter
for U/C-Plane
is updated when an outbound packet needs to be dropped due to congestion.
51127: LTE VLAN IP StThe counter is updated when a kilo-byte of outbound data needs to be dropped due to conges
51127: LTE VLAN IP StThe counter is updated when an IP multicast packet or fragment has been received.
51127: LTE VLAN IP StThe counter is updated whenever a kilo-byte of data is received in IP Multicast packets or fragm
51127: LTE VLAN IP StThe counter is updated when an IP Multicast packet or fragment has been transmitted.
51127: LTE VLAN IP St-The
Thecounter
NE didisnot
updated
join thewhen a kilo-byteIP
corresponding of multicast
an IP Multicast
group onpacket or fragment
the interface has been
on which this transm
packe
51127: LTE VLAN IP St destination
- The NE MAC
did not join address
the does notIPmatch
corresponding with group
multicast the destination MAC address
on the interface on which calculated
this packefr
51127: LTE• LTE770:
VLAN IP Basic
St
- The Performance
destination MAC address
Counter does not
Collection II match with the destination MAC address calculated fr
51128: LTE• LTE806:
LTE770: Performance
The counter
Basic isCounter
updated
Performance Plus
when
Counter Package
a kilo-byte
forIITransport
Collection is transmitted
I within the PHB class.
51128: LTE• LTE806: The counter
Performance is updated
Counter when
Plus a packet
Package
LTE770: Basic Performance Counter Collection II for is transmitted
Transport I within the PHB class.
51128: LTE• LTE806: Performance
The counter isCounter
updated Plus
whenPackage
a kilo-byte
LTE770: Basic Performance Counter Collection II for Transport
of outboundI data needs to be dropped due to conges
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
updated
Performance Plus
when
Counter Package
a packetforIIneeds
Collection Transport
to beI dropped due to congestion within the PHB
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
updated
Performance Plus
when
Counter Package
a kilo-byte
forIITransport
Collection is transmitted
I within the PHB class.
51128: LTE• LTE770: The counter
LTE806: Basic
Performance isCounter
updated
Performance when
Plus
Counter a packet
Package forIIisTransport
Collection transmitted
I within the PHB class.
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
updated
Performance Plus
when
Counter Package
a kilo-byte
forIITransport
Collection is dropped I due to congestion within the PHB class.
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
updated
Performance Plus
when
Counter Package
a packetforIIneeds
Collection Transport
to beI dropped due to congestion within the PHB
51128: LTE• LTE806:
LTE770: Performance
The counter
Basic isCounter
updated
Performance Plus
when
Counter Package
a kilo-byte
forIITransport
Collection is transmitted
I within the PHB class.
51128: LTE• LTE806: Performance
The counter isCounter
updated Plus
whenPackage
a packet
LTE770: Basic Performance Counter Collection II for is Transport
transmitted
I within the PHB class.
51128: LTE• LTE806: Performance
The counter isCounter
updated Plus
whenPackage
a kilo-byte
LTE770: Basic Performance Counter Collection II for Transport
of outboundI data needs to be dropped due to conges
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
updated
Performance Plus
when
Counter Package
a packetforIIneeds
Collection Transport
to beI dropped due to congestion within the PHB
51128: LTE• LTE770: The counter
LTE806: Basic
Performance isCounter
updated
Performance when
Plus
Counter a kilo-byte
Package is transmitted
forIITransport
Collection I within the PHB class.
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
updated
Performance Plus
when
Counter Package
a packetforIIisTransport
Collection transmitted
I within the PHB class.
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
updated
Performance Plus
when
Counter Package
a kilo-byte
forIITransport
Collection of outboundI data needs to be dropped due to conges
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
updated
Performance Plus
when
Counter Package
a packetforIIneeds
Collection Transport
to beI dropped due to congestion within the PHB
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
updated
Performance Plus
when
Counter Package
a kilo-byte
forIITransport
Collection is transmitted
I within the PHB class.
51128: LTE• LTE806: Performance
The counter isCounter
updated Plus
whenPackage
a packet
LTE770: Basic Performance Counter Collection II for is Transport
transmitted
I within the PHB class.
51128: LTE• LTE806: Performance
The counter isCounter
updated Plus
whenPackage
a kilo-byte
LTE770: Basic Performance Counter Collection II for Transport
of outboundI data needs to be dropped due to conges
51128: LTE• LTE770: The
LTE806: Basic counter
Performance is updated
Counter
Performance when a packet
Plus Package
Counter needs to
forIITransport I
Collection be dropped due to congestion within the PHB
51128: LTE• LTE806: Performance
The counter isCounter
updated Plus
whenPackage
a kilo-byte
for Transport
is transmitted
I within the PHB class.
• LTE770: Basic Performance Counter Collection II
51128: LTE• LTE806:
LTE770: Performance
The counter
Basic isCounter
Performanceupdated Plus
when
Counter Package
a packet
Collection forIIisTransport
transmitted I within the PHB class.
51128: LTE• LTE806: Performance
The counter isCounter
updated Plus
whenPackage
a
LTE770: Basic Performance Counter Collection IIkilo-byte
for Transport
of outbound I data needs to be dropped due to conges
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
Performanceupdated Plus
when
Counter Package
a packet
Collection forIIneeds
Transportto beI dropped due to congestion within the PHB
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
Performanceupdated Plus
when
Counter Package
a kilo-byte
Collection forIITransport
is received I within the PHB class.
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
Performanceupdated Plus
when
Counter Package
a packet
Collection forIIisTransport
received Iwithin the PHB class.
51128: LTE• LTE770: The counter
LTE806: Basic
Performance isCounter
Performanceupdated when
Plus
Counter a kilo-byte
Package
Collection is received
forIITransport I within the PHB class.
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
Performanceupdated Plus
when
Counter Package
a packet
Collection forIIisTransport
received Iwithin the PHB class.
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
Performanceupdated Plus
when
Counter Package
a kilo-byte
Collection forIITransport
is received I within the PHB class.
51128: LTE• LTE806: Performance
The counter isCounter
updated Plus
whenPackage
a
LTE770: Basic Performance Counter Collection IIpacket for is Transport
received Iwithin the PHB class.
51128: LTE• LTE806: The counter
Performance is updated
Counter when
Plus a kilo-byte
Package
LTE770: Basic Performance Counter Collection II for is received
Transport I within the PHB class.
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
Performanceupdated Plus
when
Counter Package
a packet
Collection forIIisTransport
received Iwithin the PHB class.
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
Performanceupdated Plus
when
Counter Package
a kilo-byte
Collection forIITransport
is received I within the PHB class.
51128: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
Performanceupdated Plus
when
Counter Package
a packet
Collection forIIisTransport
received Iwithin the PHB class.
51128: LTE• LTE806: Performance
The counter isCounter
updated Plus
whenPackage
a kilo-byte
for Transport
is received I within the PHB class.
51128: LTE• LTE770:
VLAN PHB The counter
Basic is updated
Performance whenCollection
Counter a packet IIis received within the PHB class.
51129: LTE• LTE806: Performance
The counter isCounter
incremented
Plus Package
when a frame
for Transport
is received I on the interface.
51129: LTE• LTE770:
VLAN StatThe counter is incremented when
Basic Performance Counter Collection II a kilo-octet is received on the interface.
51129: LTE• LTE806: Performance
The counter isCounter
incremented
Plus Package
when
LTE770: Basic Performance Counter Collection II a frame
for Transport
is transmitted
I over the interface.
51129: LTE• LTE806: Performance
The counter isCounter
incremented
Plus Package
when a kilo-octet
for Transport is transmitted
I over the interface.
51130: LTE ETH_IF St The counter is updated when a frame is received on the interface.
51130: LTE• LTE770:
ETH_IF StThe counter
Basic is updated
Performance whenCollection
Counter an octet is II received on the interface.
51130: LTE• LTE770:
LTE806: Basic
Performance
The counter isCounter
Performanceupdated Plus
when
Counter Package
a frameforisIITransport
Collection transmitted I over the interface.
51130: LTE• LTE806: Performance
The counter isCounter
updated
in Plus
hardwarewhenPackage
an octet
implemented forisTransport
transmitted
as 16 bit Icounter,
over the interface.
therefore it is possible that it rolls ov
51130: LTE ETH_IF St
51130: LTE ETH_IF St The counter is updated when a valid Ethernet Multicast frame conveying IP payload is received
51130: LTE ETH_IF St The counter is updated when a valid Ethernet Multicast frame generated by an IP application o
51132: LTE• LTE574: The counter is updated for every reply message to a TWAMP initiator message that the BTS h
51132: LTE• LTE574: The counter is updated for every reply message to a TWAMP initiator message that the BTS h
51132: LTE• LTE574: The counter is updated for every lost replyTWAMP
message to a TWAMP
message for theinitiator
session.message that the BTS h
51132: LTE• LTE574:
51132: LTE• LTE574: The counter is updated for every transmitted TWAMP message for the session.
51136: LTE TAC StatisCounter is incremented with each successful normal setup request message.
51136: LTE• LTE144: TCounter is incremented with each successful handover setup request message.
51136: LTE• LTE144: TCounter is incremented with each successful handover setup request message.
51136: LTE• LTE144: TCounter is incremented with each rejected normal setup request.
51136: LTE• LTE144: TCounter is incremented with each rejected handover setup request.
51136: LTE• LTE144: TTotal
Counter
UL isGBR
incremented with each
rate is measured rejected
within sampling emergency setup request.
interval.
51136: LTE• LTE1401 Total
At theUL
end of the
GBR measurement
rate is measured period (e.g. 15 min.)
within sampling the mean value is calculated and stored i
interval.
51136: LTE• LTE1401 Total
At theDL
end of the
GBR measurement
rate is measured period (e.g. 15 min.)
within sampling the max. value is stored in the performanc
interval.
51136: LTE• LTE1401 Total
At theDL
end of the
GBR measurement
rate is measured period (e.g. 15 min.)
within sampling the mean value is calculated and stored i
interval.
51136: LTE• LTE1401 The
At the end ofisthe
counter measurement
incremented period
every second(e.g.by15 themin.) the max.
number value isToP
of received stored in event
sync the performanc
message
51138: LTE TOP Phase Calculated value is representing value of the last
"The value is updated every minute using the following formula: 15min period of time. Counter value is cleare
51138: LTE TOP Phase minValue = min (minValue, actualValue)"
"The value is updated every minute using the following formula:
51138: LTE TOP Phase aveValueNew = (aveValueOld
"The value is updated * (actualIntervalLength
every minute using the following- formula: 1) + actualValue) / actualIntervalLength
51138: LTE TOP Phase maxValue = max (maxValue, actualValue)"
51138: LTE TOP Phase The number of seconds during this interval while the timing over packet phase synchronisation
8006: LTE • LTE651: The transmission of an S1AP:Initial Context Setup Response or an S1AP:E-RAB SETUP RES
8006: LTE • LTE651: The transmission of an S1AP:Initial Context Setup Response or an S1AP:E-RAB SETUP RES
8006: LTE • LTE651: The transmission of an S1AP:Initial Context Setup Response or an S1AP:E-RAB SETUP RES
8006: LTE • LTE651: This
The transmission of an S1AP:Initial
counter is updated when the S1AP:Context UE Setup
CONTEXT Response
RELEASEor an REQUEST
S1AP:E-RAB SETUP(eNB
message RES
8006: LTE • LTE651: This counter is also updated with the number of released E-RABs.
updated when the S1AP: UE CONTEXT RELEASE REQUEST message (eNB
8006: LTE • LTE651: This counter
- Radio is alsonot
resources updated with the number of released E-RABs.
available
8006: LTE • LTE651: -This
CS counter
FallbackisTriggered
also updated with the number of released E-RABs.
8006: LTE • LTE761: AThis counter is also updated with the number of released E-RABs.
• LTE9: Service
This counter
differentiation
updated when the S1AP: UE CONTEXT RELEASE REQUEST message (eNB ->
8006: LTE • LTE7:
LTE9: Support
This counter
Service of multiple
is also
EPSupdated
differentiation
updatedbearer
whenwith
the the number
S1AP: of releasedRELEASE
UE CONTEXT QCI1 E-RABs.
REQUEST message (eNB
8006: LTE • LTE7: Support
This
LTE9: Service counter
- Radioof multiple
is also
EPS
differentiation updated
bearer
resources not available with the number of released QCI1 E-RABs.
8006: LTE • LTE9:
LTE7: Service
Support
-This
CS counter
of multiple
Fallback isTriggered
also
EPSupdated
differentiation bearer with the number of released QCI1 E-RABs.
8006: LTE • LTE7: Support
This counter
of multiple
Transmission isofalso
EPS
an updated
bearer
S1AP: with the
E-RAB number INDICATION
RELEASE of released QCI1 E-RABs.
message (eNB -> MME; 3GPP TS
8006: LTE • LTE534: Transmission
The counter isofupdated
an S1AP:withE-RAB
the number of released
RELEASE GBR bearers.
INDICATION message (eNB -> MME; 3GPP TS
8006: LTE • LTE534: S1AP
The counter is updated
UE CONTEXT with the number
RELEASE COMMAND)of released non-GBR bearers.
8007: LTE • LTE651: 3GPP TS36423 (X2AP UE CONTEXT RELEASE)
8007: LTE • LTE651: 3GPP TS36.413 ( S1AP UE CONTEXT RELEASE REQUEST)
8007: LTE • LTE651: 3GPP TS36.413 (S1AP E-RAB RELEASE INDICATION, S1AP UE CONTEXT RELEASE REQ
8007: LTE • LTE761: A3GPP TS36.413 (S1AP: UE CONTEXT RELEASE REQUEST)
8012: LTE • LTE770: BThis counter is updated when a PDCP SDU is received from UE.
8012: LTE • LTE770: BThis counter is updated when a PDCP SDU is transmitted towards the UE.
8013: LTE • LTE651: The
An internal message
reception fromConnection
of an RRC the RRM Request message sent by the UE to eNB.
8013: LTE • LTE651: Note: If a UE (erroneously) sends this message several times in a row without waiting the prop
Request message to MME.
Response message sent by MME.
ST message sent by MME to the eNB in case this message contains the UE-AMBR value.
WARNING RESPONSE message is sent to the MME and the Broadcast Completed Area List IE is not included.
essage is sent to the MME and the Broadcast Cancelled Area List IE is not included.
K NAS TRANSPORT message to the MME.
WNLINK NAS TRANSPORT message sent by the MME to the eNB.
NB <- MME) in case that this message contains the ARP (Allocation and Retention Priority) priority level which is used for emergency sessio
e (eNB -> MME) in case that this message contains the E-RAB ID of the IMS emergency session in the E-RAB Setup List AND was sent in
e (eNB -> MME) in case that this message contains the E-RAB ID of the IMS emergency session in the E-RAB Failed to Setup List (becau
ssage sent by MME to the eNB.
ng 'SON Information Reply' with 'X2 TNL Configuration Info'
uding 'SON Information Request' for 'X2 TNL Configuration Info'.
e last detected delay value at the transmission of the SDU via S1 interface.
ast detected delay value at the transmission of the SDU via S1 interface.
y value at the transmission of the SDU via S1 interface.
onse excluded.
onse excluded.
onse excluded.
onse excluded.
onse excluded.
onse excluded.
onse excluded.
onse excluded.
onse excluded.
onse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ponse excluded.
ted for the first time on the RLC level
ed on the RLC level.
PDU is received
H or DTCH is transmitted first time on RLC level.
s transmitted first time on the RLC level.
ed. Valid for duplicate AMD PDU, AMD PDU segment and UMD PDU.
he RLC level for a UL RLC PDU.
ed. Duplicate RLC PDU's received and RLC PDU's received outside of the reception window trigger updates to this counter.
ffered DL RLC data is updated to this counter. DL RLC buffer status is sampled for each active TTI, where data is in the DL RLC buffer for
buffer is updated to this counter. DL RLC buffer status is sampled for each active TTI, where data is in the DL RLC buffer for at least one U
level 1 and it is stopped when Overload level 1 is left.
value is the arithmetical average of samples taken from the number of UE contexts with UL buffered data. The UL buffer status is sampled f
maximum number of UE contexts with UL buffered data is updated to this counter. UL buffer status is sampled for each active TTI, where d
level 2 and it is stopped when Overload level 2 is left.
s during the measurement period. RLC UM: Transmission of an PDCP SDU towards the UE. RLC AM: When MAC layer informs PDCP of a
eNB without having started the transmission.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
B CoMP in each TTI when PUSCH is scheduled.
hmetical average of samples each representing the number of UEs in RRC_CONNECTED state at that moment.
ak number of UEs in RRC_CONNECTED state during the measurement period.
which are paired by UL MU-MIMO.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
s, except when there is no data in the buffer.
s, except when there is no data in the buffer.
s, except when there is no data in the buffer.
s, except when there is no data in the buffer.
s, except when there is no data in the buffer.
s, except when there is no data in the buffer.
he average number of PRBs available for dynamic scheduling of user plane traffic (DCCH and DTCH).
he average number of PRBs available for dynamic scheduling of user plane traffic (DCCH and DTCH).
k on BCCH towards the UE.
CCCH towards the UE.
PCCH towards the UE.
CH from UE.
surement period.
ffered DL RLC data for QCI1 bearer is updated to this counter. DL RLC buffer status is sampled for each active TTI, where data is in the DL
ffered DL RLC data for QCI2 bearer is updated to this counter. DL RLC buffer status is sampled for each active TTI, where data is in the DL
ffered DL RLC data for QCI3 bearer is updated to this counter. DL RLC buffer status is sampled for each active TTI, where data is in the DL
ffered DL RLC data for QCI4 bearer is updated to this counter. DL RLC buffer status is sampled for each active TTI, where data is in the DL
ent viavia
s sent SIB10.
SIB11.
updated
IB12. when the last segment is sent.
updated when the last segment is sent.
Es with UE Category 8 (3GPP TS 36.306, 36.331); the average is calculated as the arithmetical average over the measurement period.
ffered DL RLC data for non-GBR bearer is updated to this counter. DL RLC buffer status is sampled for each active TTI, where data is in th
SIB, Paging and RA response excluded.
SIB, Paging and RA response excluded.
SIB, Paging and RA response excluded.
or PDSCH transmission using MCS29.
or PDSCH transmission using MCS30.
or PDSCH transmission using MCS31.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
transmissions has been exceeded for the TB.
dle NACK received on PDSCH using bundle size 2 from MCS29.
dle NACK received on PDSCH using bundle size 3 from MCS29.
dle NACK received on PDSCH using bundle size 4 from MCS29.
dle NACK received on PDSCH using bundle size 2 from MCS30.
dle NACK received on PDSCH using bundle size 3 from MCS30.
dle NACK received on PDSCH using bundle size 4 from MCS30.
dle NACK received on PDSCH using bundle size 2 from MCS31.
dle NACK received on PDSCH using bundle size 3 from MCS31.
dle NACK received on PDSCH using bundle size 4 from MCS31.
mple taken from the number of Active UEs with buffered data in DL.
Es is summed to counter SUM_ACTIVE_UE_DATA_DL.
mple taken from the number of Active UEs with buffered data in UL.
Es is summed to counter SUM_ACTIVE_UE_DATA_UL.
s thatof
ment are
thepre-selected
SDU. by L3 RRM for intra-eNB UL CoMP AND being scheduled for UL transmission
ment of the SDU.
ment of the SDU.
ment of the SDU.
ment of the SDU.
MCS25 is received.
MCS26 is received.
MCS27 is received.
MCS28 is received.
MCS25 is nacked.
MCS26 is nacked.
MCS27 is nacked.
MCS28 is nacked.
n air" in uplink.
Es that had data scheduled in DL.
n air" in downlink.
d level 1 and it is stopped when Overload level 1 is left.
d level 2 and it is stopped when Overload level 2 is left.
s delivered to higher layers.
s delivered to higher layers.
s delivered to higher layers.
s delivered
ment to higher layers.
of the SDU.
ment of the SDU.
ment of the SDU.
ment of the SDU.
ment of the SDU.
-In-Sync; the average is calculated as the arithmetical average over the measurement period.
ed UEs
time which
T of a UEhave
wasset the range
in the "deviceType" in the "UE-EUTRA-Capability" to "noBenFromBatConsumpOpt" (3GPP TS 36.331, TS 36.306); the
time T of a UE was in the range
time T of a UE was in the range
time T of a UE was in the range
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
B is detected
is upgraded. Both Outer Loop AMC and Inner Loop AMC decisions are considered.
is downgraded. Both Outer Loop AMC and Inner Loop AMC decisions are considered.
UCCH is smaller than the last cell-wide RSSI minimum.
UCCH is greater than the last cell-wide RSSI maximum.
d as follows: conversion from dBm into mW, arithmetic mean computation in mW and conversion back to dBm.
e on PUCCH is <= -120 dBm.
e on PUCCH is -120 dBm < x <= -118 dBm.
e on PUCCH is -118 dBm < x <= -116 dBm.
e on PUCCH is -116 dBm < x <= -114 dBm.
e on PUCCH is -114 dBm < x <= -112 dBm.
e on PUCCH is -112 dBm < x <= -110 dBm.
e on PUCCH is -110 dBm < x <= -108 dBm.
e on PUCCH is -108 dBm < x <= -106 dBm.
e on PUCCH is -106 dBm < x <= -104 dBm.
e on PUCCH is -104 dBm < x <= -102 dBm.
e on PUCCH is -102 dBm < x <= -100 dBm.
e on PUCCH is -100 dBm < x <= -98 dBm.
e on PUCCH is -98 dBm < x <= -96 dBm.
e on PUCCH is -96 dBm < x <= -94 dBm.
e on PUCCH is -94 dBm < x <= -92 dBm.
e on PUCCH is -92 dBm < x <= -90 dBm.
e on PUCCH is -90 dBm < x <= -88 dBm.
e on PUCCH is -88 dBm < x <= -86 dBm.
e on PUCCH is -86 dBm < x <= -84 dBm.
e on PUCCH is -84 dBm < x <= -82 dBm.
e on PUCCH is -82 dBm < x <= -80 dBm.
e on PUCCH is greater than -80 dBm.
USCH is smaller than the last cell-wide RSSI minimum.
USCH is greater than the last cell-wide RSSI maximum.
d as follows: conversion from dBm into mW, arithmetic mean computation in mW and conversion back to dBm.
e on PUSCH is <= -120 dBm.
e on PUSCH is -120 dBm < x <= -118 dBm.
e on PUSCH is -118 dBm < x <= -116 dBm.
e on PUSCH is -116 dBm < x <= -114 dBm.
e on PUSCH is -114 dBm < x <= -112 dBm.
e on PUSCH is -112 dBm < x <= -110 dBm.
e on PUSCH is -110 dBm < x <= -108 dBm.
e on PUSCH is -108 dBm < x <= -106 dBm.
e on PUSCH is -106 dBm < x <= -104 dBm.
e on PUSCH is -104 dBm < x <= -102 dBm.
e on PUSCH is -102 dBm < x <= -100 dBm.
e on PUSCH is -100 dBm < x <= -98 dBm.
e on PUSCH is -98 dBm < x <= -96 dBm.
e on PUSCH is -96 dBm < x <= -94 dBm.
e on PUSCH is -94 dBm < x <= -92 dBm.
e on PUSCH is -92 dBm < x <= -90 dBm.
e on PUSCH is -90 dBm < x <= -88 dBm.
e on PUSCH is -88 dBm < x <= -86 dBm.
e on PUSCH is -86 dBm < x <= -84 dBm.
e on PUSCH is -84 dBm < x <= -82 dBm.
e on PUSCH is -82 dBm < x <= -80 dBm.
e on PUSCH is greater than -80 dBm.
UCCH is smaller than the last cell-wide SINR minimum.
UCCH is greater than the last cell-wide SINR maximum.
d as follows: SINR mean value calculation must be done on dB (instead of linear ratio).
e on PUCCH is <= -10 dB.
e on PUCCH is -10 dB < x <= -8 dB.
e on PUCCH is -8 dB < x <= -6 dB.
e on PUCCH is -6 dB < x <= -4 dB.
e on PUCCH is -4 dB < x <= -2 dB.
e on PUCCH is -2 dB < x <= 0 dB.
e on PUCCH is 0 dB < x <= 2 dB.
e on PUCCH is 2 dB < x <= 4 dB.
e on PUCCH is 4 dB < x <= 6 dB.
e on PUCCH is 6 dB < x <= 8 dB.
e on PUCCH is 8 dB < x <= 10 dB.
e on PUCCH is 10 dB < x <= 12 dB.
e on PUCCH is 12 dB < x <= 14 dB.
e on PUCCH is 14 dB < x <= 16 dB.
e on PUCCH is 16 dB < x <= 18 dB.
e on PUCCH is 18 dB < x <= 20 dB.
e on PUCCH is 20 dB < x <= 22 dB.
e on PUCCH is 22 dB < x <= 24 dB.
e on PUCCH is 24dB < x <= 26 dB.
e on PUCCH is 26 dB < x <= 28 dB.
e on PUCCH is 28 dB < x <= 30 dB.
e on PUCCH is greater than 30 dB.
USCH is smaller than the last cell-wide SINR minimum.
USCH is greater than the last cell-wide SINR maximum.
d as follows: SINR mean value calculation must be done on dB (instead of linear ratio).
e on PUSCH is <= -10 dB.
e on PUSCH is -10 dB < x <= -8 dB.
e on PUSCH is -8 dB < x <= -6 dB.
e on PUSCH is -6 dB < x <= -4 dB.
e on PUSCH is -4 dB < x <= -2 dB.
e on PUSCH is -2 dB < x <= 0 dB.
e on PUSCH is 0 dB < x <= 2 dB.
e on PUSCH is 2 dB < x <= 4 dB.
e on PUSCH is 4 dB < x <= 6 dB.
e on PUSCH is 6 dB < x <= 8 dB.
e on PUSCH is 8 dB < x <= 10 dB.
e on PUSCH is 10 dB < x <= 12 dB.
e on PUSCH is 12 dB < x <= 14 dB.
e on PUSCH is 14 dB < x <= 16 dB.
e on PUSCH is 16 dB < x <= 18 dB.
e on PUSCH is 18 dB < x <= 20 dB.
e on PUSCH is 20 dB < x <= 22 dB.
e on PUSCH is 22 dB < x <= 24 dB.
e on PUSCH is 24 dB < x <= 26 dB.
e on PUSCH is 26 dB < x <= 28 dB.
e on PUSCH is 28 dB < x <= 30 dB.
e on PUSCH is greater than 30 dB.
iwatts for Rx antenna 1 from every sample period and calculating the average at the end of the collection interval.
iwatts for Rx antenna 2 from every sample period and calculating the average at the end of the collection interval.
iwatts for Rx antenna 3 from every sample period and calculating the average at the end of the collection interval.
iwatts for Rx antenna 4 from every sample period and calculating the average at the end of the collection interval.
iwatts for Rx antenna 5 from every sample period and calculating the average at the end of the collection interval.
iwatts for Rx antenna 6 from every sample period and calculating the average at the end of the collection interval.
iwatts for Rx antenna 7 from every sample period and calculating the average at the end of the collection interval.
iwatts for Rx antenna 8 from every sample period and calculating the average at the end of the collection interval.
a RTWP values in milliwatts every sample period and comparing to a stored maximum value. If any of the new collected values are larger t
le period the noise measurement is received as per the PUSCH RB distribution bin 0 and taking the 50 percentile value at the end of the co
le period the noise measurement is received as per the PUSCH RB distribution bin 1 and taking the 50 percentile value at the end of the co
le period the noise measurement is received as per the PUSCH RB distribution bin 2 and taking the 50 percentile value at the end of the co
le period the noise measurement is received as per the PUSCH RB distribution bin 3 and taking the 50 percentile value at the end of the co
le period the noise measurement is received as per the PUSCH RB distribution bin 4 and taking the 50 percentile value at the end of the co
le period the noise measurement is received as per the PUSCH RB distribution bin 5 and taking the 50 percentile value at the end of the co
le period the noise measurement is received as per the PUSCH RB distribution bin 6 and taking the 50 percentile value at the end of the co
le period the noise measurement is received as per the PUSCH RB distribution bin 7 and taking the 50 percentile value at the end of the co
le period the noise measurement is received as per the PUSCH RB distribution bin 8 and taking the 50 percentile value at the end of the co
the in-use PUSCH PRBs every sample period and incrementing the corresponding bin having an average SIR value less than 1.0 dB.
the in-use PUSCH PRBs every sample period and incrementing the corresponding bin having an average SIR value from 1.0 dB to less tha
the in-use PUSCH PRBs every sample period and incrementing the corresponding bin having an average SIR value from 4.0 dB to less tha
the in-use PUSCH PRBs every sample period and incrementing the corresponding bin having an average SIR value from 7.0 dB to less tha
the in-use PUSCH PRBs every sample period and incrementing the corresponding bin having an average SIR value from 10.0 dB to less th
the in-use PUSCH PRBs every sample period and incrementing the corresponding bin having an average SIR value from 13.0 dB to less th
the in-use PUSCH PRBs every sample period and incrementing the corresponding bin having an average SIR value from 16.0 dB to less th
the in-use PUSCH PRBs every sample period and incrementing the corresponding bin having an average SIR value from 19.0 dB to less th
the in-use PUSCH PRBs every sample period and incrementing the corresponding bin having an average SIR value from 22.0 dB to less th
the in-use PUSCH PRBs every sample period and incrementing the corresponding bin having an average SIR value equal or greater than 2
iwatts for Rx antenna 9 from every sample period and calculating the average at the end of the collection interval.
iwatts for Rx antenna 10 from every sample period and calculating the average at the end of the collection interval.
iwatts for Rx antenna 11 from every sample period and calculating the average at the end of the collection interval.
iwatts for Rx antenna 12 from every sample period and calculating the average at the end of the collection interval.
1AP:E-RAB SETUP REQUEST message sent by MME to the eNB.
an S1AP:E-RAB SETUP RESPONSE message sent by the eNB to MME.
P:UE CONTEXT RELEASE COMMAND message sent by MME to the eNB. The counter is not incremented in case that the S1AP:UE CON
P:UE CONTEXT RELEASE COMMAND message sent by MME to the eNB. The counter is not incremented in case that the S1AP:UE CON
P:UE CONTEXT RELEASE COMMAND message sent by MME to the eNB. The counter is not incremented in case that the S1AP:UE CON
other failure counter.
E CONTEXT RELEASE REQUEST message sent by the eNB to the MME. The counter is incremented with the number of E-RABs release
aneous E-RABs with QCI 1 characteristics at a pre-defined interval (1 sec) and then adding up these sample values over the measurement
aneous E-RABs with QCI 2 characteristics at a pre-defined interval (1 sec) and then adding up these sample values over the measurement
aneous E-RABs with QCI 3 characteristics at a pre-defined interval (1 sec) and then adding up these sample values over the measurement
aneous E-RABs with QCI 4 characteristics at a pre-defined interval (1 sec) and then adding up these sample values over the measurement
aneous E-RABs with QCI 5 characteristics at a pre-defined interval (1 sec) and then adding up these sample values over the measurement
aneous E-RABs with QCI 6 characteristics at a pre-defined interval (1 sec) and then adding up these sample values over the measurement
aneous E-RABs with QCI 7 characteristics at a pre-defined interval (1 sec) and then adding up these sample values over the measurement
aneous E-RABs with QCI 8 characteristics at a pre-defined interval (1 sec) and then adding up these sample values over the measurement
aneous E-RABs with QCI 9 characteristics at a pre-defined interval (1 sec) and then adding up these sample values over the measurement
ampling counters for the number of simultaneous E-RABs (SUM_SIMUL_ERAB_QCI_x) is done.
nt by MME to the eNB. The counter is incremented by the number of QCI1 bearers contained in the "E-RAB to be Modified List" IE (3GPP T
nt by MME to the eNB. The counter is incremented by the number of QCI2 bearers contained in the "E-RAB to be Modified List" IE (3GPP T
nt by MME to the eNB. The counter is incremented by the number of QCI3 bearers contained in the "E-RAB to be Modified List" IE (3GPP T
nt by MME to the eNB. The counter is incremented by the number of QCI4 bearers contained in the "E-RAB to be Modified List" IE (3GPP T
nt by MME to the eNB. The counter is incremented by the number of QCI5 bearers contained in the "E-RAB to be Modified List" IE (3GPP T
nt by MME to the eNB. The counter is incremented by the number of QCI6 bearers contained in the "E-RAB to be Modified List" IE (3GPP T
nt by MME to the eNB. The counter is incremented by the number of QCI7 bearers contained in the "E-RAB to be Modified List" IE (3GPP T
nt by MME to the eNB. The counter is incremented by the number of QCI8 bearers contained in the "E-RAB to be Modified List" IE (3GPP T
nt by MME to the eNB. The counter is incremented by the number of QCI9 bearers contained in the "E-RAB to be Modified List" IE (3GPP T
e sent by eNB to the MME. The counter is incremented by the number of QCI1 bearers contained in the "E-RAB Modify List".
e sent by eNB to the MME. The counter is incremented by the number of QCI2 bearers contained in the "E-RAB Modify List".
e sent by eNB to the MME. The counter is incremented by the number of QCI3 bearers contained in the "E-RAB Modify List".
e sent by eNB to the MME. The counter is incremented by the number of QCI4 bearers contained in the "E-RAB Modify List".
e sent by eNB to the MME. The counter is incremented by the number of QCI5 bearers contained in the "E-RAB Modify List".
e sent by eNB to the MME. The counter is incremented by the number of QCI6 bearers contained in the "E-RAB Modify List".
e sent by eNB to the MME. The counter is incremented by the number of QCI7 bearers contained in the "E-RAB Modify List".
e sent by eNB to the MME. The counter is incremented by the number of QCI8 bearers contained in the "E-RAB Modify List".
e sent by eNB to the MME. The counter is incremented by the number of QCI9 bearers contained in the "E-RAB Modify List".
e sent by eNB to the MME. The counter is incremented by the number of bearers contained in the "E-RAB Failed To Modify List" with the R
e sent by eNB to the MME. The counter is incremented by the number of bearers contained in the "E-RAB Failed To Modify List" with the R
e sent by eNB to the MME. The counter is incremented by the number of bearers contained in the "E-RAB Failed To Modify List" with the R
P:UE Context Release Command message sent by the MME to eNB.
P:UE Context Release Command message sent by the MME to eNB.
P:UE Context Release Command message sent by the MME to eNB.
P:UE Context Release Command message sent by the MME to eNB.The counter is updated if the release request detected does not match
E CONTEXT RELEASE REQUEST message sent by the eNB to the MME. The counter is incremented with the number of QCI1 E-RABs re
ed (UL/DL) for an E-RAB with QCI1 characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME with
ed (UL/DL) for an E-RAB with QCI2 characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME with
ed (UL/DL) for an E-RAB with QCI3 characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME with
ed (UL/DL) for an E-RAB with QCI4 characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME with
ed (UL/DL) for an E-RAB with non-GBR characteristics (QCI5...9) and the "S1AP UE Context Release Request" message is sent by eNB to
gregated during the E-RAB lifetime. At the end of the measurement period and when E-RAB is released the sum counter for all E-RABs wit
gregated during the E-RAB lifetime. At the end of the measurement period and when E-RAB is released the sum counter for all E-RABs wit
gregated during the E-RAB lifetime. At the end of the measurement period and when E-RAB is released the sum counter for all E-RABs wit
gregated during the E-RAB lifetime. At the end of the measurement period and when E-RAB is released the sum counter for all E-RABs wit
gregated during the E-RAB lifetime. At the end of the measurement period and when E-RAB is released the sum counter for all E-RABs wit
or of an S1AP:E-RAB SETUP REQUEST message in case that these messages contain an ARP (Allocation and Retention Priority) priority
1AP:INITIAL CONTEXT RESPONSE message in case their "E-RAB Setup List" IEs contain E-RAB IDs of bearers for high priority calls.
essage sent by the MME to the eNB. The counter is updated with the number of QCI1 bearers contained in the "E-RAB to Be Setup List" IE
essage sent by the MME to the eNB. The counter is updated with the number of QCI2 bearers contained in the "E-RAB to Be Setup List" IE
essage sent by the MME to the eNB. The counter is updated with the number of QCI3 bearers contained in the "E-RAB to Be Setup List" IE
essage sent by the MME to the eNB. The counter is updated with the number of QCI4 bearers contained in the "E-RAB to Be Setup List" IE
essage sent by the MME to the eNB. The counter is updated with the number of QCI5 bearers contained in the "E-RAB to Be Setup List" IE
essage sent by the MME to the eNB. The counter is updated with the number of QCI6 bearers contained in the "E-RAB to Be Setup List" IE
essage sent by the MME to the eNB. The counter is updated with the number of QCI7 bearers contained in the "E-RAB to Be Setup List" IE
essage sent by the MME to the eNB. The counter is updated with the number of QCI8 bearers contained in the "E-RAB to Be Setup List" IE
essage sent by the MME to the eNB. The counter is updated with the number of QCI9 bearers contained in the "E-RAB to Be Setup List" IE
by the MME to the eNB. The counter is updated with the number of QCI1 bearers contained in the "E-RAB to Be Setup List" IE.
by the MME to the eNB. The counter is updated with the number of QCI2 bearers contained in the "E-RAB to Be Setup List" IE.
by the MME to the eNB. The counter is updated with the number of QCI3 bearers contained in the "E-RAB to Be Setup List" IE.
by the MME to the eNB. The counter is updated with the number of QCI4 bearers contained in the "E-RAB to Be Setup List" IE.
by the MME to the eNB. The counter is updated with the number of QCI5 bearers contained in the "E-RAB to Be Setup List" IE.
by the MME to the eNB. The counter is updated with the number of QCI6 bearers contained in the "E-RAB to Be Setup List" IE.
by the MME to the eNB. The counter is updated with the number of QCI7 bearers contained in the "E-RAB to Be Setup List" IE.
by the MME to the eNB. The counter is updated with the number of QCI8 bearers contained in the "E-RAB to Be Setup List" IE.
SEbymessage
the MME sent
to the
byeNB.
eNB The
to thecounter
MME. is updated with the number of QCI9 bearers contained in the "E-RAB to Be Setup List" IE.
ned in the "E-RAB Setup List" IE.
SE message sent by eNB to the MME.
ned in the "E-RAB
SE message Setup
sent by eNBList" IE.MME.
to the
ned in the "E-RAB
SE message Setup
sent by eNBList" IE.MME.
to the
ned in the "E-RAB
SE message Setup
sent by eNBList" IE.MME.
to the
ned in the "E-RAB
SE message Setup
sent by eNBList" IE.MME.
to the
ned in the "E-RAB
SE message Setup
sent by eNBList" IE.MME.
to the
ned in the "E-RAB Setup List"
SE message sent by eNB to the IE.MME.
ned in the "E-RAB Setup List"
SE message sent by eNB to the IE.MME.
ned in the "E-RAB Setup List" IE.
sent by eNB to the MME. The counter is updated with the number of QCI1 bearers contained in the "E-RAB Setup List" IE.
sent by eNB to the MME. The counter is updated with the number of QCI2 bearers contained in the "E-RAB Setup List" IE.
sent by eNB to the MME. The counter is updated with the number of QCI3 bearers contained in the "E-RAB Setup List" IE.
sent by eNB to the MME. The counter is updated with the number of QCI4 bearers contained in the "E-RAB Setup List" IE.
sent by eNB to the MME. The counter is updated with the number of QCI5 bearers contained in the "E-RAB Setup List" IE.
sent by eNB to the MME. The counter is updated with the number of QCI6 bearers contained in the "E-RAB Setup List" IE.
sent by eNB to the MME. The counter is updated with the number of QCI7 bearers contained in the "E-RAB Setup List" IE.
sent by eNB to the MME. The counter is updated with the number of QCI8 bearers contained in the "E-RAB Setup List" IE.
sent by eNB to the MME. The counter is updated with the number of QCI9 bearers contained in the "E-RAB Setup List" IE.
aneous E-RABs with QCI1 characteristics at a pre-defined interval (1 sec). The counter is updated if the current number of simultaneous E-
aneous E-RABs with QCI2 characteristics at a pre-defined interval (1 sec). The counter is updated if the current number of simultaneous E-
aneous E-RABs with QCI3 characteristics at a pre-defined interval (1 sec). The counter is updated if the current number of simultaneous E-
aneous E-RABs with QCI4 characteristics at a pre-defined interval (1 sec). The counter is updated if the current number of simultaneous E-
aneous E-RABs with QCI5 characteristics at a pre-defined interval (1 sec). The counter is updated if the current number of simultaneous E-
aneous E-RABs with QCI6 characteristics at a pre-defined interval (1 sec). The counter is updated if the current number of simultaneous E-
aneous E-RABs with QCI7 characteristics at a pre-defined interval (1 sec). The counter is updated if the current number of simultaneous E-
aneous E-RABs with QCI8 characteristics at a pre-defined interval (1 sec). The counter is updated if the current number of simultaneous E-
aneous E-RABs with QCI9 characteristics at a pre-defined interval (1 sec). The counter is updated if the current number of simultaneous E-
t the pre-defined interval (1 sec).
t the pre-defined interval (1 sec).
t the pre-defined interval (1 sec).
t the pre-defined interval (1 sec).
-RAB MODIFY RESPONSE message sent by the eNB to the MME. The counter is incremented by the number of bearers contained in the
-RAB MODIFY RESPONSE message sent by the eNB to the MME. The counter is incremented by the number of bearers contained in the
DL) for an E-RAB with QCI5 characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME with the rele
DL) for an E-RAB with QCI6 characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME with the rele
DL) for an E-RAB with QCI7 characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME with the rele
DL) for an E-RAB with QCI8 characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME with the rele
DL) for an E-RAB with QCI9 characteristics and the "S1AP UE Context Release Request" message is sent by eNB to the MME with the rele
in the "E-RAB
NITIAL CONTEXT to Be SetupFAILURE
SETUP List" IE ofmessage
the preceding S1AP:INITIAL
sent by CONTEXT
the eNB to the MME. SETUP REQUEST if the S1AP:INITIAL CONTEXT SETUP F
in the "E-RAB
NITIAL CONTEXT to Be SetupFAILURE
SETUP List" IE ofmessage
the preceding S1AP:INITIAL
sent by CONTEXT
the eNB to the MME. SETUP REQUEST if the S1AP:INITIAL CONTEXT SETUP F
in the "E-RAB
NITIAL CONTEXT to Be SetupFAILURE
SETUP List" IE ofmessage
the preceding S1AP:INITIAL
sent by CONTEXT
the eNB to the MME. SETUP REQUEST if the S1AP:INITIAL CONTEXT SETUP F
in the "E-RAB to Be Setup List" IE of the preceding S1AP:INITIAL CONTEXT SETUP REQUEST if the S1AP:INITIAL CONTEXT SETUP F
-RAB SETUP RESPONSE message sent by the eNB to the MME. The counter is incremented by the number of bearers contained in the "E
-RAB SETUP RESPONSE message sent by the eNB to the MME. The counter is incremented by the number of bearers contained in the "
-RAB SETUP RESPONSE message sent by the eNB to the MME. The counter is incremented by the number of bearers contained in the "E
-RAB SETUP RESPONSE message sent by the eNB to the MME. The counter is incremented by the number of bearers contained in the "E
-RAB SETUP RESPONSE message sent by the eNB to the MME. The counter is incremented by the number of bearers contained in the "E
-RAB SETUP RESPONSE message sent by the eNB to the MME. The counter is incremented by the number of bearers contained in the "E
E-RAB RELEASE INDICATION or an S1AP:UE CONTEXT RELEASE REQUEST message sent by the eNB to the MME. The counter is inc
E CONTEXT RELEASE REQUEST message with the RNL cause "User Inactivity" sent by the eNB to the MME. The counter is incremente
E CONTEXT RELEASE REQUEST message with the RNL cause "Radio Connection with UE lost" sent by the eNB to the MME. If the S1A
-RAB RELEASE INDICATION message or an S1AP:UE CONTEXT RELEASE REQUEST message sent by the eNB to the MME with the T
E CONTEXT RELEASE REQUEST message sent by the eNB to the MME with the RNL causes "Inter-RAT redirection", "Redirection towa
E CONTEXT RELEASE REQUEST message with the RNL cause "E-UTRAN Generated Reason" sent by the eNB to the MME if the releas
-RAB RELEASE
RAN/SRVCC INDICATION or an S1AP:UE CONTEXT RELEASE REQUEST message sent by the eNB to the MME. The counter is inc
to GSM:
OMMAND message
RAN/SRVCC to GSM:with the cause "RNL Successful Handover", the counter is incremented with the number of bearers not admitted by the
by the HO target
RAN/SRVCC to GSM:during the preceding HO preparation procedure. The bearers, which are not admitted, are contained in the "E-RABs to Re
OMMAND message
RAN/SRVCC to GSM:with the cause "RNL Successful Handover". The counter is incremented with the number of bearers admitted by the H
EQUEST message to the MME due to the expiration of the Handover Guard Timer TS1RELOCoverall, the counter is incremented with the n
-RAB RELEASE RESPONSE message sent by the eNB to the MME. The counter is incremented by the number of bearers contained in th
-RAB RELEASE INDICATION or an S1AP:UE CONTEXT RELEASE REQUEST message sent by the eNB to the MME. The counter is incr
E CONTEXT RELEASE REQUEST message with the RNL cause "User Inactivity" sent by the eNB to the MME. The counter is incremente
E CONTEXT RELEASE REQUEST message with the RNL cause "Radio Connection with UE lost" sent by the eNB to the MME. If the S1A
-RAB RELEASE INDICATION message or an S1AP:UE CONTEXT RELEASE REQUEST message sent by the eNB to the MME with the T
E CONTEXT RELEASE REQUEST message sent by the eNB to the MME with the RNL causes "Inter-RAT redirection", "Redirection towar
E CONTEXT RELEASE REQUEST message with the RNL cause "E-UTRAN Generated Reason" sent by the eNB to the MME if the releas
-RAB/SRVCC
RAN RELEASE INDICATION or an S1AP:UE CONTEXT RELEASE REQUEST message sent by the eNB to the MME. The counter is inc
to GSM:
OMMAND message
RAN/SRVCC to GSM:with the cause "RNL Successful Handover", the counter is incremented with the number of QCI1 bearers not admitted
mitted by the to
RAN/SRVCC target
GSM:eNB during the preceding HO preparation procedure. The QCI1 bearers, which are not admitted, are contained in the "
RAN/SRVCC to GSM:with the cause "RNL Successful Handover". The counter is incremented with the number of QCI1 bearers admitted by
OMMAND message
EQUEST message to the MME due to the expiration of the Handover Guard Timer TS1RELOCoverall, the counter is incremented with the n
OMPLETE)
es for other purposes than DRB setup (that is DRB release, DRB configuration changes, transmission of security information) will not be co
e to reception
CTION SETUPofmessage
S1AP:UE CONTEXT
sent RELEASE
by eNB to COMMAND.
the UE, containing SRB1-specific configurations.
ST message several times in a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last messag
ON SETUP COMPLETE message sent by UE to eNB on SRB1/DCCH (carrying the initial NAS message).
imer used for the supervision of RRC Connection Setup procedure at the eNB. The RRC Guard Timer is stopped when the RRC CONNEC
CTION RECONFIGURATION message sent by eNB to the UE, containing SRB2-specific configurations.
ON RECONFIGURATION COMPLETE message sent by UE to eNB on SRB1/DCCH.
not be counted.
granularity period. A measurement result "0" at the end of the granularity period (for example, 15 minutes) means that no E-RAB setup occ
granularity period. A measurement result "0" at the end of the granularity period (for example, 15 minutes) means that no E-RAB setup occ
ct message, sent by the eNB to UE.
cludingispure
ecords SysInfo
reached message)
for the from S1
next paging interface.
occasion that corresponds to the paging request
n)
ding a "reportCGI" measurement configuration to the UE for a UTRAN cell according to 3GPP TS 36.331.
eportCGI" measurement result for a UTRAN cell according to 3GPP TS 36.331. The "reportCGI" measurement result contains all necessary
eportCGI" measurement result for a UTRAN cell according to 3GPP TS 36.331. The "reportCGI" measurement result does not contain the n
onnection Release message
ast of ETWS/CMAS (source eNB
warning messages -> UE) inAcase
is started. thatcampaign
paging this message contains
is started oncethe RedirectedCarrierInfo
after a new broadcast or parameter for a Home
the replacement eNB (
of an existin
e Warning Area List IE does not apply for the cell or when the eNB receives an S1AP:WRITE-REPLACE WARNING REQUEST message w
granularity period. A measurement result "0" at the end of the granularity period (for example, 15 minutes) means that no RRC connection s
granularity period. A measurement result "0" at the end of the granularity period (for example, 15 minutes) means that no RRC connection s
y the UE to eNB and of the RRM decision not to execute a handover. Updated to the source cell.
y the UE to eNB and of an RRM decision to execute a handover. Updated to the source cell.
get cells from RRM and decides on an Intra-eNB Handover. Updated to the source cell.
get cells from the RRM. The MM or RRM AC decides not to execute an Intra-eNB Handover. Updated to the source cell.
get cells from RRM. The MM or RRM AC decides not to execute an Intra-eNB Handover. The counter is updated if the failure detected does
ge sent by the eNB to UE, which indicates a Handover Command to the UE. Updated to the source cell.
e handover on the source side. Updated to the source cell.
process is obtained from CQI reports and corrected by Outer Loop Quality Control.
process is obtained from CQI reports and corrected by Outer Loop Quality Control.
cess is obtained from CQI reports and corrected by Outer Loop Quality Control.
or the transmission. It counts the number of MIMO Open Loop Actual Diversity mode usage for both new transmissions and retransmissions
selected for the transmission. It counts the number of MIMO Open Loop Actual Spatial Multiplexing mode usage for both new transmission
ord mapping to single layer mode is selected for the transmission. It counts the number of MIMO Closed Loop Actual Single Codeword map
word mapping to dual layers mode is selected for the transmission. It counts the number of MIMO Closed Loop Actual Double Codeword ma
etween the diversity mode and the spatial multiplexing mode transmission. It counts selected transmission mode changes only on the basis
tween the single codeword mode and the double codeword mode transmission. It counts selected transmission mode changes only on the
DCI with required AGG1, which cannot be scheduled at all or cannot be scheduled with required power for finally allocated AGG, is conside
DCI with required AGG2, which cannot be scheduled at all or cannot be scheduled with required power for finally allocated AGG, is conside
DCI with required AGG4, which cannot be scheduled at all or cannot be scheduled with required power for finally allocated AGG, is conside
r PDCCH scheduling. A DCI with required AGG8, which cannot be scheduled at all or cannot be scheduled with required power for finally al
counter. The mean value is the arithmetical average of all TTI measured in a granularity period.
UEs in UL per TTI has been reached.
all DL and special subframes (TDD only). It also includes TTIs in which no PDSCH can be scheduled, for example, the special subframes in
UEs in DL per TTI has been reached.
DM symbol is allocated to the PDCCH. This counter is not updated for subframes for which the number of allocated PDCCH OFDM symbo
symbols are allocated to the PDCCH. This counter is not updated for subframes for which the number of allocated PDCCH OFDM symbols
symbols are allocated to the PDCCH. This counter is not updated for subframes for which the number of allocated PDCCH OFDM symbols
hmetical average of samples each representing the number of UEs in TTI Bundling mode at that moment.
send a "TTI Bundle".
TTI Bundling mode earlier than t1 seconds after switching to TTI Bundling. Termination by leaving the cell (HO) is also counted.
TTI Bundling mode within this time span. Termination by leaving the cell (HO) is also counted.
TTI Bundling later than t2 seconds after switching to TTI Bundling mode. Termination by leaving the cell (HO) is also counted.
age, which includes a "SCellToAddModList-r10" parameter.
message related to a preceding RRC:RRCConnectionReconfiguration message, which included a "SCellToAddModList-r10" parameter an
Load Balancing state for inter-frequency load balancing; the counter is updated if the result of this check is that the cell is in the active Load
d for PUSCH data. (In case no data is present, there is no need to actually use this TTI for data transfer.)
d for PDSCH data. (In case no data is present, there is no need to actually use this TTI for data transfer.)
PUSCH PRBs, which are shared by a pair of UEs (in UL MU-MIMO mode).
s measured by an eNB internal measurement. This counter is updated if the measured cell DL CAC was zero (DL CAC = 0).
s measured by an eNB internal measurement. This counter is updated if the measured cell DL CAC was in the range 0 < DL CAC <= 20.
s measured by an eNB internal measurement. This counter is updated if the measured cell DL CAC was in the range 20 < DL CAC <= 40.
s measured by an eNB internal measurement. This counter is updated if the measured cell DL CAC was in the range 40 < DL CAC <= 60.
s measured by an eNB internal measurement. This counter is updated if the measured cell DL CAC was in the range 60 < DL CAC <= 80.
s measured by an eNB internal measurement. This counter is updated if the measured cell DL CAC was in the range 80 < DL CAC <= 100.
ng is applied.
ng is applied.
measured by an eNB internal measurement. This counter is updated if the measured cell PDCCH AC was zero (DL AC = 0).
measured by an eNB internal measurement. This counter is updated if the measured cell PDCCH AC was in the range 0 < PDCCH AC <=
measured by an eNB internal measurement. This counter is updated if the measured cell PDCCH AC was in the range 20 < PDCCH AC <
measured by an eNB internal measurement. This counter is updated if the measured cell PDCCH AC was in the range 40 < PDCCH AC <
measured by an eNB internal measurement. This counter is updated if the measured cell PDCCH AC was in the range 60 < PDCCH AC <
measured by an eNB internal measurement. This counter is updated if the measured cell PDCCH AC was in the range 80 < PDCCH AC <
ers is measured by an eNB internal measurement. This counter is updated if the measured cell DL GBR AC was zero (DL AC = 0).
ers is measured by an eNB internal measurement. This counter is updated if the measured cell DL GBR AC was in the range 0 < DL GBR A
ers is measured by an eNB internal measurement. This counter is updated if the measured cell DL GBR AC was in the range 20 < DL GBR
ers is measured by an eNB internal measurement. This counter is updated if the measured cell DL GBR AC was in the range 40 < DL GBR
ers is measured by an eNB internal measurement. This counter is updated if the measured cell DL GBR AC was in the range 60 < DL GBR
ers is measured by an eNB internal measurement. This counter is updated if the measured cell DL GBR AC was in the range 80 < DL GBR
bearers is measured by an eNB internal measurement. This counter is updated if the measured cell DL non-GBR AC was zero (DL AC = 0)
ers is measured by an eNB internal measurement. This counter is updated if the measured cell DL non-GBR AC was in the range 0 < DL n
ers is measured by an eNB internal measurement. This counter is updated if the measured cell DL non-GBR AC was in the range 20 < DL
bearers is measured by an eNB internal measurement. This counter is updated if the measured cell DL non-GBR AC was in the range 40 <
bearers is measured by an eNB internal measurement. This counter is updated if the measured cell DL non-GBR AC was in the range 60 <
bearers is measured by an eNB internal measurement. This counter is updated if the measured cell DL non-GBR AC was in the range 80 <
r UL on
time SPS activation
PUSCH or reactivation.
(non-DTX reception) in the TTI and PRBs that were previously assigned by the SPS allocation.
nfigured periodicity for
PS allocated resources. the SPS allocation do not increment the counter.
atter.
tatically allocated by SPS.
in thewhen
TTI TTI when the buffer
the buffer is emptied.
is emptied. A sample
A sample of "ThpTimeUl"
for ThpVolUl for volume
is the data each time the ULonbuffer
counted PDCP forSDU
one level
E-RAB is emptied.
in bits received in UL for one E-RA
in thewhen
TTI TTI when the buffer
the buffer is emptied.
is emptied. A sample
A sample of "ThpTimeUl"
for ThpVolUl for volume
is the data each time the ULonbuffer
counted PDCP forSDU
one level
E-RAB is emptied.
in bits received in UL for one E-RA
in thewhen
TTI TTI when the buffer
the buffer is emptied.
is emptied. A sample
A sample of "ThpTimeUl"
for ThpVolUl for volume
is the data each time the ULonbuffer
counted PDCP forSDU
one level
E-RAB is emptied.
in bits received in UL for one E-RA
in thewhen
TTI TTI when the buffer
the buffer is emptied.
is emptied. A sample
A sample of "ThpTimeUl"
for ThpVolUl for volume
is the data each time the ULonbuffer
counted PDCP forSDU
one level
E-RAB is emptied.
in bits received in UL for one E-RA
in thewhen
TTI TTI when the buffer
the buffer is emptied.
is emptied. A sample
A sample of "ThpTimeUl"
for ThpVolUl for volume
is the data each time the ULonbuffer
counted PDCP forSDU
one level
E-RAB is emptied.
in bits received in UL for one E-RA
in thewhen
TTI TTI when the buffer
the buffer is emptied.
is emptied. A sample
A sample of "ThpTimeUl"
for ThpVolUl for volume
is the data each time the ULonbuffer
counted PDCP forSDU
one level
E-RAB is emptied.
in bits received in UL for one E-RA
in thewhen
TTI TTI when the buffer
the buffer is emptied.
is emptied. A sample
A sample of "ThpTimeUl"
for ThpVolUl for volume
is the data each time the ULonbuffer
counted PDCP forSDU
one level
E-RAB is emptied.
in bits received in UL for one E-RA
in thewhen
TTI TTI when the buffer
the buffer is emptied.
is emptied. A sample
A sample of "ThpTimeUl"
for ThpVolUl for volume
is the data each time the ULonbuffer
counted PDCP forSDU
one level
E-RAB is emptied.
in bits received in UL for one E-RA
in the TTI when the buffer is emptied. A sample of "ThpTimeUl" for each time the UL buffer for one E-RAB is emptied.
exclude the volume of the last piece of data emptying
transmitted in the TTI when the buffer is emptied.
RAB is emptied.
exclude the volume of the last piece of data emptying
transmitted in the TTI when the buffer is emptied.
RAB is emptied.
exclude the volume of the last piece of data emptying
transmitted in the TTI when the buffer is emptied.
RAB is emptied.
exclude the volume of the last piece of data emptying
transmitted in the TTI when the buffer is emptied.
RAB is emptied.
exclude the volume of the last piece of data emptying
transmitted in the TTI when the buffer is emptied.
RAB is emptied.
exclude the volume of the last piece of data emptying
transmitted in the TTI when the buffer is emptied.
RAB is emptied.
exclude the volume of the last piece of data emptying
transmitted in the TTI when the buffer is emptied.
RAB is emptied.
exclude the volume of the last piece of data emptying
transmitted in the TTI when the buffer is emptied.
RAB is emptied.
exclude the volume of the last piece of data emptying
transmitted in the TTI when the buffer is emptied.
RAB is emptied.
HANDOVER REQUIRED message from the source eNB to the MME if this message prepares an Inter eNB Handover.
ELOCprep if the timer was started because of the preparation of an Inter eNB Handover.
NDOVER PREPARATION FAILURE message from MME to source eNB with cause "No Radio Resources Available in Target Cell" if this m
NDOVER PREPARATION FAILURE message from the MME to the source eNB with any other cause than "No Radio Resources Available i
NDOVER COMMAND message from the MME to the source eNB in case that this message is received in response to the preparation of an
CONTEXT RELEASE COMMAND message from the MME to the source eNB with the cause value Radio Network Layer (Successful Han
rconfigured
TS1RELOCoverall
number ofintimes.
case that this timer was started because of an Inter eNB Handover.
configured number of times.
n fails for any reason. This counter is updated in the source side of the handover.
IGURATION message is sent by the eNB to the UE, indicating a Handover Command to the UE. This counter is updated in the source side
This counter is updated in the source side of the handover.
on phase intimer
e guarding the target cell apart from a HANDOVER PREPARATION FAILURE message (from target side) or expiration of the respective g
TX2RELOCprep.
eX2AP:HANDOVER
guarding timer TS1RELOCprep.
PREPARATION FAILURE message from the target eNB with the cause "No Radio Resources Available in Target cell"
S1AP:HANDOVER PREPARATION FAILURE message from the MME with the cause "No Radio Resources Available in Target cell"
DOVER COMMAND message from the MME
S1AP:UE CONTEXT RELEASE COMMAND message from the MME with the cause value Radio Network Layer (Successful Handover) in
either TX2RELOCoverall or TS1RELOCoverall, in case that one of these timers was started because of an Inter-eNB Handover.
mer THOoverall
cluded in caseThe
from counting. thatcase
the timer has been started
of reestablishment due to
causes Intra-eNB
that Handover.
"HOfailure" is excluded from counting when re-establishment target cell is p
e considered UE context might be ongoing. The target cell of such HO preparation can be different from the cell receiving the reestablishme
s recognized
alue by reestablishment
of Tstore_UE_cntxt timer up cause "HOfailure".
from HO completion.
use "handoverFailure") received at cell prepared for incoming HO or at HO source cell is excluded from counting.
cell A within a short time period (defined by the parameter tPingPong).
onnection Reconfiguration message (sent by the eNB to the UE), which indicates a handover command to the UE in case this message is s
eption of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME with cause value Radio Network Layer (Successful Hand
message (source eNB -> UE) in case that this message was sent because the source eNB received the S1AP:INITIAL CONTEXT SETUP R
RCConnectionRelease message (source eNB -> UE) in case that this message was sent because the source eNB received an S1AP:UE C
message (source eNB -> UE) in case that this message was sent because the source eNB received the S1AP:INITIAL CONTEXT SETUP R
source MME for an Inter System Handover. This counter is updated for the source cell of the handover. This counter is updated in case of
xpiration of guarding timer TS1RELOCprep_InterRAT. This counter is updated for the source cell of the handover. This counter is updated i
E message is received from MME with cause "No radio resources available in target cell" for an Inter System Handover. This counter is upda
E message is received from MME with other cause than "No radio resources available in target cell" for an Inter System Handover. This cou
eceived from MME for a PS-HO to UTRAN. This counter is updated for the source cell of the handover.
message is received from MME with Cause value "Radio Network Layer" (Successful Handover) for a PS-HO to UTRAN. This counter is up
ing timer TS1RELOCoverall. This counter is updated for the source cell of the handover.
age (with cell change order to GSM; 3GPP TS 36.331) from the serving eNB to the UE indicates the attempt of a Network Assisted Cell Ch
ce eNB <- MME; 3GPP TS 36.413) in case that this message is received in response to the preparation of an Inter System Handover to UT
essage (source eNB <- MME; 3GPP TS 36.413) with Cause value "Radio Network Layer (Successful Handover)" in case that this message
6.413) in case that this timer was started because of an Inter System Handover to UTRAN with SRVCC (Single Radio Voice Call Continuity,
ge (source eNB -> UE; 3GPP TS36.331) in case that this message is transmitted for a CS Fallback to UTRAN with PS handover (3GPP TS
ce eNB <- MME; 3GPP TS 36.413) in case this message is received in response to the preparation of an Inter System Handover to GERAN
essage (source eNB <- MME; 3GPP TS 36.413) with Cause value "Radio Network Layer (Successful Handover)" in case this message is re
6.413) in case this timer was started because of an Inter System Handover to GERAN with SRVCC (Single Radio Voice Call Continuity, 3G
andoverFromEUTRAPreparationRequest message by the eNB to the UE (3GPP TS 36.331) if this message is sent to prepare an inter-syste
imer TUlHoPrepTransfer1xSrvcc if this timer was started because of an inter-system handover preparation to 1xRTT with SRVCC.
imer TC2KRelocPrep1xSrvcc if this timer was started because of an inter-system handover preparation to 1xRTT with SRVCC.
WNLINK S1 CDMA2000 TUNNELING (3GPP TS 36.413) message by the eNB from the MME if this message indicates a failed handover pre
WNLINK S1 CDMA2000 TUNNELING (3GPP TS 36.413) message by the eNB from the MME if this message indicates a successful handov
obilityFromEUTRACommand message by the eNB to the UE (3GPP TS 36.331) if this message is sent for an inter-system handover to 1xR
E CONTEXT RELEASE REQUEST message (3GPP TS 36.413) by the eNB to the MME if this message is sent for an inter-system handov
BParametersRequestCDMA2000 (3GPP TS 36.331) message by the eNB from the UE.
SFBParametersResponseCDMA2000 (3GPP TS 36.331) message by the eNB to the UE.
andoverFromEUTRAPreparationRequest message by the eNB to the UE (3GPP TS 36.331) in case that this message is sent for the prepar
andoverPreparationTransfer message by the eNB from the UE (3GPP TS 36.331) in case that this message is received for the preparation
WNLINK S1 CDMA2000 TUNNELING (3GPP TS 36.413) message by the eNB from the MME in case that this message indicates a "HO Fai
ls due to expiration of guarding timer TS1RELOCprep_InterRAT. This counter is updated for the source cell of the handover. This counter i
E message is received from MME with cause "No radio resources available in target cell" for an Inter System Handover. This counter is upda
E message is received from MME with other cause than "No radio resources available in target cell" for an Inter System Handover. This cou
eceived from MME for a PS-HO. This counter is updated for the source cell of the handover.
message is received from MME with Cause value "Radio Network Layer" (Successful Handover) for a PS-HO to UTRAN. This counter is up
rding timer TS1RELOCoverall. This counter is updated for the source cell of the handover.
source MME for an Inter System Handover. This counter is updated for the source cell of the handover. This counter is updated in case of
ce eNB <- MME; 3GPP TS 36.413) in case that this message is received in response to the preparation of an Inter System Handover to UT
essage (source eNB <- MME; 3GPP TS 36.413) with Cause value "Radio Network Layer (Successful Handover)" in case that this message
6.413) in case that this timer was started because of an Inter System Handover to UTRAN with SRVCC (Single Radio Voice Call Continuity,
UEs, having one SRB and at least one DRB established.
d at least one DRB established during a measurement period.
seconds when the cell "Operational State is disabled" and the "Energy State is energySaving".
nal State changes to disabled" and the "Energy State is energySaving".
eption of an S1AP:HANDOVER COMMAND message from the MME in case that this message is received in response to the preparation o
eption of an S1AP:HANDOVER COMMAND message from the MME in case that this message is received in response to the preparation o
eption of an S1AP:UE CONTEXT RELEASE COMMAND message from the MME with the cause value Radio Network Layer (Successful H
eption
(3GPP ofTS36.423)
an S1AP:UE CONTEXT
in case that theRELEASE
timer wasCOMMAND message
started because of anfrom the MME with
inter-frequency theeNB
Inter cause value Radio Network Layer (Successful H
Handover.
verall (3GPP
iration TS 36.413)
of the timer in case that(3GPP
TX2RELOCoverall the timer was started
TS36.423) if thebecause
timer was of started
an inter-frequency
because ofInter eNB Handover.Inter eNB Handover when m
an inter-frequency
iration of the guarding timer TS1RELOCoverall (3GPP TS 36.413) in case that the timer was started because of an inter-frequency Inter e
ource eNB -> MME; 3GPP TS 36.413) in case that this message prepares an Inter eNB Handover for an IMS emergency session.
onnection Reconfiguration message (sent by the eNB to the UE), which indicates a Handover Command to the UE in case this message is
eption of an S1AP:UE CONTEXT RELEASE COMMAND message from the MME with cause value Radio Network Layer (Successful Hand
message (source eNB <- MME; 3GPP TS 36.413) in case that this message is received in response to the preparation of an Inter eNB Han
message (source eNB <- MME; 3GPP TS 36.413) in case that this message is received in response to the preparation of an Inter-eNB Han
COMMAND message (source eNB <- MME; 3GPP TS 36.413) with cause value Radio Network Layer (Successful Handover) in case that
NDOVER COMMAND message (source eNB <- MME; 3GPP TS 36.413) in case that this message is received in response to the preparatio
CONTEXT RELEASE
from counting. COMMAND
The case message (source
of reestablishment eNB <- MME;
cause 'HOfailure' 3GPP TS
is excluded 36.413)
from withwhen
counting cause value Radio Network
re-establishment target Layer
cell is (Successful
prepared forHin
e considered UE context may be ongoing. The target cell of such HO preparation can be different from the cell receiving the reestablishmen
sluerecognized by reestablishment
of Tstore_UE_cntxt cause
timer up from HO'HOfailure'.
completion.
HOfailure') received at cell prepared for incoming HO or at HO source cell is excluded from counting.
onnection Reconfiguration message (sent by the eNB to the UE) which indicates a Handover Command to the UE in case this message is s
eption of an S1AP: UE CONTEXT RELEASE COMMAND message from the MME with cause value Radio Network Layer (Successful Hand
an S1AP: HANDOVER REQUEST message (MME -> target eNB) in case that this message is received for an inter-RAT handover prepara
eption of an S1AP: HANDOVER REQUEST message (MME -> target eNB) in case that this message is received for an inter-eNB handover
eption of an S1AP: HANDOVER REQUEST message (MME -> target eNB) in case that this message is received for an inter-eNB handover
eption of an S1AP: HANDOVER REQUEST message (MME -> target eNB) in case that this message is received for an inter-eNB handover
eption of an S1AP: HANDOVER REQUEST message (MME -> target eNB) in case that this message is received for an inter-eNB handover
n of an S1AP: HANDOVER REQUEST ACKNOWLEDGE message (target eNB -> MME) in case that this message is sent for a successful
smission of an S1AP: HANDOVER REQUEST ACKNOWLEDGE message (target eNB -> MME) in case that this message is sent for a suc
smission of an S1AP: HANDOVER REQUEST ACKNOWLEDGE message (target eNB -> MME) in case that this message is sent for a suc
smission of an S1AP: HANDOVER REQUEST ACKNOWLEDGE message (target eNB -> MME) in case that this message is sent for a suc
smission of an S1AP: HANDOVER REQUEST ACKNOWLEDGE message (target eNB -> MME) in case that this message is sent for a suc
n of an S1AP: HANDOVER FAILURE message (target eNB -> MME) in case that this message is sent for an inter-RAT handover preparatio
n of an S1AP: HANDOVER FAILURE message (target eNB -> MME) in case that this message is sent for an inter-RAT handover preparatio
onnection Reconfiguration message (sent by the eNB to the UE), which indicates a handover command to the UE in case this message is s
eption
eighborofeNBan S1AP: UE CONTEXT RELEASE COMMAND message from the MME with cause value Radio Network Layer (Successful Hand
_x000D_
n of Timer (wait for X2 SETUP RESPONSE) _x000D_
the interface.
fore it is possible that it rolls over within 15 minutes. An indication of a possible misconfiguration can be derived anyway.
onveying IP payload is received that is addressed to one of the multicast MAC addresses configured for IP applications of the NE.
enerated by an IP application of the network element is transmitted at one of the NE link layer interfaces.
tiator message that the BTS has sent over this TWAMP session.
tiator message that the BTS has sent over this TWAMP session, for which a new maximum round trip time is detected.
tiator message that the BTS has sent over this TWAMP session, for which a new minimum round trip time is detected.
or the session.
est message.
quest message.
quest message.
alValue) / actualIntervalLength"
the UE to eNB.
a row without waiting the proper time for the response from eNB (RRCConnectionSetup), only the last message will be counted.
h is used for emergency sessions (3GPP TS 36.413)
AB Setup List AND was sent in response to the reception of the S1AP: E-RAB SETUP REQUEST message (eNB <- MME) containing the A
AB Failed to Setup List (because of missing RB (Radio Bearer) resources) AND was sent in response to the reception of the S1AP: E-RAB
e UL buffer status is sampled for each active TTI, where data is scheduled for at least one UE.
d for each active TTI, where data is scheduled for at least one UE.
PP TS 36.331, TS 36.306); the average is calculated as the arithmetical average over the measurement period.
measurement period.
n case that the S1AP:UE CONTEXT RELEASE COMMAND is received as a response to a previously sent S1AP:UE CONTEXT RELEASE
n case that the S1AP:UE CONTEXT RELEASE COMMAND is received as a response to a previously sent S1AP:UE CONTEXT RELEASE
n case that the S1AP:UE CONTEXT RELEASE COMMAND is received as a response to a previously sent S1AP:UE CONTEXT RELEASE
the number of E-RABs released with the TNL cause "TNL Unspecified" (3GPP TS 36.413).
values over the measurement period.
values over the measurement period.
values over the measurement period.
values over the measurement period.
values over the measurement period.
values over the measurement period.
values over the measurement period.
values over the measurement period.
values over the measurement period.
er of bearers contained in the "E-RAB Failed To Modify List" with the RNL cause "Radio resources not available" (3GPP TS 36.413).
er of bearers contained in the "E-RAB Failed To Modify List" with the TNL cause "Transport Resource Unavailable" (3GPP TS 36.413).
eNB to the MME with the release cause "RNL Radio Connection with UE lost".
eNB to the MME with the release cause "RNL Radio Connection with UE lost".
eNB to the MME with the release cause "RNL Radio Connection with UE lost".
eNB to the MME with the release cause "RNL Radio Connection with UE lost".
eNB to the MME with the release cause "RNL Radio Connection with UE lost".
:INITIAL CONTEXT SETUP FAILURE message is sent with the RNL cause "Radio resources not available" (3GPP TS 36.413).
:INITIAL CONTEXT SETUP FAILURE message is sent with the TNL cause "Transport Resources Unavailable" (3GPP TS 36.413).
:INITIAL CONTEXT SETUP FAILURE message is sent with the RNL cause "Radio Connection with UE lost" (3GPP TS 36.413).
:INITIAL CONTEXT SETUP FAILURE message is sent with the RNL cause "Failure in the Radio Interface Procedure" (3GPP TS 36.413).
r of bearers contained in the "E-RAB Failed to Setup List" IE with the RNL cause "Radio resources not available" (3GPP TS 36.413).
er of bearers contained in the "E-RAB Failed to Setup List" IE with the TNL cause "Transport Resources Unavailable" (3GPP TS 36.413).
r of bearers contained in the "E-RAB Failed to Setup List" IE with the RNL cause "Radio Connection with UE lost" (3GPP TS 36.413).
r of bearers contained in the "E-RAB Failed to Setup List" IE with the RNL cause "Failure in the Radio Interface Procedure" (3GPP TS 36.4
r of bearers contained in the "E-RAB Failed to Setup List" IE with the Miscellaneous Cause "Not enough User Plane Processing Resources
r of bearers contained in the "E-RAB Failed to Setup List" IE with the RNL causes "S1 Intra System Handover Triggered", "S1 inter system
to the MME. The counter is incremented with the number of E-RABs released independently from the release cause (3GPP TS 36.413).
ME. The counter is incremented with the number of released E-RABs (3GPP TS 36.413).
e eNB to the MME. If the S1AP:UE CONTEXT RELEASE REQUEST message with the RNL cause "Radio Connection with UE lost" is sen
he eNB to the MME with the TNL cause "Transport Resources Unavailable". The counter is incremented with the number of released E-RA
redirection", "Redirection towards 1xRTT", "CS Fallback Triggered", "UE Not Available For PS Service", or "E-UTRAN Generated Reason" i
e eNB to the MME if the release cause is not set due to an intra LTE redirect. The counter is incremented with the number of released E-RA
o the MME. The counter is incremented with the number of E-RABs released with the RNL cause "Radio resources not available" (3GPP T
of bearers not admitted by the HO target of the preceding HO preparation procedure. The bearers, which are not admitted, are contained i
contained in the "E-RABs to Release List" IE of the S1AP:HANDOVER COMMAND message that is received from the MME (3GPP TS 36.4
r of bearers admitted by the HO target of the preceding HO preparation procedure. The bearers, which are not admitted, are contained in th
unter is incremented with the number of bearers admitted by the HO target during the preceding HO preparation procedure. The bearers, w
ber of bearers contained in the "E-RAB Failed to Release List" IE (3GPP TS 36.413).
o the MME. The counter is incremented with the number of QCI1 E-RABs released independently from the release cause (3GPP TS 36.413
ME. The counter is incremented with the number of released QCI1 E-RABs (3GPP TS 36.413).
e eNB to the MME. If the S1AP:UE CONTEXT RELEASE REQUEST message with the RNL cause "Radio Connection with UE lost" is sen
he eNB to the MME with the TNL cause "Transport Resources Unavailable". The counter is incremented with the number of released QCI1
edirection", "Redirection towards 1xRTT", "CS Fallback Triggered", "UE Not Available For PS Service", or "E-UTRAN Generated Reason" if
e eNB to the MME if the release cause is not set due to an intra-LTE redirect. The counter is incremented with the number of released QCI1
o the MME. The counter is incremented with the number of QCI1 E-RABs released with the RNL cause "Radio resources not available" (3G
of QCI1 bearers not admitted by the HO target of the preceding HO preparation procedure. The bearers, which are not admitted, are conta
dmitted, are contained in the "E-RABs to Release List" IE of the S1AP:HANDOVER COMMAND message that is received from MME as the
r of QCI1 bearers admitted by the target eNB during the preceding HO preparation procedure. The QCI1 bearers, which are not admitted, a
unter is incremented with the number of QCI1 bearers admitted by the HO target during the preceding HO preparation procedure. The QCI
urity information) will not be counted.
onSetup), only the last message of RRC CONNECTION SETUP will be counted.
ped when the RRC CONNECTION SETUP COMPLETE message is received from the UE.
eans that no E-RAB setup occurred in the cell during the whole granularity period and that the measurement does not contain a valid measu
eans that no E-RAB setup occurred in the cell during the whole granularity period and that the measurement does not contain a valid measu
"handoverFailure".
"otherFailure".
nt result contains all necessary IEs needed for a unique cell identification, which are: the CGI, the RNC-Id, the LAC and the RAC.
nt result does not contain the necessary IEs needed for a unique cell identification like the LAC or RAC.
or parameter for a Home
the replacement eNB (3GPP
of an existing TS 36.331).
broadcast message is received via an S1AP:WRITE-REPLACE WARNING REQUEST message.
RNING REQUEST message with Message Identifier IE and Serial Number IE which correspond to one of the warning messages already be
eans that no RRC connection setup occurred in the cell during the whole granularity period and that the measurement does not contain a va
eans that no RRC connection setup occurred in the cell during the whole granularity period and that the measurement does not contain a va
ted if the failure detected does not match any other failure counter. Updated to the source cell.
smissions and retransmissions.
age for both new transmissions and retransmissions.
p Actual Single Codeword mapping to single layer mode usage for both new transmissions and retransmissions.
p Actual Double Codeword mapping to dual layers mode usage for both new transmissions and retransmissions.
ode changes only on the basis of the new CQI / RI value decisions according to MIMO algorithm. However, this counter does not these mod
on mode changes only on the basis of the new CQI / RI value decisions according to MIMO algorithm. However, this counter does not cou
tual Double Codeword mapping to 3-layer mode usage for both new transmissions and retransmissions.
tual Double Codeword mapping to 4-layer mode usage for both new transmissions and retransmissions.
ual Single Codeword mapping to 2-layer mode usage for both new transmissions and retransmissions.
nally allocated AGG, is considered as blocked.
nally allocated AGG, is considered as blocked.
nally allocated AGG, is considered as blocked.
ith required power for finally allocated AGG, is considered as blocked.
mple, the special subframes in the configuration of normal CP and special subframe configuration 5 (TDD only), the subframes with PRS, M
O) is also counted.
is also counted.
sage, which included an "SCellToAddModList-r10" parameter and if a configured SCell is replaced by another one due to an Event A6 meas
d in the counter.
s received in UL for one E-RAB during a sample of ThpTimeUl. (It must exclude the volume of the last piece
s received in UL for one E-RAB during a sample of ThpTimeUl. (It must exclude the volume of the last piece
s received in UL for one E-RAB during a sample of ThpTimeUl. (It must exclude the volume of the last piece
s received in UL for one E-RAB during a sample of ThpTimeUl. (It must exclude the volume of the last piece
s received in UL for one E-RAB during a sample of ThpTimeUl. (It must exclude the volume of the last piece
s received in UL for one E-RAB during a sample of ThpTimeUl. (It must exclude the volume of the last piece
s received in UL for one E-RAB during a sample of ThpTimeUl. (It must exclude the volume of the last piece
s received in UL for one E-RAB during a sample of ThpTimeUl. (It must exclude the volume of the last piece
s received in UL for one E-RAB during a sample of ThpTimeUl. (It must exclude the volume of the last piece
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ere was data in the buffer but the UE was not scheduled.
ctionRequest message (eNB <-UE) with EstablishmentCause set to emergency (3GPP TS 36.331)
reception of the previous RRC:RRCConnectionRequest message (eNB <- UE) with EstablishmentCause set to emergency (3GPP TS 36.3
t message (UE -> eNB) with EstablishmentCause set to any other cause than "emergency" (3GPP TS 36.331).
t message (UE -> eNB) with EstablishmentCause set to "emergency" (3GPP TS 36.331).
age will be counted.
quest message (UE -> eNB) with EstablishmentCause set to highPriorityAccess (3GPP TS 36.331).
message (UE -> eNB) with EstablishmentCause set to "highPriorityAccess" (3GPP TS 36.331).
age will be counted.
age will be counted.
age will be counted.
age will be counted.
age will be counted.
message (UE -> eNB) with EstablishmentCause set to "mo-Signalling" (3GPP TS 36.331).
message (UE -> eNB) with EstablishmentCause set to "mo-Data" (3GPP TS 36.331).
message (UE -> eNB) with EstablishmentCause set to "mt-Access" (3GPP TS 36.331).
message (UE -> eNB) with EstablishmentCause set to "delayTolerantAccess" (3GPP TS 36.331).
ns adrmitted in the cell is reached. It shall be noted that for the Establishment Cause "emergency" the threshold 'maxNumRrcEmergency' is
ailable in Target Cell" if this message is received in response to the preparation of an Inter eNB Handover.
o Radio Resources Available in Target Cell" in case that this message is received in response to the preparation of an Inter eNB Handover.
ponse to the preparation of an Inter eNB Handover.
etwork Layer (Successful Handover) in case that this message is received for an Inter eNB Handover.
ayer (Successful Handover) in case that this message is received for an Inter eNB Handover.
ter-eNB Handover.
e-establishment target cell is prepared for incoming HO, as this means HO has been attempted, not missed. In case of reestablishment requ
ell receiving the reestablishment request.
message is sent for the preparation of a CS Fallback to 1xRTT/CDMA2000 (CDMA2000-Type is set to type1XRTT).
s received for the preparation of a CS Fallback to 1xRTT/CDMA2000 (CDMA2000-Type is set to type1XRTT).
message indicates a "HO Failure" for the CS Fallback preparation to 1xRTT (CDMA2000 HO Status is set to HO Failure, CDMA2000 RAT
of the handover. This counter is updated in case of PS-HO to UTRAN, Inter System Handover to WCDMA with SRVCC and in case of CS F
Handover. This counter is updated for the source cell of the handover. This counter is updated in case of PS-HO to UTRAN, Inter System H
er System Handover. This counter is updated for the source cell of the handover. This counter is updated in case of PS-HO to UTRAN, Inte
to UTRAN. This counter is updated for the source cell of the handover.
counter is updated in case of PS-HO to UTRAN, Inter System Handover to WCDMA with SRVCC and in case of CS Fallback to UTRAN wi
Inter System Handover to UTRAN with SRVCC (Single Radio Voice Call Continuity, 3GPP TS 23.216).
er)" in case that this message is received for an Inter System Handover to UTRAN with SRVCC (Single Radio Voice Call Continuity, 3GPP
e Radio Voice Call Continuity, 3GPP TS 23.216).
adio Network Layer (Successful Handover) in case that this message is received for a Inter System Handover to eHRPD.
usly received X2AP:RLF INDICATION message from the requesting eNB.
ggered Handover.
a bypass policy.
ed anyway.
the MME with any RNL cause except "radio resources not available".
sage (eNB -> MME; 3GPP TS 36.413) in case that these messages are used to release one or more GBR bearers with RNL cause "Radio
sage (eNB -> MME; 3GPP TS 36.413) in case that these messages are used to release one or more non-GBR bearers with RNL cause "R
3GPP TS 36.413).
e" (3GPP TS 36.413).
(3GPP TS 36.413).
ocedure" (3GPP TS 36.413).
ble" (3GPP TS 36.413).
ailable" (3GPP TS 36.413).
lost" (3GPP TS 36.413).
ce Procedure" (3GPP TS 36.413).
r Plane Processing Resources" (3GPP TS 36.413).
r Triggered", "S1 inter system Handover triggered", "X2 Handover triggered", "Inter-RAT redirection", "CS Fallback Triggered", or "E-UTRAN
e cause (3GPP TS 36.413).
onnection with UE lost" is sent due to failed intra-eNB HO, (for example, expiration of HO guard timer THOoverall), the counter ERAB_REL
h the number of released E-RABs (3GPP TS 36.413).
-UTRAN Generated Reason" if the release cause is set due to an intra-LTE redirect. The counter is incremented with the number of release
h the number of released E-RABs (3GPP TS 36.413).
ources not available" (3GPP TS 36.413).
e not admitted, are contained in the "E-RABs to Release List" IE of the S1AP:HANDOVER COMMAND message that is received from MM
from the MME (3GPP TS 36.413).
ot admitted, are contained in the "E-RABs to Release List" IE of the S1AP:HANDOVER COMMAND message that is received from MME (
ion procedure. The bearers, which are not admitted, are contained in the "E-RABs to Release List" IE of the S1AP:HANDOVER COMMAND
onnection with UE lost" is sent due to a failed intra eNB HO, (for example, expiration of HO guard timer THOoverall), the counter ERAB_RE
h the number of released QCI1 E-RABs (3GPP TS 36.413).
UTRAN Generated Reason" if the release cause is set due to an intra-LTE redirect. The counter is incremented with the number of release
h the number of released QCI1 E-RABs (3GPP TS 36.413).
o resources not available" (3GPP TS 36.413).
ich are not admitted, are contained in the "E-RABs to Release List" IE of the S1AP:HANDOVER COMMAND message that is received from
at is received from MME as the outcome of the HO preparation procedure (3GPP TS 36.413).
rers, which are not admitted, are contained in the "E-RABs to Release List" IE of the S1AP:HANDOVER COMMAND message that is rece
eparation procedure. The QCI1 bearers, which are not admitted, are contained in the "E-RABs to Release List" IE of the S1AP:HANDOVER
does not contain a valid measurement result.
does not contain a valid measurement result.
REQUEST message.
warning messages already being broadcast in the eNB.
urement does not contain a valid measurement result.
urement does not contain a valid measurement result.
is counter does not these mode changes count if transmission mode changes in case of retransmissions or transmissions not needing MIM
ver, this counter does not count these mode changes if transmission mode changes in case of retransmissions or transmissions not needin
y), the subframes with PRS, MBMS subframes, ABS subframes, and so on.
d to neighbor cells).
on interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
on interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
on interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
on interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
on interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
on interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
on interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
on interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
on interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
fic every sample period. At the end of the collection interval the accumulated used PRBs are divided by the accumulated available PRBs to
n interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the percentage value.
ollection interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
ollection interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
ollection interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
ollection interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
ollection interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
ollection interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
ollection interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
ollection interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
ollection interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the measurement percentage value.
CH traffic every sample period. At the end of the collection interval the accumulated used PRBs are divided by the accumulated available PR
lection interval the accumulated used PRBs is divided by the accumulated available PRBs to obtain the percentage value.
one due to an Event A6 measurement result that is received from the UE.
to emergency (3GPP TS 36.331).
inactivity", "Radio Connection With UE Lost", "Failure in the Radio Interface Procedure", "TX2RELOCOverall Expiry", "TS1RELOCoverall E
ase of a failed intra eNB HO, the counter UE_CTX_REL_ENB_TIMER_HO is updated (3GPP TS 36.413).
dover, the release cause "RNL TS1RELOCoverall Expiry" is used. In case of an intra eNB handover, the release cause "RNL Radio Conne
old 'maxNumRrcEmergency' is used. For all other establishment causes the threshold 'maxNumRrc' is used (3GPP TS 36.331).
n case of reestablishment request to cell prepared for incoming HO, the case of received PCI different from source cell PCI of prepared HO
-eNB handover.
establishment request to cell prepared for incoming HO, the case of received PCI different from source cell PCI of prepared HO is excluded
er-eNB Handover.
ndover.
ble for Radio Reasons.
Serving Cell.
zation Handover.
r to eHRPD.
e is greater than or equal to -10 dB and less than or equal to -8 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than -8 dB and less than or equal to -6 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than -6 dB and less than or equal to -4 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than -4 dB and less than or equal to -2 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than -2 dB and less than or equal to 0 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 0 dB and less than or equal to 2 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 2 dB and less than or equal to 4 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 4 dB and less than or equal to 6 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 6 dB and less than or equal to 8 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 8 dB and less than or equal to 10 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 10 dB and less than or equal to 12 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 12 dB and less than or equal to 14 db. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 14 dB and less than or equal to 16 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 16 dB and less than or equal to 18 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 18 dB and less than or equal to 20 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 20 dB and less than or equal to 22 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 22 dB and less than or equal to 24 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 24 dB and less than or equal to 26 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 26 dB and less than or equal to 28 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than 28 dB and less than or equal to 30 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
e is greater than or equal to -10 dB and less than or equal to -8 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than -8 dB and less than or equal to -6 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than -6 dB and less than or equal to -4 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than -4 dB and less than or equal to -2 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than -2 dB and less than or equal to 0 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 0 dB and less than or equal to 2 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 2 dB and less than or equal to 4 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 4 dB and less than or equal to 6 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 6 dB and less than or equal to 8 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 8 dB and less than or equal to 10 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 10 dB and less than or equal to 12 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 12 dB and less than or equal to 14 db. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 14 dB and less than or equal to 16 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 16 dB and less than or equal to 18 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 18 dB and less than or equal to 20 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 20 dB and less than or equal to 22 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 22 dB and less than or equal to 24 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 24 dB and less than or equal to 26 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 26 dB and less than or equal to 28 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than 28 dB and less than or equal to 30 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
e is greater than or equal to -10 dB and less than or equal to -8 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than -8 dB and less than or equal to -6 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than -6 dB and less than or equal to -4 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than -4 dB and less than or equal to -2 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than -2 dB and less than or equal to 0 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 0 dB and less than or equal to 2 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 2 dB and less than or equal to 4 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 4 dB and less than or equal to 6 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 6 dB and less than or equal to 8 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 8 dB and less than or equal to 10 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 10 dB and less than or equal to 12 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 12 dB and less than or equal to 14 db. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 14 dB and less than or equal to 16 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 16 dB and less than or equal to 18 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 18 dB and less than or equal to 20 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 20 dB and less than or equal to 22 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 22 dB and less than or equal to 24 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 24 dB and less than or equal to 26 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 26 dB and less than or equal to 28 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
e is greater than 28 dB and less than or equal to 30 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than or equal to -10 dB and less than or equal to -8 dB. Subband 11 for 20 MHz refers to PRB#80 t
ulated values where each one is greater than -8 dB and less than or equal to -6 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than -6 dB and less than or equal to -4 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than -4 dB and less than or equal to -2 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than -2 dB and less than or equal to 0 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 0 dB and less than or equal to 2 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 2 dB and less than or equal to 4 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 4 dB and less than or equal to 6 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 6 dB and less than or equal to 8 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 8 dB and less than or equal to 10 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 10 dB and less than or equal to 12 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 12 dB and less than or equal to 14 db. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 14 dB and less than or equal to 16 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 16 dB and less than or equal to 18 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 18 dB and less than or equal to 20 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 20 dB and less than or equal to 22 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 22 dB and less than or equal to 24 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 24 dB and less than or equal to 26 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 26 dB and less than or equal to 28 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than 28 dB and less than or equal to 30 dB. Subband 11 for 20 MHz refers to PRB#80 to PRB#87.
ulated values where each one is greater than or equal to -10 dB and less than or equal to -8 dB. Subband 12 for 20 MHz refers to PRB#88 t
ulated values where each one is greater than -8 dB and less than or equal to -6 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than -6 dB and less than or equal to -4 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than -4 dB and less than or equal to -2 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than -2 dB and less than or equal to 0 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 0 dB and less than or equal to 2 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 2 dB and less than or equal to 4 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 4 dB and less than or equal to 6 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 6 dB and less than or equal to 8 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 8 dB and less than or equal to 10 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 10 dB and less than or equal to 12 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 12 dB and less than or equal to 14 db. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 14 dB and less than or equal to 16 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 16 dB and less than or equal to 18 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 18 dB and less than or equal to 20 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 20 dB and less than or equal to 22 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 22 dB and less than or equal to 24 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 24 dB and less than or equal to 26 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 26 dB and less than or equal to 28 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than 28 dB and less than or equal to 30 dB. Subband 12 for 20 MHz refers to PRB#88 to PRB#95.
ulated values where each one is greater than or equal to -10 dB and less than or equal to -8 dB. Subband 13 for 20 MHz refers to PRB#96 t
ulated values where each one is greater than -8 dB and less than or equal to -6 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than -6 dB and less than or equal to -4 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than -4 dB and less than or equal to -2 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than -2 dB and less than or equal to 0 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 0 dB and less than or equal to 2 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 2 dB and less than or equal to 4 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 4 dB and less than or equal to 6 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 6 dB and less than or equal to 8 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 8 dB and less than or equal to 10 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 10 dB and less than or equal to 12 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 12 dB and less than or equal to 14 db. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 14 dB and less than or equal to 16 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 16 dB and less than or equal to 18 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 18 dB and less than or equal to 20 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 20 dB and less than or equal to 22 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 22 dB and less than or equal to 24 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 24 dB and less than or equal to 26 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 26 dB and less than or equal to 28 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
ulated values where each one is greater than 28 dB and less than or equal to 30 dB. Subband 13 for 20 MHz refers to PRB#96 to PRB#99.
is greater than or equal to -10 dB and less than or equal to -8 dB.
is greater than -8 dB and less than or equal to -6 dB.
is greater than -6 dB and less than or equal to -4 dB.
is greater than -4 dB and less than or equal to -2 dB.
is greater than -2 dB and less than or equal to 0 dB.
is greater than 0 dB and less than or equal to 2 dB.
is greater than 2 dB and less than or equal to 4 dB.
is greater than 4 dB and less than or equal to 6 dB.
is greater than 6 dB and less than or equal to 8 dB.
is greater than 8 dB and less than or equal to 10 dB.
is greater than 10 dB and less than or equal to 12 dB.
is greater than 12 dB and less than or equal to 14 dB.
is greater than 14 dB and less than or equal to 16 dB.
is greater than 16 dB and less than or equal to 18 dB.
is greater than 18 dB and less than or equal to 20 dB.
is greater than 20 dB and less than or equal to 22 dB.
is greater than 22 dB and less than or equal to 24 dB.
is greater than 24 dB and less than or equal to 26 dB.
is greater than 26 dB and less than or equal to 28 dB.
is greater than 28 dB and less than or equal to 30 dB.
ated values where each one is greater than or equal to -10 dB and less than or equal to -8 dB.
ated values where each one is greater than -8 dB and less than or equal to -6 dB.
ated values where each one is greater than -6 dB and less than or equal to -4 dB.
ated values where each one is greater than -4 dB and less than or equal to -2 dB.
ated values where each one is greater than -2 dB and less than or equal to 0 dB.
ated values where each one is greater than 0 dB and less than or equal to 2 dB.
ated values where each one is greater than 2 dB and less than or equal to 4 dB.
ated values where each one is greater than 4 dB and less than or equal to 6 dB.
ated values where each one is greater than 6 dB and less than or equal to 8 dB.
ated values where each one is greater than 8 dB and less than or equal to 10 dB.
ated values where each one is greater than 10 dB and less than or equal to 12 dB.
ated values where each one is greater than 12 dB and less than or equal to 14 dB.
ated values where each one is greater than 14 dB and less than or equal to 16 dB.
ated values where each one is greater than 16 dB and less than or equal to 18 dB.
ated values where each one is greater than 18 dB and less than or equal to 20 dB.
ated values where each one is greater than 20 dB and less than or equal to 22 dB.
ated values where each one is greater than 22 dB and less than or equal to 24 dB.
ated values where each one is greater than 24 dB and less than or equal to 26 dB.
ated values where each one is greater than 26 dB and less than or equal to 28 dB.
ated values where each one is greater than 28 dB and less than or equal to 30 dB.
in case when LTE1198 is activated , additional condition has to be met : the reported measResults.measResultP
in case when LTE1198 is activated , additional condition has to be met : th
A positive evaluation of the received RRC Measurement Report message with measResult IE containing measId
earers with RNL cause "Radio resources not available".
BR bearers with RNL cause "Radio resources not available".
y sessions (3GPP TS 36.413).
d Retention Priority) priority level which is used for emergency sessions (3GPP TS 36.413).
back Triggered", or "E-UTRAN Generated Reason" if the reject cause is set due to an intra-LTE redirect (3GPP TS 36.413).
erall), the counter ERAB_REL_HO_FAIL_TIM is incremented instead. The counter is incremented with the number of released E-RABs (3G
overall), the counter ERAB_REL_HO_FAIL_TIM_QCI1 is incremented instead. The counter is incremented with the number of released QC
MMAND message that is received from MME as the outcome of the HO preparation procedure (3GPP TS 36.413).
t" IE of the S1AP:HANDOVER COMMAND message that is received from MME (3GPP TS 36.413).
ansmissions not needing MIMO due to small amount of data.
ns or transmissions not needing MIMO due to small amount of data.
ment percentage value.
ment percentage value.
ment percentage value.
ment percentage value.
ment percentage value.
ment percentage value.
ment percentage value.
ment percentage value.
ment percentage value.
ccumulated available PRBs to obtain the measurement percentage value.
ase cause "RNL Radio Connection With UE Lost" is used (3GPP TS 36.413).
3GPP TS 36.331).
N with PS-HO.
ck to UTRAN with PS-HO.
RAN with PS-HO.
CI of prepared HO is excluded from counting.
0 to PRB#87.
8 to PRB#95.
6 to PRB#99.
for 20 MHz refers to PRB#80 to PRB#87.
efers to PRB#80 to PRB#87.
efers to PRB#80 to PRB#87.
efers to PRB#80 to PRB#87.
fers to PRB#80 to PRB#87.
ers to PRB#80 to PRB#87.
ers to PRB#80 to PRB#87.
ers to PRB#80 to PRB#87.
ers to PRB#80 to PRB#87.
efers to PRB#80 to PRB#87.
refers to PRB#80 to PRB#87.
refers to PRB#80 to PRB#87.
refers to PRB#80 to PRB#87.
refers to PRB#80 to PRB#87.
refers to PRB#80 to PRB#87.
refers to PRB#80 to PRB#87.
refers to PRB#80 to PRB#87.
refers to PRB#80 to PRB#87.
refers to PRB#80 to PRB#87.
refers to PRB#80 to PRB#87.
for 20 MHz refers to PRB#88 to PRB#95.
efers to PRB#88 to PRB#95.
efers to PRB#88 to PRB#95.
efers to PRB#88 to PRB#95.
fers to PRB#88 to PRB#95.
ers to PRB#88 to PRB#95.
ers to PRB#88 to PRB#95.
ers to PRB#88 to PRB#95.
ers to PRB#88 to PRB#95.
efers to PRB#88 to PRB#95.
refers to PRB#88 to PRB#95.
refers to PRB#88 to PRB#95.
refers to PRB#88 to PRB#95.
refers to PRB#88 to PRB#95.
refers to PRB#88 to PRB#95.
refers to PRB#88 to PRB#95.
refers to PRB#88 to PRB#95.
refers to PRB#88 to PRB#95.
refers to PRB#88 to PRB#95.
refers to PRB#88 to PRB#95.
for 20 MHz refers to PRB#96 to PRB#99.
efers to PRB#96 to PRB#99.
efers to PRB#96 to PRB#99.
efers to PRB#96 to PRB#99.
fers to PRB#96 to PRB#99.
ers to PRB#96 to PRB#99.
ers to PRB#96 to PRB#99.
ers to PRB#96 to PRB#99.
ers to PRB#96 to PRB#99.
efers to PRB#96 to PRB#99.
refers to PRB#96 to PRB#99.
refers to PRB#96 to PRB#99.
refers to PRB#96 to PRB#99.
refers to PRB#96 to PRB#99.
refers to PRB#96 to PRB#99.
refers to PRB#96 to PRB#99.
refers to PRB#96 to PRB#99.
refers to PRB#96 to PRB#99.
refers to PRB#96 to PRB#99.
refers to PRB#96 to PRB#99.
ted measResults.measResultPCell.rsrqResult is greater than configured A1 RSRQ threshold2aRsrq.
nal condition has to be met : the reported measResults.measResultPCell.rsrqResult is greater than configured A1 RSRQ threshold2aRsrq.
asResult IE containing measId of "Event E-UTRA A4 " for Idle Mode Load Balancing (IMLB) means that the following conditions of the rep
PP TS 36.413).