You are on page 1of 28

Iu Flex RAN12.

Feature Parameter Description

Issue Date

02 2012-06-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. All rights reserved.


No part of this document may be reproduced or transmitted in any form or by any means without prior written consent 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.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase 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 representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.


Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: Email: http://www.huawei.com support@huawei.com

WCDMA RAN Iu Flex

Contents

Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1 1.2 Intended Audience......................................................................................................................... 1-1 1.3 Change History.............................................................................................................................. 1-1

2 Overview......................................................................................................................................2-1
2.1.1 Background .......................................................................................................................... 2-1 2.1.2 Pool Area .............................................................................................................................. 2-1 2.1.3 NRI........................................................................................................................................ 2-2

3 NAS Node Selection Function ...............................................................................................3-1


3.1.1 Overview ............................................................................................................................... 3-1 3.1.2 UE Indicating Routing ........................................................................................................... 3-1 3.1.3 RNC Selecting CN Node ...................................................................................................... 3-1 3.1.4 IMSI Paging .......................................................................................................................... 3-2

4 Load Balancing..........................................................................................................................4-3 5 Flow Control ...............................................................................................................................5-1 6 Load Re-Distribution ................................................................................................................6-1


6.1 Load Re-distribution Based on NullNRI ........................................................................................ 6-1 6.2 Load Re-distribution Based on Blocking CN Node ....................................................................... 6-2

7 Parameters..................................................................................................................................7-1 8 Counters ......................................................................................................................................8-1 9 Glossary ......................................................................................................................................9-1 10 Reference Documents .........................................................................................................10-1

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN Iu Flex

1 Introduction

1 Introduction
1.1 Scope
This document describes the Iu Flex feature. It covers the overview, technical description, and parameters related to the feature.

1.2 Intended Audience


This document is intended for:

Personnel who are familiar with WCDMA basics Personnel who need to understand Iu Flex Personnel who work with Huawei products

1.3 Change History


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows:

Feature change: refers to the change in the Iu Flex feature. Editorial change: refers to the change in wording or the addition of the information that was not described in the earlier version.

Document Issues
The document issues are as follows:

02 (2012-06-30) 01 (2010-03-30) Draft (2009-12-05)

02 (2012-06-30)
This is the document for the first commercial release of RAN12.0. Compared with issue 01 (2010-03-30) of RAN12.0, this issue incorporates the changes described in the following table: Change Change Description Type Feature change None. Parameter Change None. None.

Editorial Added the descriptions that UEs are routed to specific CN change nodes. For details, see chapter 4 "Load Balancing."

01 (2010-03-30)
This is the document for the first commercial release of RAN12.0. Compared with issue Draft (2009-12-05) of RAN12.0, this issue optimizes the description.

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

1-1

1 Introduction

WCDMA RAN Iu Flex

Draft (2009-12-05)
This is the draft of the document for RAN12.0. Compared with issue 02 (2009-06-30) of RAN11.0, this issue optimizes the description.

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

1-2

WCDMA RAN Iu Flex

2 Overview

2 Overview
Iu 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 contains one or more MSC/SGSN service areas. In a pool area, the UE roams freely without changing the serving CN node. The Iu Flex enables a RAN node to route information to different CN nodes, implementing the load balance among MSCs or SGSNs.

2.1.1 Background
In the versions earlier than 3GPP R5, one RAN node is controlled by only one CN node. Such a network structure, however, has some limitations. From the perspective of 3G traffic distribution, the traffic volume of urban areas in the daytime constitutes a major proportion of the total, but the traffic volume of urban areas at night decreases to a low level. Therefore, Iu Flex is introduced in 3GPP R5. With Iu Flex, one RAN node can be connected to several CN nodes and these CN nodes can form a pool area. The UEs in the same pool area do not need to change the serving CN node. The introduction of Iu Flex avoids the imbalance of resource usage among different CN nodes in different traffic peak hours and achieves the load balancing among several CN nodes in the WCDMA network. In a traditional network structure, a RAN node only needs to know whether the destination is the CS domain or the PS domain before sending information. It does not need to discriminate specific 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 CS nodes and PS nodes form different pool areas. Therefore, a RAN node can send information to different CN nodes in the CS or PS domain and achieve load balancing among several CN nodes in the pool area. The pool area is described as follows:

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. Pool areas may overlap. RAN nodes belong to all the overlapping pool areas. If a UE roams in a certain pool area, it does not need to change the serving CN node. The CS pool area is independent of the PS pool area.

The Iu Flex feature enhances network reliability, achieves load balancing, and reduces UE roaming signaling.

2.1.2 Pool Area


This 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 a collection of one or more RAN node service areas. It is served, in parallel, by one or more CN nodes 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 radio coverage of the pool area. Pool areas can overlap each other. If several overlapping pool areas cover 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 with the granularity of RAN node service areas.

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

2-1

2 Overview

WCDMA RAN Iu Flex

In a pool area, the UE roams freely without changing the serving CN node. The RAN node service 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:


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. 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. PS pool area 1: includes RAN node areas 1 and 5, and SGSNs 1 and 2, which provide service for the RAN node areas. 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 coexist with 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 CS pool area 2 and PS pool area 2, or different pool areas, such as CS pool area 1 and PS pool area 1. Each pool area has its unique configuration of the CN node capability or number.

2.1.3 NRI
The Network Resource Identifier (NRI) identifies the CN node that serves a pool area. The NRI has a flexible length from 1 bit to 10 bits. 0 bit means no Iu flex. The NRI lengths are the same for all the CN nodes in one pool area.

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

2-2

WCDMA RAN Iu Flex

2 Overview

In areas where pool areas overlap, the NRI identifies the CN node that serves these overlapping pool areas. For overlapping pool areas, the NRI lengths must be configured the same for all the nodes serving specific pool areas. The CN nodes in the CS domain and those in the PS domain are addressed separately, so the NRIs 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 of the Packet TMSI (P-TMSI) for the PS domain. The TMSI or P-TMSI is assigned to the UE by the serving CN node. The TMSI or P-TMSI allocation mechanism of the CN node generates TMSIs 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 the RAN nodes. In the WCDMA system, the UE provides an intra domain NAS node selector (IDNNS) in the access stratum (AS) part of the Initial Direct Transfer message to the RAN node. The IDNNS contains a routing parameter with a fixed length of 10 bits. This routing parameter contains the NRI information. In addition, the IDNNS contains the identity that indicates the source of the routing parameters. The identity can be TMSI, international mobile subscriber identity (IMSI), international mobile equipment identity (IMEI), and so on. The RAN node masks the significant bits out of the routing parameter part of the IDNNS to determine the NRI that is used to identify the relevant CN node. The most significant bit of the NRI corresponds to the most significant bit of the routing parameter in the IDNNS.

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

2-3

WCDMA RAN Iu Flex

3 NAS Node Selection Function

3 NAS Node Selection Function


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

3.1.1 Overview
The NAS node selection function (NNSF) performs the selection of a CN node and the processing of the IMSI Paging Message in both the CS and PS domain. In the RAN node, the NNSF selects a specific CN node (MSC server or SGSN) and routes the initial NAS signaling message to the selected CN node. If a CN node address configured for the NRI can be derived from the initial NAS signaling message, the NNSF routes the message to the CN node. If no CN node address is configured for the derived NRI or no NRI can be derived (for example, the UE indicates an identity that contains no NRI), or the configured CN node cannot be reached, the NNSF selects an available CN node according to 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 to the UE when the CN allocates the TMSI or P-TMSI to the UE. 2. UE indicates the route information and sends it to the RNC in the Initial Direct Transfer message. 3. RNC selects the CN Node based on the routing information in the Initial Direct Transfer message.

3.1.2 UE Indicating Routing


UE indicates the routing information to help RNC select an appropriate CN node. The routing information is contained in the IDNNS IE in the Initial Direct Transfer message from the UE to the RNC. IDNNS IE consists of two parts of routing information:

The first part indicates the ID type (TMSI/P-TMSI, IMSI, IMEI) used for calculating the routing parameter. The second part indicates the calculated routing parameter.

The routing parameter is encoded as follows: 1. If the UE has a TMSI or P-TMSI, the routing parameter is NRI. NRI is a 10-bit field from the fourteenth bit to the twenty-third bit in TMSI or P-TMSI. TMSI and P-TMSI are allocated by CN node. 2. Else if the UE has an IMSI, the routing parameter is calculated as (IMSI div 10) mod 1000, where "div" means divided by and "mod" means modulus. 3. Else if the UE has an IMEI, the routing parameter is calculated as (IMEI div 10) mod 1000.

3.1.3 RNC Selecting CN Node


After the RNC received the Initial Direct Transfer message from the UE, the RNC selects a CN node based on the IDNNS IE in the message.

Selecting CN Node Based on TMSI/P-TMSI


If IDNNS indicates that the route information is from the TMSI or P-TMSI, the RNC selects the route based on the NRI. The RNC derives the NRI from the routing parameter and then selects a CN node

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

3-1

3 NAS Node Selection Function

WCDMA RAN Iu Flex

based on the mapping between the NRI and the CN nodes. The mapping is configured by running the ADD UNRIGLBCNIDMAP command. The mapping must be configured on both the CN and RNC sides. The NRI configured on the RNC side must be negotiated with the CN so that it is the same as the NRI configured on the CN side. If the CN node corresponding to an NRI is inhibited or cannot be reached, or the value of the NRI is NULLNRI, If the NRI is not configured at the RNC, the RNC selects a CN node based on the load balancing.

Selecting CN Node Based on IMSI


If IDNNS indicates that the route information is from the IMSI, the RNC selects the route based on the mapping between the IMSI and the CN nodes.

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 UIMSIIDNNSCNIDMAP command. the IMSI route of a UE is not configured, the RNC selects a CN node based on the load balancing.

If

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 between IMSI and global CN ID received from CN. If fails, the terminated call is processed as a originated call. For details, see 3.1.4 IMSI Paging.

Selecting CN Node Based on IMEI


If IDNNS indicates that the route information is from the IMEI, the RNC selects the CN node based on the load balancing.

3.1.4 IMSI Paging


Processing of the IMSI Paging Message (CS Domain)
To increase the success rate of routing the paging response message to the CN node that issues the paging request, the RNC capable of the Iu Flex needs to process the IMSI paging message as follows:

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 IMSI rather than the TMSI, the paging message must contain the Global-CN-ID. The NNSF in the RNC temporarily stores the IMSI and the Global-CN-ID upon reception of the paging message. When the NNSF receives the Initial Direct Transfer message (a paging response with an IMSI), it directly forwards the paging response to 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 from the MSC, the SGSN has to contain the MSC/VLR-ID in the paging message or paging-request message to the RNC.

Processing of the IMSI Paging Message (PS Domain)


According to 3GPP TS 23.236(For details, see Reference Documents), a UE returns an Attach Request message containing the IMSI parameter as a response to the PS IMSI paging. Moreover, the SGSN does not start the timer to wait for the PS IMSI paging response after sending the message. Therefore, the NNSF in the RNC does not need to store the SGSN ID when it receives the paging request. This means that the NAS Node Selection Function in the RAN node selects an available SGSN (for example, based on load balancing) when it receives an Attach Request containing the IMSI parameter.
Issue 02 (2012-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 3-2

WCDMA RAN Iu Flex

4 Load Balancing

4 Load Balancing
Load Balancing (WRFD-021306 Iu Flex Load Distribution Management) describes how the NNSF 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:

There is no CN node configured for the NRI or IMSIROUTE indicated by the UE. The CN node corresponding to an NRI or IMSIROUTE cannot be reached. The CN node corresponding to an NRI or IMSIROUTE is inhibited. No NRI or IMSIROUTE can be derived. The value of the NRI is NULLNRI.

According to the load balancing principle, the RNC records the capability of each CN node which is configured to the NORMAL state and is not in overloaded, and then selects a CN node 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 involved in load re-distribution, 25% of UEs are routed to MSC A, 50% of UEs are routed to MSC B, and 25% of UEs are routed to MSC C, according to the rules of load balancing. Other UEs are routed to the specific CN nodes identified by the NRI.

If a CN node whose available capacity is 0 is identified by a valid NRI and the route parameters of a UE include 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:

Static capability The static capability of the CN node is specified by the AvailCap of the ADD UCNNODE command in the RNC.

Dynamic capability

The dynamic capability reflects the real-time state of the CN node capability. If the parameters CsInfoUpdFlag and PsInfoUpdFlag in the RNC is set to ON, the CN informs the RNC of the dynamic capability and state through the private IEs of the INFORMATION TRANSFER INDICATION message. Therefore, the data between the CN and the RNC is synchronized to realize load balancing. If the RNC does not receive the message about updating the dynamic capability before the CS Information Update Protection Timer or PS Information Update Protection Timer expires, the static capability is preferred.
NOTE

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

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

4-3

WCDMA RAN Iu Flex

5 Flow Control

5 Flow Control
When a CN node is overloaded, the RNC receives the OVERLOAD message from the CN. The RNC then reduces the traffic volume on the CN node. A CN node in the OVERLOAD state is not selected during load balancing. For flow control, the CN short-time flow control timer IgorTmr and the CN long-time flow control timer IntrTmr are configured on the RNC. Note that the IntrTmr has to be greater than the IgorTmr. The procedure that gives some degree of signaling flow control is defined as follows: 1. The overloaded CN node sends the OVERLOAD message to the RNC to initiate the flow control procedure; 2. On the RNC side, if the IgorTmr is not running and an OVERLOAD message or the "Signaling Point Congested" information is received, the traffic volume is reduced in one step. Alternatively, the CN can indicate the number of steps in which the traffic is to be reduced in the Number of Steps IE carried in the OVERLOAD message. At the same time, timers IgorTmr and IntrTmr have to be started. 3. During the period of IgorTmr, all received OVERLOAD messages or "Signaling Point Congested" information is ignored. 4. This step-by-step reduction of the traffic volume is continued until the maximum reduction is obtained at the last step. 5. If the IntrTmr expires and no OVERLOAD message or "Signaling Point Congested" is received, the traffic volume is increased by one step and the IntrTmr is restarted unless the number of steps in which the traffic volume is reduced is back to zero.

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

5-1

WCDMA RAN Iu Flex

6 Load Re-Distribution

6 Load Re-Distribution
There are situations where a network operator needs to remove load from one CN node (for example, 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 to implement load re-distribution:

Load re-distribution based on NullNRI Load re-distribution based on blocking CN node

6.1 Load Re-distribution Based on NullNRI


Two IDs are added to implement the load re-distribution:

NullNRI:
NullNRI

is a special value of the NRI, which indicates that the CN node assigned the NRI is to be offloaded. There is one unique NullNRI in a Public Land Mobile Network (PLMN). The NullNRI can be re-used on different SGSN pool areas, and these areas are not overlapped. The parameter NullNRI is used to set the NullNRI. the RNC finds that the NRI is NullNRI, the RNC uses load balancing to select another CN node that is identified as NORMAL in the pool. Location Area Identity (LAI) or Routing Area Identity (RAI) is used to trigger UEs to perform the Location Update or Route Area Update in the CN node to be offloaded. LAI/RAI is different from the LAI/RAI in the network. So the UE will immediately initiate Location Update or Route Area Update after receiving the Non-broadcast LAI/RAI.

If

Non-broadcast LAI/RAI:
Non-broadcast Non-broadcast

The re-distribution of UE is initiated by the CN node that is to be offloaded. The procedure for load 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 in the 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.
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 new MSC server due to the NullNRI. 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 accept message to reduce the time to trigger the RAU. Shortly after that, the UE sends a new RAU request, which the RNC node will perform load balancing to route the UE to a new SGSN due to the NullNRI.

In

2. In the second phase (PS domain specific), the SGSN requests all UEs trying to set up PDP Contexts to detach and reattach. When they reattach, the SGSN moves them as described in the first phase. 3. The third phase includes scanning the remaining UEs and initiating the movement of them to other CN nodes.

In the PS domain, the UEs are requested to detach and reattach, which will cause them to be moved. In the CS domain, a new TMSI is allocated to the UEs performing the TMSI re-allocation procedure (with NullNRI and non-broadcast LAI) so that an LU is triggered, which will cause them to be moved.

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

6-1

6 Load Re-Distribution

WCDMA RAN Iu Flex

The RNC selects CN node based on the CN state for load re-distribution. The CN state is negotiated between CN and RAN. The state of CN should be specified in the RNC by the parameter CNLoadStatus. 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:

If the CN supports NullNRI:


If If

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

The RNC cannot select a CN node in INHIBITED state for a UE. 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. 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.

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

6.2 Load Re-distribution Based on Blocking CN Node


If the CN does not support NullNRI, the RNC can block the CN node to help redistribute the load 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 RNC by run the following command. MOD UCNNODE: CnOpIndex=1, CNId=2, CNDomainId=CS_DOMAIN,CNLoadStatus=NORMAL, RsvdPara1=RSVDBIT1_BIT1-1; When a CN node is in the BLOCKED state, the UE in the CN node is re-distributed by the RNC to other CN nodes.

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 from this CN node. When the CN is in BLOCKED state and other CNs are in INHIBITED state or in OFFLOAD state or are disconnected or are overloaded, the UEs can still access the CN.

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

6-2

WCDMA RAN Iu Flex

7 Parameters

7 Parameters
Table 7-1 Parameter description Parameter ID NE AvailCap MML Description

Meaning: Capacity of a CN node. This parameter BSC6900 ADD UCNNODE(Mandat indicates the proportion of different CN nodes in the total ory) capacity rather than the actual capacity of each CN node. MOD In the case of IU-FLEX, if one user cannot select a CN UCNNODE(Optiona node according to the NAS Node Selection Function l) (NNSF), the user can select a CN node according to this parameter. GUI Value Range: 0~65535 Actual Value Range: 0~65535000 step:1000 Unit: None Default Value: None

CNLoadStatu BSC6900 ADD Meaning: Status of a CN node. The status needs to be s UCNNODE(Mandat negotiated with the CN and is configured through the ory) MML command. A CN node can be configured with the MOD following status: UCNNODE(Optiona 1. Normal: This value indicates that the UE can access l) the CN node normally. 2. Offload: If the UE carries "NullNRI"("SET UOPERATORCFGPARA") in the Initial Direct transfer message, the UE cannot access the CN node. If the UE carries NRI but not "NullNRI" in the Initial Direct transfer message, the UE can access the CN node. 3. Inhibited: This value indicates that the UE cannot access the CN node normally. GUI Value Range: NORMAL, OFFLOAD, INHIBITED Actual Value Range: NORMAL, OFFLOAD, INHIBITED Unit: None Default Value: None CsInfoUpdFla BSC6900 SET Meaning: Indicating whether the CS domain permits the g UOPERATORCFG CN information to update. PARA(Optional) GUI Value Range: OFF, ON Actual Value Range: OFF, ON Unit: None Default Value: OFF Meaning: Network Resource Identity(NRI) length for CS CSNRILength BSC6900 SET UOPERATORCFG domain. PARA(Mandatory) GUI Value Range: 1~10 Actual Value Range: 1~10 Unit: None Default Value: None

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

7-1

7 Parameters

WCDMA RAN Iu Flex

Parameter ID NE IgorTmr

MML

Description

Meaning: CN flow control timer (short). The OVERLOAD BSC6900 SET UIUTIMERANDNU message received repeatedly in this period will be M(Optional) discarded. GUI Value Range: 5000~30000 Actual Value Range: 5000~30000 Unit: ms Default Value: 20000

ImsiRtMax

BSC6900 ADD UIMSIIDNNSCNID MAP(Mandatory) RMV UIMSIIDNNSCNID MAP(Mandatory) BSC6900 ADD UIMSIIDNNSCNID MAP(Mandatory) RMV UIMSIIDNNSCNID MAP(Mandatory)

Meaning: Maximum of IMSI route parameter in Intra Domain NAS Node Selector(IDNNS). GUI Value Range: 0~999 Actual Value Range: 0~999 Unit: None Default Value: None Meaning: Minimum of IMSI route parameter in Intra Domain NAS Node Selector(IDNNS). GUI Value Range: 0~999 Actual Value Range: 0~999 Unit: None Default Value: None

ImsiRtMin

IntrTmr

Meaning: CN flow control timer (long). If the OVERLOAD BSC6900 SET UIUTIMERANDNU message is not received in this period, the traffic volume M(Optional) will be increased by a degree. GUI Value Range: 15000~120000 Actual Value Range: 15000~120000 Unit: ms Default Value: 60000

NNSfTmr

Meaning: This parameter specifies the value of the NAS BSC6900 SET UOPERATORCFG Node Selection Function (NNSF) timer for CS traffic PARA(Optional) paging. For the IMSI paging of the UE in CS connection mode, on receiving the IMSI paging with the first Global CN ID, the RNC stores the Global CN ID and starts the NNSF protection timer. Once the UE responds to the IMSI paging, the RNC stops the NNSF protection timer. GUI Value Range: 0~60 Actual Value Range: 0~60 Unit: None Default Value: 3

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

7-2

WCDMA RAN Iu Flex

7 Parameters

Parameter ID NE NRI

MML

Description Meaning: Identifying network resources: 1. The NRI numbers of CS domain and PS domain are independent from each other. 2. If multiple pool areas overlap, the NRI uniquely identify all the CN nodes connected to it. 3. A CN node can have multiple NRIs. In one pool area, however, an NRI can only correspond to one CN node. GUI Value Range: 0~1023 Actual Value Range: 0~1023 Unit: None Default Value: None

BSC6900 ADD UNRIGLBCNIDMA P(Mandatory) RMV UNRIGLBCNIDMA P(Mandatory)

NullNRI

Meaning: NullNRI VALUE indicates that the ue assigns BSC6900 SET UOPERATORCFG load to other CN nodes, when NNSF selects other CN PARA(Optional) nodes. GUI Value Range: 0~1023 Actual Value Range: 0~1023 Unit: None Default Value: None

PsInfoUpdFla BSC6900 SET Meaning: Indicating whether the PS domain permits the g UOPERATORCFG CN information to update. PARA(Optional) GUI Value Range: OFF, ON Actual Value Range: OFF, ON Unit: None Default Value: OFF Meaning: Network Resource Identity(NRI) length for PS PSNRILength BSC6900 SET UOPERATORCFG domain. PARA(Mandatory) GUI Value Range: 1~10 Actual Value Range: 1~10 Unit: None Default Value: None

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

7-3

WCDMA RAN Iu Flex

8 Counters

8 Counters
For details, see the BSC6900 UMTS Performance Counter Reference.

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

8-1

WCDMA RAN Iu Flex

9 Glossary

9 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

9-1

WCDMA RAN Iu Flex

10 Reference Documents

10 Reference Documents
[1] 3GPP TS 23.236: Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes [2] BSC6900 UMTS Performance Counter Reference

Issue 02 (2012-06-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

10-1