Release With Redirect to LTE

Release with Redirect to LTEContents 1 Introduction 1.1 Basic Characteristics 1.2 Benefits 2 Feature Operational Description 2.1 Network Requirements 2.2 Technical Description 3 Parameters 3.1 Introduced Parameters 3.2 Parameters range and default values 3.3 Affected Parameters 3.4 Parameters Affecting the Feature 4 Network Impact 4.1 Subscriber Capacity 4.2 Network Performance 4.3 Hardware 4.4 Inter-Node Interface 4.5 Other Network Elements 5 Associated Features and Affected Functions 5.1 Prerequisite Features 5.2 Affected Features 5.3 Related Features 5.4 Affected System Functions 6 Performance 6.1 KPIs 6.2 Counters 6.3 Events 7 Operation and Maintenance 7.1 Activating the Feature 7.2 Deactivating the Feature 7.3 Engineering Guidelines Reference List 1 Introduction This document describes the Release with redirect to LTE FAJ 121 2174 feature and its main benefits and impacts in the WCDMA RAN. 1.1 Basic Characteristics This section describes the basic characteristics of the feature. Feature identity: FAJ 121 2174, Release with Redirect to LTE Release: Introduced in W12.1. Enhanced in W13.0. Enhanced in W13.1. Dependencies This feature requires the following RAN feature to be active:  LTE Cell Reselection FAJ 121 1474, refer to Idle Mode and Common Channel Behavior The following RAN features needs to be active for using parts of this feature:  Fast Dormancy Handling FAJ 121 1552 , refer to Connection Handling  Shared RAN (MOCN) multiple PLMN support FAJ 121 974  For usage of CSFB counters: CS Voice Fallback from LTE FAJ 121 1610, refer to Idle Mode and Common Channel Behavior  Shared Network Support FAJ 121 246, refer to Shared Network. 1.2 Benefits Release with Redirect to LTE is an inter-RAT mobility function that provides basic mobility for an LTE-capable UE from WCDMA to LTE. Redirection to LTE is controlled by the network and can be initiated at several trigger points, which can be individually turned on and off in each UTRAN cell. A redirection to LTE can be initiated from the active states CELL_DCH, CELL_FACH or URA_PCH. Figure 1 Release with Redirect to LTE enhances mobility from UTRAN to LTE. The Release with Redirect to LTE feature has the following benefits: This enables tuning the feature for best end user performance. The UE chooses the best LTE cell at time of arrival to LTE (there is no pre-allocation of resources in the target LTE system). A UE that is very active can spend very little time in Idle mode or in state URA_PCH where LTE Cell reselection can be performed.4. 2 Feature Operational Description This section describes the feature Release with Redirect to LTE. It is applicable for WCDMA networks with partial or complete overlapping LTE coverage. with this feature.1 Network Requirements This is a WCDMA-LTE radio network inter-working feature. It complements the feature LTE Cell Reselection (FAJ 121 1474) and assures mobility to LTE for an active UE. By avoiding measurements there is no throughput degradation due to compressed mode patterns.  WCDMA RAN capacity is enhanced by faster unloading of LTE-capable users to the LTE network. such UE may remain in WCDMA for an unnecessarily long time. Without Release with Redirect to LTE feature.  The feature uses a blind redirection and does not require UE support for LTE measurements in active mode. Release with Redirect to LTE supports redirection to LTE FDD and LTE TDD. each CN operator can define their own target LTE frequencies to which the UE is redirected.  In a UTRAN system with shared networks using the feature Shared Network Support (FAJ 121 246). including network configuration requirements.  Service performance for an individual LTE-capable UE is enhanced by improving the possibility for the end user to have access to LTE services.0 or later. FAJ 121 2174 in more detail. . A user that arrived in WCDMA due to a CS Fallback from LTE can. The feature requires a Multi-RAT capable (WCDMA and LTE) UE supporting 3GPP 25. The redirection to LTE is fast when LTE coverage is available. be returned to LTE immediately when the CS session is completed in WCDMA. This feature does not impact the mobility of a non-LTE capable UE.  In a UTRAN system with multi-operator Core Networks (CNs) using the Shared Network feature Multi-Operator Core Network (MOCN) (FAJ 121 974). controlled interoperability between networks is possible by selective redirection of UEs to desired LTE networks.331 release 8.  The redirection to LTE can be triggered at different points in time. 2.  Service performance for an individual LTE-capable UE is enhanced by the ability to provide fast return to LTE after a CS Fallback to WCDMA. A PS session can exist and can be pre-emptied. the following must be met:  The feature is enabled. For the redirection to LTE of a UE to succeed in a certain position. is installed and activated in the RNC. o The applicable trigger point occurred and is enabled in the best cell. For more information.  For a UE with best cell located in SRNC:  o The Utran Cell parameter releaseRedirect has the value "EUTRA" or "UTRAN_EUTRA". For a UE with best cell located in DRNC: .  No CS signalling connection exists. refer to Shared Network.  In case the feature Shared Network Support (FAJ 121 246) is activated. FAJ 121 974 is activated.2. The best cell of the active set is used when selecting LTE neighbors and evaluating triggers. the UE is connected to a CN operator and supports the LTE neighbor frequencies configured for that CN operator. .2 Technical Description Feature Release with Redirect to LTE enables RAN controlled mobility of a UE in a connected state from UTRAN to LTE. ensure that the feature LTE Cell Reselection. 2.There has to be radio coverage from the LTE network. The best cell is the active set cell with the best quality based on the latest reported primary CPICH measurement.1 Redirection For Release with Redirect to LTE to be performed.  Before activating the feature. the following must be fulfilled: . FAJ 121 1474. For each UTRAN cell. then at least one neighboring LTE frequency of the best cell is allowed for redirection according to the Shared Network Support filtering procedure. the operator selects which trigger points are enabled and which LTE neighbor frequencies are used for redirection from this cell.The UE subscription needs to allow access in the LTE network.  The best cell has an LTE neighbor frequency in an LTE frequency band supported by the UE. . or for each Iur Link in case the UE has passed an RNC border.  The UE is LTE-capable.  In case the feature MOCN.The UE needs to be LTE capable and support the frequency bands of the neighboring LTE network. 2. In this case the EutranFreqRelation is only used for broadcast in SIB 19.2. multiple frequency bands for the corresponding primary E-UTRA neighbor frequencies are configured in RNC. As soon as it finds a suitable LTE cell.2. An LTE capable UE also reports the supported LTE frequency bands. When the UE does not support the primary E-UTRA neighbor frequency. or both. RNC checks if the UE is LTE FDD or LTE TDD capable. When the UE receives the order in any of the active states CELL_FACH or CELL_DCH. o When determination is ready. The UE is only redirected if the UE capabilities support at least one E-UTRA frequency configured as a neighbor in the current best cell. When Robustness Support is activated. . the UE re-establishes its radio connection to LTE by sending a Tracking Area Update message to the eNodeB. RNC checks that the UE is not redirected from LTE due to coverage or load. When all criteria are fulfilled. RNC performs an additional check to find if the UE supports any alternative band configured in the multiple frequency band list. The parameter redirectionOrder controls how an EutranFreqRelation is used. When it is time to decide whether to redirect a UE to LTE.3 LTE Neighbor Frequency Configuration The target E-UTRA neighbor frequencies used at Release with Redirect to LTE are configured for each UTRAN cell with the MO EutranFreqRelation. This check is not done for trigger "normal release". RNC evaluates and stores the UE capabilities. a filtering of the configured neighbors is done. o The Iur Link parameter releaseRedirect has the value "EUTRA" or "UTRAN_EUTRA". The same relation is also used to identify the E-UTRA frequencies that are broadcast in SIB 19. Each E-UTRA frequency band contains a specified set of EUTRA Absolute Radio Frequency Channel Number (EARFCN). The EARFCN corresponding to the first suitable band that is found is included in the RRC Connection Release message. 2. o DRNC has configured EUTRA neighbor frequency information and sends it to the SRNC. The message conveys from one up to eight E-UTRA target frequencies. it releases its resources in WCDMA and go to search for an LTE cell on any of the conveyed frequencies. the following two additional conditions are evaluated: o When a UE is redirected from LTE. o The applicable trigger point occurred and is enabled for the Iur Link. RNC is ready with determination of the reason. 2. The alternatives are as follows:  A value of '0' means that the EutranFreqRelation is not used for redirection to LTE.2 Capability Handling When the RRC connection is established. If the FAJ 121 3963: LTE Cell Reselection for Advanced LTE Deployments feature is enabled. the RAN orders the UE to move to LTE by sending RRC Connection Release message with redirection information. Concerns for EUTRA neighbor frequency configurations over Iur are as follows:  The transfer of E-UTRA neighbor frequency information over Iur is turned on by setting the DRNC parameter MO Iur Link eutraNeighborReportSrnc to value "ON". For more information.  The value of parameter redirectionOrder controls the order in which the E-UTRA frequencies are listed in the RRC Connection Release message also in the Iur case. belonging to the EutranFreqRelation MO. When the FAJ 121 3963: LTE Cell Reselection for Advanced LTE Deployments feature is enabled..2. no redirection message is sent to the UE. refer to Shared Network. In case the shared network feature Shared RAN (MOCN). the following applies:  The RNC will analyze the PLMN-id part of the IMSI (home PLMN-id). The value range [1. Prerequisites for release with redirection to LTE to be triggered over Iur are that E-UTRA neighbor frequencies are configured in the DRNC and that the E-UTRA neighbor frequency information is transferred from the DRNC to the SRNC when the UE moves.  In case that certain E-UTRA frequencies are excluded for redirection for users connected to a certain CN operator this is configured by parameter MO EutranFreqRelation barredCnOperatorRef. In case the feature Shared Network Support (FAJ 121 246) is enabled in the network (parameter selHoSup in MO Handover is set to "TRUE"). Note that support for LTE neighboring frequencies received over Iur is possible. which LTE networks that users connected to this CN can be redirected to. in which case the same filtering mechanism applies. The eutranFrequencyRef parameter. the eutranFrequencyRef parameter.8] means that the EutranFreqRelation is also used by Release with Redirect to LTE feature. This is configured with the parameter MO CnOperator iphoNetworkRefsEutra. then redirection is allowed to the LTE neighboring frequencies belonging to the MO EutraNetwork. as an instance of EutranFrequency MO..8] controls the order in which the EUTRA frequencies are listed in the RRC Connection Release message. A E-UTRA frequency with a lower value of redirectionOrder appears first in the frequency list in the message. FAJ 121 974 is enabled in the network the following applies:  For each CN. In case no E-UTRA frequencies are available. redirection is not performed. also presents the corresponding information on the multiple frequency bands. When a trigger point occurs a filtering takes place to determine which E-UTRA frequencies to include in the Release with Redirect message. The value range [1. refers to the EutranFrequency MO that contains the downlink EARFCN (earfcnDl) used in E-UTRAN neighbor cells. If a match occurs. two new attributes: multiFreqBand and measBandwidth are introduced to the EutranFrequency MO for the overlapping LTE frequency bands. 2. In this case. The home PLMN-id must match either the value of plmnIdentity or any value in aliasPlmnIdentities in MO EutraNetwork in order for redirection to be performed. it can be configured.4 Configuration of Triggers Release with Redirect to LTE has the following triggers: . and filter the list of neighboring frequencies of the best cell before the list is sent to the UE. Otherwise. csFallbackCsRelease: When RNC receives RANAP Iu Release Command from the CS CN. normalRelease: When RNC receives RANAP Iu Release Command from the last CN connection. with a cause value counted as a "normal" release. For more information. at the point in time when a non-LTE UE is switched to CELL_FACH. with a cause value counted as a "normal" release. This is the same situation as when a non-LTE capable UE is released to Idle. refer to Channel Switching. with a cause value counted as a "normal" release.  dchToFach: This trigger initiates a redirection to LTE at any of the following situations:  o When RNC detects a period of inactivity in CELL_DCH. For this trigger to occur the feature Fast Dormancy Handling (FAJ 121 1552) should be activated.  fachToUra: When RNC detects a period of inactivity in CELL_FACH. The trigger initiates a redirection to LTE at any of the following situations: . The cause values for the Iu Release Command counted as "normal" release are as follows: o Normal Release o Successful Relocation o Resource Optimization Relocation o User inactivity o No remaining RAB Do not enable this trigger and trigger csFallbackDchToFach at the same time. at the point in time when a non-LTE UE is switched to URA_PCH or Idle. for a UE which has done CS Fallback from LTE. Any active PS RAB is pre-empted. o When the connection has Speech + PS Interactive 0/0 established and RNC receives RANAP Iu Release Command from the CS CN.  csFallbackDchToFach: This trigger is applicable for a UE which has done CS Fallback from LTE. This is the same situation as when a Fast dormancy would be triggered for a non-LTE capable UE. The UE is immediately redirected back to LTE. The cause values for the Iu Release Command counted as "normal" release are: o Normal Release o Successful Relocation o Resource Optimization Relocation o User inactivity o No remaining RAB  fastDormancy: When RNC receives RRC Signalling Connection Release Indication (SCRI) with cause value set to "UE Requested PS Data session end". A CS Fallback occurs when a UE is redirected to WCDMA from LTE to set up a CS speech call. and as soon as one trigger is fulfilled. . Reference [7]. This trigger provides redirect of a CS Fallback UE when the speech call is completed and when any established PS RAB is inactive. with a cause value counted as a "normal" release. since a UE cannot be in state CELL_FACH when connected to a DRNC. 2. The trigger parameters are configured separately for each Utran Cell.  Detection method: Used for a Release-8 UE or a Release-9 UE that does not include the IE "CSFB Indication". at the point in time when a non-LTE UE is switched to CELL_FACH.o When RNC detects a period of inactivity in CELL_DCH. When this trigger is enabled. o When the connection has Speech + PS Interactive 0/0 established and RNC receives RANAP Iu Release Command from the CS CN. for a UE of Release-9 support of this IE is optional. The RNC evaluates at RRC connection establishment if a UE is redirected from LTE due to a CS Fallback. At RRC Connection Request the presence of the IE "CSFB Indication" indicates that the UE has arrived from LTE due to a CS Fallback.2. refer to LTE feature CS Fallback from LTE. then RAN assumes that the UE arrived due to CS Fallback from LTE. If robustness support is enabled it is also required that the UE within a short time establishes a CS RAB in WCDMA RAN to allow the CS Fallback triggers. A set of counters provides observability of CS Fallback attempts and success and there is a separate Speech Accessability KPI for CSFB users. The trigger parameters are configured separately for each Iur Link. the redirection is performed. One or several trigger parameters can be enabled in a cell. o When a connection has Speech only established and RNC receives RANAP Iu Release Command from the CS CN.5 Detection of CS Fallback One of the possible criteria to redirect a UE to LTE is that the UE arrived in WCDMA RAN due to a CS Fallback from LTE. There are two ways to determine this dependent on the release of the UE:  Indication method: For a Release-10 UE or later it is mandatory to support the IE "CSFB Indication". If a UE that is redirected from LTE within a short time establishes a CS RAB in WCDMA RAN. Each trigger is evaluated separately. refer to Section 6 Performance. For description of CS Fallback. do not enable trigger csFallbackCsRelease since that can perform the preemption of the PS Interactive RAB. Trigger fachToUra is not applicable for an Iur Link. In this case RAN first decides if the UE is redirected from LTE which is the case when the UE is LTE capable and did not include the IE "pre-redirection info" in RRC Connection Request. with a cause value counted as a "normal" release. see the Engineering Guidelines chapter. For the CS Fallback detection method to work the UE has to have the RAN2 Release-9 CR 4222: (R2-114674 ‘Clarification of the Pre-Redirection info setting after the redirection from EUTRA') implemented. Therefore all triggers for Release with Redirect to LTE are blocked for a time of blockRwrEutraTime (MO Handover) after an incoming IRAT Offload from LTE. To avoid these failures and the corresponding out of service time. The detection of a coverage redirected UE is based on the same methods as Detection of CS Fallback. When a UE is redirected from LTE but not determined to be due to CSFB. CR5027. 2. This Robustness Support is controlled with the parameter MO RncFunction robustRwrEutraEnabled. In this case the blocking time is replaced by RncFunction::offloadDedicPrioEutraTime. When Robustness Support is enabled and as long as the UE only has signalling bearers. If the UE is very active. This is to avoid redirecting a UE that only performs a registration or other signalling only activity in WCDMA. the detection mechanism requires correct usage by the UE of the IE "Pre-Redirection info" and that the UE supports the RAN2 CR 4222 (R2-114674 ‘Clarification of the Pre-Redirection info setting after the redirection from E-UTRA'). When Robustness Support is enabled and a UE is determined to have arrived due to bad coverage all triggers except normalRelease are blocked for redirect to LTE . refer to FAJ 121 427: IRAT Offload from LTE.For the CS Fallback Indication method to work the UE has to have the RAN2 Release-9 optional CR 5026: (R2-123169 ‘Introduction of a CSFB Indicator in RRC Connection Request' ) implemented. all triggers are blocked for 8 seconds. The same applies when the feature FAJ 121 3588: LTE Cell Reselection Dedicated Priorities is activated and configured to prevent UE from reselecting LTE cells after IRAT Offload from LTE.7 Adaptation of Release with Redirect to LTE after Incoming IRAT Offload from LTE A UE that arrives in UTRAN with IRAT Offload from LTE should not be sent back to LTE directly to allow the load in the E-UTRA Cell to normalize. refer to LTE feature Coverage-Triggered WCDMA Session Continuity.2. If UTRAN redirects this UE back to LTE. since redirection is done without any preceding LTE measurements.8 Adaptation of Release with Redirect to LTE after Incoming IRAT HO due to Coverage .6 Robustness Support Release with Redirect to LTE expects that there is LTE coverage. This CR is optional in Release-8. UTRAN has Robustness Support to not redirect such a UE to LTE. then the UE is assumed to have arrived due to bad LTE coverage or load sharing in LTE. As for CS Fallback.2.2. see also description of criteria for redirection. In this case the only trigger that can occur is normalRelease. neither trigger normalRelease nor Cell Reselection to LTE in Idle or URA_PCH mode can happen. From Release-10 the support of CSFB Indicator is mandatory. For more information. the UE can erroneously appear to be redirected from LTE. If the CR 4222 is not supported. If that is common it can be beneficial to disable the Robustness Support. the feature must be used with care to avoid poor end user performance. 2. there is an increased risk of failure in finding a suitable LTE cell.Reference [8]. When a UE is in an LTE network and experiences bad coverage. 2. This means that in areas with uncertain LTE coverage. no RAB has been established. the LTE network can redirect the UE to UTRAN. . redirection to E-UTRA can take place for E-UTRA capable UE. o fachToUra: RWR to LTE at channel switch from FACH to URA. no redirection takes place. each with an ON or OFF value: o csFallbackCsRelease: RWR to LTE after CS Fallback at CS release. 3 Parameters This section describes parameters introduced by Release with redirect to LTE and parameters affected by activating the feature.  MO UtranCell releaseRedirect Indicates if a UE is redirected at RRC Connection Release. If the value is EUTRA or UTRAN_EUTRA. Dependencies: This attribute is only used if releaseRedirect is set to EUTRA or UTRAN_EUTRA. Applicable when the UE has a DRNC cell as the best cell in its active set. redirection to E-UTRA can take place for E-UTRA capable UEs. Applicable when this Utran cell is the best in the active set.  MO UtranCell releaseRedirectEutraTriggers Indicates the trigger points where a UE shall be redirected to E-UTRA in case the feature ReleaseRedirectLte is enabled. This handling is applied for:  Incoming SRVCC from LTE (CS only)  Incoming SRVCC for Voice and Data from LTE  Incoming PSHO from LTE  Incoming CSHO from GSM Note: Release with Redirect to LTE is not blocked after an incoming CNHHO. If the value is EUTRA or UTRAN_EUTRA. If the value is OFF. Range: 6 members.  MO IurLink releaseRedirect Indicates if a UE is redirected at RRC Connection Release. 3.A UE that arrives with IRATHO is assumed to do so due to insufficient LTE coverage and all triggers for Release with Redirect to LTE are blocked for the lifetime of the connection.1 Introduced Parameters This section describes all parameters that the operator can configure to control WCDMA RAN FAJ 121 2174 Release with Redirect to LTE. no redirection takes place. If the value is OFF. Further parameter information can be found in Radio Network Parameters. o normalRelease: RWR to LTE at normal release. o fastDormancy: RWR to LTE at Fast Dormancy. An instance with a value of 1 is listed first in the RRC Connection Release message. o A value of FALSE: no detection of coverage or load redirect from LTE. Range: 6 members.8] . The following two values are accepted:  o A value of TRUE: activate detection of coverage or load redirect from LTE. o dchToFach: RWR to LTE at channel switch from DCH to FACH or at CS release from state Sp0. Value 0 means that this EutranFreqRelation is not used for redirection to E-UTRA. o fastDormancy: RWR to LTE at Fast Dormancy. o csFallbackDchToFach: RWR to LTE after CSFB at channel switch from DCH to FACH or at CS release from state Sp0 or state Speech. MO IurLink releaseRedirectEutraTriggers Indicates the trigger points where a UE is redirected to E-UTRA in case the feature ReleaseRedirectLte is enabled for this IurLink. Range [0. o fachToUra: Since CELL_FACH state is not used over Iur the value of this parameter will be treated as OFF regardless of its actual value.. each with an ON or OFF value:  o csFallbackCsRelease: RWR to LTE after CS Fallback at CS release.  MO RncFunction robustRwrEutraEnabled Controls if detection of coverage or load redirection from LTE is activated in WCDMA RAN. o dchToFach: RWR to LTE at channel switch from DCH to FACH or at CS release from state Sp0. o csFallbackDchToFach: RWR to LTE after CSFB at channel switch from DCH to FACH or at CS release from state Sp0 or state Speech. MO EutranFreqRelation redirectionOrder Indicates whether EutranFreqRelation is included in the RRC Connection Release message in case of redirection to E-UTRA. The numerical value of this parameter tells the order in which the EARFCNs is listed in the message. o normalRelease: RWR to LTE at normal release. MO IurLink eutraNeighborReportSrnc . Dependencies: This attribute is only used if releaseRedirect is set to EUTRA or UTRAN_EUTRA. Used by the NriMocn feature to filter the EUTRA frequencies allowed for Release with redirect to LTE. EUTRA.2 Parameters range and default values Table 1 Operator Parameters Parameter Name UtranCell::releaseRedirect IurLink::releaseRedirect Default Value Value range OFF OFF. The PLMN identity information is conveyed over Iur when neighbor cells and frequencies are reported. described in Shared Network.  MO CnOperator CnOperatorIndex Used to distinguish between CN operators. UTRAN_EUTRA OFF OFF. 3.  MO EutraFreqRelation barredCnOperatorRef Defines that the CN operator. pointed out by this parameter. and Shared Network Support is enabled. is enabled. described in Shared Network. An Ericsson RNC use dummy variables for E-UTRA cell identities when transferring neighbor information over Iur. UTRAN. Only used if feature MOCN. The index represents one CN operator when the feature MOCN. Only used if feature MOCN. Only used if feature MOCN. Only used if ReleaseRedirectLte in MO RncFeature is activated. described in Shared Network. is enabled. EUTRA.  MO EutraNetwork plmnIdentity The number of possible instances of MO EutraNetwork is 4. described in Shared Network. This parameter is used for filtering of redirection target frequencies in case feature MOCN or feature Shared Network Support is enabled. The value of this parameter is set to OFF in case of interoperability with other vendors RNC. is enabled.  MO EutraNetwork aliasPlmnIdentities List of alias PLMN identities for the selective redirection feature. If the value of MO CnOperator CnOperatorIndex is "0" no monitoring of redirection to E-UTRA per CN operator is done. UEs with home PLMN-id equal to one of these alias PLMN-ids will be redirected to the frequencies of this EUTRA network.  MO CnOperator iphoNetworkRefsEutran Defines the E-UTRA networks to which a UE registered in this CN is allowed to perform a Release with redirect. includes the neighboring E-UTRA cell information in messages sent to the SRNC over Iur. When the feature Release with Redirect to LTE is activated. Each E-UTRA network shall be identified by its PLMN identity. UTRAN_EUTRA UtranCell::releaseRedirectEutraTrigger OFF for s csFallbackCsRelease ON or OFF . Used by the MOCN feature to filter the E-UTRA frequencies allowed for Release with redirect. is not allowed to use this EutraFrequencyRelation. when it is in a DRNC role. UTRAN.Controls whether this RNC. is enabled. 3. The Release-with-Redirect to LTE feature (FAJ 121 2174) can redirect a UE to LTE at different downswitches or at release. DchToFach ON for fachToUra.csFallbackDchToFach . as well as from CELL_FACH to URA_PCH. to limit the returns to LTE when LTE has high load and RABs are successfully setup in WCDMA.dchToFach OFF for csFallbackCsRelease .8 TRUE TRUE or FALSE IurLink::eutraNeighborReportSrnc OFF ON or OFF EutraNetwork::plmnIdentity n/a <MCC> <MNC> EutraNetwork::aliasPlmnIdentities n/a 0.. fastDormancy.normalRelease . .fachToUra .4 Parameters Affecting the Feature Existing inactivity parameters for channel switching.. are applied for Release with redirect to LTE. triggered by inactivity or fast-dormancy. for example at transitions from DCH to FACH or URA. during a predefined time.fastDormancy . from CELL_DCH to CELL_FACH. normalRelease Note: fachToUra Since CELL_FACH state is not used over Iur the value of this parameter will be treated as OFF regardless of its actual value EutranFreqRelation::redirectionOrder 0 0.dchToFach . csFallbackDchToFach .csFallbackCsRelease .4 CnOperator::iphoNetworkRefsEutran n/a n/a EutraFreqRelation::barredCnOperatorRef n/a n/a RncFunction::robustRwrEutraEnabled CnOperator::CnOperatorIndex 3.csFallbackCsRelease . the feature Release-with-Redirect to LTE is inhibited for this UE. csFallbackDchToFach .fachToUra .. A UE that is offloaded from LTE and then setups a connection in WCDMA should preferably not return immediately to LTE.64 0 0. A new RNC parameter Handover::blockRwrEutraTime is introduced with the IRAT Offload from LTE feature (FAJ 121 3427). normalRelease ON or OFF ON for fastDormancy. DchToFach IurLink::releaseRedirectEutraTriggers 6 members supported .normalRelease .csFallbackDchToFach .6 members supported .3 Affected Parameters The implementation of this feature affects no other parameters.fastDormancy . While this timer is not yet expired. Release With Redirect can be prevented for some class of subscribers with the help of feature Subscriber based mobility using SPID (FAJ 121 3637).2 Network Performance This section provides information on the impact of the feature on network performance. Whether this gain is possible to observe depends on the network and parameters such as: number of UEs with multi-RAT capabilities. It allows the RNC to differentiate behavior based on the subscriber profile provided by the CN.3 Hardware No feature specific information is identified. In this way this feature impacts the IRAT traffic distribution. This feature leads to faster return to LTE of LTE capable UEs.To support selective redirection using the feature Shared Network Support. the traffic model as well as the LTE network coverage and capacity. When Release with redirect to LTE is enabled over Iur the E-UTRA neighbor frequency information needs to be transferred from DRNC to SRNC by using the existing Iur interface (RNSAP) messages.5 Other Network Elements . 4.4 Inter-Node Interface This section provides information on the impact on inter-node interfaces. the network configuration. 4. 4. 4 Network Impact This section describes how the Release with redirect to LTE feature impacts the network functions and capabilities. When this feature is activated the LTE capable UEs will have a faster return back to LTE and will in general spend more time in LTE. If the SPID value received for a UE matches any value in that parameter. A new parameter spidPreventRwrEutra in MO SubscrProfileIdHandling specifies the Subscriber Profile ID (SPID) values that are used to prevent Release With Redirect. 4.1 Subscriber Capacity This section provides information on the impact of the feature on subscriber capacity. 4. the Release With Redirect is not allowed. the parameter selHoSup in MO Handover must be enabled. This section provides information on the impact on other network elements. .1 Prerequisite Features Table 2 lists prerequisite features to the Release with redirect to LTE feature. When Release with Redirect to LTE and Frequency Priority at Connection Release are enabled at the same time in a cell. in case the conditions for redirecting the UE to EUTRA are fulfilled. 5. 5. the following applies:  For an LTE capable UE the network first evaluates if Release with Redirect to LTE can be performed.2 Affected Features Depending on which trigger points are enabled. the feature Frequency priority at connection release is evaluated.3 Related Features The feature Frequency Priority at Connection Release (FAJ 121 2368) can also perform redirection at release of the connection. the LTE-capable UE is not switched to URA_PCH at fast dormancy indication from the UE. Fast Dormancy Handling (FAJ 121 1552) When the triggering point fastDormancy is enabled. Table 2 Prerequisite Features Feature Description LTE Cell Reselection (FAJ 121 1474) Introduces support for inter-working between UTRAN and E-UTRA. Only the Frequency Priority at Connection Release is evaluated for a nonLTE capable UE. Table 3 Affected Features Feature Description UTRAN Registration Area Handling (FAJ 121 When the fachToUra trigger are turned ON the LTE-capable UE is not 407) switched to state URA_PCH. there are impacts on the distribution of UE between RRC states and transitions between RRC states. No feature specific information is identified. 5. 5 Associated Features and Affected Functions This section describes how the Release with redirect to LTE FAJ 121 2174 feature affects other features and functions. in case the conditions for redirecting the UE to E-UTRA are fulfilled. If redirection to LTE is not performed. This change is visible in the counters reflecting these state transitions in UTRAN cells where the LTE redirection is performed. Table 3 lists features that are affected by the Release with redirect to LTE feature.  A non-LTE capable UE is not handled by the feature Release with Redirect to LTE. in case the conditions for redirecting the UE to E-UTRA are fulfilled. counters. 6 Performance This section describes performance indicators. see Section 2. 5. and events associated with the Release with redirect to LTE feature. Equation 1 Circuit-Switched (CS) Speech Accessibility at CS Voice Fallback from LTE. This is also used to provide a separate CSFB based Speech Key Performance Indicator: Circuit-Switched (CS) Speech Accessibility at CS Voice Fallback from LTE. the LTE-capable UE is not switched to CELL_FACH. For more information about Subscriber based mobility using SPID refer to System Description. If that is not the case the counters for the non used method will be zero and the KPI should be revised to only use the applicable of CSFB detected .The feature Subscriber based mobility using SPID (FAJ 121 3637) can be used to prevent Release With Redirect for users with certain Subscriber Profile IDs. 6. Table 4 lists functions affected by the Release with redirect to LTE feature.4 Affected System Functions Depending on which trigger points are enabled there are impacts on the distribution of UE between RRC states and transition between RRC states. Table 4 Affected System Functions Function Description Channel switching When any or both of the triggering points dchToFach and csFallbackDchToFach are enabled.2. Load Sharing Excluded This KPI depends on that the UE population in the network utilize both types of CSFB determination methods.1 KPIs The feature Release with Redirect to LTE determines when a CS fallback from LTE occurs. for example users without LTE subscription.5. 2 Counters Release with Redirect to LTE has the following options for observability defined:  Utran Cell counter pmRedirectAttemptsEutra counts the total number of attempts triggered by the RNC to redirect a UE to E-UTRA from this Utran Cell. which is stepped only for the cause value 'User Inactivity' (assuming that the CN returns the same cause value in the IuReleaseCommand as was sent in the IuReleaseRequest). Incremented by 1 in the Iur Link when an RRC Connection Release message with IE 'E-UTRA target info' is sent to a UE.counters or of CSFB indicated counters. Stepped once for the redirection.2 Counters for description of CSFB counters. This difference impacts the pmChSwitchFachIdle counter. the cause value used in the RANAP Iu Release Request is 'User Inactivity'. 6. see Section 6.  Counter pmTotNoRrcConnectUeCapability . If the same Channel Switch performs a redirection to LTE the cause value used is ‘Resource Optimisation Relocation’. for example pmRedirectAttemptsEutra[1]. CS Fallback from LTE has the following options for observability defined: . The Utran Cell counter pmRedirectAttemptsEutraCnOper is then individually stepped per CN operator.Number of times that a UE supporting E-UTRA successfully set up an RRC connection. Incremented by 1 in the best cell in the active set when an RRC Connection Release message with IE ‘E-UTRA target info’ is sent to a UE. Each CN operator is identified by configuring the parameter MO CnOperator cnOperatorIndex with a value between 1. and not for repetitions of the RRC Connection Release message. Stepped once for the redirection. there is some impact to existing counters that are stepped based on the cause value in the RANAP Iu Release Command. When a redirection to LTE is done. Below counter elements are only stepped based on information received in RRC Connection Setup Complete: [14]: E-UTRA TDD capability [15]: E-UTRA FDD capability [16]: E-UTRA TDD and FDD capability  Counter pmSpidPreventRwrEutra counts the number of times a Release With Redirect to E-UTRAN has been prevented because of received Subscriber Profile ID (SPID) value. If the feature MOCN (FAJ 121 974) is enabled in the network the number of attempts to trigger redirect to E-UTRA can additionally be counted also grouped per CN operator.4. not stepped for individual RABs.  Iur Link counter pmRedirectAttemptsEutra counts the total number of attempts triggered by the RNC to redirect a UE to E-UTRA for UEs with best cell in the DRNC connected with this Iur Link. A CN operator is identified since the index of the counter matches the value MO CnOperator cnOperatorIndex. not stepped for individual RABs.. For a Channel Switch from CELL_FACH to Idle without redirect to LTE. and not for repetitions of the RRC Connection Release message. 'Resource Optimisation Relocation'.a RANAP Iu Release Command message received from the CN with 'release cause' set to anything other than 'Normal Release'. 'Successful Relocation'. .CSFB counters require the feature CS Voice Fallback from LTE (FAJ 121 1610) to be activated. The NAS signaling phase is the phase after IU Signaling Connection establishment and before RAB Assignment Request. . or 'User Inactivity'. if the UE included the IE ‘CSFB Indication’ in the RRC Connection Request.a RAB Assignment Request message received from the CN with 'release cause' set to anything other than 'Normal Release'. for UEs that includes the IE ‘CSFB Indication’ at RRC establishment.  UtranCell counter pmTotNoRrcConnReqCsfbIndSucc counts the total number of successful RRC Connection Requests for which the UE includes the IE ‘CSFB Indication’. originating & terminating) load sharing RRC connection attempts. if the RNC received an RRC Initial Direct Transfer message prior to the NAS signalling phase and the UE included the IE 'CSFB Indication' at RRC establishment. Incremented by 1 in the best cell in the active set for each system-initiated release of the NAS signalling sequence at call setup towards a CS CN. The NAS .  UtranCell counter pmNoLoadSharingRrcConnCsfbInd counts the total number of conversational (emergency. or 'User Inactivity'. Counter supported in DRNC if IurLink::srncPmReporting = "ON" in SRNC. if the RNC received an RRC Initial Direct Transfer message prior to the NAS signalling phase and the UE included the IE 'CSFB Indication' at RRC establishment.  UtranCell counter pmNoSystemNasSignRelCsfbInd counts the total number of system-inititated releases of the Non Access Stratum (NAS) signalling sequence at call setup towards a CS CN. Incremented by 1 in the best cell in the active set for each normal release of the NAS signalling sequence at call setup towards a CS CN. Incremented by 1 per connection when the RNC sends a RRC Connection Reject message to a UE using the CS service.  UtranCell counter pmNoNormalNasSignRelCsfbInd counts the total number of successful normal releases of the NAS signalling sequence at call setup towards a CS CN for UEs that included the IE ‘CSFB Indication’ at RRC establishment. 'Resource Optimisation Relocation'. because another cell (frequency) has been selected by Load Sharing. not including retransmissions. for a UE that includes the IE ‘CSFB Indication’ at RRC establishment.detection in the RNC of RANAP Service Unavailable.  UtranCell counter pmTotNoRrcConnReqCsfbInd counts the total number of RRC Connection Request messages that included the IE ‘CSFB Indication’. Only stepped for call setup from idle. for UEs that included the IE ‘CSFB Indication’ in the RRC Connection Request. Incremented by 1 when the RNC receives an RRC Connection Setup Complete message indicating that the RRC connection is considered to be successfully established.a RANAP Reset message received from the CN. A system-initiated release can be triggered by: . . Only stepped for call setup from idle.the RNC when sending a RANAP Reset Resource message to the CN. . 'Successful Relocation'. Incremented by 1 per connection when the RNC receives an RRC Connection Request message that includes the IE ‘CSFB Indication’ from the UE with any Establishment Cause. Only stepped one time for the first CS RAB after CSFB from E-UTRA and only for a UE that included the IE ‘CSFB Indication’ in RRC Connection request. or 'User Inactivity'. or 'User Inactivity'. 'Successful Relocation'. after the configuration is selected as a valid final target configuration.  UtranCell counter pmNoRabEstAttCsfbDetect counts the total number of CS RAB establishment attempts for UEs that did not include the IE ‘CSFB Indication’ in the RRC Connection Request but are still considered to have done a CSFB from E-UTRA since: -the UE is E-UTRA capable -the UE did not include the IE ‘pre-redirection info in the RRC Connection Request -a RAB Assignment Request was received from the CS CN within 8 seconds from the RRC Connection Establishment. Counter supported in DRNC if IurLink::srncPmReporting = "ON" in SRNC. Counter supported in DRNC if IurLink::srncPmReporting = "ON" in SRNC.a RAB Assignment Request message received from the CN with 'release cause' set to 'Normal Release'. . Incremented by 1 in the SRNC after sending a RANAP RAB Assignment Response message to the CN. A normal release can be triggered by: . Incremented by 1 when the RNC receives a RANAP RAB Assignment Request message from the CS CN with RABs to be set up.a RANAP Iu Release Command message received from the CN with 'release cause' set to 'Normal Release'. 'Resource Optimisation Relocation'. when the configuration is selected as a valid final target configuration.  UtranCell counter pmNoRabEstAttCsfbInd counts the total number of CS RAB establishment attempts for UEs that indicated the IE ‘CSFB Indication’ in the RRC Connection Request. 'Successful Relocation'.  UtranCell counter pmNoRabEstSuccCsfbInd counts the total number of successful CS RAB establishments for a UEs that include the IE ‘CSFB Indication’ in the RRC Connection Request. Incremented by 1 when the RNC receives a RANAP RAB Assignment Request message from the CS CN with RABs to be set up. Only stepped one time for the first CS RAB after CSFB from E-UTRA and only for a UE that included the IE ‘CSFB Indication’ in RRC Connection Request. 'Resource Optimisation Relocation'.  UtranCell counter pmNoRabEstSuccCsfbDetect counts the total number of successful CS RAB establishments for the UEs that did not include the IE ‘CSFB Indication’ in the RRC Connection Request but are still considered to have done a CSFB from E-UTRA since: -the UE is E-UTRA capable -UE did not include the IE ‘pre-redirection info’ in the RRC Connection Request -a RAB Assignment Request was received from the CS CN within 8 seconds from the RRC Connection Establishment. Only stepped . Only stepped one time for a UE for the first CS RAB after CSFB from E-UTRA. Counter supported in DRNC if IurLink::srncPmReporting = "ON" in SRNC. . indicating a successful RAB establishment. indicating a successful RAB establishment. Counter supported in DRNC if IurLink::srncPmReporting = "ON" in SRNC.a RAB Assignment Request message with the IE "RABs to be setup or modified" for a call setup attempt towards a new CS CN. Incremented by 1 after sending the RANAP RAB Assignment Response message to the CN.signaling phase is the phase after IU Signaling Connection establishment and before RAB Assignment Request. Value CSFB_INDICATED is set. 7. 6. . INTERNAL_CALL_SETUP_FAIL More information about events can be found in General Performance Event Handling RBS and General Performance Event Handling RNC.  To use redirection to LTE at Fast Dormancy the feature Fast Dormancy Handling (FAJ 121 1552) needs to be installed and activated. refer to Section 2. This is a prerequisite for LTE neighbor filtering as the UE provides the supported LTE frequency bands per UTRAN frequency band.2.  Configure MO WcdmaCarrier with the UTRAN frequency band for each UARFCN.1.5. In all other situations NO_CSFB is indicated.. The indication can be set after a CSFB at Call Setup Failure and at RAB Establishment of the first CS RAB.  To use the counters and events related to CS Fallback the feature CS Voice Fallback from LTE (FAJ 121 1610) needs to be installed and activated. . the following conditions have to be fulfilled:  FAJ 121 1474. For these UEs an assumption method is used to detect CSFB. There are two ways to identify a CSFB UE and they are represented with separate values: . LTE Cell reselection needs to be installed and activated in the RNC.for R 10 (mandatory) and some R 9 (optional support) UEs there is an IE 'CSFB Indication' in RRC Connection Request. Value CSFB_DETECTED is set.1 Preconditions Before FAJ 121 2174 Release with Redirect to LTE can be activated.3 Events Table 5 Events Event Event Parameter Description INTERNAL_RAB_ESTABLISHMENT EVENT_PARAM_CSFB Parameter CSFB provides observability of the establishment of the first Speech Call when a UE has arrived from LTE due to CS Fallback (CSFB).for R 8 and some R 9 UEs no such IE is supported. Counter supported in DRNC if IurLink::srncPmReporting = "ON" in SRNC.1 Activating the Feature 7. 7 Operation and Maintenance This section provides Operation and Maintenance (O&M) information for the Release with redirect to LTE feature. FAJ 121 1610.one time for the first CS RAB after CSFB from E-UTRA. This parameter requires the license for feature CS Voice Fallback from LTE.  Enable selected triggering points for the cells where the feature is turned on. For this. The parameter EutranFreqRelation::redirectionOrder needs to be set in the range of 1. Frequency priority at RRC Connection release shall be activated in parallel with this feature set parameter releaseRedirect to "UTRAN_EUTRA".  Activate the feature on RNC level with parameter featureState for the RncFeature instance with designation ‘ReleaseRedirectLte’.2 Activating The following actions have to be performed for activation:  Configure which E-UTRA neighbor frequencies are to be used for redirection to LTE.  Decide if detection of coverage or load redirection from LTE shall be activated or deactivated in RNC through RncFunction::robustRwrEutraEnabled. or a subset of.  Order and install the FAJ 121 2174: Release with Redirect to LTE. Configure at least one instance of MO EutranFreqRelation for LTE neighbors in each Utran Cell where the feature Release with Redirect to LTE shall be used.)  Turn on the feature Release with Redirect to LTE in the UTRAN cells where overlapping LTE coverage exists. the following applies per Iur link:  Redirection to E-UTRA is possible if the DRNC sends E-UTRA neighbor information to the SRNC: o For Iur Link with both SRNC and DRNC from Ericsson: set DRNC parameter MO IurLink eutraNeighborReportSrnc to value "ON". (E-UTRA frequencies configured with redirectionOrder=1 is listed first in the RRC Connection Release message.At least one instance of MO EutranFrequency and parameter earfcnDlis configured.8 for at least one instance.1. This is done by setting the parameter UtranCell::releaseRedirect to "EUTRA". The license key is: CXC 403 0127. 7. o For Iur Link with Ericsson SRNC but other vendors DRNC: Check that the DRNC transfer E-UTRA frequency neighbor information to the SRNC. All. Note: This feature has one license per RNC.. . For the configuration of Release with Redirect to LTE over Iur. the following is required: . This is done by configuring trigger parameters within UtranCell::releaseRedirectEutraTriggers. In case feature FAJ 121 2368.At least one instance of MO EutraNetworks and parameter plmnIdentity is configured. The information needed is included in . E-UTRA frequencies with redirectionOrder=0 are not included in the RRC Connection Release message. the existing instances of MO EutranFreqRelation can be selected. o Preconditions: Configure MOCN. o Activate Release with Redirect to LTE. o  For Iur Link with other vendors SRNC but Ericsson DRNC: set DRNC parameter MO IurLink eutraNeighborReportSrnc to value "OFF". If feature Release with Redirect to LTE is active and feature MOCN shall be activated: o Disable Shared Network Support if active. In a multi-operator CN. o Activate MOCN. o Configure for each CN operator the EutraNetworks that are applicable for redirection. Configure MO CnOperator iphoNetworksRefsEutra. o Enable selected triggering points over the Iur link. MO EutraFreqRelation barredCnOperatorRefand MO CnOperator cnOperatorIndex. This is done by configuring the trigger parameters within MO IurLink releaseRedirectEutraTriggers. If separate observability per CN operator is wanted configure MO CnOperator cnOperatorIndex. MO EutraFreqRelation barredCnOperatorRef. when the feature MOCN (FAJ 121 974) shall be active simultaneously with the feature Release with Redirect to LTE. This is done by MO CnOperator iphoNetworksRefsEutra and. the following applies:  If feature Shared Network Support is active and feature Release with Redirect to LTE shall be activated: .IE 'Neighboring E-UTRA Cell Information' in the RNSAP messages sent at radio link setup and radio link addition. In a shared network. the following applies:   If feature MOCN is active and feature Release with Redirect to LTE shall be activated: o Configure MO EutraNetwork and parameter plmnIdentity. if applicable. Enable redirection to E-UTRA over an Iur link by doing the following configuration: o Redirection over Iur is enabled by setting MO IurLink releaseRedirect to value "EUTRA" or "UTRAN_EUTRA". when the feature Shared Network Support (FAJ 121 246) shall be active simultaneously with the feature Release with Redirect to LTE. If the DRNC does not send this information do not enable redirection to E-UTRA over Iur. If feature Release with Redirect to LTE is active and feature Shared Network Support shall be activated: o Disable MOCN if active. 7. o Configure MO EutraNetwork and parameter aliasPlmnIdentities.2 Deactivating the Feature 7. More information about licenses can be found in Licenses and Hardware Activation Codes.2. o Activate Release with Redirect to LTE. It is also possible to disable the triggering of redirection to LTE by setting all triggers points to "OFF" or by setting value of MO EutranFreqRelation redirectionOrder=0 for all E-UTRA frequencies configured in the cell.  Deactivate the feature in selected cells by setting parameter MO Utran Cell releaseRedirect to "OFF".2. 7. When the feature is deactivated.2 Deactivating The following actions are performed for deactivation:  Deactivate the feature on RNC level with parameter featureState for the RncFeature instance with designation ‘ReleaseRedirectLte’. Release with Redirect to LTE will not be triggered. Disable redirection to LTE for specific DRNC cells by not configuring E-UTRA neighbor frequencies in the cells.1 Preconditions There are no preconditions for deactivation. o Activate Shared Network Support. but feature FAJ 121 2368. o Configure MO EutraNetwork and parameter aliasPlmnIdentities. is still activated. .  By using the value "UTRAN" instead of "OFF" for parameter releaseRedirect the redirection to LTE is deactivated.  Deactivate the feature in selected DRNC by setting the parameter MO IurLink releaseRedirect to "OFF". o Configure MO EutraNetwork and parameter plmnIdentity. Frequency priority at RRC Connection release. A new RNC parameter . With this trigger the PSsession can have ongoing activities which are interrupted during a failed redirection.3 Engineering Guidelines This section provides information about tuning and practical engineering aspects when deploying Release with Redirect to LTE. the maximum time is 6 seconds when the CR is supported. see Robustness Support Section 2. and 4 is the number of seconds allowed to find a suitable cell on any frequency of that RAT. If an enabled redirect trigger occurs in WCDMA RAN. a UE will not access LTE when the coverage is bad enough for triggering a redirection back to UTRAN. If using the same suitable cell thresholds . the UE will behave according to 3GPP TS 25. With this CR the out of service time when searching for a suitable E-UTRA cell is limited to: Maximum search time = N + 4 seconds Where .3.  Optimize parameter settings in E-UTRA to minimize the risk.331 and might be out of reach for a considerable time before returning to access in any suitable cell. Even if the CS Fallback UE originally had LTE coverage before arriving in WCDMA. Using this trigger in areas with uncertain LTE coverage could be more disturbing to the end user than the other triggers.  If the LTE network supports redirect to WCDMA RAN for other reasons than CS Fallback. another attempt to redirect to LTE is initiated. To activate or deactivate the detection mechanism for redirect from LTE.2.1 Out of Service Avoidance It is recommended to have LTE coverage in the entire cell to activate Release with Redirect to LTE. 7. then consider using the WCDMA RAN mechanism to detect if a UE is redirected to WCDMA RAN due to bad coverage or load in E-UTRA.6.N is the Number of E-UTRA frequencies listed in "IE E-UTRA Target Info".for camping in E-UTRA – as the threshold for when to redirect the UE to UTRAN. mobility could have changed this. A UE that is offloaded from LTE and then setups a connection in WCDMA should preferably not return immediately to LTE. To reduce the out of service time it is recommended that UEs support the 3GPP Release-10 CR 5173. The trigger point csFallbackCsRelease preempts an ongoing PS-session.3. RRC Connection Release: Search time for E-UTRA signaled frequencies.2 Avoidance of Repeated Inter-RAT Redirections When a UE is redirected to LTE and finds a suitable LTE cell but the LTE radio coverage is bad. Trigger normalRelease means that the connection is to be released anyway and a failed redirection is less likely to be noticed by the end user. 7. use parameter RncFunction::robustRwrEutraEnabled. In case of unsuccessful redirections to LTE. With for example 2 frequencies sent to the UE in the RRC Connection Release message. the LTE RAN can redirect the UE back to WCDMA RAN. and the repeated redirections may continue.7. When the FAJ 121 3588: LTE Cell Reselection Dedicated Priorities is activated and configured to prevent UE from reselecting LTE cells after LTE Offload. design and manufacturing.413 [3] CS fallback in EPS. 82/1553-HSD 101 02 [6] Idle Mode and Common Channel Behavior. 82/1553-HSC 105 50/1 [9] RAN2 Release-9 CR 5026. 3GPP TS 25.331 [2] RANAP specification. Reference List [1] RRC specification. While this timer is not yet expired. Introduction of a CSFB Indicator in RRC Connection Reques 3GPP R2-123169 [10] RAN2 Release-10 CR 5173. 3GPP TS 25. Clarification of the Pre-Redirection info setting after the redirection from E-UTRA. 3GPP R2-114674 [5] Channel Switching. No part of this document may be reproduced form without the written permission of the copyright owner. 70/1553-HSC 105 50/1 [8] Coverage-Triggered WCDMA Session Continuity. Ericsson shall have no liability for any error or dam any kind resulting from the use of this document. the RncFunction::offloadDedicPrioEutraTime is used instead. Trademark List All trademarks mentioned herein are the property of their respective owners.Handover::blockRwrEutraTime is introduced with the IRAT Offload from LTE feature (FAJ 121 3427). 108/1553-HSD 101 02 Copyright © Ericsson AB 2012–2014. All rights reserved. during a predefined time. 3GPP TS 23. 71/1553-HSD 101 02 [7] CS Fallback to GERAN and UTRAN. These are sho the document Trademark Information. to limit the returns to LTE when LTE has high load and RABs are successfully setup in WCDMA. Release . the feature Release-with-Redirect to LTE is inhibited for this UE.272 [4] RAN2 Release-9 CR 4222. 3GPP R2-124346 [11] Shared Network. RRC Connection Release: Search time for E-UTRA signal frequencies. Disclaimer The contents of this document are subject to revision without notice due to continued progre methodology.