ran3007 cn selection method for iu request routing when ue roams from different plmn

7/21/2019 RAN3007 CN Selection Method for IU Request Routing When UE Roams From Different PLMN

http://slidepdf.com/reader/full/ran3007-cn-selection-method-for-iu-request-routing-when-ue-roams-from-different 1/21

RAN3007: CN Selection Method forIU Request Routing when UERoams from Different PLMN

Issue

Approval date 2013-12-16



Disclaimer RAN3007 CN Selection Method for IU Request Routingwhen UE Roams from Different PLMN

2 /21 Copyright © 2014 Nokia Solutions and Networks. All rights reserved.

Order No.Document ID Issue

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Solutions and Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmittedin any form or means without the prior written permission of Nokia Solutions and Networks. The

documentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Solutions and Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.The information or statements given in this documentation concerning the suitability, capacity,or performance of the mentioned hardware or software products are given "as is" and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Solutions and Networks and the customer. However,Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. Nokia Solutionsand Networks will, if deemed necessary Nokia Solutions and Networks, explain issues whichmay not be covered by the document.Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION

OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITEDTO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITYOR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATIONIN IT.

NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of NokiaCorporation. Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright © Nokia Solutions and Networks 2014. All rights reserved.

Nokia Solutions and Networks are continually striving to reduce the adverse environmental effects ofits products and services. We would like to encourage you as our customers and users to join us inworking towards a cleaner, safer environment. Please recycle product packaging and follow therecommendations for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental serviceswe offer, please contact us at Nokia Solutions and Networks for additional information.



RAN3007 CN Selection Method for IU Request Routingwhen UE Roams from Different PLMN

Table of Contents


Copyright © 2014 Nokia Solutions and Networks. All rights reserved.

3/21

Table of Contents

This document has 21 pages.

Summary of changes ...................................................................................... 6

1 Software requirements .................................................................................... 7

2 CN Selection Method for IU Request Routing when UE Roams from DifferentPLMN .............................................................................................................. 8

2.1 Description ...................................................................................................... 8

3

Different PLMN routing methods ................................................................... 11

3.1

Basic Method ................................................................................................ 11

3.2 NRI ROUTING for registration ....................................................................... 11

3.3

NRI ROUTING when NRI match with previous PLMN (old LAI) and for CallCases............................................................................................................ 12

3.4

NRI ROUTING when NRI match with previous PLMN or equivalent PLMN (oldLAI) ............................................................................................................... 12

4 Activation control (licence key, PRFILE) ........................................................ 14

5

Checking the state of feature activation ......................................................... 15

5.1 IPA-RNC ....................................................................................................... 15

5.2 mcRNC and FD-RNC .................................................................................... 15

6

Activation instructions ................................................................................... 16

6.1 IPA-RNC ....................................................................................................... 16

6.1.1 Basic Method ................................................................................................ 16

6.1.2

NRI routing for registration ............................................................................ 17

6.1.3 OLD LAI routing for registration and NRI routing for another procedures ...... 17

6.1.3.1

Allowed NRI routing from additional PLMNs with OLD LAI routing

for registration ............................................................................................... 17

6.2 mcRNC and FD-RNC .................................................................................... 18



Software requirements RAN3007 CN Selection Method for IU Request Routingwhen UE Roams from Different PLMN



6.2.1 Basic Method ................................................................................................ 18

6.2.2

NRI routing for registration ............................................................................ 19

6.2.3

OLD LAI routing for registration and NRI routing for another procedures ...... 19

6.2.3.1 Allowed NRI routing from additional PLMNs with OLD LAI routing

for registration ............................................................................................... 19

7 Deactivation instructions ............................................................................... 21

7.1 IPA-RNC ....................................................................................................... 21

7.2 mcRNC and FD-RNC .................................................................................... 21




Table of Contents



5/21

List of Tables

Table 1 Software requirements .................................................................................... 7

Table 2

TMSI Different PLMN routing methods .......................................................... 12



Software requirements RAN3007 CN Selection Method for IU Request Routingwhen UE Roams from Different PLMN



Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes between issues 1.1 (2013-10-28, RU50) and 1.2 (2013-12-10,RU50)

Added Description and mcRNC & FD-RNC

Added RU40 information

Changes between issues 1.0 (2013-10-16, RU50) and 1.1 (2013-10-28,RU50)

Updated feature details



RAN3071: Workaround for Faulty F-DCPH Support fromCertain UE Models

Software requirements



7/21

1 Software requirements

Table 1: Software requirements lists the software required for this feature.

Table 1: Software requirements

Flexi Direct RNC IPA-RNC mcRNC

RU40 I-Ada5.0 P8 RN7.0 1.0 mcRNC3.0 P8

RU50/EP1 I-Ada6.0 RN8.0 / RN8.1 mcRNC4.1

http://losdocumentos.wroclaw.nsn-rdnet.net:5905/informationbrowser/topic/m88653279_html/htm/docs/m89838529/fd_ran2290_2-0900d805809d739f/fd_ran2290_2-0900d805809d739f.html#fd_ran2290_2-0900d805809d739f__CEGCBEEJ

http://losdocumentos.wroclaw.nsn-rdnet.net:5905/informationbrowser/topic/m88653279_html/htm/docs/m89838529/fd_ran2290_2-0900d805809d739f/fd_ran2290_2-0900d805809d739f.html#fd_ran2290_2-0900d805809d739f__CEGCBEEJ



CN Selection Method for Iu request routing when UE roamsfrom different PLMN




2 CN Selection Method for Iu requestrouting when UE roams from differentPLMN

ID: RAN3007 NRI CN Selection Method for IU Request Routing when UERoams from Different PLMN is an enhancement for RAN966: Multi OperatorCore Network and RAN834: Flexible IU features.

NSN NW works according to 3GPP specifications but if the operator hasdedicated cells and shared cells, which are served in the same CN elementsor the operator has several different PLMN used in Radio Network, and whenUEs are roaming between these different networks, it will cause unnecessarysignaling when the RNC selects serving CN elements by using the loadsharing method.

Solve unnecessary signaling problem in many PLMNs network, NSNimplemented enhancement where operator can defined those PLMNs whereUE roaming shall be handled as like UE roams inside network to avoidunnecessary signaling and UE moving from one CN element to the anotherwhen IU pooling is used.

2.1 Description

When Iu-Flex is in use, and the same operator has a shared MOCN networkand an operator dedicated network, users will be moving between the two

network areas. When moving from MOCN area to dedicated area (where Iu-Flex is in use) the user will make a location update with routing basis"tmsidifferentPLMN". Since different PLMNs are in use in the dedicated areaand Common PLMN in MOCN, the RNC will route the user based on loadsharing. If the same core elements are used for MOCN and dedicated networkareas, users will be routed at least 50% of the time to the other core networkelement than the one they are served by. This will cause extra signaling. Thesame problem occurred when Iu-Flex is in use and the operator uses different




CN Selection Method for Iu request routing when UEroams from different PLMN



9/21

PLMNs for different networks (for example, GSM and WCDMA), but same CN-elements are used to serve UEs in both networks.

To improve the routing, it would be beneficial to use PLMN of the old LAI todecide the routing method. Additionally, it would be beneficial to be able todefine a couple of PLMN codes that the RNC checks in case of routing basis"tmsidifferentPLMN". And if it matches, apply the NRI routing to route the userto the core network element that is already serving the user. This will decreasethe signaling in the network.

Some UE models indicate unexpected “tmsidifferentPLMN” also in call cases,when the UE requests CM Service or answers Paging, when the UE hasmoved in connected mode to the cell, which has a different PLMN than theoriginal cell, where the RRC connection was established. In these cases, theold LAI is not available in the UE.

NSN offers the operator to define four different methods to manage CNselection when the UE roams from another PLMN under the cell of the RNC.

BASIC METHOD

NRI ROUTING for REGISTRATION

NRI ROUTING when NRI matches with previous PLMN and for callcases

NRI ROUTING when NRI matches with previous PLMN or equivalentPLMN



CN Selection Method for Iu request routing when UE roamsfrom different PLMN







Different PLMN routing methods



11/21

3 Different PLMN routing methods

3.1 Basic method

In the basic method, the RNC will use load sharing to select the CN elementwhere the UE request will be routed.

The basic method is used as the default method when MOCN is not in use.

The basic method is not used for Iu-Flex if old LAI is used for routing.

3.2 NRI routing for registration

Used only for Location Update, Attach and Routing Area Update.

In NRI routing, the RNC selects CN based on the received NRI from the UE:

- when NRI is valid, CN is selected based on NRI

If NRI is NULL NRI, then PLMN is selected by NRI but CNselection is made by load sharing from selected pool (PLMN).

If selected CN is not available, the RNC will use load sharing toselect another CN from same pool (PLMN).

If there is no available CN of the pool (PLMN) and MOCN isused, the RNC will select PLMN and CN by using load sharing,excluding PLMN of the NRI.

- when NRI is not valid, PLMN and CN is selected by load sharing



Different PLMN routing methods RAN3007 CN Selection Method for IU Request Routingwhen UE Roams from Different PLMN



3.3 NRI routing when NRI matches with previousPLMN (old LAI) and for call cases

In this method, registration procedures routing by NRI are limited only forcases when the old LAI contains the same PLMN as where NRI pointed. Otherprocedures routing will follow the NRI routing for registration without old LAIchecking.

3.4 NRI routing when NRI matches with previousPLMN or equivalent PLMN (old LAI)

In this method, registration procedures routing by NRI are limited for caseswhen the old LAI contains the same PLMN as where NRI pointed, or the oldLAI contains PLMN, which is defined as equivalent for PLMN where NRIpointed. Other procedures routing will follow NRI routing for registrationwithout old LAI checking.

Both old LAI based NRI routing methods follow NRI ROUTING FORREGISTRATION method. The only exception is that when NRI is not valid forprevious PLMN or its equivalent PLMN from the old LAI, then NRI is handledas an invalid NRI.

Table 2. TMSI Different PLMN routing methods

METHOD NRI ACTION

BASIC METHOD - CN selected by Load Sharing

NRI ROUTING FORREGISTRATION

Only for Location Update, Attach or Routing Area

Update

Valid

CN selected by NRI f CN isdown then another CN from

same pool will be selected byload sharing

NULL NRIPLMN selected by NRI and CN

from pool will be selected by

load sharing

Not valid NRIPLMN and CN selected by Load

Sharing

OLD LAI ROUTING ANDCALL CASE NRI

ROUTING

Other than LU, Attach

Valid for previous PLMN

CN selected by NRI if CN isdown, then another CN from the





Different PLMN routing methods



13/21

and RAU no OLD LAIchecking

NULL NRI of theprevious PLMN

PLMN selected by NRI and CNfrom pool will be selected by

load sharing

Not valid NRI for theprevious PLMN

PLMN and CN selected by LoadSharing

OLD LAI with EquivalentPLMN routing

Other than LU, Attach

and RAU no OLD LAIchecking

Valid for previous PLMNor valid for PLMN, whichis defined as equivalentto the previous PLMN

CN selected by NRI if CN isdown, then another CN from the


NULL NRI of theprevious PLMN or PLMN

which is defined asequivalent to the

previous PLMN

PLMN selected by NRI and CNfrom pool will be selected by

load sharing

Not valid NRI for theprevious PLMN or PLMN

, which is defined asequivalent to theprevious PLMN

PLMN and CN selected by LoadSharing



Activation control (license key, PRFILE) RAN3007 CN Selection Method for IU Request Routingwhen UE Roams from Different PLMN



4 Activation control (license key, PRFILE)

This workaround is controlled with PRFILE parameters:

007:269 RN40_MAINT_01

007:270 RN40_MAINT_02 And SharedPLMNs in IUO object

By default, the workaround is disabled (default value == 0H)



Document title Checking the state of feature activation



15/21

5 Checking the state of feature activation

5.1 IPA-RNC

Status of the workaround activation can be checked with MML

ZWOI:7,269;

ZWOI:7,270;

5.2 mcRNC and FD-RNC

Status of the workaround activation can be checked with SCLI

# fsclish> show app-parameter configuration-parameter class 7number 269

> show app-parameter configuration-parameter class 7number 270



Activation instructions RAN3007 CN Selection Method for IU Request Routingwhen UE Roams from Different PLMN



6 Activation instructions

6.1 IPA-RNC

Activation and deactivation is made by setting the correct value to parameter7,269 and 7,270 by command ZWOC:

ZWOC:7,269,<new value>;

ZWOC:7,270,<new value>;

The new value shall be a combination of the old value and wanted activation, whichare presented in each own section. If the old value first bit is 0, then it can be skippedand the new value is the same as the wanted activation.

Old value can be checked by command:

ZWOI:7,269;

ZWOI:7,270;

OLD value = yyyy yyyy yyyy yyy1ACTIVATION = xxxx xxxx xxxx x101NEW value = yyyy yyyy yyyy y101

6.1.1 Basic method

Load sharing used method is used to select the CN.

Non MOCN configurationLoad sharing method is the default method that is used with non MOCNconfiguration. See parameter 7,269: Load sharing method is used by thefollowing values:

xxxx xxxx xxxx xxx0

xxxx xxxx xxxx x0x1

xxxx xxxx xxxx x111



Document title Activation instructions



17/21

MOCN configuration

Load sharing method (Basic Method) can be activated by setting the followingvalue to 7,269:

xxxx xxxx xxxx xx11

6.1.2 NRI routing for registration

Non MOCN configuration

This method is not available for non MOCN configuration.

MOCN configuration

NRI routing for registration is by default in use with MOCN configuration. Seeparameter 7,269:

xxxx xxxx xxxx xxx0xxxx xxxx xxxx x001

6.1.3 The old LAI routing for registration and NRI routing for anotherprocedures

The old LAI routing for registration means that NRI routing will be used in casethat NRI matches with the old LAI PLMN. When the old LAI routing forregistration is activated, then also the NRI routing is active for otherprocedures (for example, MO/MT calls).

Both non MOCN and MOCN configurationsThe old LAI routing for registration can be activated by setting the followingvalue to 7,269:

xxxx xxxx xxxx x101

6.1.3.1 Allowed NRI routing from additional PLMNs with OLD LAI routing forregistration

This is an additional functionality for the old LAI routing for registration. Theoperator can use this when the operator has several PLMNs in use RadioNetwork and all those networks are managed by the same core networkelements (for example, 2G and 3G networks).

1. Defining equivalent PLMNs for each operator

- When the operator has several PLMNs, which need to be handledlike network’s own PLMN, then those extra PLMNs need to bedefined to the operators’ IUO object as a shared PLMN.

When the operator also wants to use an equivalent PLMNfunctionality, then an extra activation will be made by 7:270:

Check old value:






ZWOI:7,270;

OLD VALUE = yyyy yyyy yyyX yyyX ACTIVATION = xxxx xxxx xxx1 xxx1

NEW VALUE = yyyy yyyy yyy1 yyy1 Activate:

ZWOC:7,270,<NEW VALUE>

- After the parameter value has been changed, the workaround isactivated within 1 minute


The activation and deactivation will be made by setting the correct value toparameter 7,269 and 7,270 by SCLI

# fsclish

> set app-parameter configuration-parameter class 7number 269 value <new value>

> set app-parameter configuration-parameter class 7number 270 value <new value>

The new value shall be a combination of the old value and the wantedactivation, which are presented in their own sections. If the old value’s first bit

is 0, then it can be skipped and the new value is the same as the wantedactivation.

The old value can be checked by SCLI command

# fsclish



OLD value = yyyy yyyy yyyy yyy1 ACTIVATION = xxxx xxxx xxxx x101NEW value = yyyy yyyy yyyy y101

6.2.1 Basic method

Load sharing used method is used to select CN.




Document title Activation instructions



19/21

Load sharing is the default method that is used with non MOCN configuration.See parameter 7,269: Load sharing method in use by following values:

xxxx xxxx xxxx xxx0

xxxx xxxx xxxx x0x1

xxxx xxxx xxxx x111

MOCN configuration

Load sharing method (Basic method) can be activated by setting the following

value to 7,269:

xxxx xxxx xxxx xx11

6.2.2 NRI routing for registration


This method is not available for non MOCN configuration.

MOCN configuration

NRI routing for registration is in use by default with MOCN configuration. See

parameter 7,269:

xxxx xxxx xxxx xxx0xxxx xxxx xxxx x001

6.2.3 Old LAI routing for registration and NRI routing for otherprocedures

Old LAI routing for registration means that the NRI routing will be used if NRImatches with the old LAI PLMN. When the old LAI routing for registration isactivated, then also the NRI routing is active for other procedures (forexample, MO/MT calls).

Both non MOCN and MOCN configuration

Old LAI routing for registration can be activated by setting the following valueto 7,269:

xxxx xxxx xxxx x101

6.2.3.1 Allowed NRI routing from additional PLMNs with OLD LAI routing forregistration

This is an additional functionality for the old LAI routing for registration. Theoperator can use this when the operator has several PLMNs in use RadioNetwork and all those networks are managed by the same core networkelements (for example, 2G and 3G networks).

1. Defining equivalent PLMNs for each operator






- When the operator has several PLMNs, which need to be handledlike the network’s own PLMN, then those extra PLMNs need to be

defined to the operator’s IUO object as a shared PLMN.

When the operator also wants to use an equivalent PLMNfunctionality, then the extra activation will be made by 7:270:

Check old value:

# fsclish

> show app-parameter configuration-parameterclass 7 number 270

OLD VALUE = yyyy yyyy yyyX yyyX ACTIVATION=xxxx xxxx xxx1 xxx1NEW VALUE =yyyy yyyy yyy1 yyy1

Activate:

# fsclish

> set app-parameter configuration-parameter class7 number 270 value <new value>

- After parameter the value has been changed, the workaround isactivated within 1 minute.



Document title Deactivation instructions



21/21

7 Deactivation instructions

7.1 IPA-RNC

To deactivate the workaround, PRFILE parameter value should be changed tothe original value with MML:

ZWOC:7,269,<OLD VALUE>;

ZWOC:7,270,<OLD VALUE>;

After PRFILE change, the workaround is deactivated within 1 minute.


To deactivate the workaround, PRFILE parameter value should be changed tothe original value.

# fsclish

> set app-parameter configuration-parameter class 7number 269 value <old value>

> set app-parameter configuration-parameter class 7number 270 value <old value>

After PRFILE change, the workaround is deactivated within 1 minute.

ran3007 cn selection method for iu request routing when ue roams from different plmn

Documents

use of nokia solutions

trademark of nokia solutions

copyright nokia solutions

necessary nokia solutions

networks customers

document id

software products

iu request routing