Professional Documents
Culture Documents
RAN15.0
Issue 01
Date 2013-04-28
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 a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
1 Introduction....................................................................................................................................1
1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
2 Overview.........................................................................................................................................3
2.1 Background.....................................................................................................................................................................4
2.2 Pool Area........................................................................................................................................................................4
2.3 NRI.................................................................................................................................................................................6
2.4 NullNRI..........................................................................................................................................................................6
2.5 Non-broadcast LAI/RAI.................................................................................................................................................6
8 Feature Deployment....................................................................................................................19
8.1 Configuring Iu Flex......................................................................................................................................................19
8.1.1 Prerequisites...............................................................................................................................................................19
8.1.2 Procedure...................................................................................................................................................................19
8.1.3 Example.....................................................................................................................................................................26
8.2 Configuring Iu Flex Load Distribution Management...................................................................................................27
8.2.1 Prerequisites...............................................................................................................................................................27
8.2.2 Procedure...................................................................................................................................................................27
8.2.3 Example.....................................................................................................................................................................35
9 Parameters.....................................................................................................................................37
10 Counters......................................................................................................................................77
11 Glossary.......................................................................................................................................79
12 Reference Documents...............................................................................................................80
1 Introduction
1.1 Scope
This document describes the Iu Flex feature. It covers the overview, technical description, and
parameters related to the feature.
Document Issues
The document issues are as follows:
l 01 (2013-04-28)
l Draft A (2013-01-30)
01 (2013-04-28)
This is the first commercial release of RAN15.0.
Compared with issue Draft A (2013-01-30) of RAN15.0, this issue has no change.
Draft A (2013-01-30)
This is the first draft of the document for RAN15.0.
Compared with issue 01 (2012-07-20) of RAN14.0, this issue incorporates the changes described
in the following table:
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 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. The situation
may be reverse in the suburban area. Therefore, the load of CN nodes for urban and suburban
area is imbalanced.
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:
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 UE
roaming signaling.
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.3 NRI
The Network Resource Identifier (NRI) identifies the CN node that serves a pool area. The NRI
has a flexible length from 0 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.
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/P-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. A routing parameter containing the identity
of IMSI is in range of 0 to 999 (calculated by (IMSI div 10) mod 1000) and is called IMSIROUTE
in this document. The association between IMSIROUTE and the CN nodes in the CN pool area
is configured on the RNC.
2.4 NullNRI
NullNRI is a special value of the NRI, which indicates that the CN node identified by the NRI
is to be offloaded. On receiving a message carrying NullNRI, the RNC starts the IDNNS function
to 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.
NAS Node Selection Function (NNSF) is used to select an appropriate CN Node for a UE.
3.1 Overview
The 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
based on load balancing and routes the message to the selected CN node.
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 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.
In following cases, the RNC selects a CN node based on the load balancing.
Calling and called parties follow the same way of selecting the CN node based on TMSI/P-
TMSI.
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 UIMSIIDNNSCNIDMAP
command.
– 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 between
IMSI and global CN ID received from CN. If fails, the terminated call is processed as an
originated call.
Calling and called parties follow the same way of selecting the CN node based on IMEI.
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.
5. When the MS requests to access the network though the RAN2, the MS provides the IDNNS
to the RAN2, containing the SGSN1 NRI.
6. The RAN2 finds the SGSN1 that serves the MS originally, and then connects the MS to
the 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 CN
node. Therefore, the location update process between the SGSNs is avoided, and the network
load is reduced.
5 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:
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 which
is configured to the NORMAL state and is not in overloaded, and then selects a CN node based
on 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 accessing
in load balancing condition, 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.
NOTE
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.
l Static capability
The static capability of the CN node is specified by the AvailCap(UMTS BSC6900,UMTS
BSC6910) of the ADD UCNNODE command in the RNC.
l Dynamic capability
The dynamic capability reflects the real-time state of the CN node capability.
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
6 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. For details, see the Flow Control Feature
Parameter Description.
A CN node in the OVERLOAD state is not selected during load balancing.
7 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:
l Load re-distribution based on NullNRI
l Load re-distribution based on blocking CN node
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.
8 Feature Deployment
8.1.1 Prerequisites
l 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 license
items and how to activate the license, see License Management Feature Parameter
Description.
l Others
– The MSC and the serving GPRS support node (SGSN) support this feature.
8.1.2 Procedure
NOTE
The CNId of the same PLMN cannot be the same,even the different CN domain. The setting of
CNId must be consistent between the RNC and CN. If CNId on the CN is set to 5, CNId on the
RNC must also be set to 5.
4. Run the RNC MML command ADD UNRIGLBCNIDMAP. In this step, set Cn Operator
Index, CN node ID, and Network resource identity to configure the mapping
relationships between NRI and CN nodes.
5. Optional: Run the RNC MML command ADD UIMSIIDNNSCNIDMAP to configure
the mapping relationships between international mobile subscriber identity (IMSI) ranges
and CN nodes.
After configuring the mapping relationships, the RNC routes the UE whose IMSI is within the
IMSI range to the specified CN. To ensure load balance among CN nodes, the IMSI range
mapped to each CN node must match the capacity of the CN node.
When configuring the feature on the CME, you must configure a single configuration first, and then perform
batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are advised to perform batch modifications before logging out of the parameter setting interface.
----End
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.
CN node ID CNId(UMTS
BSC6900,
UMTS
BSC6910)
CN domain ID CNDomainId
(UMTS
BSC6900,
UMTS
BSC6910)
CNLoadStatus CNLoadStatus
(UMTS
BSC6900,
UMTS
BSC6910)
AvailCap AvailCap
(UMTS
BSC6900,
UMTS
BSC6910)
Switch3GPP25415 Switch3GPP25
CR0125 415CR0125
(UMTS
BSC6900,
UMTS
BSC6910)
CN node ID CNId(UMTS
BSC6900,
UMTS
BSC6910)
CN node ID CNId(UMTS
BSC6900,
UMTS
BSC6910)
Verification Procedure
1. 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.
When configuring the feature on the CME, you must configure a single configuration first, and then perform
batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are advised to perform batch modifications before logging out of the parameter setting interface.
----End
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 on the wizard interface to obtain online help.
CN node ID CNId
(UMTS
BSC69
00,
UMTS
BSC69
10)
SN MO SN MO NE Paramete
r Name
Paramete
r ID
Configur
able in
CME
Batch
Modifica
tion
Center
CN node ID CNId
(UMTS
BSC69
00,
UMTS
BSC69
10)
SN MO SN MO NE Paramete
r Name
Paramete
r ID
Configur
able in
CME
Batch
Modifica
tion
Center
CN node ID CNId
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
SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX,
PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, PSNRILength=5;
//Configuring the first CN node
ADD 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 node
ADD UCNNODE: CnOpIndex=1, CNId=18, CNDomainId=CS_DOMAIN, Dpx=3, CNProtclVer=R6,
8.2.1 Prerequisites
l 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 the
license items and how to activate the license, see License Management Feature Parameter
Description.
l Other Prerequisites
The CN supports dynamic capacity management and load redistribution.
8.2.2 Procedure
Load balancing in dynamic capacity mode takes effect only when the RNC is connected to
Huawei CN and the preceding switches related to Iu Flex are turned on.
When configuring the feature on the CME, you must configure a single configuration first, and then
perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are 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. For instructions on how
to perform the CME single configuration, see CME Single Configuration 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 modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center, press
F1 on the wizard interface to obtain online help.
NOTE
When configuring the feature on the CME, you must configure a single configuration first, and then
perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are 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-4. For instructions on how
to perform the CME single configuration, see CME Single Configuration 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 modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center, press
F1 on the wizard interface to obtain online help.
Feature PsNriCfgMo
Supporting de(UMTS
Mode of PS BSC6900,
Domain UMTS
Set this BSC6910)
parameter to
SUPP_IUFL
EX
CS CsInfoUpdF
Information lag(UMTS
Update BSC6900,
Switch UMTS
Set this BSC6910)
parameter to
ON
PS PsInfoUpdT
Information mr(UMTS
Update BSC6900,
Switch UMTS
Set this BSC6910)
parameter to
ON
NOTE
When configuring the feature on the CME, you must configure a single configuration first, and then
perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are 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-5. For instructions on how
to perform the CME single configuration, see CME Single Configuration 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 modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center, press
F1 on the wizard interface to obtain online help.
NOTE
When configuring the feature on the CME, you must configure a single configuration first, and then
perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are 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-6. For instructions on how
to perform the CME single configuration, see CME Single Configuration 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 modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center, press
F1 on the wizard interface to obtain online help.
Verification Procedure
l Verifying load balancing in static capacity mode
1. 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
When configuring the feature on the CME, you must configure a single configuration first, and then
perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are 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. For instructions on how
to perform the CME single configuration, see CME Single Configuration 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 modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center, press
F1 on the wizard interface to obtain online help.
When configuring the feature on the CME, you must configure a single configuration first, and then
perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are 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-8. For instructions on how
to perform the CME single configuration, see CME Single Configuration 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 modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center, press
F1 on the wizard interface to obtain online help.
NOTE
When configuring the feature on the CME, you must configure a single configuration first, and then
perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are 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-9. For instructions on how
to perform the CME single configuration, see CME Single Configuration 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 modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center, press
F1 on the wizard interface to obtain online help.
PROCESSS PROCESSS
WITCH WITCH
Set this (UMTS
parameter to BSC6900,
IUFLEX_N UMTS
OT_SEL_BL BSC6910)
OCK_SWIT
CH-0
8.2.3 Example
//Activating Iu Flex Load Distribution Management
//Configuring Load balancing in static capacity mode
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 mode
SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX,
PsNriCfgMode=SUPP_IUFLEX, CSNRILength=5, CsInfoUpdFlag=ON, PsInfoUpdFlag=ON;
//Configuring load redistribution based on NullNRI
MOD 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 Node
MOD 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 mode
SET UOPERATORCFGPARA: CnOpIndex=1, CsNriCfgMode=SUPP_IUFLEX,
9 Parameters
the CN node is
unchanged. 2)
REL7_QOS_H
ANDLE_SWIT
CH(Release 7
Qos Parameter
handle switch)
Whether the CN
Node need send
R7 Qos
parameter to
UE. 1:This
switch is turned
on.Element
"Higher bitrates
than 16 Mbps
flag" will added
to the Initial UE
Message by
RNC. 0:This
switch is turned
off.Element
"Higher bitrates
than 16 Mbps
flag" will not
added to the
Initial UE
Message by
RNC.
GUI Value
Range:IUFLEX
_NOT_SEL_BL
OCK_SWITCH
(IUFLEX_NOT
_SEL_BLOCK
_SWITCH),
REL7_QOS_H
ANDLE_SWIT
CH
(REL7_QOS_H
ANDLE_SWIT
CH)
Unit:None
Actual Value
Range:This
parameter is set
to 0 or 1
according to the
related domains.
Default
Value:IUFLEX
_NOT_SEL_BL
OCK_SWITCH
-0,
REL7_QOS_H
ANDLE_SWIT
CH-0
to the Initial UE
Message by
RNC. 0:This
switch is turned
off.Element
"Higher bitrates
than 16 Mbps
flag" will not
added to the
Initial UE
Message by
RNC.
GUI Value
Range:IUFLEX
_NOT_SEL_BL
OCK_SWITCH
(IUFLEX_NOT
_SEL_BLOCK
_SWITCH),
REL7_QOS_H
ANDLE_SWIT
CH
(REL7_QOS_H
ANDLE_SWIT
CH)
Unit:None
Actual Value
Range:This
parameter is set
to 0 or 1
according to the
related domains.
Default
Value:IUFLEX
_NOT_SEL_BL
OCK_SWITCH
-0,
REL7_QOS_H
ANDLE_SWIT
CH-0
four binary
digits.
Therefore, the
value range of
NRI is 0 to 15.
GUI Value
Range:0~1023
Unit:None
Actual Value
Range:0~1023
Default
Value:None
four binary
digits.
Therefore, the
value range of
NRI is 0 to 15.
GUI Value
Range:0~1023
Unit:None
Actual Value
Range:0~1023
Default
Value:None
Actual Value
Range:NORMA
L, OFFLOAD,
INHIBITED
Default
Value:None
Actual Value
Range:NORMA
L, OFFLOAD,
INHIBITED
Default
Value:None
GUI Value
Range:OFF, ON
Unit:None
Actual Value
Range:OFF, ON
Default
Value:None
GUI Value
Range:OFF, ON
Unit:None
Actual Value
Range:OFF, ON
Default
Value:None
10 Counters
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
12 Reference Documents
[1] 3GPP TS 23.236: Intra-domain connection of Radio Access Network (RAN) nodes to
multiple Core Network (CN) nodes