Iu Flex(RAN15.0_02)

WCDMA RAN

Iu Flex Feature ParameterDescription

Issue 02Date 2013-09-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2013. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied. Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.comEmail: [email protected]

Issue 02 (2013-09-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

Contents

1 Introduction....................................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................12 Overview.........................................................................................................................................32.1 Background.....................................................................................................................................................................42.2 Pool Area........................................................................................................................................................................42.3 NRI.................................................................................................................................................................................62.4 NullNRI..........................................................................................................................................................................62.5 Non-broadcast LAI/RAI.................................................................................................................................................63 NAS Node Selection Function....................................................................................................73.1 Overview........................................................................................................................................................................83.2 UE Indicating Routing....................................................................................................................................................83.3 RNC Selecting CN Node................................................................................................................................................93.4 IMSI Paging..................................................................................................................................................................104 Iu-Flex Service Process...............................................................................................................115 Load Balancing.............................................................................................................................136 Flow Control.................................................................................................................................157 Load Re-Distribution..................................................................................................................167.1 Load Re-distribution based on NullNRI.......................................................................................................................177.2 Load Re-distribution based on Blocking CN Node......................................................................................................188 Feature Deployment....................................................................................................................198.1 Configuring Iu Flex......................................................................................................................................................198.1.1 Prerequisites...............................................................................................................................................................198.1.2 Procedure...................................................................................................................................................................198.1.3 Example.....................................................................................................................................................................258.2 Configuring Iu Flex Load Distribution Management...................................................................................................268.2.1 Prerequisites...............................................................................................................................................................268.2.2 Procedure...................................................................................................................................................................268.2.3 Example.....................................................................................................................................................................35

WCDMA RANIu Flex Feature Parameter Description Contents


ii

9 Parameters.....................................................................................................................................3710 Counters......................................................................................................................................9011 Glossary.......................................................................................................................................9212 Reference Documents...............................................................................................................93

WCDMA RANIu Flex Feature Parameter Description Contents


iii

1 Introduction1.1 Scope

This document describes WRFD-021302 Iu Flex, including its technical principles, relatedfeatures, network impact, and engineering guidelines.

1.2 Intended AudienceThis document is intended for personnel who:l Need to understand the features described hereinl Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes, which are defined as follows:l Feature change

Changes in features of a specific product versionl Editorial change

Changes in wording or addition of information that was not described in the earlier version

02 (2013-09-30)This issue includes the following changes.

WCDMA RANIu Flex Feature Parameter Description 1 Introduction


1

Change Type Change Description Parameter ChangeFeature change Added flow control in

scenarios where Iu Flex isenabled. For details, seechapter 6 Flow Control.

AddedRESERVED_SWITCH_3_BIT32 to the RsvSwitch3(BSC6900,BSC6910)parameter in the SETUALGORSVPARAcommand.

Editorial change None None

01 (2013-04-28)This issue does not include any changes.

Draft A (2013-01-30)Compared with issue 01 (2012-07-20) of RAN14.0, Draft A (2013-01-30) of RAN15.0 includesthe following changes.

Change Type Change Description Parameter ChangeFeature change None The reserved parameter

RsvdPara1 is replaced withthe PROCESSSWITCH(BSC6900,BSC6910)parameter.

Editorial change Added the descriptions ofUE'S coding mode priorityselection. For details, seesection 3.2 UE IndicatingRouting.

None

Added the descriptions of IuFlex service process. Fordetails, see 4 Iu-Flex ServiceProcess.

WCDMA RANIu Flex Feature Parameter Description 1 Introduction


2

2 OverviewIu Flex is an extended function of RAN. The 3GPP TS 23.236 defines Iu Flex as follows: "Intra-domain Connection of Radio Access Network (RAN) Nodes to Multiple Core Network Nodes."The Iu Flex (WRFD-021302 Iu Flex) brings in the concept of "pool area". A pool area containsone or more MSC/SGSN service areas. In a pool area, the UE roams freely without changingthe serving CN node. The Iu Flex enables a RAN node to route information to different CNnodes, implementing the load balance among MSCs or SGSNs.

WCDMA RANIu Flex Feature Parameter Description 2 Overview


3

2.1 BackgroundIn the versions earlier than 3GPP R5, one RAN node is controlled by only one CN node. Sucha network structure, however, has some limitations. From the perspective of 3G trafficdistribution, the traffic volume of urban areas in the daytime constitutes a major proportion ofthe total, but the traffic volume of urban areas at night decreases to a low level. The situationmay be reverse in the suburban area. Therefore, the load of CN nodes for urban and suburbanarea is imbalanced.Therefore, Iu Flex is introduced in 3GPP R5. With Iu Flex, one RAN node can be connected toseveral CN nodes and these CN nodes can form a pool area. The UEs in the same pool area donot need to change the serving CN node.The introduction of Iu Flex avoids the imbalance of resource usage among different CN nodesin different traffic peak hours and achieves the load balancing among several CN nodes in theWCDMA network.In a traditional network structure, a RAN node only needs to know whether the destination isthe CS domain or the PS domain before sending information. It does not need to discriminatespecific CN nodes because a RAN node is connected to only one CN node.With Iu Flex, however, one RNC can connect to several MSCs/SGSNs physically, where CSnodes and PS nodes form different pool areas. Therefore, a RAN node can send information todifferent CN nodes in the CS or PS domain and achieve load balancing among several CN nodesin the pool area.The pool area is described as follows:l A pool area is a collection of one or more MSC or SGSN serving areas. One or more CN

nodes can provide services in parallel and these CN nodes share the traffic in the pool area.l Pool areas may overlap. RAN nodes belong to all the overlapping pool areas.l The CS pool area is independent of the PS pool area.l If a UE roams in a certain pool area, it does not need to change the serving CN node.The Iu Flex feature enhances network reliability, achieves load balancing, and reduces UEroaming signaling.

2.2 Pool AreaThis section describes the pool area, in terms of what it is, and how it is served and configured.A RAN node service area contains all the cells controlled by the RAN node. A pool area is acollection of one or more RAN node service areas. It is served, in parallel, by one or more CNnodes that share the traffic of this area.A UE is served by one dedicated CN node in a pool area as long as the UE is under the radiocoverage of the pool area. Pool areas can overlap each other. If several overlapping pool areascover a same RAN node service area, the RAN node service area belongs to these pool areas.The pool areas of the CS domain and those of the PS domain are configured independently withthe granularity of RAN node service areas.



4

In a pool area, the UE roams freely without changing the serving CN node. The RAN nodeservice area can belong to the same pool area or several pool areas.Figure 2-1 shows an example of the pool area configurations.

Figure 2-1 Pool area configuration example

Figure 2-1 shows the following four pool areas:l CS pool area 1: includes RAN node areas 1, 2, 5, 6, and MSC servers 1, 2, and 3, which

provide service for the RAN node areas.l CS pool area 2: includes RAN node areas 2, 3, 6, 7, and MSC servers 4, 5, and 6, which

provide service for the RAN node areas.l PS pool area 1: includes RAN node areas 1 and 5, and SGSNs 1 and 2, which provide

service for the RAN node areas.l PS pool area 2: includes RAN node areas 2, 3, 6, 7, and SGSN 3, 4, and 5, which provide

service for the RAN node areas.NOTE

As shown in Figure 2-1, the pool areas without the Iu Flex, such as RAN node areas 4 and 8, may coexistwith the pool areas with the Iu Flex.

The pool areas of the CS and PS domains can be configured as identical pool areas, such as CSpool area 2 and PS pool area 2, or different pool areas, such as CS pool area 1 and PS pool area1.Each pool area has its unique configuration of the CN node capability or number.



5

2.3 NRIThe Network Resource Identifier (NRI) identifies the CN node that serves a pool area. The NRIhas a flexible length from 0 bit to 10 bits. 0 bit means no Iu flex. The NRI lengths are the samefor all the CN nodes in one pool area.In areas where pool areas overlap, the NRI identifies the CN node that serves these overlappingpool areas. For overlapping pool areas, the NRI lengths must be configured the same for all thenodes serving specific pool areas.The CN nodes in the CS domain and those in the PS domain are addressed separately, so theNRIs of the CS and PS domains are independent of each other.The NRI is a part of the Temporary Mobile Station Identity (TMSI) for the CS domain, or ofthe Packet TMSI (P-TMSI) for the PS domain. The TMSI or P-TMSI is assigned to the UE bythe serving CN node. The TMSI or P-TMSI allocation mechanism of the CN node generatesTMSIs or P-TMSIs with NRIs determined by certain bits.The association between the NRIs and the CN nodes in the CN pool area is configured on theRAN nodes.In the WCDMA system, the UE provides an intra domain NAS node selector (IDNNS) in theaccess stratum (AS) part of the Initial Direct Transfer message to the RAN node. The IDNNScontains a routing parameter with a fixed length of 10 bits. This routing parameter contains theNRI information. In addition, the IDNNS contains the identity that indicates the source of therouting parameters. The identity can be TMSI/P-TMSI, international mobile subscriber identity(IMSI), international mobile equipment identity (IMEI), and so on. The RAN node masks thesignificant bits out of the routing parameter part of the IDNNS to determine the NRI that is usedto identify the relevant CN node. The most significant bit of the NRI corresponds to the mostsignificant bit of the routing parameter in the IDNNS. A routing parameter containing the identityof IMSI is in range of 0 to 999 (calculated by (IMSI div 10) mod 1000) and is called IMSIROUTEin this document. The association between IMSIROUTE and the CN nodes in the CN pool areais configured on the RNC.

2.4 NullNRINullNRI is a special value of the NRI, which indicates that the CN node identified by the NRIis to be offloaded. On receiving a message carrying NullNRI, the RNC starts the IDNNS functionto select an appropriate CN node. NullNRI can be unique in a Public Land Mobile Network(PLMN) or set separately in the CS domain and PS domain.

2.5 Non-broadcast LAI/RAINon-broadcast Location Area Identity (LAI) or Routing Area Identity (RAI) is different fromthe normal LAI/RAI in the network. It is used in the scenario that the CN node is to be offloaded.The UE will immediately initiate Location Update or Route Area Update after receiving theNon-broadcast LAI/RAI.



6

3 NAS Node Selection FunctionNAS Node Selection Function (NNSF) is used to select an appropriate CN Node for a UE.

WCDMA RANIu Flex Feature Parameter Description 3 NAS Node Selection Function


7

3.1 OverviewThe NNSF performs the selection of a CN node and the processing of the IMSI Paging Messagein both the CS and PS domain.In the RAN node, the NNSF selects a specific CN node (MSC server or SGSN) and routes theinitial NAS signaling message to the selected CN node.If a CN node address configured for the NRI can be derived from the initial NAS signalingmessage, the NNSF routes the message to the CN node. If no CN node address is configured forthe derived NRI or no NRI can be derived (for example, the UE indicates an identity that containsno NRI), or the configured CN node cannot be reached, the NNSF selects an available CN nodebased on load balancing and routes the message to the selected CN node.The procedure for NNSF is as follows:1. CN Node allocates route information to the UE.

If CN supports the Iu Flex, the CN indicate the NRI in the TMSI or P-TMSI when allocatingthe TMSI or P-TMSI to the UE.

2. UE indicates the route information and sends it to the RNC in the Initial Direct Transfermessage.

3. RNC selects the CN Node based on the routing information in the Initial Direct Transfermessage.

3.2 UE Indicating RoutingUE indicates the routing information to help RNC select an appropriate CN node. The routinginformation is contained in the IDNNS IE in the Initial Direct Transfer message from the UE tothe RNC.IDNNS IE consists of two parts of routing information:l The first part indicates the ID type (TMSI/P-TMSI, IMSI, IMEI) used for calculating the

routing parameter.l The second part indicates the routing parameter with a fixed length of 10 bits.The routing parameter is encoded by UE according to the following priorities:1. The coding is performed based on the TMSI/P-TMSI.Tthe routing parameter is derived

from TMSI or P-TMSI. It is a 10-bit field from the fourteenth bit to the twenty-third bit inTMSI or P-TMSI. The most significant bit of the NRI shall correspond with the mostsignificant bit of the routing parameter.

2. If the TMSI/P-TMSI information is unavailable, but the MS has the USIM/SIM card, thecoding is performed based on the IMSI. The routing parameter is derived from IMSI andcalculated as (IMSI div 10) mod 1000, where "div" means divided by and "mod" meansmodulus.

3. If the MS is not inserted with the USIM/SIM card, the coding is performed based on theIMEI. The routing parameter is derived from IMEI and calculated as (IMEI div 10) mod1000.



8

3.3 RNC Selecting CN NodeAfter the RNC received the Initial Direct Transfer message from the UE, the RNC selects a CNnode based on the IDNNS IE in the message.

Selecting CN Node Based on TMSI/P-TMSIIf IDNNS indicates that the route information is from the TMSI or P-TMSI, the RNC selects theroute based on the NRI. The RNC derives the NRI from the routing parameter and then selectsa CN node based on the mapping between the NRI(BSC6900,BSC6910) and the CN nodes. Themapping is configured by running the ADD UNRIGLBCNIDMAP command.The mapping must be configured on both the CN and RNC sides. The NRI configured on theRNC side must be negotiated with the CN so that it is the same as the NRI configured on theCN side.In following cases, the RNC selects a CN node based on the load balancing.l The CN node corresponding to an NRI is inhibited or cannot be reached.l The value of the NRI is NullNRI.l The NRI is not configured at the RNC.Calling and called parties follow the same way of selecting the CN node based on TMSI/P-TMSI.

Selecting CN Node Based on IMSIIf IDNNS indicates that the route information is from the IMSI, the RNC selects the route basedon the mapping between the IMSI and the CN nodes.l If the Initial Direct Transfer message indicates that this message is initiated by a mobile

originated call, If the IMSI route of a UE is within the configured IMSI range of a CN node, the RNC

routes the UE to the CN node.The mapping is configured on RNC by running the ADD UIMSIIDNNSCNIDMAPcommand. If the IMSI route of a UE is not configured, the RNC selects a CN node based on the

load balancing.l If the Initial Direct Transfer message indicates that this message is initiated by a mobile

terminated call (paging response), the RNC routes the UE based on the mapping betweenIMSI and global CN ID received from CN. If fails, the terminated call is processed as anoriginated call.

For details, see 3.4 IMSI Paging.

Selecting CN Node Based on IMEIIf IDNNS indicates that the route information is from the IMEI, the RNC selects the CN nodebased on the load balancing.Calling and called parties follow the same way of selecting the CN node based on IMEI.



9

3.4 IMSI PagingProcessing of the IMSI Paging Message (CS Domain)

To increase the success rate of routing the paging response message to the CN node that issuesthe paging request, the RNC capable of the Iu Flex needs to process the IMSI paging messageas follows:l In R5 protocols or later releases, the Global-CN-ID is contained in the RANAP PAGING

message. If the RNC enables the Iu Flex and the paging message contains only the IMSIrather than the TMSI, the paging message must contain the Global-CN-ID.

l The NNSF in the RNC temporarily stores the map between the IMSI and the Global-CN-ID upon reception of the paging message. When the NNSF receives the Initial DirectTransfer message (a paging response with an IMSI), it directly forwards the paging responseto the CN node identified by this Global-CN-ID.

If a CS paging message with mobile identity type IMSI is received over the Gs interface fromthe MSC, the SGSN has to contain the MSC/VLR-ID in the paging message or paging-requestmessage to the RNC.

Processing of the IMSI Paging Message (PS Domain)Based on 3GPP TS 23.236 (For details, see Reference Documents), a UE returns an AttachRequest message containing the IMSI parameter as a response to the PS IMSI paging. Becauseany SGSN can process the Attach Request message, the NNSF for the RNC does not need tostore the SGSN ID when it receives the paging request. The NNSF ensures that the RAN nodeselects an available SGSN (for example, based on load balancing) when it receives an AttachRequest containing the IMSI parameter.



10

4 Iu-Flex Service ProcessThe Iu Flex service process is as follows (taking the PS domain as an example).

Figure 4-1 Iu Flex service process

1. The MS accesses the network through the RAN1, and provides the IDNNS to the RAN1.2. The RAN1 obtains the corresponding SGSN based on the IDNNS, and then connects the

MS to the SGSN1.3. The SGSN1 sends its NRI to the MS when the MS access is completed.4. The MS moves to the area served by the RAN2.

WCDMA RANIu Flex Feature Parameter Description 4 Iu-Flex Service Process


11

5. When the MS requests to access the network though the RAN2, the MS provides the IDNNSto the RAN2, containing the SGSN1 NRI.

6. The RAN2 finds the SGSN1 that serves the MS originally, and then connects the MS tothe SGSN1 that serves the MS at the first time of network access.

When a UE is moving within a Pool area, the UE can be continuously served by a certain CNnode. Therefore, the location update process between the SGSNs is avoided, and the networkload is reduced.

WCDMA RANIu Flex Feature Parameter Description 4 Iu-Flex Service Process


12

5 Load BalancingLoad Balancing (WRFD-021306 Iu Flex Load Distribution Management) describes how theNNSF balances the load between the available CN nodes.The RNC selects a CN node from the available CN nodes based on the load balancing principle.Load balancing occurs in one of the following situations:l There is no CN node configured for the NRI or IMSIROUTE indicated by the UE.l The CN node corresponding to an NRI or IMSIROUTE cannot be reached.l The CN node corresponding to an NRI or IMSIROUTE is inhibited.l No NRI or IMSIROUTE can be derived.l The value of the NRI is NullNRI.Based on the load balancing principle, the RNC records the capability of each CN node whichis configured to the NORMAL state and is not in overloaded, and then selects a CN node basedon randomization function for the UE.Assume that the RNC is connected to three MSCs in NORMAL state (identified as MSC A, B,and C) and their available capabilities are 10, 20, and 10, respectively. Among the UEs accessingin load balancing condition, 25% of UEs are routed to MSC A, 50% of UEs are routed to MSCB, and 25% of UEs are routed to MSC C, according to the rules of load balancing. Other UEsare routed to the specific CN nodes identified by the NRI.

NOTE

If a CN node whose available capacity is 0 is identified by a valid NRI and the route parameters of a UEinclude the NRI, the UE will still be routed to the CN node.

The capability of the CN node is acquired in the following two ways:l Static capability

The static capability of the CN node is specified by the AvailCap(BSC6900,BSC6910) ofthe ADD UCNNODE command in the RNC.

l Dynamic capabilityThe dynamic capability reflects the real-time state of the CN node capability.If the parameters CsInfoUpdFlag(BSC6900,BSC6910) or PsInfoUpdFlag(BSC6900,BSC6910) in the RNC is set to ON, the CN informs the RNC of the dynamiccapability and state through the private IEs of the INFORMATION TRANSFER INDICATION

WCDMA RANIu Flex Feature Parameter Description 5 Load Balancing


13

message. Therefore, the data between the CN and the RNC is synchronized to realize loadbalancing.If the RNC does not receive the message about updating the dynamic capability before the CSInformation Update Protection Timer or PS Information Update Protection Timer expires, thestatic capability is preferred.

NOTE

The Iu interface standard messages INFORMATION TRANSFER INDICATION and INFORMATIONTRANSFER CONFIRM contain the extended private IEs. The CN node has to support the extension ofthe private IEs to inform the RNC of the dynamic capability.

WCDMA RANIu Flex Feature Parameter Description 5 Load Balancing


14

6 Flow ControlThe RNC considers a CN code to be congested when either of the following occurs:l The RNC detects Signaling Connection Control Part (SCCP) congestion.l The RNC receives an overload message from the CN node.In non-Iu Flex networking, if a CN node is congested, the RNC reduces the load on the CN node.For details, see Flow Control Feature Parameter Description.In Iu Flex networking, when receiving an Initial Direct Transfer message from a UE, the RNCforwards the message to the correct CN node based on the routing information carried in themessage. If the CN node is congested, the RNC determines whether to send the message to theCN code based on the severity of the congestion and randomization function. If the RNCdetermines not to send the message to the CN code, the RNC processes the message based onthe setting of RESERVED_SWITCH_3_BIT32 in the RsvSwitch3(BSC6900,BSC6910)parameter in the RNC command SET UALGORSVPARA.l If RESERVED_SWITCH_3_BIT32 is set to 1, the RNC discards the Initial Direct

Transfer message.l If RESERVED_SWITCH_3_BIT32 is set to 0 and if the RNC considers the CN node to

be congested after receiving an overload message from the CN node, the RNC sends theInitial Direct Transfer message to a normal CN node. If the RNC considers the CN nodeto be congested after detecting SCCP congestion, the RNC performs the followingprocessing: If RESERVED_SWITCH_3_BIT16 in the RsvSwitch3(BSC6900,BSC6910)

parameter in the SET UALGORSVPARA command is set to 1, the RNC sends themessage to a normal CN node. If RESERVED_SWITCH_3_BIT16 in the RsvSwitch3(BSC6900,BSC6910)

parameter in the SET UALGORSVPARA command is set to 0, the RNC sends themessage to another CN node, regardless of whether the CN node is congested or not.

NOTE

The RNC selects the CN node for the UE based on the proportion of the available capability of each CNnode in the NORMAL state.

WCDMA RANIu Flex Feature Parameter Description 6 Flow Control


15

7 Load Re-DistributionThere are situations where a network operator needs to remove load from one CN node (forexample, to perform scheduled maintenance, upgrade or load re-distribution to avoid overload),with minimal impact on end users, or additional load on other entities, or both.Load Re-Distribution helps to re-distribute UEs to other CN nodes. There are two ways toimplement load re-distribution:l Load re-distribution based on NullNRIl Load re-distribution based on blocking CN node

WCDMA RANIu Flex Feature Parameter Description 7 Load Re-Distribution


16

7.1 Load Re-distribution based on NullNRITwo IDs are added to implement the load re-distribution: NullNRI and Non-broadcast LAI/RAI.The re-distribution of UE is initiated by the CN node that is to be offloaded. The procedure forload re-distribution is described as follows:1. In the first phase (a couple of Periodic LU or RAU periods long), the UEs doing Location

Update (LU), Routing Area Update (RAU), or Attach are moved to the other CN nodes inthe pool.When the CN node receives the LU, RAU, or Attach request, it returns a new TMSI or P-TMSI with a NullNRI, and a Non-broadcast LAI/RAI in the accept message.l In the CS domain, the non-broadcast LAI will cause the UE to immediately send a new

LU request, which the RNC node will perform load balancing to route the UE to a newMSC server due to the NullNRI.

l In the PS domain, the non-broadcast RAI will cause the UE to send a new RAU request.The periodic routing area update timer is set to a sufficiently low value in the acceptmessage to reduce the time to trigger the RAU. Shortly after that, the UE sends a newRAU request, which the RNC node will perform load balancing to route the UE to anew SGSN due to the NullNRI.

2. In the second phase (PS domain specific), the SGSN requests all UEs trying to set up PDPContexts to detach and reattach. When they reattach, the SGSN moves them as describedin the first phase.

3. The third phase includes scanning the remaining UEs and initiating the movement of themto other CN nodes.

l In the PS domain, the UEs are requested to detach and reattach, which will cause them tobe moved.

l In the CS domain, a new TMSI is allocated to the UEs performing the TMSI re-allocationprocedure (with NullNRI and non-broadcast LAI) so that an LU is triggered, which willcause them to be moved.

The RNC selects CN node based on the CN state for load re-distribution. The CN state isnegotiated between CN and RAN. The state of CN should be specified in the RNC by theparameterCNLoadStatus(BSC6900,BSC6910). The state for a CN node can be NORMAL,OFFLOAD, INHIBITED or BLOCKED.The principle for selecting a CN node for load re-distribution is as follows:l If the CN supports NullNRI:

If the NRI is NullNRI, the RNC can select the CN nodes only in the Normal state. If the NRI is not NullNRI, the RNC can select the CN nodes only in the Normal or

OFFLOAD state.l The RNC cannot select a CN node in INHIBITED state for a UE.l The UEs being moved from one CN node are prevented from registering in the same CN

node again or in a CN node that is overloaded.l The RNC ensures that the movements do not overload the network and the RNC can handle

the situations where several CN nodes are overloaded simultaneously.



17

For multi-operator core network (MOCN) network sharing, re-distribution is always done withinthe same CN operator. This is ensured by each CN operator using its own unique NullNRI. TheRNC is pre-configured with the NullNRIs for different CN operators, and it uses the NullNRIto select a CN node within the same CN operator.

7.2 Load Re-distribution based on Blocking CN NodeIf the CN does not support NullNRI, the RNC can block the CN node to help redistribute theload of the CN node to other CN nodes.BLOCKED state is a sub-state of NORMAL state. The BLOCKED state can be set in the RNCby run the following command.MOD UCNNODE: CnOpIndex=1, CNId=2, CNDomainId=CS_DOMAIN,CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS,Switch3GPP25415CR0125=OFF,PROCESSSWITCH=IUFLEX_NOT_SEL_BLOCK_SWITCH-1;When a CN node is in the BLOCKED state, the UE in the CN node is redistributed by the RNCto other CN nodes.A UE can still access a CN node in the BLOCKED state in the following two situations:l When the CN is in BLOCKED state and other CNs are in NORMAL state, the UEs that

are routed to this CN node cannot access the CN and will be routed to other CNs. However,the UE can still access the CN node if the UE is responding to the paging message fromthis CN node.

l When the CN is in BLOCKED state and other CNs are in INHIBITED state or inOFFLOAD state or are disconnected or are overloaded, the UEs can still access the CNnode.



18

8 Feature Deployment8.1 Configuring Iu Flex

This section describes how to activate, verify, and deactivate the optional feature WRFD-021302Iu Flex.

8.1.1 Prerequisitesl Dependencies on Hardware

This feature does not depend on the hardware.l Dependencies on Other Features

This feature does not depend on other features.l License

The license " IU FLEX" on the RNC side has been activated. For details about the licenseitems and how to activate the license, see License Management Feature ParameterDescription.

l Others The MSC and the serving GPRS support node (SGSN) support this feature.

8.1.2 ProcedureActivation (Using MML Commands)

1. Run the RNC MML command SET UOPERATORCFGPAR. In this step, set FeatureSupporting Mode of CS Domain to SUPP_IUFLEX, set Feature Supporting Mode of PSDomain to SUPP_IUFLEX, and set Length of CS NRI in bits and Length of PS NRI inbits to appropriate values.

2. Configure the Iu interface transmission between RNC and multiple core networks (CNs)by referring to "Configuring the Interfaces" in RNC UMTS Initial Configuration Guide.

3. Run the RNC MML command ADD UCNNODE to add multiple CN nodes for an operatoraccording to the network plan.

WCDMA RANIu Flex Feature Parameter Description 8 Feature Deployment


19

NOTE

The CNId of the same PLMN cannot be the same,even the different CN domain. The setting ofCNId must be consistent between the RNC and CN. If CNId on the CN is set to 5, CNId on theRNC must also be set to 5.

4. Run the RNC MML command ADD UNRIGLBCNIDMAP. In this step, set Cn OperatorIndex, CN node ID, and Network resource identity to configure the mappingrelationships between NRI and CN nodes.

5. Optional: Run the RNC MML command ADD UIMSIIDNNSCNIDMAP to configurethe mapping relationships between international mobile subscriber identity (IMSI) rangesand CN nodes.

After configuring the mapping relationships, the RNC routes the UE whose IMSI is within theIMSI range to the specified CN. To ensure load balance among CN nodes, the IMSI rangemapped to each CN node must match the capacity of the CN node.

Activation (Using the CME)NOTE

When configuring the feature on the CME, you must configure a single configuration first, and then performbatch modifications if required.You must perform a single configuration for a parameter before batch modifications of the parameter. Youare advised to perform batch modifications before logging out of the parameter setting interface.

Step 1 Configure a single object on the CME.Set parameters on the CME according to the operation sequence in Table 8-1. For instructionson how to perform the CME single configuration, see CME Single Configuration OperationGuide.

Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)----End

To modify objects in batches, click on the CME to start the batch modification wizard. Forinstructions on how to perform a batch modification through the CME batch modification center,press F1 on the wizard interface to obtain online help.

Table 8-1 Parameters to be set on the CMESN MO NE Parameter Name Parameter ID Configurable

in CME BatchModificationCenter

1 UOPERATORCFGPARA

RNC Feature SupportingMode of CS DomainSet this parameter toSUPP_IUFLEX

CsNriCfgMode(BSC6900,BSC6910)

No



20

SN MO NE Parameter Name Parameter ID Configurablein CME BatchModificationCenter

Feature SupportingMode of PS DomainSet this parameter toSUPP_IUFLEX

PsNriCfgMode(BSC6900,BSC6910)

Length of CS NRI inbits

CSNRILength(BSC6900,BSC6910)

Length of PS NRI inbits

PSNRILength(BSC6900,BSC6910)

2 UCNNODE

RNC Cn Operator Index CnOpIndex(BSC6900,BSC6910)

No

CN node ID CNId(BSC6900,BSC6910)

CN domain ID CNDomainId(BSC6900,BSC6910)

DSP index Dpx(BSC6900,BSC6910)

CN protocol version CNProtclVer(BSC6900,BSC6910)

CNLoadStatus CNLoadStatus(BSC6900,BSC6910)

AvailCap AvailCap(BSC6900,BSC6910)

Iu transfers bearertype

TnlBearerType(BSC6900,BSC6910)

Switch3GPP25415CR0125

Switch3GPP25415CR0125(BSC6900,BSC6910)



21

SN MO NE Parameter Name Parameter ID Configurablein CME BatchModificationCenter

3 UNRIGLBCNIDMAP

RNC Cn Operator Index CnOpIndex(BSC6900,BSC6910)

No


Network resourceidentity

NRI(BSC6900,BSC6910)

4 UIMSIIDNNSCNIDMAP

RNC Minimum of IMSIroute parameter inIDNNS

ImsiRtMin(BSC6900,BSC6910)

No

Maximum of IMSIroute parameter inIDNNS

ImsiRtMax(BSC6900,BSC6910)

Cn Operator Index CnOpIndex(BSC6900,BSC6910)


Verification Procedure1. Enable the UE to access a cell and register in the cell.2. According to the mapping relationships between IMSI ranges and CN nodes and the load

balance algorithm, the RNC selects a CN node for the UE, and the UE registers successfully.3. Then, if the UE initiates a service, the RNC routes the UE to the corresponding CN node

according to the mapping relationships between NRI and CN nodes.

Deactivation (Using MML Commands)1. Run the RNC MML command RMV UNRIGLBCNIDMAP to remove NRI and all of CN

Node Mapping Information.2. Run the RNC MML command RMV UCNNODE to remove CN Node (Keep one CN

Node).3. (Optional) Run the RNC MML command RMV UIMSIIDNNSCNIDMAP to remove the

mapping relationships between IMSIROUTE and CN nodes.



22

4. Run the RNC MML command SET UOPERATORCFGPARA to deactivate this feature.In this step, set Feature Supporting Mode of CS Domain to SUPP_NONE, set FeatureSupporting Mode of PS Domain to SUPP_NONE.

Deactivation (Using the CME)NOTE

When configuring the feature on the CME, you must configure a single configuration first, and then performbatch modifications if required.You must perform a single configuration for a parameter before batch modifications of the parameter. Youare advised to perform batch modifications before logging out of the parameter setting interface.

Step 1 Configure a single object on the CME.Set parameters on the CME according to the operation sequence in Table 8-2. For instructionson how to perform the CME single configuration, see CME Single Configuration OperationGuide.

Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)----End

To modify objects in batches, click on the CME to start the batch modification wizard. Forinstructions on how to perform a batch modification through the CME batch modification center,press F1 on the wizard interface to obtain online help.

Table 8-2 Parameters to be set on the CMESN MO SN MO NE Paramete

r NameParameter IDConfigurable inCMEBatchModificationCenter

1 UNRIGLBCNIDMAPNOTE

Delete the MOconfiguration.

RNC


No



23

SN MO SN MO NE Parameter NameParameter IDConfigurable inCMEBatchModificationCenter


Network resourceidentity

NRI(BSC6900,BSC6910)

2 UCNNODENOTE


RNC


No


4 UIMSIIDNNSCNID-MAPNOTE


RNC

Minimum of IMSI routeparameter in IDNNS

ImsiRtMin(BSC6900,BSC6910)

No



24

SN MO SN MO NE Parameter NameParameter IDConfigurable inCMEBatchModificationCenter

Maximum of IMSI routeparameter in IDNNS

ImsiRtMax(BSC6900,BSC6910)


CN node ID CNId5 UOPERATORCFGP

ARARNC

Feature SupportingMode of CS DomainSet this parameter toSUPP_NONE


No

Feature SupportingMode of PS DomainSet this parameter toSUPP_NONE


8.1.3 Example//Activating Iu Flex//Configuring the RNC supporting Iu Flex with Length of CS NRI in bits and Length of PS NRI in bits set to appropriate values



25

SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, PSNRILength=5;//Configuring the first CN nodeADD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, Dpx=2, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=1000, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;//Configuring the second CN nodeADD UCNNODE: CnOpIndex=1, CNId=18, CNDomainId=CS_DOMAIN, Dpx=3, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=1000, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;//Configuring the mapping relationship between NRI and the first CN nodeADD UNRIGLBCNIDMAP: CnOpIndex=1, CNId=17, NRI=8;//Configuring the mapping relationship between NRI and the second CN nodeADD UNRIGLBCNIDMAP: CnOpIndex=1, CNId=18, NRI=9;//Configuring the mapping relationship between the IMSI range and the first CN nodeADD UIMSIIDNNSCNIDMAP: ImsiRtMin=0, ImsiRtMax=499, CnOpIndex=1, CNId=17;//Configuring the mapping relationship between the IMSI range and the second CN nodeADD UIMSIIDNNSCNIDMAP: ImsiRtMin=500, ImsiRtMax=999, CnOpIndex=1, CNId=18;//Deactivating Iu FlexRMV UNRIGLBCNIDMAP: CnOpIndex=1, CNId=18, NRI=9;RMV UNRIGLBCNIDMAP: CnOpIndex=1, CNId=17, NRI=8;RMV UCNNODE: CnOpIndex=1, CNId=18;RMV UIMSIIDNNSCNIDMAP: ImsiRtMin=0, ImsiRtMax=499, CnOpIndex=1, CNId=17;RMV UIMSIIDNNSCNIDMAP: ImsiRtMin=500, ImsiRtMax=999, CnOpIndex=1, CNId=18;SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_NONE, PsNriCfgMode=SUPP_NONE;

8.2 Configuring Iu Flex Load Distribution ManagementThis section describes how to activate, verify, and deactivate the optional feature WRFD-021306Iu Flex Load Distribution Management.

8.2.1 Prerequisitesl Dependencies on Hardware

This feature does not have any special requirements for hardware.l Dependencies on Other Features

The feature WRFD-021302 Iu Flex has been configured before this feature is activated.l License

The license "Enhanced Iu Flex" on the RNC side has been activated. For details about thelicense items and how to activate the license, see License Management Feature ParameterDescription.

l Other PrerequisitesThe CN supports dynamic capacity management and load redistribution.

8.2.2 ProcedureActivation (Using MML Commands)

l Configuring load balancing in static capacity mode1. Run the RNC MML command MOD UCNNODE. In this step, set Capability of CN

Node to an appropriate value. The RNC performs load balancing between CN nodes basedon the configured CN capacities.



26

l Configuring load balancing in dynamic capacity mode1. Run the RNC MML command SET UOPERATORCFGPARA. In this step:

l Set Feature Supporting Mode of CS Domain to SUPP_IUFLEX.l Set Feature Supporting Mode of PS Domain to SUPP_IUFLEX.l Set CS Information Update Switch to ON.l Set PS Information Update Switch to ON.

NOTE

Load balancing in dynamic capacity mode takes effect only when the RNC is connected toHuawei CN and the preceding switches related to Iu Flex are turned on.

l Configuring load redistribution based on NullNRI1. Run the RNC MML command MOD UCNNODE. In this step, set Status of CN Node to

OFFLOAD.2. Run the RNC MML command SET UOPERATORCFGPARA. In this step, set NullNRI

VALUE to an appropriate value based on the network plan.l Configuring load redistribution based on Block CN Node1. Run the RNC MML command MOD UCNNODE. In this step, set Status of CN Node to

NORMAL and select the IUFLEX_NOT_SEL_BLOCK_SWITCH(IUFLEX NOTSEL BLOCK SWITCH) check box under the parameter PROCESS SWITCH.

Activation (Using the CME)l Configuring load balancing in static capacity mode

NOTE

When configuring the feature on the CME, you must configure a single configuration first, and thenperform batch modifications if required.You must perform a single configuration for a parameter before batch modifications of the parameter. Youare advised to perform batch modifications before logging out of the parameter setting interface.1. Configure a single object on the CME.

Set parameters on the CME according to the operation sequence in Table 8-3. Forinstructions on how to perform the CME single configuration, see CME SingleConfiguration Operation Guide.

2. (Optional) Modify objects in batches on the CME. (CME batch modification center)

To modify objects in batches, click on the CME to start the batch modificationwizard. For instructions on how to perform a batch modification through the CMEbatch modification center, press F1 on the wizard interface to obtain online help.



27

Table 8-3 Parameters to be set on the CMESN MO NE Paramete

r NameParameter ID

Configurable inCMEBatchModificationCenter

1 UCNNODE

RNC Capabilityof CNNode

AvailCap(BSC6900,BSC6910)

No

l Configuring load balancing in dynamic capacity mode

NOTE






r NameParameter ID


1 UOPERATORCFGPARA

RNC FeatureSupportingMode ofCS DomainSet thisparametertoSUPP_IUFLEX


No



28

SN MO NE Parameter Name

Parameter ID


FeatureSupportingMode of PSDomainSet thisparametertoSUPP_IUFLEX


CSInformation UpdateSwitchSet thisparameterto ON

CsInfoUpdFlag(BSC6900,BSC6910)

PSInformation UpdateSwitchSet thisparameterto ON

PsInfoUpdTmr(BSC6900,BSC6910)

l Configuring load redistribution based on NullNRI

NOTE







29

Table 8-5 Parameters to be set on the CMESN MO NE Paramet

er NameParameterID


1 UCNNODE

RNC Status ofCN NodeSet thisparameterOFFLOAD

CNLoadStatus(BSC6900,BSC6910)

No

2 UOPERATORCFGPARA

RNC NullNRIVALUE

NullNRI(BSC6900,BSC6910)

No

l Configuring load redistribution based on Block CN Node

NOTE







30

Table 8-6 Parameters to be set on the CMESN MO NE Parameter Name Parameter

IDConfigurableinCMEBatchModificationCenter

1 UCNNODE

RNC

Status of CN NodeSet this parameter to NORMAL


No

PROCESSS WITCHSet this parameter toIUFLEX_NOT_SEL_BLOCK_SWITCH-1

PROCESSSWITCH(BSC6900,BSC6910)

Verification Procedurel Verifying load balancing in static capacity mode1. Run the RNC MML command DSP UCNNODE to query the capacity ratio of CN nodes.2. Check the following performance counters on the M2000 to verify that the RNC performs

load balancing based on the preconfigured CN capacity:l Performance counters for CS service setup:

VS.IU.LdBalRtCS.IMSI VS.IU.LdBalRtCS.InValidNRI VS.IU.LdBalRtCS.IMEI

l Performance counters for PS service setup: VS.IU.Load.RoutePS.IMSI VS.IU.Load.RoutePS.NRI VS.IU.Load.RoutePS.IMEI

l Verifying load balancing in dynamic capacity mode1. Run the RNC MML command DSP UCNNODE to query the capacity ratio of CN nodes.2. On the RNC LMT, choose Trace > UMTS Services to initiate Uu and Iu interface message

tracing.3. Check the traced messages. If the CN sends the RNC an INFORMATION TRANSFER

INDICATION message, the dynamic CN capacity ratio is updated and used. If the CNdoes not send any INFORMATION TRANSFER INDICATION message to the RNC,the static CN capacity ratio is used.

4. Check the following performance counters on the M2000 to verify that the RNC performsload balancing based on the dynamic CN capacity ratio:



31

l Performance counters for CS service setup: VS.IU.LdBalRtCS.IMSI VS.IU.LdBalRtCS.InValidNRI VS.IU.LdBalRtCS.IMEI

l Performance counters for PS service setup: VS.IU.Load.RoutePS.IMSI VS.IU.Load.RoutePS.NRI VS.IU.Load.RoutePS.IMEI

l Verifying load redistribution based on NullNRI1. On the RNC LMT, choose Trace > UMTS Services to initiate Uu and Iu interface message

tracing.2. Power off the UE. The PTMSI of the UE is assigned by SGSN1.3. Set SGSN1 to the OFFLOAD state and SGSN2 to the NORMAL state on the RNC.4. Set SGSN1 to the OFFLOAD state on SGSN1.5. Power on the UE and the UE makes an attach request. Check the traced Iu interface

messages. The expected result is as follows:l The RNC routes the RRC_INIT_DIRECT_TRANSFER message to SGSN1 based

on NULL NRI. The attach reception message from SGSN1 contains NULL NRI andnon-broadcasting location areas.

l After receiving the non-broadcasting location areas, the UE sends a new routing areaupdate (RAU) request and contains NULL NRI in theRRC_INIT_DIRECT_TRANSFER message. The RNC routes theRRC_INIT_DIRECT_TRANSFER message to SGSN2, of which the state is notOFFLOAD, based on NULL NRI.

l Verifying load redistribution based on Block CN Node1. On the RNC LMT, choose Trace > UMTS Services to initiate Uu and Iu interface message

tracing.2. Power off the UE. The PTMSI of the UE is assigned by SGSN1.3. Set SGSN1 to the BLOCK state and SGSN2 to the NORMAL state on the RNC.4. Power on the UE and the UE makes an attach request. Check the

RRC_INIT_DIRECT_TRANSFER message traced on the Iu interface.Expected result: The RRC_INIT_DIRECT_TRANSFER message contains NRI of SGSN1.The RNC routes the RRC_INIT_DIRECT_TRANSFER message to SGSN2 because SGSN1is in the BLOCK state.

Deactivation(Using MML Commands)l Deactivating load balancing in static capacity modeLoad balancing in static capacity mode does not need to be deactivated.l Deactivating load balancing in dynamic capacity mode1. Run the RNC MML command SET UOPERATORCFGPARA. In this step, set CS

Information Update Switch to OFF and PS Information Update Switch to OFF.



32

l Deactivating load redistribution based on NullNRI1. Run the RNC MML command MOD UCNNODE. In this step, set Status of CN Node to

NORMAL.l Deactivating load redistribution based on Block CN Node1. Run the RNC MML command MOD UCNNODE. In this step, set Status of CN Node to

NORMAL and deselect the IUFLEX_NOT_SEL_BLOCK_SWITCH(IUFLEX NOTSEL BLOCK SWITCH) check box under the parameter PROCESS SWITCH.

Deactivation(Using the CME)l Configuring load balancing in static capacity modeLoad balancing in static capacity mode does not need to be deactivated.l Configuring load balancing in dynamic capacity mode

NOTE

When configuring the feature on the CME, you must configure a single configuration first, and thenperform batch modifications if required.You must perform a single configuration for a parameter before batch modifications of the parameter. Youare advised to perform batch modifications before logging out of the parameter setting interface.

1. Configure a single object on the CME.Set parameters on the CME according to the operation sequence in Table 8-7. Forinstructions on how to perform the CME single configuration, see CME SingleConfiguration Operation Guide.



Table 8-7 Parameters to be set on the CMESN MO NE Parameter Name Paramet

er IDConfigurableinCMEBatchModificationCenter

1 UOPERATORCFGPARA

RNC

CS Information UpdateSwitchSet this parameter to OFF

CsInfoUpdFlag(BSC6900,BSC6910)

No



33

SN MO NE Parameter Name Parameter ID

ConfigurableinCMEBatchModificationCenter

PS Information UpdateProtection TimerSet this parameter to OFF

PsInfoUpdTmr(BSC6900,BSC6910)

l Configuring load redistribution based on NullNRI

NOTE






r NameParameter ID


1 UCNNODE

RNC Status ofCN NodeSet thisparametertoNORMAL


No



34

l Configuring load redistribution based on Block CN Node

NOTE






r NameParameter ID


1 UCNNODE

RNC Status ofCN NodeSet thisparametertoNORMAL


No

PROCESSS WITCHSet thisparametertoIUFLEX_NOT_SEL_BLOCK_SWITCH-0

PROCESSSWITCH(BSC6900,BSC6910)

8.2.3 Example//Activating Iu Flex Load Distribution Management//Configuring Load balancing in static capacity mode



35

ADD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, Dpx=2, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=1000, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;//Configuring load balancing in dynamic capacity modeSET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, CsInfoUpdFlag=ON, PsInfoUpdFlag=ON;//Configuring load redistribution based on NullNRIMOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, CNLoadStatus=OFFLOAD, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, NullNRI=31;//Configuring load redistribution based on Block CN NodeMOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF, PROCESSSWITCH=IUFLEX_NOT_SEL_BLOCK_SWITCH-1;//Deactivating Iu Flex Load Distribution Management//Deactivating load balancing in dynamic capacity modeSET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX, PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, CsInfoUpdFlag=OFF, PsInfoUpdFlag=OFF;//Deactivating load redistribution based on NullNRIMOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;//Deactivating load redistribution based on Block CN NodeMOD UCNNODE: CnOpIndex=1, CNId=17, CNDomainId=CS_DOMAIN, CNLoadStatus=NORMAL, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF, PROCESSSWITCH=IUFLEX_NOT_SEL_BLOCK_SWITCH-0;



36

9 ParametersTable 9-1 Parameter description

Parameter ID NE MMLCommand

Feature ID Feature Name Description

RsvSwitch3 BSC6900 SETUALGORSVPARA

None None Meaning:RRMalgorithmreserved U32Switch Para 3.The 32-bitparameter isreserved forfurther changerequest use.Disusestatement: Thisparameter isusedtemporarily inpatch versionsand will bereplaced with anew parameterin later versions.The newparameter IDreflects theparameterfunction.Therefore, thisparameter is notrecommendedfor theconfigurationinterface.

WCDMA RANIu Flex Feature Parameter Description 9 Parameters


37



GUI ValueRange:RESERVED_SWITCH_3_BIT1,RESERVED_SWITCH_3_BIT2,RESERVED_SWITCH_3_BIT3,RESERVED_SWITCH_3_BIT4,RESERVED_SWITCH_3_BIT5,RESERVED_SWITCH_3_BIT6,RESERVED_SWITCH_3_BIT7,RESERVED_SWITCH_3_BIT8,RESERVED_SWITCH_3_BIT9,RESERVED_SWITCH_3_BIT10,RESERVED_SWITCH_3_BIT11,RESERVED_SWITCH_3_BIT12,RESERVED_SWITCH_3_BIT13,RESERVED_SWITCH_3_BIT14,RESERVED_SWITCH_3_BIT15,RESERVED_SWITCH_3_BIT



38



16,RESERVED_SWITCH_3_BIT17,RESERVED_SWITCH_3_BIT18,RESERVED_SWITCH_3_BIT19,RESERVED_SWITCH_3_BIT20,RESERVED_SWITCH_3_BIT21,RESERVED_SWITCH_3_BIT22,RESERVED_SWITCH_3_BIT23,RESERVED_SWITCH_3_BIT24,RESERVED_SWITCH_3_BIT25,RESERVED_SWITCH_3_BIT26,RESERVED_SWITCH_3_BIT27,RESERVED_SWITCH_3_BIT28,RESERVED_SWITCH_3_BIT29,RESERVED_SWITCH_3_BIT30,RESERVED_SWITCH_3_BIT31,RESERVED_S



39



WITCH_3_BIT32Unit:NoneActual ValueRange:RESERVED_SWITCH_3_BIT1,RESERVED_SWITCH_3_BIT2,RESERVED_SWITCH_3_BIT3,RESERVED_SWITCH_3_BIT4,RESERVED_SWITCH_3_BIT5,RESERVED_SWITCH_3_BIT6,RESERVED_SWITCH_3_BIT7,RESERVED_SWITCH_3_BIT8,RESERVED_SWITCH_3_BIT9,RESERVED_SWITCH_3_BIT10,RESERVED_SWITCH_3_BIT11,RESERVED_SWITCH_3_BIT12,RESERVED_SWITCH_3_BIT13,RESERVED_SWITCH_3_BIT14,RESERVED_S



40



WITCH_3_BIT15,RESERVED_SWITCH_3_BIT16,RESERVED_SWITCH_3_BIT17,RESERVED_SWITCH_3_BIT18,RESERVED_SWITCH_3_BIT19,RESERVED_SWITCH_3_BIT20,RESERVED_SWITCH_3_BIT21,RESERVED_SWITCH_3_BIT22,RESERVED_SWITCH_3_BIT23,RESERVED_SWITCH_3_BIT24,RESERVED_SWITCH_3_BIT25,RESERVED_SWITCH_3_BIT26,RESERVED_SWITCH_3_BIT27,RESERVED_SWITCH_3_BIT28,RESERVED_SWITCH_3_BIT29,RESERVED_SWITCH_3_BIT30,RESERVED_S



41



WITCH_3_BIT31,RESERVED_SWITCH_3_BIT32DefaultValue:RESERVED_SWITCH_3_BIT1-0&RESERVED_SWITCH_3_BIT2-0&RESERVED_SWITCH_3_BIT3-0&RESERVED_SWITCH_3_BIT4-0&RESERVED_SWITCH_3_BIT5-0&RESERVED_SWITCH_3_BIT6-0&RESERVED_SWITCH_3_BIT7-0&RESERVED_SWITCH_3_BIT8-0&RESERVED_SWITCH_3_BIT9-0&RESERVED_SWITCH_3_BIT10-0&RESERVED_SWITCH_3_BIT11-0&RESERVED_SWITCH_3_BIT12-0&RESERVED_SWITCH_3_BIT13-0&RESERVED_SWITCH_3_BIT14-0&RESERVED_SWITCH_3_BIT15-0&RESERVED_SWITCH_3_BIT16-0&RESERVED_SWITCH_3_BIT17-0&RESERVE



42



D_SWITCH_3_BIT18-0&RESERVED_SWITCH_3_BIT19-0&RESERVED_SWITCH_3_BIT20-0&RESERVED_SWITCH_3_BIT21-0&RESERVED_SWITCH_3_BIT22-0&RESERVED_SWITCH_3_BIT23-0&RESERVED_SWITCH_3_BIT24-0&RESERVED_SWITCH_3_BIT25-0&RESERVED_SWITCH_3_BIT26-0&RESERVED_SWITCH_3_BIT27-0&RESERVED_SWITCH_3_BIT28-0&RESERVED_SWITCH_3_BIT29-0&RESERVED_SWITCH_3_BIT30-0&RESERVED_SWITCH_3_BIT31-0&RESERVED_SWITCH_3_BIT32-0



43



RsvSwitch3 BSC6910 SETUALGORSVPARA

None None Meaning:RRMalgorithmreserved U32Switch Para 3.The 32-bitparameter isreserved forfurther changerequest use.Disusestatement: Thisparameter isusedtemporarily inpatch versionsand will bereplaced with anew parameterin later versions.The newparameter IDreflects theparameterfunction.Therefore, thisparameter is notrecommendedfor theconfigurationinterface.GUI ValueRange:RESERVED_SWITCH_3_BIT1,RESERVED_SWITCH_3_BIT2,RESERVED_SWITCH_3_BIT3,RESERVED_SWITCH_3_BIT4,RESERVED_SWITCH_3_BIT5,RESERVED_S



44






45



WITCH_3_BIT22,RESERVED_SWITCH_3_BIT23,RESERVED_SWITCH_3_BIT24,RESERVED_SWITCH_3_BIT25,RESERVED_SWITCH_3_BIT26,RESERVED_SWITCH_3_BIT27,RESERVED_SWITCH_3_BIT28,RESERVED_SWITCH_3_BIT29,RESERVED_SWITCH_3_BIT30,RESERVED_SWITCH_3_BIT31,RESERVED_SWITCH_3_BIT32Unit:NoneActual ValueRange:RESERVED_SWITCH_3_BIT1,RESERVED_SWITCH_3_BIT2,RESERVED_SWITCH_3_BIT3,RESERVED_SWITCH_3_BIT4,RESERVED_S



46






47



WITCH_3_BIT21,RESERVED_SWITCH_3_BIT22,RESERVED_SWITCH_3_BIT23,RESERVED_SWITCH_3_BIT24,RESERVED_SWITCH_3_BIT25,RESERVED_SWITCH_3_BIT26,RESERVED_SWITCH_3_BIT27,RESERVED_SWITCH_3_BIT28,RESERVED_SWITCH_3_BIT29,RESERVED_SWITCH_3_BIT30,RESERVED_SWITCH_3_BIT31,RESERVED_SWITCH_3_BIT32DefaultValue:RESERVED_SWITCH_3_BIT1-0&RESERVED_SWITCH_3_BIT2-0&RESERVED_SWITCH_3_BIT3-0&RESERVED_SWITCH_3_BIT4-0&RESERVED_SWITC



48



H_3_BIT5-0&RESERVED_SWITCH_3_BIT6-0&RESERVED_SWITCH_3_BIT7-0&RESERVED_SWITCH_3_BIT8-0&RESERVED_SWITCH_3_BIT9-0&RESERVED_SWITCH_3_BIT10-0&RESERVED_SWITCH_3_BIT11-0&RESERVED_SWITCH_3_BIT12-0&RESERVED_SWITCH_3_BIT13-0&RESERVED_SWITCH_3_BIT14-0&RESERVED_SWITCH_3_BIT15-0&RESERVED_SWITCH_3_BIT16-0&RESERVED_SWITCH_3_BIT17-0&RESERVED_SWITCH_3_BIT18-0&RESERVED_SWITCH_3_BIT19-0&RESERVED_SWITCH_3_BIT20-0&RESERVED_SWITCH_3_BIT21-0&RESERVED_SWITCH_3_BIT22-0&RESERVED_SWITCH_3_BIT23-0&RESERVED_SWITCH_3_BIT24-0&RESERVED_SWITCH_3_BI



49



T25-0&RESERVED_SWITCH_3_BIT26-0&RESERVED_SWITCH_3_BIT27-0&RESERVED_SWITCH_3_BIT28-0&RESERVED_SWITCH_3_BIT29-0&RESERVED_SWITCH_3_BIT30-0&RESERVED_SWITCH_3_BIT31-0&RESERVED_SWITCH_3_BIT32-0



50



PROCESSSWITCH

BSC6900 ADDUCNNODEMODUCNNODE

WRFD-021304 RAN SharingIntroductionPackage

Meaning:1)IUFLEX_NOT_SEL_BLOCK_SWITCHWhether theRNC forwardsthe INITIAL UEMESSAGEmessage to a CNnode in Iu Flexnetworkingwhen the statusof the CN nodeis NORMAL onthe RNC. 1: Thisswitch is turnedon. The status ofthe CN node ischanged fromNORMAL toBLOCK, and theRNC forwardsonly theINITIAL UEMESSAGEmessage withcause value"pagingresponse" to theCN node. 0: Thisswitch is turnedoff. The status ofthe CN node isunchanged. 2)REL7_QOS_HANDLE_SWITCH(Release 7Qos Parameterhandle switch)Whether the CNNode need sendR7 Qosparameter toUE. 1:Thisswitch is turnedon.Element"Higher bitratesthan 16 Mbps



51



flag" will addedto the Initial UEMessage byRNC. 0:Thisswitch is turnedoff.Element"Higher bitratesthan 16 Mbpsflag" will notadded to theInitial UEMessage byRNC.GUI ValueRange:IUFLEX_NOT_SEL_BLOCK_SWITCH(IUFLEX_NOT_SEL_BLOCK_SWITCH),REL7_QOS_HANDLE_SWITCH(REL7_QOS_HANDLE_SWITCH)Unit:NoneActual ValueRange:Thisparameter is setto 0 or 1according to therelated domains.DefaultValue:IUFLEX_NOT_SEL_BLOCK_SWITCH-0,REL7_QOS_HANDLE_SWITCH-0



52



PROCESSSWITCH

BSC6910 ADDUCNNODEMODUCNNODE

WRFD-021304 RAN SharingIntroductionPackage

Meaning:1)IUFLEX_NOT_SEL_BLOCK_SWITCHWhether theRNC forwardsthe INITIAL UEMESSAGEmessage to a CNnode in Iu Flexnetworkingwhen the statusof the CN nodeis NORMAL onthe RNC. 1: Thisswitch is turnedon. The status ofthe CN node ischanged fromNORMAL toBLOCK, and theRNC forwardsonly theINITIAL UEMESSAGEmessage withcause value"pagingresponse" to theCN node. 0: Thisswitch is turnedoff. The status ofthe CN node isunchanged. 2)REL7_QOS_HANDLE_SWITCH(Release 7Qos Parameterhandle switch)Whether the CNNode need sendR7 Qosparameter toUE. 1:Thisswitch is turnedon.Element"Higher bitratesthan 16 Mbps



53



flag" will addedto the Initial UEMessage byRNC. 0:Thisswitch is turnedoff.Element"Higher bitratesthan 16 Mbpsflag" will notadded to theInitial UEMessage byRNC.GUI ValueRange:IUFLEX_NOT_SEL_BLOCK_SWITCH(IUFLEX_NOT_SEL_BLOCK_SWITCH),REL7_QOS_HANDLE_SWITCH(REL7_QOS_HANDLE_SWITCH)Unit:NoneActual ValueRange:Thisparameter is setto 0 or 1according to therelated domains.DefaultValue:IUFLEX_NOT_SEL_BLOCK_SWITCH-0,REL7_QOS_HANDLE_SWITCH-0



54



NRI BSC6900 ADDUNRIGLBCNIDMAPRMVUNRIGLBCNIDMAP

WRFD-021302WRFD-021311

Iu FlexMOCNIntroductionPackage

Meaning:Identi-fying a Networkresourse: 1. TheNRI numbers ofCS domain andPS domain areindependentfrom each other.2. If multiplepool areasoverlap, the NRIuniquelyidentify all theCN nodesconnected to it.3. A CN nodecan havemultiple NRIs.In one pool area,however, anNRI can onlycorrespond toone CN node.An NRIuniquelyidentifies a CNnode that servesa pool area. Thevalue range ofNRI is variable.The value rangedepends on thescale of a CNdomain andexpansionrequirements.The maximumnumber of NRIsis 1,024. Forexample, a CSdomain has amaximum of 16nodes. In thiscase, Length ofCS NRI in bits isset to 4, whichindicates that anNRI is



55



represented byfour binarydigits.Therefore, thevalue range ofNRI is 0 to 15.GUI ValueRange:0~1023Unit:NoneActual ValueRange:0~1023DefaultValue:None



56



NRI BSC6910 ADDUNRIGLBCNIDMAPRMVUNRIGLBCNIDMAP

WRFD-021302WRFD-021311

Iu FlexMOCNIntroductionPackage

Meaning:Identi-fying a Networkresourse: 1. TheNRI numbers ofCS domain andPS domain areindependentfrom each other.2. If multiplepool areasoverlap, the NRIuniquelyidentify all theCN nodesconnected to it.3. A CN nodecan havemultiple NRIs.In one pool area,however, anNRI can onlycorrespond toone CN node.An NRIuniquelyidentifies a CNnode that servesa pool area. Thevalue range ofNRI is variable.The value rangedepends on thescale of a CNdomain andexpansionrequirements.The maximumnumber of NRIsis 1,024. Forexample, a CSdomain has amaximum of 16nodes. In thiscase, Length ofCS NRI in bits isset to 4, whichindicates that anNRI is



57



represented byfour binarydigits.Therefore, thevalue range ofNRI is 0 to 15.GUI ValueRange:0~1023Unit:NoneActual ValueRange:0~1023DefaultValue:None

AvailCap BSC6900 ADDUCNNODEMODUCNNODE

WRFD-021306WRFD-021311

Iu Flex LoadDistributionManagementMOCNIntroductionPackage

Meaning:Thisparameter isused toconfigure therelative capacityof each CN nodein Iu-Flexscenarios. If auser cannotselect a CN nodebased on theNNSF, a CNnode needs to beselected amongall the availableCN nodesaccording to theproportionsgenerated basedon CN nodecapacity.GUI ValueRange:0~65535Unit:NoneActual ValueRange:0~65535000step:1000DefaultValue:None



58



AvailCap BSC6910 ADDUCNNODEMODUCNNODE

WRFD-021306WRFD-021311

Iu Flex LoadDistributionManagementMOCNIntroductionPackage

Meaning:Thisparameter isused toconfigure therelative capacityof each CN nodein Iu-Flexscenarios. If auser cannotselect a CN nodebased on theNNSF, a CNnode needs to beselected amongall the availableCN nodesaccording to theproportionsgenerated basedon CN nodecapacity.GUI ValueRange:0~65535Unit:NoneActual ValueRange:0~65535000step:1000DefaultValue:None

CsInfoUpdFlag BSC6900 SETUOPERATORCFGPARA

WRFD-021306 Iu Flex LoadDistributionManagement

Meaning:Indicating whether theCS domainpermits the CNinformation toupdate .GUI ValueRange:OFF, ONUnit:NoneActual ValueRange:OFF, ONDefaultValue:OFF



59



CsInfoUpdFlag BSC6910 SETUOPERATORCFGPARA


Meaning:Indicating whether theCS domainpermits the CNinformation toupdate .GUI ValueRange:OFF, ONUnit:NoneActual ValueRange:OFF, ONDefaultValue:OFF

PsInfoUpdFlag BSC6900 SETUOPERATORCFGPARA


Meaning:Indicating whether thePS domainpermits the CNinformation toupdate .GUI ValueRange:OFF, ONUnit:NoneActual ValueRange:OFF, ONDefaultValue:OFF

PsInfoUpdFlag BSC6910 SETUOPERATORCFGPARA


Meaning:Indicating whether thePS domainpermits the CNinformation toupdate .GUI ValueRange:OFF, ONUnit:NoneActual ValueRange:OFF, ONDefaultValue:OFF



60



CNLoadStatus BSC6900 ADDUCNNODEMODUCNNODE

WRFD-021306WRFD-021311MRFD-211502

Iu Flex LoadDistributionManagementMOCNIntroductionPackageIP-Based BSCand RNC Co-Transmission onMBSC Side

Meaning:Statusof a CN node.The status needsto be negotiatedwith the CN andis configuredthrough theMMLcommand. A CNnode can beconfigured withthe followingstatus: 1.Normal: Thisvalue indicatesthat the UE canaccess the CNnode normally.2. Offload: If theUE carries"NullNRI"("SETUOPERATORCFGPARA") inthe Initial Directtransfermessage, the UEcannot accessthe CN node. Ifthe UE carriesNRI but not"NullNRI" in theInitial Directtransfermessage, the UEcan access theCN node. 3.Inhibited: Thisvalue indicatesthat the UEcannot accessthe CN nodenormally.GUI ValueRange:NORMAL, OFFLOAD,INHIBITED



61



Unit:NoneActual ValueRange:NORMAL, OFFLOAD,INHIBITEDDefaultValue:None



62



CNLoadStatus BSC6910 ADDUCNNODEMODUCNNODE

WRFD-021306WRFD-021311MRFD-211502

Iu Flex LoadDistributionManagementMOCNIntroductionPackageIP-Based BSCand RNC Co-Transmission onMBSC Side

Meaning:Statusof a CN node.The status needsto be negotiatedwith the CN andis configuredthrough theMMLcommand. A CNnode can beconfigured withthe followingstatus: 1.Normal: Thisvalue indicatesthat the UE canaccess the CNnode normally.2. Offload: If theUE carries"NullNRI"("SETUOPERATORCFGPARA") inthe Initial Directtransfermessage, the UEcannot accessthe CN node. Ifthe UE carriesNRI but not"NullNRI" in theInitial Directtransfermessage, the UEcan access theCN node. 3.Inhibited: Thisvalue indicatesthat the UEcannot accessthe CN nodenormally.GUI ValueRange:NORMAL, OFFLOAD,INHIBITED



63



Unit:NoneActual ValueRange:NORMAL, OFFLOAD,INHIBITEDDefaultValue:None

CsNriCfgMode BSC6900 SETUOPERATORCFGPARA

WRFD-021304WRFD-021311WRFD-021302WRFD-021306

RAN SharingIntroductionPackageMOCNIntroductionPackageIu FlexIu Flex LoadDistributionManagement

Meaning:Thisparameterspecifies featuremode ofoperators in theCS domain. Youshouldconfigure thenetworkresourceidentifier (NRI)when MOCN orIu-Flex issupported.GUI ValueRange:SUPP_NONE,SUPP_IUFLEX, SUPP_MOCN,SUPP_IUFLEX_MOCNUnit:NoneActual ValueRange:SUPP_NONE,SUPP_IUFLEX, SUPP_MOCN,SUPP_IUFLEX_MOCNDefaultValue:SUPP_NONE



64



CsNriCfgMode BSC6910 SETUOPERATORCFGPARA

WRFD-021304WRFD-021311WRFD-021302WRFD-021306

RAN SharingIntroductionPackageMOCNIntroductionPackageIu FlexIu Flex LoadDistributionManagement

Meaning:Thisparameterspecifies featuremode ofoperators in theCS domain. Youshouldconfigure thenetworkresourceidentifier (NRI)when MOCN orIu-Flex issupported.GUI ValueRange:SUPP_NONE,SUPP_IUFLEX, SUPP_MOCN,SUPP_IUFLEX_MOCNUnit:NoneActual ValueRange:SUPP_NONE,SUPP_IUFLEX, SUPP_MOCN,SUPP_IUFLEX_MOCNDefaultValue:SUPP_NONE



65



PsNriCfgMode BSC6900 SETUOPERATORCFGPARA

WRFD-021302WRFD-021311WRFD-021306

Iu FlexMOCNIntroductionPackageIu Flex LoadDistributionManagement

Meaning:Thisparameterspecifies featuremode ofoperators in thePS domain. Youshouldconfigure thenetworkresourceidentifier (NRI)when MOCN orIu-Flex issupported.GUI ValueRange:SUPP_NONE,SUPP_IUFLEX, SUPP_MOCN,SUPP_IUFLEX_MOCNUnit:NoneActual ValueRange:SUPP_NONE,SUPP_IUFLEX, SUPP_MOCN,SUPP_IUFLEX_MOC