UMTS - Compressed MODE AND SOFT Handover

CDMA networks can use the same frequency in each cell and differentiated user through code. This means it's easier for the EU to decode the signals from more than one Node B simultaneously by way of de spreading the received radio signals single with M enggunakan some scrambling and channelisation codes are different. technique is used in CDMA to support a feature known as soft handover, which the EU can communicate with more than one Node B simultaneously when moving between cells in tissues. Soft Handover has a number of advantages compared to hard handover used in FDMA and TDMA systems such as TACS and GSM, in which simultaneous communication with more than one base station is not allowed. excellence first, soft handover between neighboring cells can be more reliable, because it allows the EU to establish communication with the target Node B before communication with the original cell is released - it is a 'make-before-break 'handover. establishment If a problem occurs with the target cell, the EU is still able to maintain communication with the network through the original cell. In systems, such as GSM, where handover 'break-before-make', there is always the possibility that MS is not able to make the link with cell targets and as a link to the original cell has been damaged, it would be difficult to re-establish links and possibilities can drop calls. Another advantage of soft handover is the ability to exploit macrodiversity gains between different Node Bs. Most cellular systems using multi-antenna diversity at the receiver base station and the newer cellular systems can also support the transmit antenna diversity at the base station transmitter. Technique 'microdiversity' is primarily aimed at reducing the effects of multipath fading and they have very little impact on the larger scale effects of the shadow fading. If MS can establish simultaneous connection to different Node B, then, given the spatial separation of Node B, each link is likely to experience the different characteristics of the shadow fading. By combining the information received on each individual link, the effect of shadow fading can be mitigated to a certain extent and it is called macrodiversity. UTRA FDD the system, soft handover is controlled by the active set, which contains all the Node Bs that are communicating with the EU. If the active set contains more than one Node B, the EU considered the soft handover. On the downlink, all Node Bs in the active set of the EU will send the same user data for the EU.UE will receive signals from each Node B and using combining techniques (eg maximal ratio combining) to determine the pattern of the transmitted data. On the uplink, the EU will continue sending a single uplink signal, but it will be accepted by more than one Node B at UE in soft handover. Each Node B will decode user data and sends it to the RNC. RNC will select data from Node B with the best quality in frameby-frame. This technique is known as switched diversity, the benefits that can be used to reduce the overall UE transmit power. If UE in soft handover between the two sectors of the same Node B, is known as softer handover and Node B can perform maximal ratio combining with uplink signals received at each sector. Though UTRA FDD system can support soft handover, must also have the ability to support hard handover. This handover type is required

when the UE moves between different CDMA radio frequency or the frequency of the same CDMA radio (eg moving from UTRA FDD to GSM). ======= Whilst this approach is relatively
straightforward from the network point of view, it adds a level of complexity to the terminal that, in many cases, would be unacceptable. Therefore, a second option exists whereby gaps are opened up in the downlink transmissions to give the EU an opportunity to retune to another radio channel and make a measurement .Unfortunately, the amount of data that must flow between the Node B and the UE in the downlink direction does not necessarily Decrease during the periods when these measurements are required and this means that the Node B must transmit at a higher data rate on either side of the measurement gaps to Ensure that the same amount of data can be transferred. This mode of operation is Referred to as compressed mode Because of the manner in roomates the Data is compressed into the transmission periods on either side of the measurement gap. The Simplest way to increase of the data transmission rate is to Decrease the channel spreading factor. For example, the spreading factor could be Decreased from 64 to 32, thereby doubling the channel throughput and allowing the Node B to operate with a 50% duty cycle transmission. Since the Decrease in spreading factor leads to a reduction in processing gain on the channel, the Node B will need to increase of the transmit power for a particular UE to compensate for this effect. Code puncturing may also be used as a means of increasing the user data rate without changing the spreading code. In this case, some of the coded data bits are not transmitted and the channel decoding process at the receiver is relied upon to recover these 'lost' bits.This is Similar to the situation that would occur if errors were imposed on these bits during transmission, but the receiver has the added advantage that it will know roomates data bits have been removed, whereas it does not usually know roomates bits Contain errors. This puncturing process has the effect of decreasing the error correcting capabilities of the channel coding (ie the power of the code) and this has a Similar effect to decreasing the processing gain, ie the Node B needs to allocate more power to the EU during the puncturing periods . In some cases, it may also be possible to Decrease the amount of data that is transmitted betweenthe Node B and the UE during periods when the UE must the make inter-frequency measurements. This requires the schedule for compressed mode operation to be communicated to the higher layers in the protocol stack and these higher layers then restrict the amount of information presented to the physical layer during compressed mode operation.

ISHO Analysis
Breakdown ISHO analysis into three phases:

Compressed mode performance (RNC_294c/RNC_295c) Inter-system measurement success (RNC_573c/RNC_574c) Inter-system handover success (RNC_300e / RNC_301d)

If high ISHO compressed mode start not possible Check busy hour data of PrxTotal , PtxTotal and M1000C22 AVE_PTXTOT_CLASS_4 and M1000C20 AVE_PTXTOT_CLASS_3 for AC rejection

If Low ISHO Measurement Success Rate (RNC_573c/RNC_574c) Check ADJG neighbour list for missing neighbours or existing neighbour performance (RNC_905a/RNC_902a)

Check parameter discrepancy (BSIC) or BSIC collision due to too tight reuse Check Compressed mode parameter set Check ISHO triggering Threshold too slow triggering

Check EcNo Distribution (M1007C38-M1007C47) or propagation delay counters (M1006) to indicate low coverage / interference problem If Low ISHO Success Rate (RNC_300e <95% / RNC_301d < 80%)

Check missing or wrong 2G parameter in MSC/SGSN (LAC, CellId, BCCH) Check discrepancy of Cell information in RNC Check 2G cell GPRS/EGPRS data congestion

May require further troubleshooting with ICSU logging to determine root cause of failure

HSDPA Retainability Analysis

1. Identify root cause failure distribution and main contributor of low retainability - RSRAN079 2. If high HSDPA Radio Link Failures (NRT) dominant cause Compare to Cell Update ATT due to Radio link Failure (M1006C39) and Cell Update ATT due to RLC Recoverable Error (M1006C40) Check Serving Cell Change failure rate (KPI RNC_733a) - high SCC failures lead to radio link failure -------> RSRAN079 Check CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue (M1007C38-M1007C47) --> RSRAN039 Check HSDPA FMCS Mobility Control Parameter (handover or SCC too late) Check call re-establishment T315 timer due to radio link failure 3. If high HSDPA Non- Radio Link Failures (NRL) UE responding with some failure message or not responding to some message but no RL failure (timer expiry) --> RSRAN038 Check RB reconfiguration, physical channel reconfiguration, NBAP RL reconfiguration failure rate Required ICSU log for further troubleshooting

HSDPA Retainability Failure Cause Analysis Flowchart

ISHO vs Failures
Beberapa penampakan Failure yang ada di KPI ISHO :

1. 2. 3. 4. 5. 6. 7. 8.

UTRAN_NOT_ABLE_EXEC_ISHHO_RT UE_NOT_ABLE_EXEC_ISHHO_RT UTRAN_NOT_ABLE_EXC_ISHHO_NRT UE_NOT_ABLE_EXEC_ISHHO_NRT UNSUCC_IS_HHO_UE_TRX_PWR_RT UNSUCC_IS_HHO_CPICH_ECNO_RT UNSUCC_IS_HHO_CPICH_RSCP_RT UNSUC_IS_HHO_UE_TRX_PWR_NRT

9. 10.

UNSUCC_IS_HHO_CPICH_ECNO_NRT UNSUCC_IS_HHO_CPICH_RSCP_NRT

1. UTRAN_NOT_ABLE_EXEC_ISHHO_RT Description: Number of inter-system handover failures for RT due to UTRAN. --- The failure can occur, for example, due to the following reasons: relocation preparation procedure failure in the CN, or relocation resource allocation procedure failure in the target BSC. Updated: When the hard handover attempt fails before the serving RNC sends the handover When the RNC receives an RANAP: RELOCATION PREPATION FAILURE message from the CN, or the RNC does not receive an RANAP: RELOCATION COMMAND message from the CN within a certain time period. This counter is updated only during inter-system handovers.

2. UE_NOT_ABLE_EXEC_ISHHO_RT Description : The number of times when during inter-system handover for RT the source RNC has ordered the UE to use a configuration which the UE does not support. --- If the source RNC instructs the UE to use a configuration that it does not support, the UE will send a failure message to the source RNC. The handover procedure ends and the UE resumes normal operation as if no handover attempt had occurred. Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE message from the UE, and the failure cause is "configuration unacceptable".

3. UTRAN_NOT_ABLE_EXC_ISHHO_NRT Description: The number of inter-system handover failures for NRT due to UTRAN. Updated: This counter is never updated.

4. UE_NOT_ABLE_EXEC_ISHHO_NRT Description: The number of times when during inter-system handover for NRT the source RNC has ordered the UE to use a configuration which the UE does not support. --- If the source RNC instructs the UE to use a configuration

that it does not support, the UE will send a failure message to the source RNC. The handover procedure ends and the UE resumes normal operation as if no handover attempt had occurred. Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILURE message from the UE, and the failure cause is "configuration unacceptable".

5. UNSUCC_IS_HHO_UE_TRX_PWR_RT Description: The number of unsuccessful inter-system handovers caused by UE transmission power for RT. --- If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had occurred. Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE message from the UE, and the failure cause is not "configuration unacceptable". This counter is updated only when the trigger reason is UE transmission power.

6. UNSUCC_IS_HHO_CPICH_ECNO_RT Description: The number of unsuccessful inter-system handovers caused by CPICH Ec/No for RT. --- If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had occurred. Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE message from the UE, and the failure cause is not "configuration unacceptable". This counter is updated only when the trigger reason is CPICH Ec/No.

7. UNSUCC_IS_HHO_CPICH_RSCP_RT Description: The number of unsuccessful inter-system handovers caused by CPICH RSCP for RT. --- If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had occurred.

Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE message from the UE, and the failure cause is not "configuration unacceptable". This counter is updated only when the trigger reason is CPICH RSCP.

8. UNSUC_IS_HHO_UE_TRX_PWR_NRT Description: The number of unsuccessful inter-system handovers caused by UE transmission power for NRT. --- If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had occurred. Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILURE message from the UE, and the failure cause is not "configuration unacceptable".

9. UNSUCC_IS_HHO_CPICH_ECNO_NRT Description: The number of unsuccessful inter-system handovers caused by CPICH Ec/No for NRT. --- If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had occurred. Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILURE message from the UE, and the failure cause is not "configuration unacceptable". This counter is updated only when the trigger reason is CPICH Ec/No.

10. UNSUCC_IS_HHO_CPICH_RSCP_NRT Description: The number of unsuccessful inter-system handovers caused by CPICH RSCP for NRT. --- If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had occurred.

Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILURE from the UE, and the failure cause is not "configuration unacceptable". This counter is updated only when the trigger reason is CPICH RSCP.

Cell Selection Parameters

QrxlevMin (A_WCEL) Description : The minimum required RX level in the cell. This parameter is also used to create value for the parameter DeltaQrxlevmin to be sent in SIB3/4 when the used value is < -115. Default value : -115 dBm QqualMin (A_WCEL) Description : The minimum required quality level in the cell (Ec/No) Default : -18 db UEtxPowerMaxPRACH (A_WCEL) Maximum UE transmission power on PRACH This parameter defines the maximum transmission power level a UE can use on PRACH. The value of the parameter also effects the cell selection and reselection procedures. The value of the parameter is sent to UE in the Cell selection and re-selection of System Information Blocks 3 and 4 of the serving cell. Default : 21 dBm

AAL2 resources availability in RNC (M800) RNC_602a

AAL2 resource reservation success rate [%] :

The transport resource request success ratio [%] KPI describes the average success rate of the transport resource reservation attempts for all AAL2 type connections

AAL2_SUCCEEDED - AAL2 signaling requests which have been successfully executed in A2SP

AAL2_REJECTED - AAL2 signaling requests which have failed for any reason. E.g. signaling failed or uplink CAC reject

RES_EXT_CAP - Transport resources requests which are rejected by downlink CAC since there is not enough capacity in the external AAL2 path.

RES_INT_CAP - Resource reservations which are rejected by downlink CAC since there are no RNC-internal AAL2 processing resources available

RES_OTHER - Resource reservations which have failed for any other reason than CAC or signaling (for example route analysis, parameter or DSP resource allocation problem)

Diposkan oleh Admin di 14.47 Tidak ada komentar: Kirimkan Ini lewat EmailBlogThis!Berbagi ke TwitterBerbagi ke Facebook SELASA, 24 JULI 2012

AAL2 Resource Reservation in RAN05 (M800)

M800 is useful for monitoring success of the resource reservation requests and able to point out different type of failures, such as

Lack of Iub bandwidth Lack of RNC capacity AAL2 signaling failure

M800 collects the statistics per AAL2 user plane VCC object, note that there can be several UP VCCs! The resource reservation is performed in such order that all CAC reservations for RNC internal and external (AAL2 path) resources are done before signaling If the CAC actions are successfully completed, the signaling is started and RNC asks BTS to arrange its resources accordingly If the CAC actions fail, the signaling phase is not started at all and the signaling counters are not aware of the connections rejected due to RNC AAL2 layer CAC

There are also dedicated counters for HSDPA connections resource reservations The object of the measurement is the AAL2 path selected with ATM interface ID/VPI/VCI identifiers The statistics for the whole RNC (sum of all configured AAL2 paths counters) are available by selecting the measurement object as interface-0/VPI-0/VCI-0 Also some failure situations, for example digit analysis failure, are updated only for 0/0/0 object because the actual VCI is not known

Diposkan oleh Admin di 23.35 Tidak ada komentar: Kirimkan Ini lewat EmailBlogThis!Berbagi ke TwitterBerbagi ke Facebook

Performance Measurements for Transport

Counter

Diposkan oleh Admin di 13.47 Tidak ada komentar: Kirimkan Ini lewat EmailBlogThis!Berbagi ke TwitterBerbagi ke Facebook SENIN, 09 APRIL 2012

SENIN, 24 OKTOBER 2011

UMTS -- CELL BREATHING AND SOFT CAPACITY

Cell breathing menggambarkan car perubahan coverage Node B dalam menanggapi perubahan pada load jaringan. Untuk menunjukkan efek ini analoginya adalah : UE dengan transmit power yang tetap berkomunikasi dengan Node B, signal dari UE diterima dan di decode di node B pada keadaan thermal noise saja. Jika UE bergerak menjauh dr Node B, sampai dimana kekuatan sinyal yg di terima Node B hanya cukup untuk mengatasi thermal noise dan mempertahankan quality link yg memadai. Pada titik ini kita bisa berasumsi UE berada di tepi Boundary sel . Jika kita menambah UE aktif kedua, UE ini akan menyebabkan interence di UE pertama di node B. Untuk mengatasi interferensi tambahan ini, UE pertama memberikan daya lebih untuk Node B, karena UE memiliki daya pancar yang tetap, ini hanya dapat dicapai dengan UE pertama bergerak lebih dekat ke Node B. Ketika UE pertama bergerak lebih dekat ke Node B, akan tercapai titik dimana sinyal kekuatan di Node B hanya cukup untuk mengatasi efek dari thermal noise dan intereference oleh UE kedua. Hal ini secara efektif menjadi batas sel baru. Semakin banyak UE ditambahkan ke sistem, UE pertama semakin ter interference, sehingga sel boundary bergerak lebih dekat ke Node B (menyusut / shrink). Sebaliknya, ketika UE meninggalkan sistem dan interferensi akan turun,dan sel boundary akan berkembang.

UMTS - its interface and architectur

5 new interface in UMTS: Cu: electrical interface between the USIM and ME Uu: Interface between UE and Node B Iu: Interface between the RNC to GSM phase 2 Iu-CS: for circuit-switched data Iu-PS: for packet-switched data Iub: Interface between Node B and RNC Iur: Interface between the RNC to another RNC architectur jaringa UMTS

Node B Node B can support both single mode FDD and TDD, and may be co-located with GSM base stations to reduce implementation costs. Node B is connected with the EU through the radio interface Uu W-CDMA and the RNC via the Iub interface of asynchronous transfer mode (ATM).

primary task Node B is the conversion of data to and from the Uu radio interface, including forward error correction (FEC), rate adaptation, W-CDMA spreading / despreading, and quadrature phase shift keying modulation (QPSK) in the air interface. Node B also participates in power control, as it allows the EU to adjust the power to command DL TPC (transmission power control) through the inner-loop power control based on information UL TPC . Radio Network Controller (RNC) function is similar to the GSM BSC. RNC relate to each other with Iur interface, while the RNC to node B related to the Iub interface. task RNC is to control some node B, is responsible to load and congestion control, and almost all of the RRM case here (layer 3: RRC), handover, outer loop power control.

Core Network (CN) CN is divided into 2 parts, service for processing Circuit Switched (CS) and Packet Switched (PS). Where there is integration between the CN of the GSM system to service the CS and CN SYSTEM INFORMATION BLOCK 1

T302/N302 : CELL UPDATE/URA UPDATE (MS timer) T309 : The timer for supervising successful connection establishment incase of an inter-RAT cell re-selection (MS timer)

SIB1 T300/N300 : The timer for supervising successful connection establishment incase of an inter-RAT cell re-selection (MS timer). T312 : The timer for supervising successful establishment of a physicalchannel (MS timer used in idle mode). N312 : This parameter defines the maximum number of "in sync"indications received from L1 during the establishment of a physical channel (UE counter used in idle mode). SYSTEM INFORMATION BLOCK 3

CellID = RNCID (12bit)+CID(16bit) CellIreselection is based on CPICH EcNo Sintrasearch : 10dB (5*2) Sintersearch : 8dB (4*2)

Treselection : 1 sec Max UE Txpwr: 21 dBm

SYSTEM INFORMATION BLOCK 5

CPICH: 33 dBm PRACH Power ramp step: 2 dB Peambleretransmax: 8 times

SYSTEM INFORMATION BLOCK 7

Ul Interference

SYSTEM INFORMATION BLOCK 11

Neighbor Cell: Qqualmin=-18dB Qrxlevmin=-115dBm [(2*-58)+1]

Intra Freq Neighbor measurement is based on CPICH Ec/No