Training Silder UMTS RAN Sharing (RAN17.1)

Security Level:
11/25/16
Training on UMTS
RAN Sharing
Professional Service Team
HUAWEI TECHNOLOGIES CO., LTD.
Huawei Confidential
www.huawei.com
Introduction to RAN Sharing

RAN Sharing Feature Design
MOCN Feature Design
Feature Combination Policy Design
RAN sharing & MOCN Reconstruction Guideline
Commercial Sites of RAN Sharing
Huawei Confidential
Page 3

Resource
allocation design
Networking design
Customer
requirements
Interface design
Traffic model and

network scale
License Management
design
Transmission
network information
OM design
Operator and CN
information
Feature combination
policy design
RAN hardware
information
The payment
approves
NE
Guideline and Tool

Support
Implementation
Version
RNC
RAN13 or later version
Node B
RAN13 or later version
Network sharing feature service

Huawei Confidential
Page 4

MOCN Feature Design
Huawei Confidential
Page 5
RAN Sharing Network Structure
Operator B NMS
Operator A NMS
Operator A
CN
Operator B
CN
Iu interface
Itf-N
iManagerTM
M2000
RNC
Iub interface
Shared Master OSS
4 operators
32 MSC servers
32 SGSN
32 MGW
Macro
Node B
F1: Operator A
F2: Operator B
15 Neighboring RNC
4 CBC
RRU
Shared RAN
Huawei Confidential
Page 6
Dedicated
Carrier Mode
Typical Networking Design
Networking scenario 1
Co-existence of full coverage by shared and non-shared RANs
Operator A and operator B share RAN devices on the global network. This networking can quickly deploy
networks and save network construction costs in the preliminary network construction phase when the
user scale is small.
Huawei Confidential
Page 7
Co-existence of shared network and 2G network
One or both of two operators have GSM networks in certain areas. To use the GSM network resources, the operator(s)
will require that the new RAN sharing network be interoperable with the existing GSM network(s).
In this scenario, by using the neighboring cell configuration of the shared RNC and BSSs, when users of operator A
and/or operator B move to the existing GSM serving area from the serving area of the shared network, the service
continuity can be guaranteed.
Huawei Confidential
Page 8
Co-existence of shared network and 2G network
One kind of special scene needs to pay attention, the operator uses RAN Sharing on 3G, roaming to
realize to share on 2G. The operator B GSM network allows A to roam, such need configure the neighbor
relations between the B GSM Cell with A sharing Cell.
Huawei Confidential
Page 9
Co-existence of full coverage and partial coverage by different operators
Operator A and operator B share the RAN system. Operator A provides full network coverage. Operator B
provides coverage in certain areas. In this case, operator B may need to use network resources of operator A in
areas where operator B does not provide coverage.
Huawei Confidential
Page 10
Co-existence of Iu-Flex and RAN sharing
Operator A and operator B share RANs. Operator A and/or operator B can implement Iu-Flex networking in
one or both the CS and PS domains of the CN to improve network reliability.
Huawei Confidential
Page 11
Co-existence of multiple operators
Operator A and operator B share the RAN system. Operator C and operator B enter into a roaming
agreement that allows users of the other party to use its network resources.
Huawei Confidential
Page 12
Iu/Iur Interface Design

Iur interface design
Iu interface design
Constraints
For different operators, the Iu
Constraints
interface are shared among operators.
interface is independent.
Design method
Iu interface design in RAN sharing
The transmission resources at the Iur
Design method
Iur interface design in RAN sharing
(the same as that in non-RAN
(the same as that in non-RAN sharing
sharing scenario)
scenario)
The Iu interface design is the same
Total Iur transmission bandwidth =
bewteen
(Iur transmission bandwidth required
The operators can activate or de-
by operator i)
excitation Iu-Flex alone, Iu-Flex
Interface transmission capability design
configuration in RAN sharing is
Interface networking design
similar with non-sharing RNC
QoS design
Interface transmission capability

design
Interface networking design
QoS design
Huawei Confidential
Page 13
Iub Interface Design

Control Plane and Management
Plane Design
Constraints
A shared RNC supports shared and

non-shared NodeBs.
The constraints on sharing of the
transmission resources are shown
as follows:
The NCP, CCPs, ALCAP link, and

OM channel are shared among
operators. That is, one NodeB has
only one set of control plane and
OM configuration data.
User Plane Design
When uses the ATM/IP double protocol

stack, two operators may use the double
protocol stack or use an protocol stack.
When Iub user plane configure special

purpose, each operator user plane
transmission resources may also be
completely independent physical links
The user plane resources of each operator
share completely, does not differentiate the
virtual link or the logical link, transmission
efficiency to be highest in this situation
Huawei Confidential
Transmission resources can be shared

among operators or separated.
When Iub user plane configure special
purpose, the user planes transmission
resources can configure different virtual
port(VP) or logical port(LP), each VP or LP
only correspond an operator.
Page 14
OM Design
Mangers of
Operator A
A s cell
level data
Instance
set 1
Mangers
Operator
of
B
shared
data
Bs cell
level data
EntryPointIRP Agent
CMIRP Agent
PMIRP Agent
FMIRP
FMIRP Agent
Agent Supplier
Notification
Topology Configuration
Fault
Itf - N
PMIRP Agent
FMIRP Agent
Notification Supplier
Instance
set 2
Performance Security System Software License

iManager TM M2000
Node B RNC
Shared
RAN
Node B RNC
NonNon-Shared
Shared
RAN
The shared master OSS is operated by an operator (normally the primary operator) or a third-party company to
implement network management and OM functions. The shared master OSS provide services to each operator
by using the Itf-N northbound interface. Operators can maintain dedicated or shared data by using the Itf-N
interface, and perform functions such as cell-level fault management (FM), performance management (PM), and
configuration management (CM).
By using the shared master OSS and Itf-N northbound interface, dedicated data of an operator can be obtained
by only the corresponding operator and shared data can be obtained by all operators.
The shared master OSS shields the impact of different operators on the RAN. Therefore, the OM design is the
same as that in non-shared RNC scenarios.
Huawei Confidential
Page 15
License Management Design
RNC License
The total maximum user number of CS of all operators cannot exceed the maximum user number of CS
specified in the purchased RNC license. The same is true for the maximum throughput of PS. That is, the
following license constraint is met:
(LIC_i) <= LIC_Purchase
NodeB License
Private group: defines the dedicated resources and functions of a certain operator.
Common group: defines resources and functions shared by all operators. The common group is optional.
License groups meet the following constraint (taking two operators for example):
(LIC_NodeBi_A + LIC_NodeBi_B + LIC_NodeBi_A&B) <= LIC_Purchase
Resource control item including the CE quantity, HSDPA code, frequency and PA output, may configure
differently on M2000 according to operator.
The NodeB functional control item to the NodeB level, the functional control item on M2000 providing shares
by all operators, cannot configure independently.
Huawei Confidential
Page 16

MOCN Feature Design
Huawei Confidential
Page 17
MOCN Network Structure

Core Node
A
MSC
Server SGSN
MGW
Operator A NMS
Core Node
B
MGW
MSC
Server
SGSN
Operator B NMS
Iu interface
iManagerTM M2000
RNC
Shared Master OSS
Iub interface
A maximum of 4 operators can be supported.
NodeB
All RAN resources, including carrier and

baseband resources are shared.
...
Shared RAN
Huawei Confidential
Page 18
Shared Carrier
Mode
The Whole network MOCN
All carriers of entire network share among the operators. Under this scene, only
involves the mobility management between MOCN cell and MOCN cell.
Huawei Confidential
Page 19
MOCN Private cell network
Part carrier sharing , other part carrier does not share in the same RNC. HUAWEI MOCN solution support private cell and
sharing cell coexistence, this very suitable this situation that among the operators some carriers sharing or only share
some regions.
If under the NodeB both has the MOCN cell and private cell, then the NodeB attribution configure MOCN, more than 1
operator is the MOCN cell, equal to 1 operator is the private cell. When the cell establishes that will configure the operator.
Huawei Confidential
Page 20
MOCN RNC and special RNC coexist
Operator A and B deploy independent 3G network in some regional, and deploy the MOCN
network in other regional.
Sharing MOCN RNC connects special RNC A and RNC B through Iur interface, and configures
the neighboring area relations. Therefore, when operator A and B in same sharing cell UE from
sharing region migration to non-sharing region, enable A operator's UE handover to the A
neighboring cell and B operator's UE handover to the B neighboring cell.
Huawei Confidential
Page 21
MOCN RNC and 2G network coexist
operator A and operator B respectively had deployed a GSM network, and deploys MOCN
3G network. MOCN network requirement and GSM network interoperability, therefore has
configured BSS A and BSS B neighboring cell on MOCN RNC. when operator A and B UE
between UMTS cell and neighboring GSM cell moving can guarantee the service
continuity.
Huawei Confidential
Page 22
MOCN RNC and 2G network coexist
Has the intra-system operator handover switch and inter-system operator handover switch in the RNC, if
opens the switch, when RNC is issuing the measurement control to UE, will not filter this operator's
neighboring list again specially, issues all neighboring list normally, the user will possibly be handover to
other operators cell. At present it doesnt use intra-system operator handover switch in the present
network, but has network used inter-system operator handover switch.
The operators use MOCN on 3G and roaming on 2G. Operator A GSM is according to different LAC to
configure in some regions whether permits user roaming of other operators.
Huawei Confidential
Page 23
Iu-Flex and MOCN coexist
Operator A and operator B shares RAN. In order to enhance the reliability of network,
operator A uses Iu-Flex in CS and PS domain, but operator B only uses Iu-Flex in the
PS domain.
Huawei Confidential
Page 24
Multi-operator coexist
Operator A and operator B shares RAN, but operator C and operator B signs the
roaming agreement, this agreement permits operator B and operator C all user shared
network resources.
Huawei Confidential
Page 25
Interface Design
Iu interface
Iu interface design is the same as that

in the RAN sharing service design.
Interface design
Iur interface design is the

same as that in the RAN
sharing service design.
Iur interface
Iub interface
RAN14.0: The RAN SHARING scene

supports Iub transmission separation,
but the MOCN scene does not support
it.
RAN15.0 The MOCN scene
supports the Iub service plane
transmission resources independently
(including IP or ATM transmission);
The largest difference with Iub interface design in RAN sharing

service design is as follows: In RAN sharing scenarios, Iub
transmission separation is supported; in MOCN scenarios, Iub
transmission separation is not supported.
Huawei Confidential
Page 26
OM design & License management design

OM design
License management design
Does not support many operators to have

one set of M2000 to manage a shared
network respectively.
The MOCN network shares FM (fault
management) and CM (configuration
management). PM (performance
management) may the part independence,
each operator can be possible to gain the
independent RNC level statistics, but
shared the cell level performance statistics.
Each operator modify the cell parameter in
sharing cell can affect other operators,
therefore should by jointly manage the
maintenance team or the host operator
team is responsible.
Huawei Confidential
MOCN RAN, only has RNC License and NodeB

License.
RNC License contained the functional control
item and the resource control item, resources
License may configure independently, the
functional control item is shared by various
operators. First, RNC License may the whole
activate and does not differentiate the operator,
then according to configure resources by each
operator.
In the NodeB side, the functional control item is
shared by all operators, cannot establish
independently, namely various operators use the
same feature.
RAN15.0 introduces the MOCN independent CE
resources allocation feature, M2000 assigns
each NodeB level uplink and downlink CE
license group according to the operator, the CE
license group of each NodeB assignment may
not be different or may be the same, including
private group and sharing group.
Page 27
Load Balancing Design

MOCN RNC broadcast multiple PLMN identities in MIB on BCCH
Common PLMN
OperA CN
OperB CN
Iu Interface
MOCN RNC
Uu Interface
Master Information Block

{
PLMN identity
Multiple PLMN List
{
MIB PLMN identity
Multiple PLMNs
{
OperA PLMN
OperB PLMN
...
}
}
...
}
UE
Non-supporting UE
PLMN list
If 'MIB PLMN Identity' = TRUE
Common PLMN
Broadcasting in MIB
Indicates if Common
PLMN is one of the
Multiple PLMNs
Supporting UE
OperA PLMN
OperB PLMN
Multiple operators may provide services to a certain UE (for example, a roaming UE). In this case, a
load balancing mechanism is needed to balance the load and ensure network sharing fairness among
operators.
Generally, the Default mode is used. The default operator is the primary operator.
MOCN network support proportionate route roaming of user loading balance based on RAN13 version,
RNC may judge non-supporting UE whether have the roaming relations with many operators, realizes
proportionate division roaming user, guarantees operator's income to the roaming user.
Huawei Confidential
Page 28
Resource Allocation Design

R15 MOCN Independent CE Resource Allocation feature
strategy
RAN15.0 introduced the MOCN independent CE resource allocation feature, supports assignment CE
License resource according to the operator by the NodeB level, if the customer just has this requirement, it
can deploy this feature.
Before the deployment , we need to audit the traffic of each operator to prevent the assignment the CE
number is less than the traffic demand
a)If among the operators the independent request to resources is high, then the sharing group may not
assign CE, only assigns CE in the private group; And NodeB total CE utility will drop.
b)If the operator considered independence and utility of resources, then may increase the assignment of
CE in the sharing group, more CE in the sharing group , then the utility is higher, the independence is
lower.
c)Sum of various operators' private group CE and sharing group CE cannot pass the purchase the CE
license.
Huawei Confidential
Page 29

MOCN Feature Design
Huawei Confidential
Page 30

Feature
Connected to
Multiple CNs or Not
CNs Belong to the Same

Operator or Not
Radio Frequency
Spectrum Shared or Not
Iu-Flex
Yes
Yes
Yes
MOCN
Yes
No
Yes
RAN Sharing
Yes
No
No
Iu-Flex + RAN
Sharing
Iu-Flex + MOCN
Not supporting co-existence of

MOCN and MRCN in a same RNC
Huawei Confidential
Page 31
NodeB Sharing Type Design
NodeB Sharing Mode
Basic RNC Information

Configuration
NodeB Configuration
RNC Supporting Network Sharing

or Not
Shared or
Not
Resource
Management Mode
MOCN NodeB
Yes
Yes
Shared
RAN Sharing NodeB
Yes
Yes
Shared or dedicated
Yes or No
No
Dedicated NodeB
A dedicated NodeB and a shared NodeB can co-exist in a same RNC. A RAN sharing NodeB and an
MOCN NodeB cannot co-exist in a same RNC.
If no special requirements exist, it is recommended that all NodeBs under a same RNC be shared NodeBs.
Huawei Confidential
Page 32

MOCN Feature Design
Huawei Confidential
Page 33
RAN sharing/MOCN Reconstruction

Guideline
RAN Sharing reconstruction meaning is the non-shared network
rebuilding to the RAN Sharing network.
MOCN reconstruction meaning is the non-shared network or RAN
Sharing network rebuilding to MOCN network.
The Single NodeB reconstruction:
Scope
The Single NodeB reconstruction

only supports the non-shared network to RAN SHARING or MOCN network reconstruction
The main operator does not change
CME exporting the cell configuration method that increases and deletes are as
follows:
Huawei Confidential
Page 34

Guideline
The Single NodeB reconstruction :
Regarding the single NodeB reconstruction, output all cells of NodeB data by CME, modify
the operator group and import the data, then modify the RNC configuration data online, this
method may not use reset the RNC.
Modify the configure data referring to the install guideline, the cell data cant be modified
online, need output the cell data by CME, modify the operator group and import the modified
data online.
The methods that increases and deletes are as follows
Huawei Confidential
Page 35

Network sharing reconstruction tool:
Guideline
This is the network sharing reconstruction tool which can provide the implementation
instruction.
Suitable for the scenes
Scene 1: General network to RAN Sharing
Scene 2: RAN Sharing to MOCN
Scene 3: General network to MOCN
Scene 4: MOCN to RAN Sharing
Take a general network to RAN Sharing reconstruction of scene 1 as the example,

introduce the operational procedure
Start the tool, clicks on the NetworkTool.exe.
Make the script and checklist:1) enter the tool, click the button
script, and chooses the reconstructiontype, clicks on Next
Huawei Confidential
import the original
Page 36

Guideline
introduce the operational procedure :
Make the script and checklist:2) Parameters Setting page, First click on the button of the
Generate excel template, then the tool will import the data which is relevant with RAN
Sharings information to the EXCEL form.
Huawei Confidential
Page 37

Guideline
Make the script and checklist:3) click on the button of Edit excel template, enters in the
EXCEL template.
Huawei Confidential
Page 38

Guideline

Make the script and checklist:4) in the EXCEL template, input the network sharing
parameters, edit completely, save and close it.
The input request referring to the Usage Note of each form
The meaning of parameters refers to the WEB LMT MML help documents
Huawei Confidential
Page 39

Guideline
Make the script and checklist:5) click on the button of the Check excel template data, it
will verify the information in EXCEL form.
If the verification passes, will have the

following prompt, please click the next
step.
If the verification does not pass, will have the

following prompt, according to wrong
indications, clicks on the button of Edit
excel template again, re-enters EXCEL to
edit, saves and closes. Selects the button of
Check excel template data again until the
verification passes.
Huawei Confidential
Page 40

Guideline
Make the script and checklist:6) click on the button of Start Convert, generate the
script and CheckList. clicks on Finish.
Huawei Confidential
Page 41

Guideline
Make the script and checklist:7) Generate the new script and CheckList with the original
script on the same folder.
CheckList processing
According to customer's reconstruction scene, the tool can produce a checklist and do
preparatory work according to this checklist. Please complete before the reconstruction
implementation.
Mobility processing
Please read the RAN Sharing mobility management of Network Sharing Instruction guideline
book.
LICENSE
Please guarantee that the RAN Sharing/MOCN related characteristic opens in the RNC License
item.
If modify the main operator, please remember applied the new License of RNC/NodeB side,
because ESN is obtained according to main operator's MCC and MNC computation.
Huawei Confidential
Page 42

MOCN Feature Design
Huawei Confidential
Page 43

Country
Spain
UK
Sweden
Australia
Australia
Canada
Sweden
Poland
Operator
VDF
Orange
T-Mobile
H3G
TeliaSonera
Tele2
VDF
Optus
Telstra
H3G
Telus
Bell
H3G
Telenor
Sferia
AERO2
Mode
RAN Sharing (Dedicated Carrier)
MOCN
MOCN
MOCN
MOCN
RAN Sharing
Huawei Confidential
Page 44
Thank you
www.huawei.com

Training Silder UMTS RAN Sharing (RAN17.1)

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Training Silder UMTS RAN Sharing (RAN17.1)

Загружено:

Авторское право:

Доступные форматы

Security Level:

HUAWEI TECHNOLOGIES CO., LTD.

Introduction to RAN Sharing

HUAWEI TECHNOLOGIES CO., LTD.

Introduction to RAN Sharing

Traffic model and

Guideline and Tool

RAN13 or later version

RAN13 or later version

HUAWEI TECHNOLOGIES CO., LTD.

Network sharing feature service

Introduction to RAN Sharing

HUAWEI TECHNOLOGIES CO., LTD.

RAN Sharing Network Structure

Shared Master OSS

Typical Networking Design

HUAWEI TECHNOLOGIES CO., LTD.

Typical Networking Design

HUAWEI TECHNOLOGIES CO., LTD.

Typical Networking Design

HUAWEI TECHNOLOGIES CO., LTD.

Typical Networking Design

HUAWEI TECHNOLOGIES CO., LTD.

Typical Networking Design

HUAWEI TECHNOLOGIES CO., LTD.

Typical Networking Design

HUAWEI TECHNOLOGIES CO., LTD.

Iu/Iur Interface Design

For different operators, the Iu

interface are shared among operators.

Iu interface design in RAN sharing

The transmission resources at the Iur

Iur interface design in RAN sharing

(the same as that in non-RAN

(the same as that in non-RAN sharing

The Iu interface design is the same

Total Iur transmission bandwidth =

(Iur transmission bandwidth required

The operators can activate or de-

excitation Iu-Flex alone, Iu-Flex

Interface transmission capability design

configuration in RAN sharing is

Interface networking design

similar with non-sharing RNC

Interface transmission capability

Interface networking design

HUAWEI TECHNOLOGIES CO., LTD.

Iub Interface Design

A shared RNC supports shared and

The NCP, CCPs, ALCAP link, and

User Plane Design

When uses the ATM/IP double protocol

When Iub user plane configure special

HUAWEI TECHNOLOGIES CO., LTD.

Transmission resources can be shared

Performance Security System Software License

HUAWEI TECHNOLOGIES CO., LTD.

License Management Design

HUAWEI TECHNOLOGIES CO., LTD.

Introduction to RAN Sharing

HUAWEI TECHNOLOGIES CO., LTD.

MOCN Network Structure

Shared Master OSS

A maximum of 4 operators can be supported.