Вы находитесь на странице: 1из 14

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

HSDPA Accessibility Analysis


1. Identify root cause of failure distribution and main failure contributor in Services RSRAN073

2. If high HSDPA Access Failure _max user fails --> check RSRAN067

3. If high HSDPA Access Failure_UL DCH check


Rejected HS-DSCH return channel due to lack of radio power resource

Check M1002C521 or M1002C522 or M1000C144 (RAS06) only when HSDPA static allocation

Check Cell resource PrxTotal, PtxTotal

Check scrambling code congestion

4. If high HSDPA Access Failure_UE

Check RB reconfiguration failure rate

ICSU log for UE types troubleshooting

5. If high HSDPA Access Failure_BTS

Lack of UL channel resources (check CE resource utilisation using M5001 counters at BH)
Too high SHO overhead all branches must have enough CE capacity if UE is in SHO when HSDSCH allocation is started

6. HS-DSCH return channel setup fail due to Iub transport

Breakdown the failure distribution (64,128,384,MAC-d)

Evaluate number of reconfiguration failure due the transmission

Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL

Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533

Check Iub Utilisation / max CID / avg CID

High in call drop rate - - WCDMA (Nokia)


1. Check high call drop cells and its neighbouring cells of any faulty alarms
2. Identify call drop root cause failure distribution and main failure contributor (radio, Iu, BTS, Iur, MS, RNC) Services ->
RSRAN079

3. Check SHO KPI if performance < 90% ( leads to radio failure)


Check if cells are at RNC border (check Iur capacity and SRNC relocation problem)

Detect badly performing neighbours using HO success rate per adjacency counters (M1013)

High incoming HO failure rate in all adjs check sync alarms

Assessing neighbor list plan and visualization check with map

Evaluate HO control parameters and trigger threshold

4. Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure)
Check missing neighbour (M1015), GSM frequency plan neighbour RNC and MSC database consistency audit,
check alarm of reference clock in 3G or in 2G, check 2G TCH congestion
Check RRC Drop ISHO RT / NRT

5. Detecting DL or UL path loss problem if RAB drop due to radio (dominant call
drop cause > 50%)

Check UL Lost Active KPI from Iub counters (active L1 synchronization failure) to check UL/DL path loss problem

Check ASU failure rate (UNSUC_ASU) which link to NO RESPONSE FROM RLC

Mapping radio failures with Tx power and CPICH related parameters -> CPICHToRefRABOffset, PTXDPCH MAX

Check Call reestablishment timer -> T315

Ecno distribution for bad coverage issue (M1007C38-M1007C47)

6. Check core network parameter setting if RAB_ACT_FAIL_XXX_IU

Check SCCP SGSN/RNC IuPS Tias/Tiar if RAB_ACT_FAIL_BACKG_IU

7. If high RAB_ACT_FAIL_XXX_BTS

Check if any BTS faulty alarm (7653 cell faulty alarm)

If no alarms, COCO detach/attach

8. If high RAB_ACT_FAIL_XXX_MS

Check physical channel reconfiguration failure rate (IFHO, ISHO, code optimisation)

Optimising Iub considering CID congestion


Following performance indicators are proposed :
M550: Average utilisation of AAL2 connections - includes R99, SRB, HSDPA and return channels

SUM_AAL2_CONNECTIONS / NBR_SAMPLES/ CID MAX = C4/C7/248


M550: Max utilisation of AAL2 connections during measurement period
MAX_AAL2_CONNECTIONS/CID MAX = C6/248

CID Utilisation Monitoring Process

The maximum CID utilisation is followed and forecasted to future so that there is enough time
to introduce the new configuration before CID congestion occurs.

Average CID utilisation helps in interpreting if a peak in the maximum value is normal growth or
just load variation.

CID congestion is usually a problem of special events when there are a lot of voice calls and
SMS

CID congestion is probable in DCH&HSDPA, DCH and RT_DCH VCCs

Unlikely in others

CID Optimisation Actions and RU10 Features

The CID congestion needs to be solved by adding a VCC

DCH&HSDPA (former shared) UP VCC

Likely to cause performance degradation to HSDPA if transmission capacity is not increas


- HSDPA rates are limited to VCC PCR
- UBR+ is not recommended with DCH&HSDPA VCC
Path Selection CID congestion in RT VCC
- Introduce a 2nd RT VCC
- If additional capacity is not available then each VCC will get PCR_RT_NEW =
PCR_RT_OLD/2
- Capacity fragmentation may cause increased probability for AAL2 CAC blocking, with
AMR the impact should not be big

FMCG Parameter

GSMcauseCPICHEcNo : This parameter indicates whether a handover to GSM caused by low measured
absolute CPICH Ec/No of the serving cell is enabled.
When the handover to GSM is enabled, the RNC shall set up an intra-frequency CPICH Ec/No
measurement in order to monitor the absolute CPICH Ec/No of the serving cell.
The measurement reporting criteria of the intra-frequency CPICH Ec/No measurement are defined by
the Intra-frequency Measurement Control parameters (FMCS object).
Rec : Enabled (1)
GSMcauseCPICHrscp : This parameter indicates whether a handover to GSM caused by low measured
absolute CPICH RSCP of the serving cell is enabled.
When the handover to GSM is enabled, the RNC shall set up an intra-frequency CPICH RSCP
measurement in order to monitor the absolute CPICH RSCP of the serving cell.
The measurement reporting criteria of the intra-frequency CPICH RSCP measurement are defined by
the Intra-frequency Measurement Control parameters (FMCS object).
Rec : Enabled (1)
GSMcauseTxPwrDL : This parameter indicates whether a handover to GSM caused by high downlink
DPCH TX power is enabled.
Downlink DPCH TX power threshold for the handover to GSM is determined on service-by-service basis.
Rec : Disabled (0)
GSMcauseTxPwrUL : This parameter indicates whether a handover to GSM caused by high UE TX power
level is enabled.
UE TX power threshold for the handover to GSM is determined on service-by-service basis.
Rec : Disabled (0)

GSMcauseUplinkQuality : This parameter indicates whether a handover to GSM caused by bad uplink
DCH quality is enabled.
Rec : Disabled (0)
GsmDLTxPwrThrAMR : This parameter determines the downlink DPCH TX power threshold for a CS
voice connection.
When the handover to GSM caused by high DL DPCH TX power is enabled, the RNC starts inter-RAT
(GSM) measurements in compressed mode if the DPCH TX power of a single radio link reaches the
threshold. The DL DPCH TX power threshold is relative to the allocated maximum transmission power of
the DPCH.
Rec : '-3 dB, internal_value = gui_value * 2
GsmDLTxPwrThrCS : This parameter determines the downlink DPCH TX power threshold for a CS data
connection.
When the handover to GSM caused by high DL DPCH TX power is enabled, the RNC starts inter-RAT
(GSM) measurements in compressed mode if the DPCH TX power of a single radio link reaches the
threshold. The DL DPCH TX power threshold is relative to the allocated maximum transmission power of
the DPCH.
Rec : '-3 dB, internal_value = gui_value * 2
GsmDLTxPwrThrNrtPS : This parameter determines the downlink DPCH TX power threshold for a nonreal time PS data connection.
When the handover to GSM caused by high DL DPCH TX power is enabled, the RNC starts inter-RAT
(GSM) measurements in compressed mode if the DPCH TX power of a single radio link reaches the
threshold. The DL DPCH TX power threshold is relative to the allocated maximum transmission power of
the DPCH.
Rec : '-1 dB, internal_value = gui_value * 2
GsmDLTxPwrThrRtPS : This parameter determines the downlink DPCH TX power threshold for a real
time PS data connection.
When the handover to GSM caused by high DL DPCH TX power is enabled, the RNC starts inter-RAT
(GSM) measurements in compressed mode if the DPCH TX power of a single radio link reaches the
threshold. The DL DPCH TX power threshold is relative to the allocated maximum transmission power of
the DPCH.
Rec : '-3 dB, internal_value = gui_value * 2
GsmMaxMeasPeriod : The maximum number of periodical inter-RAT (GSM) measurement reports
determines the maximum allowed duration of the GSM measurement. If the RNC is not able to execute
the handover to GSM, it stops the GSM measurement after the UE has sent the predefined number of
measurement reports to the RNC.
Rec : 20, internal_value = gui_value
GsmMeasAveWindow : This parameter determines the maximum number of periodical inter-RAT (GSM)
measurement reports (maximum size of the sliding averaging window) from which the RNC calculates
the averaged GSM RSSI values for the handover decision algorithm.
Rec : 6, internal_value = gui_value
GsmMeasRepInterval : This parameter determines the measurement reporting interval for periodical
inter-RAT (GSM) measurements.
Rec : 0.5 s, range 0.5 s (2) | 1 s (3) | 2 s (4) | 3 s (5) | 4 s (6)

GsmMinHoInterval : This parameter determines the minimum interval between a successful inter-RAT
handover from GSM to UTRAN and the following inter-RAT handover attempt back to GSM related to the
same RRC connection.
Rec : 10 s, internal_value = gui_value
GsmMinMeasInterval : This parameter determines the minimum interval between an unsuccessful
inter-RAT (GSM) measurement or handover procedure, and the following GSM measurement procedure
related to the same RRC connection.
Rec : 2 s, internal_value = gui_value
GsmNcellSearchPeriod : This parameter determines the number of periodical inter-RAT (GSM)
measurement reports, starting from the first report after the measurement setup, during which a
handover to GSM is not possible. This period allows the UE to find and report all potential GSM
neighbour cells before the handover decision.
Rec : 0, internal_value = gui_value
GsmUETxPwrFilterCoeff : In the CELL_DCH state the UE physical layer measurement period for UE TX
power measurements is 1 slot. The Filter Coefficient parameter controls the higher layer filtering of
physical layer UE TX power measurements before the event evaluation and measurement reporting is
performed by the UE.
Rec : 10 ms (8), range : Filtering period approximates 10 ms (8) | Filtering period approximates 15 ms
(9) | Filtering period approximates 30 ms (10) | Filtering period approximates 60 ms (11) | Filtering
period approximates 120 ms (12) | Filtering period approximates 240 ms (13) | Filtering period
approximates 480 ms (14)
GsmUETxPwrThrAMR : This parameter determines the UE TX power threshold for a CS voice
connection. If the handover to GSM caused by high UE TX power level is enabled, the RNC starts interRAT (GSM) measurements in compressed mode when the UE TX power reaches this threshold. The UE TX
power threshold is relative to the maximum TX power level an UE can use on the DPCH in the cell (or
the maximum RF output power capability of the UE, whichever is lower).
Rec : '-3dB as default , -60dB only on 3G congested site defined by TSEL to force AMR to 2G,
internal_value = gui_value
GsmUETxPwrThrCS : This parameter determines the UE TX power threshold for a CS data connection.
If the handover to GSM caused by high UE TX power level is enabled, the RNC starts inter-RAT (GSM)
measurements in compressed mode when the UE TX power reaches this threshold. The UE TX power
threshold is relative to the maximum TX power level an UE can use on the DPCH in the cell (or the
maximum RF output power capability of the UE, whichever is lower).
Rec : '-3 dB, internal_value = gui_value
GsmUETxPwrThrNrtPS : This parameter determines the UE TX power threshold for a non-real time PS
data connection. If the handover to GSM caused by high UE TX power level is enabled, the RNC starts
inter-RAT (GSM) measurements in compressed mode when the UE TX power reaches this threshold. The
UE TX power threshold is relative to the maximum TX power level an UE can use on the DPCH in the
cell (or the maximum RF output power capability of the UE, whichever is lower).
Rec : '-1 dB, internal_value = gui_value
GsmUETxPwrThrRtPS : This parameter determines the UE TX power threshold for a real time PS data
connection. If the handover to GSM caused by high UE TX power level is enabled, the RNC starts interRAT (GSM) measurements in compressed mode when the UE TX power reaches this threshold. The UE TX
power threshold is relative to the maximum TX power level an UE can use on the DPCH in the cell (or
the maximum RF output power capability of the UE, whichever is lower).
Rec : '-3 dB, internal_value = gui_value

GsmUETxPwrTimeHyst : If the handover to GSM caused by high UE TX power is enabled, the RNC starts
inter-RAT (GSM) measurements in compressed mode when the UE TX power reaches a predefined
threshold. If the UE TX power goes down again (after the UE TX power threshold has once triggered),
the UE TX Power Time Hysteresis determines the time period during which the UE TX power must stay
below the UE TX power threshold before the RNC calls off the GSM measurements caused by the high
UE TX power.
Rec : 320 ms (11)
GsmMinSLHOInterval : This parameter defines the minimum interval between a successful service- or
load-based inter-RAT handover from GSM to UTRAN and the next service- or load-based inter-RAT
handover attempt back to GSM, related to the same RRC connection.
This parameter is effective if the original handover reason is known to be a service- or load-based one.
Rec : 30, internal_value = gui_value, unit s, Recommeded value is only applicable if GSM ==> UTRAN
IRAT HO is available
AMRDirReCell : This parameter enables and disables the use of Directed Retry of AMR call Inter-system
Handover. If the value is 'Enabled', then AMR calls are directed to the GSM network in case of UTRAN
congestion, in order to improve the setup of AMR calls. If the value is 'Disabled', then AMR calls are
rejected in case of UTRAN congestion.
Range : Disabled (0), Enabled (1)
DLDPCHTxPwrClOffset : This parameter defines the cancellation threshold
(DL_DPCH_TXPWR_THRESHOLD+DLDPCHTxPwrClOffset) for the DL DPCH TX Pwr.
Def : -3 dB
ISHOClcauseCPICHEcNo : This parameter indicates whether an inter-system handover cancellation
caused by a CPICH Ec/No exceeding the cancellation threshold is enabled or not. If the value is '0', the
ISHO cancellation due to CPICH Ec/No is disabled. If the value is '1', the ISHO cancellation due to CPICH
Ec/No is enabled.
ISHOClcauseCPICHrscp : This parameter indicates whether an inter-system handover cancellation
caused by a CPICH RSCP exceeding the cancellation threshold is enabled or not. If the value is '0', the
ISHO cancellation due to CPICH RSCP exceeding the cancellation threshold is disabled. If the value is
'1', the ISHO cancellation due to CPICH RSCP exceeding the cancellation threshold is enabled.
ISHOClcauseTxPwrDL : This parameter indicates whether an inter-system handover cancellation
caused by a low measured Downlink DPCH Transmission power level is enabled or not. If the value is '0',
the ISHO cancellation due to low measured Downlink DPCH Transmission power level is disabled. If the
value is '1', the ISHO cancellation due to low measured Downlink DPCH Transmission power level is
enabled.
ISHOClcauseTxPwrUL : This parameter indicates whether an inter-system handover cancellation
caused by UE Transmission power decreasing below the reporting threshold is enabled or not. If the
value is '0', the ISHO cancellation due to UE Transmission power is disabled. If the value is '1', the ISHO
cancellation due to UE Transmission power is enabled.

RAB setup failures for PS calls


RAB SETUP FAILURES DUE TO AC FOR PS DATA CONV
NetAct name: RAB_STP_FAIL_PS_CONV_AC

Description: The number of RAB setup failures caused by admission control for PS data conversational.
When the RNC decides to reject the PS data conversational RAB request because the admission control
entity reports a failure (excluding frozen BTS reason). This happens before the RRC: RADIO BEARER
SETUP message would be sent to the UE
RAB SETUP FAILURES DUE TO BTS FOR PS DATA CONV
NetAct name: RAB_STP_FAIL_PS_CONV_BTS
Description: The number of RAB setup failures caused by BTS for PS data conversational.
When the RAB assignment fails due to radio link setup or reconfiguration failure. The failure can
happen either in the Iub or in the Iur interface
RAB SETUP FAILURES DUE TO TRANSPORT FOR PS DATA CONV
NetAct name: RAB_STP_FAIL_PS_CONV_TRANS
Description: The number of RAB setup failures caused by transport for PS data conversational.
When the RNC decides to reject the PS data conversational RAB request due to transport failure. This
happens before the RRC: RADIO BEARER SETUP message would be sent to the UE.
RAB SETUP FAILURES DUE TO RNC FOR PS DATA CONV
NetAct name: RAB_STP_FAIL_PS_CONV_RNC
Description: The number of RAB setup failures caused by RNC for PS data conversational.
When the RNC decides to reject the PS data conversational RAB request due to RNC internal failure.
This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE.
RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA CONV
NetAct name: RAB_STP_FAIL_PS_CONV_FROZBS
Description: The number of RAB setup failures caused by frozen BTS for PS data conversational.
When the RNC decides to reject the PS data conversational RAB request because the admission control
entity blocks the radio link establishment to ensure the setup of high priority calls. This happens before
the RRC: RADIO BEARER SETUP message would be sent to the UE
RAB SETUP FAILURES DUE TO AC FOR PS DATA STREAM
NetAct name: RAB_STP_FAIL_PS_STREA_AC
Description: The number of RAB setup failures caused by admission control for PS data streaming.
When the RNC decides to reject the PS data streaming RAB request because the admission control
entity reports a failure (excluding frozen BTS reason). This happens before the RRC: RADIO BEARER
SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO BTS FOR PS DATA STREAM


NetAct name: RAB_STP_FAIL_PS_STREA_BTS
Description: The number of RAB setup failures caused by BTS for PS data streaming.
When the RAB assignment fails due to radio link setup or reconfiguration failure. The failure can
happen either in the Iub or in the Iur interface.
RAB SETUP FAILURES DUE TO TRANSPORT FOR PS DATA STREAM
NetAct name: RAB_STP_FAIL_PS_STREA_TRANS
Description: The number of RAB setup failures caused by transport for PS data streaming.
When the RNC decides to reject the PS data streaming RAB request due to transport failure. This
happens before the RRC: RADIO BEARER SETUP message would be sent to the UE
RAB SETUP FAILURES DUE TO RNC FOR PS DATA STREAM
NetAct name: RAB_STP_FAIL_PS_STREA_RNC
Description: The number of RAB setup failures caused by RNC for PS data streaming.
When the RNC decides to reject the PS data streaming RAB request due to RNC internal failure. This
happens before the RRC: RADIO BEARER SETUP message would be sent to the UE
RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA STREAM
NetAct name: RAB_STP_FAIL_PS_STREA_FROZBS
Description: The number of RAB setup failures caused by frozen BTS for PS data streaming.
When the RNC decides to reject the PS data streaming RAB request because the admission control
entity blocks the radio link establishment to ensure the setup of high priority calls. This happens before
the RRC: RADIO BEARER SETUP message would be sent to the UE
RAB SETUP FAILURES DUE TO AC FOR PS DATA INTERA
NetAct name: RAB_STP_FAIL_PS_INTER_AC
Description: The number of RAB setup failures caused by admission control for PS data interactive.
When the RNC decides to reject the PS data interactive RAB request because the admission control
entity reports a failure (excluding frozen BTS reason). This happens before the RRC: RADIO BEARER
SETUP message would be sent to the UE.
RAB SETUP FAILURES DUE TO RNC FOR PS DATA INTERA
NetAct name: RAB_STP_FAIL_PS_INTER_RNC
Description: The number of RAB setup failures caused by RNC for PS data interactive.
When the RNC decides to reject the PS data interactive RAB request due to RNC internal failure. This
happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

RAB SETUP FAILURES DUE TO ANCHORING FOR PS DATA INTERA


NetAct name: RAB_STP_FAIL_PS_INTER_ANCH
Description: The number of RAB setup failures caused by ongoing relocation or hard handover for PS
data interactive.
When the RNC rejects the PS data interactive RAB assignment request due to ongoing relocation or
hard handover.
RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA INTERA
NetAct name: RAB_STP_FAIL_PS_INTER_FROZBS
Description: The number of RAB setup failures caused by frozen BTS for PS data interactive.
When the RNC decides to reject the PS data interactive RAB request because the admission control
entity blocks the radio link establishment to ensure the setup of emergency calls. This happens before
the RRC: RADIO BEARER SETUP message would be sent to the UE.
RAB SETUP FAILURES DUE TO AC FOR PS DATA BACKG
NetAct name: RAB_STP_FAIL_PS_BACKG_AC
Description: The number of RAB setup failures caused by admission control for PS data background.
When the RNC decides to reject the PS data background RAB request because the admission control
entity reports a failure (excluding frozen BTS reason). This happens before the RRC: RADIO BEARER
SETUP message would be sent to the UE
RAB SETUP FAILURES DUE TO RNC FOR PS DATA BACKG
NetAct name: RAB_STP_FAIL_PS_BACKG_RNC
Description: The number of RAB setup failures caused by RNC for PS data background.
When the RNC decides to reject the PS data background RAB request due to RNC internal failure. This
happens before the RRC: RADIO BEARER SETUP message would be sent to the UE.
RAB SETUP FAILURES DUE TO ANCHORING FOR PS DATA BACKG
NetAct name: RAB_STP_FAIL_PS_BACKG_ANCH
Description: The number of RAB setup failures caused by ongoing relocation or hard handover for PS
data background.
When the RNC rejects the PS data background RAB assignment request due to ongoing relocation or
hard handover
RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA BACKG
NetAct name: RAB_STP_FAIL_PS_BACKG_FROZBS
Description: The number of RAB setup failures caused by frozen BTS for PS data background.

When the RNC decides to reject the PS data background RAB request because the admission control
entity blocks the radio link establishment to ensure the setup of emergency calls. This happens before
the RRC: RADIO BEARER SETUP message would be sent to the UE
RAB SETUP NOT STARTED DUE TO NOT SUPPORTED PARAMETERS FOR PS
NetAct name: RAB_STP_FAIL_PS_NOT_SUPP_PAR
Description: The number of occasions when the PS RAB setup attempt is not started due to requested
parameters are not supported by the RNC. The RAB setup attempt counter is not updated in this case.
The counter is updated when RANAP: RAB ASSIGNMENT RESPONSE with error information is sent to the
CN as a result of that the requested parameters are not supported.
RAB SETUP NOT STARTED DUE TO UE CAPABILITY FOR PS
NetAct name: RAB_STP_FAIL_PS_UE_CAPA
Description: The number of occasions when the PS RAB setup attempt is not started due to requested
parameters are not supported by the UE. The RAB setup attempt counter is not updated in this case.
The counter is updated when RANAP: RAB ASSIGNMENT RESPONSE with error information is sent to the
CN as a result of that the requested parameters are not supported.
RAB SETUP FAILURES DUE TO IUB AAL2 TRANS FOR PS DATA STREAM
NetAct name: RAB_STP_FAIL_PS_ST_IUB_AAL2
Description: The number of RAB setup failures caused by Iub AAL2 transport resource shortage for PS
data streaming.
When the RNC decides to reject the PS data streaming RAB request due to Iub transport resource
shortage between RNC and WBTS. This happens before the RRC: RADIO BEARER SETUP message is sent
to the UE
RAB SETUP FAILURES DUE TO IUR TRANSPORT FOR PS STREAMING
NetAct name: RAB_STP_FAIL_PS_STRE_IUR_TR
Description: The number of failed PS Streaming traffic class RAB setups due to Iur transport resources.
Also counter M1001C102 is updated with this counter.
When a PS streaming traffic class RAB setup fails due to Iur transport resources.