Training Silder UMTS RAN Sharing (RAN17.1)

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

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 TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

Resource
allocation design
Customer
Networking design requirements
Interface design
Traffic model and
network scale
Transmission
License Management network information
design OM design
Operator and CN
information
RAN hardware
information
Feature combination Guideline and Tool
policy design Support
The payment
approves Implementation
NE Version
RNC RAN13 or later version

Node B RAN13 or later version Network sharing feature service

MOCN Feature Design

RAN Sharing Network Structure
Operator A Operator B
CN CN
Operator A NMS Operator B NMS
Itf-N Iu interface
RNC
Iub interface
Shared Master OSS
Macro
Node B
4 operators
32 MSC servers
32 SGSN F1: Operator A
32 MGW F2: Operator B RRU
15 Neighboring RNC Dedicated

Shared RAN Carrier Mode
4 CBC

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.

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.

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.

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.

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.

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.

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

Iub Interface Design
Control Plane and Management User Plane Design
Constraints Plane Design
A shared RNC supports shared and The NCP, CCPs, ALCAP link, and Transmission resources can be shared
non-shared NodeBs. OM channel are shared among among operators or separated.
The constraints on sharing of the operators. That is, one NodeB has When Iub user plane configure special
only one set of control plane and purpose, the user planes transmission
transmission resources are shown
OM configuration data. resources can configure different virtual
as follows:
port(VP) or logical port(LP), each VP or LP
only correspond an operator.
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

OM Design
Mangers of Mangers
Operator A shared Operator
of
data B
A s cell Bs cell
level data level data
EntryPointIRP Agent
Instance CMIRP Agent Instance
set 1 PMIRP Agent set 2
FMIRP PMIRP Agent
FMIRP Agent FMIRP Agent
Agent Supplier
Notification Itf - N Notification Supplier
Topology Configuration Fault Performance Security System Software License

iManager TM M2000
Node B RNC Node B RNC

Shared Non-
Non-Shared
Shared
RAN 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.

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.

MOCN Feature Design

MOCN Network Structure
Core Node Core Node

A B
MSC
MGW MSC
Server SGSN MGW SGSN
Server
Operator A NMS Operator B NMS
Iu interface
RNC
Shared Master OSS
Iub interface
NodeB
A maximum of 4 operators can be supported.
...
All RAN resources, including carrier and
Shared Carrier
baseband resources are shared. Mode
Shared RAN

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.

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.

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.
Operator A CN Operator B CN
Iu
Operator A
Iur
Dedicated RNC MOCN Shared
RNC
Operator B Iur
Dedicated RNC
Operator B Cell
MOCN Cell
Operator A Cell

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.
Operator A MOCN Operator B

BSS Shared RNC BSS
GSM Cell MOCN Cell GSM Cell

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.
Operator A MOCN Operator B

BSS Shared RNC BSS
GSM Cell MOCN Cell GSM Cell

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.
Operator A
MSC server 3
MSC server 2
MSC server 1
MGW 4 SGSN 2
MGW 3 SGSN 1
MGW 2
MGW 1
Operator B
MGW MSC server
MOCN SGSN 1
SGSN 2
Shared
RNC SGSN 3
MOCN Cell MOCN Cell MOCN Cell

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.

Interface Design
Iur interface design is the

Iu interface same as that in the RAN
Iu interface design is the same as that sharing service design.
in the RAN sharing service design.
Interface design
Iur interface
Iub interface
RAN14.0: The RAN SHARING scene The largest difference with Iub interface design in RAN sharing
supports Iub transmission separation, service design is as follows: In RAN sharing scenarios, Iub
but the MOCN scene does not support transmission separation is supported; in MOCN scenarios, Iub
it. transmission separation is not supported.
RAN15.0 The MOCN scene supports
the Iub service plane transmission
resources independently (including IP
or ATM transmission);

OM design & License management design
OM design License management design
Does not support many operators to have MOCN RAN, only has RNC License and NodeB
one set of M2000 to manage a shared License.
network respectively. RNC License contained the functional control
The MOCN network shares FM (fault item and the resource control item, resources
management) and CM (configuration
License may configure independently, the
management). PM (performance
functional control item is shared by various
management) may the part independence,
operators. First, RNC License may the whole
each operator can be possible to gain the
independent RNC level statistics, but activate and does not differentiate the operator,
shared the cell level performance statistics. then according to configure resources by each
Each operator modify the cell parameter in operator.
sharing cell can affect other operators, In the NodeB side, the functional control item is
therefore should by jointly manage the shared by all operators, cannot establish
maintenance team or the host operator independently, namely various operators use the
team is responsible. 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.

Load Balancing Design
MOCN RNC broadcast multiple PLMN identities in MIB on BCCH
Common PLMN
Master Information Block
{
OperA CN OperB CN PLMN identity
Multiple PLMN List Indicates if Common
{ PLMN is one of the
MIB PLMN identity Multiple PLMNs
Multiple PLMNs
Iu Interface {
OperA PLMN
OperB PLMN
PLMN list
MOCN RNC ...
}
}
...
Uu Interface }
Common PLMN If 'MIB PLMN Identity' = TRUE

Broadcasting in MIB
UE OperA PLMN Supporting UE
Non-supporting UE
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.

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.

MOCN Feature Design

Feature Connected to CNs Belong to the Same Radio Frequency

Multiple CNs or Not Operator or Not 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

NodeB Sharing Type Design
NodeB Sharing Mode Basic RNC Information NodeB Configuration

Configuration
RNC Supporting Network Sharing Shared or Resource
or Not Not Management Mode
MOCN NodeB Yes Yes Shared
RAN Sharing NodeB Yes Yes Shared or dedicated
Dedicated NodeB Yes or No No -
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.

MOCN Feature Design

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:

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

Network sharing reconstruction tool:
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 import the original script, and
chooses the reconstruction type, clicks on Next

Take a general network to RAN Sharing reconstruction of scene 1 as the example, 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.

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

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

the operational procedure
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 If the verification does not pass, will have the
following prompt, please click the next step. 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.

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

the operational procedure
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.

MOCN Feature Design

Country Operator Mode

VDF
Spain RAN Sharing (Dedicated Carrier)
Orange
T-Mobile
UK RAN Sharing (Dedicated Carrier)
H3G
TeliaSonera
Sweden MOCN
Tele2
VDF
Australia RAN Sharing (Dedicated Carrier)
Optus
Telstra
Australia MOCN
H3G
Telus
Canada MOCN
Bell
H3G
Sweden MOCN
Telenor
Sferia
Poland RAN Sharing
AERO2

Thank you
www.huawei.com

Training Silder UMTS RAN Sharing (RAN17.1)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Training Silder UMTS RAN Sharing (RAN17.1)

Hochgeladen von

Copyright:

Verfügbare Formate

2017/8/11 Security Level:

Professional Service Team www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

RAN Sharing Feature Design

MOCN Feature Design

Feature Combination Policy Design

RAN sharing & MOCN Reconstruction Guideline

Commercial Sites of RAN Sharing

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

RNC RAN13 or later version

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

RAN Sharing Feature Design

MOCN Feature Design

Feature Combination Policy Design

RAN sharing & MOCN Reconstruction Guideline

Commercial Sites of RAN Sharing

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5

15 Neighboring RNC Dedicated

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

Co-existence of full coverage by shared and non-shared RANs

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

Co-existence of shared network and 2G network

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

Co-existence of shared network and 2G network

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

Co-existence of full coverage and partial coverage by different operators

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

Co-existence of Iu-Flex and RAN sharing

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

Co-existence of multiple operators

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

Iu interface design Iur interface design

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

When uses the ATM/IP double protocol stack,

When Iub user plane configure special

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

Topology Configuration Fault Performance Security System Software License

Node B RNC Node B RNC

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

RAN Sharing Feature Design

MOCN Feature Design

Feature Combination Policy Design

RAN sharing & MOCN Reconstruction Guideline

Commercial Sites of RAN Sharing

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

Core Node Core Node

Operator A NMS Operator B NMS

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 18

The Whole network MOCN

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

MOCN Private cell network

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

MOCN RNC and special RNC coexist

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

MOCN RNC and 2G network coexist

Operator A MOCN Operator B

GSM Cell MOCN Cell GSM Cell

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

MOCN RNC and 2G network coexist

Operator A MOCN Operator B

GSM Cell MOCN Cell GSM Cell

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23