0% found this document useful (0 votes)
4 views22 pages

Redirect With System Information

The Redirect with System Information feature enhances outage times when a User Equipment (UE) is redirected from LTE to other networks like GSM, WCDMA, or TD-SCDMA, facilitating faster connections during circuit-switched fallbacks. It operates by providing system information for target cells during the RRC connection release process, thereby improving session continuity and reducing downtime. The feature requires specific licensing and is dependent on other features being enabled, particularly in shared network setups.

Uploaded by

Med Missaoui
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views22 pages

Redirect With System Information

The Redirect with System Information feature enhances outage times when a User Equipment (UE) is redirected from LTE to other networks like GSM, WCDMA, or TD-SCDMA, facilitating faster connections during circuit-switched fallbacks. It operates by providing system information for target cells during the RRC connection release process, thereby improving session continuity and reducing downtime. The feature requires specific licensing and is dependent on other features being enabled, particularly in shared network setups.

Uploaded by

Med Missaoui
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Redirect with System Information [Link]

LI=EN/LZN%20793%201040%20R47G

Feature Description 98/221 04-LZA 701 6014/1 Uen AU

Redirect with System Information


Contents
O ve r v i e w
Dependencies
Fe a t u re O p e ra t i o n
RAN Information Management Pool Concept
Configuration
Prioritization of Cells
N e t wo r k I m p a c t
P a ra m e te r s
Performance
Ac t i va te
D e a c t i va te

1 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

2 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

1 Redirect with System Information Overview


This feature improves outage times when the UE is redirected from LTE.

Fe a t u re N a m e Redirect with System Information


Fe a t u re I d e nt i t y FAJ 121 0876
Va l u e P a c k a g e N a m e LTE Base Package
Va l u e P a c k a g e I d e n t i t y FAJ 801 0400
Node Type Baseband Radio Node
Access Type LTE
Licensing License-controlled feature. One license is required for each node.

Summary
The Redirect with System Information feature improves outage time when the UE is redirected from LTE to one of the
following networks:

– GSM

– WCDMA

– TD-SCDMA

This is important when performing a CS fallback, since the UE is able to connect to the circuit switched domain faster.
The following concepts apply to the operation and maintenance of the Redirect with System Information feature:
E x te r n a l c e l l External cells in the eNodeB hold information about cells in the following networks:

– GERAN

– UTRAN

– E-UTRAN

– TD-SCDMA

C e l l re l a t i o n Relations are established between cells in the eNodeB and in the following networks:

– GERAN

– UTRAN

– E-UTRAN

– TD-SCDMA

R AN I n fo r m a t i o n A RAN Information Management association is created between the serving BSS and the
M a n a g e m e nt target BSS for redirecting the UE with system information. The redirection with system
association information works between the cell on the serving BSS (eNodeB) and the cell on the target
BSS (BSC or RNC node).

Ad dit i onal Info rm ati o n


For more information about this feature and related topics, see the following documentations:

– 3GPP TS 23.272, Circuit Switched (CS) fallback in Evolved Packet System (EPS)

– 3GPP TS 36.331, Evolved Universal Terrestrial Radio Access (E-UTRA)

3 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

– 3GPP TS 48.018, General Packet Radio Service (GPRS)

4 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

5 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

2 Dependencies of Redirect with System Information


Depending on where the UE is redirected to, the feature needs other features to be enabled. The support of this
feature is limited under shared network setup.

Table 1 Feature Dependencies

Fe a t u re Re l a t i o n s h i p Description
At least one of these four features must be enabled:
The Coverage-Triggered GERAN Session
Continuity feature is required for coverage
triggered or CS fallback-triggered redirect from
Coverage-Triggered GERAN Session
Prerequisite LTE to GSM.
Continuity (FAJ 121 0495)
The session continuity access times are
improved for the Coverage-Triggered GERAN
Session Continuity feature.
The Coverage-Triggered WCDMA Session
Continuity feature is required for coverage
triggered or CS fallback-triggered redirect from
Coverage-Triggered WCDMA Session
Prerequisite LTE to WCDMA.
Continuity (FAJ 121 0493)
The session continuity access times are
improved for the Coverage-Triggered WCDMA
Session Continuity feature.
TDD only: The Coverage-Triggered TD-SCDMA
Session Continuity feature is required for
coverage triggered or CS fallback-triggered
Coverage-Triggered TD-SCDMA Session
Prerequisite redirect from LTE to TD-SCDMA.
Continuity (FAJ 121 3004)
The session continuity access times are
improved for the Coverage-Triggered TD-
SCDMA Session Continuity feature.
The CS Fallback to GERAN and UTRAN feature
is required for CS fallback from LTE to GSM,
CS Fallback to GERAN and UTRAN (FAJ 121 WCDMA, or TD-SCDMA (TDD only).
Prerequisite
0856) The session continuity access times are
improved for the CS Fallback to GERAN and
UTRAN feature.
When the PSHO-Based CS Fallback to UTRAN
and Redirect with System Information features
PSHO-Based CS Fallback to UTRAN(FAJ 121 are used together, NACC information is included
Related
3072) in RRC connection release message after
measurement timeout or handover preparation
failure.
RAN Information Management associations are
not supported for MORAN cells on the eNodeB
configured with MORAN on Single Baseband
configuration.
To prevent RAN Information Management
associations, the following attributes must be
Shared LTE RAN (FAJ 121 0860) Related set to RIM_INCAPABLE:
– [Link]

– [Link]

– [Link]

6 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

H a rd wa re
No specific hardware requirements.

L im i tat io ns
The support of the Redirect with System Information feature is limited under shared network setup. Only those RAN
Information Management associations get established that belong to the operator of primary PLMN.
Note: RAN Information Management associations that belong to the non-primary PLMN can only be enabled if the
correct routing information for non-primary PLMN eNodeBs is defined in the MME of the primary PLMN.

Ne twork Requ i reme nts


To benefit from this feature, the UEs must support e-RedirectionUTRA-r9 or e-RedirectionGERAN-r9
capability. For more information, see 3GPP TS 36.331 Section 6.3.6.

7 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

8 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

3 Feature Operation of Redirect with System Information


This feature supports the redirection of UEs by adding system information for cells.

The Redirect with System Information feature extends the following features by including system information for cells
belonging to the target RAT when performing RRC connection release with redirect to GSM, WCDMA, or TD-SCDMA:

– Coverage-Triggered GERAN Session Continuity

– Coverage-Triggered WCDMA Session Continuity

– Coverage-Triggered TD-SCDMA Session Continuity

– CS Fallback to GERAN and UTRAN

The RAN Information Management function collects information from NACC for GERAN and system information for
UTRAN. The feature enables the UE to connect to the target cell faster because the system information is directly
supplied to it during release time. It is unnecessary to read the system information from the target system.

3.1 RAN Information Management Pool Concept


P riority Pools
To limit the load on a system, RAN Information Management associations are set up to some external cells. These cells
are then subject to decision about redirection with NACC at UE release or CS Fallback with NACC. The prioritized
external cells are selected based on the [Link] or
[Link] attribute.
For each E-UTRAN cell, two pools of prioritized external cells are created, one for session continuity and one for CS
Fallback purpose. Different sets of two pools are created separately for GERAN and UTRAN. An external cell can be
present in both the session continuity and CS Fallback pools.
All pools from E-UTRAN cells are coordinated to create a primary set of associations on an eNodeB level to avoid
duplication of associations created for the same external cell.

Building P riority Pools


The priority pools are initially built at the eNodeB start up. All GERAN and UTRAN neighboring cells are initially
evaluated from a license and RAN Information Management association capability point of view. Suitable external
cells are subject to the prioritization algorithm to create the pools. After the evaluation, necessary RAN Information
Management associations are created.

Updating P riority Pools


The pools are updated dynamically when RAN Information Management conditions or coverage conditions change.
The eNodeB checks condition changes that affect pool prioritization of external cells. A given cell can be moved in or
out of a pool depending on the circumstances.
Supervised conditions specifically concern the following points:

– The value of the [Link] or


[Link] attribute

– RAN Information Management capability

– Cell creation

– Cell removal

– Relation creation

– Relation removal

9 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

The adaptation of the pool content can result in the creation or removal of RAN Information Management associations,
according to the current needs.
If the eNodeB tags a target BSS as RIM_INCAPABLE, the relevant rimCapable attribute must be set to the following
values in this order to be able to set up an eNodeB association with BSS:

1. RIM_INCAPABLE

2. RIM_CAPABLE

3.2 Configuration
For a coverage-triggered RRC connection release with redirect, the system information is only included f if the
mobilityAction parameter is set to RELEASE_WITH_REDIRECT_NACC for the specific RAT.

For a CS fallback-triggered RRC connection release with redirect, the system information is only included if the
mobilityActionCsfb parameter is set to RELEASE_WITH_REDIRECT_NACC for the specific RAT.

For UTRAN, the system information is also included for CS fallback-triggered RRC connection release after
measurement timeout or handover preparation failure, if the mobilityActionCsfb parameter is set to HANDOVER.

3.3 Prioritization of Cells


The prioritization of external cells is based on how the [Link] or
[Link] attribute is configured. The CSFB and Session Continuity pools have
their own level of priority.

Cell candidates with the same [Link] or


[Link] value are placed in the prioritized list in a random order. If there are
more than four cell candidates with the same [Link] or
[Link] value placed in the top of the prioritized list, only the first four cells
from the list are used for pool constitution.

For the CSFB list, the eNodeB includes system information for cells with the
[Link] or [Link] attribute set to the
following values in this order:

1. COVERS

2. OVERLAP

3. CONTAINED_IN or NONE

For the Session Continuity list, the eNodeB includes system information for cells with the
[Link] or [Link] attribute set to the
following values in this order:

1. COVERS

2. NONE

3. OVERLAP

4. CONTAINED_IN

The Session Continuity and CSFB pool prioritization rules affect the number of RAN Information Management
associations. Each internal cell adds the first four candidates in its Session Continuity pool and its CSFB pool.

Figure 1 shows what happens when the Session Continuity and CSFB pool structure is the same in each internal cell.

10 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

Figure 1 An eNodeB with the Same External Cells Highly Prioritized

Each pool contains the same candidates, and every candidate has the [Link]
or [Link] attribute set to COVERS. Four active RAN Information Management
associations are set up in the eNodeB.

Since the Session Continuity and CSFB structures are the same in the internal cells, they add the same external cells.
However, each association is only added once, regardless of how many internal cells it is used in. This is because the
RAN Information Management associations are between the eNodeB and the target cell.

Figure 2 shows what happens when the Session Continuity and CSFB pool structure is different in each internal cell.

Figure 2 An eNodeB with Different External Cells Highly Prioritized

The pools contain different candidates, and the candidates have the [Link] or
[Link] attribute set to different values. Six active RAN Information
Management associations are set up in the eNodeB.

Each association is only added once, regardless of how many internal cells it is used in. This is because the RAN
Information Management associations are between the eNodeB and the target cell.

11 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

12 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

4 Network Impact of Redirect with System Information


This feature reduces outage times.

C apac it y and P er fo rm ance


The Redirect with System Information feature reduces outage time for release.

I nte r fa c e s
No impact.

Ot her N et wor k El e me nts


No impact.

13 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

14 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

5 Parameters for Redirect with System Information


This feature introduces parameters related to GERAN and UTRAN cells.

Table 2 Parameters
P a ra m e te r Ty pe Description
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.
[Link] Introduced See MOM description.

15 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

16 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

6 Performance of Redirect with System Information


This feature uses counters related to connection release and RAN Information Management association and events
are generated when UEs are released with redirection.

KPIs
This feature has no associated KPIs.

C o u nte r s

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

17 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

– [Link]

Eve nt s

Table 3 Events

Eve nt Eve nt P a ra m e te r
EVENT_PARAM_MOBILITY_DECISION
INTERNAL_EVENT_UE_MOBILITY_EVAL
EVENT_PARAM_RELEASE_WITH_REDIRECT_REASON

For more information about events, see Lists and Delta Lists.

18 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

19 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

7 Activate Redirect with System Information


To use the feature, it must be activated following the usual feature activation procedure.

P rere q u i s i tes

– The license key is installed in the node.

– CCTR is active for at least one week before this procedure to collect enough troubleshooting data.

– The prerequisite features are enabled in the node.

Ste p s

1. Set the [Link] attribute to ACTIVATED in the FeatureState=CXC4010973 MO


instance.

After This Task


Keep CCTR active for at least one week after this procedure for continued collection of troubleshooting data.

20 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

21 of 22 12/11/2024, 8:30 AM
Redirect with System Information [Link]

8 Deactivate Redirect with System Information


If the feature is no longer needed, it can be deactivated following the usual feature deactivation procedure. It must
also be deactivated before the activation of any conflicting feature.

P rere q u i s i tes
CCTR is active for at least one week before this procedure to collect enough troubleshooting data.

Ste p s

1. Set the [Link] attribute to DEACTIVATED in the FeatureState=CXC4010973 MO


instance.

After This Task


Keep CCTR active for at least one week after this procedure for continued collection of troubleshooting data.

Legal | © Ericsson AB 2016-2019, 2021-2024


Copyright © Ericsson AB 2016-2019, 2021-2024. All rights reserved. No part of this document may be reproduced in
any form without the written permission of the copyright owner.

Disclaimer The contents of this document are subject to revision without notice due to continued progress in
methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind
resulting from the use of this document.

Trademarks All trademarks mentioned herein are the property of their respective owners. These are shown in the
document Trademark Information.

22 of 22 12/11/2024, 8:30 AM

You might also like