target kpi of evnt modified

8/8/2019 Target KPI of EVNT Modified

1/20

41732466.xls Security Level:

10/11/2010 HUAWEI Confidential Page1of20

General Con

(6) The UE transmit p

The given Target Valsuggestions) on plannnetwork planning or nconditions should be

(1) If external factors (- Force Majeure (inclu- Facilities and Servic- Hardware or softwar- 3rd party (products,Network, 2G Existing- Network Resource C- Interference caused- Equipment failures cwhich are not attributdiscarded in case that

(2) The following itemmethodology/conditio

(3) Network performasystem parameters a

(4) Eliminate the redutest (with E1 direct co

(5) The RF conditionsconditions of at leastthe specific CS and Pbe low.

(7) The failure causedfacility and by networ


2/20

41732466.xls Security Level:

10/11/2010 HUAWEI Confidential Page2of20

traints

ower, Iub bandwidth, and other resources are not limited.

e can be met only when Huaweis suggestions (for example, the site addition suggestions or RF adjustmenting, implementation, and optimization are completely followed. Especially, if the customer does not purchase Huaweietwork optimization services, Huawei shall not make commitments to the network KPIs. The general applicableet forth as follows:

such asding but not limited to wars, riots, explosions, terrorist activities or natural disastersproducts),s not included in the responsibility matrix or Supply Contract,

e problems caused by non-Huawei design and planning,acilities or services) non-performance or problems, for example, problems caused by non-Huawei Terminal, CoreNetwork, PSTN and Transmission, which have a direct impact on KPIs ,ongestion (for example, Burst Traffic or Network capacity expansion, which exceeds the planned capacity),by other mobile telecommunications systems or radio systems,aused by unauthorized actions),ble to Huaweis fault, adversely affect the performance of the KPIs, the measurement failure data should bethe KPI measurement result is affected.

s shall be negotiated and agreed upon between both sides: KPIs definitions, test routes, test equipment, test, and test time.

ce greatly benefits from the proper settings of system parameters, so Huawei shall have full control to specify alld configurations.

ndant Iub delay. Huawei will compare the Iub Node Synchronization Procedure delay obtained through Huawei labnnection) with that of the commercial network. The redundant delay of commercial network shall be eliminated.

of each KPI shall follow Huaweis comments and the traffic volume shall be low. The Field Test are performed in theSCP > -95dBm and Ec/Io > -14dB (for Static Test, there shall only be one serving cell with good RF environment),

S services of testing for KPIs must base on the continuous coverage service in this testing area and the traffic shall

by external equipments to the Huawei system, by admission failure, by congestion, by UE, by unstable transmissionfaults shall be eliminated. The test result will be an average KPIs performance of busy hour for at least one week.


3/20

Item Service Method of Performance Measuremen

Accessibility

Call Setup Success Rate

Voice AMR 12.2

Driving Test

Video Phone

Call Setup Time

Voice AMR 12.2

stationary Test

Video Phone

PDP Context Activation Setup Time R99 PS

R99 PS


4/20

RTT / WCDMA Driving test

Ping test (32 Bytes) Driving test

PS RAB Establishment Succ Driving test

PS RAB Drop Driving test

RTT / HSxPA stationary Test

Ping test (32 Bytes)

Retain ability

CS Call Drop Rate

Voice AMR 12.2

Driving test

Video Phone

PS Call Drop Rate

R99 PS

HSDPA

Mobility

Soft handover Success Rate

Voice AMR 12.2

Video Phone


5/20

Hard handover Success Rate Video Phone

R99 PS

Average throughput DL/UL R99 PS Driving test

CPICH RSCP

Driving test

Ec/Io

Voice Call DL BLER


6/20

*HSDPA Session Activation time HSDPA

stationary Test

RRC Success Ratio

RAB Success Ratio, Voice (CSR)

Packet Session Success Ratio (SSR) [%]

MULTI-RAB AMR Voice CSSR during HSPA Call

AMR Voice CSSR during PS 64/64 call

HSPA CSSR during AMR Voice Call

PS 64/64 CSSR during AMR Voice call

other services SMS Success Rate

SMS Delivery Time < 40s WAP Failure Rate

WAP Session Estab. Elapsed Time < 13s

MMS Success Rate

MMS Delivery Time < 40s

Intra SGSN Routing Area Update Time

Cell Capacity

AMR


7/20

Explanation

(1) Call Setup Success Ratio = Number of originating call completions/Number of originating call requests x 100%(2) The number of originating call requests equals the number of RRC Connection Request messages sent by the originating call UEConnection Request messages are retransmitted.(3) The number of originating call completions equals the number of Alerting messages received by the originating call UE.(4) This counter can be manually measured if the signaling on the UE side cannot be recorded.(5) The access failures caused by network congestion or poor network coverage should not be taken into consideration.(6) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.(7) Drive test route and procedures to be mutually agree by both EVNT and Vendor.(8) Should test MOC and MTC

The defined time delay equals to: T(CC_Alerting) of Calling UE to T(first RRC Connection Request) of Calling UE.The test conditions should be as follows:(1) The calling and called UE should be stationary(2) The calling and called UEs are at the same RNC.(3) The abnormal delay caused by Non_RAN equipment should be eliminated.(4) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.

The defined time delay equals to: T(CC_Alerting) of called UE to T(first paging)The test conditions should be as follows:(1) The calling and called UE should be stationary(2) The calling and called UEs are at the same RNC.(3) The abnormal delay caused by Non_RAN equipment should be eliminated.(4) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.

The defined time delay equals to: T(CC_Alerting) of calling UE to T(first RRC Connection Request) of calling UEThe test conditions should be as follows:(1) The calling and called UE should be stationary(2) The calling and called UEs are at the same RNC.(3) The abnormal delay caused by Non_RAN equipment should be eliminated.(4) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.

The defined time delay equals to: T(CC_Alerting) of calling UE to T(first RRC Connection Request) of calling UEThe test conditions should be as follows:(1) The calling and called UE should be stationary(2) The calling and called UEs are at the same RNC.(3) The abnormal delay caused by Non_RAN equipment should be eliminated.(4) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.

The defined time delay equals to: T(Activate PDP Context accept)-T(Activate PDP Context Request)The test conditions should be as follows:(1) The calling and called UE should be stationary(2) The calling and called UEs are at the same RNC.(3) The abnormal delay caused by Non_RAN equipment should be eliminated.(4) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.(5) Test only choose PS384 mode.

(1) PDP Context Activation Success Rate = Number of successful PDP context activations/Number of PDP context activation reques(2) The number of PDP context activation requests can be defined as either of the following:

A. The number of RRC Connection Request messages (with the cause value of interactive service or background service) sent by Uregardless of how many times the RRC Connection Request messages are retransmitted.B. The number of Activate PDP Context Request messages sent by UEs.It is recommended that definition A be used.


8/20

CS call drop rate = (number of CS call drops)/(number of successful CS call connections)(1) Number of successful CS call connections: the number of Alerting messages received by UEs after service requests are sent.(2) Number of CS call drops: According to the Uu interface signaling on the UE side, during a call (connection state), if a Uu interfaceincreases by 1.a. The RRC Release message is not received, but the UE state is changed from CELL_DCH to IDLE.b. The RRC Release message is received and the release cause value is not Normal.c. One of the following messages is received: CC Disconnect, CC Release Complete, and CC Release. In addition, the release causalerting no answer, call rejected, or destination out of order.(3) The call drops caused by network congestion or poor network coverage should not be taken into consideration.(4) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.(5)Drive test route and procedures to be mutually agree by both EVNT and Vendor.

CS call drop rate = (number of CS call drops)/(number of successful CS call connections)(1) Number of successful CS call connections: the number of Alerting messages received by UEs after service requests are sent.(2) Number of CS call drops: According to the Uu interface signaling on the UE side, during a call (connection state), if a Uu interfaceincreases by 1.a. The RRC Release message is not received, but the UE state is changed from CELL_DCH to IDLE.b. The RRC Release message is received and the release cause value is not Normal.c. One of the following messages is received: CC Disconnect, CC Release Complete, and CC Release. In addition, the release causalerting no answer, call rejected, or destination out of order.(3) The call drops caused by network congestion or poor network coverage should not be taken into consideration.(4) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.(5)Drive test route and procedures to be mutually agree by both EVNT and Vendor.

(1) PS call drop rate = (number of PS call drops)/(number of successful PDP context activations) x 100%(2) Number of successful PDP context activations: the number of Activate PDP Context Accept messages received by UEs.(3) Number of PS call drops: According to the RRC signaling on the UE side, in the data service connection state, if a Uu interface m

increases by 1.Condition 1:The RRC Release message is not received, but the UE state is changed from the connection state (CELL_DCH, CELL_Condition 2: The RRC Release message is received and the release cause value is not Normal or User Inactivity.(4)The call drops caused by network congestion or poor network coverage should not be taken into consideration.(5)This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.(6)Drive test route and procedures to be mutually agree by both EVNT and Vendor.(7) Test only choose PS384 mode.

(1) PS call drop rate = (number of PS call drops)/(number of successful PDP context activations) x 100%(2) Number of successful PDP context activations: the number of Activate PDP Context Accept messages received by UEs.(3) Number of PS call drops: According to the RRC signaling on the UE side, in the data service connection state, if a Uu interface mincreases by 1.Condition 1:The RRC Release message is not received, but the UE state is changed from the connection state (CELL_DCH, CELL_Condition 2: The RRC Release message is received and the release cause value is not Normal or User Inactivity.(4)The call drops caused by network congestion or poor network coverage should not be taken into consideration.

(5)This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.

The measurement should be performed on the RNC side:(1) Success Rate = Number of successes/Number of attempts x 100%(2) Number of attempts equals the number of Active Set Update messages sent by the RNC.(3) Number of successes equals the number of Active Set Update Complete messages received by the RNC.(4)The soft handover failures caused by network congestion or poor network coverage should not be taken into consideration.(5) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.(6)Drive test (low speed) route and procedures to be mutually agree by both EVNT and Vendor.

The measurement should be performed on the RNC side:(1) Success Rate = Number of successes/Number of attempts x 100%(2) Number of attempts equals the number of Active Set Update messages sent by the RNC.(3) Number of successes equals the number of Active Set Update Complete messages received by the RNC.

(4)The soft handover failures caused by network congestion or poor network coverage should not be taken into consideration.(5) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.(6)Drive test (low speed) route and procedures to be mutually agree by both EVNT and Vendor.


9/20

(sum of transport_blocks with CRC_errors collected block errors /sum of transport_blocks) * 100

The measurement should be performed on the RNC side:(1) Success Rate = Number of Successes/Number of Attempts x 100%(2) Number of successes equals the number of physical channel reconfiguratioen complete messages received by the RNC. This typ(3) Number of attempts equals the number of physical channel reconfiguratioen request messages sent by the RNC. This type of me(4)The handover failures caused by network congestion or poor network coverage should not be taken into consideration.(5)The hard handover test should be performed within the same vendor's RAN equipment(6) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.(7)Drive test (low speed) route and procedures to be mutually agree by both EVNT and Vendor.

The measurement should be performed on the RNC side:(1) Success Rate = Number of Successes/Number of Attempts x 100%(2) Number of successes equals the number of physical channel reconfiguratioen complete messages received by the RNC. This typ(3) Number of attempts equals the number of physical channel reconfiguratioen request messages sent by the RNC. This type of me(4)The handover failures caused by network congestion or poor network coverage should not be taken into consideration.(5)The hard handover test should be performed within the same vendor's RAN equipment(6) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.(7)Drive test (low speed) route and procedures to be mutually agree by both EVNT and Vendor.

(8) Test only choose PS384 mode.

Average throughput of the 95% file transfered can be achieved at:a)Maxinum throughput >=300kbps for 384kbps bearer and average throughput>=280kbps for 384kbps bearerThe moving UE performs single-thread upload of large-sized file:(1) None of the uplink RTWP, lub bandwidth, and UE transmit power is limited. Uplink BLER 1%.(2) The moving tests should be performed in the cell where there is no other service(3) MTU = 1,500; size of TCP receive window on the server side 32 KB; DOS upload; file size = 10 MB.(5) This KPI can only be committed if the Radio Network Optimization Service are ordered by EVNT.

(1)The test should be performed with scanner.(2) KPI adjustment to be mutually agree by both EVNT and Vendor.(2) This KPI can only be committed if the Radio network design service and Radio Network Optimization service are ordered by EVN

(1) Based on the the bidding document, this KPI is the requirement for prelaunch optimization and hence the test should be performe(2) This KPI can only be committed if the Radio network design service and Radio Network Optimization service are ordered by EVN

(1) BLER target =0.5%,UL full rate transmission.(2)Test area coverage requirement: RSCP>=-90dBm, Ec/Io>=-10dB(3) No limitation in UL and DL TX power.(4)BLER caused by poor network coverage and call drop should not taken into account.(5)BLER caused by equipment out of RAN should not taken into account.

Suggest that the testing should be measured by in-car drive test with following conditions:a) Any external Failure by othere quipment or UE proven is excluded.b) Drive test route and procedures to be mutually agree by both EVNT and Vendor


10/20

a) CQT Measurement. Average per cluster and coverage area. 100MB file to be transferred. Application layer throughput.b)Under RSCP level >=-80dBm and Ec/Io >= -8dB.


11/20

Some definitions need to be clearly defined Suggestions of EVNT

poor network coverage?Which features and advanced options are the Radio Network

Optimization Service provided?At the point (4): This counter can be manually measured if the signalingon the UE side cannot be recorded. What does manually measured

means and the method to implement?

Formulas for calculation should be amended as the establishment succeradio access bearer (RABs) are included and taken into co

AMR CSSR: (Successful RRC setups (MOC Conversational Emergency Call) * Successful RAB setups for Conversationa(All RRC setup attempts (MOC Conversational + MTC ConveRAB setup attempts for Conversational with Source Descript

The abnormal delay caused by Non_RANequipment should be eliminated (failedhappened have nothing to do with RAN,for exmple, transmission have prolbemduring test- answered by Zhu)

- For Voice AMR 12.2 kbps : MTM: 95% of successful c- For VT : MTM: 95% of successful calls


12/20


13/20

formulas for counters and DT


14/20


15/20


16/20


17/20


18/20


19/20


20/20

target kpi of evnt modified

Documents