Scribd Logo
Upload

Welcome to Scribd!

  • 65 views

    Drop of ERAB Scenario of LTE: LTE Reesta Functional Description

    Uploaded by

    srimanta
    This document discusses the RRC connection re-establishment procedure in LTE. It describes scenarios where the procedure can be initiated by the UE, such as due to radio link failure or integrity check failure. It also discusses cases where the source cell or target cell may reject or accept the RRC connection re-establishment request from the UE during a handover. If rejected, the eNodeB sends a rejection message and releases the UE context.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Drop of ERAB Scenario of LTE: LTE Reesta Functional Description

    Uploaded by

    srimanta
    65 views2 pages
    This document discusses the RRC connection re-establishment procedure in LTE. It describes scenarios where the procedure can be initiated by the UE, such as due to radio link failure or integrity check failure. It also discusses cases where the source cell or target cell may reject or accept the RRC connection re-establishment request from the UE during a handover. If rejected, the eNodeB sends a rejection message and releases the UE context.

    Original Title

    Drop of ERAB Scenario

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses the RRC connection re-establishment procedure in LTE. It describes scenarios where the procedure can be initiated by the UE, such as due to radio link failure or integrity check failure. It also discusses cases where the source cell or target cell may reject or accept the RRC connection re-establishment request from the UE during a handover. If rejected, the eNodeB sends a rejection message and releases the UE context.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    65 views2 pages

    Drop of ERAB Scenario of LTE: LTE Reesta Functional Description

    Uploaded by

    srimanta
    This document discusses the RRC connection re-establishment procedure in LTE. It describes scenarios where the procedure can be initiated by the UE, such as due to radio link failure or integrity check failure. It also discusses cases where the source cell or target cell may reject or accept the RRC connection re-establishment request from the UE during a handover. If rejected, the eNodeB sends a rejection message and releases the UE context.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 2

    Drop of ERAB Scenario of LTE

    LTE Reesta Functional description


    Functional overview
    The Flexi Multiradio BTS supports the RRC Connection r-establishment procedure. The procedure
    is initiated by the UE in RRC connected in case of:
     Radio link failure detection due to for example
    o expiry of the timer T310 (timer started after detection of physical layer problem)
    o random access problem indication from MAC
     Integrity check failure indication from lower layers
     RRC connection reconfiguration failure

    LTERRC Connection Re-Establishment


    RRC Connection Re-Establishment Procedure (RRC Re-Establishment) can be initiated by UE for
    different reasons during an ongoing intra LTE Handover, inter RAT Handover or eNACC to GSM.In
    case RRC Re-Establishment was caused by Radio link failure or T304 expiry eNodeB will accept
    the RRC Re-Establishment if the UE enters the Source cell or an prepared Target Cell.In case the
    UE tries to enter an unprepared cell or the RRC Re-Establishment was caused by an configuration
    error the eNodeB will not accept RRC Re-Establishment.
    Rejection of RRC Connection Re-Establishment in the Source cell of an Handover
    The RRC Connection Re-Establishment Request by the UE will not always be acceptable by the
    Source cell. Resons may be:
     reason for RRC Re-Establishment was "reconfiguration failure
     UE has already applied configuration for target cell
    The general handling in eNodeB follows the list below:
     eNodeB decides to reject the RRC Connection Re-Establishment request and sends the
    rejection message towards the UE
     eNodeB initates a UE Context Release procedure towards the MME to inform the MME that
    the UE was send to idle
     depending on the type of mobility procedure eNodeB needs to cancel the ongoing
    mobility procedure. Especially for X2-handover eNodeB has to inform its peer via X2
    signalling the ongoing handover shall be cancelled. In case of S1 based handover
    procedures no explicit cancellation is needed as the MME does not need an explicit
    cancellation of the S1-HO in addition to the UE Context Release. For other mobility
    procedures eNodeB internal actions will be sufficient.
    Acceptance of RRC Connection Re-Establishment in the Target cell of an Handover
    In general it can happen during any mobility procedure (for example intra LTE handover, inter
    RAT handover or eNACC) that UE fails to execute the procedure, performs cell selection and
    initiates RRC Re-Establishment procedure towards the Target cell which has already been
    prepared. In the following only the cases where the Target Cell is an LTE Cell are considered.The
    general handling in eNodeB follows the list below:

    The RRC Connection Re-Establishment Request by the UE will not always be acceptable by the
    Target cell. Resons may be:
     reason for RRC Re-Establishment was "reconfiguration failure"
    The general handling in eNodeB follows the list below:
     eNodeB decides to reject the RRC Connection Re-Establishment request and sends the
    rejection message towards the UE
     eNodeB initates a UE Context Release procedure towards the MME to inform the MME that
    the UE was send to idle.

    You might also like