Professional Documents
Culture Documents
Feature Guide
RAN Sharing
RAN Sharing
Version
V1.0
Date
2014/06/28
Author
Pang
Xiufeng
Reviewer
Wang Juntao
Notes
First edition
RAN Sharing
TABLE OF CONTENTS
1
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.1.9
2.1.10
2.1.11
2.2
2.3
Overview ............................................................................................................ 8
Feature Introduction ............................................................................................. 8
ZWF21-30-100 Basic Network Sharing Support ................................................... 9
ZWF21-30-101 RAN Sharing with Dedicated Carrier ......................................... 10
ZWF21-30-102 Shared Network Access Control ................................................ 11
ZWF21-30-121 Operator Specific CE Resource ................................................ 12
ZWF21-30-120 Operator Specific FM/PM/CM.................................................... 12
ZWF21-30-116 Operator Specific Function Control............................................ 13
ZWF21-30-117 Operator QoS Priority ................................................................ 14
ZWF21-30-118 Operator Specific Iub/Iur Transmission ..................................... 15
ZWF21-30-119 Operator Specific RNC Resource .............................................. 16
ZWF21-30-122 Extended GSM Neighboring Cells ............................................. 16
ZWF21-30-200 Multi PLMN Support .................................................................. 16
License Control .................................................................................................. 17
Correlation With Other Features ........................................................................ 17
3
3.1
3.1.1
3.1.2
3.1.3
3.2
3.3
3.3.1
3.3.2
3.3.3
3.4
3.4.1
3.4.2
3.4.3
3.5
3.6
3.7
3.8
3.9
3.10
RAN Sharing
4
4.1
4.2
4.3
4.4
4.5
4.6
Parameters....................................................................................................... 48
ZWF21-30-100 Basic Network Sharing Support Parameter List ......................... 48
ZWF21-30-101 RAN Sharing with Dedicated Carrier Parameters List................ 50
ZWF21-30-102 Shared Network Access Control Parameters List ...................... 51
ZWF21-30-118 Operator Specific Iub/Iur Transmission Parameters List ............ 55
ZWF21-30-121 Operator Specific CE Resource Parameters List ....................... 56
ZWF21-30-119 Operator Specific RNC Resource Parameters List .................... 58
5
5.1
5.1.1
5.1.2
5.2
6
6.1
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
6.2.7
6.2.8
6.2.9
6.2.10
6.2.11
6.3
6.3.1
6.3.2
6.3.3
6.3.4
6.3.5
6.3.6
6.3.7
6.3.8
6.3.9
6.3.10
6.3.11
6.4
6.4.1
RAN Sharing
6.4.2
6.4.3
6.4.4
6.4.5
6.4.6
6.4.7
6.4.8
6.4.9
6.4.10
6.4.11
6.5
Abbreviation .................................................................................................... 95
Reference Document....................................................................................... 96
RAN Sharing
FIGURES
Figure 2-1 Network Architecture of MOCN .......................................................................... 9
Figure 2-2 Network Architecture of Gateway Core Network Sharing ................................... 9
Figure 2-3 Independent Carrier Network Sharing ...............................................................11
Figure 2-4 Four-Operator-Shared Iub Interface ..................................................................15
Figure 3-1 Flow of Information Transfer .............................................................................23
Figure 3-2 Structure of the Shared Network Information IE..............................................23
Figure 3-3 Structure of the SNA Access Information IE......................................................24
Figure 3-4 Scenario of Sharing 3G network and 2G network .............................................25
Figure 3-5 Example of Baseband Resources Shared in the Method of Splitting During
Congestion ...........................................................................................................................29
Figure 6-1 Parameters on the UMTS Logical Function Configuration Tab..........................63
Figure 6-2 Parameters on the Local MangedElement Plmn Information Tab .....................63
Figure 6-3 Parameters on the UMTS Logical Function Configuration Tab..........................64
Figure 6-4 Parameters on the PLMN Group Tab................................................................64
Figure 6-5 Parameters on the Used LocalPlmnGroup Tab .................................................65
Figure 6-6 Parameters on the External RNC Function Tab ................................................65
Figure 6-7 Parameters on the External UTRAN Cell Tab ...................................................66
Figure 6-8 Parameters on the External GSM Cell Tab .......................................................67
Figure 6-9 Parameters on the UMTS logical Function Configuration Tab ...........................67
Figure 6-10 Parameters on the External UTRAN Cell Tab .................................................68
Figure 6-11 Parameters on the External GSM Cell Tab .....................................................68
Figure 6-12 The parameters in LTE Handover Support Sharing Switch ...........................69
Figure 6-13 Configuring the Minimal percent of CE can be used by the PLMN Parameter .70
Figure 6-14 Configuring the CE Share Switch for Carrier Sharing Parameter ....................71
Figure 6-15 Configuring the CE Share Switch for Carrier Sharing Parameter ....................71
Figure 6-16 Parameters on the PLMN Configuration of Path Group Tab............................72
Figure 6-17 Parameters on the Service IP Configuration Tab ............................................73
Figure 6-18 Parameters on the UDP Port Configuration Tab .............................................73
RAN Sharing
TABLES
Table 2-1 License Control List ...........................................................................................17
Table 3-1 Example of the Main PLMN-id and Other PLMN-Id Mapping List .......................19
Table 3-2 Example of 3G Cell PLMN-Id Label ...................................................................25
Table 3-3 Example of GSM Neighbor Cell PLMN-Id Label .................................................25
Table 3-4 Example of LTE Neighbor Cell PLMN-Id Label ..................................................27
Table 3-5 Features Allowed for Per Operator Activation ....................................................43
Table 3-6 Basic Priority Mapping of Operator A .................................................................44
Table 3-7 Basic Priority Mapping of Operator B .................................................................45
Table 3-8 RNC Hardware Resource Allowed to be Purchased Per Operator .....................46
Table 4-1 ZWF21-30-100 Basic Network Sharing Support Parameter List .........................48
Table 4-2 ZWF21-30-101 RAN Sharing with Dedicated Carrier Parameter List .................50
Table 5-1 ZWF21-30-100 Basic Network Sharing Support measurement type...................59
Table 5-2 Alarm List for V3 ................................................................................................61
Table 5-3 Alarm List for V4 ................................................................................................61
Table 6-1 Feature Validation Procedure - Basic Network Sharing Support ........................80
Table 6-2 Feature Validation Procedure - RAN Sharing with Dedicated Carrier .................80
Table 6-3 Feature Validation Procedure.............................................................................82
Table 6-4 Feature Validation Procedure - Operator Specific CE Resource ........................83
Table 6-5 Feature Validation Procedure - Operator Specific FM/PM/CM ...........................84
RAN Sharing
Table 6-6 Feature Validation Procedure - Operator Specific Function Control ...................86
Table 6-7 Feature Validation Procedure - Operator QoS Priority .......................................86
Table 6-8 Feature Validation Procedure - Operator Specific Iub Transmission ..................87
Table 6-9 Feature Validation Procedure - Operator Specific Iur Transmission ...................88
Table 6-10 Feature Validation Procedure - Operator Specific RNC Resource ...................89
Table 6-11 Feature Validation Procedure - Extended GSM Neighboring Cells ...................90
Table 6-12 Feature Validation Procedure - Multi PLMN Support ........................................91
Table 6-13 Feature Deactivation Procedure - Basic Network Sharing Support ..................92
Table 6-14 Feature Deactivation Procedure - Operator Specific CE Resource ..................93
Table 6-15 Feature Deactivation Procedure - Operator Specific RNC Resource................94
RAN Sharing
Feature Attribute
RNC Version: [ZXWR RNC V3.13.10.15/ZXUR 9000 V4.13.10.15]
Node B Version: [ZXSDR V4.13.10.20]
Attribute: [Optional]
Involved NEs:
NE Name
Related or Not
MS/UE
BTS/Node B
BSC/RNC
iTC
MSC
MGW
SGSN
GGSN
HLR
Special Requirement
Overview
2.1
Feature Introduction
Due to the long period and high cost for establishing a 3G network, it is hard for a single
operator to establish a 3G network with complete coverage during a short period, and the
business combination between operators requires network sharing. To satisfy the above
requirements, the 3GPP develops the network sharing technology. This technology can
be used for operators to share the access network section that is the largest part in the
network investment to reduce the investment of the 3G network, enhance the layout
speed, and integrate the access network resources of different operators. Network
sharing is particularly important for operators at the early stage.
RAN Sharing
2.1.1
Figure 2-1
CN
Operator A
CN
Operator B
CN
Operator C
Iu
RNC
Node B
Node B
In this network architecture, operators have different core network devices, and all the
core network devices are connected to the same RNC, sharing the RAN radio resources.
Figure 2-2
CN
Operator A
CN
Operator B
Shared
MSC/SGSN
Shared
MSC/SGSN
CN
Operator C
Shared
MSC/SGSN
Iu
RNC
RNC
RNC
RAN Sharing
In this network architecture, operators use the same core network devices (MGW,
MSC-server, and SGSN) as the gateway to connect independent HLR, GGSN, GMSC,
GSGW, and systems (such as a billing system) of different operators.
In the MOCN scenario, PLMNs are handled as follows:
ZTE RAN devices configure different PLMN codes for multiple operators with shared
networks. In the MOCN network architecture, the RNC differentiates subscribers of
different operators, and routes the signaling connections and services of subscribers of
different operators to the core network devices of each operator. The RNC routes
messages in accordance with PLMN information indicated by the UE or UEs access
carrier. If that is not enough for routing, the RNC randomly selects a core network node
for the UE. If the core network node rejects the users request, the RNC retries other core
network nodes until it finds the core network node that the user is authorized to access.
When the UTRAN is shared, it can also be connected to one or more operators core
networks through the Iu Flex interface.
With this feature during UTRAN network sharing, all UEs transparently access the
shared network, and enjoy the services provided by their own operators. If a UE can only
obtain the common PLMN code through the system message, it is advised to use the
NITZ function (3GPP TS22.042) in the core network to identify the logo of its own
operator. The network informs the UE of the operator PLMN ID after a successful
location update, and the corresponding logo is displayed on the UE.
2.1.2
10
RAN Sharing
required. Carriers of different operators can also be deployed in different Node Bs. They
can be connected to the same RNC through the lub interface, sharing the RNC devices
such as cabinets, power supply, and control plane and user plane processing boards.
Figure 2-3
Operator one
Operator two
Shared RNC
Shared Node B
Frequency one
Frequency one
MNC
one
Frequency two
Frequency two
MNC
two
2.1.3
11
RAN Sharing
The area where users can obtain services is configured by the core network. The RNC
can learn the SNACs of each LA under the RNC through the core network, and the SNAs
that each user is authorized to access. In a cross-lur handover, the SRNC can learn the
SNAs of the cells under the DRNC through the lur interface. The RNC reserves the
SNAC that each user is allowed to access, and performs filtering in the construction of
the intra-frequency, inter-frequency, and inter-system neighboring cell list. Only the cell
with the authorized SNA can be configured as the new neighboring cell. Then the cell can
be added into the cell list in the measurement control message, ensuring that the UE
performs handovers only in the authorized cells.
2.1.4
2.1.5
12
RAN Sharing
Independent CM
Different operators can independently configure the parameters related to the cell
that belongs to only one operator. For example, different operators own dedicated
SW (software) functions, and features differentiation can be embodied in the
cell-level configuration.
Independent PM
For those counters related to cells, performance statistics can be done based on
operators. The operator-dedicated results of performance statistics can only be
accessed by the owner PM manager, for example, operators can differentiate the
counters related to the networks KPI from different operators, independently
manage their own measurement tasks and measurement objects.
Independent FM
The fault management function can differentiate the cell-level alarms for different
operators. The alarm that corresponds to only one operator can be only accessed
by its owner, so only the owner FM manager can process the alarm.
2.1.6
13
RAN Sharing
Most of those functions can be configured in an RNC level based on the PLMN and
can be applied to different subscribers belonging to different operators. Still few
RNC-level optional functions only support the same configuration to all operators
and cannot be purchased separately.
2.1.7
14
RAN Sharing
2.1.8
Figure 2-4
ANI+Path+PLMN1
ANI+Path1+PLMN2
Node B
RNC
ANI+Path1+PLMN3
ANI+Path1+PLMN4
ANI+Path+PLMN_MIX
15
RAN Sharing
2.1.9
2.1.10
2.1.11
16
RAN Sharing
2.2
License Control
Table 2-1
Feature ID
ZWF21-30-100
Feature Name
License
Configured
Control Item
NE
WCDMA
Support
Basic RAN
Sharing
Unit
RNC
RNC
RNC
RNC
RNC
RNC
RNC
RNC
Support
ZWF21-30-101
WCDMA
Dedicated Carrier
Basic RAN
Sharing
Support
ZWF21-30-102
Shared Networks
WCDMA
Access Control
Basic RAN
Sharing
Support
ZWF21-30-200
WCDMA
Basic RAN
Sharing
Support
2.3
17
RAN Sharing
Technical Description
3.1
3.1.1
18
RAN Sharing
3.1.1.1
User Identification
If an operator has multiple PLMN-Ids, the multi-home PLMN-Id in the IMSI of his
subscriber may exist. In this case, the RAN should indentify a users home operator with
its IMSI. The URncFunction.defPlmnInGwcnInd parameter is set to enable or disable
such identification.
Each operator should select a PLMN-Id as the main PLMN-Id from his multi-PLMN-Id. A
list of mapping between the main PLMN-Id and the other PLMN-Id for each operator
should be pre-configured. Table 3-1 shows an example. When the RAN gets an IMSI
from the core network, it extracts the home PLMN-Id and checks the table to identify the
operator that the user belongs to.
Table 3-1
Other PLMN-Id
PLMN A1
PLMN A2
PLMN A3
PLMN A
..
..
PLMN Ax
PLMN B1
PLMN B2
PLMN B
PLMN By
PLMN C1
PLMN C2
PLMN C
PLMN Cz
At most 200 PLMN-Ids are allowed to be configured and at most four main PLMN-Ids are
supported in the mapping list.
19
RAN Sharing
The
other
PLMN-Ids
PlmnGroup.AliasMCC
and
PlmnGroup.AliasMNCBcdCodeLen
The
configured
with
the
parameters
PlmnGroup.AliasMNC.
UPlmnSpecFunction.refLocalPlmnGroup
PlmnGroup.AliasMNC
are
can
parameter
number
of
the
associate
indicates
other
one
the
PLMN-Ids
Each
PlmnGroup.
coding
is
The
size
of
indicated
by
PlmnGroup.AliasPlmnNum.
3.1.2
3.1.2.1
Message Routing
In MOCN mode, the RNC is connected to multiple operators core networks. So, the RNC
has to determine which operator a UE should be connected to. This procedure is called
routing.
When a RAN is shared in dedicated carriers, one cell only belongs to one operator. A UE
will select its home PLMN after it starts up. After an RRC is established, the UE will send
an Initial Direct Transfer message. The RNC selects the operator of the cell in which the
UE resides. In other words, the Initial UE Message will be routed to the operator to
establish a signaling and data connection to the operator for the UE.
In shared carriers, for message routing, refer to Section 3.1.2 in the ZTE UMTS RAN
Sharing with Shared Carrier Feature Guide.
3.1.2.2
Paging
In MOCN mode, if a paging message from the core network carries the Paging Area IE,
the RNC pages terminals that are in IDLE state in the specified LAI/RAI area. If the
paging message does not carry the Paging Area IE but carries the Global CN-ID IE
instead, the RNC pages terminals in IDLE state in cells that belong to the indicated core
network.
20
RAN Sharing
If neither Paging Area nor Global CN-ID is carried, the RNC will get the Origination
Point Code (OPC) from the SCCP data packets that carry paging messages in the
transmission network layer. Every OPC corresponds to an NE (such as an RNC, MSC, or
SGSN) connected to the RNC. The RNC finds out the core network that has sent the
paging message through the OPC. Then the RNC pages terminals that are in IDLE state
in the cells belonging to the operator of the core network.
Paging terminals in URA_PCH state is similar to paging terminals in IDLE state. Except
that, the SRNC pages terminals in cells in the DRNC through the Iur interface. The URA
of these DRNC cells must be the URA that terminals reside in.
3.1.2.3
3.1.3
3.2
21
RAN Sharing
of each operator sharing the RAN should be configured to the RAN. Then it is possible
for the RAN to allocate system resources based on the operator and calculate
performance for an individual operator. Also it is possible for individual operators users
to select the RAN with the broadcasted operators PLMN-Id.
The PLMN of ZTE RAN is configured with
parameter.
PlmnGroup.
Each
The
the UPlmnSpecFunction.refLocalPlmnGroup
UPlmnSpecFunction.refLocalPlmnGroup
PLMN-Id
is
configured
with
the
can
associate
one
PLMNGroup.MCC
and
with
one
group
UExternalRncFunction.MNC,
and
of
one
UExternalRncFunction.MCC
or
more
groups
and
of
3.3
3.3.1
Based on SNAC
The SNAC, which is valid in one PLMN, is allocated by the operator. One SNAC includes
one or multiple LAs. The value of SNAC ranges from 0 to 65,535. An SNAC, together
with a PLMN-Id, constitutes a Shared Network Area Identifier (SNA-Id), which uniquely
identifies an area among all operators PLMNs.
The mapping between SNAC and LAC is delivered to the RNC in an RANAP procedure
by the core network. See Figure 3-1. The core network carries Shared Network
22
RAN Sharing
Figure 3-1
CN
RNC
Information Transfer
Information Transfer Confirmation
Figure 3-2
SNAC
SNAC
Operator n
PLMN ID
LAC
SNAC
SNAC
When a ZTE RNC acts as the DRNC, it carries SNA Information in a Radio Link Setup
Response message (an RANAP message) to provide the SRNC with the mapping
between the DRNC neighboring cells and the SNAC. When a ZTE RNC acts as the
SRNC, if the DRNC does not support SNA Information on the Iur interface, the SNAC of
inter-RNC
neighboring
cells
allows
to
be
configured
through
the
neighboring
cell,
the
SNA-Id
is
obtained.
The
23
RAN Sharing
GSM
neighbor
cell,
the
SNAC
is
configured
through
the
Figure 3-3
IMSI
Because every cell is assigned with a LAC, when the RAN initiates intra-frequency,
inter-frequency, or inter-system measurements, it knows which neighbor cell is
accessible for the subscriber by checking whether the PLMN-Id + LAC are the allowed
SNA-Id. Only the neighboring cells that belong to the allowed SNA-Id are included in the
Measurement Control message. In this way, the access restriction for subscribers in
dedicated state is performed.
Access control over the SNAC-based shared network requires the cooperation of the
core network. If the core network does not support access control, IMSI-based handover
can be used. For details, refer to the ZTE RAN UMTS IMSI based Handover Feature
Guide.
3.3.2
24
RAN Sharing
these operators are allowed to access the cell. Actually, the operator list is a PLMN-Id
label. Each PLMN-Id in the PLMN-Id label represents an operator. There are three
operators sharing a 3G network: Operator A and Operator C share the GSM network,
and Operator B has its own 2G network, see Figure 3-4.
Figure 3-4
For 3G cell U1, the PLMN-Id label is shown in Table 3-4. It means that cell U1 is allowed
to be accessed by three operators users.
Table 3-2
Cell U1
PLMN B
PLMN C
Cell U1s GSM neighbors are cell G1, G2, G3, B1, B2, and B3. The PLMN-Ids of these
GSM cells are shown in Table 3-5. Cell G1, G2, and G3 are allowed to be accessed by
the users of Operator A and Operator C. And Cell B1, B2, and B3 are only allowed to be
accessed by the users of Operator B.
Table 3-3
GSM Neighbors
PLMN ID Label
PLMN A
Cell G1
PLMN C
PLMN A
Cell G2
PLMN C
PLMN A
Cell G3
PLMN C
Cell B1
PLMN B
25
RAN Sharing
GSM Neighbors
PLMN ID Label
Cell B2
PLMN B
Cell B3
PLMN B
When the RNC gets an IMSI from the core network for a user in RRC dedicated state, the
RAN identifies his home operator through the method described in 3.1.1.1 User
Identification if GWCN is used, or through the method described in 3.1.2.1 Message
Routing if MOCN is used. When it is time to trigger intra-frequency, inter-frequency, or
inter-system measurements, the RAN only provides neighbor cells labeled with the home
operators PLMN-Id in the Measurement Control message.
The PLMN-Id labels of 3G cells belonging to the neighbor RNC are configured through
the
parameters
UExternalUtranCellFDD.MCC,
UExternalUtranCellFDD.MNC,
The
UExternalUtranCellFDD.SharingMNCLength
indicate
the
coding
size
of
UExternalGsmCell.MNC.
The
3.3.3
26
RAN Sharing
Table 3-4
LTE Neighbors
PLMN ID Label
PLMN A
Cell G1
PLMN C
PLMN A
Cell G2
PLMN C
PLMN A
Cell G3
PLMN C
Cell B1
PLMN B
Cell B2
PLMN B
Cell B3
PLMN B
When the RNC gets an IMSI from the core network for a user in RRC dedicated state, the
RAN identifies his home operator through the method described in 3.1.1.1 User
Identification if GWCN is used, or through the method described in 3.1.2.1 Message
Routing if MOCN is used. When it is time to trigger inter-system measurements, the RAN
only provides neighbor cells labeled with the home operators PLMN-Id in the
Measurement Control message.
The PLMN-Id labels of LTE neighbor cells are configured through the parameters
UExternalEUtranCellFDD.sharingMCC,
UExternalEUtranCellFDD.sharingMNC,
UExternalEUtranCellFDD.sharingMNCLength,
UExternalEUtranCellTDD.sharingMCC,
UExternalEUtranCellTDD.sharingMNC,
and
UExternalEUtranCellTDD.sharingMNCLength.
The
of
UExternalEUtranCellFDD.sharingMNC.
The
3.4
3.4.1
27
RAN Sharing
Pooling
The operators share all or some of the baseband processing resources. When the
RAN receives baseband processing resource requests during call admission, if
there are free baseband processing resources in the sharing part, the RAN
allocates baseband processing resources for the call. Call admission will be
rejected until all shared baseband processing resources are used up. For CE
Admission Control, refer to the ZTE UMTS Admission Control Feature Guide and
the ZTE UMTS HSUPA Introduction Guide.
Reservation
A certain percentage of baseband processing resources are reserved for an
operator. No matter how many resources other operators use, the RAN always
guarantees at least a certain percentage of the baseband processing resources for
the operator. The ratio is configured through the ULogicalIubLink.MinCEPercent
parameter for an operator of shared carrier and through the
ULogicalIubLink.CePercent parameter of dedicated carrier sharing. For CE
Admission Control, refer to 3.4.2 CE-based Admission Control in PLMN.
28
RAN Sharing
of users with the lowest QoS priority within the selected operator. The released
baseband processing resources are allocated to the new call.
Figure 3-5
Congestion
In the three methods to partition baseband processing resources, pooling and splitting
during congestion cannot be activated at the same time. The UIubLink.CEShareMode
parameter
determines
which one is
used between
The
29
RAN Sharing
For admission control of baseband processing resources during RAN sharing, the
algorithm should be based on the number of CEs that can be used by an operator. For
details, refer to the ZTE UMTS Admission Control Feature Guide.
ZTE RAN does not support co-existence of dedicated carrier sharing and shared carrier
sharing in one Node B.
3.4.2
If
the
UIubLink.CeShareSwitch
parameter
is
set
to
1:
On
and
the
If
the
UIubLink.CeShareSwitch
parameter
is
set
to
1:
On
and
the
is
less
than
the
CE
credit
in
the
local
cell
group,
and
the
is
less
than
the
CE
credit
in
the
local
cell
group,
and
the
30
RAN Sharing
If the number of the valid data groups in the extension IE in AUDIT RESPONSE> Local
Cell Group Information is greater than or equal to 2:
If
the
UIubLink.CeShareSwitch
parameter
is
set
to
1:
On
and
the
If
the
UIubLink.CeShareSwitch
parameter
is
set
to
1:
On
and
the
If the UIubLink.CeShareSwitch parameter is set to 0: Off, and the first bit of data[1]
of the extension IE in AUDIT RESPONSE > Local Cell Group Information is 0, the
CE is not shared.
CE share mode 1 means that the minimal CE percent should be guaranteed only
when the CE is in congestion state, and the minimal CE percent is only used when CE
31
RAN Sharing
congestion occurred in a local cell or local cell group (for more information about it,
refer to Section 3.4.3). The following sections describe CE share mode 0.
3.4.2.1
3.4.2.1.1
Principles for Reporting the CE Credit When the Cells in Different PLMNs Share
the CE Resources
For the software version that allows different PLMNs to share the CE resources, both
Audit Response and Resource Status Indication of the Node B contain two IEs: Local
Cell Information and Local Cell Group Information. The CE Credit in Audit Response
indicates the minimum number of CE resources that should be guaranteed for the
operator (PLMN) in the cell group, and the CE Credit in Resource Status Indication
indicates the maximum number of CE resources that can be used in the cell group
3.4.2.1.2
Check whether Audit Response or Resource Status Indication contains Local Cell
Group Information. If not, the admission decision is not made (the CE resources in a
certain PLMN in the cell group are not restricted).
2.
Check whether Local Cell Group Information in Audit Response or Resource Status
Indication contains the UL Capacity Credit IE. If yes, the uplink uses its independent
CE resources, and the total quantity is UL Capacity Credit. If not, the uplink and
downlink share the CE resources, and the total quantity is DL Or Global Capacity
Credit. If neither UL Capacity Credit nor DL Or Global Capacity Credit is available,
the admission decision is not made (the CE resources in a certain PLMN in the cell
group are not restricted).
3.
32
RAN Sharing
Decision of UL CE restriction:
max (Number of CEs occupied by the uplink channels, UL Capacity Credit reported by the cell)
Cumulative sum
of other PLMNs
}
If the formula is true, the subsequent admission decision is made. Otherwise,
the admission request is directly rejected.
Decision of DL CE restriction:
ULTotalCost+DLTotalCost+N*ULCost2+ULCost1+N*DLCost2+DLCost1<=
{DL or Global Capacity Credit reported in the cell group
If the formula is true, the subsequent admission decision is made. Otherwise, the
admission request is directly rejected.
Where,
33
RAN Sharing
If the RL in the admission request is not the first RL in the corresponding RLS
(handover user), the resource consumption cost2 of the RL is taken into account. If
the RL in the admission request is the first RL in the corresponding RLS (new user),
the resource consumption cost1 of the RLS is also taken into account. The resource
consumption is derived from Dedicated Channels Capacity Consumption Law or
E-DCH Capacity Consumption Law in Local Cell Information. Its value is
determined by the spreading factor.
When the PLMN of the UE is changed, the CE cost in the old PLMN will be released
and CE admission control will be decided in the new PLMN. If the new PLMN is
limited by CE, the UE will be denied to access the new PLMN.
34
RAN Sharing
3.4.2.2
3.4.2.2.1
Principles for Reporting the CE Credit and for Configuring the Operators Available
CE Proportion When CE Resources Are Shared
When the CE is shared in the Shared Carriers Scene, the Node B cannot obtain the
PLMN information. Therefore, the total CE Credit in the resource pool is reported in Local
Cell Group.
The minimum available CE proportion is configured in the RNC for each operator
(PLMN), indicating the minimum proportion of available CE resources that the operator
can use in each Local Cell Group. The RNC supports up to four PLMNs that share one
RAN.
3.4.2.2.2
If Audit Response or Resource Status Indication does not contain Local Cell Group
Information, the admission decision is not made (the CE resources in a certain
PLMN in the cell group are not restricted).
35
RAN Sharing
If not, the uplink and downlink share the CE resources, and the total quantity is
DL Or Global Capacity Credit.
Total number of available downlink and uplink CE resources in a certain PLMN
in the cell group = (Total number of downlink and uplink CE resources in the
cell group)
3.4.2.2.3
36
RAN Sharing
2.
Where,
Cost1 refers to the CE resources consumed by the reported RLS in the cell. It uses
the maximum value of Cost1 from Local cell information in RLS.
Cost2 refers to the CE resources consumed by the reported RL in the cell. It uses
the Cost2 from the local cell information of the RL.
Notes:
If the currently established RL is the first link in the corresponding radio link set, the
consumed CE resources include Cost1 and Cost2, and are calculated based on the
37
RAN Sharing
consumption rule reported by the Node B. If the currently established RL is not the
first link (handover user) in the corresponding RLS, the consumed CE resources
only include Cost2. The resource consumption is derived from Dedicated Channels
Capacity Consumption Rule or E-DCH Capacity Consumption Rule in Local Cell
Information. Its value is determined by the spreading factor.
When the PLMN of the UE is changed, the CE cost in the old PLMN will be released
and the CE admission control will be decided in the new PLMN. If the new PLMN is
limited by CE, the UE will be denied to access the new PLMN.
3.4.3
38
RAN Sharing
percent is larger than the minimum percent configured for the PLMN shall be released to
guarantee user A to access (Mode 1).
Because the modes used for sharing CE resources are different, the congestion control
strategies are different. The differences reside on determining the range of target users
for downgrading or service pre-emption. The specific target users within the range are
selected in an ascending order, from the lowest priority to the highest priority.
They are described respectively in the following sections.
3.4.3.1
If only local cell CE resource congestion occurs, the subscribers in the local cell
whose priorities are lower than the priorities of originator subscribers should be
downgraded.
If local cell group CE congestion occurs (including both local cell group CE
congestion and PLMN CE congestion in a local cell group), or only PLMN CE
congestion in a local cell group occurs, the subscribers whose PLMNs are the same
as the subscribers triggering downgrading or the subscribers who belong to the
other PLMNs whose CE percent occupied are larger than the minimum percent of
CE configured (MinCE) should be downgraded, and the RNC selects the
subscribers whose priorities are lower than the priorities of originator subscribers
out of the above subscribers to be downgraded.
When local cell CE resource congestion occurs, and meanwhile, local cell group CE
congestion occurs (including both local cell group CE congestion and PLMN CE
congestion in a local cell group) or the PLMN CE congestion in a local cell group
occurs (the local cell group CE is not congested), the subscribers in the local cell
whose PLMNs are the same as the subscribers triggering downgrading or the
subscribers in the local cell who belong to the other PLMNs whose CE percent
occupied are larger than the minimum percent of CE configured (MinCE) should be
downgraded, and the RNC selects the subscribers whose priorities are lower than
the priorities of originator subscribers out of the above subscribers to be
39
RAN Sharing
downgraded.
When local cell group CE congestion or PLMN CE congestion in a local cell group
together with other resource congestion occur (for example, the cause of the
congestion is DL code resource, RTWP, TCP, number of HSDPA/HUSPA users, or
HS-DSCH data throughput), the subscribers in the local cell whose PLMNs are the
same as the subscribers triggering downgrading or the subscribers in the local cell
who belong to the other PLMNs whose CE percent occupied are larger than the
minimum percent of CE configured (MinCE) should be downgraded, and the RNC
selects the subscribers whose priorities are lower than the priorities of originator
subscribers out of the above subscribers to be downgraded.
2.
In Mode 1, there are two kinds of congestion: local cell CE resource congestion and local
cell group CE congestion, and they are independent each other. If local cell CE resource
congestion occurs, the subscribers in the local cell should be downgraded. If local cell
group CE congestion occurs, the subscribers in the local cell group should be
downgraded. The same strategies on selecting subscribers are for the two kinds of
congestion.
Specific strategies are as follows:
If the CE occupancy of the PLMN is larger than or equal to the minimum percent of
CE occupancy (MinCE) configured for the PLMN, the subscribers whose PLMNs
are the same as the subscriber triggering downgrading or the subscribers who
belong to the other PLMNs whose CE percent occupied are larger than the
minimum percent of CE configured (MinCE) should be downgraded, and the RNC
selects the subscribers whose priorities are lower than the priorities of originator
40
RAN Sharing
3.4.3.2
If only local cell CE resource congestion occurs, the subscribers in the local cell
whose priorities are lower than the priorities of originator subscribers should be
selected for pre-emption.
If local cell group CE congestion occurs (both local cell group CE congestion and
PLMN CE congestion in a local cell group occur), or only PLMN CE congestion in a
local cell group occurs, the subscribers whose PLMNs are the same as the
subscriber triggering pre-emption or the subscribers who belong to the other
PLMNs whose CE percent occupied are larger than (MinCE+CEneed) should be
selected for pre-emption, and the RNC selects the subscribers whose priorities are
lower than the priorities of originator subscribers out of the above subscribers for
pre-emption. Where, MinCE is the minimum percent of CE configured.
If local cell CE resource congestion occurs, and meanwhile, local cell group CE
congestion occurs (including both local cell group CE congestion and PLMN CE
congestion in a local cell group) or PLMN CE congestion in a local cell group occurs
(the local cell group CE is not congested), the subscribers in the local cell whose
PLMNs are the same as the subscriber triggering pre-emption or the subscribers in
the local cell who belong to the other PLMNs whose CE percent occupied are larger
than (MinCE+CEneed) should be selected for pre-emption, and the RNC selects
the subscribers whose priorities are lower than the priorities of originator
subscribers out of the above subscribers for preemption. Where, MinCE is the
minimum percent of CE configured.
41
RAN Sharing
HS-DSCH data throughput congestion), the subscribers in the local cell whose
PLMN is the same as the subscribers triggering pre-emption or the subscribers in
the local cell who belong to the other PLMNs whose CE percent occupied are larger
than (MinCE+CEneed) should be selected for pre-emption, and the RNC selects
the subscribers whose priorities are lower than the priorities of originator
subscribers out of the above subscribers for pre-emption. Where, MinCE is the
minimum percent of CE configured.
2.
If the CE occupancy of the current PLMN is less than the minimum percent of
CE configured (MinCE), the subscribers who belong to the other PLMNs whose CE
percent occupied are larger than (MinCE+CEneed) should be selected for
pre-emption, ignoring the priority difference between the target subscribers and the
originator subscribers. If no subscribers who belong to other PLMNs are selected,
the subscribers whose PLMN is the same as the subscriber triggering pre-emption
and whose priorities are lower than the originator subscriber should be selected for
pre-emption. Where, MinCE is the minimum percent of CE configured.
If the CE occupancy of the current PLMN is larger than or equal to the minimum
percent of CE configured (MinCE), the subscribers whose PLMNs are the same as
the subscriber triggering pre-emption or the subscribers who belong to the other
PLMNs whose CE percent occupied are larger than (MinCE+CEneed) should be
selected for pre-emption, and the RNC selects the subscribers whose priorities are
lower than the priorities of originator subscribers out of the above subscribers for
pre-emption. Where, MinCE is the minimum percent of CE configured.
42
RAN Sharing
3.5
Table 3-5
Feature ID
Feature Name
Active/Deactiv
e
ZWF21-02-020
Yes
ZWF21-02-021
Yes
ZWF21-02-022
Yes
ZWF21-03-022
Yes
ZWF21-04-005
Yes
ZWF21-05-020
Yes
ZWF21-05-022
Service-Based Handover
Yes
ZWF21-05-024
Yes
ZWF21-10-001
Yes
ZWF21-10-002
AGPS
Yes
ZWF21-30-026
Yes
ZWF23-01-042
Yes
ZWF23-05-003
Yes
ZWF24-01-011
Yes
ZWF25-02-011
Yes
ZWF25-05-002
Yes
ZWF21-03-023
Yes
43
RAN Sharing
PLMN based
Feature ID
Active/Deactiv
Feature Name
3.6
ZWF21-03-024
Yes
ZWF21-03-025
NACC
Yes
ZWF21-03-026
Yes
ZWF26-02-005
CS over HSPA
Yes
ZWF21-01-025
Yes
ZWF21-01-026
Yes
ZWF21-03-110
Yes
ZWF21-03-120
SR-VCC
Yes
ZWF27-01-100
Yes
ZWF27-03-002
Yes
ZWF21-05-026
Yes
ZWF27-02-002
Yes
ZWF25-01-033
Yes
ZWF21-30-119
Yes
Table 3-6
ARPSeg
SIP
C_Voice
C_Video
I (THP)
15
610
1115
44
RAN Sharing
15
14
14
11
15
13
13
10
15
12
12
10
Table 3-7
ARPSeg
SIP
C_Voice
C_Video
15
14
14
15
13
15
12
I (THP)
15
610
1115
10
13
10
12
10
The ZTE RAN RRM policy is based on the mapped priority. Users having a higher priority
can preferentially use resources. Users having a lower priority might be forced to release
all or part of occupied resources during congestion. It means that the mapped priorities
of different operators are considered together. Take operator A and operator B mentioned
above for example, because the uplink interference and downlink admission threshold
differentiate basic priority configurations, the admission threshold of operator As
ARPSeg=1 streaming services is the one based on priority 11, while the admission
threshold of operator B is the one based on priority 10.
3.7
Dynamic sharing
Transmission bandwidths are shared among operators. Unused transmission
bandwidths are allocated to a new request of a call, until all transmission
bandwidths are occupied.
Static reservation
45
RAN Sharing
3.8
Table 3-8
Step Length
Unit
CS service capacity
Erlang
PS service capacity
Mbps
The CS traffic capacity or PS data throughput used by a user depends on the operator
who provides service for the user.
If
the
IU
PS
capacity and IU
CS
capacity are
purchased
independently
should
configure
the
upper
threshold
of
the
CS
flow
the
PS
flow
(UIuFlowCtrl.IuPSHighThres)
to
min(IuPSLowThres*120%,
46
RAN Sharing
the
number
exceeds
the
upper
threshold
of
the
CS
flow
the
lower
threshold
of
IU
PS
and
CS
traffic
mix
control
raised.
When
the
traffic
capacity
exceeds
the
upper
threshold
3.9
47
RAN Sharing
measurement.
3.10
Parameters
4.1
Parameter
Name
GUI Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
Network
(GWCN), 0:GWCN
Multi-Operator
URncFunct
ion.shared
NetMode
Network
Shared
Core
(MOCN),
Multi-PLMN.
Both
and
radio
networks
are
1:MOCN
2:
0xFF:
No
Multi
Plmn
N/A
Networ
Shared kplanni
0xFF: No
Networ ng
Shared
Network
48
RAN Sharing
Recom
Parameter
Name
GUI Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
belongs
to
dedicated
Networ
N/A
N/A
N/A
ng
nGroup
User-Defined
URncFunct
ion.defPlm
nInGwcnIn
d
PLMN
Selection
In
case
of
GWCN
.AliasPlmn
Num
Number
Mobile
Alias
MNC
BCD
Code
Length
PlmnGroup Alias
Mobile
Default PLMN
Indicator
Networ
N/A
N/A
kplanni
ng
user-defined
Alias PLMN
PlmnGroup Alias
PLMN selection.
Indicator
PlmnGroup
supports
support
kplanni
Networ
0-50
N/A
kplanni
ng
Networ
N/A
N/A
kplanni
ng
Alias
MNC
BCD
Code
Length
Networ
2,3
N/A
kplanni
ng
Networ
N/A
N/A
kplanni
ng
Networ
0/1
N/A
kplanni
ng
49
RAN Sharing
4.2
Parameter
Name
GUI Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
UPlmnSpe
cFunction.r
efLocalPlm
nGroup
Used
N/A
N/A
N/A
0..999
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
UExternal
RncFunctio
n.mcc
uniquely identifies
MCC
is
allocated
uniformly
and
internationally.
UExternal
RncFunctio
n.mnc
UExternal
RncFunctio
n.sharingM
NC
UExternal
RncFunctio
n.sharingM
CC
Mobile
Network Code
Sharing
Mobile
Sharing
Mobile
50
RAN Sharing
4.3
Parameter
GUI Name
Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
UExternal Shared
GsmCell.s Network Area
nacList
Code
Code
(SNAC)
that
the
0..65535 N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
UExternal Shared
GsmCell.s Network Area
nacNum
Code Number
neighboring
cell
belongs to.
0..
MAX_NU
M_SNAC N/A
_PER_G
SMCEL
Shared
Network Area
Code
Code
(SNAC)
that
the
0..65535 N/A
UExternal
UtranCellF
DD.
snacNum
Shared
Network Area
Code Number
Target
URncFunct
ion.
ShaNetTar
CelStra
the
neighboring
cell
belongs to.
Judgment
Strategy
MAX_NU
M_SNAC N/A
_PER_G
SMCEL
Cell
0:Judgme
This parameter indicates nt Based
Access/Hand access/handover
to
Shared network.
Network
0..
Informati
on
51
RAN Sharing
Recom
Parameter
Name
GUI Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
1:Judgme
nt Based
on
Selected
PLMN
UExternal
GsmCell.
Mobile
N/A
N/A
N/A
2..3
N/A
N/A
0..999
N/A
N/A
N/A
UExternal Sharing
GsmCell.s Mobile
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
mnc
UExternal
GsmCell.m
ncLength
Network Code
MNC
GsmCell.m
cc
of
the
UExternal
BCD
uniquely identifies
MCC
is
allocated
uniformly
and
internationally.
MNC
BCD
of
the
Length
digits
(09),
parameter
and
indicates
2..3
this
the
number of digits.
UExternal Sharing
GsmCell.s Mobile
Mobile
Network Code
52
RAN Sharing
Recom
Parameter
Name
GUI Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
UExternal
UtranCellF MNC
BCD
of
the
2..3
ngth
UExternal Sharing
UtranCellF Mobile
DD.mcc
UExternal
UtranCellF
DD.sharing
MNC
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Mobile
UExternal
UtranCellF
DD.sharing
MNCLengt
MNC
BCD
of
UMTS
the
cell.
2..3
parameter
indicates
the
number of digits.
UExternal
UtranCellF
DD.sharing
MCC
Sharing
Mobile
UExternalE
UtranCellF
DD.sharing
MCC
Sharing
Mobile
Country Code
identifies
the
UExternalE
UtranCellF
DD.sharing
MNC
Sharing
Mobile
0..999
53
RAN Sharing
Recom
Parameter
Name
GUI Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
DD.sharing
MNC
MNCLengt
BCD
of
the
indicates
the
number of digits.
This parameter indicates
UExternalE
UtranCellT
DD.sharing
MCC
Sharing
Mobile
Country Code
identifies
the
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
UExternalE
UtranCellT
DD.sharing
MNC
Sharing
Mobile
0..999
UExternalE
UtranCellT
DD.sharing
MNCLengt
MNC
BCD
of
the
2, 3
parameter
indicates
the
number of digits.
The parameter indicates
URncFunct
ion.ShareE
xLteSwch
Sharing
on
Switch
handover to LTE in a
selected
PLMN
for 1: On
N/A
0: Off
N/A
shared network.
54
RAN Sharing
4.4
Parameter
Name
GUI Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
applies
resources
ServiceIp.r
efLocalPlm
nGroup
Used
Local
Plmn Group
multiple
to
radio
shared
by
operators.
This
N/A
N/A
N/A
N/A
1: Yes N/A
the
list.
If
all
the
parameter
is
not
configured.
This parameter indicates
whether the service IP
address supports all the
ServiceIp.I
sSupportAl
lPlmn
Whether
IP
address
support
PLMNs
all
operators. It applies to
radio resources shared by
multiple operators. If this
parameter is set to support
all
the
operators,
0: No
1: Yes
the
55
RAN Sharing
4.5
Parameter
Name
GUI Name
Parameter Description
Value
Unit
Range
Default mende
Value
d
Value
carrier
sharing.
percentage
of
occupied
Minimal
percent of CE
can be used
by the PLMN
operators
by
at
any
other
time. (0100)
step %
N/A
N/A
are
not
congestion,
minimum
the
percentage
of
N/A
56
RAN Sharing
Recom
Parameter
GUI Name
Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
eShareSwi Switch
tch
Carrier
carrier
sharing.
If
this
Sharing
sharing.
If
this
PLMN
cannot
based
on
the
First-Arrive-First-Get rule.
This parameter indicates 0:
the shared mode of CE Minimal
multiple CE
operators. If this parameter Percenta
resources
for
for
no
the guarante
for
matter ed
UIubLink.C of
N/A
N/A
should
guaranteed
for
be Minimal
the CE
CE
percentage guarante
for
57
RAN Sharing
Recom
Parameter
Name
GUI Name
Value
Parameter Description
Range
Unit
Default mende
Value
d
Value
rate
can
improved
when
resources
are
be when CE
CE Resource
not is
congested.
congeste
d
4.6
Parameter
Name
GUI Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
UIuFlowCtr
l.IuFlowCtrl
Type
IU traffic flow
control type
UIuFlowCtr IU
PS
low
l.IuPSLow control
Thres
PS
high
l.IuCSLow control
Thres
threshold
IU
PS
low
IU
CS
N/A
50000 N/A
control
0..20000
0000,429 Kbps
60000 N/A
4967295
low
threshold
CS
UIuFlowCtr IU CS High IU
threshold
l.IuCSHigh control
high
threshold
threshold
CS
4967295
l.IuPSHigh control
UIuFlowCtr IU
N/A
0..10000
threshold
UIuFlowCtr IU
Thres
control
0..10000
00,42949 Erl
500
N/A
600
N/A
67295
High
control 0..20000
00,42949
Erl
58
RAN Sharing
Recom
Parameter
Name
GUI Name
Parameter Description
Value
Range
Unit
Default mende
Value
d
Value
Thres
threshold
UIuFlowCtr
l.IuMixLow
Thres
IU PS and CS
traffic
control
threshold
UIuFlowCtr
l.IuMixHigh
Thres
67295
IU PS and CS
traffic
control
threshold
0..10000
0000,429 Kbps
50000 N/A
4967295
0..20000
0000,429 Kbps
60000 N/A
4967295
5.1
Related Counters
5.1.1
the ZXUR 9000 UMTS (V3.13.10.15) Radio Network Controller Performance Counter Reference.
Table 5-1
Measurement Type ID
31001
31002
31003
31004
31192
31377
59
RAN Sharing
31085
31330
31336
31337
31338
31339
31340
31341
31342
31343
31344
31345
31346
31347
31348
31349
31366
31350
31351
31352
31353
31354
Statistics of
31355
31356
31357
31358
31359
31360
31361
31362
Statistics of
31380
Statistics of
31407
time
60
RAN Sharing
5.1.2
Counter ID
C313300001
C313300002
C313300003
C313300004
C313300005
C313300006
C313300007
5.2
Counter Name
Related Alarms
Table 5-2
Alarm Code
Alarm Name
198105022
198105023
198105024
Table 5-3
Alarm Code
Alarm Name
199105022
199105023
199105024
61
RAN Sharing
Engineering Guide
6.1
Application Scenario
The sharing network technology provides services to multiple operators at the same time
through a physical network. This technology can be used for operators to share the
access network, which is the largest part in network investment to reduce 3G network
investment, enhance the layout speed, and to integrate the access network resources of
different operators, which is particularly important for operators at the early stage. Typical
application scenarios are as follows:
In Gateway Core Network (GWCN) mode, not only RNCs and/or Node Bs are
shared by multiple operators, but also some network elements of the core network
are shared.
In MOCN mode, RNCs and/or Node Bs are shared by multiple operators, whereas
the core networks are not shared.
GWCN mode and MOCN mode determine the CN RANAP message routing mode.
But no matter which mode is used, RNC resources such as CE, transport resources,
carrier frequency, and QoS are shared in accordance with the requirements of
operators.
6.2
6.2.1
62
RAN Sharing
Figure 6-1
In the configuration resource tree, select Modify Area > Managed Element > UMTS
logical Function Configuration > Link Configuration, and double-click Local
ManagedElement Plmn Information. Set Used LocalPlmnGroup. See Figure 6-2.
Figure 6-2
In the configuration resource tree, select Modify Area > Managed Element, and
double-click UMTS logical Function Configuration. Set User-Defined PLMN
Selection In case of GWCN support Indicator. See Figure 6-3.
63
RAN Sharing
Figure 6-3
In the configuration resource tree, select Modify Area > Managed Element > Plmn
Group Configuration, and double-click PLMN Group. Set Number of Alias PLMN,
Alias Mobile Country Code, Alias MNC BCD Code Length, Alias Mobile Network
Code, and Default PLMN Indicator. See Figure 6-4.
Figure 6-4
6.2.2
64
RAN Sharing
Figure 6-5
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical
Function
Configuration
>
External
Resource
Configuration,
and
double-click External RNC Function. Set the related parameters. See Figure 6-6.
Figure 6-6
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > External Resource Configuration > External RNC
65
RAN Sharing
Function, and double-click External UTRAN Cell. Set the related parameters. See
Figure 6-7.
Figure 6-7
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical
Function
Configuration
>
External
Resource
Configuration,
and
double-click External GSM Cell. Set the related parameters. See Figure 6-8.
66
RAN Sharing
Figure 6-8
6.2.3
Figure 6-9
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > External Resource Configuration > External RNC
Function, and double-click External UTRAN Cell. Set the related parameters. See
Figure 6-10.
67
RAN Sharing
Figure 6-10
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical
Function
Configuration
>
External
Resource
Configuration,
and
double-click External GSM Cell. Set the related parameters. See Figure 6-11.
Figure 6-11
68
RAN Sharing
Figure 6-12
6.2.4
69
RAN Sharing
Figure 6-13
Parameter
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Link Configuration, and double-click Iub Link. Set
CE Share Switch for Carrier Sharing and Share Mode of CE Resource for
Multi-Operators. See Figure 6-14 and Figure 6-15.
70
RAN Sharing
6.2.5
Figure 6-14
Figure 6-15
6.2.6
6.2.7
71
RAN Sharing
6.2.8
Figure 6-16
In the configuration resource tree, select Modify Area > Managed Element > Transport
Network > User Plane Service Configuration, and double-click Service IP
Configuration. Set Whether IP address support all PLMNs and Used Local Plmn
Group. See Figure 6-17.
72
RAN Sharing
Figure 6-17
In the configuration resource tree, select Modify Area > Managed Element > System
Global Configuration > System Function, and double-click UDP Port Configuration.
Set System Mode, Plmn Index, Application Type of IP address, and Multiple of UDP
port. See Figure 6-18.
Figure 6-18
73
RAN Sharing
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Link Configuration > Local Managed Element
PLMN Information > Logical Iub Link, and double-click Iub Transmission Path. Set
Used PLMN Configuration of Path Group. See Figure 6-19.
Figure 6-19
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Link Configuration > Local Managed Element
PLMN Information > Logical MGW Link, and double-click MGW Transmission Path.
Set Used PLMN Configuration of Path Group. See Figure 6-20.
74
RAN Sharing
Figure 6-20
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Link Configuration > Adjacent ManagedElement
PLMN Information > Logical Iur Link, and double-click Iur Transmission Path. Set
Used PLMN Configuration of Path Group. See Figure 6-21.
Figure 6-21
75
RAN Sharing
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Link Configuration > Local Managed Element
PLMN Information > Logical Iups Link Group > Logical Iups Link, and double-click
Iups Transmission Path. Set Used PLMN Configuration of Path Group. See Figure
6-22.
Figure 6-22
6.2.9
76
RAN Sharing
Figure 6-23
6.2.10
6.2.11
77
RAN Sharing
Figure 6-24
In the configuration resource tree, select Modify Area > Managed Element > PLMN
Group, and double-click Local PLMN Group. Set Used PLMN Group. See Figure 6-25.
Figure 6-25
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Link Configuration > UMTS Logical Function
Configuration > Link Configuration, and double-click Adjacent ManagedElement
PLMN Information. Set Used PLMN Group. See Figure 6-26.
78
RAN Sharing
Figure 6-26
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Link Configuration, and double-click Local
ManagedElement Plmn Information. Set Used LocalPlmnGroup. See Figure 6-27.
Figure 6-27
79
RAN Sharing
6.3
6.3.1
Test Item
Prerequisit
e
Steps
Expected
Result
6.3.2
Test Item
80
RAN Sharing
Test Item
2.
3.
Prerequisit
e
4.
5.
1.
2.
3.
4.
5.
6.
1.
Expected
2.
Result
3.
Steps
message.
6.3.3
6.3.3.1
Based on SNAC
Table 6-1
Test Item
81
RAN Sharing
Test Item
2.
3.
Preconditio
4.
ns
5.
6.
1.
UE1 makes a voice call to PSTN/UE2 and move the UE1 from
cell1 to cell2 to trigger handover to cell2.
Test Steps
2.
UE1 makes a voice call to PSTN/UE2 and move the UE1 from
cell1 to cell3 to trigger handover to cell3.
1.
Anticipative
authorized to UE1;
Result
2.
6.3.3.2
Table 6-3
Test Item
2.
Preconditio
3.
ns
4.
1.
2.
Test Steps
82
RAN Sharing
Test Item
Anticipative
Result
2.
6.3.4
Test Item
83
RAN Sharing
Test Item
Expected
Result
resources.
Test Item
84
RAN Sharing
Test Item
1.
2.
3.
Prerequisit
4.
5.
6.
1.
2.
3.
4.
5.
6.
Configure the query granularity and the check the time in the
Query Time page.
Steps
7.
8.
9.
Select View > Fault Management, and click the sub menu.
10. Select Query > View History Alarms. The History Alarm Query
Conditions window is displayed.
11. Click the Quick Search button at the top left corner of the window.
The View History Alarms dialog box is displayed.
12. Set the query conditions (by different PLMN) in the Query History
Alarm window.
13. After the query condition is set, click OK. The query results are
returned in View History Alarms.
Expected
Result
85
RAN Sharing
6.3.6
Test Item
2.
3.
Prerequisit
e
4.
Expected
2. In step2, encryption algorithm UEA1 and UEA0 are used for UE2.
Result
6.3.7
Test Item
86
RAN Sharing
Test Item
2.
Prerequisit
e
3.
4.
5.
1.
2.
Expected
1.
Result
2.
In step2, UE2 fails to set up the voice call due to DL TCP limit.
Steps
6.3.8
Test Item
2.
Prerequisit
e
4.
87
RAN Sharing
Test Item
Expected
Result
Table 6-9
Test Item
Prerequisit
and Cell 3 and Cell 2 are adjacent cells over the Iur interface with
different coverage.
5. RNC2 acts as an SRNC, which has two Iur transmission paths:
PATH 3 for PLMN1 and PATH4 for PLMN2. The bandwidth of the
two paths are different.
6. The timer of Relocation Delay for PS Service is large enough to
hold the UE on the Iur interface.
7. The UE resides in cell3 in idle mode, and background
MBR2048kbps/2048kbps (DL/UL) is subscribed in HLR at first.
88
RAN Sharing
Test Item
Steps
5. Use the UE to activate a PS call in Cell 3.
6. Move the UE from Cell3 to Cell2 to trigger event 2D and activate
compressed mode.
7. Move the UE further to Cell2 to trigger event 2A.
8. End the PS call after 30 seconds.
1. In step1-3, the UE sets up the PS call successfully and occupies the
transmission bandwidth of PATH3.
Expected
Result
6.3.9
Test Item
1.
2.
Prerequisit
3.
4.
Only three pairs of CS12.2k services are allowed for PLMN A, and
other resources are reserved for PLMN B.
5.
6.
89
RAN Sharing
Test Item
Steps
1.
2.
3.
4.
5.
1.
2.
3.
4.
Expected
5.
Result
6.
7.
6.3.10
Test Item
2.
Prerequisit
3.
4.
5.
UE1 and UE2 reside in the cell1 in idle mode. UE1 supports UMTS
and GSM.
90
RAN Sharing
Test Item
Steps
Expected
Result
6.3.11
91
RAN Sharing
Test Item
2.
3.
Prerequisit
4.
5.
6.
1.
Steps
2.
Expected
1.
2.
Result
3.
6.4
6.4.1
GUI Name
URncFunction.
Shared Network
sharedNetMode
Mode
Default
Value
0xFF:
Shared
Deactivation Value
No
0xFF
Network
92
RAN Sharing
6.4.2
6.4.3
6.4.4
MinCEPercent[DBS_RR_MAX_NU
M_SHARED_PLMN_PER_CELL
CeShareSwitch
URncFunction. ShareExLteSwch
6.4.5
GUI Name
Default
Deactivat
Value
ion Value
Minimal percent of CE
can be used by the
0:Off
0:Off
PLMN
CE Share Switch for
Carrier Sharing
LTE Handover Support
Sharing Switch
6.4.6
6.4.7
6.4.8
93
RAN Sharing
6.4.9
UIuFlowCtrl. IuFlowCtrlType
UIuFlowCtrl. IuPSLowThres
UIuFlowCtrl. IuPSHighThres
UIuFlowCtrl. IuCSLowThres
UIuFlowCtrl. IuCSHighThres
6.4.10
GUI Name
IU traffic flow
control type
IU PS low control
threshold
IU PS high control
threshold
IU CS low control
threshold
IU CS High control
threshold
Default
Deactivation
Value
Value
50000
60000
500
600
0
ALL PLMNs:
50000
ALL PLMNs:
60000
ALL PLMNs:
500
ALL PLMNs:
600
6.4.11
6.5
RNC resources, such as CE, transport, carrier frequency, and QoS, are shared in
accordance with the different sharing requirements of the operators.
None
94
RAN Sharing
Abbreviation
Abbreviation
Full Name
rd
3GPP
BSC
CE
Channel Element
CN
Core Network
CS
Circuit Switch
DL
Down Link
MS/UE
PS
Packet Switch
RNC
UL
Up Link
UTRAN
WCDMA
BPA
IDNNS
IMEI
IMSI
LA
Location Area
MCC
MNC
MOCN
MS
Mobile Station
MSC
NNSF
NRI
PLMN
PPA
RA
Routing Area
RAN
SGSN
TMSI
95
RAN Sharing
DRNC
GWCN
MOCN
OPC
SCCP
SNA
SNAC
SRNC
Reference Document
[1]ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Radio Parameter
Reference
[2]ZXWR RNC (V3.13.10.15) Radio Network Controller Radio Parameter Reference
[3]ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Radio Counter Reference
[4]ZXWR RNC (V3.13.10.15) Radio Network Controller Radio Counter Reference
96