LTE Counters and KPIs

LTE Counters and KPI • Hugo Ahumada Navarro

1 13/12/2015 Confidential

© Nokia 2014

Content

• Standard Definitions • Performance KPI Details • Driver test KPI • KPI Analysis


© Nokia 2014

Standard Definitions Reference Document

3GPP TS 32.450 • 3rd Generation Partnership Project • Technical Specification Group Services and System Aspects • Telecommunication management

• Key Performance Indicators (KPI) for Evolved Universal Terrestrial Radio Access Network • (E-UTRAN)


© Nokia 2014

Standard Definitions Reference Document

• The quality of network performance is mainly evaluated by KPI (Key Performance Index) - Drive Test KPI/ Stationary Test: Some KPIs should be attained by drive test, such as such as coverage KPI and latency KPI, measurement results are coming from driver test tools

- Performance

Measurement KPI: Most of KPIs are attained by this

approach, such as RRC success Rate, HHO success rate,eg, these KPIs are coming from eNodeB performance statistic.


© Nokia 2014

Standard Definitions Reference Document • The traffic measurement data and drive test data are the objective basis of the network optimization, while the human perception is the subjective basis. It is necessary to trace and analyze signalling messages to locate problems before these problems are solved. It is obvious that the traffic measurement data provide a very important method to analyze the network performance. Especially when there is traffic in the network, the traffic measurement data provide important references and guide for the network optimization. The integrity and accuracy of the measurement items and the convenience of operations will directly affect the efficiency of network optimization. Meanwhile, the quality of measurement items is also a very important factor to measure the effect of network optimization.


© Nokia 2014

Standard Definitions Reference Document • On the other hand, network operators set much store by the traffic measurement data. The boss of network operators usually learns and judges the running status of networks according to the visual data obtained from traffic measurement. These visual traffic measurement data also provide an important basis for the future network capacity expansion.


© Nokia 2014

Content

• Standard Definitions - KPI Overview - KPI Definitions Template

- E-UTRAN KPI Definitions


© Nokia 2014

Standard Definitions KPI Overview

The following KPI categories are covered by the present document: • Accessibility • Retainability • Integrity • Availability • Mobility


© Nokia 2014

Content




© Nokia 2014

Standard Definitions KPI Definitions Template

• Long name (Mandatory): This field shall contain the long and descriptive name of the KPI.

• Description (Mandatory): This field shall contain the description of the KPI. Within this field it should be given if the KPI is focusing on network or user view. • Logical formula definition (Mandatory): The logical formula should describe what the KPI formula is in logical way. The description of the formula is given in a written textual format without any measurement or counter names. E.g. a success rate KPI‟s logical formula is the successful event divided by all event. 10 13/12/2015 Confidential

© Nokia 2014


• Physical formula definition (Optional): This field should contain the KPI formula description using the 3GPP defined counter names. This field can be used only if the counters needed for the KPI formula is defined in any of the 3GPP TS for performance measurements (TS 32.404 [3], TS 32.405 [4], TS 32.406 [5], TS 32.407 [6], TS 32.408 [7], TS 32.409 [8], TS 52.402 [9], TS 32.425 [10]) • Measurement names used for the KPI (Optional): This section should list the measurement names used for the KPI. This section can be filled out only when the underlying measurements for the KPI formula can be defined, i.e. physical formula definition is available. 11 13/12/2015 Confidential

© Nokia 2014


• KPI Object (mandatory) This section shall describe the object of the KPI. The object of the KPI is one or some of the following: - UTRAN; - GERAN; - CS core; - PS core; - IMS; - E-UTRAN.

• The field can have multiple selection, e.g. for a network level end to end KPI the selection can be UTRAN+PS core network. 12 13/12/2015 Confidential

© Nokia 2014


• KPI category (mandatory): This section contains the classification of the KPI into one of the KPI categories listed in section 4

• Unit of the KPI (mandatory): This section describes the unit of the KPI. The unit can be one of the following: - percentage; - time interval (second or millisecond); - Erlang; - kbit/s.


© Nokia 2014


• Type of the KPI (Mandatory): This section describes the type of the KPI. The KPI type can be one of the following: - MEAN: This KPI is produced to reflect a mean measurement value based on a number of sample results. - RATIO: KPI is produced to reflect the percentage of a specific case occurrence to all the cases. - CUM: This KPI is produced to reflect a cumulative measurement which is always increasing.

• Remark: (Optional): This field is for any further information that is needed for the KPI definition. Here it is proposed to define any additional information that would be needed for the KPI definition; e.g. the definition of a call in UTRAN. 14 13/12/2015 Confidential

© Nokia 2014

Content




© Nokia 2014

Content

• E-UTRAN KPI Definitions - KPI Categories - Services Levels


© Nokia 2014

Content

• KPI Categories - Accessibility - Retainability

- Integrity - Availability - Mobility


© Nokia 2014

Standard Definitions E-UTRAN KPI Definitions: Accessibility

• Accessibility KPIs are used to measure the probability that a user accesses the network and requests services in the given operating conditions. The service provided by the EUTRAN is defined as EPS/E-RABs. (EPS is short for evolved packet system, and E-RAB is short for E-UTRAN radio access bearer). Radio

Resource Control (RRC) connections and System Architecture Evolution (SAE) setups are the main procedures whose performance is measured by accessibility KPIs. 18 13/12/2015 Confidential

© Nokia 2014

Content

• E-UTRAN KPI Definitions - Accessibility - Retainability



© Nokia 2014

Standard Definitions E-UTRAN KPI Definitions: Retainability

• Retainability KPIs indicate the network's capability to retain services requested by a user for a desired duration once the user is connected to the services. Retainability KPIs are important in evaluating whether the system can maintain a certain level of service quality. • Reliability KPIs can be referred to Service Drop Rates or to Transport Error Rates, that is, the ratio between erroneous or lost data units and the overall number of data units sent.


© Nokia 2014

Standard Definitions E-UTRAN KPI Definitions: Retainability • The Service Drop Rates KPIs (i.e. drop rates) can be measured in the field with an FMT (Field Measurement Tool). They represent the ratio between unsuccessful („abnormal‟) terminations of a service request (e.g. network attach, register, service request) to the overall established services. • For certain services, like bearer creation or VoIP call the service drop rate is also related to the duration of the session. This is motivated by the fact that the possibility of network errors, e.g. hand-over failures is higher if the service duration is longer. In this case, the drop ratio is expressed in [1/s] units instead of [%]. • As always-on connectivity is the basic idea for LTE, traditional CDR KPIs may cause abnormal results. CDR per Data Volume has been proposed to solve this problem. 21 13/12/2015 Confidential

© Nokia 2014

Content




© Nokia 2014

Standard Definitions E-UTRAN KPI Definitions: Integrity

• The service integrity KPIs indicate the E-UTRAN impacts on the service quality provided to the end-user. The service integrity KPIs can be calculated for each cell or radio network.

• Throughput KPIs show the data rates that can be provided to the users of a cell under different radio conditions. The location of the UE in the cell and the number of active UEs in that cell will strongly influence the data rate that can be experienced by one user.


© Nokia 2014

Standard Definitions E-UTRAN KPI Definitions: Integrity

• Peak/Average cell throughputs and peak user throughputs are the metrics that characterize the capacity of an LTE network, and the average UL/DL user throughputs along a drive route (i.e. under different radio conditions) represent the end user experience. However, only cell throughput and peak user throughput metrics will be covered in this document.


© Nokia 2014

Content




© Nokia 2014

Standard Definitions E-UTRAN KPI Definitions: Availability

• A cell is available when the eNodeB can provide EPS bearer services. Availability in a cell can be measured when a variety of hardware/software faults occurs in the cell.


© Nokia 2014

Content




© Nokia 2014

Standard Definitions E-UTRAN KPI Definitions: Mobility

• Mobility KPIs are used to evaluate E-UTRAN mobility performance, which is critical to customer experience. Three categories of mobility KPIs are defined based on the following handover types: intrafrequency, inter-frequency, and inter-Radio Access Technology (RAT).


© Nokia 2014

Standard Definitions E-UTRAN KPI Definitions: Mobility

• Mobility KPIs build a group because all of them are related to handover procedures. They could, however, be discussed in the Latency and Accessibility groups as well, because HO-related KPIs are either service interrupt time or success ratio type KPIs. • A successful handover is understood to be any successfully performed make before break procedure and it is marked by an entry in the log, which carries the identifier of the new cell (destination).


© Nokia 2014

Content

• E-UTRAN KPI Definitions - KPI Categories - Services Levels


© Nokia 2014

E-UTRAN KPI Definitions Services Levels

In addition to the different categories, KPIs are also defined for different service levels as per 3GPP 36.300. These are: • Application Services • LTE E2E Network Service • Radio Bearer (RB) Service • IP based LTE Bearer Services: X2, S1, S5/S8 and external


© Nokia 2014


Figure shows the LTE Bearer Service Architecture where the KPIs categories above can be mapped into.


© Nokia 2014


• When it comes to field performance evaluation the most interesting KPIs are the “LTE E2E Network Service” KPIs as they characterize the overall LTE network performance. • Another important group is the Application Service KPIs as they show the user‟s perceived qualityThe of KPIs application services as impacted by the LTE network. of this group are service specific. 33 13/12/2015 Confidential

© Nokia 2014


The services of common interest for mobile network operators and therefore, the ones that can be of interest during an acceptance process are: • Web Browsing (HTTP) • Data Upload / Download (FTP) • Email (POP/SMTP) • Conversational Audio Video (VoIP) 34 13/12/2015 Confidential

© Nokia 2014

Content



© Nokia 2014

Content

• Performance KPI Details - Accessibility - Retainability



© Nokia 2014

Content

• Performance KPI Details - Accessibility • E-RAB Setup Success Rate


© Nokia 2014

Performance KPI Details E-RAB Accessibility - Long name: E-RAB Accessibility. - Description: A KPI that shows probability for an end-user to be provided with an ERAB at request. - Logical formula definition: Probability success rate for E-RABs establishment. Successful attempts compared with total number of attempts for the different parts of the E-RAB establishment. - Physical formula definition


© Nokia 2014

Performance KPI Details E-RAB Accessibility - Measurement names used for the KPI: RRC.ConnEstabAtt. Cause, RRC.ConnEstabSucc.Cause, S1SIG.ConnEstabAtt, S1SIG.ConnEstabSucc, ERAB.EstabInitAttNbr.QCI, ERAB.EstabInitSuccNbr.QCI, ERAB.EstabAddAttNbr.QCI, ERAB.EstabAddSuccNbr.QCI - KPI Object: E-UTRAN - KPI category: Accessibility - Unit of the KPI: Percentage - Type of the KPI: RATIO - Remark: The definition of the service provided by E-UTRAN is E-RABs.


© Nokia 2014

Content

• Performance KPI Details - Retainability • E-RAB Retainability


© Nokia 2014

Performance KPI Details E-RAB Retainability - Long name: E-RAB Retainability. - Description: A measurement that shows how often an end-user abnormally looses an E-RAB during the time the E-RAB is used. - Logical formula definition: Number of E-RABs with data in a buffer that was abnormally released, normalized with number of data session time units. - Physical formula definition: To measure E-RAB Retainability for a single QCI (R1) is fairly straight forward.


© Nokia 2014

Performance KPI Details E-RAB Retainability However to measure the E-RAB Retainability for UEs is not as straight forward. The measurement R1 is defined to look at the activity level of just one QCI at the time, so to use this formula and measurements in an aggregated way to get E-RAB Retainability on UE level will not be accurate (e.g. for an UE with multiple E-RABs, there might be E-RABs that are active at the same time, hence aggregating the QCI measurements for session time will give a larger session time than the total UE session time. See picture below). UE session time:

10 periods (UE1:4, UE2:6)

QCI=X ses sion time : 7 period s (UE1:4, UE 2:3) QCI=Y ses sion time : 5 period s (UE1:0, UE 2:5)

UE1

E-RAB QCI=X

One activity period E-RAB QCI=X


© Nokia 2014

UE2

E-RAB QCI=Y

[t]

Performance KPI Details E-RAB Retainability Hence a measurement E-RAB Retainability on UE level is defined (R2) to provide a measurement for the overall E-RAB Retainability.

- Measurement names used for the KPI: ERAB.RelActNbr.QCI, ERAB.SessionTimeUE, ERAB.SessionTimeQCI.QCI

- KPI Object: E-UTRAN - KPI category: Retainability. - Unit of the KPI: Active release/second. - Type of the KPI: MEAN. - Remark: The definition of the service provided by E-UTRAN is E-RABs. 43 13/12/2015 Confidential

© Nokia 2014

Performance KPI Details E-RAB Retainability

Extended definition: The retainability rate is defined as:

As for defining an abnormal E-RAB release with end-user impact, it shall only be considered an abnormal release of the E-RABs if the eNodeB considers there to be data waiting for transfer in any of the buffers. As for defining an E-RAB as active, an E-RAB shall be considered active if there recently has been any data transmission in any direction. 44 13/12/2015 Confidential

© Nokia 2014

Content

• Performance KPI Details - Integrity • E-UTRAN IP Throughput


© Nokia 2014

Performance KPI Details E-UTRAN IP Throughput - Long name: E-UTRAN IP Throughput.. - Description: A KPI that shows how E-UTRAN impacts the service quality provided to an end-user. - Logical formula definition: Payload data volume on IP level per elapsed time unit on the Uu interface. - Physical formula definition: - Measurement names used for the KPI: - KPI Object: E-UTRAN - KPI category: Integrity


© Nokia 2014

Performance KPI Details E-UTRAN IP Throughput - Unit of the KPI:kbits/s - Type of the KPI: MEAN

- Remark: To make sure that only impacts from the RAN is included in this measurement, time units to be included in “elapsed time unit on the Uu interface “shall only be the ones where there is data in the buffer to be transmitted E.g.in application data flows such as a web session, there are times when there is no data to transmit by the eNodeB due to bursty traffic pattern, then this “eNodeB idle time” shall not be included in “elapsed time unit on the Uu interface “.


© Nokia 2014

Performance KPI Details E-UTRAN IP Throughput Extended definition: To achieve a Throughput measurement that is independent of file size it is important to remove the samples where one TTI on the radio interface is not utilized. (Successful transmission, buffer empty in figure below).

Successful transmission, buffer not empty Failed transmission ( ” Block error ”)

The last data unit TTI shall always be removed from calulations since it can be impacted by packet size of User Plane (UP) packets.

T_tp_DL

Successful transmission, buffer empty No transmission, buffer not empty (e.g. due to contention)

Time (ms)

Data arrives to empty DL buffer First data is transmitted to the UE

V_tp_DL =

∑ ∑

V_tot_DL =

The send buffer is again empty

(Bytes) +

(Bytes)

Throughput_DL =V_tp_DL / T_tp_DL (Byte/s) 48 13/12/2015 Confidential

© Nokia 2014

Performance KPI Details E-UTRAN IP Throughput • To achieve a throughput measurement that is independent of bursty traffic pattern, it is important to make sure that idle gaps between incoming data is not included in the measurements. That shall be done as considering each burst of data as one sample. • V_tp_DL is the volume on IP level and the T_tp_DL is the time elapsed on Uu for transmission of the volume included in V_tp_DL. Buffer fillness

Session

Sample 1


© Nokia 2014

Sample 2

Content

• Performance KPI Details - Integrity • E-UTRAN IP Latency


© Nokia 2014

Performance KPI Details E-UTRAN IP Latency - Long name: E-UTRAN IP Latency. - Description: A measurement that shows how E-UTRAN impacts on the delay experienced by an end-user. - Logical formula definition: Time from reception of IP packet to transmission of first packet over the Uu. - Physical formula definition

- Measurement names used for the KPI: DRB.IPLatDl. QCI

- KPI Object: E-UTRAN 51 13/12/2015 Confidential

© Nokia 2014

Performance KPI Details E-UTRAN IP Latency - KPI category: Integrity. - Unit of the KPI: Milliseconds.

- Type of the KPI: MEAN. - Remark: To make sure only contribution from the RAN is included in this measurement, only delay of the first block to the Uu is counted.


© Nokia 2014

Performance KPI Details E-UTRAN IP Latency Extended definition: To achieve a delay measurement that is independent of IP data block size only the first packet sent to Uu is measured.

To find the delay for a certain packet size the IP Throughput measure can be used together with IP Latency (after the first block on the Uu, the remaining time of the packet can be calculated with the IP Throughput measure). Successful transmission, buffer not empty

T_Lat_DL

Failed transmission ”(Block error”) Successful transmission, buffer empty No transmission, buffer not empty (e.g. due to contention)

Time (ms)

Data arrives to empty DL buffer First data is transmitted to the UE by the eNodeB


© Nokia 2014

Latency_DL = ∑ T_Lat_DL (s) / # samples

Content

• Performance KPI Details - Availability • E-UTRAN Cell Availability


© Nokia 2014

Performance KPI Details E-UTRAN Cell Availability - Long name: E-UTRAN Cell Availability. - Description: A KPI that shows Availability of E-UTRAN Cell.

- Logical formula definition: Percentage of time that the cell is considered available. - Physical formula definition:

- Measurement names used for the KPI: RRU.CellUnavailableTime.cause - KPI Object: E-UTRAN 55 13/12/2015 Confidential

© Nokia 2014

Performance KPI Details E-UTRAN Cell Availability - KPI category: Availability - Unit of the KPI: Percentage

- Type of the KPI: RATIO - Remark: -

Extended Definition:

As for defining the cell as available, it shall be considered available when the eNodeB can provide E-RAB service in the cell. 56 13/12/2015 Confidential

© Nokia 2014

Content

• Performance KPI Details - Mobility • E-UTRAN Mobility


© Nokia 2014

Performance KPI Details E-UTRAN Mobility - Long name: E-UTRAN Mobility. - Description: A KPI that shows how E-UTRAN Mobility functionality is working. - Logical formula definition: Success rate of E-UTRAN Mobility. - Physical formula definition:

- Measurement names used for the KPI: HO.ExeAtt, HO.ExeSucc, HO.PrepAtt.QCI, HO.PrepSucc.QCI 58 13/12/2015 Confidential

© Nokia 2014

Performance KPI Details E-UTRAN Mobility - KPI Object: E-UTRAN - KPI category: Mobility

- Unit of the KPI: Percentage - Type of the KPI: RATIO - Remark: -

Extended Definition: The measurement shall include both Intra E-UTRAN and Inter RAT handovers. The measurement shall include both the preparation and execution phase of the handover. ”Entering preparation phase” is defined as the point of time when the source eNB attempts to prepare resources for an UE in a neighboring cell. ”Success of execution phase” is defined as the point of time when the source eNB receives information that the UE successfully is connected to the target cell. 59 13/12/2015 Confidential

© Nokia 2014

Content



© Nokia 2014

Content

• Driver test KPI - Field KPI Definitions - Test Conditions and Target Values


© Nokia 2014

Driver test KPI Definitions

• The defined field KPI lists do not present by any means a complete set of KPIs to be used in a customer case. It is the project team responsibility to define and agree with the customer the final list of KPIs to be used in each and every case. • The measurement each onKPI is just informative, actual testprocedure procedure of depends customer‟s requirements and may quite different from what has been stated here. 62 13/12/2015 Confidential

© Nokia 2014

Driver test KPI Definitions

• The most interested field KPIs are listed below: KPI Name PS Data Service Accessibility Ratio [%] Application Services (FTP, Completed Session Ratio [%] Services HTTP etc) Single User Throughput [Mbps] Attach Time [ms] Attach Success Rate [%] Service Request (EPS) Time [ms] Control Plane Service Request (EPS) Success Rate [%] LTE E2E Network Service

User Plane


© Nokia 2014

Radio Bearer Services

KPI Category Accessibility Reliability Throughput Latency Accessibility Latency Accessibility

Service (EPS) Drop Rate [%] Handover Procedure Time [ms]

Reliability Latency

Handover Success Rate [%] (LTE) Round Trip Time (RTT) [ms]

Accessibility Latency

(LTE) Single User Throughput [Mbps] (LTE) Service Interrupt Time (HO) [ms]

Throughput Latency

(RB) Single User Throughput [Mbps]

Throughput

Cell Throughput [Mbps]

Throughput

User Plane

Driver test KPI (FTP) Service Accessibility Ratio (1) Definition

It denotes the probability that the user can establish the necessary bearer (EPS) and access the FTP service successfully.

Service access covers starting the FTP client on the UE, setting up mobile access and creating a TCP connection to the FTP server. Measurement 1. Set the FMT to generate calls to the FTP Server automatically with the following script/sequence: methodology a. Connection a ttempt ( network at tach) b. Log into the FTP Server c. FTP Dow nload 800M B file (o r othe r size wit h transfer dur ation >1mi n) d. Wait 3 se c. after session f inishes e. FTP Upl oad 300 MB file ( or oth er siz e with t ransfer du ration >1m in) f. Log out the FTP Server If UE gets into UE deregistered status between calls, this test also valid to


check the Attach Success Rate g. Connection rel ease (network detach) h. Leave 5 seconds before start next session i. Repeat all previous steps (from „a‟) 2. Continue drive testing till the drive route is completed. 3. Stop the F MT at the en d o f t he route. 4. If the route does not generate more than 100 calls repeat the measuremen t on the same measurement route. 5. © Nokia The2014 FMT shall record the CRS RSRP, RSRQ and CRS SINR during the measurement. 6. Verify the PS Data Call success rate as per formula below

Driver test KPI (FTP) Service Accessibility Ratio (2)

Formula (logical) Assumptions, pre-conditions

The FTP transfer shall be executed in binary mode.

Preconditions: UE EMM-DEREGISTERED Message flow, Trigger points: trigger points Start: ftp get / put command issued on the UE. Stop: first data byte sent / received by the UE, or ftp indicates network error (e.g. timeout expired). Related E2E KPIs (FTP) Completion Session Ratio.


© Nokia 2014

Driver test KPI (FTP) Completed Session Ratio (1) Definition

The Completion Session Ratio is the proportion of completed FTP sessions and sessions that were started successfully. The session is not completed if a predefined timer expires, or a network failure occurred that could not be repaired by automatic restarts. Measurement 1. Set the F MT to gen erate calls t o the FTP Se rver autom atically with t he fol lowing scr ipt/sequence: methodology a. Connection a ttempt (n etw ork at tach) b. Log into the FTP S erver c. FTP Do wnlo ad 800 MB file ( or oth er siz e with tr ansfer du ration >1m in) d. Wait 3 s ec. after session finishes e. FTP Up load 3 00MB f ile (o r oth er siz e with transfer duration >1mi n) f. Log out the FTP Server If UE gets into UE deregistered status between calls, this test also valid to check the Attach Success Rate


g. Connection re lease (n etwork det ach) h. Leave 5 seconds before start next session i. Repeat a ll previous s teps (from „a‟) 2. Continue drive testing till the drive route is complet ed. 3. Stop the F MT at the end o f t he route. 4. If the route does not generate more than 100 calls repeat the measurement on the same measurement route. 5. © NokiaThe 2014F MT shall record th e CRS RSR P, RS RQ and CRS S INR during the measurement. 6. Verify the Complet ion Session Ratio as per formula below

Driver test KPI (FTP) Service Accessibility Ratio (2) Assumptions, pre- The FTP transfer shall be executed in binary mode. conditions FTP Application DL Throughput as measured by the DOS ftp application. If above measurement methodology is followed the UE needs to attach to the network between FTP UL/DL sessions if the Attach Success Rate wants to be measured. Formula (logical)

Message flow, Trigger points: trigger points Start: ftp get / put command issued on the UE Stop: after error free execution of the command, ftp returns with a prompt and indicates the number of bytes transmitted. Related E2E KPIs (FTP) Service Accessibility Ratio.  


© Nokia 2014

Driver test KPI (FTP) Single User Throughput (1) Definition

After the connection to the FTP server has been successfully established, the parameter describes the average data transfer rate measured over the data transfer phase. I.e. prerequisite to the data transfer is successful Service Access (availability of an EPS bearer and connection to the FTP service). The data transfer phase shall also be successfully terminated.

The throughput is measured on application level in UL/DL direction. Measurement 1. Set the FMT to generate calls to the FTP Server automatically with t he following script /sequence: methodology a. Co nne ct ion a tt em pt (n et wor k at ta ch) b. Lo g int o t he FT P Serv er c. FTP Do wnlo ad 80 0MB fi le (or ot her si ze wit h tran sfer dura tio n >1m in) d. Wa it 3 s ec. af te r se ssion finish es e. FTP Up loa d 300M B file ( or oth er siz e with t ran sfer dura tio n >1mi n) f. Log out the FTP Server If U E gets into UE de regist ered st atus be tween calls, this te st also valid t o check the Attach Success Rate g. Co nne ct ion re leas e (ne two rk de tach )

2. 3. 4. 5. 6. 7. 68 13/12/2015 Confidential

h. Lea ve 5 second s befo re star t ne xt sessio n i. Re pe at a ll p re vi ou s s teps ( fr om „a‟) Cont inue driv e test ing till the drive rout e is comp let ed. St op th e F MT a t t he en d o f t he ro ut e. If the route d oes not genera te more than 100 calls repeat the measurement on the same measurement route). The F MT sh all r eco rd th e CRS RSR P, RS RQ an d CRS S INR d urin g the m easure ment. Verify the average DL/UL th roughput o f each session and deter mine the fin al average throughp ut of all sessions. The measured mean throughputs can be displayed in diagrams as function of time to show t he impact of FTP slow start.

© Nokia 2014

Driver test KPI (FTP) Service Accessibility Ratio (2) Assumptions, conditions

pre- The initial status of UE before starting the application: EMM-REGISTERED, ECM-CONNECTED. If above measurement methodology is followed the UE needs to attach to the network between FTP UL/DL sessions if the Attach Success Rate wants to be measured. The FTP application shall be executed in binary mode, and the file to be transferred shall be binary.

Formula (logical) Message flow, The average throughput is measured from opening the data connection to trigger points the end of the successful transfer of the content (file, e-mail or web page).

Related E2E KPIs


© Nokia 2014

Trigger points for ftp upload / download are defined in [ETSI102.250-2] Chapters 4.6.1.7 and 4.6.2.7. (FTP) Service Access Time, (FTP) Session Time.

Driver test KPI Attach Time (1) Definition

With Attach, the mobile terminal registers at the LTE network. At the end of the procedure the UE is authenticated, and a default (non-GBR) bearer is established.

The Attach Time is the interval between the RRC CONNECTION REQUEST (carrying the Attach Request) and the reception of a positive response by the UE (Attach Complete). Measurement 1 LTE UE/terminal with FMT methodology Set FMT to generate data calls to the data server automatically Check the UE DEGERISTERED between data calls Start drive test and continue driving until drive route is completed and enough samples are collected (re-drive route if necessary) Verify the Attach Time Assumptions, UE status before measurement: EMM-DEREGISTERED pre-conditions UE locked to LTE network.    




© Nokia 2014

Driver test KPI Attach Time (2)

Formula (logical) Message flow, trigger Trigger points on UE R interface (see Figure 2, and refer to [3GPP23.401]): points Begin: 1. RRC CONNECTION REQUEST sent by UE carrying L3 NAS: Attach Request in its body. End: 21. RRC DIRECT TRANSFER message with L3 NAS: Attach Complete in its body sent by UE (refer to [3GPP24.008]). Related E2E KPIs a) Attach Success Rate. b) No 3G PP def ined KPI fo r Attach T ime fo und ex ists, or me asurements defined in R8 documents. 




© Nokia 2014



© Nokia 2014



© Nokia 2014

Driver test KPI Attach Success Rate (1) Definition

The Attach Success Rate is defined as the ratio between the number of successful registrations (RRC DIRECT TRANSFER: Attach Complete) and the number of all requests (RRC CONNECTION REQUEST: Attach Request). It is the probability that a user can attach to the LTE network at any moment of time.

The calculated success ratio figure excludes attach requests, which are rejected by authentication failures. On the other hand, network attach requests which are terminated by timer expiry (due to the unavailability of some LTE resource) are considered as unsuccessful registrations. If the success rate is calculated on the eNB by counting incoming RRC requests, RRC CONNECTION REQUEST retries are to be excluded, since they would increase the overall number of establishment attempts, and thus reduce the success ratio. Measurement For defining the success ratio, the same series of “Attach Time” measurements can be used: methodology   



1 LTE UE/terminal with FMT Set FMT to generate data calls to the data server automatically Start drive test and continue driving until drive route is completed and enough samples are collected (re-drive route if necessary) Verify the Attach Success Rate as per formula below

The KPI cannot be measured as end-user perceived ratio on certain mobiles, which do not indicate network attachment status to the end-user. 74 13/12/2015 Confidential

© Nokia 2014

Driver test KPI Attach Success Rate (2) Assumption UE status before measurement: EMM-DEREGISTERED s, UE locked to LTE network. preconditions Formula (logical) Message flow, trigger

Trigger events on UE R interface (see Figure 2): 

points

Success: 21. RRC DIRECT TRANSFER message

with L3 NAS: Attach Complete in its body sent by the UE Attempts: 1. RRC CONNECTION REQUEST messages (with cause Attach Request) sent by UE Related E2E Attach Time, Service Request (EPS) Success Rate. KPIs 


© Nokia 2014

Driver test KPI Service Request (EPS) Time, UE Initiated (1) Definition

Time taken by the LTE network to setup an EPS bearer on request by the UE. The EPS bearer can be new (dedicated) or an existing one (e.g. the default EPS bearer). The latter is needed to re-assign Uu radio and S1 bearer resources to the existing EPS bearer of a previously idle UE. The EPS bearer has to be created before IP packets can be exchanged. The UE Initiated EPS Bearer Setup Time is the interval between the submission of the message RRC CONNECTION REQUEST: Service Request (refer to [3GPP36.331]) and the reception of the RRC CONNECTION RECONFIGURATION response on the UE. The Bearer Setup procedure is based on the Service Request procedure according to [3GPP23.401] and [3GPP36.300]. 

Measurement methodology

 

 


© Nokia 2014

1 LTE UE/terminal with FMT Set FMT to generate data calls to the data server automatically Start drive test and continue driving until drive route is completed and enough samples are collected (re-drive route if necessary) Verify the EPS Bearer Setup Time Note below that UE pre-status is EMM-REGISTERED so this KPI excludes the Attach time

Driver test KPI Service Request (EPS) Time, UE Initiated (2) Assumptions, UE status before measurement: EMM-REGISTERED and idle initial state. pre-conditions UE locked to LTE network. Formula (logical) Message flow, The message flow diagram is shown in Figure 3 and Figure 4. The user trigger points initiated EPS bearer setup time is measured between the trigger points BUE and EUE on the UE R interface: 



Related KPIs 77 13/12/2015 Confidential

E2E a) b)

© Nokia 2014

Begin: RRC CONNECTION REQUEST(NAS: Service Request) sent by UE End: corresponding RRC CONNECTION RECONFIGURATION COMPLETE message or first PDU in UL sent by the UE (refer to [3GPP24.008]). Attach Time. No 3G PP defined KPI for EPS be arer setu p found (ex ists).

Driver test KPI Service Request (EPS) Time, UE Initiated (3)


© Nokia 2014



© Nokia 2014


LTE-Uu UE

S1 M-M E eN o d eB

T1

S1 1 M ME

S1-AP: INITIAL CONTEXT

S6 a S- GPW /- GW

H SS

PM Counter: EPS_SETUP_ATT

SETUP REQUEST S1-AP: INITIAL CONTEXT SETUP FAILURE RRC SECURITY MODE COMMAND RRC CONNECTION RECONFIGURATION

Setup user plane RB

RRC SECURITY MODE COMMAND COMPLETE EUE

RRC CONNECTION RECONFIGURATION

End measurement

COMPLETE

First UL PDU

T2

S1-AP: INITIAL CONTEXT

PM Counter: EPS_SETUP_SUCC

SETUP COMPLETE L2 SCTP: Update Bearer Request L2 SCTP: Update Bearer EN Response


© Nokia 2014

First DL PDU

Means „Delay DL Packet Notification Request“ to stop/ enable DL data transfer

Driver test KPI Service Request (EPS) Success Rate (1) Definition

Ratio between successfully established EPS bearers compared to the overall number of EPS bearer establishment attempts. It corresponds to the probability that a user or the LTE network can establish an EPS bearer at any moment in time. Requests which are terminated by timer expiry (due to the unavailability of some LTE resource) are considered as unsuccessful attempts. Authentication errors (requests rejected by the MME) are included in the total number of failures.

Only the first RRC CONNECTION REQUEST is to be considered, since counting retries of the same message would increase the overall number of bearer establishment attempts, and thus reduce the success ratio. Measurement 1 LTE UE/terminal with FMT 

methodology

 



Set FMT to generate data calls to the data server automatically Start drive test and continue driving until drive route is completed and enough samples are collected (re-drive route if necessary) Verify the EPS Bearer Setup Success Rate

Note below that UE pre-status is EMM-REGISTERED so this KPI excludes the Attach time 81 13/12/2015 Confidential

© Nokia 2014

Driver test KPI Service Request (EPS) Success Rate (2) Assumptions, pre- UE status before measurement: EMM-REGISTERED and idle initial state. conditions UE locked to LTE network. Formula (logical) Message flow, The message flow diagram is shown in Figure 3 and Figure 4. The trigger trigger points points for UE initiated EPS bearer setup success ratio on the R interface are: 



Success: RRC CONNECTION RECONFIGURATION COMPLETE message sent by the UE, see EUE on Figure 4. Total: an attempt is the sending of RRC CONNECTION REQUEST with UE on Figure 3. appropriate establishment cause by the UE, see B

Related E2E KPIs

Service Request (EPS) Time, UE Initiated. For initial EPS bearers, refer to KPI“Attach Success Rate”.


© Nokia 2014

Driver test KPI Service (EPS Bearer) Drop Rate (1)

Definition

Ratio between abnormally released bearers, and the overall number of established EPS bearers. An abnormal release is defined as any EPS bearer termination, which was not triggered by the mobile user (from UE side). Thus, it reflects the probability that an established bearer gets aborted due to insufficient network resources. Dropping the bearer gets visible to the end-user if an application service is actively using it. If the application automatically reestablishes the bearer, it remains unnoticed by the user. 1 LTE UE/terminal with FMT Set FMT to generate data calls to the data server automatically   




Start drive test and continue driving until drive route is completed and enough samples are collected (re-drive route if necessary) Verify the EPS Bearer Drop Rate

Note below that UE pre-status is EMM-REGISTERED so this KPI excludes the Attach time.


© Nokia 2014

Driver test KPI Service (EPS Bearer) Drop Rate (2) Assumptions, pre-conditions

UE status before measurement: EMM-REGISTERED and idle initial state. UE locked to LTE network.

Formula (logical) Trigger points on UE R interface: 

Message

flow,

trigger points

Related E2E KPIs 84 13/12/2015 Confidential

© Nokia 2014



Success: submission of the message RRC CONNECTION RECONFIGURATION COMPLETE by the UE, refer to [3GPP36.331] Drop: successful establishments minus terminations by the user, i.e. the UE submitting a L3 DETACH REQUEST (refer to [3GPP24.008]) carried within the RRC message UL NAS TRANSPORT (refer to [3GPP36.331]).

For the calculation of a network initiated EPS bearer drop rate, EPC initiated L3 DETACH REQUEST-s are to be considered. Service Request (EPS) Success Rate.

Driver test KPI Handover Procedure Time (1) Definition

It denotes the total time needed for the handover procedure as seen by the UE. It begins by receiving a Handover Command from the source eNB and ends by sending the Handover Confirm response to the target eNB by the UE. The value of the KPI also depends of the handover scenario. The following HO scenarios are distinguished (though not directly seen by the UE):  

Measurement



intra- and inter-frequency HO inter eNB HO via X2/S1 interface 1 LTE UE/terminal with FMT



methodology





Set FMT to test generate data callsdriving to the data automatically Start drive and continue until server drive route is completed and enough samples are collected (re-drive route if necessary) Verify HO time for the different HOs

The handover time shall be measured on the UE R interface. 85 13/12/2015 Confidential

© Nokia 2014

Driver test KPI Handover Procedure Time (2) Assumptions, Since Inter-RAT HO is not part of RL15 the only HO scenarios pre-conditions considered are intra LTE. Therefore, the LTE UE must be locked to LTE network. UE status before measurement: registered and connected. Formula (logical) Message flow, The HO time is seen by the UE as the elapsed time between: trigger points Start: UE receives Handover Command in the body of an RRC Connection Reconfiguration request from source eNB. Stop: UE sends Handover Confirm response to target eNB in an RRC Connection Reconfiguration Complete message. Related E2E a) (LTE) Service Interrupt Time (HO), Handover Success Rate KPIs b) No 3GPP defined KPI for H O procedure time found. 




© Nokia 2014

Driver test KPI Handover Success Rate (1)

Definition Measurement methodology

The Handover Success Rate is the ratio between successfully executed (committed) HO procedures and the number of all Handover attempts. 1 LTE UE/terminal with FMT Set FMT to generate data calls to the data server automatically Start drive test and continue driving until drive route is completed and enough samples are collected (re-drive route if necessary) Verify the Handover Success Rate   



Assumptions, pre-conditions


© Nokia 2014

The measurement is to be executed for different HO scenarios. LTE terminal must be locked into the LTE network.

Driver test KPI Handover Success Rate (2) Formula (logical) Message flow, trigger points

Trigger points on eNB X2/S1 interfaces: 



Total #: Handover Requests sent by Source eNB to Target eNB (HO via X2), or sent by MME to Target eNB(HO via S1). Success #: UE Context Release message received by Source eNB from Target eNB(HO via X2), or UE Context Release Command received by Source eNB from M ME(HO via S1).

Related E2E KPIs


© Nokia 2014

In case of intra eNB HO procedures, no Handover Request is sent. Both trigger points are counted by the Source eNB internally. Handover Procedure Time

Driver test KPI (LTE) Round Trip Time (1) Definition


RTT in UL is the interval between sending a datagram by the UE & receiving the corresponding reply from an IP peer entity connected to the Gi interface of the P-GW. RTT in DL is the interval between sending a datagram to the UE & receiving the corresponding reply by the IP host (peer entity). Stationary users in different cell positions, which are uniformly distributed across the cell. RTT is measured with the Ping application between the UE and an IP host (peer entity). As average RTT figure, the output of the Ping application is used (e.g. “MS-DOS >ping -n count -l size host name”). Size of ICMP packets: 32, …, MTU bytes. Ping shall be executed at least 100 times to reduce the impact of the first ICMP message, which triggers the setup of radio bearer establishments in UL and DL directions. Record the average RTT shown on the screen after the application has run. Repeat the test 5 times in each location under different SINR. Note: Ping tests can also be carried out as part of a drive test sequence in which case, it is not possible to guarantee certain SINR levels


© Nokia 2014

Driver test KPI (LTE) Round Trip Time (2) Assumptions, pre-conditions

UE status before measurement: registered and connected. An IP address is assigned to the UE. The IP peer entity shall be located as close as possible to the SGi interface. Usually, 1 hop away the SAE-GW. Additional delays between the P-GW and the IP host shall be avoided or minimized.

Formula (logical) Message flow, Trigger points both from UE, and from IP peer entity view: trigger points Start: ICMP ECHO REQUEST Stop: ICMP ECHO REPLY Related E2E KPIs No 3GPP defined KPI for LTE RTT found.  


© Nokia 2014

Driver test KPI (LTE) Single User Throughput (1) Definition

The metric describes the data speed available to one user of the LTE network on UDP/IP level. It is given as the maximum (95%-ile) value that can be observed over a short period of time (e.g. of 1s) and as a mean value that characterizes longer data transfer periods (minutes). Its value distribution over the radio cell is given as a function of the SINR. The maximum value is often referred to in the literature as instantaneous "Peak Throughput" that is achieved in optimal radio conditions. The user throughput can be given for a single user active in the cell



© Nokia 2014

(single users. user data rate), or to one of several concurrently active Stationary and mobile user covering all kinds of cell positions: near, medium, far, including different HO scenarios. The data rate is measured in UL/DL direction with UDP/IP traffic over a time period of several minutes.

Driver test KPI (LTE) Single User Throughput (2) Assumptions, pre-conditions

The IP host used as traffic generator (e.g. with Iperf) should be connected directly to the SGi interface. Additional delays and bandwidth restrictions between the S/P-GW and the server need to be excluded.

Formula (logical)

Message

flow, Trigger points on the UE R interface:

trigger points


© Nokia 2014

• UL: UE sending UDP/IP packets to the IP peer entity.

• DL: IP peer entity sending UDP/IP packets to the UE. E2E Cell Throughput, (FTP) Single User Throughput, (RB) Single User Throughput.

Driver test KPI (LTE) Service Interrupt Time (HO) (1) Definition

Service interrupt is the discontinuity (increased packet inter-arrival time) of an IP packet flow caused by hand-over. It is the interval between the last sent/received user IP packet of a continuous UL/DL data stream in the old cell, and the first sent/received user IP packet in the new cell (user plane break).


The value of the KPI also depends of the handover scenario. 1 LTE UE/terminal with FMT 



Set FMT to generate data calls to the data server automatically



Start drive test and continue driving until drive route is completed and enough samples are collected (re-drive route if necessary)



Verify the Service Interrupt Time

The measurement is to be executed for different HO scenarios: intra eNB, inter eNB via X2/S1 etc. Only mobile user scenarios are considered. FTP upload/download data transfer, or real-time media flow during the handover. 93 13/12/2015 Confidential

© Nokia 2014

Driver test KPI (LTE) Service Interrupt Time (HO) (2)

Assumptions, conditions

pre- It is assumed that the X2 interface is enabled between the source and target eNBs (for inter eNB HO scenarios). LTE terminal must be locked into the LTE network to measure the Service Interrupt Time.

Formula (logical) Message

flow, The trigger points for service interrupt time (from UE point of view):

trigger points

Related E2E KPIs


© Nokia 2014



Start: UE sends/receives last packet to/from source eNB



Stop: UE sends/receives first packet to/from target eNB.

Handover procedure time.

Driver test KPI (RB) Single User Throughput (1) Definition

The metric describes the RB throughput achievable by one user. It can be given as single user throughput if only one user is active in the cell, or as multi-user throughput for a given number of concurrently active users. The user throughput distribution over the cell is given as function (CDF) of the radio conditions characterized by the SINR.


The time variation of the KPI value in a given cell position is given with its maximum (95%ile) (also referred to as instantaneous “Peak User Throughput”), and with its average (mean) value. Stationary and mobile user covering all kinds of cell positions: near, medium, far, including different HO scenarios. The eNB assigns all resources (resource blocks) to this user, except the resource blocks used for signaling and throughputs cancontrolling. be defined.With the help of trace analysis, PDCP, RLC, MAC and PHY layer With and w/o concurrency in UL / DL traffic. The mean user data rate is calculated over a few minutes, peak data rate values are averaged over short periods of time (e.g. 1s).


© Nokia 2014

Driver test KPI (RB) Single User Throughput (2)

Assumptions, pre-conditions

All transport bearers between the UE and IP peer entity should have higher capacity than the radio link in order to avoid bandwidth bottlenecks.

Formula (logical) Message flow, Trigger events on the eNB Uu interface or the UE R interface: trigger points UL: eNB receiving PDUs, or UE sending PDUs DL: eNB sending PDUs, or UE receiving PDUs  

Measured at the upper SAPs of the protocols PDCP, RLC, MAC or PHY. Related E2E KPIs (LTE) Single User Throughput, Cell Throughput.


© Nokia 2014

Driver test KPI Cell Throughput Definition

The metric shows the sustainable aggregate throughput of the cell (in UL/DL) available to “n” stationary users distributed uniformly in the cell and running a typical mix of applications. The “cell throughput” is the sum of all bits transported in all resource blocks carrying PDUs (i.e. bits in ULSCH/DL-SCH transport blocks) during one second. The cell capacity is also given as peak value (called peak cell capacity, or throughput), which is defined as the aggregate throughput of “n” users all located in best radio conditions.


The cell throughput value is defined here on PHY level, but could be given for other protocol levels (UDP/IP, PDCP, RLC, MAC), too. When the (peak, average) cell throughput is expressed on UDP/IP level, it corresponds to the (peak, mean) user throughput value at comparable radio conditions. Stationary users uniformly distributed in the cell. UE categories according to application mix. Peak value measured with one user in LoS cell position using UDP/IP load to approach the full buffer condition. Measured with UDP/IP traffic on PHY layer (UL-SCH/DL-SCH transport block bits) over several minutes. With the help of trace analysis PDCP, RLC and MAC layer values can also be given.


© Nokia 2014

Driver test KPI Cell Throughput Assumptions, pre-conditions

All IP transport bearers (S1, S5/S8, SGi) between the UE and IP peer entity should have higher bandwidth than the cell capacity to avoid bandwidth bottlenecks.

Formula (logical)

Message flow, Trigger events on the eNB Uu interface or the UE R trigger points interface: UL: eNB receiving PDUs, or UE sending PDUs DL: eNB sending PDUs, or UE receiving PDUs E2E (RB) Single User Throughput.  


© Nokia 2014

Content

• Driver test KPI - Field KPI Definitions - Test Conditions and Target Values


© Nokia 2014

Test Conditions and Target Values Field KPI

Target Values

Comments

Single User UL In case UL/DL conf=2:2(#1) and special subframe conf=10:2:2(#7): 15.4M CMCC Hangzhou TD-LTE trial: Peak Throughput In case UL/DL conf=3:1(#2) and special subframe conf=10:2:2(#7): 7.5M *Cat 3 UE is considered and MCS20 is the max MCS in UL for RL15. *PUCCH overhead is 4RB and PDCCH In case UL/DL conf=2:2(#1) and special subframe conf=10:2:2(#7): overhead is 3 OFDM symbols. TM3: 59.6M *L3 TCP throughput is considered. Single User DL TM7: 34M *Network is unloaded. Peak Throughput In case UL/DL conf=3:1(#2) and special subframe conf=10:2:2(#7): *System bandwidth is 20M. TM3: 80.7M TM7: 40.3M Throughput

In case UL/DL conf=2:2(#1) and special subframe conf=10:2:2(#7): 0% load: 14.5M 50% load: 13.3M

Cell UL Average Throughput 70% load: 15.6M In case UL/DL conf=3:1(#2) and special subframe conf=10:2:2(#7): 0% load: 7.6M 50% load: 6.5M

10 13/12/2015 0 Confidential

In case UL/DL conf=2:2(#1) and special subframe conf=10:2:2(#7): 0% load: 35.6M 50% load: 21.77M Cell DL Average 70% load: 24.82M Throughput In case UL/DL conf=3:1(#2) and special subframe conf=10:2:2(#7): © Nokia 2014 0% load: 40M 50% load: 25.1M

CMCC Hangzhou TD-LTE trial: *Cat 3 UE is considered and MCS20 is the max MCS in UL for RL15. *PUCCH overhead is 4RB and PDCCH overhead is 3 OFDM symbols. *L3 TCP throughput is considered. *System bandwidth is 20M. *20 UEs distributed by 2:4:8:6. *DL MIMO is TM3/TM7 adaptive and UL is SIMO. *eNB SW version is different for each neighbor load: RL15_2_CD1.0 for 0% load, RL15_2_CD2.0 for 50% load and RL15_2_CD3.0 for 70% load.

Test Conditions and Target Values

Latency (Control Plane)

oentelecom Russia TD-LTE Trial: In case UL/DL conf=2:2(#1) and special *Radio condition is classified as: Attach Latency subframe conf=10:2:2(#7): Good: CRS SINR >25 0% load: 168ms Average: 10
Idle to Active Latency

Latency (User Plane)


Ping Latency

© Nokia 2014

In case UL/DL conf=2:2(#1) and special subframe conf=10:2:2(#7): 50% load: 106ms In case UL/DL conf=2:2(#1) and special subframe conf=10:2:2(#7): 0% load and single UE: for 32 bytes payload: 26ms for 1500 bytes payload: 30ms 50% load and single UE: for 32 bytes payload: 27ms for 1500 bytes payload: 31ms 50% load and 3 UEs: for 32 bytes payload: 28ms for 1500 bytes payload: 38ms

CMCC Hangzhou TD-LTE trial: *Radio condition is classified as: Very Good: CRS SINR > 22dB Good: 15dB< CRS SINR < 20dB Medium: 5dB < CRS SINR < 10dB Poor: -5dB < CRS SINR < 0dB *Pre-scheduling is off for 'Ping Latency' test,

Test Conditions and Target Values In case UL/DL Handover Latency conf=2:2(#1) and special (Control Plane, intra-eNB subframe conf=10:2:2(#7): or inter-eNB via X2) CMCC Hangzhou TD-LTE trial: 0% load: 32ms *Drive route includes both intra-eNB handover and inter-eNB handover (via X2).. Mobility Handover Latency (User Plane, intra-eNB or inter-eNB via X2)

In case UL/DL conf=2:2(#1) *C-plane latency is counted as MAC layer latency, and U-plane latency is counted as and special subframe PDCP layer latency, which is not strictly conf=10:2:2(#7): 0% load: 61ms


© Nokia 2014

complied with CMCC's test specification.

Test Conditions and Target Values In case UL/DL conf=2:2(#1) and special subframe Attach Success Rate conf=10:2:2(#7): 0% load: 100% 50% load: 99.17% In case UL/DL conf=2:2(#1) and RRC Connection special subframe conf=10:2:2(#7): Establishment Success Rate 0% load: 99% 50% load: 97.84% Accessibility

Handover Success Rate


© Nokia 2014

In case UL/DL conf=2:2(#1) and special subframe conf=10:2:2(#7): 0% load: 100% 50% load: 98.37%

CMCC Hangzhou TD-LTE trial: *2.6G frequency band w ith 20M system bandwidth. *Drive test, speed is about 30Km/h. *Attach SR is defined as: #(Attach complete) / #(UE Power on). *RRC Connection Establishment SR is defined as: #(RRCConnectionReconfigurationComplete) / #(Data service request) *Handover SR is defined as: #(RRCConnectionReconfigurationComplete containing Handover Confirm to Target eNB) / #(Handover Request) *DR is defined as: #(RRCConnectionRelease and/or without application-layer throughput for more than 10s) / #(RRCConnectionReconfigurationComplete)

Test Conditions and Target Values CMCC Hangzhou TD-LTE trial: *2.6G frequency band w ith 20M system bandwidth.

Reliability


Drop Rate

© Nokia 2014

In case UL/DL conf=2:2(#1) and special subframe conf=10:2:2(#7): 0% load: 2% 50% load: 3.42%

*Drive test, speed is about 30Km/h. *Attach SR is defined as: #(Attach complete) / #(UE Power on). *RRC Connection Establishment SR is defined as: #(RRCConnectionReconfigurationComplete) / #(Data service request) *Handover SR is defined as: #(RRCConnectionReconfigurationComplete containing Handover Confirm to Target eNB) / #(Handover Request) *DR is defined as: #(RRCConnectionRelease and/or without application-layer throughput for more than 10s) / #(RRCConnectionReconfigurationComplete)

Content



© Nokia 2014

KPI Analysis KPIs per measurement


© Nokia 2014

KPI Analysis LTE S1AP (M8000) S1 Interface measurement (M8000) measures GTP protocol procedures on user plane.


© Nokia 2014

KPI Analysis LTE Cell Load (M8001) (1/2) LTE Cell Load measurement (M8001) measures packet scheduling related measurements.


© Nokia 2014

KPI Analysis LTE Cell Load (M8001) (2/2) LTE Cell Load measurement (M8001) measures packet scheduling related measurements.


© Nokia 2014

KPI Analysis LTE Transport Load (M8004)

Transport Load measurement (M8004) measures GTP-U protocol procedures.


© Nokia 2014

KPI Analysis LTE Power and Quality UL (M8005) (1/3)

LTE Power and Quality UL measurement (M8005) measures UL connection quality related measurements.


© Nokia 2014




© Nokia 2014




© Nokia 2014

KPI Analysis LTE EPS Bearer (M8006)

LTE EPS Bearer measurement (M8006) measures EPS Bearer related measurements.


© Nokia 2014

KPI Analysis LTE Radio Bearer (M8007)

LTE Radio Bearer measurement (M8007) measures Radio Bearer related measurements.


© Nokia 2014

KPI Analysis LTE RRC (M8008)

LTE RRC measurement (M8008) measures RRC protocol procedures.


© Nokia 2014

KPI Analysis LTE Intra eNB Handover (M8009) LTE Intra eNB Handover measurement (8009) measures Intra eNB Handovers.


© Nokia 2014

KPI Analysis LTE Power and Quality DL (M8010)

LTE Power and Quality DL measurement (M8010) measures DL connection quality related measurements.


© Nokia 2014

KPI Analysis LTE Cell Resource (M8011) (1/2) LTE Cell Resource measurement (M8011) measures cell resource related measurements.


© Nokia 2014

KPI Analysis LTE Cell Resource (M8011) (1/2) LTE Cell Resource measurement (M8011) measures cell resource related measurements.


© Nokia 2014

KPI Analysis LTE Cell Throughput (M8012) (1/3) LTE Cell throughput measurement (M8012) measures cell throughput related measurements.


© Nokia 2014



© Nokia 2014



© Nokia 2014

KPI Analysis LTE UE State (M8013) LTE UE State measurement (M8013) measures UE State Management related measurements.


© Nokia 2014

KPI Analysis LTE Inter eNB Handover (M8014) LTE Inter eNB measurement (M8014) Inter eNB Handovers.


© Nokia 2014

Handover measures

KPI Analysis LTE Neighbor cell related Handover (M8015) Neighbor cell related measurement (M8015)


© Nokia 2014

Handover

KPI Analysis LTE eNB Load (M8018)

LTE eNB Load measurement (M8018)


© Nokia 2014

KPI Analysis KPIs with counters from several measurements


© Nokia 2014

KPI Analysis Measurements detailed analysis and KPI‟s:


© Nokia 2014

KPI Analysis Transport Performance Monitoring

The Performance Package for Transport, provides detailed insight into the performance of the transport interface of the eNodeB on IP layer.


© Nokia 2014

KPI Analysis LTE IP Statistics (M51120) LTE IP statistics measurement (M51120) contains PM counters to monitor the performance of the IP Iub functionality per IP interface.


© Nokia 2014

KPI Analysis LTE PHB Statistics (M51121) (1/2) LTE IP statistics measurement (M51121) contains PM counters to monitor the performance of the IP Iub functionality per IP interface.


© Nokia 2014

KPI Analysis LTE PHB Statistics (M51121) (2/2) LTE IP statistics measurement (M51121) contains PM counters to monitor the performance of the IP Iub functionality per IP interface.


© Nokia 2014

KPI Analysis LTE Ethernet Link (M51123) LTE Ethernet link measurement (M51123) contains PM counters to measure the ethernet link performance.


© Nokia 2014

KPI Analysis LTE IP Sec (M51125) LTE IP statistics measurement (M51120) contains counters for counting protected, discarded and bypassed octets and frames for IPSec.


© Nokia 2014

KPI Analysis LTE IP Filtering (M51126)

LTE IP filtering measurement (M51126) contains PM counters to monitor the firewall functionality of the BTS


© Nokia 2014

KPI Analysis LTE IP Filtering (M51126)

LTE VLAN IP statistics measurement (M51127) contains PM counters to monitor the performance of the IP Iub functionality per VLAN interface.


© Nokia 2014

KPI Analysis LTE VLAN PHB Statistics (M51128) (1/2)

LTE VLAN PHB statistics measurement (M51128) contains PM counters to monitor the performance of the IP Iub functionality per VLAN interface for each per hop behaviour.


© Nokia 2014

KPI Analysis LTE VLAN PHB Statistics (M51128) (2/2)

LTE VLAN PHB statistics measurement (M51128) contains PM counters to monitor the performance of the IP Iub functionality per VLAN interface for each per hop behaviour.


© Nokia 2014

Content

• KPI Analysis - KPI for Call Setup - Local analysis

- Vendor Report


© Nokia 2014

Content

• KPI for Call Setup - Introduction - KPIs

- Optimization actions/analysis - Summary - Project examples


© Nokia 2014

KPI for Call Setup Introduction 1. PRACH phase 2. SRB1 setup 3. NAS security 4. RRC security + UE Capability Enquiry

5. SRB2/DRB setup


© Nokia 2014

KPI for Call Setup Call Setup Phases : e s a h P

PRACH setup

PRACH setup Complete

SRB1 setup

SRB1 Setup complete

s t p m te t A

s s e c c u S

S1 conn. setup

RRC security

S1 conn complete

s RRC s e c security c ucomplete S

SRB2 + DRB

s SRB2 s e c +DRB c u S

Security complete failures S1 setup failures SRB1 setup failures PRACH failures (blocking) 14 13/12/2015 3 Confidential

© Nokia 2014

s s e c c u S

SRB2 +DRB setup failures

PRACH + Msg3 Initial network access process between UE and eNB SRB1 setup eNB resources are reserved for signalling connection between UE and eNB NAS security UE has RRC connection. If dropped, also active RAB is dropped. RRC security + UE capability enquiry SRB2 + DRB setup UE has RAB connection Call setup is affected if any of the followings take

•place. PRACH setup failures • SRB 1 setup failures • S1 connection failures • RRC security + UE cap failures • SRB2 & DRB setup failures

Content




© Nokia 2014

KPI for Call Setup List of important KPIs LTE_5218c Total E-UTRAN RRC Connection Setup Success Ratio If the value is lower than 99.5%, there are clear problems in network stability. 100% RRC Setup Failure Rate in a cell is an indication that the site needs recovery actions LTE_5017a E-UTRAN E-RAB Setup Success Ratio LTE_5009a S1 Initial Context Setup Success Ratio LTE_5096a E-UTRAN S1 Initial Context Setup Failure Ratio per Cause OTH LTE_5095a E-UTRAN S1 Initial Context Setup Failure Ratio per Cause RESOURC LTE_5094a E-UTRAN S1 Initial Context Setup Failure Ratio per Cause TRPORT LTE_5093a E-UTRAN S1 Initial Context Setup Failure Ratio per Cause RNL LTE_138a LTE_806a

RACH Setup Complete Success ratio Maximum of RRC connected users

LTE_1056b Complete RACH Setup Success Rate LTE_5a

SRB1 setup Success Ratio

LTE_5003a E-UTRAN Data Radio Bearer Setup Success Ratio LTE_5009a E-UTRAN S1 Initial Context Setup Success Ratio 14 13/12/2015 5 Confidential

© Nokia 2014

RRC Connection Establishment System program Report (RRC)

Note: • The majority of RRC connections are successfully established but possible site issues due to no response to RRC setup message or admission control failures due to congestion. • High number of RRC releases are initiated by EPC -> MME mobility management failures (e.g. TAU or Attach rejects). In case of Rejections:

Admission

Control

•Increase PUCCH capacity if the number of connected users in a cell is exceeding physical capacity and/or set RAC thresholds as per PUCCH capacity. In case of RRC releases initiated by EPC: • Check MME statistics regarding TAU and Attach procedures for troubleshooting. 14 13/12/2015 7 Confidential

© Nokia 2014

E-RAB Connection System program Report (E-RAB)

Note: •The majority of EPS Bearer connection establishments problems (if RRC SR is good) indicate the transport or the core network issues • E-RAB drop ratio depends on RRC inactivity timer • 3GPP recommends normalizing drops by time (drops per minute) for non-GBR bearers • Core network KPIs need to be analyzed for further problem isolation


© Nokia 2014

Content




© Nokia 2014

Counter and KPI analysis for Call setup Phase

Call setup has five phases:

 

1.

PRACH phase (also applies to handover)

2.

SRB1 setup

3.

NAS security setup (optional)

4.

RRC security + UE Capability Enquiry (UE Cap Enquiry optional)

5.

SRB2 + DRB setup (DRB optional in TAU)

Success phases counters 1-2 must be monitored from PRACH and RRCof signaling Success of phases 3-5 is monitored from S1AP and ERAB counters: ”S1 view” – s1 counters


© Nokia 2014

KPI /counter analysis from Air –Interface view


© Nokia 2014

1. PRACH phase, including Msg3 eNB

UE 1 PRACH MAC Random Access Preamble

M8001C6:RACH_STP_ATT_SMALL_MSG M8001C7:RACH_STP_ATT_LARGE_MSG M8001C286:RACH_STP_ATT_DEDICATED

2 PDCCH MAC RA-RNTI 2 PDSCH MAC Random Access Response 3 PUSCH RLC TM SRB0 RRC-ConnectionRequest 4 PDSCH MAC Contention Resolution NOTE: No counters for Msg4 in RL30

M8001C8: RACH_STP_COMPLETIONS

M8013C17:SIGN_CONN_ESTAB_ATT_MO_S M8013C18:SIGN_CONN_ESTAB_ATT_MT M8013C19:SIGN_CONN_ESTAB_ATT_MO_D M8013C20:SIGN_CONN_ESTAB_ATT_OTHERS M8013C21:SIGN_CONN_ESTAB_ATT_EMG

Analysis:

• LTE_138a RACH Setup Complete Success ratio indicates RAR blocking in scheduler only • To detect Msg2/Msg3 problems compare M8001C8 to sum of M8013C17-C21 • Compare drive test logs to Emil logs if Msg2 heard by UE • Compare drive test logs to Emil logs if Msg3 heard by eNB 15 13/12/2015 2 Confidential

© Nokia 2014

2. SRB1 setup phase Successful case eNB

UE 3 PUSCH RLC TM SRB0 RRC-ConnectionRequest

PDSCH RLC TM SRB0 RRC-ConnectionSetup

PUSCH RLC AM SRB1 RRC-ConnectionSetupComplete (NAS)

NOTE: • No RLC layer DL retransmissions in RRC Conn Setup •Default MCS and number of PRBs used.

M8007C7: SRB1 SETUP ATT

M8007C8: SRB1 SETUP SUCC M8013C5: SIGN_CONN_ESTAB_COMP

Analysis: • LTE_5a SRB1 setup Success Ratio


© Nokia 2014

2. SRB1 setup phase Unsuccessful Case 1 eNB

UE

3 PUSCH RLC TM SRB0 RRC-ConnectionRequest

SRB1 may be rejected due to: • Insufficient PUCCH resources Max • number of RRC connected users exceeded

RAC rejects RRC Connection Request M8013C8 SIGN_CONN_ESTAB_FAIL_RRMRAC PDSCH RLC TM SRB0 RRC Connection Reject


© Nokia 2014

2. SRB1 setup phase Unsuccessful case 2

eNB

UE 3 PUSCH RLC TM SRB0 RRC-ConnectionRequest PDSCH RLC TM SRB0 RRC-ConnectionSetup

PUSCH RLC AM SRB1 RRC-ConnectionSetupComplete (NAS) Erroneous or incomplete message


© Nokia 2014

M8013C7 SIGN_EST_F_RRCCOMPL_ERROR

2. SRB1 setup phase Unsuccessful Case 3 eNB

UE 3 PUSCH RLC TM SRB0 RRC-ConnectionRequest

NOTE: UE continues cell re-selection related measurements as well as cell re-selection evaluation until it receives RRC Conn Setup. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection during the procedure and silently disappears. Having some hysteresis for cell reselection may (or may not) help in reducing RRC setup problems.

PDSCH RLC TM SRB0 RRC-ConnectionSetup UE does not receive RRC Conn Setup and timer T300 expires, or UE reselects another cell. No response from UE (timer tHalfRrcCon)

M8013C6 SIGN_EST_F_RRCCOMPL_MISSING

• UE timer T300 (def=200ms) may expire if DL RRC Conn Setup reception fails • eNB has a vendor-file timer parameter for half-open RRC connections tHalfRrcCon (def=2000ms) to wait for RRC Conn Setup Complete from UE 15 13/12/2015 6 Confidential

© Nokia 2014

2. SRB1 setup phase Unsuccessful Case 3: Emil example

tHalfRrcCon expires after 2sec, TUP 15 13/12/2015 7 Confidential

© Nokia 2014

deletes user. NOTE: there is no RRC Connection to release

3. NAS security Successful Case start T3460 MME timer stop T3460 MME timer

start T3460 MME timer stop T3460 MME timer

eNB

UE

PDSCH RLC AM SRB1 NAS transfer (AUTH REQ)

PUSCH RLC AM SRB1 NAS transfer (AUTH RSP)

PDSCH RLC AM SRB1 NAS transfer (SEC CMD)

PUSCH RLC AM SRB1 NAS transfer (SEC CMP)

No RRC counters for NAS procedure failures Even if Auth or SecMod NAS procedure fails on NAS layer, it can still be successful from RRC pov Default T3460 is usually larger than radio link fail timers (3GPP default = 6sec),after which NAS retransmission follow 15 13/12/2015 8 Confidential

© Nokia 2014

4. RRC security Successful + Unsuccessful UE

eNB S1AP Init Ctxt Setup Req (NAS) PDSCH RLC AM SRB1 RRC Security Cmd PDSCH RLC AM SRB1 UE Cap Enquiry

PUSCH RLC AM SRB1 RRC Security Complete

3GPP: After this point RRC Conn ReEstablishment is possible for UE, since RRC security has been set up. If call drops after PRACH but before this point, then RRC Re-Est is not possible and UE makes cell reselection + TAU Req if it drops the call.

PUSCH RLC AM SRB1 UE Cap Info

No RRC counters for this phase NSN implementation may send UE Capability Enquiry (if required) and RRC Connection Reconfiguration before receiving RRC Security Complete 15 13/12/2015 9 Confidential

© Nokia 2014

4. RRC security Unsuccessful Case UE

eNB

PDSCH RLC AM SRB1 RRC Security Cmd

S1AP Init Ctxt Setup Req (NAS)

rrcGuardTimer PDSCH RLC AM SRB1 UE Cap Enquiry

rrcGuardTimer

•rrcGuardTimer expires • eNB triggered RLF • RRC Conn Re-Est Reject S1AP Init Ctxt Setup Failure

RRC Guard Timer supervises • RRC Security Mode Command • UE Capability Enquiry • RRC Connection Reconfiguration • no RRC counters for expiry 16 13/12/2015 0 Confidential

© Nokia 2014

NSN BEARERMAN.957: If RRC Conn Re-Est Req received from UE before S1 context has been successfully set up, eNB shall abort the Initial Context Setup procedure by the S1AP message INITIAL CONTEXT SETUP FAILURE with cause “Radio Connection With UE Lost”. This includes the case when UE sends RRC Conn Re-Est to eNB, reestablishment is rejected

5. SRB2/DRB setup Successful Case eNB

UE PDSCH RLC AM SRB1 RRC Conn Reconf

M8007C0 DATA_RB_STP_ATT M8007C10: SRB2 SETUP ATT

M8007C1 DATA_RB_STP_COMP M8007C11: SRB2 SETUP SUCC

PDSCH RLC AM SRB1 RRC Conn Reconf Complete

S1AP Init Ctxt Setup Response

Analysis: • LTE_5003a Data Radio Bearer Setup Success Ratio 16 13/12/2015 1 Confidential

© Nokia 2014

5. SRB2/DRB setup Unsuccessful Case eNB

UE PDSCH RLC AM SRB1 RRC Conn Reconf

M8007C0 DATA_RB_STP_ATT M8007C10: SRB2 SETUP ATT rrcGuardTimer, default =2000ms M8007C2 DATA_RB_STP_FAIL M8007C12 SRB2_SETUP_FAIL •rrcGuardTimer expires • eNB triggered RLF •UE RRC Conn Re-Est Reject

S1AP Init Ctxt Setup Failure

• M8007C0 is triggered for incoming Handover in case of a successful handover preparation procedure indicated e.g. by the transmission of the HANDOVER REQUEST ACKNOWLEDGE message. • M8007C2 triggered also when Data Radio Bearers failed to setup during incoming Handover at the target cell, unsuccessfully completed Handover Execution phase at the target eNB (e.g. expiration of TS1Relocexec/Tx2Relocexec). 16 13/12/2015 2 Confidential

© Nokia 2014

KPI/Counter analysis from S1 point of view


© Nokia 2014

S1 Context Setup Successful Case eNB

MME

RRC Connection Setup 1 S1AP Init UE Message (NAS)

M8000C12 UE_LOG_S1_SETUP

NAS security 2 S1AP Init Ctxt Setup Req (NAS) M8000C0 INI_CONT_STP_REQ M8006C0 EPS_BEARER_SETUP_ATTEMPTS

RRC security SRB2 + DRB setup

3 S1AP Init Ctxt Setup Response

Analysis: • LTE_5009a S1 Initial Context Setup Success Ratio • LTE_5017a E-RAB Setup Success Ratio 16 13/12/2015 4 Confidential

© Nokia 2014

M8000C1 INI_CONT_STP_COMP M8006C1 EPS_BEARER_SETUP_COMPLETION S

S1 Context Setup Unsuccessful Case 1 eNB

M8000C12 UE_LOG_S1_SETUP MME M8000C0 INI_CONT_STP_REQ M8006C0 EPS_BEARER_SETUP_ATTEMPTS

RRC Connection Setup 1 S1AP Init UE Message (NAS) NAS security 2 S1AP Init Ctxt Setup Req (NAS) RRC security

failure

SRB2 + DRB setup 3 S1AP Init Ctxt Setup Failure

Analysis:

M8000C2 INI_CONT_STP_FAIL_RNL M8000C3 INI_CONT_STP_FAIL_TRPORT M8000C4 INI_CONT_STP_FAIL_RESOUR M8000C5 INI_CONT_STP_FAIL_OTHER

M8006C2 EPS_BEARER_SETUP_FAIL_RNL M8006C3 EPS_BEARER_SETUP_FAIL_TRPORT M8006C4 EPS_BEARER_SETUP_FAIL_RESOUR M8006C5 EPS_BEARER_SETUP_FAIL_OTHER

• LTE_5096a E-UTRAN S1 Initial Context Setup Failure Ratio per Cause OTH • LTE_5095a E-UTRAN S1 Initial Context Setup Failure Ratio per Cause RESOURC • LTE_5094a E-UTRAN S1 Initial Context Setup Failure Ratio per Cause TRPORT • LTE_5093a E-UTRAN S1 Initial Context Setup Failure Ratio per Cause RNL 16 13/12/2015 5 Confidential

© Nokia 2014

S1 Context Setup (RL30) Unsuccessful Case 2 eNB

MME

RRC Connection Setup 1 S1AP Init UE Message (NAS)


eNB receives no response from MME for time period defined by tEstS1Con S1 + SRB1 released

• vendor file parameter
16000
• unit: milliseconds

Analysis: • No counter available for the number of S1 connection setup timer expirys (available after RL40) • Can compare M8000C12 UE_LOG_S1_SETUP and M8000C0 INI_CONT_STP_REQ • Need to analyze with Emil 16 13/12/2015 6 Confidential

© Nokia 2014

S1 Context Setup(RL30) Unsuccessful Case 3 MME

eNB RRC Connection Setup 1 S1AP Init UE Message (NAS)


NAS security Call drops at air interface

Analysis: • No eNB counters available (available after RL40) • Can compare M8000C12 UE_LOG_S1_SETUP and M8000C0 INI_CONT_STP_REQ • Need to analyze with Emil 16 13/12/2015 7 Confidential

© Nokia 2014

S1 Context Setup Unsuccessful Case: Emil example

tEstS1Con timer expires after 16 sec 16 13/12/2015 8 Confidential

© Nokia 2014

RRC release

S1 Context Setup Unsuccessful Procedure (No response from MME)


© Nokia 2014

S1 Context Setup Unsuccessful Procedure (MME Failure)


© Nokia 2014

RRC Connection Establishment Procedure T300

• The UE initiates the RRC connection establishment procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE state. • UE L3 sends RRC Connection Request to lower layers (L2/L1) which are responsible for preamble sending and RA response monitoring and starts timer T300 which supervises the RRC connection establishment procedure. – Start: Transmission of RRCConnectionRequest. – Stop: Reception of RRCConnectionSetup or RRCConnectionReject message, cell re-selection and upon abortion of connection establishment by upper layers. – In case of T300 (200ms) expiry the UE will stop RRC Connection Establishment procedure and informs higher layer about failed procedure (T300 = preambTxMax*20ms+ harqMaxMsg3 *raContResoT).


© Nokia 2014

T300 : started when UE L3 sends RRC Connection Request to L2/L1 and stopped in case of RRC Connection Setup or RRC Connection Reject is received

UE

eNB

RRC Connection Request RA Preamble RA Response Contention Resolution RRC Connection Setup

Random Access Procedure RA Preamble -

In case of initial access the contention based RA procedure is used, i.e. Random Access preamble is selected by the UE from available PRACH contention based preamble signatures on a cell (raNondedPreamb =40).

-

A preamble transmission power is determined as follows: • PPRACH = min{P CMAX , preambleInitialReceivedTarg etPower + DELTA_PREAMBLE (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerR amping S tep + PL} [dBm]

+

-

PCMAX is the configured UE transmitted power.

-

PL is the downlink path loss estimate calculated by the UE.

-

preambleInitialReceivedTargetPower is defined by parameter ulpcIniPrePw = -90 dBm.

-

powerRampingStep is defined by parameter prachP wrR amp = 2 dB. DELTA_PREAMBLE is as per 3GPP 36.321 and given by the prachC onfIndex = 3 means preamble format 0 i.e. DELTA_PREAMBLE = 0. UE

eNB RA Preamble (msg1) RA Response (msg2)


© Nokia 2014 RRC Connection Request (msg3)

Random Access Procedure RA Response (1/3) •

Once the Random Access Preamble is transmitted, and of the possible occurrence of a measurement gap, the UE the PDCCH for Random Access Response(s) identified by the RA-RNTI.

•

The UE may stop monitoring for Random Access Response(s) after successful reception of a Random Access Response containing Random Access Preamble identifiers that matches the transmitted Random Access Preamble. UE

regardless monitors

eNB

RRC Connection Request RA Preamble

5 TTI (5 ms) waiting time for the RA response from sending the corresponding RA preamble defined by parameter raRespWinSize (3 internal value)


© Nokia 2014

RA Response

3TTI delay 36.321

processing by 3GPP


The RA Response is sent on PDSCH informed by PDCCH DCI 1A.

•

PDCCH aggregation level is set by parameter pdcc hA g g R ares p = 4 (default).

•

The PDSCH message for RA Response is sent using QPSK modulation and default coding rate set by parameter maxC rR aDl = 0.12 (default) – The 48bit RA response (+header = 7B = 56bit) has to use very low coding rate due to the very small amount of bits (turbo coding efficiency is greatly degraded). – PDSCH HARQ is performed normally based on harqMaxTrDl = 4. UE

eNB

RRC Connection Request RA Preamble

5 TTI (5 ms) waiting time for the RA response from sending the corresponding RA preamble defined by parameter raRespWinSize (3) 17 13/12/2015 4 Confidential

© Nokia 2014

RA Response

3TTI processing delay by 3GPP 36.321


In case the UE does not receive RA response within the specified window then the UE will reattempt and send the new RA preamble with a higher power.

•

The new preamble can be transmitted earliest (from the last sent preamble) 3 TTI+ raRespWinSize (5TTI) + 4TTI (3GPP 36.213) = 12 TTI and with the prachC onfIndex =3 this means after 20 ms from the first preamble. -

The single PRACH resource (1 subframe) per 10 ms radio frame prachC onfI ndex = 3.

-

Random access response window size raR espWinSi ze = 5 TTI.

-

The entire preamble retransmission time (in case no response) is preambTxMax*20ms=10*20ms = 200ms UE eNB 5 TTI (5 ms) waiting time for the RA response from sending the corresponding RA preamble defined by parameter raRespWinSize (3)

If no random access response is received ,the UE shall transmit a new preamble sequence no later than in subframe n+4 (36.213) 17 13/12/2015 5 Confidential

© Nokia 2014

RRC Connection Request RA Preamble RA Response

RA Preamble (retransmission)


Random Access Procedure Message 3 •

The RRC Connection Request (msg3) is the first message sent over the PUSCH and thus, UL power control settings need to be set appropriately in order to maximize Msg3 decoding reliability.

    sg3   j PPUSCH Msg3  minPCMAX ,10 logM PUSCH i   ulpcIniPrePwr   PREAMBLE_M - PCMAX is maximum allowed UE power (23 dBm for class 3).

 PL  TF

i

 preamble

power ramp up   Msg2 

-

MPUSCH: number of scheduled RBs (UE Tx power increases proportionally to # of PRBs).

-

ulpcIniPrePwr (-90 dBm) is preamble initial received power.

-

ΔPREAMBLE_Msg3 allows for boosting of the UL power for Msg3 transmission by parameter deltaPreMsg3 (0 dB).

-

a(j) = path loss compensation factor defined by ulpcAlpha (1).

-

PL: pathloss [dB] = referenceSignalPower – higher layer filtered RSRP

-

ΔTF(i) enables TB size impact to UE PUSCH power calculation deltaTfEnabled (false)

-

Prampup is the total power ramp-up from the first to the last preamble i.e. the total power ramping until the preamble is acknowledged by the RA response.

-

ΔMsg2 is given by RA response TPC field according to the ulpcRarespTpc (0)

UE

eNB RA Preamble RA Response


© Nokia 2014

RRC Connection Request

The message 3 can actually be a RRC Connection Request, RRC Connection Reconfiguration complete (HO) or RRC Connection Re-Establishment depending on the cause that initiated the RACH procedure

Random Access Procedure Contention Resolution (1/2) •

Once RRC Connection Request (msg3) has been transmitted, the UE starts Contention Resolution Timer and restart timer at each HARQ retransmission. – the maximum content resolution timer parameter defines the maximum amount of time allowed for contention resolution, raContResoT (32ms). – harqMaxTrDl (4) indicates the maximum number of HARQ transmissions in DL. The HARQ delay is 8ms including some 0.6ms UE processing delay so 4 retransmissions equal 4*9ms=36 ms which covers the Contention Resolution timer 40 ms. UE

eNB RA Preamble

7 TTI (7 ms) waiting time for the RA response Once RRC Connection Request (msg3 of RA Procedure) has been transmitted, the UE starts Contention Resolution Timer raContResoT (32ms) 17 13/12/2015 7 Confidential

© Nokia 2014

RA Response RRC Connection Request Contention Resolution


Random Access Procedure Contention Resolution (2/2) • The CQI reporting is started when measurements are configured in RRC Setup message and therefore the contention resolution message is sent in DL using default QPSK modulation and coding rate. • Used coding rate is defined by parameter maxCrRa4Dl , def 0.39, this default value is higher (less channel coding) compared to the same size RA response (maxCrRaDl = 0.12) and the default has been changed from 0.12 to 0.39 recently in order to improve DL throughput. • The maxCrRa4Dl could be reduced to the same value as maxCrRaDl = 0.12 to improve the detection of Contention Resolution message. • Negative impact (1 PRB -> 3 PRBs reserved for CT) will be slight reduction in DL throughput (but net effect can be positive due to less resources reserved due to less overlapping reservations).


© Nokia 2014

Content




© Nokia 2014

Parameters related to call setup MO

par amet er full name

LNCEL

parameter short name

Preamble initial ulpcIniPrePwr received target power

LNCEL

TPC command in random access response

LNCEL

Delta preamble random deltaPreMsg3 access message 3

LNCEL

Enabled TB size impact to UE PUSCH power deltaTfEnabled calculation

LNCEL

Maximum number of message 3 HARQ transmissions


© Nokia 2014

ulpcRarespTpc

harqMaxMsg3

descr ipt ion

The parame ter defines the initial power for Random Access preamble transmission.

PDDB default

valuer ange -120 dBm -114 dBm -108 dBm -102 dBm (11), dBm (14),

dBm (0), -118 (1), -116 dBm dBm (3), -112 (4), -110 dBm dBm (6), -106 (7), -104 dBm dBm (9), -100 (10), -98 dBm -96 dBm (12), (13), -92 dBm -90 dBm (15)

TPC command indicated in the Random Access response related to Random Access -6...8 dB, step 2 dB message 3 or 1st scheduled uplink transmission. Used for the calculation of P0_NOMINAL_PUSCH(j=2) for PUSCH (re)transmission -1...6,step1 corresponding to the random access response grant. Enabling/disabling of the transport format depende nt offset on a per UE basis. If this parameter is enabled, PUSCH power calculation in UE uplink ower control e uation P1 Indicates the maximum number of HARQ transmissions used for message 3 of the contention1...8,step1 based random access procedure.

(2), (5), (8),-104 dBm (8)

-94

0 dB

1

false

5

Parameters related to call setup LNCEL

Maximum number of HARQ transmission in UL

harqMaxTrUl

Indicates the maximum number of HARQ transmissions in UL that is 1...7,step1 configured for each UE at initial access to a s pecific cell.

5

LNCEL

Maximum code rate for random access maxCrRaDl message 2

The parameter defines the maximum code rate for random access procedure messages 2 0.05...0.5, st ep 0.01 (RA response). Th is maximum coderate is taken into account during PDSCH scheduling.

LNCEL

Maximum number of RRC connections

maxNumRrc

Maximum number of UEs in the cell with an established RRC connection.

LNCEL

Maximum number of out-of-sync indications

n310

This is the maximum number of consecutiv e "out of sync" n1 (0), n2 (1), n3 (2), indications received from lowern4 (3), n6 (4), n8 (5), layers. n10 (6), n20 (7) n1 corresponds to 1 and so on.

LNCEL

Maximum number of inn311 sync indications

0...840, step1

Maximum number of consecutive "in-sync" n1 (0), n2 (1), n3 (2), indications received from lowern4 (3), n5 (4), n6 (5),

0.12

300

-

-

layers. n1 corresponds to 1 and so on.n8 (6), n10 (7)

LNCEL

LNCEL


The parameter defines default aggregation for UE to be used PDCCH LA UE default in PDCCH Link Adaptation pdcchAggDefUe 1 (0), 2 (1), 4 (2), 8 (3) 4 (2) aggregation when enableAmcPdcch has been disabled or when enableAmcPdcch has been The parameter defines the reserved number of Cont rol PDCCH aggregation for Channel Elements (CCEs) for pdcchAggMsg4 4...8,step4 4 RA msg4 dedicated Random Access Message 4 assingment on PDCCH.

© Nokia 2014

Parameters related to call setup


LNCEL

PDCCH aggregation for pdcchAggRares random access p response message

PDCCH aggregation for Random Access response message defines how many CCEs are used for one PDCCH.

LNCEL

PRACH c yclic sh ift

prachCS

Preamble cyc lic s hift defines the configuration which is used for preamble generation. The 0...15,step1 configuration determines how many cycl ic s hifts are needed to generate preamble.

LNCEL

Power ramping step

prachPwrRamp

The power ramping step size parameter defines the power increment s tep size for Random Access preamble transmission.

0dB (0), 2dB (1), 4dB (2), 6dB (3)

LNCEL

Preamble transmission preambTxMax maximum

The preamble transmission maximum defines the maximum number of Random Access transmissions. Note: The values n50, n100 and n200 should not be used.

3 (0), 4 (1), 5 (2), 6 (3), 7 (4), 8 (5), 10 (6), 20 8 (5) (7), 50 (8), 100 (9), 200 (10)

LNCEL

Large size random access MCS in uplink

raLargeMcsUl

Defines the Modulation and Coding Scheme (MCS) to be used for large size random access message 3 in case of initial access or handover.

0...15,step1

LNCEL

RA message power offset for group B selection

raMsgPoffGrB

LNCEL

Number of random access preambles

© Nokia 2014

4...8,step4

4

12

2dB (1)

5

Path loss threshold in dB required for selecting one of the-infinity (0), 0 dB (1), 5 two groups of Random Access dB (2), 8 dB (3), 10 dB 10 dB (4) (4), 12 dB (5), 15 dB preambles. (6), 18 dB (7) The UE will only use preambles from group B if it This parameter determines the 4 (0), 8 (1), 12 (2), 16 total number of non-dedicated (3), 20 (4), 24 (5), 28 raNondedPream RA preambles that a UE can (6), 32 (7), 36 (8), 40 40 (9) b select from (i.e. for contention (9), 44 (10), 48 (11), 52 based RA). The minimum (12), 56 (13), 60 (14), cannot be zero. 64 (15)

Parameters related to call setup LNCEL

Random access preambles group A size

raPreGrASize

4 (0), 8 (1), 12 (2), 16 (3), 20 (4), 24 (5), 28 Defines the size of the Random (6), 32 (7), 36 (8), 40 32 (7) Acc ess preambles Group A. (9), 44 (10), 48 (11), 52 (12), 56 (13), 60 (14)

LNCEL

Random access response window siz e

raRespWinSize

Random Access Response Window Siz e parameter 2 (0), 3 (1), 4 (2), 5 (3), defines the window size for the 6 (4), 7 (5), 8 (6), 10 10 (7) random access response in (7) TTIs.

LNCEL

Small size random access MCS in uplink

raSmallMcsUl

Defines the Modulation and Coding Scheme (MCS) to be used for the small size random access message 3 in case of UL or DL data arrival.

0...15,step1

LNCEL

Small size random access data volume in uplink

raSmallVolUl

Defines the data volume to be used for small size Random Acc ess message 3 in c ase of UL or DL data arrival.

56 bits (0), 144 bits (1), 208 bits (2), 256 bits (3)

Timer T300 supervises the RRC connection establishment procedure. Start: Transmission of LNCEL

TimerT300

t300

LNCEL

TimerT310

t310


© Nokia 2014

RRCConnectionRequest Stop: Reception of RRCConnectionSetup or RRCConnectionReject message, cell re-selection and upon abortion of connection establishment by upper layers At ex piry: P erform the actions Timer T310 supervises the recovery from physic al layer problems.

5

144 bits (1)

100ms (0), 200ms (1), 300ms (2), 400ms (3), 600ms (4), 1000ms (5), 1500ms (6), 2000ms (7)

0ms (0), 50ms (1), 100ms (2), 200ms (3), 500ms (4), 1000ms (5), 2000ms (6)

-

-

Content




© Nokia 2014

Project Example – LTE Project in APAC RRC Connection Establishment – Failure Rate • Project was carried out during main roll out phase, around 200 sites are on air.

RRC Connection Setup Failures LTE_5229b RRC Connection Setup Failure Ratio due to "RRC timer expiry" failure (%) LTE_5231b RRC Connection Setup Failure Ratio per Cause RRM RAC (%) LTE_5230B RRC Connection Setup Failure Ratio per Cause RRC Setup Complete Error (%) LTE_5218c RRC Connection Setup Success Ratio (%)

• The majority of RRC connection establishments are successful on PLMN level but there are still few failures due to no response to RRC setup message.

0.60

100.20

0.50

100.00

0.40

99.80

) % ( e r 0.30 u li a F

99.60

methods • Parameter changes has done as described in next slides

0.20

99.40

0.10

99.20

• Managed to improve the RRC connection establishment SR.

0.00

99.00

• Analysis has done using different


© Nokia 2014

) % ( s s e c c u S

Parameter Recommendations – DL • The following parameter settings are recommended to reduce RRC setup failures due to DL issues. Parameters

Current

raRespWinSize

5 (3)

MaxCrRa4Dl

0.39

harqMaxTrDl

4

Range

Description

2 (0), 3 (1), 4 (2), 5 (3), 6 (4),Random Access Response Window Size parameter defines the 7 (5), 8 (6), 10 (7) window size for the random access response in TTIs.

0.05...0.5, step 0.01

1…16, step 1

The parameter defines the maximum code rate for random access procedure messages 4 (SRB0 message). This maximum code rate is taken into account during PDSCH scheduling. The value 0.05 would be optimal and thus, it should be tested in live network as well in order to further improve RRC setup success rate. The maximum number of HARQ transmissions in DL that is configured for each UE at initial access to a specific cell. The

recommendation is to allow more transmissions of contention resolution message . The maximum amount of time allowed for contention resolution. 8ms (0), 16ms (1), 24ms (2), The HARQ delay is 8ms + 0.6ms for UE processing delay and thus, raContResoT 32ms (3) 32ms (3), 40ms (4), 48ms in case harqMaxTrDl is increased 4->7 the raContResoT should be (5), 56ms (6), 64ms (7) increased accordingly to 7*8.6ms = 60.2 ms => 64ms 100ms (0), 200ms (1), Timer T300 supervises the RRC connection establishment 300ms (2), 400ms (3), procedure. T300 should be set according to preambTxMax*20ms T300 200ms (1) 600ms (4), 1000ms (5), + harqMaxMsg3*raContResoT = 10*20ms+5*64ms = 520ms -> 1500ms (6), 2000ms (7) T300 = 600ms (4). 13/12/2015 © Nokia 2014

18 6 Confidential

Recommendation 7(5)

0.12

7

64ms (7)

600ms (4)

Parameter Recommendations – UL • The following parameter settings are recommended to reduce RRC setup failures due to UL issues. Parameters

Current

Range

Description

Recommendation

-120 dBm (0), -118 dBm (1), -116 dBm (2), -114 dBm (3), -112 dBm (4), The parameter defines the initial power for Random Access -110 dBm (5), -108 dBm (6), -90 dBm preamble transmission. The recommendation is to reduce ulpcIniPrePwr -106 dBm (7), -104 dBm (8), -102 -110 dBm (5) (15) the PRACH interference generation by reducing the PRACH dBm (9), -100 dBm (10), -98 dBm initial power . (11), -96 dBm (12), -94 dBm (13), -92 dBm (14), -90 dBm (15) The power ramping step size parameter defines the power increment step size for Random Access preamble prachPwrRamp 2 dB (1) 0dB (0), 2dB (1), 4dB (2), 6dB (3)transmission. The rachPwrRamp from 2dB to 4dB is 4 dB (2) recommended to have faster rampup due to decreased PRACH initial power. The maximum number of HARQ transmissions harqMaxMsg3 3 used for message 3 of the contention-based random access 5 1…8, step 1 procedure. Used for the calculation of P0_NOMINAL_PUSCH (j=2) = last deltaPreMsg3 0 dB (1) 1…6, step 1 (1 corresponds 0 dB) preamble power + deltaPreMsg3 for PUSCH (re)transmission 4 dB (2) corresponding to the random access response grant. The maximum number of HARQ transmissions in UL that is configured for each UE at initial access to a harqMaxTrUl© Nokia 2014 5 1…7 7 18 13/12/2015 specific cell. The parameter is aligned with DL HARQ 7 Confidential transmissions.

PUCCH Configuration

• The following parameters are recommended for PUCCH configuration. Parameters

nCqiRb

1

cqiperNp n1pucchAn

deltapucchshift cellSrPeriod prachFreqOff

maxNrSymPdcch 18 13/12/2015 8 Confidential

Current

Range

1...98

Description

Number of PRBs dedicated to Formats 2.x

2ms (0), 5ms (1), 10msPeriodicity of periodic CQI / PMI feedback on PUCCH or 20 ms (3) (2), 20ms (3) PUSCH AckNack index offset relative to the lowest CCE index of the 36 10...2047 associated DL scheduling PDCCH, i.e. offset to decide the number of resources reserved for SRI . Maximum number of cyclic shifts allowed for Formats 2 1…3 1/1a/1b 20 ms (2)5ms 10ms 20ms (2), (0), 40ms (3), (1), 80ms (4)Scheduling Request periodicity in the cell. 3

3

© Nokia 2014

0...94, step 1

1…3

Recommendation 1 20 ms 18 2 20 ms

First physical resource block available for PRACH in the UL system frequency band. Roundup [PUCCH resources/2]

3

The parameter defines how many OFDM symbols are used for PDCCH channel transmission. In RL20 eNB uses fixed value for each TTI but in RL30 the PDCCH allocation is dynamic depending on the load.

3

Radio Admission Control • RAC thresholds for the maximum number of RRC connected users and the active (DRB) users in a cell can be aligned with the configured PUCCH capacity. Parameters

Current

maxNumRrc

240

Range

0...840

Description The number of RRC-connections established in the cell cannot exceed maxNumRrc. RAC shall always be invoked for the admission of SRB1 at RRC Connection Setup. An RRC connection is considered as established if the SRB1 has been admitted and successfully configured. Maximum number of RRC connections (maxNumRrc) is to be set to a higher value (or equal) than maximum number of active UEs in the cell: maxNumActUE + max [addAUeRrHo, addAUeTcHo] <= maxNumRrc.

Recommendation

120

The RAC will check this condition for the admission of the single non-GBR DRB at S1AP: Initial Context Setup. A UE is termed active if at least one single nonmaxNumActUE

80

maxNumQci1Drb

100

maxNumActDrb

360


© Nokia 2014

0...840 GBR data radio bearer has been successfully configured for it. The number of active UEs in the cell cannot exceed: maxNumActUE + max[addAUeRrHo (15), addAUeTcHo (20)] 0…200

0...4200

100

Threshold for the maximum number of established QCI1-GBR-DRBs in the cell. maxNumQci1Drb must be equal or less than maxNumActUE .

100

Threshold for the maximum number of established DRBs in the cell. maxNumActDrb must be equal or greater than m axNumActUE.

360

Usage Based PDCCH Adaptation

• The number of PDCCH symbols is adaptively adjusted based on the current load condition. • This will improve the end user DL throughput during small PDCCH load condition (few UEs to be scheduled). • The feature adjusts the number of PDCCH symbols per subframe (TTI), i.e. data region (PDSCH) is varying accordingly.


© Nokia 2014

[other examples]


© Nokia 2014

RRC Performance

E-UTRAN RRC Signalling LTE_753a RRC Con nec tion Establishment at tempts (#) 100.00

70.00

LTE_5220a RRC Succes s Ratio (%) 4 500 000

90.00

80.00

LTE_5218c RRC Conne ction Setup S ucc ess Ratio (%)

4 000 000

RRC completion success degraded due to initial context setup failures

3 500 000

3 000 000

60.00 2 500 000 50.00 2 000 000 40.00 1 500 000 30.00 20.00

10.00

0.00


© Nokia 2014

1 000 000

500 000

0

RRC Connection Release Failures

E-UTRAN RRC Connection Release Failures LTE_229b EPC Initiated RRC Release Ratio due RNL (%)

80.00

70.00

60.00

LTE_230b EPC Initiated RRC failure r atio du e Other ( %)

LTE_233b eNB Initiated, RR C release Failure ra tio RNL (%)

LTE_234b eNB Initiated, R RC releas e failure ratio, Other (%)

LTE_227B EPC Initiated norm al RRC Release Ratio ( %)

LTE_231b eNB Initiated, RR C relea se ratio, nor mal Rele ase (%)

Most of RRC release failures due to EPC with „other‟ reason caused by the initial context setup failure (see scenario).

70.00

60.00

50.00 50.00 40.00 40.00 30.00 30.00 20.00 20.00

10.00

10.00

0.00


0.00

© Nokia 2014

E-RAB Performance

E-UTRAN E-RAB LTE_5118aE-RAB Setup Attempts (#) LTE_5023b E -RAB Normal Relea se Ratio User Perspect ive (%) 100.00

LTE_5017aERAB Setup SuccessRatio ( %) LTE_5024b E -RAB Normal Release Ratio RAN View (%) 8 000 000

90.00 7 000 000 80.00

70.00

60.00

E-RAB setup success degraded due to initial context setup failures.

50.00

6 000 000

5 000 000

4 000 000

40.00 3 000 000 30.00 2 000 000 20.00 1 000 000 10.00

0.00


© Nokia 2014

0

E-RAB Setup Failures

E-UTRAN E-RAB Setup Failures LTE_5086a E-RAB set up failure ra tio, RNL (%) LTE_5088a E -RAB setup fa ilure ra tio, resources (%)

LTE_5087a E-RAB set up failure ra tio, TNL (%) LTE_5089a E -RAB setup fa ilure ra tio, other ( %)

LTE_5017a E-RAB Setup Success Ratio (%) 70.00

120.00

Most of E-RAB setup failures due to „other‟ reasons (see scenario)

60.00

100.00

50.00 80.00

40.00 60.00 30.00

40.00 20.00

20.00

10.00

0.00


0.00

© Nokia 2014

/

Initial Context Setup Failure – Scenario

• The initial context setup failure due to incorrect UE-AMBR = 0 setting. • The eNB rejects the S1AP: INITIAL CONTEXT SETUP REQUEST message because the both UE-AMBR in UL and UE-AMBR in DL have been set to 0 and thus, EPC initiates UE context release (RRC release) with cause “Semantic Error”. 19 13/12/2015 6 Confidential

© Nokia 2014

Content


- Vendor Report


© Nokia 2014

KPI Analysis Local analysis

Select the BTS Performance Management tool


© Nokia 2014

KPI Analysis Local analysis Select «Measurement Configuration»

Enable the «Measurement type»


© Nokia 2014

Specify the «Interval» for your measurement

KPI Analysis Local analysis 1. Select «Counters» for set your query

2. Sort by «Counter» or «time» for your query

5. Choose the «Counter» group to query 20 13/12/2015 0 Confidential

© Nokia 2014

3. Select the «presentation» type by graph or table 4. Select the «Object» for your query



© Nokia 2014



© Nokia 2014

KPI Analysis Local analysis To perform individual (intra or inter) handover analysis, select on the objects windows the relationship of your interest, and the KPI to query. The object structure is: Local cell ##### MCC ### MNC ## ECI ####### MCC ### MNC##


© Nokia 2014

KPI Analysis Local analysis To perform inter RAT handover analysis, select on the object windows the object with the following structure: Local cell ##### MCC ### MNC ## HOT ### TCID ##### MCC ### MNC ## On the counters windows, select the KPI to query by graph or table.


© Nokia 2014

Content


- Vendor Report


© Nokia 2014

PERFORMANCE REPORT SUMMARY (COCHABAMBA)


© Nokia 2014



© Nokia 2014



© Nokia 2014

PERFORMANCE REPORT SUMMARY (SANTA CRUZ)


© Nokia 2014



© Nokia 2014



© Nokia 2014

PERFORMANCE REPORT SUMMARY (NETWORK)


© Nokia 2014



© Nokia 2014



© Nokia 2014

PERFORMANCE REPORT AVAILABILITY (COCHABAMBA)


© Nokia 2014

PERFORMANCE REPORT AVAILABILITY (SANTA CRUZ)


© Nokia 2014

PERFORMANCE REPORT AVAILABILITY (NETWORK)


© Nokia 2014

PERFORMANCE REPORT ACCESSIBILITY (COCHABAMBA)


© Nokia 2014

PERFORMANCE REPORT ACCESSIBILITY (SANTA CRUZ)


© Nokia 2014

PERFORMANCE REPORT ACCESSIBILITY (NETWORK)


© Nokia 2014

PERFORMANCE REPORT RETAINABILITY (COCHABAMBA)


© Nokia 2014

PERFORMANCE REPORT RETAINABILITY (SANTA CRUZ)


© Nokia 2014

PERFORMANCE REPORT RETAINABILITY (NETWORK)


© Nokia 2014

PERFORMANCE REPORT MOBILITY (COCHABAMBA) –INTRA & INTER ENODEB HOSR


© Nokia 2014

PERFORMANCE REPORT MOBILITY (SANTA CRUZ) –INTRA & INTER ENODEB HOSR


© Nokia 2014

PERFORMANCE REPORT MOBILITY (NETWORK) –INTRA & INTER ENODEB HOSR


© Nokia 2014

PERFORMANCE REPORT MOBILITY (COCHABAMBA) –INTER RAT HOSR


© Nokia 2014

PERFORMANCE REPORT MOBILITY (SANTA CRUZ) –INTER RAT HOSR


© Nokia 2014

PERFORMANCE REPORT MOBILITY (NETWORK) –INTER RAT HOSR


© Nokia 2014

PERFORMANCE REPORT MOBILITY (COCHABAMBA) –CSFB


© Nokia 2014

PERFORMANCE REPORT MOBILITY (SANTA CRUZ) –CSFB


© Nokia 2014

PERFORMANCE REPORT MOBILITY (NETWORK) –CSFB


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (COCHABAMBA) –AVERAGE PDCP THROUGHPUT


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (SANTA CRUZ) –AVERAGE PDCP THROUGHPUT


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (NETWORK) –AVERAGE PDCP THROUGHPUT


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (COCHABAMBA) –MAX PDCP THROUGHPUT


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (SANTA CRUZ) –MAX PDCP THROUGHPUT


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (NETWORK) –MAX PDCP THROUGHPUT


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (COCHABAMBA) –AVERAGE QCI9 THROUGHPUT


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (SANTA CRUZ) –AVERAGE QCI9 THROUGHPUT


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (NETWORK) –AVERAGE QCI9 THROUGHPUT


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (COCHABAMBA) –AVERAGE DATA VOLUME


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (SANTA CRUZ) –AVERAGE DATA VOLUME


© Nokia 2014

PERFORMANCE REPORT INTEGRITY (NETWORK) –AVERAGE DATA VOLUME


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (COCHABAMBA) –AVERAGE OF MAX ACTIVE USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (SANTA CRUZ) –AVERAGE OF MAX ACTIVE USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (NETWORK) –AVERAGE OF MAX ACTIVE USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (COCHABAMBA) –TOTAL OF MAX ACTIVE USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (SANTA CRUZ) –TOTAL OF MAX ACTIVE USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (NETWORK) –TOTAL MAX ACTIVE USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (COCHABAMBA) –AVERAGE RRC CONNECTED USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (SANTA CRUZ) –AVERAGE RRC CONNECTED USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (NETWORK) –AVERAGE RRC CONNECTED USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (COCHABAMBA) –TOTAL AVERAGE RRC CONNECTED USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (SANTA CRUZ) –TOTAL AVERAGE RRC CONNECTED USERS


© Nokia 2014

PERFORMANCE REPORT UTILIZATION (NETWORK) –TOTAL AVERAGE RRC CONNECTED USERS


© Nokia 2014

Thank You!


© Nokia 2014

LTE Counters and KPIs

Recommend Documents