technology blog 2

Upload: abdillah-reza

Post on 13-Oct-2015

26 views

Category:

Documents


3 download

DESCRIPTION

3G

TRANSCRIPT

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 1/16

    R a b u , 1 6 N o v e m b e r 2 0 1 1

    Diposkan oleh Admin di 14.23 Tidak ada komentar:

    3G Handover Types

    Intra-Frequency Handovers

    1. Softer Handover

    Handover between sectors of the same Node B (handled by BTS)

    No extra transmissions across Iub interface

    Maximum Ratio Combining (MRC) is occurring in both the UL & DL

    2. Soft Handover

    UE simultaneously connected to multiple cells (from different Node Bs)

    Extra transmission across Iub, more channel cards are needed (compared to non-SHO)

    Mobile Evaluated Handover (MEHO)

    DL/UE: MRC & UL/RNC: Frame selection combining

    3. Hard Handover

    Arises when inter-RNC SHO is not possible (Iur not supported or Iur congestion

    Decision procedure is the same as SHO (MEHO and RNC controlled)

    Causes temporary disconnection of the (RT) user

    Inter-Frequency Handover

    Can be intra-BS, intra-RNC, inter-RNC

    Network Evaluated Handover (NEHO)

    Decision algorithm located in RNC

    Inter-RAT Handover

    Handovers between WCDMA and GSM (NEHO) or GAN (WLAN)

    Rekomendasikan ini di Google

    S e n i n , 1 4 N o v e m b e r 2 0 1 1

    RRC connection request

    Cari

    Search :.

    Home

    Disclosure Policy

    Laman :.

    2013 (1)

    2012 (14)

    2011 (43)

    Desember (1)

    November (17)

    Export data Nemo to Mapinfo

    FMCS Parameter

    HOPS Parameter

    ADJS Parameter

    3G HO Basic reporting events

    3G Handover Types

    RRC connection request

    How to avoid ping pong (3G -GSM)

    2G -> 3G Cell Re / Selection

    3G --> 2G Cell Re / selection

    RAB setup failures for CS voicecalls

    Portable Google_Earth

    RAB setup failures for PS calls

    RRC active failures

    RRC access failures

    RRC setup failures

    Save As PDF

    Oktober (19)

    Juli (6)

    Arsip Blog :.

    0Bagikan Lainnya Blog Berikut Buat Blog Masuk

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 2/16

    Diposkan oleh Admin di 17.36 Tidak ada komentar:

    If admission control rejects the RRC connection request, the RNC sends the RRC: RRC Connection Reject

    message to the UE. The message includes mandatory IE Wait time.

    The user equipment waits at least the time stated in the parameter before sending a new RRC: RRC Connection

    Request message. The value of the Wait time is defined with the Wait time in RRC connection request rejection

    (WaitTimeRRC) management parameter.

    Rekomendasikan ini di Google

    Diposkan oleh Admin di 15.35 Tidak ada komentar:

    How to avoid ping pong (3G - GSM)

    When UE is camped on 3G -> GSM measurements start when CPICH Ec/Io of serving cell is below Ssearch_RAT +

    QqualMin

    When UE is camped on GSM -> cell reselection to 3G is possible if CPICH Ec/Io of the candidate is above

    FDD_Qmin

    FDD_Qmin >= QqualMin+Ssearch_RAT

    Rekomendasikan ini di Google

    J u m a t , 1 1 N o v e m b e r 2 0 1 1

    2G -> 3G Cell Re / Selection

    QsearchI (A_BTS)

    With this parameter you define the threshold for dual mode mobiles in idle state to search for and to measure

    UTRAN neighbour cells introduced in 3G Cell Reselection list when a running average of the received downlink

    signal level (RLA_C) of the serving cell is below (0-7) or above (8-15) the threshold. This parameter is broadcast

    only on BCCH.

    If the parameter value is 7, dual mode mobiles in idle state measure always neighbour UTRAN cell(s). If the

    parameter value is 15, dual mode mobiles in idle state do not measure any of the neighbour UTRAN cells.

    GPRS-capable mobiles do not use this parameter if NCCR is active in the serving cell

    QsearchP (A_BTS)

    With this parameter you define the threshold for GPRS capable dual mode mobiles to search for and to measure

    UTRAN neighbour cells introduced in 3G Cell Reselection list when a running average of the received downlink

    signal level (RLA_C) of the serving cell is below (0-7) or above (8-15) the threshold.

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 3/16

    Diposkan oleh Admin di 15.39 Tidak ada komentar:

    This parameter is broadcast on BCCH.

    In case this parameter is broadcast on BCCH it shall be used only if GPRS cell re-selection parameters for one or

    more cells are sent to the MS in a Packet Cell Change Order or Packet Measurement Order message

    If the parameter value is 7, GPRS-capable multi-RAT MSs measure always neighbour UTRAN cell(s). If the

    parameter value is 15, GPRS-capable multi-RAT MSs do not measure any of neighbour UTRAN cells.

    GPRS-capable mobiles use this parameter only if NCCR is active in the serving cell

    fddQOffset (A_BTS)

    With this parameter you define a UTRAN cell reselection offset for non-GPRS capable dual mode mobiles which

    are in the idle state.

    The mobiles add the offset to the running average (RLA_C) of the received signal level of the serving GSM cell

    and non-serving GSM cells. After that the mobiles compare the measured RSCP values of UTRAN cells with signal

    levels of the GSM cells.

    -32 db = minus infinity dB

    range: -28..28 dB, step 4 dB

    FDD_GPRS_Offset

    FDDQmin (A_BTS)

    This parameter defines a minimum Ec/Io threshold which must be exceeded before a non-GPRS capable dual

    mode mobile is allowed to make a reselection from the serving GSM cell to an adjacent WCDMA RAN cell that is

    using frequency division duplex (FDD) type access technology/mode

    FDD_REP_QUANT

    defines the reporting quantity for UTRAN cell

    3G_Search_PRIO

    Is used to inidicate to the MS if 3G cells can be looked for when BSIC decoding is required. (0=no, 1=yes, default:

    1)

    Rekomendasikan ini di Google

    K a m i s , 1 0 N o v e m b e r 2 0 1 1

    3G --> 2G Cell Re / selection

    Cell Re / selection Criteria S di define sbb :

    Squal = Qqualmeas Qqualmin

    Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation

    Dimana :

    Squal : Cell Selection quality (dB)

    Qqualmeas : Measured cell quality value

    Qqualmin : Minimum required quality level in the cell (dB)

    Srxlev : Cell Selection RX level value (dB)

    Qrxlevmeas : Measured cell RX level value

    Qrxlevmin : Minimum required RX level in the cell (dBm)

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 4/16

    Diposkan oleh Admin di 19.32 Tidak ada komentar:

    Pcompensation : max(UE_TXPWR_MAX_RACH P_MAX, 0) in dB

    "UE_TXPWR_MAX_RACH" : Maximum TX power level an UE may use when accessing the cell on RACH (dBm)

    P_MAX : Maximum RF output power of the UE (dBm)

    Cell Re / selection Criteria S akan terpenuhi jika :

    Squal > 0

    Srxlev > 0

    Asumsi tidak menggunakan HCS maka :

    If Squal > Sintrasearch, UE need not perform intra-frequency measurements

    If Squal Sintersearch, UE need not perform inter-frequency measurement

    If Squal SsearchRAT m, UE need not perform measurements on cells of RAT "m"

    If Squal 2G adalah :

    HCS_PRIO : Defines the HCS priority level for a cell (def:0) (A_WCEL)

    NCr : Defines the maximum number of cell reselections (def:8) (A_WCEL)

    QHCS : Quality threshold level for applying prioritised hierarchical cell re-selection for a cell (def:WCDMA : -24)

    (A_WCEL)

    Qhyst1 : Qhyst1 is used for TDD and GSM cells, and for FDD cells when cell selection and re-selection quality

    measure is set to CPICH RSCP (def:4) (A_WCEL)

    Qhyst2 : Qhyst2 is used for FDD cells when cell selection and re-selection quality measure is set to CPICH Ec/No

    (def:4) (A_WCEL)

    QqualMin : The minimum required quality level in the cell (Ec/No) (def:-20) (A_WCEL)

    QrxlevMin : The minimum required RX level in the cell (def: WCDMA -115, GSM -105) (A_WCEL)

    SHCS_RAT : The RAT specific threshold for inter-RAT measurement rules (def:1) (A_WCEL)

    Sintersearch : The threshold for inter-frequency measurements, and for the HCS measurement rules (def:2)

    (A_WCEL)

    Sintrasearch : The threshold for intra-frequency measurements, and for the HCS measurement rules (def:4)

    (A_WCEL)

    Slimit_SearchRAT : Threshold for skipping inter-RAT measurement rules in HCS (def:2) (A_WCEL)

    Ssearch_RAT : The RAT-specific threshold for inter-RAT measurement rules (def:0) (A_WCEL)

    SsearchHCS : Threshold for intra- and interfrequency measurement rules in HCS (def:1) (A_WCEL)

    TCrmax : The duration for evaluating the allowed amount of cell reselections (def:60sec) (A_WCEL)

    TCrmaxHyst : Cell reselection hysteresis for reverting from UE high-mobility measurements (def:0sec) (A_WCEL)

    Treselection : The UE triggers the reselection of a new cell if the cell reselection criteria are fulfilled during the

    time interval Treselection (def:0) (A_WCEL)

    UseOfHCS : Indicates whether the serving cell belongs to a Hierarchical Cell Structure (HCS), or not (def:0)

    (A_WCEL)

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 5/16

    Rekomendasikan ini di Google

    RAB setup failures for CS voice calls

    RAB SETUP FAILURES DUE TO BTS FOR CS VOICE

    NetAct name: RAB_STP_FAIL_CS_VOICE_BTS

    Description: The number of RAB setup failures caused by BTS for CS voice.

    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 CS VOICE

    RAB_STP_FAIL_CS_VOICE_TRANS

    Description: The number of RAB setup failures caused by transport for CS voice.

    When the RNC decides to reject the CS voice 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 CS VOICE

    NetAct name: RAB_STP_FAIL_CS_VOICE_RNC

    Description: The number of RAB setup failures caused by RNC for CS voice.

    When the RNC decides to reject the CS voice 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 CS VOICE

    NetAct name: RAB_STP_FAIL_CS_VOICE_FROZBS

    Description: The number of RAB setup failures caused by frozen BTS for CS voice.

    When the RNC decides to reject the CS voice 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 IUB AAL2 TRANS FOR CS VOICE

    NetAct name: RAB_STP_FAIL_CS_V_IUB_AAL2

    Description: The number of RAB setup failures caused by Iub AAL2 transport resource shortage for CS voice.

    When the RNC decides to reject the CS voice 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 FAILURE CS VOICE WPS

    NetAct name: RAB_STP_FAIL_CS_VOICE_WPS

    Description: The number of RAB setup failures for CS voice calls using Wireless Priority Service. Also some other

    RAB SETUP FAILURE counter is updated along with this counter.

    RAB SETUP FAILURES DUE TO AC FOR CS VOICE

    NetAct name: RAB_STP_FAIL_CS_VOICE_AC

    Description: The number of RAB setup failures caused by admission control for CS voice.

    When the RNC decides to reject the CS voice 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

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 6/16

    Diposkan oleh Admin di 18.56 Tidak ada komentar:

    When allocating resources for Wireless Priority Service CS Voice RAB fails and blind Inter-System handover to

    GSM is not possible for example due to no neighbour cell available. In this case RNC responds to CN with RANAP:

    RAB ASSIGNMENT RESPONSE("No Resource Available").

    RAB SETUP FAILURES DUE TO LICENCE FOR CS VOICE

    NetAct name: RAB_STP_FAIL_CS_VOICE_LIC

    Description: The number of RAB setup failures caused by AMR capacity license exceeded for CS voice.

    When the RNC rejects a CS Voice RAB request due to AMR capacity license exceeded.

    RAB SETUP FAILURES DUE TO IUR TRANSPORT FOR CS VOICE

    NetAct name: RAB_STP_FAIL_CS_VOICE_IUR_TR

    Description: The number of failed CS voice RAB setups due to Iur transport resources. Also counter M1001C82 is

    updated with this counter

    When a CS voice traffic class RAB setup fails due to Iur transport resources.

    RAB SETUP FAILURES DUE TO IU-CS TRANSPORT FOR CS VOICE

    NetAct name: RAB_STP_FAIL_CS_VOICE_IU_CS

    Description: The number of failed CS voice RAB setups due to Iu-CS transport resources. Also counter M1001C82

    is updated with this counter

    Updated: When a CS voice traffic class RAB setup fails due to Iu-CS transport resources.

    Rekomendasikan ini di Google

    S e l a s a , 0 8 N o v e m b e r 2 0 1 1

    Diposkan oleh Admin di 18.58 Tidak ada komentar:

    Portable Google_Earth

    Download : Link Download

    Rekomendasikan ini di Google

    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

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 7/16

    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

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 8/16

    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.

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 9/16

    Diposkan oleh Admin di 18.03 Tidak ada komentar:

    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.

    Rekomendasikan ini di Google

    S e n i n , 0 7 N o v e m b e r 2 0 1 1

    RRC active failures

    RRC ACTIVE FAIL DUE TO IU INT

    NetAct name: RRC_CONN_ACT_FAIL_IU

    Description: The number of RRC active failures caused by Iu-interface related problem.

    When an Iu interface failure occurs, and the failure causes the release of the RRC connection. After this, the

    RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 10/16

    RRC ACTIVE FAIL DUE TO RADIO INTERFACE

    NetAct name: RRC_CONN_ACT_FAIL_RADIO

    Description: The number of RRC active failures due to radio interface.

    When a radio interface failure occurs, and the failure causes the release of the RRC connection. After this, the

    RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs.

    RRC ACTIVE FAIL DUE TO BTS REASONS

    NetAct name: RRC_CONN_ACT_FAIL_BTS

    Description: The number of RRC active failures due to BTS.

    When a BTS failure occurs, and the failure causes the release of the RRC connection. After this, the RNC sends

    an RANAP: IU RELEASE REQUEST to all involved CNs

    RRC ACTIVE FAIL DUE TO THE IUR INT

    NetAct name: RRC_CONN_ACT_FAIL_IUR

    Description: The number of RRC active failures due to drift RNC.

    When a procedure failure in drift RNC occurs, and the failure causes the release of the RRC connection. After

    this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs

    RRC ACTIVE FAIL DUE TO CIPH FAIL

    NetAct name: RRC_CONN_ACT_FAIL_CIPH

    Description: The number of RRC connection releases after a failed Security Mode Control procedure.

    When the RNC releases the RRC connection after receiving RANAP: IU RELEASE COMMAND with cause "Requested

    Ciphering and/or Integrity Protection Algorithms not Supported" from the core network.

    RRC ACTIVE FAIL DUE TO RNC INTER REASONS

    NetAct name: RRC_CONN_ACT_FAIL_RNC

    Description: The number of RRC active failures due to reasons not covered by the other failure counters.

    When an RNC internal failure occurs, and the failure causes the release of the RRC connection. After this, the

    RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs. The possible failure reasons updating this

    counter are for example RNC internal failure, transmission failure or loss of Frame Protocol synchronization.

    RRC ACTIVE FAIL DUE TO UE

    NetAct name: RRC_CONN_ACT_FAIL_UE

    Description: Number of RRC active failures due to UE.

    When the RRC connection is released due to the UE not responding to an RRC message or responding with such

    failure message that the connection must be released. After this, the RNC sends a RANAP: IU RELEASE REQUEST

    to all involved CNs

    SRB ACTIVE FAILURE CONVERSATIONAL

    NetAct name: SRB_ACT_FAIL_CONV

    Description: The number of abnormally released RRC connections with standalone signalling radio bearer before

    RAB assignment. Both originating and terminating conversational calls are included.

    When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in the old

    Service Level counters. The counter is updated when the establishment cause in RRC: RRC CONNECTION

    REQUEST is either Originating Conversational Call or Terminating Conversational Call.

    SRB ACTIVE FAILURE STREAMING

    NetAct name: SRB_ACT_FAIL_STREA

    Description: The number of abnormally released RRC connections with standalone signalling radio bearer before

    RAB assignment. Both originating and terminating streaming calls are included.

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 11/16

    Diposkan oleh Admin di 21.15 Tidak ada komentar:

    When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in the old

    Service Level counters. The counter is updated when the establishment cause in RRC: RRC CONNECTION

    REQUEST is either Originating Streaming Call or Terminating Streaming Call.

    SRB ACTIVE FAILURE INTERACTIVE

    NetAct name: SRB_ACT_FAIL_INTERA

    Description: The number of abnormally released RRC connections with standalone signalling radio bearer before

    RAB assignment. Both originating and terminating interactive calls are included.

    When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in the old

    Service Level counters. The counter is updated when the establishment cause in RRC: RRC CONNECTION

    REQUEST is either Originating Interactive Call or Terminating Interactive Call.

    SRB ACTIVE FAILURE BACKGROUND

    NetAct name: SRB_ACT_FAIL_BACKG

    Description: The number of abnormally released RRC connections with standalone signalling radio bearer before

    RAB assignment. Both originating and terminating background calls are included.

    When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in the old

    Service Level counters. The counter is updated when the establishment cause in RRC: RRC CONNECTION

    REQUEST is either Originating Background Call or Terminating Background Call.

    SRB ACTIVE FAILURE OTHER

    NetAct name: SRB_ACT_FAIL_OTHER

    Description: The number of abnormally released RRC connections with standalone signalling radio bearer before

    RAB assignment.

    When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in the old

    Service Level counters. The counter is updated when the establishment cause in RRC: RRC CONNECTION

    REQUEST is some other cause not covered by counters M1001C635-M1001C638.

    Rekomendasikan ini di Google

    M i n g g u , 0 6 N o v e m b e r 2 0 1 1

    RRC access failures

    RRC ACC FAIL DUE TO RADIO INT SYNCH

    NetAct name: RRC_CONN_ACC_FAIL_RADIO

    Description: The number of RRC access failures caused by radio interface synchronisation failure

    When the RNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE message from the UE within 6

    seconds, and the RNC has not received the NBAP message which indicates that L1 synchronisation has been

    established between UE and BTS. This counter is updated also in case of inter-system handovers and inter-RNC

    hard handovers

    RRC ACC FAIL DUE TO UU INT

    NetAct name: RRC_CONN_ACC_FAIL_MS

    Description: The number of RRC access failures caused by UE.

    When the RNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE message from the UE within 6

    seconds, and the RNC has received the NBAP message which indicates that L1 synchronisation has been

    established between UE and BTS. This counter is updated also in case of incoming SRNS relocations, inter-system

    handovers, and inter-RNC hard handovers

    RRC ACC FAIL DUE TO RNC INTER REASONS

    NetAct name: RRC_CONN_ACC_FAIL_RNC

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 12/16

    Diposkan oleh Admin di 22.42 Tidak ada komentar:

    Description: The number of RRC access failures caused by RNC internal reason.

    When an RNC internal failure occurs before receiving the RRC: RRC CONNECTION SETUP COMPLETE message

    from the UE. This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and

    inter-RNC hard handovers

    Rekomendasikan ini di Google

    J u m a t , 0 4 N o v e m b e r 2 0 1 1

    RRC setup failures

    RRC SETUP FAIL DUE TO HC

    NetAct name: RRC_CONN_STP_FAIL_HC

    Description: The number of RRC setup failures caused by Handover Control.

    When the RNC decides to reject the RRC connection request because the handover control entity reports a

    failure. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.

    This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard

    handovers

    RRC SETUP FAIL DUE TO AC

    NetAct name: RRC_CONN_STP_FAIL_AC

    Description: The number of RRC setup failures caused by Admission Control.

    When the RNC decides to reject the RRC connection request because the admission control entity reports a

    failure (excluding frozen BTS reason).

    After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. This counter is updated also in

    case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers

    RRC SETUP FAIL DUE TO BTS REASONS

    NetAct name: RRC_CONN_STP_FAIL_BTS

    Description: The number of RRC setup failures caused by BTS.

    When the RNC decides to reject the RRC connection request due to unsuccessful radio link setup. After this, the

    RNC sends an RRC: RRC CONNECTION REJECT message to the UE.

    This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard

    handovers

    RRC SETUP FAIL DUE TO TRANS

    NetAct name: RRC_CONN_STP_FAIL_TRANS

    Description: The number of RRC setup failures caused by Transport.

    When the RNC decides to reject the RRC connection request due to transport failure. After this, the RNC sends

    an RRC: RRC CONNECTION REJECT message to the UE.

    This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard

    handovers

    RRC SETUP FAIL DUE TO RNC INTER REASONS

    NetAct name: RRC_CONN_STP_FAIL_RNC

    Description: The number of RRC setup failures caused by RNC internal reason.

    When the RNC decides to reject the RRC connection request due to RNC internal failure. After this, the RNC

    sends an RRC: RRC CONNECTION REJECT message to the UE

    This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard

    handovers

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 13/16

    Diposkan oleh Admin di 18.59 Tidak ada komentar:

    RRC SETUP FAIL DUE TO FROZEN BTS

    NetAct name: RRC_CONN_STP_FAIL_FROZBS

    Description: The number of RRC setup failures caused by frozen BTS.

    When the RNC decides to reject the RRC connection request, because the admission control entity blocks the

    radio link establishment, to ensure the setup of high priority calls. After this, the RNC sends an RRC: RRC

    CONNECTION REJECT message to the UE.

    This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard

    handovers

    RRC CONN SETUP FAIL DUE TO RNTI ALLO FAIL

    NetAct name: RRC_CONN_STP_FAIL_RNTI_ALLO

    Description: Number of RRC setup failures caused by RNTI allocation failure

    When the RNC decides to reject the RRC connection request due to RNTI allocation failure caused by RRMU

    overload. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE

    RRC SETUP FAIL DUE TO IUB AAL2 TRANS

    NetAct name: RRC_CONN_STP_FAIL_IUB_AAL2

    Description: The number of RRC setup failures caused by Iub AAL2 transport resource shortage.

    When the RNC decides to reject the RRC connection request due to Iub transport resource shortage between RNC

    and WBTS. After this the RNC sends an RRC: RRC CONNECTION REJECT message to the UE

    This counter is updated also in case of inter-system handovers, and inter-RNC hard handover

    RRC SETUP REJECT DUE TO EMERGENCY CALL REDIRECTION

    NetAct name: RRC_CONN_STP_REJ_EMERG_CALL

    Description: The number of RRC connections rejected due to emergency call redirection.

    When the RNC redirects an emergency call to the GSM network by sending an RRC CONNECTION REJECT with

    redirection information to the UE

    RRC CONN SETUP FAIL DUE TO ICSU OVERLOAD

    NetAct name: RRC_CONN_STP_FAIL_ICSU_OVERL

    Description: The number of RRC setup failures caused by ICSU overload.

    When the RNC decides to reject the RRC connection request due to ICSU overload. After this, the RNC sends an

    RRC: RRC CONNECTION REJECT message to the UE.

    Rekomendasikan ini di Google

    Save As PDF

    Overview

    This download allows you to export and save to the PDF format in eight 2007 Microsoft Office programs. It also

    allows you to send files as e-mail attachments in the PDF format in a subset of these programs. Specific features

    vary by program.

    This Microsoft Save as PDF Add-in for 2007 Microsoft Office programs supplements and is subject to the license

    terms for the 2007 Microsoft Office system software. You may not use this supplement if you do not have a

    license for the software.

    Supported Operating Systems: Windows Server 2003, Windows Vista, Windows XP Service Pack 2

    This download works with the following Office programs:

    Download : Link Download

    System requirements

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 14/16

    Diposkan oleh Admin di 18.01 Tidak ada komentar:

    Microsoft Office Access 2007

    Microsoft Office Excel 2007

    Microsoft Office InfoPath 2007

    Microsoft Office OneNote 2007

    Microsoft Office PowerPoint 2007

    Microsoft Office Publisher 2007

    Microsoft Office Visio 2007

    Microsoft Office Word 2007

    To install this download:

    1. Download the file by clicking the Download button (above) and saving the file to your hard disk.

    2. Double-click the SaveAsPDF.exe program file on your hard disk to start the Setup program.

    3. Follow the instructions on the screen to complete the installation.

    Instructions for use:

    After you install this download open the document you want to publish and then, depending on the program you

    are using, select Save to PDF from the Office or File menu.

    For more information, search Office Help for "Save a file in PDF format".

    To remove this download:

    To remove the download file, delete the file SaveAsPDF.exe.

    1. On the Start menu, point to Settings and then click Control Panel.

    2. Double-click Add/Remove Programs.

    3. In the list of currently installed programs, select Microsoft Save as PDF Add-in for 2007 Microsoft Office

    programs and then click Remove or Add/Remove. If a dialog box appears, follow the instructions to

    remove the program.

    4. Click Yes or OK to confirm that you want to remove the program.

    Instructions

    Rekomendasikan ini di Google

    S e n i n , 3 1 O k t o b e r 2 0 1 1

    NEMO - - SYSTEM INFORMATION BLOCK

    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

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 15/16

    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

  • 6/13/13 Technology Blog

    taktiktek.blogspot.com/search?updated-min=2010-12-31T09:00:00-08:00&updated-max=2011-11-16T14:53:00%2B07:00&max-results=43&start=6&by-date=false 16/16

    Posting Lebih Baru Posting LamaBeranda

    Langganan: Entri (Atom)

    Diposkan oleh Admin di 19.05 Tidak ada komentar:

    Neighbor Cell:

    Qqualmin=-18dB

    Qrxlevmin=-115dBm [(2*-58)+1]

    Intra Freq Neighbor measurement is based on CPICH

    Ec/No

    Rekomendasikan ini di Google

    Map

    pagerank check

    Template Simple. Diberdayakan oleh Blogger.