Вы находитесь на странице: 1из 14

RAN Information Management (RIM) for GSM

➢LTE498: RAN Information Management (RIM) for GSM feature

1 © Nokia Networks 2015


Confidential
RELATED FEATURES
Related Feature in LTE
➢ LTE498: RAN Information Management (RIM) for GSM feature

Related Feature in GSM

➢ BSS21355: Inter-System Network-Assisted Cell Change for LTE (IS-NACC for LTE)[ZW7M:FEA=1528]
➢ BSS11506 : NACC FEATURE [ZW7M:FEA=10]
➢ BSS20083: IB-NACC FEATURE [ZW7M:FEA=66]
FEATURE CODE:..............1528
FEATURE NAME:..............Inter System NACC for LTE
FEATURE STATE:.............ON
FEATURE CAPACITY:..........1

FEATURE CODE:..............10
FEATURE NAME:..............NACC
FEATURE STATE:.............ON
FEATURE CAPACITY:..........1

FEATURE CODE:..............66
FEATURE NAME:..............ext NACC
FEATURE STATE:.............ON
FEATURE CAPACITY:..........1
2 © Nokia Networks 2015
Confidential
LTE 498 RIM for GSM
Key Functionality
• Feature LTE498 introduces the functionality “RIM for GSM” to transfer up-to-date system information of GERAN
neighbor cells from remote BSC to local eNB (see [TS48.018]), which can be used to populate GERAN System
Information for eNACC procedure (LTE442), CSFB to GSM and redirection to GSM procedure (LTE984).

• The RIM function enable the eNB to retrieve system information from a target GSM cell: SI1, SI3 and SI13

• RL40 up to 256 relation to GSM can be created per one eNB (e.g. via Inter-RAT ANR features)

• Currently this information is provided by management system in LNADJG object, but as system information changes
quite often, without this feature there were operation challenges

• UE can avoid reading of System Information Broadcasts when accessing the target cell and hence to shorten the
connection setup times for both CS voice call (for CS Fallback) and PS connection (redirection due to radio conditions).

3 © Nokia Networks 2015


• LTE498 retrieves the GERAN
Confidential System Information from the remote BSC handing the GERAN cell using RIM protocol
9/4/ Document ID / v. 0.1 / Life
LTE 498 RIM for GSM
Key Functionality
3GPP 23.401:
“The RAN Information Management (RIM) procedures provide a generic mechanism for the exchange of
arbitrary information between applications belonging to the RAN nodes [eNB, RNC, BSC].

The RAN information is transferred via the MME and SGSN core network node(s).

In order to make the RAN information transparent for the Core Network, the RAN information is included
in a RIM container that shall not be interpreted by the Core Network nodes.”

The exchange of information is triggered by the application in a controlling BSS

4 © Nokia Networks 2015


9/4/2019
LTE 498 RIM for GSM
E-UTRAN to GERAN NACC basic network
Key Functionality architecture
A SGSN or MME shall use the destination address
included in each RIM PDU either to send the PDU to the
relevant BSS, RNS or eNodeB through the Gb, the Iu or
RIM Signaling the S1 interface.

eNodeB S1 MME

E-UTRAN Relaying RIM


Signaling S3/Gn Each message carrying the RIM container is routed
and relayed independently by the core network
node(s). Any relation between messages is
GERAN
transparent for the MME/SGSN, i.e. a
request/response exchange between RIM applications,
Gb/Iu for example, is routed and relayed as two independent
BSS SGSN messages by the MME/SGSN.

RIM Signaling

5 © Nokia Networks 2015


Confidential
CONFIGURATION

6 © Nokia Networks 2015


Confidential
LNBTS Parameter

▪ RAN Information Management (RIM) for GSM parameter to be Enabled


7 © Nokia Networks 2015
Adjacency definition

▪ All LNADJ parameters defined properly. If the connectivity is through then the RIM Interface
status will be available
8 © Nokia Networks 2015
Adjacency definition

▪ redirWithSysInfoAllowed=allowed

9 © Nokia Networks 2015


RIM STATUS PRE AND POST

10 © Nokia Networks 2015


Nokia RIM Feature Results

11 © Nokia Networks 2015


CSFB to 2G :: With and With out RIM
With out RIM With RIM Active
CSFB to CSFB With out RIM CSFB to CSFB With RIM
EventId Time RRC subchannel
RRC direction RRC message name Remarks Time Spent EventId Time RRC subchannel RRC direction RRC message name Remarks Time Spent
L3SM 40:33.3 Uplink EXTENDED_SERVICE_REQUEST Call Start L3SM 45:41.2 Uplink EXTENDED_SERVICE_REQUEST Call Start
RRCSM 40:33.3 DCCH Downlink RRCConnectionRelease ESR to RRC Conn. Release 00:00.0 RRCSM 45:41.3 DCCH Downlink RRCConnectionRelease ESR to RRC Conn. Release 00:00.1
L3SM 40:35.6 DCCH Uplink 1
LOCATION_UPDATING_REQUEST RRC Conn. Release to LU request 00:02.3 L3SM 45:42.0 DCCH Uplink 1
LOCATION_UPDATING_REQUEST RRC Conn. Release to LU request 00:00.7
L3SM 40:36.0 CCCH Downlink IMMEDIATE_ASSIGNMENT LU Request to Imm. Asignment 00:00.4 L3SM 45:42.2 CCCH Downlink IMMEDIATE_ASSIGNMENT LU Request to Imm. Asignment 00:00.2
L3SM 40:38.7 DCCH Downlink LOCATION_UPDATING_ACCEPT LU req. to LU Accept 00:02.7 L3SM 45:44.8 DCCH Downlink LOCATION_UPDATING_ACCEPT LU req. to LU Accept 00:02.8
L3SM 40:39.6 DCCH Uplink SETUP 2 ESR to Setup 00:06.4 L3SM 45:47.6 DCCH Uplink SETUP 2 ESR to Setup 00:06.4
L3SM 40:48.0 DCCH Downlink ALERTING Setup to alerting time 00:08.4 L3SM 45:57.9 DCCH Downlink ALERTING Setup to alerting time 00:10.3
3 Call Setup Time 00:14.7 3 Call Setup Time 00:16.7

L3SM 41:40.3 Uplink EXTENDED_SERVICE_REQUEST Call Start L3SM 46:57.1 Uplink EXTENDED_SERVICE_REQUEST Call Setup time
RRCSM 41:40.4 DCCH Downlink RRCConnectionRelease ESR to RRC Conn. Release 00:00.0 RRCSM 46:57.2 DCCH Downlink RRCConnectionRelease ESR to RRC Conn. Release 00:00.1
L3SM 41:41.5 DCCH Uplink LOCATION_UPDATING_REQUEST RRC Conn. Release to LU request 00:01.2 L3SM 46:57.8 DCCH Uplink LOCATION_UPDATING_REQUEST RRC Conn. Release to LU request 00:00.6
L3SM 41:41.9 CCCH Downlink IMMEDIATE_ASSIGNMENT LU Request to Imm. Asignment 00:00.4 L3SM 46:57.9 CCCH Downlink IMMEDIATE_ASSIGNMENT LU Request to Imm. Asignment 00:00.1
L3SM 41:44.5 DCCH Downlink LOCATION_UPDATING_ACCEPT LU req. to LU Accept 00:02.6 L3SM 47:00.7 DCCH Downlink LOCATION_UPDATING_ACCEPT LU req. to LU Accept 00:02.8
L3SM 41:45.5 DCCH Uplink SETUP ESR to Setup 00:05.1 L3SM 47:03.0 DCCH Uplink SETUP ESR to Setup 00:05.9
L3SM 41:53.8 DCCH Downlink ALERTING Setup to alerting time 00:08.4 L3SM 47:13.4 DCCH Downlink ALERTING Setup to alerting time 00:10.4
Call Setup Time 00:13.5 Call Setup Time 00:16.3

1
RRC Connection release to LU Request Further exercise required to Reduce overall
Time is reduced with RIM from 1 to 2 call setup time.
2
seconds to 0.6 to 0.7 seconds. 1) LU time is ~2.5 sec
RRC Release Message in Next slide 2) Call Setup time in 2G is more than 8 sec. 3

12 © Nokia Networks 2015


RRC Release Message : Layer 3
SIB 1 , SIB2 and SIB3 in RRC Release Message

1 2 3

13 © Nokia Networks 2015


14 © Nokia Networks 2015