All KPIs - Except Thruput - For LE6.0 201201030 V1.0 PDF

LE6.0 E2E and RAN KPIs: Part 1 V1.
4
5 LE6.0 E2E and RAN KPIs:
6
7 Part 1
8
9 Version 1.0
10 October, 2012
11
12 Owner:
13 Ming-Hsu Tu
14
15 Authors:
16 Lingshan Kong
17 Subhasis Laha
18 BAI Qing
19 Rongfu Qian
20 Omar Salvador
21 Baoling Sheen
22 Padma Sudarsan
23 Jin Wang
24 Tomas Young
25 Pengfei (Peter) Zhu

26
27
10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 1

Use pursuant to company instructions
LE6.0 E2E and RAN KPIs: Part 1 V1.0
28 PUBLICATION HISTORY
29 July/2011
30 Version 0.1
31 : Initial version
32 August/2011
33 Version 0.4
34 : Final version for LE6.0 Phase 1 (covering Macro cell only) KPI work
35 October/2011
36 Version 1.0
37 : Final version for LE6.0 Phase 2 (including Metro cell traffic model) KPI work
38
39

40
41 TABLE OF CONTENTS
42
43 TABLE OF CONTENTS.................................................................................................. 3
44 1 Introduction ............................................................................................................. 5
45 1.1 Purpose........................................................................................................................ 5
46 1.2 Scope ........................................................................................................................... 5
47 1.3 Audience ...................................................................................................................... 6
48 1.4 Feature Dependency ................................................................................................... 6
49 1.5 Open Issues ................................................................................................................. 6
50 2 Customer network Configurations ........................................................................ 8

51 2.1 Network Configuration and Performance Models ..................................................... 8
52 2.1.1 E2E LTE Network Architecture – Base ................................................................... 8
53 2.2 E2E LTE Network Performance Model ....................................................................... 9
54 2.2.1 E2E Packet Transmission Latency Model ............................................................... 9
55 3 End-to-End LTE Specification Methodologies .................................................... 10

56 3.1 Methodologies ............................................................................................................10
57 3.2 Structure of the Specifications and Requirements ..................................................10
58 3.3 Traffic Model, Loading and Assumption ..................................................................10
59 3.3.1 Traffic Model ..........................................................................................................11
60 3.3.2 Loading ..................................................................................................................11
61 3.3.3 Assumption ............................................................................................................17
62 3.4 Statistics on KPI Targets in Requirements...............................................................18
63 4 End-to-end KPI and Requirement ........................................................................ 19

64 4.1 User Plane Latency KPI .............................................................................................24
65 4.1.1 KPI Summary ........................................................................................................24
66 4.1.2 End-to-End Network Requirement .........................................................................24
67 4.2 Control Plane Latency KPI.........................................................................................48
68 4.2.1 KPI Summary ........................................................................................................48

69 4.2.2 End-to-end Network Requirement ..........................................................................48

70 4.3 Intra-LTE Mobility KPI ................................................................................................73
71 4.3.1 KPI Summary ........................................................................................................73
72 4.3.2 End-to-end Network Requirement for Handover Interruption Time and Procedure
73 Latency KPIs ......................................................................................................................76
74 4.3.3 End-to-end Network Requirement for Handover Success Rate KPIs ...................107
75 4.4 Network Performance and Quality of Experience KPI ...........................................118
76 4.4.1 KPI Summary ......................................................................................................118
77 4.4.2 End-to-end Network Requirement for Network Performance KPIs .......................119
78 4.4.3 End-to-end Network Requirement for Quality of Experience KPIs ........................155
79 4.5 Product Performance KPI ........................................................................................168
80 4.5.1 KPI Summary ......................................................................................................168
81 4.5.2 End-to-end Network Requirement for Product Performance KPIs ........................168
82 4.6 Inter RAT KPI ............................................................................................................173
83 4.6.1 KPI Summary ......................................................................................................173
84 4.6.2 End-to-end Network Requirement ........................................................................173
85 References ................................................................................................................. 210

86 Appendix A: LSTI KPIs ............................................................................................. 214
87 Appendix B: Glossary ............................................................................................... 218

88 1 Introduction
89 1.1 Purpose
90 This document provides specification for the LTE E2E Network Performance KPI targets for Alcatel-
91 Lucent LTE Release LE6.0.
92 This document is the common E2E KPI specification for both FDD and TDD. KPIs specified in this
93 document shall apply to both FDD and TDD unless otherwise specified in the KPI requirements.
94 Requirements are specified in this document to provide guidelines to each LTE Network Element in
95 meeting the expected E2E performance targets based upon current architecture and software. It is
96 expected this document will be used for:
97 • Providing a centralized document to specify LTE E2E performance KPI targets for each LTE
98 release
99 • Driving KPI related requirement documents to be provided by each NE using the specified
100 allocations
101 • Deriving the lab workload model for cluster, Performance Assurance, NLV and FOA test cases
102 The LTE E2E Network Performance KPI Specification document will be issued for every LTE E2E
103 release.
104 The E2E KPIs specified in this document will be verified under Solution level feature LS36001-04.
105 1.2 Scope

106 This document covers the E2E LTE KPIs and their participating NEs for LE6.0 (including macro cells;
107 metro cell information will be added later). If there is more than one software load in LE6.0 then the
108 targets specified in this document shall apply to the last load of LA5.0.3.
109 Starting LE/LA5.0 the LTE E2E KPI Specification will also cover the original scope of the eNB KPI FTS.
110 This document provides input for both RAN R&D team and RAN ST teams. Appendix A lists all the KPIs
111 specified in this document and the scope (E2E, eNB, or both) of each KPI. It is expected these KPIs will
112 be validated by the E2E testing, or by RAN testing or by both teams.
113 This document covers requirements for LTE Network Elements or entities within the LTE scope, which
114 includes UE, air interface, RAN, EPC and other interfacing Network Elements, i.e. PCRF, HSS. This
115 document currently doesn’t cover requirements for IMS.
116 This document is aimed at to have a full coverage for the KPIs that are specified by the PLMs and/or
117 requested by customers so far. This document also provides the guidelines to allow each NE’s document
118 to specify other KPIs if needed following the allocated End-to-end budget specifications.
119 The LTE E2E Network Performance KPI and Specification document is tightly coupled with release
120 features and all performance requirements and specifications are to be reviewed and revised on a per
121 release basis.
122 The testing method section associated with each KPI describes one of the testing options which can be
123 used by the test teams when verifying the KPI. For example, Performance Management Counters (PMCs)
124 or Per Call Measurement Data (PCMD) parameters, if applicable, are specified in the Measurement or UE
125 logs and other active test mechanism may be specified as an option. The post processing tool, NPO, will
126 support the KPI calculations using those counters if specified. Regarding NPO support of LTE node
127 counters, refer to [R6] and [R7]. It is not the intention of this document to dictate how the tests should be
128 performed which should be judged and handled by the test teams. It is recommended that the test effort
129 is coordinated among various teams to avoid any confusion.

130 Before LE4.0 the Network Capacity specification is included in this document. Starting from LE4.0 a
131 separate document [R19]covers Network Element Capacity, thus the capacity sections are now removed
132 from the KPI document.
133 Note:
134 The scope of this KPI document has now been expanded to cover outdoor metro cells in addition to
135 macro cells:
136 • The same KPI definitions and targets that have been defined for Macro Cells apply to Outdoor
137 Metro Cells without any change.
138 • However, the traffic model and capacity numbers are different for the metro cells. These
139 differences have been pointed out in sections 3.3.1 and 3.3.2.3.
140 1.3 Audience

141 This document is intended for internal use only. This document contains sensitive network design and
142 performance information and is NOT viewable to external customers. The audience of this document
143 may include:
144 • RAN R&D team
145 • E2E Solution PLM and Network Product PLM, eNB PLM and EPC PLM
146 • Trial test teams, e.g. RF performance testing, BSHSE & AT & PEC.
147 • Performance Assurance teams (Voice & Data Quality, Over The Air, and RF Performance) for
148 E2E KPI testing
149 • NLV, EPC CLT for critical KPI and EPC KPI testing
150 • RAN ST and Software Integration teams
151 • Technology Introduction Program Management (TIPM) team
152 • Customer FSA or FOA team
153 • LTE NE Architects
154 • LTE NE KPI document authors
155
156 1.4 Feature Dependency

157 :
158 This document inherits all the KPIs from its predecessor KPI specification document for LE5.x [R18].
159
160 1.5 Open Issues

161
162 1. The following HO performance related KPIs will be considered in the next version of the
163 document:
164 - LTE to eHRPD enhanced non-optimized redirection success rate -
165 - CSFB to UTRAN PSHO success rate
166 - CSFB to UTRAN redirection success rate

167 (ATT need to define that, however, the challenge is defining the formula with eNB
168 counters)
169 - CSFB to 1xRTT enhanced non-optimized redirection success rate – Verizon needs

170 - Voice Call Setup Time for CSFB to UTRAN (enhanced redirection)
171 - Voice Call Setup Time for CSFB to GERAN (enhanced redirection)
172 2. Targets for UP_KPI_7aa and UP_KPI_7ba need to be studied further in next version.
173 3. E2E Packet loss KPI need to be updated based on eNB RAN FTS packet loss KPI.
174 4. The voice MoS reading varies with the voice codec, the MoS targets for a specific voice codec for
175 commonly used codec need FFS.
176 5. LTE to UMTS HO interruption time (enhanced redirection) should be addressed.
177 6. LTE to GERAN HO interruption time (enhanced redirection) should be addressed.
178 7. A new KPI for Uplink RLC retransmitted bytes (%) need to be added – need new eNB PM
179 counters to support that KPI.
180 8. Considerations should be given to add traffic loading in the EPC elements for testing
181 KPI’s in future.
182 9. Consider contribution of MME message bundling delay for C-plane latency KPI targets in
183 future.
184
185

186 2 Customer network Configurations
187 2.1 Network Configuration and Performance Models

188 2.1.1 E2E LTE Network Architecture – Base
189 The configurations below describe a base LTE end-to-end network configuration based on LTE standard
190 logic network structure. The customer network configurations for individual customer are not covered
191 in detail in this document.
192
Non-Pooled Nodes
AAA PCRF
CGF IMS
DNS
PGW HSS OAM
S6a S5/S8
SAM NPO NET-P
Core
Network
OAM
EPC Pool A EPC Pool B
S6a Network
S10/S11
MME1 MMEn MME1 MMEn
EPC S5/S8
EPC
SGW1 Network Network
SGWx SGW1 SGWx
S1-U S1-U
S1-MME S1-MME
Backhaul
Network
Pool Area A S1-flex Pool Area B
S1-flex
eNB eNB eNB eNB
LTE-Uu LTE-Uu
eNB eNB eNB eNB
TA1 TAn TA1 TAn
UE UE
193
194
195 Figure-2.1.1-1: LTE End-to-end Reference Network Architecture
196 The KPI targets/requirements specified in this document apply to customer deployment with and without
197 EPC Pools (note: so far all customers will deploy EPC pools).
198 • Pool Area: One or more TAs, which are served by an MME Pool Area and SGW Service Area (note:
199 an SGW Service Area sometimes is also referred to as SGW Pool Area).
200 • MMEs must have S1 (e.g., SCTP) connectivity to all eNBs within the pool area (and overlapping
201 areas).

202 • SGWs must have S1 (e.g., IP/UDP) connectivity to all eNBs within the pool area (and overlapping
203 areas).
204 • The UE is served by any of the MME/SGWs within a pool. No MME/SGW relocation required within
205 the MME/SGW pool.
206 • The eNBs must support S1-flex (which provides capability for eNB to perform MME selection
207 function)
208 As shown in Figure-2.1.1-1 the MME and SGW are the only EPC elements that are deployed in a pooled
209 configuration, in order to support a Pool Area. Other elements (e.g., PGW, HSS, PCRF, AAA, DNS, etc)
210 are not pooled. So each of these (non-pooled) elements need to support the required KPI targets for the
211 Pool Area (these may be deployed per pool area or per multiple pool areas).
212
213 2.2 E2E LTE Network Performance Model

214 The end to end performance model depends on the type of the metric. This section explains the method
215 to determine the end to end performance metrics based on the network element (NE) level performance
216 measurements and transport link level performance measurements. Note in practice, some of the NE-
217 level or link-level performance measurements are not always available. In those cases, the E2E
218 performance metric will be determined by direct E2E measurements or other means.
219
220 2.2.1 E2E Packet Transmission Latency Model

221 For E2E packet latency metric, an additive model is used. That is:
222 E 2 E _ Delay = ∑ NE _ Delay (i ) + ∑ link _ Delay ( j ) .

i j
223 The above formula assumes the delays experienced in different NEs and over different transmission links
224 are independent which excludes parallelism thus the calculated E2E_Delay is an upper-bound for the
225 latency. However, the Excel tool that is used to actually determine the E2E delay KPIs actually take this
226 parallelism into account.
227 The model also assumes the user IP packets are the unit of transmission across different NEs and
228 transmission links, although different protocol overheads may be applied over different segments.
229 Requirements are given for various statistical points:
230 • Average value
231 o Average value is usually the mean value, except when it is specified explicitly as Median
232 (50-percentile) value
233 • 95-percentile
234 o 95% of all measured value are better than this value (for latency this means lower than
235 the specified value)
236 Other percentage may also be adopted
237
238

239 3 End-to-End LTE Specification Methodologies

240 3.1 Methodologies
241 The KPI targets are derived based on the following information:
242 • FRS requirements from PLM [R1] [R22] [R39]
243 • Customer contractual agreements [R23] [R24]
244 • LSTI test specifications (See Appendix A for LSTI KPI specifications)
245 • LTE standard (3GPP TS) [R37] [R38] [R52]
246 • NGMN test requirement [R31]
247 • ALU system simulation and analysis results
248 • ALU testing data
249 • Network element specifications and performance data [R4]
250
251 3.2 Structure of the Specifications and Requirements

252
253 All the customer KPIs are covered in this document under the ALU internal KPIs. All the ALU internal KPIs
254 are categorized in the following categories
255 • User Plane Latency
256 • Control Plane Latency
257 • Mobility
258 • Throughput
259 • Quality of Experience
260 • Network Performance
261 • Product Performance
262 • IRAT
263 .
264 The End-to-end Network Requirements are specified in section 4: End-to-end KPI and Requirement for each
265 ALU Internal KPI in one of the categories specified above.
266
267
268 3.3 Traffic Model, Loading and Assumption

269 o Lawful interception is off.
270 o Throughput KPIs specified in this document are based on certain configuration assumptions and
271 parameters. Some definition about the RF conditions e.g. Near Cell, Mid Cell and Cell Edge (described
272 later in this section) also apply to other KPIs.
273 o It’s recommended to make sufficient test runs to ensure the test results represent the true system
274 performance before the final test outcome is declared. Given that each KPI is different, In general it’s up to
275 test team to determine number of tests to perform. However for some KPIs, requirement may specify # of
276 tests expected to be run.
277
278 3.3.1 Traffic Model

279 The LE6.0 KPIs are specified based on the LTE E2E Traffic Models for LE6.0 – FDD Generic document [R3].
280 The following table provides guidelines on the Traffic Model to follow when validating KPIs.
281
KPI Type Traffic Model Note
FDD VoIP KPIs M2 Refer to Table 7 in [R3] for

applicable QCI values per
application.
FDD All Other KPIs M2-C See above
282 Note: <above macro only>For KPI testing of Outdoor Metro Cells, traffic model as specified in [R55] is
283 applicable. Though the title of this document says “LE7.1”, it is still applicable for LE6.0; there is no separate
284 document for LE6.0 traffic model for small cells. Only the VZ-S model (and NOT the VZ-ST model) is
285 applicable for KPI testing.
286
287 3.3.2 Loading

288 The three main categories of loadings, “No Load”, “Typical Load” and “Full Load” are used in this document. The
289 “No Load” is specified for baseline lab testing. “Typical Load” and “Full Load” are specified for both lab and
290 field/FSA testing with certain assumptions specified in the requirement section. “Typical loading” and “Full Load”
291 exclude the scenarios that UEs are persistently in bad RF conditions.
292 The traffic loading specified in the following sub-sections shall follow the LTE Traffic Models document [R3].
293 Except for the throughput KPIs the following loading conditions apply to all the KPIs specified in this
294 document unless otherwise stated in the KPI section(s).
295 3.3.2.1 No Load: specified for baseline lab testing

296 Table 3.3.2-1
No Load (Single UE)
RF Best lab RF conditions:
Condition
- no HARQ re-transmission and no ARQ re-transmission (see note below)
- 0% OCNS
- No IoT
Traffic Single UE
MIM VZw MIM parameter setting
Setting
Assumption No packet loss
Minimum latency between RAN and EPC
Target Average value of all tests performed for this KPI on the single UE
Other All network traces are turned off
condition
Assume only one Bearer (Default Bearer) for non VoIP/VT KPIs. One default + 1 dedicated
for VoIP. One default and 2 dedicated for VT.
297 Note: There are no packet segmentation in transmissions, any BLER, and any HARQ retransmissions and
298 RLC ARQ retransmissions.
299
300
301 3.3.2.2 Typical load: specified for field testing (assumed loading for initial
302 deployment)
303 Approximately 65% of the maximum loading within the cell vicinity, other cell interference with equivalent
304 other cell loading. Mobiles are located in the mid cell or randomly positioned in the cell. For moving mobiles,
305 the mobile should be in random driving paths at local speeds and highway speeds.
306 Table 3.3.2-2

Typical Load (Multiple UEs)
RF 50% OCNS loading
3dB IoT
25% UEs in NC, 50% UEs in MC and 25% UEs in CE (see note 1 below)
Traffic 65% of LA/LE6.0 maximum engineered capacity [R19] (see note below)
Refer to 3.3.1 for Traffic Model guidelines.
MIM VZw MIM settings
Setting
Target [Average]: Average value of all measurements performed
[X%-tile]: X% of all measured values are better than this value (for latency this means
upper X% of the measured values are lower than the value)
Other Default traces turned on if needed
condition
Number of active Bearers per UE follows the user profile specified in the LTE Traffic
Models document [R3].
Other conditions, e.g. mobility, are specified in the KPI sections if applicable
307
308 Note:
309 1. The UE under test is currently placed in NC RF condition while the background UEs are distributed
310 based on the requirement (25%-50%-25%) except for handover-related KPI’s.
311 The GPL settings for specific releases are available at
312 For all nodes:
313 http://ihgpweb.ih.lucent.com/~mimndata/lte/.
314 The eNodeB specific ones are at
315 http://mobility.web.alcatel-lucent.com/~datadef/lte/enb_gpl/.
316 For customer-specific KPI’s, customer-specific MIM’s should be used and KPI target value may need to
317 be modified accordingly.
318

319 3.3.2.3 Full Load: Specified for lab testing and Field testing
320 The full load lab testing is targeting to test the NE capability to support sustainable capacity with required
321 latency.
322 Table 3.3.2-3

Full Load (Multiple UEs)
RF 100% OCNS loading
5dB IoT
25% UEs in NC, 50% UEs in MC and 25% UEs in CE
(Note: Please see further details below.)
Traffic 100% of LA/LE6.0 maximum engineered capacity [R19] (see note in 3.3.2.2)
Refer to 3.3.1 for Traffic Model guidelines.
MIM VZw MIM settings
Setting
Target [Average]: Average value of all measurements performed
[X%-tile]: X% of all measured value are better than this value (for latency this means lower
than the value)
Other Default traces turned on if needed
condition
Number of active Bearers per UE follows the user profile specified in the LTE Traffic
Models document [R3].
Packet loss on EPC and BH is assumed <10^-5.
Other conditions, e.g. channel mode, mobility, etc. are specified in the KPI sections if
applicable
323
324 In particular the FULL LOAD testing condition with all the static users is referring to a system
325
326 - Lab testing with OCNS loading 100%, 5dB IoT
327 - 25% UEs in Near Cell (NC), 50% UE in Mid Cell (MC) and 25% UE in Cell Edge (CE) for max
328 number of active users in a cell
329 - Lab testing with OCNS loading 100%, 5dB IoT
330 - 25% UEs in Near Cell (NC), 50% UE in Mid Cell (MC) and 25% UE in Cell Edge (CE) for max
331 number of active users in a cell
332 - Testing conditions for Throughput and other KPIs are specified in the following table:
333

DL Configuration UL Configuration
UE location
PDSCH SINR (dB) PUSCH SINR (dB)* Path Loss (dB)*
Peak 25 16 75
Near Cell (NC) 21 13 90
Mid Cell (MC) 11 9 110
Cell Edge (CE) 2 5 130
334 ∗ The following FPC parameters can be used for the stated values of SINR and path loss:
335 Alpha = 0.8, PL nominal = 60 dB, max SINR target max19 dB, min 0 dB, PUSCH P0_nominal = -82
336 dB, UL SINR target 19 dB.
337 ∗ Please note that the (mean Wideband) PUSCH SINR at the eNodeB (along with the stated set of
338 FPC parameters) is the parameter that determines the UE location; the Path Loss is provided here
339 for informational purpose.
340 Note: the UL and DL configurations are configured independently of each other and might not be met
341 simultaneously.
342
343 The UE under test is currently placed in NC RF condition while the background UEs are distributed based on
344 the requirement (25%-50%-25%).
345
346 The Max Active Users per Cell is the max number of user that a cell can support in LE6.0 for 1.4, 3, 5, 10
347 and 20 MHz systems simultaneously with payload traffic. Each active user can have GBR or non GBR
348 bearers.
349
350 In particular the term of Max Number of VoIP Bearers per Cell is referring to the capacity committed by LTE
351 eNB team in terms of max number of VoIP bearers per cell supportable in LE6.0 for 1.4, 3, 5, 10 and 20 MHz
352 systems. Each VoIP bearer can operate either under Semi-Persistent Scheduling (SPS) or under Dynamic
353 Scheduling (DS).
354
355 In LA 6.0, the following capacity is committed by LTE eNB team in terms of max number of bearers per user
356 (max number of bearers for active users). The capacity is also committed in terms of Max Number of Bearer
357 per Cell.
358
359 Max number of VoIP bearers per user is committed in terms of max number of VoIP bearers per active VoIP
360 user. There is no scheduling preference for the VoIP bearers.
361
362 The Max number of bearers per user applies to the mixed data bearers and VoIP bearers with constraints of
363 max number of VoIP bearers per user.

364 Full Load parameters for 1.4, 3, 5, 10, 20 MHz system for Macro Cell:
Release Capacity for
Parameter 1.4 MHz 3 MHz 5 MHz 10 MHz 20 MHz
system system system system system
Max Number of active Users per Cell
200 250 167
(includes VOIP users) for bCEM
Max Number of active Users per Cell

48 100 167 200 54
(includes VOIP users) for eCEM
100(bCEM)
Max Number of VoIP Bearers per Cell 0 0 100 100
40(eCEM)
Max value of Average Number of

3.25 3.25 3.25 3.25 3.25
Bearers per User
eNodeB Paging Capacity (#pages/sec) 500 500 500 500 500
365
366 Full Load parameters for 1.4, 3, 5, 10, 20 MHz system for Metro Cell Outdoor:
367 The above table is applicable to macro cells only. For Metro cells, the following numbers apply for only 5
368 and 10 MHz systems:
369 • Max Number of active Users per Cell (includes VOIP users) = 64
370 • Max Number of VoIP Bearers per Cell = 64 (1 VOIP bearer per user)
371 • Max value of Average Number of Bearers per User = 3.25
372 Note: For KPI testing of Metro Cells, traffic model as specified in [R55] is applicable. Suggested number of
373 UE per cell by application category is specified in Table 7 of [R55]. Only the VZ-S model is
374 applicable for KPI testing. However, a scaling factor of (64/103) needs to be applied to all entries in
375 this table to adjust the total number of active users (#UE) from 103 to 64 for full load. For example,
376 the number of UEs with “Download” for “Full Load” should be taken as 5*(64/103), instead of the
377 stated value of 5.
378
379 3.3.2.3.1 FULL LOAD for U-plane

380 The U-plane Full Load varies with the applications. The FULL LOAD for U-plane defined below is a system
381 traffic load.
382
383 3.3.2.3.1.1 FULL LOAD for VOIP U-plane

384 - Max number of VoIP bearers active in the cell (with 1 VOIP bearer per VOIP user)
385 - Each VoIP users are equipped with AMR WB12.65 Voice codec.
386 - Testing scenarios with ROHC:
387 100% voice bearers with ROHC enabled (ROHC type v1 and profile 0x0001)
388 - Two UE types included in test:
389 a) SPS capable UE
390 b) DS capable UE

391 - The rest of the users are active BE users (max number of active users per cell – max number of
392 active VoIP users/bearers per cell), and each active user’s U-plane traffic profile is defined as in
393 Section 3.1 in [R3]
394 - The % of UE at NC, MC, and CE should be applied to different VoIP UE types and BE UE type.
395 Note: Rel. 9 non-SPS-capable UE and Rel. 9 DS capable UE are associated with different physical layer
396 traffic patterns, such as packet size and packet inter-arrival time.
397
398 3.3.2.3.1.2 FULL LOAD for BE U-plane

399 - No VoIP bearer active in the cell
400 - All users are active BE users (max number of active users per cell),and each users’ U-plane traffic
401 profile is defined as in Section 3.1 in [R3]
402 - The % of UE at NC, MC, and CE should be applied to the BE UEs.
403
404 3.3.2.3.1.3 FULL LOAD for VT U-plane

405 - Max number of VT users active and each VT users video part average throughput Kbps as specified
406 in the table below
407 - VT bearers mapped to either GBR or non-GBR type (both mapping are currently under study)
408 - Max number of VoIP bearers active as background
409 -
410 - Each VoIP user is equipped with AMR WB 12.65 Voice codec
411 - The rest of the users are BE users (max number of active users – max number of VT users – max
412 number of VoIP users/bearers) and each users’ U-plane traffic profile is defined as in Section 3.1 in
413 [R3]
414 - The % of UE at NC, MC, and CE should be applied to VT UE with DS, VoIP UE with SPS, VoIP UE
415 with DS, and the BE UEs with DS respectively.
416 Full Load parameters for 10 MHz system VT
Name Release Capacity
Max number of VT users active 10
Per user Video average throughput (Kbps) 300 ~400 kbps *
417 • This number is preliminary depending on the customer specified video display and resolutions.
418
419 3.3.2.3.1.4 FULL LOAD for C-plane

420 C-plane full load varies with the mixture of different applications and customer call models. The following is a
421 generic C-plane full load definition based on aggregated C-plane traffic models [3].
422 FULL LOAD for C-plane

423 - Max number of active users per cell,
424 - Each UE proceeding C-plane events that are specified in Aggregate M2 model in Section 3.2
425 “General Control Plane Parameters” in [R3] .
426

427 3.3.3 Assumption
428 3.3.3.1 Backhaul Latency Assumption
429 The numbers specified in the following table are used in calculating the E2E latency targets for different
430 interfaces.
431
No Load Full Load Average
Air interface DL (UE-eNB) 0ms 3ms
Air interface UL (eNB-UE) 1ms 2.6ms
X2 (eNB<->eNB) 1ms 1ms
S1-MME (eNB<->MME) 0.5ms 0.5ms
S11 (MME<->SGW) 0.5ms 0.5ms
S4 (SGW<->SGSN) 0.5ms 0.5ms
S5/S8 (SGW<->PGW) 0.5ms 0.5ms
S10 (MME<->MME) 0.5ms 0.5ms
S16 (SGSN<->SGSN) 0.5ms 0.5ms
S6 (MME<->HSS) 0.5ms 0.5ms
Gx (PGW<->PCRF) 0.5ms 0.5ms
Sh (PCRF<->HSS) 0.5ms 0.5ms
S3 0.5ms 0.5ms
IuPS 0.5ms 0.5ms
S1-U (eNB<->SGW) 0.5ms 0.5ms
SGi (PDSN<->Internet or 0ms 0ms

Server)
432
433 The BH (backhaul) latency for full load average all uses minimum BH latency which assumes NEs are
434 collocated thus no propagation delay. It is assumed that the full traffic loading on the participating NEs would
435 not result into backhaul congestion which usually causes the latency to increase. In the field BH latency
436 depends mainly on the distance between the communicating NEs and customer’s configuration. In this case
437 these KPI latency targets need to be adjusted to reflect the real settings in the field.
438
439 3.3.3.2 HSS and PCRF Latency Assumption

440
441 PCRF and HSS message level latency information is provided by PCRF/HSS R&D. The numbers are very
442 conservative and need to be validated during testing phase.
443

444 3.3.3.3 IRAT Latency contribution from other technologies
445 Most of the IRAT KPIs include contribution from systems other than LTE.
446
447 3.4 Statistics on KPI Targets in Requirements

448
449 3.4.1.1Simple Statistics

450 Average or Median covers the samples that have sufficient size of population.
451 Max and Min are also used.
452 3.4.1.2 CDF Percentile (%-ile)

453 Percentile of CDF covers the samples that have sufficient size of population. When the KPI requirement is
454 specified in percentile, the number of sampling points collected through the test shall exceed the required
455 points to ensure high confidence of the reading
456
457 3.4.1.3 Other Statistics

458 Other statistics are used as stated.
459 Testing teams should make sure sufficient tests are run before test statistics are reported to ensure the correctness
460 of the test results.
461 Statistics recording used to compare with the KPI targets should not include any overhead induced by testing
462 or tracing tools. For example, in the latency test, the activation of the traces could induce latency increase in
463 measurement reading. In such a case, the latency increase due to the testing or trace tool should be
464 calibrated and extracted from the measurement reading before the statistics recording.
465

466 4 End-to-end KPI and Requirement

467 To facilitate the testing effort due to large amount of E2E KPIs specified in the document, the following table
468 provides a list of critical KPIs for LE6.0. Different passing criteria can be set accordingly. Please note the list
469 may change depending on feedbacks received from customers.
470
Category KPI ID # KPI Name

st
CP_KPI_2 1 Page Response Time
Control
Plane CP_KPI_27 UE Activation Time
Latency
CP_KPI_27b Service Request Setup Time
Best effort Ping RTD @ 32 Bytes between

UE and Application Server at SGi interface
User Plane UP_KPI_6 (pre-scheduled)
Latency Best effort Ping RTD @ 32 Bytes between
UE and Application Server at SGi interface
UP_KPI_6b (unscheduled)
NP_KPI_11 Intra-eNB HO Success Rate
NP_KPI_12 Inter-eNB X2 HO Success Rate
Mobility Intra-SGW Intra-eNB Best-effort HO

CP_KPI_20 Interruption time
Intra-SGW Inter-eNB Best-effort X2 HO

CP_KPI_23 Interruption time
TH_KPI_DL_FTP_APP_5_ST_Peak_FDD DL FTP Application Layer / PDSCH
throughput@ 5MHz:
TH_KPI_DL_FTP_APP_5_ST_NC_FDD
- Stationary Peak
TH_KPI_DL_FTP_APP_5_ST_MC_FDD
- Stationary Near Cell
TH_KPI_DL_FTP_APP_5_ST_CE_FDD
- Stationary Mid Cell
TH_KPI_DL_FTP_APP_5_ST_Multi_FDD
- Stationary Cell Edge
- Multi-UE (3) with 1/1/1 (NC/MC/CE)
Throughput distribution
(FDD) TH_KPI_DL_FTP_APP_10_ST_Peak_FDD DL FTP Application Layer / PDSCH
throughput@ 10MHz:
- Stationary Peak
distribution


TH_KPI_DL_FTP_APP_20_ST_Peak_FDD DL FTP Application Layer / PDSCH
throughput@ 20MHz:
- Stationary Peak
distribution
TH_KPI_DL_FTP_PHY_5_ST_Peak_FDD DL FTP Physical Layer / PDSCH
throughput@ 5MHz:
TH_KPI_DL_FTP_PHY_5_ST_NC_FDD
- Stationary Peak
TH_KPI_DL_FTP_PHY_5_ST_MC_FDD
TH_KPI_DL_FTP_PHY_5_ST_CE_FDD
TH_KPI_DL_FTP_PHY_5_ST_Multi_FDD
distribution
throughput@ 10MHz:
- Stationary Peak
distribution
throughput@ 20MHz:
- Stationary Peak
distribution
TH_KPI_UL_FTP_APP_5_ST_Peak_FDD UL FTP Application Layer / PUSCH
throughput@ 5MHz:
TH_KPI_UL_FTP_APP_5_ST_NC_FDD
- Stationary Peak
TH_KPI_UL_FTP_APP_5_ST_MC_FDD
TH_KPI_UL_FTP_APP_5_ST_CE_FDD
TH_KPI_UL_FTP_APP_5_ST_Multi_FDD
distribution

TH_KPI_UL_FTP_APP_10_ST_NC_FDD throughput@ 10MHz:
TH_KPI_UL_FTP_APP_10_ST_MC_FDD - Stationary Peak
TH_KPI_UL_FTP_APP_10_ST_CE_FDD - Stationary Near Cell
TH_KPI_UL_FTP_APP_10_ST_Multi_FDD - Stationary Mid Cell

distribution
throughput@ 20MHz:
TH_KPI_UL_FTP_APP_20_ST_NC_FDD
- Stationary Peak
TH_KPI_UL_FTP_APP_20_ST_MC_FDD
TH_KPI_UL_FTP_APP_20_ST_CE_FDD
TH_KPI_UL_FTP_APP_20_ST_Multi_FDD
distribution
TH_KPI_UL_FTP_PHY_5_ST_Peak_FDD UL FTP Physical Layer / PUSCH
throughput@ 5MHz:
TH_KPI_UL_FTP_PHY_5_ST_NC_FDD
- Stationary Peak
TH_KPI_UL_FTP_PHY_5_ST_MC_FDD
TH_KPI_UL_FTP_PHY_5_ST_CE_FDD
TH_KPI_UL_FTP_PHY_5_ST_Multi_FDD
distribution
throughput@ 10MHz:
- Stationary Peak
distribution
throughput@ 20MHz:
- Stationary Peak
distribution
Throughput TH_KPI_DL_FTP_PHY_20_ST_Peak_TDD[1|2]_SS DL FTP Physical Layer / PDSCH Throughput

(TDD) F7_TM[2|3_4|7] @ 20 MHz for Config #1, Config#2, SSF#7,

TM2, TM3/4 and TM7:
TH_KPI_DL_FTP_PHY_20_ST_NC_TDD[1|2]_SSF
7_TM[2|3_4|7] Single UE:
TH_KPI_DL_FTP_PHY_20_ST_MC_TDD[1|2]_SSF o Stationary Peak

7_TM[2|3_4|7] o Stationary Near Cell
TH_KPI_DL_FTP_PHY_20_ST_CE_TDD[1|2]_SSF7 o Stationary Mid Cell
_TM[2|3_4|7]
o Stationary Cell Edge
TH_KPI_DL_FTP_PHY_20_ST_Multi_TDD[1|2]_SSF
Multi-UE (3) with 1/1/1 (NC/MC/CE)
7_TM[2|3_4|7]
distribution
TH_KPI_UL_FTP_PHY_20_ST_Peak_TDD[1|2]_SS UL FTP Physical Layer / PUSCH Throughput

F7_TM[2|3_4|7] @ 20 MHz for Config #1, Config#2, SSF#7,
TM2, TM3/4 and TM7:
TH_KPI_UL_FTP_PHY_20_ST_NC_TDD[1|2]_SSF7
Single UE:
_TM[2|3_4|7]
o Stationary Peak
TH_KPI_UL_FTP_PHY_20_ST_MC_TDD[1|2]_SSF7
_TM[2|3_4|7] o Stationary Near Cell
o Stationary Mid Cell
TH_KPI_UL_FTP_PHY_20_ST_CE_TDD[1|2]_SSF7
_TM[2|3_4|7] o Stationary Cell Edge
TH_KPI_UL_FTP_PHY_[10|20]_ST_Multi_TDD[1|2]_ Multi-UE (3) with 1/1/1 (NC/MC/CE)

SSF7_TM[2|3_4|7] distribution
TH_KPI_DL_UDP_PHY_20_ST_Peak_TDD[1|2]_S DL UDP Physical Layer / PDSCH

SF7_TM[2|3_4|7] Throughput @ 20 MHz for Config #1,
Config#2, SSF#7, TM2, TM3/4 and TM7:
TH_KPI_DL_UDP_PHY_20_ST_NC_TDD[1|2]_SSF
Single UE:
7_TM[2|3_4|7]
o Stationary Peak
TH_KPI_DL_UDP_PHY_20_ST_MC_TDD[1|2]_SSF
TH_KPI_DL_UDP_PHY_20_ST_CE_TDD[1|2]_SSF7
TH_KPI_DL_UDP_PHY_20_ST_Multi_TDD[1|2]_SS Multi-UE (3) with 1/1/1 (NC/MC/CE)

F7_TM[2|3_4|7] distribution
TH_KPI_UL_UDP_PHY_20_ST_Peak_TDD[1|2]_SS UL UDP Physical Layer / PUSCH

F7_TM[2|3_4|7] Throughput @ 20 MHz for Config #1,
Config#2, SSF#7, TM2, TM3/4 and TM7:
TH_KPI_UL_UDP_PHY_20_ST_NC_TDD[1|2]_SSF
Single UE:
7_TM[2|3_4|7]
o Stationary Peak
TH_KPI_UL_UDP_PHY_20_ST_MC_TDD[1|2]_SSF
TH_KPI_UL_UDP_PHY_20_ST_CE_TDD[1|2]_SSF7
TH_KPI_UL_UDP_PHY_[10|20]_ST_Multi_TDD[1|2] Multi-UE (3) with 1/1/1 (NC/MC/CE)

_SSF7_TM[2|3_4|7] distribution
Network NP_KPI_1a Attach Success Rate

Performance NP_KPI_1b Service Request Setup Success Rate
CP_KPI_4 Paging Success Rate
NP_KPI_1 Bearer Establishment Success Rate
NP_KPI_3 UE Context Drop Rate
NP_KPI_9 Drop EPS Bearer Rate
SLA_KPI_1 Attach Failure Rate - ALU system related
Service Request Failure Rate - ALU system

SLA_KPI_2 related
Service Request Setup Success Rate for

NP_KPI_10b emergency call
Quality of NP_KPI_4a Uplink Residual BLER with SPS

Experience
NP_KPI_4b Uplink Residual BLER with DS
NP_KPI_5 Downlink BLER with SPS
NP_KPI_5b Downlink BLER with DS
471
472

473 4.1 User Plane Latency KPI
474 4.1.1 KPI Summary
475 Table 4.1.1-1 User Plane Latency KPIs
User Plane KPIs
KPI ID# KPI Description
UP_KPI_1a VoIP Mobile-to-mobile Mouth-to-ear-delay
UP_KPI_1aa VoIP Mobile-to-mobile packet latency
UP_KPI_3 Best-effort Ping RTD @ 32 Bytes in the RAN(Unscheduled)
UP_KPI_6 Best effort Ping RTD @ 32 Bytes between UE and Application

Server at SGi interface (pre-scheduled)
UP_KPI_6b Best effort Ping RTD @ 32 Bytes between UE and Application

Server at SGi interface (un-scheduled)
UP_KPI_7a VoIP Mobile-to-land Mouth-to-ear-delay
UP_KPI_7aa VoIP Mobile-to-land over Internet packet latency
UP_KPI_7ab VoIP Mobile-to-land over PSTN packet latency
UP_KPI_7b VoIP Land-to-mobile Mouth-to-ear-delay
UP_KPI_7ba VoIP Land-to-mobile over Internet packet latency
UP_KPI_7bb VoIP Land to-mobile over PSTN packet latency
476
477 4.1.2 End-to-End Network Requirement

478
479 ALU KPI ID UP_KPI_1a
ALU KPI ID UP_KPI_1a
ALU KPI Release LE5.0
ALU KPI Name VoIP Mobile-to-Mobile Mouth-to-Ear Delay
ALU KPI Type User Plane Latency
ALU KPI Scope RAN, E2E
ALU KPI Description The mouth-to-ear-delay is defined as time elapse from voice audio feed to output of
receiver after play-out circuits.
ALU Internal Target No Load: 150 msec (Average)

ALU Public Target
ALU Measurement Other (specify below) TBD

Method
ALU KPI Comments The target value assumes zero propagation latency for BH, Intra-net latency, and other
parts of the IP network.
Use 20 VoIP users as LE4.0 full capacity loading
The targets specified assume AMR-WB Voice Codec 12.65kbps.
The UE non-AS processing time 40 ms is assumed. This UE delay due to the AS
processing time and time waiting for UL grants are not included.
The dejittering buffer is assumed 80 ms for no load testing. Linear estimation of the delay
variation are counted.
The mouth-to-ear delay KPIs are application dependent and the enlisted targets are for
VoIP enabled UE. The targets may not be met if using PC based VoIP application.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, BH, IMS, Air Interface, SGW, eNB, PGW
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
SE Feature ID LS36001-03
SE Review Status Approved
Test Consideration SR period = 20 ms

BO status update period = 20 ms
VAF = 100%
Test Notes
Test Owner
Test Reference
Test Feature ID LS36001-03
Test Review Status Approved
Test Plan
480
481
482

483 ALU KPI ID UP_KPI_1aa
ALU KPI ID UP_KPI_1aa
ALU KPI Name VoIP Mobile-to-Mobile Packet Latency
ALU KPI Scope E2E
ALU KPI Description The delay between the VoIP RTP packets captured at the output of the VoIP client of the
source UE transcoder and the corresponding packets captured at the input of the voice
client decoder of the terminating UE.
ALU Internal Target No Load: 55 msec (Average), Typical Load: Full Load: TBD (Average),
ALU Public Target
ALU Measurement Other (specify below) Using UE log to measure the time difference between the first VoIP
packet output from the originating UE and the corresponding packet captured at the
Method terminating UE.
ALU KPI Comments The target values assume zero propagation latency for BH, Intra-net latency, and other
In LA4.0.1 eNB supports the following VoIP related capacity (under feature 114531):
Up to 20 VoIP/Data Active users per cell shall be supported (simultaneously coexisting in
cell)
Up to two simultaneous VoIP bearers per user connection
The target for this KPI is adjusted in LE4.0 to take into account the LE2.1 test results.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution

Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
484
485
486

487 ALU KPI ID UP_KPI_3
ALU KPI ID UP_KPI_3
ALU KPI Name Best-effort Ping RTD @ 32 Bytes in the RAN(Unscheduled)
ALU KPI Scope RAN
ALU KPI Description Round Trip Delay (RTD) time between UE and eNB in both directions for a Ping of size 32
bytes sent from UE to an Application Server that is connected to the SGi interface.
ALU Internal Target No load Average:

23 msec (FDD) with SR=5 msec;
30.5 msec (FDD) with SR=20 msec;
ALU Public Target
ALU Measurement
Method
ALU KPI Comments Note: The RTD value of the server to UE ping is expected to be the same time duration
because of the symmetry in the LTE system.
Critical No
Dashboard
LE1 KPI ID
Validator
Impacted Entities
Application
Duplex Method FDD
Solution eNB
Level Cell
Customer Viewable No

SE Conditions
SE Owner
SE Reference
SE Review Status
Test Consideration
Test Notes
Test Owner
Test Reference
Test Review Status
Test Plan
488
489
490

491 ALU KPI ID UP_KPI_6
ALU KPI ID UP_KPI_6
ALU KPI Name Best effort Ping RTT @ 32 Bytes between UE and Application Server at SGi interface
(pre-scheduled)
ALU KPI Description Round Trip Time (RTT) for a Ping of size 32 bytes measured on the originating device
connected to UE and an Application Server that is connected to the SGi interface.
ALU Internal Target No Load: 18 msec (FDD); 14.5msec (TDD-config 1, SSF7); 15.0 msec (TDD-config 2,
SSF7) (Average),
ALU Public Target
ALU Measurement Other (specify below) Active test from terminal to the server connected to SGi interface.
Method
ALU KPI Comments This requirement does not include delay due to propagation latency for BH, intra-net, and
IP network. The requirement assumes perfect RF condition for no load case.
Prescheduled - UL grants are prescheduled and is available in each TTI during the
testing. Test should be configured using ulBO period 1ms such that a zero UL scheduling
delay for each UL packet transmission.
The target value does not include any UE terminal delay. The UE delay due to the AS
processing and time waiting for UL grants are included.
For FDD, This requirement also implies the RAN RTT requirement defined as the round
trip time between UE and eNB. The RAN RTT shall meet 16 ms for prescheduled (Total
EPC latency is around 1~2 ms).
The RAN delay target is not meeting LSTI's requirement (10ms) [R30].
TDD test results showed pre-scheduled PING latency is between 13 msec (min) and 18
msec (max).
For TDD, the following configurations are used in testing:

ulSchedMPEstage3AccountForBO = false
Estimated TDD results are:
Config 1, SSF 7: min: 12.4ms, max: 18.4ms
Config 2, SSF 7: min 12.4, max: 18.4ms
Critical No
Dashboard
LE1 KPI ID

Validator
Impacted Entities Air Interface, SGW, BH, eNB, PGW
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration For pre-scheduled latency test, continuous PINGs over every TTI shall be applied using at
least a total of 20 pings.
Make sure the UL Grant available on each TTI with sufficient size for the PING.
Test Notes
Test Owner
Test Reference UP_KPI_6b
Test Plan
492
493
494

495 ALU KPI ID UP_KPI_6b
ALU KPI ID UP_KPI_6b
ALU KPI Name Best effort Ping RTT @ 32 Bytes between UE and Application Server at SGi interface
(Unscheduled)
ALU KPI Description Round Trip Time (RTT) for a Ping of size 32 bytes measured on the originating device
connected to UE and an Application Server that is connected to the SGi interface.
ALU Internal Target No Load Average:

25 msec (FDD)(Mean) & 40 msec (FDD)(95%) with SR= 5 msec;
32.5 msec (FDD)(Mean) & 47.5 msec (FDD)(95%) with SR=20 msec;
25.5 msec (TDD-config 1, SSF7);
27ms (TDD-confg 1, SSF7)
ALU Public Target
ALU Measurement Other (specify below) Active test from terminal to the server connected to SGi interface.
Method
ALU KPI Comments This requirement does not include delay due to propagation latency for BH, intra-net, and
IP network. The requirement assumes perfect RF condition for no load case.
Unscheduled - UL grants are scheduled after eNB receives an SR. Test should be
configured using SR period 5ms such that the latency will include all the time taken for SR
transmission and receiving, scheduling delay, and grant transmission and receiving.
The target value does not include any UE terminal delay. The UE delay due to the AS
processing and time waiting for UL grants are included.
The target Value does not include the delay due to the RF loading.
The no load (average) target for FDD is given by
(22.5 msec + 0.5 * SR period in msec)
For single UE scenario in TDD, eNB needs to wait for SR to send UL grant.
For TDD the following configuration is used:
ulSchedMPEstage3AccountForBO = true
Estimated TDD test results are:
Config 1, SSF 7: min 20.4ms; max: 31.4ms
Config 2, SSF 7: min: 24.4ms; max: 31.4ms
Critical Yes
Dashboard

LE1 KPI ID
Validator
Impacted Entities Air Interface, SGW, BH, eNB, PGW
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference UP_KPI_6
Test Consideration For pre-scheduled latency test, continuous PINGs over every TTI shall be applied using at
least a total of 20 pings.
For un-scheduled latency test, the time between two consecutive pings should be set to
greater than or equal to 1 sec using at least 20 pings.
SR period = 5 ms. UL Grant size sufficient for the PING.
Test Notes To meet the "no load" FDD target of 25 msec, the EPC delay is budgeted as 2 msec.
Test Owner
Test Reference UP_KPI_6
Test Plan

496
497
498

499 ALU KPI ID UP_KPI_7a
ALU KPI ID UP_KPI_7a
ALU KPI Name VoIP Mobile-to-Land Mouth-to-Ear Delay
ALU KPI Scope E2E
ALU KPI Description The VoIP mobile to land mouth-to-ear-delay is the elapsed time from voice audio feed to
output of receiver after play-out circuits.
ALU Internal Target No Load: 100 msec (95%-tile), Typical Load: 125 msec (95%-tile), Full Load:
ALU Public Target

Method
parts of the IP network. This requirement does include the latency in MGW and LEC
including the de-jittering buffering latency.
Using 20 VoIP users/5Mhz as LE4.0 typical loading
The targets specified assume AMR Voice Codec 12.2kbps.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
500
501
502

503 ALU KPI ID UP_KPI_7aa
ALU KPI ID UP_KPI_7aa
ALU KPI Name VOIP Mobile-to-Land over Internet Packet Latency
ALU KPI Scope E2E
ALU KPI Description The delay between the VoIP RTP packets captured at the output of the VoIP client
encoder of the originating UE and the corresponding packets captured at the input of a
VoIP PC client decoder.
ALU Internal Target No Load: 60 msec (95%-tile), Typical Load: 60 msec (95%-tile), Full Load:
ALU Public Target

Method
cell)
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
504
505
506

507 ALU KPI ID UP_KPI_7ab
ALU KPI ID UP_KPI_7ab
ALU KPI Name VOIP Mobile-to-Land over PSTN Packet Latency
ALU KPI Scope E2E
ALU KPI Description The delay between the VoIP RTP packets captured at the output of the VoIP client
encoder of the originating UE and the corresponding packets captured at the input of the
Media Gateway transcoder.
ALU Internal Target No Load: 65 msec (Average), Typical Load: 65 msec (95%-tile), Full Load:
ALU Public Target

Method
cell)
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
508
509
510

511 ALU KPI ID UP_KPI_7b
ALU KPI ID UP_KPI_7b
ALU KPI Name VoIP Land-to-Mobile Mouth-to-Ear Delay
ALU KPI Scope E2E
ALU KPI Description The VoIP mobile to land mouth-to-ear-delay is as the elapsed time from voice audio feed
to output of receiver after play-out circuits.
ALU Internal Target No Load: 100 msec (95%-tile), Typical Load: 100 msec (95%-tile), Full Load: 125 msec
(Average),
ALU Public Target

Method
parts of the IP network. This requirement does include the latency in MGW and LEC.
This requirement does not include delay due to propagation latency for BH, intra-net, and
other parts of IP network.
Using 100 VoIP user as LE4.0 full capacity loading
The targets specified assume AMR Voice Codec 12.2kbps.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution

Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
512
513
514

515 ALU KPI ID UP_KPI_7ba
ALU KPI ID UP_KPI_7ba
ALU KPI Name VOIP Land-to-mobile over Internet packet latency
ALU KPI Scope E2E
ALU KPI Description The delay between the VoIP RTP packets captured at the output of a VoIP PC client
encoder and the corresponding packets captured at the input of the VoIP client decoder of
the terminating UE.
ALU Public Target

Method
cell)
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
516
517
518

519 ALU KPI ID UP_KPI_7bb
ALU KPI ID UP_KPI_7bb
ALU KPI Name VOIP Land to-mobile over PSTN packet latency
ALU KPI Scope E2E
ALU KPI Description The delay between the VoIP RTP packets captured at the output of the Media Gateway
transcoder and the corresponding packets captured at the input of the voice decoder of
the terminating UE.
ALU Public Target

Method
ALU KPI Comments The target values assume zero propagation latency for BH including MGW to PGW, Intra-
net latency, and other parts of the IP network.
cell)
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
520
521

522
523 4.2 Control Plane Latency KPI

525
526 Table 4.2.1-1
527
C-Plane Latency KPIs
CP_KPI_10 Mobile-to-Mobile VoIP Call Setup Time
CP_KPI_14 Dedicated Bearer Activation Time
CP_KPI_2 1st Page Response Time
CP_KPI_27 UE Activation Time
CP_KPI_27b Service Request Setup Time
CP_KPI_36a VoIP Call End Time (Mobile to PSTN)
CP_KPI_36b VoIP Call End Time (Mobile to Mobile)
CP_KPI_6 Attach Time
CP_KPI_7a UE-initiated Detach Time
CP_KPI_7b MME-initiated Detach Time
CP_KPI_8 MO VoIP Call Setup Time (Mobile to PSTN)
CP_KPI_9 MT VoIP Call Setup Time (PSTN to Mobile)
528
529 4.2.2 End-to-end Network Requirement

530
531 ALU KPI ID CP_KPI_10
ALU KPI ID CP_KPI_10
ALU KPI Name Mobile-to-Mobile VoIP Call Setup Time
ALU KPI Type Control Plane Latency
ALU KPI Scope E2E

ALU KPI Description The elapsed time between sending of a SIP INVITE message from the originating UE, to
the receipt of the corresponding SIP 200 OK message at the originating UE, assuming the
terminating UE is answering the call immediately.
ALU Internal Target No Load: 820 msec (Average), Typical Load: Full Load: 2.5 sec (Median),
ALU Public Target
ALU Measurement Other (specify below) This latency should include all the SIP messages required to set up
a VoIP mobile-to-mobile calls
Method
ALU KPI Comments In general, for the no loaded case it assumes RAN and EPC are collocated for no loaded
case. For loading case, it assumes the propagation latency between eNB to SGW limited
to < 10 ms, and the propagation latency between eNB to MME limited to < 10 ms. The
loaded case number is allowed to be relaxed to cover the additional propagation latency.
The target of this KPI is adjusted in LE4.0 to take into account the LE2.1 test results (with
10% margin).
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, PCRF, Air Interface, SGW, BH, eNB, PGW
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference

Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
532
533
534

ALU KPI Name Dedicated Bearer Activation Time
ALU KPI Description The elapsed time from the sending of the initial message from the PCRF (either an IP-
CAN Session modification message or a PCC decision provision (QoS policy) message)
to the P-GW until the P-GW's corresponding response message to the PCRF indicating a
successful bearer activation.
ALU Internal Target No Load: 100 msec (Average) 135 msec (95%), Typical Load: Full Load: 175 msec
(Average), 300 msec (95%)
ALU Public Target
ALU Measurement Other (specify below) Using testing equipment to measure the time difference between:
Start: sending of the initial message from the PCRF (either an IP-CAN Session
Method modification message or a PCC decision provision (QoS policy) message) to the P-GW
End: Sending at P-GW the corresponding response message to the PCRF indicating a
successful bearer activation
ALU KPI Comments For the no loaded case, it assumes RAN and EPC are collocated for no loaded case
The no load target doesn't include the overhead at PGW due to batching and scheduling.
According to LE2.1 test result the overhead is ~110ms (for 4 interface messages).
The targets specified above do not include PCRF processing time for the RAA message
(last step in the call flow)
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, PCRF, Air Interface, SGW, BH, eNB, PGW
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference Refer to 5.1.1.2 of this document for NE latency allocations.
Test Consideration
Test Notes PGW Initiated Dedicated Bearer allocation callflow is at [R17] (section 4.3).
Test Owner
Test Reference
Test Plan
536
537
538

ALU KPI ID CP_KPI_2
ALU KPI Name 1st Page Response Time
ALU KPI Description The time from the first page message sent by the MME, until a successful UE response
(the corresponding NAS message), is received in response to the first Page attempt in the
series of Pages.
ALU Internal Target No Load: 85 msec + 1/2 (paging DRX) (Average), 125 msec + paging DRX (95%),
Full Load: 160 msec + 1/2 (paging DRX)* (Median), 250 msec + Paging DRX (95%)
ALU Public Target
ALU Measurement PCMD TimeOfServiceRequestRcvd - ProcedureStartTime

(with Attempt_1_Success_Fail = Success for Paging Procedure) Measure the time
Method difference between:
Start: when MME sends for the Paging message to the eNB
End: when MME receives the Service Request message from the UE (not including the
processing time of the Service Request)
ALU KPI Comments For the no loaded case, it assumes RAN and EPC are co-located.
For full load test, the target is set for using Paging DRX cycle 320ms.
The targets specified above do not include MME processing time for INITIAL UE
MESSAGE (Service Request) which is the last step of this KPI.
Critical Yes
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, Air Interface, SGW, eNB, BH
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
Test Consideration Only successful Paging procedures shall be included in the calculation
Test Notes Refer to [R11] for PCMD details.

ProcedureStartTime for Paging procedure is when MME receives the Downlink Data
Notification message from SGW which adds additional 6 ms to the latency specified in this
requirement.
Test Owner
Test Reference
Test Plan
540
541
542

ALU KPI LE5.0

Release
ALU KPI UE Activation Time (Idle to Active)

Name
ALU KPI RAN, E2E

Scope
ALU KPI The time delay for a UE in the RRC_Idle state to transition to the 1st DB setup to eNB. This is the time between first
RACH preamble and the receipt at the eNB of an RRC Connection Reconfiguration Complete message (DB1 setup)
Description from the UE
ALU Internal No Load: 92 msec*(FDD)(Average), 120 msec (FDD)(95%); 90 msec (TDD-8 ant); 85ms (TDD-2 ant) (Average),
Target Full Load: 195 msec (FDD) (Average), 300 msec (FDD)(95%)
ALU Public
Target
ALU Other (specify below) Using UE logs to measure the time difference between:
Start: sending of the first RACH at UE
Measurement End: sending of the RRC Connection Reconfiguration Complete at UE
Method The official end point for this KPI is when eNB receives the RRC Connection Reconfiguration Complete from the UE.
However only the sending of the message will be captured in the UE log.
ALU KPI For no load case, the target values assume RAN and EPC are collocated and minimum scheduling latency for RRC
messages. That is a quick DL scheduling and 1ms uLBO grant period for immediate UL scheduling for RRC message
Comments after RACH Msg 4. These values apply only for the case that UE has previously been successfully attached to
network.
Critical Yes
Dashboard
LE1 KPI ID
Validator
Impacted UE, MME, Air Interface, eNB

Entities
Application

Duplex
Method
Solution
Level
Customer
Viewable
SE
Conditions
SE Owner
SE Review Approved
Status
Test This KPI applies to simplified UE Activation Time scenario. The applicable call flow is available at:
https://wcdma-ll.app.alcatel-
Consideration lucent.com/livelink/livelink.exe/Simplified_Idle_to_Active_flow_0.4.jpg?func=doc.fetch&nodeId=58780533&viewType=
Test Notes
Test Owner
Test
Reference
Test Feature LS36001-03

ID
Test Review Approved

Status
Test Plan
544
545
546

547 ALU KPI ID CP_KPI_27b
ALU KPI ID CP_KPI_27b
ALU KPI Name Service Request Setup Time
ALU KPI Description The Service Request time is the time when the UE sends Service Request to the MME
and the time when Initial UE Context Setup Complete is received at the MME.
ALU Internal Target No Load: 55 msec (Average), 75 msec (95%)

Full Load: 65 msec (Average), 100 msec (95%)
ALU Public Target
ALU Measurement Other (specify below) Using active test/UE logs to measure the time difference between:
Start: Sending of the Service Request Message at UE to the MME
Method End: Sending of Service Request Complete message at the UE to the MME
Service Request NAS IE is included in the RRC Connection Setup Complete message.
ALU KPI Comments For the no loaded case, it assumes RAN and EPC are collocated for no loaded case.
The Service Request Setup Time target numbers do not include the latency introduced
due to authentication procedure (HSS authentication and UE authentication).
Assumption: Based on test result using M13 UE, UE authentication time is ~1.5sec.
From UE perspective the SR procedure is considered as successful after RRC
Connection Reconfiguration Complete message is sent,
The above targets do not include MME processing time for the Initial Context Setup
Response message.
Critical Yes
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, BH, Air Interface, eNB
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
Test Consideration
Test Notes The measurement method specified above is one of the mechanisms to measure the
Service Request Setup Time. Using UE log limit the measuring point to be at the UE for
start and end. The latency measured using this method is slightly lower than the definition
which uses Initial Context Setup Complete message as the end marker.
Service Request callflow is at [R17] (section 5.1.1.4).
Test Owner
Test Reference
Test Plan
548
549
550

551 ALU KPI ID CP_KPI_36a
ALU KPI ID CP_KPI_36a
ALU KPI Name VoIP Call End Time (Mobile to PSTN)
ALU KPI Scope E2E
ALU KPI Description This KPI quantifies the amount of time taken to successfully release a Mobile-to-PSTN
VoIP call.
VoIP call release time starts when the originating UE sends BYE message and ends when
the UE receives the 200 OK message in response to the BYE.
ALU Internal Target No Load: 6 sec (Max), Typical Load: 6 sec (Max), Full Load: 6 sec (Max),
ALU Public Target
ALU Measurement Other (specify below) Use active test to verify the time to successfully release a VoIP call
between Mobile and PSTN.
Method
ALU KPI Comments Target number is from AT&T contract Attachment F2 for INT08.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, IMS, Air Interface, SGW, PCRF, eNB, PGW, BH
Application
Duplex Method
Solution
Level
Customer Viewable

SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
552
553
554

ALU KPI Name VoIP Call End Time (Mobile to Mobile)
ALU KPI Scope E2E
ALU KPI Description This KPI quantifies the amount of time taken to successfully release a Mobile-to-Mobile
VoIP call.
VoIP call release time starts when the originating UE sends BYE message and ends when
the UE receives the 200 OK message in response to the BYE.
ALU Internal Target No Load: 8 sec (Max), Typical Load: 8 sec (Max), Full Load: 8 sec (Max),
ALU Public Target
ALU Measurement Other (specify below) Use active test to verify the time to successfully release a Mobile-to-
Mobile VoIP call.
Method
ALU KPI Comments This KPI is added per AT&T contract.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable

SE Conditions
SE Owner
SE Reference Target number is from AT&T contract Attachment F2 for INT09.
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
556
557
558

ALU KPI ID CP_KPI_6
ALU KPI Name Initial Attach Time
ALU KPI Description This KPI quantifies the amount of time taken by the network to successfully perform an
Initial ATTACH
The attach time is the time between the sending Attach Request NAS message from the
UE (inside the RRC Connection Setup Complete message) and the receipt at the MME of
the Attach Complete message from the UE.
ALU Internal Target No Load: 290 msec (Average), 400 msec (95%)
Full Load: 600 msec (Average), 1 sec (95%)
ALU Public Target
ALU Measurement Other (specify below) Using active test/UE logs to measure the time difference between:
Start: Sending of the Attach Request Message at UE to the MME
Method End: Receiving the Attach Complete message at the MME
Attach Request NAS IE is included in the RRC Connection Setup Complete message.
ALU KPI Comments The Attach Setup Time target numbers do not include the latency introduced due to:
Authentication procedure (HSS authentication and UE authentication) and transport
delays.
UE authentication time (~1.5sec for M13 UE, <=200ms for Solution3 UE, and >21ms for
G13 UE) shall be excluded to compare the KPI targets.
Initial Attach Time doesn't include Modify Bearer.
The targets specified above do not include MME processing time for UPLINK NAS
TRANSPORT (Attach Complete) which is the last step of this KPI.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, HSS, Air Interface, SGW, PCRF, eNB, PGW, BH
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions Assumptions:
Same MME
IMSI Attach
Authentication not included
No Cipher options
No Previous Bearers
No handover
SE Owner
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
560
561
562

ALU KPI Name UE-initiated Detach Time
ALU KPI Scope E2E
ALU KPI Description This KPI quantifies the amount of time taken to successfully perform an Detach for a
single PDN by UE.
UE initiated Detach: The time between the sending by the UE of the initiated Detach
Request until the receipt of the corresponding Detach Accept message (originating from
the MME) by the UE.
ALU Internal Target No load: <=170ms (average)

Full load: <=350ms (average)
ALU Public Target
ALU Measurement
Method
ALU KPI Comments Note: While these initial values of Detach Time are set equal to those of Attach Time,
further analysis may result in their reduction.
Critical No
Dashboard
LE1 KPI ID
Validator
Impacted Entities
Application
Duplex Method FDD
Solution E2E
Level Cluster

SE Conditions
SE Owner Jin Wang
SE Reference
SE Review Status
Test Consideration
Test Notes
Test Owner
Test Reference
Test Review Status
Test Plan
564
565
566

ALU KPI Name MME-initiated Detach Time
ALU KPI Scope E2E
ALU KPI Description This KPI quantifies the amount of time taken to successfully perform an Detach for a
single PDN by MME.
MME initiated Detach: The time between the sending of a Detach Request from the
MME to the UE (via the eNB) until the later of the following two events: (1) the receipt of
a Detach Accept message from the UE (via the eNB) at the MME, or, (2) the receipt of
the Delete Session Response message by the MME from the SGW.
ALU Internal Target No load: <=150ms (average)

Full load: <=300ms (average)
ALU Public Target
ALU Measurement
Method
ALU KPI Comments Note: While these initial values of Detach Time are set equal to those of Attach Time,
further analysis may result in their reduction.
When MAC DRX is supported in LA7, the KPI target needs re-visit due to extra delay if
the eNB-to-UE message coincides with DRX "Off" interval and thus the delivery has to
wait for the next "On" interval.
Critical No
Dashboard
LE1 KPI ID
Validator
Impacted Entities
Application
Duplex Method FDD
Solution E2E

Level Cluster
SE Conditions
SE Owner Jin Wang
SE Reference
SE Review Status
Test Consideration
Test Notes
Test Owner
Test Reference
Test Review Status
Test Plan
568
569

ALU KPI ID CP_KPI_8
ALU KPI Name MO VoIP Call Setup Time (Mobile to PSTN)
ALU KPI Scope E2E
ALU KPI Description The elapsed time between sending of a SIP INVITE message from the originating UE, to
the receipt of the corresponding SIP 200 OK message at the originating UE, assuming the
terminating landline party is answering the call immediately.
ALU Public Target
ALU Measurement Other (specify below) This latency includes all the SIP messages required to setup MO
VoIP call
Method
ALU KPI Comments This requirement is subject to further refinement. For the no loaded case, it assumes RAN
and EPC are co-located and UE in ideal RF condition. For load case, it assumes the
propagation latency between eNB to SWG limited to < 10 ms, and the propagation latency
between eNB to MME limited to < 10 ms. The load case number is allowed to be relaxed
to cover the additional propagation latency.
The target for this KPI is specified to be the same as the M-M VoIP Call Setup time
(CP_KPI_10). It is expected the M-PSTN VoIP call setup time would be lower than the M-
M VoIP call setup time.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution

Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
571
572
573

ALU KPI ID CP_KPI_9
ALU KPI Name MT VoIP Call Setup Time (PSTN to Mobile)
ALU KPI Scope E2E
ALU KPI Description This KPI quantifies the amount of time taken to successfully establish a VoIP call
terminated by a mobile and originating from a landline.
End-to-end Definition: The elapsed time between the receipt of a SIP INVITE message
from the originating landline at the P-GW, to the forwarding from the P-GW of the
corresponding SIP OK message from the terminating mobile.
ALU Public Target
ALU Measurement Other (specify below) This latency includes all the SIP messages required to setup MT
VoIP call
Method
ALU KPI Comments For the no loaded case, it assumes RAN and EPC are co-located. For loading case, it
assumes the propagation latency between eNB to SWG limited to < 10 ms, and the
propagation latency between eNB to MME limited to < 10 ms. The loaded case number is
allowed to be relaxed to cover the additional propagation latency.
LTE Network Definition: The elapsed time between P-GW request for a page to the mobile
and the completion at the terminating mobile of the corresponding radio bearer
establishment procedure (as part of the establishment of a suitable QoS enabled
dedicated bearer).
The target for this KPI is specified to be the same as the M-M VoIP Call Setup time
(CP_KPI_10). It is expected the PSTN-M VoIP call setup time would be lower than the M-
M VoIP call setup time.
Critical
Dashboard
LE1 KPI ID
Validator
Application

Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
575

576
577 4.3 Intra-LTE Mobility KPI

578 This section covers the intra-LTE handover related KPIs. Inter-RAT related KPIs are covered in a later
579 section.
580

582 Table 4.3.1-1
Mobility KPIs
CP_KPI_18 Intra-SGW Intra-eNB VoIP HO Interruption time
CP_KPI_19 Intra-SGW Intra-eNB Video Telephony HO Interruption Time
CP_KPI_20 Intra-SGW Intra-eNB Best-effort HO Interruption time
CP_KPI_20d Intra-SGW Intra-eNB Best-effort HO Procedure Latency
CP_KPI_21 Inter-eNB VoIP X2 HO Interruption time
CP_KPI_21b Inter-eNB VoIP S1 HO Interruption time
CP_KPI_21d Inter-eNB Inter-frequency VoIP X2 HO Interruption time
CP_KPI_21e Inter-eNB Inter-frequency VoIP S1 HO Interruption time
CP_KPI_22 Inter-eNB Video Telephony X2 HO Interruption Time
CP_KPI_22b Inter-eNB Video Telephony S1 HO Interruption Time
CP_KPI_23 Inter-eNB Best-effort X2 HO Interruption time
CP_KPI_23b Inter-eNB Best-effort S1 HO Interruption time
CP_KPI_23d Inter-eNB Inter-frequency Best-effort X2 HO Interruption time
CP_KPI_23e Inter-eNB Inter-frequency Best-effort S1 HO Interruption time
CP_KPI_23f Inter-eNB X2 Handover Procedure Latency (without SGW Relocation)
NP_KPI_11 Intra-SGW Intra-eNB HO Success Rate
NP_KPI_12 Inter-eNB X2 HO Success Rate
NP_KPI_12b Inter-eNB S1 HO Success Rate
NP_KPI_12c Inter-eNB Inter-frequency X2 HO Success Rate
583

584 Here are the assumptions for the KPIs for HO Interruption delay:
RACH access opportunity period 10
Number of UE per cell for 4.0 167
Number of VoIP UE/bearers per cell for 4.0 20
VoIP VAF 0.8 / 1.0
VoIP Payload packet inter arrival time 20
VoIP SID packet inter arrival time 160
UL grant (ACQI) size for 4.0 (Bytes) 190
585
586 These KPIs for HO interruption delay are associated with three traffic types:
587 1. Best-effort
588 2. VOIP
589 3. Video-Telephony (VT)
590 Because VT packet inter-arrival time varies with video encoder types and RTP packet packing mechanism,
591 as well as the MAC scheduling implementation, the average VT packet inter-arrival time is variable. To avoid
592 this complexity, the HO gap for VT traffic has been defined in terms of the gap of the audio packets
593 associated with the video traffic. As a result, the HO interruption delay for VT has become the same as the
594 HO interruption time for VOIP. Therefore, all the KPIs listed in the above table have only two different sets of
595 values for the interruption times, as listed in the following table:
596
HO Interruption NO LOAD TARGET:
Delay for VOIP
DL: 62 ms (ave.), 90 ms (95%)
and VT
UL: 60 ms (ave.), 90 ms (95%)
(Associated FULL LOAD TARGET:

KPI’s: DL: 72 ms (ave.), 120 ms (95%)
CP_KPI_18,
CP_KPI_19, UL: 70 ms (ave.), 120 ms (95%)
CP_KPI_21,
CP_KPI_21b,
CP_KPI_21d, For UE with higher than expected processing delay of 25 msec:
CP_KPI_21e, NO LOAD TARGET (average):
CP_KPI_22,
CP_KPI_22b) DL: (37 + UE delay) ms
UL: (35 + UE delay) ms
FULL LOAD TARGET (average):

DL: (47 + UE delay) ms

HO Interruption NO LOAD TARGET:
Delay for BE
DL: 52 ms (ave.), 70 ms (95%): when FID 109433 disabled
DL: 64 ms (ave.), 82 ms (95%): when FID 109433 enabled for RLC AM mode
(Associated
UL: 50 ms (ave.), 70 ms (95%)
KPI’s:
CP_KPI_20, FULL LOAD TARGET:
CP_KPI_23, DL: 95 ms (ave.), 135 ms (95%) : when FID 109433 disabled
CP_KPI_23b,
CP_KPI_23d, DL: 134 ms (ave.), 175 ms (95%): when FID 109433 enabled for RLC AM mode
CP_KPI_23e) UL: 93 ms (ave.), 135 ms (95%)
FID 109433: Downlink packet duplication avoidance
For UE with higher than expected processing delay of 25 msec:

NO LOAD TARGET (average):
DL: (27 + UE delay) ms : when FID 109433 disabled
DL: (39 + UE delay) ms : when FID 109433 enabled

597
598 Note:
599 • The values specified in “No Load Target” average are mean values.
600 • The values specified in “Full Load Target” average are median values.
601

602
603 4.3.2 End-to-end Network Requirement for Handover Interruption Time and
604 Procedure Latency KPIs
605
ALU KPI Name Intra-SGW Intra-eNB VoIP HO Interruption time
ALU KPI Type Mobility Performance
ALU KPI Description HO interruption time for DL is the time interval between the instant the UE receives the
last HARQ of the last PHY VOIP packet from the source eNB and the instant the UE
receives the 1st HARQ of the 1st PHY VOIP packet from the target eNB.
HO interruption time for UL is the time interval between the instant the UE transmits the
last HARQ of the last PHY VOIP packet to the source eNB and the instant the UE
transmits the 1st HARQ of the 1st PHY VOIP packet to the target eNB.
ALU Internal Target NO LOAD TARGET:

DL: 62 ms (ave.), 90 ms (95%)
UL: 60 ms (ave.), 90 ms (95%)
FULL LOAD TARGET:
DL: 72 ms (ave.), 120 ms (95%)
UL: 70 ms (ave.), 120 ms (95%)
ALU Public Target
ALU Measurement Other (specify below) Using UE logs to measure the duration between:
Start: the last HARQ Acknowledged VoIP packet received from the source eNB cell
Method End: the first HARQ Acknowledged VoIP packet received from the target eNB cell
ALU KPI Comments For UE with higher than expected processing delay of 25 msec:
This required number should be averaged over significant number of samples, e.g. 100 in
the field test excluding the UE persistently in the bad RF conditions.
These values assume an average access DRX waiting time 5 ms for regular size cell.
Critical

Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, Air Interface, eNB, IMS
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference Refer to 5.1.2.1 for NE allocations.
Test Consideration DS, VAF=100%

RSRP > -90dbm
DL Target SNR (per antenna) > -5db
Speed: up to 60 km/hr
RF loading is using target OCNS loading on PDCCH and PDSCH: no load=0%, typical
load =50%, full load=100%
Consecutive Cell IDs will be assigned.
Test Notes This required number should be averaged over significant number of samples, e.g. 100 in
Test Owner
Test Reference

Test Plan
607
608
609

ALU KPI Name Intra-SGW Intra-eNB Video Telephony HO Interruption Time
last HARQ of the last PHY audio packet from the source eNB and the instant the UE
receives the 1st HARQ of the 1st PHY audio packet from the target eNB.
last HARQ of the last PHY audio packet to the source eNB and the instant the UE
transmits the 1st HARQ of the 1st PHY audio packet to the target eNB.

DL: 62 ms (ave.), 90 ms (95%)
UL: 60 ms (ave.), 90 ms (95%)
FULL LOAD TARGET:
DL: 72 ms (ave.), 120 ms (95%)
UL: 70 ms (ave.), 120 ms (95%)
ALU Public Target
Start: the last Acknowledged Video packet received from the source eNB cell
Method End: the first Acknowledged Video packet received from the target eNB cell
Critical
Dashboard
LE1 KPI ID
Validator

Impacted Entities UE, eNB, IMS, Air Interface, BH
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions Loading for HO KPIs refers to RF loading using OCNS
SE Owner

RSRP > -90dbm
Test Notes This required number should be averaged over large number of samples in the field test
excluding the UE persistently in the bad RF conditions.
Test Owner
Test Reference
Test Plan
611
612
613

ALU KPI Name Intra-SGW Intra-eNB Best-Effort HO Interruption time
last HARQ of the last PHY BE packet from the source eNB and the instant the UE
receives the 1st HARQ of the 1st PHY BE packet from the target eNB.
last HARQ of the last PHY BE packet to the source eNB and the instant the UE transmits
the 1st HARQ of the 1st PHY BE packet to the target eNB.

UL: 50 ms (ave.), 70 ms (95%)
FULL LOAD TARGET:
DL: 95 ms (ave.), 135 ms (95%) : when FID 109433 disabled
UL: 93 ms (ave.), 135 ms (95%)
ALU Public Target
Start: the last (traffic) grant received from the source eNB cell
Method End: the first (traffic) grant received from the target eNB cell
Critical Yes
Dashboard
LE1 KPI ID

Validator
Impacted Entities UE, MME, BH, Air Interface, SGW, eNB, PGW
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
Test Consideration RSRP > -90dbm

Test Notes Full buffer transfer should be used to measure BE HO interruption time
Test Owner
Test Reference
Test Plan
615
616
617

618 ALU KPI ID CP_KPI_20d
ALU KPI ID CP_KPI_20d
ALU KPI Name Intra-eNB Handover Procedure Latency
ALU KPI Description The elapsed time between receiving at eNB the MeasurementReport, message from the
UE, which triggered the intra-eNB HO, and receiving at eNB the RRC Connection
Reconfiguration Complete message to the UE.
ALU Internal Target No Load: 50 msec (TDD) (Average), Typical Load: Full Load:
ALU Public Target
ALU Measurement Other (specify below) Measure the duration between:

Start: Receiving at the eNB of the MeasurementReport message which triggers the HO
Method End: Receiving at the eNB of the RRC Connection Reconfiguration Complete message
If using UE logs the start time would be sending the MeasurementReport message at the
UE and the end time would be sending the RRC Connection Reconfiguration Complete
message at the UE.
ALU KPI Comments Only TDD target is specified for this KPI in LE4.0. FDD target will be added in future
release.
TDD test results showed intra-eNB HO procedure latency is between 39 msec (min) and
63 msec (max).
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, Air Interface, eNB
Application
Duplex Method
Solution

Level
Customer Viewable
SE Conditions
SE Owner
SE Reference

Test Notes
Test Owner
Test Reference
Test Plan
619
620
621

ALU KPI Name Inter-eNB VoIP X2 HO Interruption time

DL: 62 ms (ave.), 90 ms (95%)
UL: 60 ms (ave.), 90 ms (95%)
FULL LOAD TARGET:
DL: 72 ms (ave.), 120 ms (95%)
UL: 70 ms (ave.), 120 ms (95%)
ALU Public Target
The above targets are for no SGW relocation scenario.
Critical
Dashboard
LE1 KPI ID
Validator

Impacted Entities UE, MME, IMS, Air Interface, SGW, eNB, PGW
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner

RSRP > -90dbm
Test Owner
Test Reference
Test Plan
623
624
625

ALU KPI Name Inter-eNB VoIP S1 HO Interruption time

DL: 62 ms (ave.), 90 ms (95%)
UL: 60 ms (ave.), 90 ms (95%)
FULL LOAD TARGET:
DL: 72 ms (ave.), 120 ms (95%)
UL: 70 ms (ave.), 120 ms (95%)
ALU Public Target
This KPI currently covers targets for S1 HO without MME and SGW relocation scenario.
Critical
Dashboard
LE1 KPI ID
Validator

Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner

RSRP > -90dbm
Test Owner
Test Reference
Test Plan
627
628
629

ALU KPI Name Inter-eNB Inter-frequency VoIP X2 HO Interruption time
There is no SGW relocation in this case.

DL: 62 ms (ave.), 90 ms (95%)
UL: 60 ms (ave.), 90 ms (95%)
FULL LOAD TARGET:
DL: 72 ms (ave.), 120 ms (95%)
UL: 70 ms (ave.), 120 ms (95%)
ALU Public Target
The targets specified above are for no SGW relocation scenario.
This KPI is MOB06 in AT&T Attachment F2 and AT&T target is <120 msec. This KPI
target is defined as average.
Critical
Dashboard
LE1 KPI ID

Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference

RSRP > -90dbm
Test Owner
Test Reference
Test Plan
631
632
633
634 ALU KPI ID CP_KPI_21e
ALU KPI ID CP_KPI_21e
ALU KPI Name Inter-eNB Inter-frequency VoIP S1 HO Interruption time

DL: 62 ms (ave.), 90 ms (95%)
UL: 60 ms (ave.), 90 ms (95%)
FULL LOAD TARGET:
DL: 72 ms (ave.), 120 ms (95%)
UL: 70 ms (ave.), 120 ms (95%)
ALU Public Target
This KPI is MOB06 in AT&T contract Attachment F2 and AT&T's target is <120 msec.
Critical
Dashboard
LE1 KPI ID

Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference

RSRP > -90dbm
Test Owner
Test Reference
Test Plan
635
636
637
ALU KPI Name Inter-eNB Video Telephony X2 HO Interruption Time

DL: 62 ms (ave.), 90 ms (95%)
UL: 60 ms (ave.), 90 ms (95%)
FULL LOAD TARGET:
DL: 72 ms (ave.), 120 ms (95%)
UL: 70 ms (ave.), 120 ms (95%)
ALU Public Target
The targets specified are for no SGW relocation scenario.
Critical
Dashboard
LE1 KPI ID

Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner

RSRP > -90dbm
Test Owner
Test Reference
Test Plan
639
640
641
ALU KPI Name Inter-eNB Video Telephony S1 HO Interruption Time

DL: 62 ms (ave.), 90 ms (95%)
UL: 60 ms (ave.), 90 ms (95%)
FULL LOAD TARGET:
DL: 72 ms (ave.), 120 ms (95%)
UL: 70 ms (ave.), 120 ms (95%)
ALU Public Target
Critical
Dashboard
LE1 KPI ID
Validator

Application
Duplex Method
Solution
Level
Customer Viewable
SE Owner

RSRP > -90dbm
Test Owner
Test Reference
Test Plan
643
644
645

ALU KPI Name Inter-eNB Best-effort X2 HO Interruption time

UL: 50 ms (ave.), 70 ms (95%)
FULL LOAD TARGET:
UL: 93 ms (ave.), 135 ms (95%)
ALU Public Target
RLC Full buffer is assumed which has no waiting time for packet inter-arrival
Critical Yes
Dashboard

LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner

Test Notes
Test Owner
Test Reference
Test Plan
647
648
649 10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 98
ALU KPI Name Inter-eNB Best-effort S1 HO Interruption time

UL: 50 ms (ave.), 70 ms (95%)
FULL LOAD TARGET:
UL: 93 ms (ave.), 135 ms (95%)
ALU Public Target
RLC Full buffer is assumed which has no waiting time for packet inter-arrival.
Critical Yes
Dashboard

LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner

Test Notes
Test Owner
Test Reference
Test Plan
651
652
ALU KPI Name Inter-eNB Inter-frequency Best-effort X2 HO Interruption time

UL: 50 ms (ave.), 70 ms (95%)
FULL LOAD TARGET:
UL: 93 ms (ave.), 135 ms (95%)
ALU Public Target
Method End: the first (traffic) grant received from the target eNB cell Using UE logs to measure the
duration between:
End: the first (traffic) grant received from the target eNB cell
RLC Full buffer is assumed which has no waiting time for packet inter-arrival
The targets specified above are for no SGW relocation scenario.
This KPI is MOB10 in AT&T contract Attachment F2 and AT&T target is <2 sec.
Critical

Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner

Test Notes
Test Owner
Test Reference

Test Plan
655
656
657

658 ALU KPI ID CP_KPI_23e
ALU KPI ID CP_KPI_23e
ALU KPI Name Inter-eNB Inter-frequency Best-effort S1 HO Interruption time

UL: 50 ms (ave.), 70 ms (95%)
FULL LOAD TARGET:
UL: 93 ms (ave.), 135 ms (95%)
ALU Public Target
RLC Full buffer is assumed which has no waiting time for packet inter-arrival.
This KPI currently covers S1 HO without MME and SGW relocation scenario.
This KPI is MOB10 in AT&T contract Attachment F2 and AT&T target is <2 sec.
Critical
Dashboard

LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner

Test Notes
Test Owner
Test Reference
Test Plan
659
660
662 ALU KPI ID CP_KPI_23f
ALU KPI ID CP_KPI_23f
ALU KPI Name Inter-eNB X2 Handover Procedure Latency (without SGW Relocation)
ALU KPI Description The elapsed time between receiving at the source eNB the MeasurementReport message
from the UE and receiving at the target eNB the RRC Connection Reconfiguration
Complete message to the UE.
ALU Internal Target No Load: 55 msec (TDD) (Average), Typical Load: Full Load:
ALU Public Target
ALU Measurement Other (specify below) Measure the duration between:

Start: Receiving at the source eNB of the MeasurementReport message which triggers the
Method HO
End: Receiving at the target eNB of the RRC Connection Reconfiguration Complete
message
If using UE logs the start time would be sending the MeasurementReport message at the
UE and the end time would be sending the RRC Connection Reconfiguration Complete
message at the UE.
ALU KPI Comments Only TDD target is specified for this KPI in LE4.0. FDD target will be added in future
release.
Test results showed latency is between 45 msec (min) and 70 msec (max).
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, Air Interface, eNB
Application
Duplex Method

Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference

Test Notes This KPI is specified for TDD only. FDD targets will be added in future release.
Test Owner
Test Reference X2 HO callflow is at [R17] (section 4.9).
Test Plan
663
664 4.3.3 End-to-end Network Requirement for Handover Success Rate KPIs
665
666 ALU KPI ID NP_KPI_11
ALU KPI ID NP_KPI_11

ALU KPI Name Intra-eNB HO Success Rate
ALU KPI Description The intra-eNB handover success rate is the percentage of the successfully performed
intra-eNB handovers.
ALU Internal Target No Load: >99.5% (Average), Typical Load: >98.5% (Average), Full Load: >98.5%
(Average),
ALU Public Target
ALU Measurement Counter:

100 * HO.IntraEnbOutSucc.Sum / VS.OutgoingIntraENodeBHOAttempt
Method
Start: eNB receives RrcMeasurementReport message from the UE and mobility decision
is made to perform HO to another cell in the same eNB
End: target cells receives RrcReconfigurationComplete message from the UE
ALU KPI Comments This required number should be averaged over large number of samples in the field test
This KPI covers both contention-based handover and contention-free handover scenarios.
The typical load and full load targets are based on AT&T's contract (MOB01 in Attachment
F2).
Critical Yes
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions

SE Owner
SE Reference

Test Notes This required number should be averaged over significant number of samples (e.g. 100) in
Test Owner
Test Reference
Test Plan
667
668
669

ALU KPI Name Inter-eNB Intra-Frequency X2 HO Success Rate
ALU KPI Description The inter-eNB handover success rate is the percentage of the successfully performed
inter-eNB handovers within a specified population.
HO attempt is when the source eNB sends Handover Request message to the target eNB.
HO success is when the source eNB receives X2AP UE CONTEXT RELEASE message
from the target eNB.
(Average),
ALU Public Target

100*( VS.OutgoingInterENodeBX2HOSuccess
Method -VS.OutgoingInterENodeBX2HOSuccessScreened.InterFreqSameFrameStructure)
/(VS.OutgoingInterENodeBX2HOAttempt
-VS.OutgoingInterENodeBX2HOAttemptScreened.InterFreqSameFrameStructure)
The target for typical and full loading average is updated to meet AT&T's requirement
(MOB01 in Attachment F2).
Critical Yes
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, Air Interface, SGW, eNB, PGW
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference

Test Notes This required number should be averaged over significant number of samples, e.g. 100, in
Test Owner
Test Reference
Test Plan
671
672
673

674 ALU KPI ID NP_KPI_12b
ALU KPI ID NP_KPI_12b
ALU KPI Name Inter-eNB Intra-Frequency S1 HO Success Rate
inter-eNB handovers within a specified population.
HO attempt is when the source eNB sends S1 HANDOVER REQUIRED to the MME. HO
success is when the source eNB receives S1 UE CONTEXT RELEASE COMMAND.
ALU Internal Target No Load: >99.5% (Average), Typical Load: >98.5 (Average), Full Load: TBD (Average),
ALU Public Target

100*( VS.OutgoingInterENodeBS1HOSuccess
Method -VS.OutgoingInterENodeBS1HOSuccessScreened.InterFreqSameFrameStructure)
/(VS.OutgoingInterENodeBS1HOAttempt
-VS.OutgoingInterENodeBS1HOAttemptScreened.InterFreqSameFrameStructure)
The target for typical and full loading average were set to 98.5% in AT&T's requirement
(MOB01 in Attachment F2). However, whether this target is achievable is an open issue
for FFS.
Critical Yes
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution

Level
Customer Viewable
SE Owner
SE Reference

Test Owner
Test Reference
Test Plan
675
676
677

678 ALU KPI ID NP_KPI_12c
ALU KPI ID NP_KPI_12c
ALU KPI Name Inter-eNB Inter-frequency X2 HO Success Rate
inter-eNB inter-frequency X2 handovers within a specified population.
HO attempt is when the source eNB sends Handover Request message to the target eNB.
HO success is when the source eNB receives X2AP UE CONTEXT RELEASE message
from the target eNB.
(Average),
ALU Public Target
ALU Measurement Counter 100 *

VS.OutgoingInterENodeBX2HOSuccessScreened.InterFreqSameFrameStructure
Method / VS.OutgoingInterENodeBX2HOAttemptScreened.InterFreqSameFrameStructure
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME , Air Interface, SGW, eNB, PGW
Application
Duplex Method
Solution

Level
Customer Viewable
SE Owner
SE Reference

Test Owner
Test Reference
Test Plan
679
680
681

682 ALU KPI ID NP_KPI_12d
ALU KPI ID NP_KPI_12d
ALU KPI Name Inter-eNB Inter-frequency S1 HO Success Rate
inter-eNB inter-frequency S1 handovers within a specified population.
HO attempt is when the source eNB sends S1 HANDOVER REQUIRED to the MME. HO
success is when the source eNB receives S1 UE CONTEXT RELEASE COMMAND from
the MME.
ALU Internal Target No Load: >99.5% (Average), Typical Load: >98.5% (Average), Full Load: TBD (Average),
ALU Public Target
ALU Measurement Counter 100 *

VS.OutgoingInterENodeBS1HOSuccessScreened.InterFreqSameFrameStructure
Method / VS.OutgoingInterENodeBS1HOAttemptScreened.InterFreqSameFrameStructure
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME , Air Interface, SGW, eNB, PGW
Application
Duplex Method
Solution
Level
Customer Viewable
SE Owner
SE Reference

Test Owner
Test Reference
Test Plan
683
684

685
686 4.4 Network Performance and Quality of Experience KPI

688 Table 4.4.1-1
Network Performance KPIs

st
CP_KPI_3 1 Page Success Rate
CP_KPI_4 Paging Success Rate
NP_KPI_1 Bearer Establishment Success Rate
NP_KPI_10 RRC Connection Setup Success Rate
NP_KPI_10a Bearer Establishment Success Rate for emergency VoIP call
NP_KPI_10b Service Request Setup Success Rate for emergency call
NP_KPI_1a Attach Success Rate
NP_KPI_1b Service Request Setup Success Rate
Bearer Establishment Success Rate excluding repeated occurrences of RRC

NP_KPI_1x
Connection Request message
NP_KPI_25 GBR Satisfied Rate
NP_KPI_26a Intra-MME Tracking Area Update Success Rate
NP_KPI_26b Inter-MME Tracking Area Update Success Rate
NP_KPI_3 UE Context Drop Rate
NP_KPI_8 SAE Dedicated Bearer Setup Success Rate
NP_KPI_9 EPS Bearer Drop Rate
SLA_KPI_1 Attach Failure Rate - ALU System Related
SLA_KPI_2 Service Request Failure Rate - ALU System Related

689

690 Table 4.4.1-2
Quality of Experience KPIs
KPI# Description
NP_KPI_4a Uplink Residual BLER with Semi-Persistent Scheduling for VoIP
NP_KPI_4b Uplink Residual BLER with Dynamic Scheduling
NP_KPI_5 Downlink Residual BLER with Semi-Persistent Scheduling for VoIP
NP_KPI_5b Downlink Residual BLER with Dynamic Scheduling
Q_KPI_1 Mean Opinion Score (VoIP)
Q_KPI_2 Video Quality Metric (Video)
691
692 4.4.2 End-to-end Network Requirement for Network Performance KPIs

693
ALU KPI ID CP_KPI_3
ALU KPI Name 1st Page Success Rate
ALU KPI Type Network Performance
ALU KPI Scope E2E
ALU KPI Description Out of all paging attempts, the percentage of paging attempts for which the UE
responds to the first page.
ALU Internal Target No load: >=99.5%

Typical load: >=90% (average)
ALU Public Target
ALU Measurement PCMD method:

Method Numerator (1st Page Attempt Success) = # of PCMD Records in which
Attempt_1_Success_Fail (i.e. "Paging Strategy – Attempt 1 Result") = Success
Denominator (total Page Attempts) = # of PCMD Records in which ProcedureID =
Paging (sum of "Number Paging Attempts" PCMDs).
Start: When MME sends the first Page attempt for a UE
End: When MME receives the Service Request message from the UE in response to
the 1st Page.
MME Counter method:

100 * (AttPaging_FirstAttempt
- VS.NbrPagingTO_FirstAttempt)
/ AttPaging_FirstAttempt

ALU KPI Comments Prior to LA5 this KPI can be undercounted during eNB paging overload. This is because
a 1st page attempt can be delayed by one or more defaultPagingCycle on the eNB if
the Paging Ocassion of the UE already had one or more page messages for other UEs
and they are ahead of the 1st page attempt such that MME sends a 2nd page attempt.
The Service Request message from the UE can thus be the response to the delayed
1st page attempt rather than the 2nd page attempt.
This problem does not apply to LA5 eNB thanks to the support of multiple S1 page
messages per eNB Page (L108282). This new capability is expected to improve the
success rates under typical and full load conditions.
Critical No
Dashboard
LE1 KPI ID
Validator
Impacted Entities
Application
Duplex Method FDD
Solution E2E
Level Cluster
SE Conditions
SE Owner Jin Wang
SE Reference
SE Review Status
Test Consideration
Test Notes
Test Owner
Test Reference

Test Review Status
Test Plan
695
696

ALU KPI ID CP_KPI_4
ALU KPI Name Paging Success Rate
ALU KPI Scope E2E
ALU KPI Description Out of all paging attempts, the number of paging attempts for which the UE responds.
ALU Internal Target No Load: >99.5% (Average), Typical Load: >98% (Average), Full Load: >98% (Average),
ALU Public Target

100 * (VS.NbrPageRespInLastSeenTA + VS.NbrPageRespNotInLastSeenTA) /
Method VS.AttPaging_FirstAttempt
Start: when MME sends the first Page attempt for a UE

End: when MME receives the Service Request message from the UE
ALU KPI Comments The targets assume 1) UE will send acknowledge as paging response all the time to eNB
after the paging message successfully decoded, 2) UE is in paging coverage area.
The paging successful rate obtained from market statistics includes the failures due to
above mentioned two cases; therefore it tends to be lower.
How to exclude the statistics of these two cases in the field testing data is an open issues
at this time.
Critical Yes
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, Air Interface, eNB, BH
Application
Duplex Method
Solution

Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes Verification method uses MME counters.
Test Owner
Test Reference
Test Plan
698
699
700

ALU KPI ID NP_KPI_1
ALU KPI Name Bearer Establishment Success Rate
ALU KPI Description This KPI provides the rate for successful access to LTE resources for services. It is based
on the RRC Connection Setup Success Rate for traffic, S1 Connection establishment with
the MME, and the SAE Access Bearer Setup Success Rate with the network. These KPIs
are multiplied to get the overall bearer establishment success rate.
ALU Internal Target No Load: >98% (Average), Typical Load: >98% (Average), Full Load: >98% (Average),
ALU Public Target

Method 100 * [RRC.ConnEstabSucc.Sum /
(RRC.ConnEstabAtt.EmergencyCallAttempts
+ RRC.ConnEstabAtt.HighPriorityAccessAttempts
+ RRC.ConnEstabAtt.PageResponsesReceived
+ RRC.ConnEstabAtt.MobileOriginatedSignalling
+ RRC.ConnEstabAtt.MobileOriginatedUserBearer
+ RRC.ConnEstabAtt.Other)]
*[ (VS.FirstDLNasTransport +
VS.InitialContextSetupSuccess.WithoutPreviousDLNASTransport)
/ S1SIG.ConnEstabAtt ]
*[ (∑SAEB.EstabInitSuccNbr + ∑ SAEB.EstabAddSuccNbr)
/ (∑SAEB.EstabInitAttNbr + ∑ SAEB.EstabAddAttNbr) ]
ALU KPI Comments The sample of admission failure should be excluded in the statistics. This also assumes
zero no response rate (NRR). There always an answer if the calls have gone through.
Critical Yes
Dashboard
LE1 KPI ID
Validator

Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions when there is zero failure rate of admission
SE Owner
SE Reference
Test Consideration
Test Notes The counters are provided by eNB.
Test Owner
Test Reference
Test Plan
702
703
704

ALU KPI Name RRC Connection Setup Success Rate
ALU KPI Scope RAN
ALU KPI Description The percentage of successful RRC connection set-ups per eNB in a non-overlapping 15
minute interval. A successful RRC connection set-up occurs when the eNB sends an RRC
connection set-up message in response to a UE originated RRCConnectionRequest
message (see 3GPP TS 36.331 for details).
ALU Internal Target Typical load: max >99.25%
ALU Public Target

Method 100*RRC.ConnEstabSucc.Sum/(
VS.RrcConnectionRequestWithoutRepetition.EmergencyCallAttempts+
VS.RrcConnectionRequestWithoutRepetition.HighPriorityAccessAttempts+
VS.RrcConnectionRequestWithoutRepetition.PageResponsesReceived+
VS.RrcConnectionRequestWithoutRepetition.MobileOriginatedSignalling+
VS.RrcConnectionRequestWithoutRepetition.MobileOriginatedUserBearer+
VS.RrcConnectionRequestWithoutRepetition.Other)
ALU KPI Comments RRC connection setup failures due to reasons such as RRC.ConnEstabFail.CACFailure
etc are excluded.
The granularity of CAC may be eNodeB, cell or PLMN.
Critical Yes
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, eNB, Air Interface
Application
Duplex Method FDD

Solution eNB
Level Cluster
SE Conditions
SE Owner Jin Wang
SE Reference
SE Review Status
Test Consideration
Test Notes
Test Owner
Test Reference
Test Review Status
Test Plan
706
707
708

709 ALU KPI ID NP_KPI_10a
ALU KPI ID NP_KPI_10a
ALU KPI Name Bearer Establishment Success Rate for emergency VoIP call
ALU KPI Description This KPI provides the rate of Bearer attempts for emergency VoIP calls, which succeeds
at the network side (includes emergency attach requests and PDN connectivity request for
emergency services after UE normal attached).
(Average),
ALU Public Target
ALU Measurement Counter

Method 100 * (VS.NbrSuccessEmergencyPDNConnReq +
VS.NbrSuccessEmergencyAttachRequests ) / (VS.AttEmergencyPDNConnReq +
VS.AttEmergencyAttachRequests)
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Owner
SE Reference
SE Review Status Draft
Test Consideration Four different behaviors of emergency bearer support can be tested:
a. Valid UEs only. No limited service state UEs are supported in the network. Only normal
UEs that have a valid subscription, are authenticated and authorized for PS service in the
attached location are allowed. It is not expected that a normal UE would perform an
emergency attach. Normal UEs should be attached to the network and then perform a
PDN Connection Request when an IMS emergency session is detected by the UE.
b. Only UEs that are authenticated are allowed. These UEs must have a valid IMSI. These
UEs are authenticated and may be in limited service state due to being in a location that
they are restricted from service. A UE that cannot be authenticated will be rejected.
c. IMSI required, authentication optional. These UEs must have an IMSI. If authentication
fails, the UE is granted access and the unauthenticated IMSI retained in the network for
recording purposes. The IMEI is used in the network as the UE identifier. IMEI only UEs
will be rejected (e.g., UICCless UEs).
d. All UEs are allowed. Along with authenticated UEs, this includes UEs with an IMSI that
cannot be authenticated and UEs with only an IMEI. If an unauthenticated IMSI is
provided by the UE, the unauthenticated IMSI is retained in the network for recording
purposes. The IMEI is used in the network to identify
Test Notes This KPI identifies bearer success but does not address the E2E emergency call.
Test Owner
Test Reference
Test Review Status
Test Plan
710
711
712

ALU KPI Name Service Request Setup Success Rate for emergency call
ALU KPI Description This KPI provides the rate (percentage) for successful Service Request procedure setup
for emergency service. For success scenario the procedure starts when the UE sends
Service Request message for emergency service to the MME and ends when Modify
Bearer Response is received from the SGW at the MME.
(Average),
ALU Public Target
ALU Measurement Counter

Method 100 * VS.NbrSuccessEmergencyServiceReq /VS.AttEmergencyServiceReq
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Owner
SE Reference
Test Consideration
Test Notes The counters are provided by the MME.
Test Owner
Test Reference
Test Review Status
Test Plan
714
715
716

ALU KPI Name Attach Success Rate
ALU KPI Description This KPI provides the rate (percentage) for successful Attach request setup. For success
scenario the procedure starts when the UE sends Attach Request to the MME and ends
when Modify Bearer Response is received at MME.
ALU Internal Target No Load: > 99.5% (Average), Typical Load: >98% (Average), Full Load: >98% (Median)
ALU Public Target
ALU Measurement Counter 100 * NbrSuccessAttachRequests / VS.AttAttachRequests

Method For success scenario:
Start: when MME receives Attach Request from the UE
End: when MME receives Modify Bearer Response from the SGW
ALU KPI Comments
Critical Yes
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration Testing results exclude authentication failures and UE related problems.
Test Notes The verification method uses MME counters.
Test Owner
Test Reference Attach call flow is at [R17] (section 4.1).
Test Plan
718
719
720

ALU KPI Name Service Request Setup Success Rate
ALU KPI Description This KPI provides the rate (percentage) for successful Service Request procedure setup.
For success scenario the procedure starts when the UE sends Service Request message
to the MME and ends when Modify Bearer Response is received from the SGW at the
MME.
ALU Internal Target No Load: > 99.5% (Average), Typical Load: > 98.5% (Average), Full Load: >98% (Median)
ALU Public Target
ALU Measurement Counter 100 * VS.NbrSuccessServiceRequests / VS.AttServiceRequests

Method For success scenario:
Start: when MME receives Service Request message from the UE
ALU KPI Comments Service Request may still succeed if a subset of the bearers cannot be established as
long as those failed bearers are not required to serve the UE's application.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference Refer to 5.1.1.4
Test Consideration Testing results exclude authentication failures if performed and UE related problems.
Test Owner
Test Reference
Test Plan
722
723
724

725 ALU KPI ID NP_KPI_1x
ALU KPI ID NP_KPI_1x
ALU KPI Name Bearer Establishment Success Rate excluding repeated occurrences of RRC Connection
Request message
ALU KPI Description This KPI provides the rate for successful access to LTE resources for services. It is based
on the RRC Connection Setup Success Rate for traffic (excluding repeated occurrences of
RRC Connection Request message), S1 Connection establishment with the MME, and the
SAE Access Bearer Setup Success Rate with the network. These KPIs are multiplied to
get the overall bearer establishment success rate.
ALU Internal Target No Load: >99.5% (Average)
ALU Public Target

Method 100 * [RRC.ConnEstabSucc.Sum /
(VS.RrcConnectionRequestWithoutRepetition.EmergencyCallAttempts
+ VS.RrcConnectionRequestWithoutRepetition.HighPriorityAccessAttempts
+ VS.RrcConnectionRequestWithoutRepetition.PageResponsesReceived
+ VS.RrcConnectionRequestWithoutRepetition.MobileOriginatedSignalling
+ VS.RrcConnectionRequestWithoutRepetition.MobileOriginatedUserBearer
+ VS.RrcConnectionRequestWithoutRepetition.Other)]
*[ (VS.FirstDLNasTransport +
VS.InitialContextSetupSuccess.WithoutPreviousDLNASTransport)
/ S1SIG.ConnEstabAtt ]
*[ (∑SAEB.EstabInitSuccNbr + ∑ SAEB.EstabAddSuccNbr)
/ (∑SAEB.EstabInitAttNbr + ∑ SAEB.EstabAddAttNbr) ]
Critical No
Dashboard
LE1 KPI ID
Validator

Application
Duplex Method FDD/TDD
Solution E2E
Level Cluster
SE Conditions When there is zero failure rate of admission
SE Owner
SE Reference
SE Review Status
Test Consideration
Test Owner
Test Reference
Test Plan
726
727
728

ALU KPI Name GBR Satisfied Rate
ALU KPI Description The percentage of time during which GBR E-RABs have been satisfied with their required
bit rate.
ALU Internal Target No Load: > 99.5% (Average), Typical Load: >98% (Average), Full Load: TBD (Average),
ALU Public Target
ALU Measurement Counter 100 * (VS.GBRERABSatisfied.Satisfied / (VS.GBRERABSatisfied.Satisfied +

VS.GBRERABSatisfied.Unsatisfied) )
Method
ALU KPI Comments The definition for GBR success rate is based on UTIL02 in AT&T's Attachment F2. It is
measured the percentage of time GBR Bearer is satisfied.
Assumption: When GBR is setup, it is assumed resource is allocated to serve the bearer
which takes into account bursty traffic characteristics associated with certain type of
applications. Based on LE4.0 Traffic Model M2-C, GBR bearer ratio is less significant so
the GBR satisfied rate should not be impacted even with full load.
Open Issue: Whether such assumption is valid for testing.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes This KPI is added per AT&T contract (UTIL02).

The counters are provided by eNB.
Test Owner
Test Reference
Test Plan
730
731
732

ALU KPI Name Intra-MME Tracking Area Update Success Rate
ALU KPI Scope E2E
ALU KPI Description The percentage of Tracking Area Update with MME relocation procedures has been
successfully completed.
A successful TAU update is from a successful UE transmission of an RRC Connection
Complete (with TAU Request) to the successful UE reception of the TAU Accept
message.
ALU Public Target
ALU Measurement Counter 100 * (VS.NbrSuccessTAU-VS.TauInterMmeSucc) / (VS.AttTAU-

VS.TauInterMmeAtt)
Method
ALU KPI Comments This KPI is part of VzW FSA KPIs.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Owner
Test Reference
Test Plan
734
735
736

ALU KPI Name Inter-MME Tracking Area Update Success Rate
ALU KPI Scope E2E
ALU KPI Description The percentage of Tracking Area Update with MME relocation procedures has been
successfully completed.
A successful TAU update is from a successful UE transmission of an RRC Connection
Complete (with TAU Request) to the successful UE reception of the TAU Accept
message.
ALU Public Target
ALU Measurement Counter 100 * VS.TauInterMmeSucc / VS.TauInterMmeAtt

Method
ALU KPI Comments This KPI is part of VzW FSA KPIs.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Owner
Test Reference
Test Plan
738
739
740

ALU KPI ID NP_KPI_3
ALU KPI Name UE Context Drop Rate
ALU KPI Description The KPI is the rate at which ALL Bearers associated with a UE are dropped without an
indication from the UE to drop them. This KPI does not include abnormal UE Context
drops due to poor RF conditions.
ALU Internal Target No Load: <1% (Average), Typical Load: <1% (Average), Full Load: <2% (Average),
ALU Public Target

100*(VS.UEContextReleaseRequest.RadioLinkFailure
Method +VS.UEContextReleaseRequest.InternalFailure
+VS.UEContextReleaseRequest.Congestion
+VS.LocalUEContextRelease.S1APResetMME
+VS.LocalUEContextRelease.S1FaultExternalFailure
+VS.LocalUEContextRelease.S1APResetENodeB)
/(VS.UEContextReleaseCommandSum
+VS.LocalUEContextReleaseSum
–VS.UEContextReleaseRequest.NoInitialContextSetupRequest
–VS.InitialContextSetupFailedSum)
ALU KPI Comments The full load target specified is still preliminary.
Critical Yes
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method

Solution
Level
Customer Viewable
SE Conditions This excludes UE Contexts dropped due to UE bad RF conditions
SE Owner
SE Reference
Test Consideration

The formula specified above represents abnormal UE Context release ratio which may
include some of the releases occurred during UE Context setup stage. Due to lack of
counters to accurately capture the UE Context Drop Rate after Context establishment thus
this formula is specified under the assumption the chance for abnormal UE context
release to occur during context setup is uncommon.
Justifications:
InitialContextSetupRequest is subtracted because this scenario occurs prior to receiving
the initial UE Context Setup Request from the MME => Before Context Establishment
VS.InitialContextSetupFailedSum is subtracted because when Context Setup failure

occurs eNB will either send Initial UE Context Setup Failure or UE Context Release
Request to MME, thus all these failures are captured in either
VS.UEContextReleaseCommandSum or VS.LocalUEContextReleaseSum depending on
whether receiving MME's response => Before Context Establishment
There is still inaccuracy for both the numerator and the denominator. Some examples are:
UE Context setup failure counter could include context releases occurred during Initial
Context setup stage
S1 reset could occur during Initial UE Context setup
RFL could occur during Initial UE Context setup
Observation: If UE Context setup failure rate is high then the above formula could be
inaccurate.
Test Owner
Test Reference

Test Plan
742
743
744

ALU KPI ID NP_KPI_8
ALU KPI Name SAE Dedicated Bearer Setup Success Rate
ALU KPI Description This KPI provides the percentage of SAE Dedicated Bearer attempts for any call
independent of QoS usage and data rate, which succeed at the network side (after RRC
Connection has already been established).
(Average),
ALU Public Target
ALU Measurement Counter 100 * ( 1 - ∑VS.NbrFailedCreateDedicatedBearer_QCI_x /

VS.AttCreateDedicatedBearer_sum)
Method where x=1..9
Start: when the MME receives Create Dedicated Bearer Request from the S-GW
End: when the MME sends Create Dedicated Bearer Response to the S-GW.
ALU KPI Comments This rate is defined for the network portion of the Dedicated Bearer setup, which assumes
the Default Bearer is already established.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities MME, BH, eNB, SGW, PGW
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration This KPI assumes Default Bearer has already been setup.
Test Notes This KPI is a network KPI. The verification method uses MME counters.
The abort cases occurred during Dedicated Bearer setup are not considered as failures
thus they are excluded in the formula.
The following abort rate formula can be used to understand the percentage of Dedicated
Bearer setup procedure has been aborted:
Dedicated Bearer Setup Abort Rate = 100 * VS.NbrCreateDedicatedBearerAbort /
VS.AttCreateDedicatedBearer_sum
Test Owner
Test Reference
Test Plan
746
747
748

ALU KPI ID NP_KPI_9
ALU KPI Name EPS Bearer Drop Rate
ALU KPI Description The KPI is the rate at which EPS Bearer is dropped without an indication from the UE to
drop the bearer.
ALU Internal Target No Load: <0.5% (Average), Typical Load: <1% (Average), Full Load: <2% (Average),
ALU Public Target
ALU Measurement Counter 100 * ∑VS.AbnormalERABReleasePerQCI

Method / (∑VS.NormalERABRelease
+ ∑VS.AbnormalERABReleasePerQCI)
ALU KPI Comments
Critical Yes
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable

SE Conditions This excludes the drop bearer connections due to UE bad RF conditions
SE Owner
SE Reference
Test Consideration This excludes the drop bearer connections due to UE bad RF conditions
Test Owner
Test Reference
Test Plan
750
751
752

753 ALU KPI ID SLA_KPI_1
ALU KPI ID SLA_KPI_1
ALU KPI Name Attach Failure Rate - ALU System Related
ALU KPI Scope E2E
ALU KPI Description This KPI provides the rate (percentage) for unsuccessful Attach request setup due to ALU
system related reasons. The ALU system related failures include either software or
hardware problems occurred at ALU's LTE NEs (network elements). In LE2.0 and beyond,
ALU's LTE NEs include eNB, MME, and SGW.
ALU Internal Target No Load: <0.5% (Average), Typical Load: <0.5% (Average), Full Load: <0.5% (Average),
ALU Public Target
ALU Measurement Counter 100 * (VS.NbrAttachFailureSysRelatedMME +

VS.NbrAttachFailureSysRelatedSGW + VS.NbrAttachFailureSysRelatedENB) /
Method VS.AttAttachRequests
This KPI measures Attach Establishment failures due to ALU system related reasons. For
success scenario:
Start: when MME receives Attach Request from the UE
ALU KPI Comments This requirement is specified under the condition that all the UEs are in good RF
condition. Attach failure rate only counts the ALU's eNB, MME, and SGW failures. The
failure occurred at eNB, MME and SGW but caused by defects of other network elements
should not included as well.
This KPI is specified for VzW SLA contractual agreement with VzW for Failed Call Attempt
Rate. "Fail Calls" is defined as either Attach failure or Service Request failure due to ALU
system related reasons. "ALU system" in VzW's markets include eNB, MME and SGW
from LE2.x. This view may change in future releases. Only the following interface failure
reasons are considered as "System Related Failures":
S1AP: Multiple E-RAB ID Instances, Hardware Failure, Unknown or already allocated eNB
UE S1AP ID, Unknown or already allocated MME UE S1AP ID.
S11: Invalid Length, Mandatory IE Incorrect, Mandatory IE Missing, System Fail.
Critical Yes
Dashboard
LE1 KPI ID
Validator

Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Owner
Test Reference
Test Plan
754
755
756

757 ALU KPI ID SLA_KPI_2
ALU KPI ID SLA_KPI_2
ALU KPI Name Service Request Failure Rate - ALU System Related
ALU KPI Scope E2E
ALU KPI Description This KPI provides the rate (percentage) for unsuccessful Service Request setup due to
ALU system related reasons. The ALU system related failures include either software or
hardware problems occurred at ALU's LTE NEs (network elements). In LE2.0, ALU's LTE
NEs include eNB, MME, and SGW.
ALU Internal Target No Load: <0.5% (Average), Typical Load: <0.5% (Average), Full Load: <0.5% (Average),
ALU Public Target
ALU Measurement Counter 100 * VS.NbrServiceReqFailureSysRelated_sum / VS.AttServiceRequests

Method This KPI measures Service Request setup failures due to ALU system related reasons.
For success scenario:
Start: when MME receives Service Request message from the UE
ALU KPI Comments This requirement is specified under the condition that all the UEs are in good RF
condition. Service Request failure rate only counts the ALU's eNB, MME, and SGW
failures. The failure occurred at eNB, MME and SGW but caused by defects of other
network elements should not included as well.
This KPI is specified for VzW SLA contractual agreement with VzW for Failed Call Attempt
Rate. "Fail Calls" is defined as either Attach failure or Service Request failure due to ALU
system related reasons. "ALU system" in VzW's markets include eNB, MME and SGW
from LE2.x. This view may change in future releases. Only the following interface failure
reasons are considered as "System Related Failures":
S1AP: Multiple E-RAB ID Instances, Hardware Failure, Unknown or already allocated eNB
UE S1AP ID, Unknown or already allocated MME UE S1AP ID.
S11: Invalid Length, Mandatory IE Incorrect, Mandatory IE Missing, System Fail.
Critical Yes
Dashboard
LE1 KPI ID
Validator

Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration

VS.NbrServiceReqFailureSysRelated_sum is the sum of the following counters:
VS.NbrServiceReqFailureSysRelatedENB
VS.NbrServiceReqFailureSysRelatedMME
VS.NbrServiceReqFailureSysRelatedSGW
Test Owner
Test Reference
Test Plan
758
759

760
761 4.4.3 End-to-end Network Requirement for Quality of Experience KPIs

762
ALU KPI Name Uplink Residual BLER with Semi-Persistent Scheduling (for VoIP)
ALU KPI Type Quality of Experience
ALU KPI The percentage of errored transport blocks in an LTE transport uplink channel (PUSCH
Description Residual BLER, as detected by the 24 bit CRC with Semi-Persistent Scheduling) with
residual MAC BLER less than or equal to 1%
ALU Internal No Load: >99.5% (Average), Typical Load: >99% (Average), Full Load: >99% (preliminary)
Target (Average)
ALU Public
Target
ALU Other Using active test

Measurement
Method
ALU KPI This requirement applies to the PUSCH blocks carriers payload traffic excluding the blocks
Comments containing control information. This also excludes the packets that carried before traffic
channel setup and after traffic channel starting tear down.
AT&T's contract (INT01) target is <2.5%.
Critical Yes
Dashboard
LE1 KPI ID
Validator
Impacted UE, Air Interface, eNB

Entities

Application
Duplex Method
Solution
Level
Customer
Viewable
SE Conditions Peak coverage mode: max HARQ=5

Nominal mode: max HARQ=2
SE Owner
SE Reference
SE Review Approved
Status
Test Peak coverage mode: max HARQ=5

Consideration Nominal mode: max HARQ=2
Test Notes Percentage of UL Residual BLER lower than or equal to 1%

= 100 *
(VS.CNAME.LEThreshold1NotNull)
/
(VS.CNAME.LEThreshold1NotNull +
VS.CNAME.GTThreshold1LEThreshold2 +
VS.CNAME. GTThreshold2LEThreshold3 +
VS.CNAME.GTThreshold4)
Where CNAME = “ULResidualMacBLERWithSemiPersistentScheduling”
Range1=1%, Range2= 2.5%, Range3= 5%,Range4= 10%
Test Owner
Test Reference
Test Review
Status
Test Plan

764
765
766

ALU KPI Name Uplink Residual BLER with Dynamic Scheduling
ALU KPI The percentage of errored transport blocks in an LTE transport uplink channel (PUSCH
Description Residual BLER, as detected by the 24 bit CRC with Dynamic Scheduling) with residual MAC
BLER less than or equal to 1%
Target (Average)
ALU Public
Target

Measurement
Method
ALU KPI This requirement applies to the PUSCH blocks carriers payload traffic excluding the blocks
channel setup and after traffic channel starting tear down. This requirement excludes the UE
in bad RF conditions.
Critical Yes
Dashboard
LE1 KPI ID
Validator

Entities
Application
Duplex Method
Solution

Level
Customer
Viewable
SE Conditions Max HARQ=5
SE Owner
SE Reference
SE Review Approved
Status
Test Max HARQ=5

Consideration
Test Notes Percentage of UL Residual BLER lower than or equal to 1%

= 100 *
(VS.CNAME.LEThreshold1)
/
(VS.CNAME.LEThreshold1 +
Where CNAME = “ULResidualMacBLERWithDynamicScheduling”
Range1=1%, Range2= 2%, Range3= 5%,Range4= 10%
Test Owner
Test Reference
Test Review
Status
Test Plan
768
769
770

ALU KPI ID NP_KPI_5
ALU KPI Name Downlink Residual BLER with Semi-Persistent Scheduling (for VoIP)
ALU KPI The percentage of errored transport blocks in an LTE transport downlink channel (PUSCH
Description Residual BLER, as detected by the 24 bit CRC with Semi-Persistent Scheduling) with
residual MAC BLER less than or equal to 1%
Target (Average)
ALU Public
Target

Measurement
Method
ALU KPI This requirement applies to the PDSCH blocks carriers payload traffic excluding the blocks
AT&T's contract (INT02) is <2.5%
Critical Yes
Dashboard
LE1 KPI ID
Validator

Entities
Application
Duplex Method
Solution
Level
Customer
Viewable
SE Conditions Target for initial BLER is 10%. Max HARQ=4
SE Owner
SE Reference
SE Review Approved
Status
Test Target for initial BLER is 10%. Max HARQ=4

Consideration
Test Notes Percentage of DL Residual BLER lower than or equal to 1%

= 100 *
(VS.CNAME.LEThreshold1NotNull)
/
(VS.CNAME.LEThreshold1NotNull +
Where CNAME = “DLResidualMacBLERWithSemiPersistentScheduling”
Range1=1%, Range2= 2.5%, Range3= 5%,Range4= 10%
Test Owner
Test Reference
Test Review
Status
Test Plan
772
773
774

ALU KPI Name Downlink Residual BLER with Dynamic Scheduling
ALU KPI The percentage of errored transport blocks in an LTE transport downlink channel (PUSCH
Description Residual BLER, as detected by the 24 bit CRC with Dynamic Scheduling) with residual MAC
BLER less than or equal to 1%
Target (Average)
ALU Public
Target

Measurement
Method
ALU KPI This requirement applies to the PDSCH blocks carriers payload traffic excluding the blocks
Critical Yes
Dashboard
LE1 KPI ID
Validator

Entities
Application
Duplex Method
Solution

Level
Customer
Viewable
SE Conditions Target for initial BLER is 10%. Max HARQ=4
SE Owner
SE Reference
SE Review Approved
Status
Test Target for initial BLER is 10%. Max HARQ=4

Consideration
Test Notes Percentage of DL Residual BLER lower than or equal to 1%

= 100 *
(VS.CNAME.LEThreshold1)
/
(VS.CNAME.LEThreshold1 +
Where CNAME = “DLResidualMacBLERWithDynamicScheduling”
Range1=1%, Range2= 2%, Range3= 5%,Range4= 10%
Test Owner
Test Reference
Test Review
Status
Test Plan
776
777
778

779 ALU KPI ID Q_KPI_1
ALU KPI ID Q_KPI_1
ALU KPI Name Mean Opinion Score (VoIP)
ALU KPI Scope E2E
ALU KPI Description The user perception of subjective voice quality per ITU-T Recommendation P.800 &
P.800.1, or an estimate of this subjective assessment of voice quality via objective
models. The ALU version of voice assessment (ROVA) uses an objective estimate of
voice quality based on the advanced version of the model specified in American National
Standard ANSI ATIS 0100005-2006
ALU Internal Target No Load: >3.4 (Average)
ALU Public Target
ALU Measurement Other (specify below) Active test using UEs, estimation of MOS using ROVA
Method
ALU KPI Comments This excludes the cases when UE is persistently in bad RF conditions.
The current targets are minimum requirements for all voice codecs.
The MoS targets differentiate the voice codec remain an open issue for FFS. If empirical
data is not available, It's recommended to adjust the targets with reference of the ALU lab
testing results.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution

Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
780
781
782

783 ALU KPI ID Q_KPI_2
ALU KPI ID Q_KPI_2
ALU KPI Name Video Quality Metric (Video)
ALU KPI Scope E2E
ALU KPI Description The user perception of subjective video quality per ITU-R BT.500 or an estimate of this
subjective assessment of voice quality via objective models. The ALU version of video
quality assessment (LVAT) uses an objective estimate of video quality using either full-
reference or single-ended model depending on the availability and characteristics of the
source content.
ALU Internal Target No Load: 3.5 (no-reference), 4.0 (full-reference) (Average), 3.1 (no-reference), 3.5 (full-
reference) (95%-tile), Typical Load: 3.5 (no-reference), 4.0 (full-reference) (Average), 3.1
(no-reference), 3.5 (full-reference) (95%-tile), Full Load: 3.5 (no-reference), 4.0 (full-
reference) (Average), 3.1 (no-reference), 3.5 (full-reference) (95%-tile),
ALU Public Target
ALU Measurement Other (specify below) Active test using UEs, estimation of MOS using LVAT.
Method
ALU KPI Comments This excludes the cases when UE is persistently in bad RF conditions.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference
Test Consideration
Test Notes Video Quality Metric KPI is not completely defined in the Standard. Each customer may
choose to use their own tool to measure Video Quality thus test results may vary
depending on the tools used. The KPI target is specified based on ALU's LVAT tool.
Test Owner
Test Reference
Test Plan
784
785

786 4.5 Product Performance KPI

788 Table 4.5.1-1
Product Performance KPIs
KPI# Description
PP_KPI_4 Downlink RLC retransmitted bytes (%)
PP_KPI_6 eNB processor occupancy (%)

789
790
791 4.5.2 End-to-end Network Requirement for Product Performance KPIs

792
793 ALU KPI ID PP_KPI_4
ALU KPI ID PP_KPI_4
ALU KPI LE5.0

Release
ALU KPI Name Downlink RLC retransmitted bytes (%)
ALU KPI Type Product Performance
ALU KPI eNB

Scope
ALU KPI The number of RLC retransmitted bytes in downlink as a percentage of the total number of
Description RLC transmitted bytes in downlink within each non-overlapping 15 minute interval.
ALU Internal Typical load: Average <= 1%

Target
ALU Public
Target
ALU RLC Re-transmission Rate for DL

Measurement = 100*(VS.DLRlcPduRetransmitted.GBR
+ VS.DLRlcPduRetransmitted.NonGBR)
Method / (VS.DLRlcPduSent.OtherGBR
+ VS.DLRlcPduSent.NonGBR)
The above calculation uses eNB counters. VoIP is not taken into account in the
VS.DLRlcPduRetransmitted.GBR counter (no retransmission for VoIP).

ALU KPI
Comments
Critical No
Dashboard
LE1 KPI ID
Validator
Impacted
Entities
Application
Duplex FDD
Method
Solution eNB
Level Cell
Customer No
Viewable
SE Conditions
SE Owner
SE Reference
SE Review
Status
Test
Consideration
Test Notes
Test Owner
Test
Reference


ID
Test Review
Status
Test Plan
794
795
796

797 ALU KPI ID PP_KPI_6
ALU KPI ID PP_KPI_6
ALU KPI LE5.0

Release
ALU KPI Name eNB processor occupancy (%)
ALU KPI Type Product Performance
ALU KPI eNB

Scope
ALU KPI The eNB processor occupancy is (%SYS + %USR in eCCM) averaged over 15 minutes of time
Description interval.
ALU Internal 1 - Under Typical Load less than 60%

Target
2 - Under Max Load less than 80%
ALU Public
Target
ALU Laptop running eNB polling script; eCCM PO measured real-time inside eNB.
Measurement
Method
ALU KPI
Comments
Critical No
Dashboard
LE1 KPI ID
Validator
Impacted
Entities
Application
Duplex FDD
Method

Solution eNB
Level Cell
Customer No
Viewable
SE Conditions
SE Owner
SE Reference
SE Review
Status
Test For typical loading, the number of active users is 65%* max active users. For example, for the
Consideration full load case, the number of active users is 200 (for 5, 10, 15 and 20 MHz systems). For the
typical load case, the number of active users is 200*65% = 130 (for 5, 10, 15 and 20 MHz
systems).
Test Notes
Test Owner
Test
Reference

ID
Test Review
Status
Test Plan
798
799
800

801 4.6 Inter RAT KPI

803 Table 4.6.1-1
IRAT Handover KPIs

KPI# Description
CP_KPI_28 LTE to CDMA HO Interruption time Type 1 HO (data)
CP_KPI_28b LTE to CDMA HO Interruption time Type 2 HO (data)
Enhanced Non-optimized LTE-to-HRPD Handover Procedure
CP_KPI_28d
Latency
CP_KPI_30 LTE to UMTS HO Interruption time (data)
CP_KPI_30b LTE to UTRAN PS Handover Procedure Latency
Data Interruption time for LTE-to-UTRAN PS Mobility via
CP_KPI_30d
Redirection
Data Interruption Time for LTE to GERAN PS Mobility using
CP_KPI_31a
CCO with NACC
CP_KPI_31c LTE-to-GERAN Handover via Redirection Interruption Time
CP_KPI_32a Voice Call Setup Time for CSFB to UTRAN using PSHO
CP_KPI_32b Voice Call Setup Time for CSFB to UTRAN using Redirection
CP_KPI_32d Data Interruption Time due to LTE to UTRAN CSFB via
Redirection
CP_KPI_33a Voice Call Setup Time for CSFB to GERAN using CCO with
NACC
CP_KPI_33b Voice Call Setup Time for CSFB to GERAN using Redirection
CP_KPI_39a Voice Call Setup Preparation Time for CSFB to 1xRTT by idle
Dual-Rx UE, delay Optimized
CP_KPI_39b Voice Call Setup Preparation Time for CSFB to 1xRTT by idle
Dual-Rx UE, delay Not Optimized
CP_KPI_40 Voice Call Interruption time for SRVCC HO to UTRAN
NP_KPI_16 Outgoing LTE to UMTS Handover Success Rate
NP_KPI_18 Outgoing LTE to GSM Handover Success Rate
804
805
806 4.6.2 End-to-end Network Requirement

807
ALU KPI Name LTE to CDMA HO Interruption time Type 1 HO (data)

ALU KPI Type IRAT
ALU KPI Description The elapsed time between last BE packet received by UE (approximately when receiving
RRC Connection Release message with redirectedCarrierInfo set to cdma2000-HRPD
from source LTE eNB) and 1st BE packet can be received by UE from target eHRPD
system.
ALU Internal Target No Load: 6320 msec (Average), Typical Load: 8090 msec (Average), Full Load: 9880
msec (Average),
ALU Public Target
Start: the last (traffic) grant received from the source LTE eNB cell
Method End: the first (traffic) grant received from the target eHRPD BTS
ALU KPI Comments The targets specified in the requirement include the RRC Connection Release latency
which takes ~50ms.
Based on LE2.1 testing, ~830ms latency is observed on average at UE side once
receiving the RRC Connection release before the UE starts looking for eHRPD network.
This latency is added to the original target numbers which were estimated assuming UE
immediately tune to eHRPD. The delay at UE is confirmed by Qualcomm.
The delay introduced is due to that the eHRPD modem at UE is always off when the UE is
with LTE and it will be turned on after RRC connection release message arrives.
The above measurements are from LE2.1 testing the LE4.0 targets are subject to change
if UE contribution changes in LE4.0 timeframe.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, BH, EVDO BTS, Air Interface, SGW, HSGW, eNB, PGW, EVDO RNC
Application
Duplex Method
Solution
Level
Customer Viewable

SE Conditions
SE Owner
SE Reference

Test Notes The testing method specified above is for one of the approaches and is meant to be used
as reference. Other testing methods can be used to measure the interruption time based
on the definition.
Test Owner
Test Reference
Test Plan
809
810
811

ALU KPI Name LTE to CDMA HO Interruption time Type 2 HO (data)
ALU KPI Type IRAT
ALU KPI Description The elapsed time between last BE packet received by UE (approximately when receiving
RRC Connection Release message with redirectedCarrierInfo set to cdma2000-HRPD
from source LTE eNB) and 1st BE packet can be received by UE from target eHRPD
system.
ALU Internal Target No Load: 2570 msec (Average), Typical Load: 3090 msec (Average), Full Load: 3630
msec (Average),
ALU Public Target
Method End: the first (traffic) grant received from the target eHRPD BTS
ALU KPI Comments The targets specified in the requirement include the RRC Connection Release latency
which takes ~50ms.
Based on LE2.1 testing, ~830ms latency is observed on average at UE side once
receiving the RRC Connection release before the UE starts looking for eHRPD network.
This latency is added to the original target numbers which were estimated assuming UE
immediately tune to eHRPD. The delay at UE is confirmed by Qualcomm.
The delay introduced is due to that the eHRPD modem at UE is always off when the UE is
with LTE and it will be turned on after RRC connection release message arrives.
The above measurements are from LE2.1 testing the LE4.0 targets are subject to change
if UE contribution changes in LE4.0 timeframe.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, BH, EVDO BTS, Air Interface, SGW, HSGW, eNB, PGW, EVDO RNC
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference

on the definition.
Test Owner
Test Reference
Test Plan
813
814
815

ALU KPI Name Enhanced Non-optimized LTE-to-HRPD Handover Preparation Latency
ALU KPI Type IRAT
ALU KPI Description The elapsed time between when eNB receives the MeasurementReport message which
triggers the enhanced redirection to RRC Connection Release with Redirection message
is received at the UE.
ALU Internal Target No Load: 25ms (Average), Typical Load: Full Load: 35ms (Average),
ALU Public Target
ALU Measurement Other (specify below) Using test equipment to measure the time difference between when
eNB receives the MeasurementReport message from the UE and when the UE
Method connection setup procedure is completed at the HRPD system.
ALU KPI Comments Some enhanced UEs may take 10% less time in acquiring the eHRPD system which will
reduce the total HO interruption time.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, EVDO BTS, BH, Air Interface, SGW, EVDO RNC, eNB, PGW, HSGW
Application
Duplex Method
Solution
Level
Customer Viewable

SE Conditions
SE Owner
SE Feature ID LS36001-03, L84876

Test Notes
Test Owner
Test Reference
Test Feature ID LS36001-03, L84876
Test Plan
817
818
819

ALU KPI Name LTE to UMTS PS HO Interruption time (data)
ALU KPI Type IRAT
ALU KPI Description The time associated with a handover from LTE to UMTS during which the flow of user
data on active bearers is stopped.
Definition (HO Latency): The elapsed time between last BE packet received or sent by the
UE (approximately when receiving HO from E-UTRAN Command from source LTE eNB)
and 1st BE packet can be received/sent by UE from/to the target UMTS NodeB.
ALU Public Target
Method End: the first (traffic) grant received from the target UMTS NodeB
ALU KPI Comments Cell unknown is defined no measurement has been done for a prolong time usually for 5
sec.
This KPI applies both pre-R8 and R8 SGSN.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, BH, Air Interface, SGW, UMTS SGSN, eNB, PGW, UMTS RNC/BSS
Application
Duplex Method FDD
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference
SE Review Status

on the definition.
Test Owner
Test Reference
Test Review Status
Test Plan
821
822
823

ALU KPI Name LTE-to-UTRAN PS Handover Preparation Latency
ALU KPI Type IRAT
ALU KPI Description The elapsed time between when eNB receives the MeasurementReport message from the
UE and handover decision is to make LTE to UTRAN PS handover and when the Mobility
From EUTRA Command for the PSHO is received at the UE.
ALU Public Target
ALU Measurement Other (specify below) Using test equipment to measure the time difference between when
eNB receives MeasurementReport message from the UE and when the target SGSN
Method receives Modify Bearer Response from the SGW.
ALU KPI Comments
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, UMTS SGSN, Air Interface, SGW, UMTS RNC/BSS, eNB, PGW, BH
Application
Duplex Method
Solution
Level
Customer Viewable

SE Conditions
SE Owner

Test Notes
Test Owner
Test Reference
Test Plan
825
826
827

ALU KPI Name Data Interruption time for LTE-to-UTRAN PS Mobility via Redirection
ALU KPI Type IRAT
ALU KPI Description The elapsed time between last BE packet received or sent by the UE (approximately when
receiving RRC Connection Release with Redirection IE from source LTE eNB) and 1st BE
packet can be received/sent by UE from/to the target UMTS NodeB.
ALU Internal Target No Load: 4.5 sec (Average)
ALU Public Target
ALU KPI Comments
Critical No
Dashboard
LE1 KPI ID
Validator Mohammad Zarrabizadeh
Application
Duplex Method FDD
Solution E2E
Level Cluster

SE Conditions
SE Owner
SE Reference

Test Notes
Test Owner
Test Reference
Test Review Status
Test Plan
829
830
831

ALU KPI Name Data Interruption Time for LTE to GERAN PS Mobility using CCO with NACC
ALU KPI Type IRAT
ALU KPI Description The elapsed time between last BE packet received by UE (approximately when UE
receiving Mobility from EUTRA Command message from source eNB) and 1st BE packet
can be received by UE from target GERAN system.
ALU Public Target
ALU Measurement Other (specify below)

Method Using UE logs to measure the duration between:
End: the first (traffic) grant received from the target GERAN cell
ALU KPI Comments
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, UMTS SGSN, HSS, Air Interface, SGW, UMTS RNC/BSS, eNB, PGW, BH
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference Refer to next requirement for NE allocations.
Test Consideration
Test Notes
Test Owner
Test Reference
Test Review Status Draft
Test Plan
833
834
835

836 ALU KPI ID CP_KPI_31c
ALU KPI ID CP_KPI_31c
ALU KPI Name LTE-to-GERAN Handover via Redirection Interruption Time
ALU KPI Type IRAT
ALU KPI Description The elapsed time between last user plane packet received or sent by UE from the source
LTE eNB (approximately when receiving RRC Connection Release with Redirection IE
from source LTE eNB) and 1st user plane packet can be received/sent by the UE from/to
the target GERAN BSS.
ALU Public Target
Start: the last (traffic) grant received from the source LTE eNB
Method End: the first (traffic) grant received from the target GERAN BSS
ALU KPI Comments This KPI applies to both pre-R8 and R8 SGSN.
This KPI is added per AT&T contract.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, SGSN, Air Interface, SGW, GERAN BSS, eNB, PGW, BH
Application
Duplex Method
Solution

Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
SE Review Status

as reference. Other testing methods can be used to measure the interruption time.
Test Owner
Test Reference
Test Review Status
Test Plan
837
838
839

ALU KPI Name Voice Call Setup Time for CSFB to UTRAN using PSHO
ALU KPI Type IRAT
ALU KPI Description This KPI quantifies the amount of time taken by the network to successfully perform a
voice call setup for CSFB to UTRAN using PSHO.
The CSFB to UTRAN using PSHO setup time is the duration between sending an
Extended Service Request at the UE to the NB and the LTE-UTRAN packet switch HO
execution completion (after TAU procedure completion).
ALU Public Target
ALU Measurement Other (specify below) Using test equipment to measure the time difference sending an
Extended Service Request at the UE to the NB and the LTE-UTRAN packet switch HO
Method execution completion (after TAU procedure completion).
ALU KPI Comments The target number specified above doesn't include RRC connection setup time which is ~
100ms.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, SGSN, MSC, Air Interface, SGW, UMTS RNC, BH, eNB, PGW, UMTS NodeB
Application
Duplex Method
Solution
Level

Customer Viewable
SE Conditions
SE Owner
SE Reference
SE Review Status
Test Consideration
Test Notes
Test Owner
Test Reference
Test Review Status
Test Plan
841
842
843

ALU KPI Name Voice Call Setup Time for CSFB to UTRAN using Redirection
ALU KPI Type IRAT
voice call setup for CSFB to UTRAN using blind redirection.
The CSFB to UTRAN using blind redirection setup time is the duration between sending
an Extended Service Request at the UE to the NB and when the CS call is successfully
established at UMTS (after Routing Area Update or Combined RA/LA Update procedure
completion).
ALU Internal Target No Load: 4710 ms (Average)
ALU Public Target
ALU Measurement Other (specify below) Using test equipment to measure the time difference between
sending an Extended Service Request at the UE to the NB and when the CS call is
Method successfully established at UMTS (after Routing Area Update or Combined RA/LA Update
procedure completion).
ALU KPI Comments The target number specified above doesn't include RRC connection setup time which is ~
100ms.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, UMTS NodeB, UMTS RNC, Air Interface, SGW, MSC, BH, eNB, PGW, SGSN
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
845
846
847

ALU KPI Name Data Interruption Time due to LTE to UTRAN CSFB via Redirection
ALU KPI Type IRAT
ALU KPI Description This KPI quantifies the amount of HO interruption time for data service due to LTE to
UTRAN CSFB procedure.
The data interruption time measures the elapsed time between last data user plane packet
received or sent by UE from the source LTE eNB (approximately when receiving RRC
Connection Release with Redirection IE from source LTE eNB) and 1st data user plane
packet can be received/sent by the UE from/to the target UMTS NodeB.
ALU Public Target
ALU KPI Comments This KPI is specified for AT&T contract.

This KPI assumes using basic redirection and the following:
RRC connection release: 50ms
Tune to GERAN cell: 150ms
Read MIB &SIB1/3/5/7: 1380ms
UTRAN RRC Connection Setup: 750ms
NAS/E2E procedure (mobile to landline): 2280ms
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, UMTS NodeB, UMTS RNC, Air Interface, SGW, MSC, BH, eNB, PGW, SGSN
Application
Duplex Method

Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference
SE Review Status
Test Consideration
Test Notes
Test Owner
Test Reference
Test Review Status
Test Plan
849
850
851

ALU KPI Name Voice Call Setup Time for CSFB to GERAN using CCO with NACC
ALU KPI Type IRAT
voice call setup for CSFB to GERAN using CCO with NACC.
This voice call setup time is the duration between sending an Extended Service Request
from the UE to the eNB and when the CS call is successfully established at GERAN.
ALU Internal Target No Load: 4760 to 6920 msec (depending on the actual GERAN cell measurement time by
the UE while still connected to the LTE system). (Average)
ALU Public Target
ALU Measurement Other (specify below)

Method Using test equipment to measure the time difference between sending an Extended
Service Request from the UE to the eNB and when the CS call is successfully established
at GERAN.
ALU KPI Comments The target number specified above doesn’t include RRC connection setup time which is ~
100ms.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, GERAN BSS, Air Interface, SGW, MSC, eNB, PGW, BH
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference Refer to next requirement for NE allocations.
SE Review Status
Test Consideration
Test Notes The GERAN cell measurement time by the UE while still connected to the LTE system is
highly variable (min: 480 msec; max: 2640 msec)
Test Owner
Test Reference
Test Plan
853
854
855

ALU KPI Name Voice Call Setup Time for CSFB to GERAN using Redirection
ALU KPI Type IRAT
voice call setup for CSFB to GERAN using blind redirection.
The CSFB to UTRAN using blind redirection setup time is the duration between sending
an Extended Service Request at the UE to the NB and when the CS call is successfully
established at GERAN (after Routing Area Update or Combined RA/LA Update procedure
completion).
ALU Internal Target No Load: 6630ms (Average)
ALU Public Target
ALU Measurement Other (specify below) Using test equipment to measure the time difference between
sending an Extended Service Request at the UE to the NB and when the CS call is
Method successfully established at GERAN (after Routing Area Update or Combined RA/LA
Update procedure completion).
ALU KPI Comments The blind redirection doesn't perform the CCO procedure.
This KPI doesn't include the optional Measurement Report Solicitation.
The target number specified above doesn't include RRC connection setup time which is ~
100ms.
Critical
Dashboard
LE1 KPI ID
Validator
Impacted Entities UE, MME, GERAN BSS, Air Interface, SGW, MSC, eNB, PGW, BH
Application
Duplex Method
Solution

Level
Customer Viewable
SE Conditions
SE Owner
Test Consideration
Test Notes
Test Owner
Test Reference
Test Plan
857
858
859

ALU KPI Name Voice Call Setup Preparation Time for CSFB to 1xRTT by idle Dual-Rx UE, delay Optimized
ALU KPI Type IRAT
ALU KPI Scope RAN
ALU KPI This KPI quantifies the amount of time contributed by the LTE network to successfully
Description perform a voice call setup preparation for Dual-Rx UE 1xCSFB where
Enb::idle1xCsfbForDualRxUE is set to ‘Optimized-for-1xCSFB-KPIs’.
The Voice Call Setup preparation time for CSFB to 1xRTT is the duration between sending
an Extended Service Request (with CSFB indicator) at the UE to the eNB and when the
RRC Connection Release message for the CSFB is sent to the UE.
ALU Internal No Load: 50ms; Typical Load: 65ms; Full Load: 75ms.
Target
ALU Public
Target
ALU PCMD method: The time difference between DRxCSFBto1xRttRrcRlsTime and

Measurement rrcConnectionSetupCompleteTime. The former is pegged pegged when eNB sends RRC
CONNECTION RELEASE to the UE due to CSFB; the latter is pegged when RRC
Method Connection Setup Complete is received from UE. The difference is LTE's contribution to
1xCSFB call setup latency.
ALU KPI When Enb::idle1xCsfbForDualRxUE is set to ‘Optimized-for-1xCSFB-KPIs’, eNB skips up to

Comments 3 round trip messages between eNB and UE to minimize 1xCSFB call setup latency:
- UE Capability Enquiry (and response);
- Secure Mode Command (and response);
- RRC Connection Reconfiguration (and response).
And eNB also skips Initial Context Setup Response to MME.
VzW indicated that a UE vendor of Single-Rx UEs may also make use of the 3GPP
procedure defined for Dual-Rx UE to do 1xCSFB. A PCMD field isUeCdmaDualRx indicates
whether the UE requesting 1xCSFB is a Dual-Rx UE or Single-Rx UE.
Critical Yes
Dashboard
LE1 KPI ID
Validator
Impacted UE, MME, BH, Air Interface, eNB

Entities
Application
Duplex Method FDD
Solution eNB
Level Cluster
Customer No
Viewable
SE Conditions
SE Owner Jin Wang
SE Review Approved
Status
Test
Consideration
Test Notes
Test Owner
Test Reference

Status
Test Plan
861
862
863

ALU KPI Name Voice Call Setup Preparation Time for CSFB to 1xRTT by idle Dual-Rx UE, delay Not
Optimized
ALU KPI Type IRAT
ALU KPI Scope RAN
ALU KPI This KPI quantifies the amount of time contributed by the LTE network to successfully
Description perform a voice call setup preparation for Dual-Rx UE 1xCSFB where
Enb::idle1xCsfbForDualRxUE is set to ‘Not-Optimized-for-1xCSFB-KPIs’.
The Voice Call Setup preparation time for CSFB to 1xRTT is the duration between sending
an Extended Service Request (with CSFB indicator) at the UE to the eNB and when the RRC
Connection Release message for the CSFB is sent to the UE.
ALU Internal No Load: 65ms; Typical Load: 85ms; Full Load: 105ms.
Target
ALU Public
Target
ALU PCMD method: The time difference between DRxCSFBto1xRttRrcRlsTime and

Measurement rrcConnectionSetupCompleteTime. The former is pegged pegged when eNB sends RRC
CONNECTION RELEASE to the UE due to CSFB; the latter is pegged when RRC
Method Connection Setup Complete is received from UE. The difference is LTE's contribution to
1xCSFB call setup latency.
ALU KPI When Enb::idle1xCsfbForDualRxUE is set to ‘Not-Optimized-for-1xCSFB-KPIs’, eNB does

Comments not skip the following 3 round trip messages between eNB and UE:
- UE Capability Enquiry (and response);
- Secure Mode Command (and response);
- RRC Connection Reconfiguration (and response).
And eNB also sends Initial Context Setup Response to MME.
VzW indicated that a UE vendor of Single-Rx UEs may also make use of the 3GPP
procedure defined for Dual-Rx UE to do 1xCSFB. A PCMD field isUeCdmaDualRx indicates
whether the UE requesting 1xCSFB is a Dual-Rx UE or Single-Rx UE.
Critical Yes
Dashboard
LE1 KPI ID
Validator

Impacted UE, MME, BH, Air Interface, eNB

Entities
Application
Duplex Method FDD
Solution eNB
Level Cluster
Customer No
Viewable
SE Conditions
SE Owner Jin Wang
SE Review Approved
Status
Test
Consideration
Test Notes
Test Owner
Test Reference

Status
Test Plan
865
866
867

ALU KPI Name Voice Call Interruption time for SRVCC HO to UTRAN
ALU KPI Type IRAT
ALU KPI Description The elapsed time between the instant the UE receives the last HARQ of the last PHY
VOIP packet from the source eNB and the instant the UE receives the 1st voice frame
from the target UMTS NodeB.
ALU Public Target
Start: the last HARQ Acknowledged VoIP packet received from the source eNB
Method End: the first voice frame received from the target UMTS NodeB
ALU KPI Comments
Critical No
Dashboard
LE1 KPI ID
Validator Mohammad Zarrabizadeh
Application
Duplex Method FDD
Solution E2E
Level Cluster

SE Conditions
SE Owner
SE Reference
SE Review Status

Test Notes This KPI target for SRVCC assumes that the IMS network elements are in the home
network and the MGCF and Media Gateway are colocated with the MSC.
For eSRVCC, the same target will apply irrespective of the location of the IMS network
elements - locally in home network or not.
Test Owner
Test Reference
Test Review Status
Test Plan
869
870
871

ALU KPI Name Outgoing LTE to UMTS HO Success Rate
ALU KPI Type IRAT
ALU KPI Description From a specific eNB, the number of directed inter-RAT HOs to UMTS that successfully
complete.
ALU Public Target
ALU Measurement Other (specify below) Active test using LTE/UMTS capable mobiles.
Method
ALU KPI Comments This KPI corresponds to MOB03 in AT&T Attachment F2.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference

Test Notes There is no measurement or PCMD available to verify this KPI.
Test Owner
Test Reference
Test Plan
873
874
875

ALU KPI Name Outgoing LTE to GSM HO Success Rate
ALU KPI Type IRAT
ALU KPI Description This KPI represents the percentage of directed inter-RAT HOs to GSM that successfully
completed
ALU Public Target
ALU Measurement Other (specify below) Active test using LTE/GSM capable mobiles.
Method
ALU KPI Comments This KPI corresponds to MOB04 in AT&T Attachment F2.
Critical
Dashboard
LE1 KPI ID
Validator
Application
Duplex Method
Solution
Level
Customer Viewable
SE Conditions
SE Owner
SE Reference

Test Notes There is no measurement or PCMD available to verify this KPI.
Test Owner
Test Reference
Test Plan
877

878 References
879
880 [R1] FRS 92643 LTE End-to-End Commercial KPIs (https://wcdma-ll.app.alcatel-
881 lucent.com/livelink/livelink.exe/60484738/FRS_92643_-_LTE_End-to-
882 End_Commercial_KPI%28s%29_V0_7.doc?func=doc.fetch&nodeId=60484738&viewType=1)
883 [R2] FTS eNB Objectives for LA3.0 (https://wcdma-ll.app.alcatel-

884 lucent.com/livelink/livelink.exe/58435900/FTS_L109433_rfa_r3.doc?func=doc.fetch&nodeId=584359
885 00&viewType=1)
886 [R3] LTE E2E Traffic Models for LE6.0 – FDD Generic:
887 https://wcdma-ll.app.alcatel-
888 lucent.com/livelink/livelink.exe?func=ll&objId=65727904&objAction=browse&viewType=1
889
890 [R4] SSD-7327 V4.0: Mobility Management Entity System Specification Document
891 (http://mobility.web.alcatel-lucent.com/~apxlib/cgi-bin/srchdoc.cgi?entry=d51855)
892 [R5] LTE Core End-to-End Performance KPIs for LE1.0 (http://nwswww.ih.lucent.com/~apxlib/cgi-
893 bin/viewpdf.cgi?d49835)
894 [R6] FTS 026343: Support of Counter Analysis in NPO (https://wcdma-ll.app.alcatel-

895 lucent.com/livelink/livelink.exe?func=ll&objId=54285918&objAction=browse&viewType=1)
896 [R7] FTS 027915: NPO Support for MME Counters (https://wcdma-ll.app.alcatel-
898 [R8] FDD-7466 VoLGA Solution with GSM/UMTS Interworking

899 (http://mobility.ih.lucent.com/~slaha/CSoPS/fdd.html)
900 [R9] FTS eNB KPI Objectives for LA3.0 (https://wcdma-ll.app.alcatel-

901 lucent.com/livelink/livelink.exe?func=ll&objId=57607605&objAction=browse)
902 [R10] LTE E2E Network Performance KPI Specification for LE2.0 and LE2.1 (http://cdms.ca.alcatel-
903 lucent.com/livelink/livelink/19198642/LTE_E2E_Network_Performance_KPI_Specification_for_LE2.0
904 _and_LE2.1?func=doc.Fetch&nodeid=19198642)
905 [R11] MME OA&M Functionality System Specification Document (http://nwswww.ih.lucent.com/~apxlib/cgi-

906 bin/srchdoc.cgi?entry=d52350)
907 [R12] EUTRAN RRM DRA&PS - Uplink Scheduler – SRS (https://wcdma-ll.app.alcatel-

908 lucent.com/livelink/livelink.exe?func=ll&objId=54791290&objAction=browse&sort=name&viewType=
909 1)
910 [R13] LTE RRM DRA&PS and MAC - DL Scheduler – SRS (https://wcdma-ll.app.alcatel-
911 lucent.com/livelink/livelink.exe?func=ll&objId=54358822&objAction=browse)
912 [R14] LA11D1E08_Database Release Note (https://wcdma-ll.app.alcatel-

913 lucent.com/livelink/livelink.exe/57122586/LA1_1_MIM3.5_Database_Release_Note_Ed08.doc?func=
914 doc.fetch&nodeId=57122586&viewType=1)
915 [R15] FTS for FRS-92643 LTE End-to-End Commercial KPI(s) (https://wcdma-ll.app.alcatel-
917 1)
918 [R16] eUTRAN Mobility Control Plane SRS ed02.01 (https://wcdma-ll.app.alcatel-

920 [R17] ALU LTE Basic Call Flows v0.1 (https://sps.na.alcatel-
921 lucent.com/personal/jlichter/LTE_E2E/Shared%20Documents/Commercial%20LTE%20Call%20Flow
922 s/LE2.0%20Commercial%20Call%20Flow/ALU%20LTE%20Basic%20Call%20Flows%20v1.doc)
923 [R18] LTE E2E Network Performance KPI and NE Capacity Specification for LE5.x
924 (https://cdms.app.alcatel-
925 lucent.com/livelink/livelink?func=ll&objId=19493525&objAction=browse&viewType=1) (document is
926 divided into 2 parts)
927 [R19] FTS for FRS115233 eNB SW Capacity Configuration in LA5.0 (https://wcdma-ll.app.alcatel-
929 (Note: the above FTS covers capacity information for both LA5 and LA6)
930 [R20] FRS115114 LA4.0 eNB SW Capacity Improvements as appeared in CPDR
931 (The above feature provides alignment for 20MHz 3-sector eNB SW Capacity based on LA3.0 eNB
932 SW capacity for 10MHz (i.e. 167 AU(s)/cell with 4.5 simultaneous bearers per connection in average)
933 [R21] LTE Phase 1 Call Flows for VzW v1.02 (https://sps.na.alcatel-
934 lucent.com/personal/jlichter/LTE_E2E/Shared%20Documents/Commercial%20LTE%20Call%20Flow
935 s/VZ%20LE2.0%20-%20Commercial/Vz%20LTE%20E2E%20call%20flows.zip)
936 [R22] eNB KPI Objective for LA3.0 (https://wcdma-ll.app.alcatel-
937 lucent.com/livelink/livelink.exe/60484745/FRS_109433_-
938 _eNB_KPI_Objectives_for_LA3.0_v1.1.doc?func=doc.fetch&nodeId=60484745&viewType=1)
939 [R23] VzW FSA KPI Exit Criteria (http://sae-tis.web.alcatel-lucent.com/lte/kpi/LE2.0_exit_criteria_KPIs.pdf)
940 [R24] AT&T KPI Requirements: Exhibit F2: E-UTRAN KPI Requirements (http://sae-tis.web.alcatel-
941 lucent.com/lte/kpi/ATT-KPI-mapping%20v0.xls)
942 [R25] TS36.101 Release 9 V9.5.0 (2010-10) – E-URTA User Equipment (UE) radio transmission and
943 reception (http://www.3gpp.org/ftp/Specs/html-info/36101.htm)
944 [R26] TS36.211 Release 9 V9.1.0 (2010-03) – E-URTA Physical Channels and Modulation
945 (http://www.3gpp.org/ftp/Specs/html-info/36211.htm)
946 [R27] TS36.213 Release 9 V9.3.0 (2010-09) – E-URTA Physical layer procedures
948 [R28] TS36.306 Release 9 V9.3.0 (2010-10) – E-UTRA User Equipment (UE) radio access capabilities
950 [R29] LSTI Friendly Customer Trials – Common Configurations and Methods (https://all1.na.alcatel-
951 lucent.com/carrier/lte/tis/sharearea/releaseintroduction/KPI/KPI%20feedback%20from%20field/LSTI
952 %20feedbacks/20090930_LSTI_Trial_Common_Test_Information_v4-10.ppt)
953 [R30] LSTI Latency Test Sheet

954 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/Latency%20test%20sheet_v1_providedByJerom
955 e.doc)
956 [R31] Mobility within NGMN System: Mobility within LTE Test Sheet
957 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/2-06-
958 5_20090910_LSTI%20Trial%20Mobility%20within%20LTE_v1-1.doc)
959 [R32] LSTI PoC L1 Peak rates v5 (https://bscw.verkstad.net/bscw/bscw.cgi/88987)

960 [R33] LSTI Throughput at Cell Edge Test Sheet
961 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/20090327_LSTI%20Trial%20Throughput%20at
962 %20Cell%20Edge%20test%20sheet_v4.doc)
963 [R34] LSTI State Transition Test Sheet

964 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/20090618_LSTI%20Trial%20State%20Transition
965 %20-TC%20description.doc)
966 [R35] LSTI Coexistence of VoIP with other applications

967 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/LSTI%20Trial%20Coexistence%20of%20VoIP_w
968 ith%20other%20applications_v1.2.doc)
969 [R36] LSTI Service continuity of RT/NRT session in Mobile use
970 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/LSTI%20Trial%20Mobility%20Service%20contin
971 uity%20v2.0_TelecomItalia.doc)
972 [R37] TS36.133 V9.5.0 E-UTRA Requirements for support of radio resource management
974 [R38] TS23.203 V9.6.0 Policy and charging control architecture (http://www.3gpp.org/ftp/Specs/html-
975 info/23203.htm)
976 [R39] Requirements for feature L115113: LA4.0 KPI Targets (search L115113 from CPDR:
977 http://wngpjm.web.lucent.com/cpdr/)
978 [R40] LSTI VoIP Call Capacity Test Sheet

979 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/LSTI%20Trial%20VOIP%20call%20capacity%20
980 test_W13.doc)
981 [R41] LSTI Basic QoS: 2.09.1 Verification of Static QoS Profiles
983 01_2.09.1%20Static%20QoS%20Profiles%20v1_0.doc)
984 [R42] LSTI Throughput Measurement Test Sheet (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/2-02-

985 2_20090910_LSTI%20Trial%20Average%20Throughput%20test%20sheet_V5-1.doc)
986 [R43] LSTI Peak Rate Test Sheet

987 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/20090316_LSTI%20Trial%20Peak%20Rate%20t
988 est%20sheet_v4.doc)
989 [R44] LSTI Cell Throughput Test Sheet (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/2-03-

990 1_20090910_LSTI%20Trial%20Cell%20Throughput%20test%20sheet_v1-1.doc)
991 [R45] LSTI Path Loss and System Coverage Performance Test Sheet
993 5_20090910_LSTI%20Trial%20Path%20loss%20and%20system%20coverage%20performance%20
994 test%20sheet_v4-1.doc)
995 [R46] TR25.912 Feasibility Study for evolved UTRA and URTAN (http://www.3gpp.org/ftp/Specs/html-
996 info/25912.htm)
997 [R47] LSTI Packet Loss in Mobility Use

998 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/LSTI%20Trial%20Mobility%20Packet%20Loss%
999 20Rate%20v2.0_TelecomItalia.doc)
1000 [R48] LSTI VoIP Speech Quality

1001 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/LSTI%20Trial%20VoIP%20Speech%20Quality_v
1002 1 2.doc)

1003 [R49] LSTI Email Services (POP3 & SMTP) Measurement Test Sheet
1004 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/20090315_2.8.6
1005 Email%20services%20v0_1.doc]
1006 [R50] LSTI HTTP Downloads Measurement Test Sheet

1007 (http://nwswww.wh.lucent.com/~perf_dat/LTE/LSTI/20090529_2.8.5%20HTTP%20Downloads%20v1
1008 _0.doc)
1009 [R51] TS32.450 v9.4.0 Performance Measurements E-UTRAN (http://www.3gpp.org/ftp/Specs/html-
1010 info/32450.htm)
1011 [R52] TR25.913 Requirements for E-UTRA and E-UTRAN (http://www.3gpp.org/ftp/Specs/html-

1012 info/25913.htm)
1013 [R53] ITU-T J.144 (http://www.itu.int/itudoc/itu-t/aap/sg9aap/history/j144/index.html)
1014 [R54] FTS for FRS115113 LA4.0 KPI Targets (https://wcdma-ll.app.alcatel-

1016 1)
1017 [R55] LTE_E2E_Traffic_Model_LE7.1_VzW_Small_Cell_v0.1.doc (https://wcdma-ll.app.alcatel-

1019

1020 Appendix A: LSTI KPIs

1021 The following KPIs are specified in the “LSTI Friendly Customer Trials Common Configurations and
1022 Methods” v4.10.0 [R29]. The targets for these KPIs are spread across multiple documents and test sheets.
1023
KPI Definition Reference
VoIP call-set up Success Amount of successfully established calls at the first LSTI VoIP call
Rate attempt divided by total amount of unique initiated capacity Test Sheet
call requests / attempts [R40]
VoIP call Success Rate The percentage of successfully established calls at LSTI VoIP call
the first attempt, maintained for 2 minutes, capacity Test Sheet
presenting a correct level of voice quality and [R40]
correctly released
VoIP Calls/cell/MHz with a Amount of calls/cell/MHz meeting the agreed

minimum agreed MOS minimum MOS
VoIP call setup time MMC:
Call Setup signaling latency time:
Start Timer: Cell Selection / Stop Timer: SIP

180 Ringing
Total Call Setup latency time:

ACK
MOC->PSTN

180 Ringing

ACK
MTC (PSTN->MTC)
Start Timer: IAM / Stop Timer:

ACM/CPG
Start Timer: IAM / Stop Timer: ANM
QoS success rate per user in Binary Pass / Fail LSTI Basic QoS:
overloaded cell (QoS Status 2.09.1 Verification
in Overloaded cell) of Static QoS
Profiles [R42]
Transition time Idle -> Active Idle -> Active TR25.913 [R52]


state
Start Timer: RACH Preamble LSTI State
Transition Test
Stop Timer: RRC Reconfiguration Complete Sheet [R34]
Active -> Sleep
Start Timer: RRC Reconfiguration
Stop Timer: RRC Reconfiguration Complete
Sleep -> Active in DL
Start Timer: Paging
Sleep -> Active in UL
Start Timer: RACH Preamble
Paging Success Time:
Start Timer: Paging
Stop Timer: RRC Connection Setup Complete
Throughput As the test case defines ONLY full buffers KPI can TS 32.450 section
be simplified compared to 3GPP TS 32.450: 6.3.1 [R51]
TCP: LSTI FTP

Throughput
Test duration (Seconds): Stop Time - Start Time Measurement Test
Sheet [R42]
Start Time: First IP packet containing test
traffic LSTI Peak Rate
Test Sheet [R43]
Stop Time: Last IP packet containing test
traffic
Total amount of Acknowledged Data (Bytes):

Sum of all packet sizes for all IP packets containing
TCP PDU's that have been acknowledged from the
TCP End point between Start and Stop time. (Size
of TCP packet inside containing IP Packet) as
received on UE on Downlink OR on Test Server on
Uplink and acknowledged.
TCP Throughput: Total amount of

Acknowledged Data * 8 / Test Duration
UDP:
Test duration (Seconds): Stop Time - Start

Time
Start Time: First IP packet containing test

traffic
Stop Time: Last IP packet containing test


traffic
Total amount of Data (Bytes): Sum of all packet

sizes for all IP packets between Start and Stop
time. (Size of UDP packet inside containing IP
Packet) as received on UE on Downlink OR on
Test Server on Uplink.
UDP Throughput: Total amount of Data * 8 /

Test Duration
Cell throughput Measure IP throughput for each individual user and LSTI Cell
aggregate for all users in cell for synchronized time Throughput Test
captures Sheet [R44]
Throughput variation during See throughput KPI, sample rate must be high LSTI Path loss and
HO enough to differentiate to variations due to SINR system coverage
and variations due to HO interruption. (It is known performance Test
that SINR is not defined according to 3GPP but Sheet [R46]
consider SINR as a representation of the RF
environment at the point and time).
Cell edge performance See throughput KPI LSTI Throughput at

Cell Edge Test
Sheet [R33]
Handover success/failure HO.ExeSucc / HO.ExeAtt * HO.PrepSuss.QCIQCI=x / LSTI Mobility within

rate HO.PrepAtt.QCIQCI=x * 100 LTE Test Sheet
[R31]
Handover interruption time in Start Timer : Handover Command [RRC TS36.133 [R37]
UP during HO Connection Reconfiguration] OR Last PDU
received on OLD Cell TR25.912 [R46]
Stop Timer : First DL PDU received on Target Cell LSTI Mobility within
LTE Test Sheet
[R31]
Interruption time on MAC DL MAC Interruption TS36.133 [R37]

layer during HO
Start timer: Handover Command [RRC LSTI Mobility within
Connection Reconfiguration] LTE Test Sheet
[R31]
Stop timer: Random Access Response (MAC:
RAR)
UL MAC Interruption
Start timer: Handover Command [RRC

Connection Reconfiguration]
Stop timer: RLC Ack received by UE from

Target Cell, to acknowledge receipt of RRC
Connection Reconfiguration Complete
Intra LTE HO Interruption See Interruption on MAC layer during HO KPI

time for Signaling
Latency E2E Latency (EPC Latency) : TS 32.450 section

6.3.2 [R51]
Timer Start: ICMP ECHO Request Message OR

Scheduling Request
LSTI Latency Test
Timer Stop: ICMP ECHO Response Sheet [R30]
Core Latency :
Start Timer: On S1-U ICMP Echo Request
Stop Timer: On S1-U ICMP Echo Response
RAN Latency:
EPC Latency - Core Latency
Packet Loss Rate Packet Loss Rate (PLR) = (number of sent IP LSTI Packet Loss in
packets- number of IP received packets) / number Mobile use [R47]
of sent IP packets * 100 [%]
LSTI VoIP Speech
Quality [R48]
Download/Upload time Start Timer: First TCP packet of download/upload LSTI Email services
received (POP3 & SMTP)
Measurement Test
Stop Timer: Last TCP packet of download/upload Sheet [R49]
received
LSTI HTTP
For Download measure on UE side. For Upload Downloads
measure on file server location. Measurement Test
Sheet [R50]
Jitter Max, Min and Average Jitter on RTP/UDP/IP traffic LSTI VoIP Speech
compared to original frame interspacing (20ms). Quality [R48]
Voice Quality, MOS E-Model MOS for Transport LSTI Coexistence

of VoIP with other
PESQ MOS for End2End Quality applications Test
Sheet [R35]
Codec to be decided, bit rate to be decided
Video Quality Audio PESQ MOS ITU-T J.144 [R53]
Video ITU J.144 or other relevant video quality

method aligned with ITU intent
E-RAB set-up success rate Successful established E-RABs compared with 32.450 section
total number of attempts for the different parts of 6.1.1 [R51]
the E-RAB establishment
Planning time per BS Start Timer: First activity related to planning of

the Site
Stop Timer: End of successful planning of the

Site including the loading of the parameters into
the Network Management System
1024

1025 Appendix B: Glossary

rd
1026 3GPP 3 Generation Partnership Project
1027 ALU Alcatel-Lucent
1028 ARD Architecture Requirements Document
1029 ASCII American Standard Code for Information Interchange
1030 ASN.1 Abstract Syntax Notation One
1031 AT Access Terminal

1032 AWGN Additive White Gaussian Noise
1033 BH Backhaul
1034 BIST Built In Self Test
1035 BLST Board Level Self Test
1036 BSHSE & AT & PEC Base Station Hardware Systems Engineering and Advanced Technologies and
1037 Performance Expertise
1038 BTS Base Transceiver Station
1039 CallP Call Processing
1040 CCITT Consultative Committee for International Telegraphy and Telephony

1041 CCO Cell Change Order
1042 CDMA Code Division Multiple Access
1043 CDF Cumulative distribution function
1044 CID Component Interface Definition
1045 CLI Command Line Interface
1046 CM Configuration Management
1047 CPDR Common Project Data Repository
1048 CPE Customer Premises Equipment
1049 CPRI Common Public Radio Interface
1050 CPU Central Processing Unit
1051 CRC Cyclic Redundancy Check
1052 CB Controller Board
1053 D1U Digital 1U Unit
1054 D2U Digital 2U Unit
1055 DBU Digital Base Unit
1056 DCN Data Communication Network
1057 DE Development Estimate
1058 DHCP Dynamic Host Control Protocol

1059 DL Downlink
1060 DM Data Management
1061 DN Distinguished Name
1062 DNS Domain Name Server
1063 DPM Department Project Manager
1064 DPRAM Dual Ported RAM
1065 DS Dynamic Scheduling
1066 DSL Digital Subscriber Line
1067 DSP Digital Signal Processor
1068 EEPROM Electrically Erasable Programmable ROM
1069 E-LAN Ethernet Multipoint-to-Multipoint Virtual Connection service
1070 E-Line Ethernet Point-to-Point Virtual Connection service
1071 eNB evolved NodeB BTS for LTE
1072 FDD Feature Definition Document
1073 FFS For Further Study
1074 FM Fault Management
1075 FN Fault Notification
1076 FPGA Field Programmable Gate Array
1077 FRS Feature Requirements Specification
1078 FTP File Transfer Protocol
1079 FTS Feature Technical Specification
1080 FW Firmware
1081 GigE Gigabit Ethernet
1082 GPS Global Positioning System
1083 GPRS General Packet Radio Service
1084 GTP GPRS Tunneling Protocol
1085 HDLC High-level Data Link Control
1086 HTTP Hyper Text Transport Protocol
1087 HTTPS Hyper Text Transfer Protocol Secure
1088 HW Hardware
1089 I&C Installation and Commissioning
1090 I/F Interface
1091 ILCP Initial Link Configuration Parameter

1092 IMEI International Mobile Equipment Identifier
1093 IMSI International Mobile Subscriber Identification
1094 IoT Interference Over Thermal
1095 ITU International Telecommunications Union
1096 IP Internet Protocol
1097 IRM International Roaming MIN
1098 JTAG Joint Test Action Group
1099 KPI Key Performance Indicator
1100 L1 Layer 1
1101 L2 Layer 2
1102 LAN Local Area Network
1103 LED Light Emitting Diode
1104 LMT Local Maintenance Terminal
1105 LNA Low Noise Amplifier
1106 LO Logical Object
1107 LTE Long Term Evolution
1108 LVDS Low Voltage Differential Signaling
1109 MAC Media Access Control
1110 MCA MAC Control Application
1111 MCC Metro Core Connect
1112 MHz MegaHertz
1113 MIB Management Information Base
1114 MIM Management Information Model
1115 MIMO Multiple Input Multiple Output
1116 MIN Mobile Identification Number
1117 MLS Multi-Layer Switch
1118 MME Mobility Management Entity
1119 MMI Man Machine Interface
1120 MO Managed Object
1121 MSPP Multi-Service Provider Platform
1122 MTU Maximum Transmission Unit
1123 MU Modem Unit

1124 NACC Network Assisted Cell Change

1125 NAPT Network Address Port Translation
1126 NAT Network Address Translation
1127 NBI North Bound Interface
1128 NE Network Element
1129 NEM Network Element Manager
1130 NETCONF Network Configuration Protocol
1131 NMEA National Marine Electronics Association
1132 NPO Network Performance Optimizer
1133 NPU Network Processing Unit
1134 NTP Network Time Protocol
1135 OAM Operations, Administration and Maintenance
1136 OCNS Orthogonal Channel Noise Simulator
1137 OFDM Orthogonal Frequency Division Multiplexing
1138 PA Performance Alarm
1139 PAC Power and Alarm Card
1140 PCMD Per Connection Measurement Data
1141 PCRF Policy and Charging Rules Function
1142 PDN Packet Data Network
1143 PGW PDN Gateway
1144 PHY Physical layer
1145 PKI Public Key Infrastructure
1146 PLM Product Line Management
1147 PM Performance Management
1148 PPM Project and Portfolio Management
1149 PPP Point-to-Point Protocol
1150 PQ Power QUICC Motorola processor
1151 PSA Product and Software Architecture
1152 QSFP Quad Small Form-factor Pluggable
1153 QoS Quality of Service
1154 R&D Research and Development
1155 RAM Random Access Memory
1156 RAN Radio Access Network
1157 RF Radio Frequency

1158 RFC Request For Comment
1159 RFM Radio Frequency Module
1160 RFO Radio Frequency Optimizer
1161 RLC Radio Link Control
1162 RMT Remote Maintenance Terminal
1163 RO Resource object
1164 ROCM Reverse Optical CPRI Module
1165 ROM Read Only Memory
1166 RRC Radio Resource Control
1167 RRH Remote Radio Head
1168 RTU Right To Use
1169 Rx Receive
1170 S1 Interface from eNodeB to MME and SGW
1171 S1-MME S1 control plane interface between eNodeB and MME
1172 S1-U S1 User plane interface between eNodeB and SGW
1173 SAE 3GPP System Architecture Evolution
1174 SAM Service Aware Manager
1175 SEG Security Gateway
1176 SCN State Change Notification
1177 SCTP Stream Control Transport Protocol
1178 SEA Systems Engineering and Architecture
1179 SFP Small Form-factor Pluggable
1180 SFTP Secure File Transfer Protocol
1181 SGW Serving Gateway
1182 SID System Interface Definition
1183 SIMO Single Input Multiple Output
1184 SISO Single Input Single Output
1185 SFS Subsystem Functional Specification
1186 SMI Serial Management Interface
1187 SNMP Simple Network Management Protocol
1188 SOAP Simple Object Access Protocol
1189 SPS Semi-Persistent Scheduling
1190 SRB Signaling Radio Bearer

1191 SRIO Serial Read Input Output
1192 SRS System Requirements Specification
1193 SS Subscriber Station
1194 SSH Secure SHell
1195 S-TMSI Serving Temporary Mobile Subscriber Identifier
1196 SW Software
1197 SWM Software Management
1198 TAI Time Atomic International
1199 TBD To Be Determined
1200 TC Transmission Convergence Adaptor
1201 TCP Transmission Control Protocol
1202 TDD Time Division Duplex
1203 TE Test Estimate
1204 TIPM Technology introduction Program Management
1205 TLS Transport Layer Security
1206 TMN Telecommunication Management Network
1207 TPL Technical Project Lead
1208 TRB Traffic Radio Bearer
1209 TRDU TRansceiver Duplexer Unit
1210 Tx Transmit
1211 UDP User Datagram Protocol
1212 UE User Equipment
1213 UL Uplink
1214 UMTS Universal Mobile Telecommunication System
1215 UPE User Plane Entity
1216 UPS Unified Platform Services
1217 URL Uniform Resource Locator
1218 USM User-Based Security Model
1219 USOD Usage State On Demand
1220 UTC Universal Time Coordinated
1221 VACM View-Based Access Control Model
1222 VLAN Virtual Local Area Network
1223 VoIP Voice Over IP

1224 VP Virtual Path
1225 VSWR Voltage Standing Wave Ratio
1226 W-CDMA Wideband Code Division Multiple Access
1227 WIMAX Worldwide Interoperability for Microwave Access
1228 WPS Wireless Provisioning System
1229 X2 Interface between neighboring eNodeBs
1230 X2-C X2 Control plane interface
1231 X2-U X2 User plane interface
1232 XML eXtensible Mark-up Language
1233 XMS eXtended Management System
1234


All KPIs - Except Thruput - For LE6.0 201201030 V1.0 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

All KPIs - Except Thruput - For LE6.0 201201030 V1.0 PDF

Uploaded by

Copyright:

Available Formats

LE6.0 E2E and RAN KPIs: Part 1 V1.

25 Pengfei (Peter) Zhu

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 1

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 2

50 2 Customer network Configurations ........................................................................ 8

55 3 End-to-End LTE Specification Methodologies .................................................... 10

63 4 End-to-end KPI and Requirement ........................................................................ 19

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 3

69 4.2.2 End-to-end Network Requirement ..........................................................................48

85 References ................................................................................................................. 210

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 4

105 1.2 Scope

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 5

140 1.3 Audience

156 1.4 Feature Dependency

160 1.5 Open Issues

164 - LTE to eHRPD enhanced non-optimized redirection success rate -

165 - CSFB to UTRAN PSHO success rate

166 - CSFB to UTRAN redirection success rate

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 6

176 5. LTE to UMTS HO interruption time (enhanced redirection) should be addressed.

177 6. LTE to GERAN HO interruption time (enhanced redirection) should be addressed.

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 7

186 2 Customer network Configurations

187 2.1 Network Configuration and Performance Models

eNB eNB eNB eNB

195 Figure-2.1.1-1: LTE End-to-end Reference Network Architecture

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 8

213 2.2 E2E LTE Network Performance Model

220 2.2.1 E2E Packet Transmission Latency Model

222 E 2 E _ Delay = ∑ NE _ Delay (i ) + ∑ link _ Delay ( j ) .

229 Requirements are given for various statistical points:

230 • Average value

236 Other percentage may also be adopted

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 9

239 3 End-to-End LTE Specification Methodologies

242 • FRS requirements from PLM [R1] [R22] [R39]

243 • Customer contractual agreements [R23] [R24]

245 • LTE standard (3GPP TS) [R37] [R38] [R52]

246 • NGMN test requirement [R31]

247 • ALU system simulation and analysis results

248 • ALU testing data

249 • Network element specifications and performance data [R4]

251 3.2 Structure of the Specifications and Requirements

255 • User Plane Latency

256 • Control Plane Latency

259 • Quality of Experience

260 • Network Performance

261 • Product Performance

268 3.3 Traffic Model, Loading and Assumption

278 3.3.1 Traffic Model

KPI Type Traffic Model Note

FDD VoIP KPIs M2 Refer to Table 7 in [R3] for

FDD All Other KPIs M2-C See above

287 3.3.2 Loading

295 3.3.2.1 No Load: specified for baseline lab testing

306 Table 3.3.2-2

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 12

322 Table 3.3.2-3

10/30/2012 -- Alcatel-Lucent PROPRIETARY -- Page No. 13

Near Cell (NC) 21 13 90

Mid Cell (MC) 11 9 110

Cell Edge (CE) 2 5 130