100% found this document useful (1 vote)
851 views

CSFB With RIM

Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
851 views

CSFB With RIM

Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 34

RAN3086 CSFB with RIM

Network Engineering Information


• Piotr Kowalski
• 14.09.2015

Please always check the latest version of the NEI slides!

1 © Nokia Solutions and Networks 2015


For internal use
Disclaimer

• Please note that the NEI materials are for internal use only. If they shall be used as a
source for the customer presentation, it is mandatory to align the contents with the
Product Management and/or local sales teams at first!

• This NEI slide deck reflects the state of the feature/solution as it is at the moment of
the NEI slide deck release and is being updated up to C5 (release available) milestone.

2 © Nokia Solutions and Networks 2015


RAN3086 CSFB with RIM
Table of contents

Introduction Technical Inter – Benefits and Configuration Deployment


Details dependencies Gains Management Aspects
Motivation and Feature Detailed Functionality Simulation, Lab and Parameters and
Interdependencies with Activation,
Overview Description Field Findings Parameterization
other features and Simulation, Lab Configuration Examples,
functions Scenarios Fault Mgmt, Trial Area
1 and Field Findings

5 © Nokia Solutions and Networks 2015


For internal use
RAN3086 CSFB with RIM

Introduction

Table of contents

6 © Nokia Solutions and Networks 2015


For internal use
Introduction
CSFB introduction
VoLTE
• Voice call in LTE may be established only if capable UE
network supports VoLTE solution and also
if UE terminal is VoLTE capable
• If at least one of these conditions is not
met the only way to establish a voice call
for the UE served by the LTE is to move it
towards RAT other than LTE with CS
Request for
domain
voice service
LTE coverage area
• For this purposes 3GPP has defined so LTE coverage area
called CSFB procedure. In the context of
CSFB toward WCDMA it is possible to
WCDMA coverage area
move the UE:
Handover/Redirection
- via redirection LTE562
- via PSHO LTE736

7 © Nokia Solutions and Networks 2015


For internal use
Introduction
SIB configuration

• In case of CSFB via redirection the main issue is call setup time. In the
RRC Connection
standard way after UE receives RRC Connection Release message with Release message
redirect info, the first thing UE have to do is acquisition of SIB content (SIB’s included)
broadcast by target WCDMA cell. This may spent a lot of time
• To speed up call setup on WCDMA side, the content of SIBs broadcast in
target cells may be provided to the UE directly by including appropriate
information in RRC Connection Release message with redirect
• If selected WCDMA cell is one of these listed in RRC Connection Release
with redirect there is no need to read SIBs content by the UE. Finally the
call setup time for CSFB via redirection may be speeded up
• How to configure SIBs content of WCDMA cells on LTE side?
- This may be done manually in eNB however it requires some operator
actions
• The entries on LTE side shall reflect exactly the same
configuration which is applied on WCDMA side. It means high risk LTE coverage area WCDMA coverage area
of faults or not up to date information in case some
reconfiguration is done on WCDMA side
Redirection procedure
- Automatically with help of RIM protocol – eNB exchange the
information with RNC about SIB content in WCDMA cells

8 © Nokia Solutions and Networks 2015


For internal use
Introduction
CSFB via redirection - evolution

CSFB blind redirection CSFB via redirection CSFB redirection with CSFB with RIM via
with meas. Sys Info Provisioning redirection
(LTE562) (LTE1073) (CRL 0562) (RAN3086) (LTE1196)
WCDMA LTE WCDMA LTE WCDMA LTE WCDMA LTE
[Connected Mode] [Connected Mode] [Connected Mode] [Connected Mode] [Connected Mode] [Connected Mode] [Connected Mode] [Connected Mode]

Idle Mode Idle Mode Idle Mode Idle Mode Idle Mode Idle Mode Idle Mode Idle Mode

Target WCDMA layer is Target WCDMA layer is RRC Connection Release RRC Connection Release
selected based entries in selected based on message provides message provides
REDRT/MORED.MODRED event B2 related information about SIBs information about SIBs
(ARFCNs and priorities) measurements content used by target content used by target
WCDMA cells; manually WCDMA cells; SIBs
created on eNB content on eNB is
provided in automated
way with the help of RIM

9 © Nokia Solutions and Networks 2015


For internal use
Introduction
Before & after

Before After

• WCDMA SIB information were manually • With this feature WCDMA SIB
configured in the eNB information is provided to eNB
automatically
Manually added Automatically
WCDMA SIB added WCDMA
information RRC Connection
Release SIB Information RRC Connection
release

LTE WCDMA LTE WCDMA

10 © Nokia Solutions and Networks 2015


For internal use
RAN3086 CSFB with RIM

Technical Details

Table of contents

11 © Nokia Solutions and Networks 2015


For internal use
Technical Details
Dependency Table (WCDMA)

Release information Sales information


RAS release WCDMA16 BSW/ASW ASW
Flexi Direct release - RAS SW component RAN
RNC release RN8.1 Licence control in
RNC LK
mcRNC release mcRNC4.1 NE
BTS Flexi release Support not required Licence control Long-term on/off
BTS Flexi Lite attributes license
Support not required
release
BTS Flexi HW
-
release
NetAct release -
UE release 3 GPP Rel-9

12 © Nokia Solutions and Networks 2015


For internal use
Technical Details
Overview(1/2)

• RAN3086 supports RIM(RAN Information Management) procedure in RNC


- With RIM it is possible to exchange information between different Radio Access Technologies
via the Core Network
• As a result System Information used in WCDMA cells can be automatically provided to
eNB which reduces manual effort in SI configuration
- Manual configuration of SI on LTE side is no longer a blocking point in CSFB with SI deployment
• System Information(SI) of WCDMA cells provided to UE with the help of RRC
Connection release message with redirect may speed-up call setup time on 3G side in
case of CSFB via redirection

13 © Nokia Solutions and Networks 2015


For internal use
Technical Details
Overview(2/2)

• WCDMA SIB information is retrieved by eNB


via CN with RIM procedure
- SGs interface between MME and MSC is
needed
- Interworking between SGSN and MME
and PDN-GW is realized via Gn interface
or via S3/S4 interfaces
SGs Gn/S3/S4
MSC PDN-GW
eNB RNC
Gn/S3/S4

MME SGSN
RIM data

14 © Nokia Solutions and Networks 2015


For internal use
Technical Details
Overview(2/2)

• WCDMA SIBs are delivered to eNB with use


Request for Voice Service RIM Procedure
of the RIM procedure
WCDMA SIBs content
- When CSFB is needed, eNB can add information
WCDMA SIBs content to RRC eNB
UE CN
Connection Release message
- BCCH Container keeps information
about transmitted SIBs RRC Connection Release

BCCH Container UTRA BCCH Container


MIB
SIB1
SIB3
SIB5
SIB7
SIB11

15 © Nokia Solutions and Networks 2015


For internal use
Technical Details
RIM signaling procedure

eNB CN RNC
• The eNB requests Single or Multiple
Report from RNC’s cell which initialize RIM
signaling RAN INFORMATION REQUEST
RAN INFORMATION REQUEST
- Then RNC will answer to this request RAN INFORMATION
with Single Report – RNC immediately RAN INFORMATION
replies for request with the current SIB Cell Modification
content. No further actions RAN INFORMATION(Update)
RAN INFORMATION(Update)
- Multiple Report – Also immediate
RAN INFORMATION(ACK)
response with SIB information. RAN INFORMATION(ACK)
Additionally, whenever relevant SIB
Cell Deletion
content is modified in the cell, RNC
RAN INFORMATION(END)
send a system information report to RAN INFORMATION(END)
LTE
RAN INFORMATION(ACK)
RAN INFORMATION(ACK)

16 © Nokia Solutions and Networks 2015


For internal use
Technical Details
RIM signaling procedure

eNB CN RNC
• Then RNC will answer to this request with
SIB information of the specific cell
RAN INFORMATION REQUEST
- In case of any modification of the cell, RAN INFORMATION REQUEST
updates of the SIB’s will be send only RAN INFORMATION
when Multiple Reporting is in use RAN INFORMATION
Cell Modification
- Other vendor’s eNB may require Single
Report from Nokia RNC (Single Report RAN INFORMATION(Update)
RAN INFORMATION(Update)
support needed)
RAN INFORMATION(ACK)
• RNC terminates the updates of SIB’s RAN INFORMATION(ACK)

(Multiple Report) when, e.g. the Cell Deletion


reporting cell is deleted in RNC RAN INFORMATION(END)
RAN INFORMATION(END)
Updates from Multiple
Reports indicate that RIM RAN INFORMATION(ACK)
RAN INFORMATION(ACK)
Association is ongoing
17 © Nokia Solutions and Networks 2015
For internal use
Technical Details
Supervision timer for RIM association

• RIM association means the relationship between RNC eNB


3G cell and 4G eNB which is used for CSFB with
RIM Core
• RNC can supervise the RIM association (multiple Network
report) by sending RAN Information to eNB
every 120 (hardcoded value) minutes
• RIM association does not exist in eNB if:
- RNC receives RAN Information Error
- The wait timer (15 seconds) expires
RAN INFORMATION
• Wait timer is set after sending RAN Information (Checking
and reset when RNC receives the response. This existence of RIM
timer is hardcoded. association)

18 © Nokia Solutions and Networks 2015


For internal use
Technical Details
Cell deletion of RIM UTRA SI Target Cell NodeB

NodeB
NodeB
• If the cell has been permanently removed, RAN
INFORMATION/END PDU will be send to all eNB’s
• Also cell can be temporarily unavailable, e.g.
NBAP(Node B Application Part) link to NodeB RNC
Cell
does not work Deletion
- In such situation, RNC will wait 120(hardcoded Core Network
value) seconds to recover the resources
- In case of not re-creating cell resources MME
during that time, RNC will delete the RIM eNodeB
association eNodeB
eNodeB
All eNB’s receive RAN
INFORMATION END
message

19 © Nokia Solutions and Networks 2015


For internal use
Technical Details eNodeB
Barred RIM UTRA SI Target Cell
eNodeB
• Information about cell state is included in
MME
SIB3
• If the cell state is barred, UE will have to
search another cell for CSFB (cell with not-
barred state) Core Network
1
• When the cell state changes (barred, not SI request
from eNB
barred), RNC will send the updated system
information container, only when multiple NodeB NodeB
RNC
report is in use

2
3
Barred cell Searching
for another
cell for CSFB

20 © Nokia Solutions and Networks 2015


For internal use
Technical Details
RANAP Protocol (DIRECT INFORMATION TRANSFER MESSAGE)
Direct Information
• RANAP protocol is used to RANAP Transfer Message RANAP
transport and route RIM PDU’s
between RNC and SGSN Iu

• After activation of the feature RNC SGSN


eNB will inquire RIM data from
IE/Group Name Presence
RNC
Message Type M
• Then RNC entity will receive
Inter-system O IE/ Group Name Presence
Direct Information Transfer Information Transfer RIM Information M
message (RANAP protocol Type
signaling message) from CN RIM Routing Address O
CN Domain indicator M

- Inside RANAP message Global RNC-ID O


there is RIM Information Global CN-ID O
which include UTRA SI Extended RNC-ID O UTRA SI Container is included
Container in RIM Information

21 © Nokia Solutions and Networks 2015


For internal use
Technical Details
UTRA SI Container
IE/Group Name Need Version

• MIB, SIB1, SIB3, SIB5, SIB7 are the MIB MP Scheduling information on SIB’s REL-9

mandatory content SysInfoTypeSB1 OP REL-9

SysInfoTypeSB2 OP REL-9
• SIB11 is optional and could be
included in System Information SysInfoType1 MP NAS(Non access stratum) Information REL-9

Container according to Deferred SIB SysInfoType3 MP Cell selection/reselection parameters REL-9


Reading functionality
SysInfoType5 MP Information on common physical channels for UE REL-9
- If Deferred SIB Reading is on,
SIB11 is not included SysInfoType7 MP Fast changing cell parameters information REL-9

• The UTRA SI Container is a part of SysInfoType11 OP Measurement control information (UE in IDLE Mode) REL-9

RIM UTRA SI Application Container SysInfoType11bis OP REL-9


inside the RAN Information PDU
SysInfoType12 OP REL-9

SysInfoType22 OP REL-11

22 © Nokia Solutions and Networks 2015


For internal use
RAN3086 CSFB with RIM

Interdependencies

Table of contents

23 © Nokia Solutions and Networks 2015


For internal use
Interdependencies

LTE1196 RAN Information Management for UTRAN


prerequisites
Supporting mechanism for CSFB with RIM is required from the LTE side.

More information regarding LTE1196 can be found in dedicated NEI slide


set under the sharenet link

24 © Nokia Solutions and Networks 2015


For internal use
Interdependencies

RAN2746 Fast HSPA Mobility


extensions
With „Deferred SIB Reading” functionality, RNC can inform in SIB3 that UE do
not need to read SIB11, SIB11bis and SIB12 before transmitting on RACH.

Therefore, the RNC do not need to include SIB11 into the System
Information report to the eNB.

This speeds-up setup time after cell selection/reselection.

25 © Nokia Solutions and Networks 2015


For internal use
Interdependencies

RAN801 Radio Network Access Regulation Function


limitations
RAN1167 Domain Specific Access Class restriction
RAN2480 Automatic Access Class Restriction
RAN3018 BTS Load Based AACR

When any of access class restriction features is active, SIB3 is frequently


updated which increases signaling between RNC and eNB

26 © Nokia Solutions and Networks 2015


For internal use
RAN3086 CSFB with RIM

Benefits and Gains

Table of contents

27 © Nokia Solutions and Networks 2015


For internal use
Benefits and Gains
Customer Benefits

• RIM improve inter RAT mobility procedures for users in multiple-RAT environment
• Thanks to RIM procedure WCDMA SIB’s can be configured automatically, which decreases the
manual effort of adding SIB’s in eNB
• Automated configuration of SIB’s can speed-up call setup time. The benefit is in order of few
hundred milliseconds

28 © Nokia Solutions and Networks 2015


For internal use
RAN3086 CSFB with RIM

Configuration
Management
Table of contents

29 © Nokia Solutions and Networks 2015


For internal use
Configuration Management
New parameter

Abbreviated name Full name PKDB link


RNFC:RIMUtraSIEnab RIM UTRA System Information
Application Enabled

31 © Nokia Solutions and Networks 2015


For internal use
Configuration Management
Related parameter

Abbreviated name Full name PKDB link


WCEL:DefMeasCtrlReading Deferred Measurement Control
Reading
WCEL:FastHSPAMobilityEnabled Fast HSPA Mobility Enabled

32 © Nokia Solutions and Networks 2015


For internal use
RAN3086 CSFB with RIM

Deployment
Aspects
Network graphic boxes Network element boxes
Table of contents

33 © Nokia Solutions and Networks 2015


For internal use
Deployment aspects
Activation, verification, deactivation

RAN3086 Activation RAN3086 Verification RAN3086 Deactivation


• Check that the license for • Check the RNC logs and • CSFB with RIM is activated
CSFB with RIM exists verify the message flow and in use
• Steps - Deactivate the license

1,234 123+
1. Activate the license
CSFB with RIM
of for CSFB with RIM
- Set
2.Activate the feature RNFC:RIMUtraSIEnab as

99.9
by setting parameter ‘Disabled’ value
RNFC:RIMUtraSIEnab as
‘Enabled’ value

88
34 © Nokia Solutions and Networks 2015
For internal use
Deployment aspects
RAN level usage(1/2)

• Operator may want to use CSFB with S3/Gn


RIM as an option in addition to other
MME SGSN
CSFB via redirection features
• Feature can be implemented when
Operator has System Information
provisioning enabled or not
- WCDMA SIB’s could be configured RNC
eNB
automatically and then Operator
turns System Information
UE
provisioning if it was not yet (LTE coverage area) (WCDMA coverage area)
enabled
- WCDMA SIB’s will be automatically
updated and Operator do not have
to manually introduce changes of
WCDMA SIB’s

35 © Nokia Solutions and Networks 2015


For internal use
Deployment aspects
RAN level usage(2/2)

• RIM message could be used in MOCN (Multiple Operator Core Network)


• It can be implemented in the scenarios presented below
- Scenario 1 is for the case that different MOCN operator has its own WCDMA network
- Scenario 2 is for the case that different MOCN operators share the same WCDMA network also
• Even if only one Operator use CSFB with RIM feature on the 3G side, it will still work properly

Scenario 1 Scenario 2
SGSN RNC
MME SGSN
MME
eNB RNC
eNB
MME SGSN RNC SGSN
MME

36 © Nokia Solutions and Networks 2015


For internal use
37 © Nokia Solutions and Networks 2015
For internal use

You might also like