3g ran sharing
DESCRIPTION
3G RAN Sharing_ALUTRANSCRIPT
-
Alcatel-Lucent Mobile Network Sharing solutions for 3G
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction. 1 | MS Product Support | April 2010
solutions for 3G
-
Site sharing
UTRAN sharing (MORAN)
National Roaming(Geo Split)
Area covered by Operator A
Network control Passive RAN Sharing Active RAN Sharing
Roaming Based Sharing
Dedicated frequencies
NETWORK SHARING BIG PICTURE
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
2
Costs savings
MOCN
Area covered by Operator A
Area covered by Operator B
Tower
Site
Antenna
Shelter
Transmission
Site Support
Dedicated frequencies
Shared frequencies
-
f1 + f2
Subscriber
operator A
Subscriber
operator B
PLMN A&B
BW #1 BW #2
PLMNA&B
PLMNA&B
f1 f2
Subscriber
operator A
Subscriber
operator B
BW gap
BW #1 BW #2
Shared Spectrum
Subscribers of operator A and operator B can use the full
spectrum of operators A and B.
MOCN
SPECTRUM USAGE
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
3
PLMN A PLMN B
f1 f2
Subscriber
operator A
Subscriber
operator B
BW gap
BW #1 BW #2
PLMN A PLMN B
f1 f2
Subscriber
operator A
Subscriber
operator B
Dedicated Spectrum
Subscribers can only get network access using their
respective operators spectrum
UTRAN Sharing (MORAN)
-
1. Sharing solutions panel
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction. 4 | MS Product Support | April 2010
-
UTRAN NETWORK SHARING OPTIONS
SHAREDNB
Spectrum from the operators/PLMN can be shared or dedicated. The PA can be shared within PA instantaneous
CCM allows transmission sharing for Iub back to RNC
CEM Resources can be pooled among operators or dedicated
NB
SHAREDRNC
Supports up to 4 PLMNs with independent Iu-Flex config. Connected to shared and non-shared RNC (up to 36 Iur connections)
Connected to shared and non-shared NBs
Resources pooled among operatorsRNC
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
RNC
SHAREDTRANSMISSION
Iub traffic can be split or pooled
Flexible partitioning or pooling of Iub bandwidth
Transport
SHAREDO&M
O&M
The shared part of the network is managed by a prime operatorCell-level parameters/counters can be set/derived per operator
Resource based Access Control per PLMN in WMS
Performance reporting per PLMN in NPO
-
National Roaming (Geo Split) overview
Each operator builds its own RAN and CN in its home geographical area, and allows
subscribers from the other operator to roam in the visited network
Traffic from roamers is rerouted in the core network
Operators may also deploy non-shared, overlapping coverage in strategic areas
In order to provide Seamless roaming across the network, ALU provides in particular
following mobility features :
Inter-RNC Inter-frequency Inter-PLMN Handover without Iur
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
Inter-RNC Inter-frequency Inter-PLMN Handover without Iur
IMSI Based Handover, to direct subscribers to the correct non-shared 3G or 2G areas
Operator A sub.
2G A
2G B
3G B 3G A
3G A
3G B
3G Shared Area 3G Shared Area3G Strategic Non-Shared
Operator B sub.
-
UTRAN Sharing (MORAN) overview
Operators share physically the Radio Access Network (NodeB and RNC) from a common supplier, but do not share any Core Network node
Each operator uses its own licensed spectrum, broadcasts its own PLMN id
Mobility is handled on separate layers
Mobile camps on appropriate cell, shows right operator logo
Handovers are directed to cells of the same operator (both 3G and 2G)
RNC supports multiple Ius to independent Core Networks, with or without IuFlex
Routing to CN operator based on the current cell PLMN id
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
Routing to CN operator based on the current cell PLMN id
Differentiation at cell level (radio parameters, features activation) and on network services
No Terminal or Core Network dependency; seen as two separate networks
Iu
Iu
RNC
NodeB
Core NetworkOperator A
Core NetworkOperator B
Shared RAN
f1, PLMN1
f2, PLMN2
f2, PLMN2
f1, PLMN1
Operator ASubscriber
Operator BSubscriber
-
MOCN (Multiple Operator Core Network) overview
Operators share physically the Radio Access Network (NodeB and RNC) from a common supplier, but do not share any Core Network node
On a shared cell, a common PLMNid is broadcast for non-MOCN capable UEs, plus additional PLMNids for MOCN-capable UEs
RNC supports multiple Ius to independent Core Networks
Supporting UEs indicate the selected PLMN to the RNC, which routes accordingly
Non-supporting UEs only see the common PLMN, hence are unable to select one; the RNC selects one CN and reroutes to another CN if rejected
No differentiation at RAN level, but possible on network services
LR14.2
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
No differentiation at RAN level, but possible on network services
Support from CN (CS/PS) is required.
RNC
NodeB
Shared RAN
F1, Common PLMN +PLMN A +PLMN B
Iu
Iu
Core NetworkOperator A
Core NetworkOperator B
Operator ASubscriber
Operator BSubscriber
-
RAN Sharing solutionsSummary
Site Sharing RAN Sharing National Roaming MOCN
Combined architectures are possible
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
Cost savings Low Medium Medium High
Access to full bandwidth
with Shared SpectrumNo No No Yes
Guaranteed resources and
QoS per operatorYes Yes No No
Core Network dependency No No No Yes
Terminal dependency No No NoYes (non optimal behaviour for non
supporting UEs)
Need for an OAM
coordinationLow High Medium High
-
2. Resources Sharing
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction. 10 | MS Product Support | April 2010
-
Physical resources sharingCEM resource use examples
CEM CEM
Partial reservation Unbalanced
Resources can be pooled and/or dedicated
The operator can configure for each carrier the resources that are reserved
These reserved resources cannot be used by another carrier, the remaining resources being shared
It is then possible to have a pool of resources for Operator A, a pool or resources for Operator B, and a pool shared between 2 of them
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
No dedicated resources
CEM
Fully pooled
Dedicated resources on F1
Dedicated resources on F2
Pooled resources on F1&F2
No pooled resources
Fixed dedicated resources
CEM
Dedicated resources on F1
Pooled resources on F1&F2Fully split
MORAN all reservation options are possible
MOCN Fully pooled option
-
Physical resources sharingShared transmissions : Iub bandwidth pool concept
Support of logical bandwidth pools dedicated per PLMN Id (for 9370 RNC only)
Flexible partitioning or pooling of the Iub bandwidth can be achieved
At CAC time, bandwidth pool is selected based on PLMN Id
When a bandwidth pool is dedicated to an operator, its bandwidth is not accessible
to another operator
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
to another operator
When a bandwidth pool is shared between operators, the bandwidth is used on a first
come, first served basis
-
Iub Load reported per PLMN ID
One operator may experience congestion or high load on its own bandwidth pool and this
means that only cells belonging to that operator should change colour (Iub load taken into
account in in iRM algo) according to the load.
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
-
RNC aspects
Reduce cost by maximizing the number of shared
elements
in the RNC all cards are pooled among operators
reuse of existing RNC hardware
no reserved processing capacity per operator
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
A shared RNC does not require more processing
capacity to support the same traffic as a non-shared
RNC:
all RNC HW resources are pooled between both
operators sharing the RNC
complexity associated to signaling processing is
not significantly increased
-
3. RAN sharing network management
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction. 15 | MS Product Support | April 2010
-
Wireless Management System (WMS) for UTRAN SharingHigh Level principles
The ALU sharing solution supports up to 4 operators
The ALU sharing solution assumes that the
business model includes a Neutral/Master operator that will be responsible for:
Installation and maintenance of the NEs
Upgrade of the NEs
Parameters optimization of the common
parameters
Nodal availability of the NEs
Operator
Red
OSS
Operator
Blue
OSS
Operator
Orange
OSS
WPS SDA NPOWQA RFO
Shared W-CDMA Management Solution
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
Nodal availability of the NEs
Global network QoS analysis,
Call traces that can be across multiple shared
cells
Etc.
It is assumed that the shared operators and the
neutral one are working in good terms and
conditions. Typically, all partners will meet
regularly to define any new features to
activate, decide new deployment, site to share
/ no more share, etc.
WMSData
Cell
Data
Cell
Data
Cell
Data
Common
-
Wireless Management System (WMS) for UTRAN SharingAccess Control
The Access Control tool allows the system administrator to create, modify and view user access permissions in order to control the functions users perform and the access to selected areas of the system based on those functions.
Consequently, a user group can only view and manage their own network resources.
Per Role Permissions
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
Access control is at the Node Level
Topological View with map Grid View for large networkMatrix View per RNS
Some users will see a NE, other not
-
Network Performance Optimizer (NPO) for UTRAN SharingGenerated reports
Cell-based counters may be used to derive independent performance reports
per operator. In particular, the following categories of statistics apply per cell /
operator:
>Radio Measurement
> Iu Connection
> IuR Interface
> Soft Handover
>Hard Handover
>Paging
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
> IuR Interface
>Power Management
>Retainability
>Accessibility
>Paging
>RRC Connection
>Mobility
>QoS Performance
>RAB and RB Management
>Radio Link Management
-
Features Activation Management
In MORAN option, any feature which can be controlled via parameter(s) linked to the FDDCell can generally be configured to behave in a per-operator manner. For example: iMCTA, HSDPA, HSUPA This isnt the case for MOCN when the cells are shared.
Some other features may also be activated per operator: Hybrid Iub, IuPS over IP, Iu Flex
Common strategy to be agreed for features which are controlled via parameter(s) linked to the RNC. For example: Always-On, URA_PCH, Pre-emption, HSxPA to DCH fallback
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
DCH fallback
> iMCTA
>HSDPA
>HSUPA
>
Activated per operator Common activation
>Always on
>URA_PCH
>Pre-emption
>HSxPA to DCH fallback
>Hybrid Iub
> IuPS over IP
> Iu Flex
>
-
Parameters Configuration
Access control parameters (access class barring, cell barring)
Neighboring information (FDD and GSM cells)
Cell (re)selection parameters (Intra-frequency, Inter-Frequency and Inter-System)
Measurement control parameters (including GSM measurements activation)
In addition, many parameters can be individually tuned for each operator. That includes in particular for MORAN option:
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
Measurement control parameters (including GSM measurements activation)
Handover mobility decision algorithm parameters (Intra-frequency, Inter-Frequency and Inter-System)
Power control, Power Partitioning, TX Power parameters
Call admission control parameters (load thresholds for iRM, interference levels for Admission)
In MOCN option, cell parameters must be agreed between operators except if they can be distinguished per PLMN e.g. Neighboring information.
-
4. NodeB Configurations
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction. 21 | MS Product Support | April 2010
-
TRDU2x80-21RRH2x60-21ATRDU60-21
RAN Sharing configurations WCDMA 2100MHz band
LR14.2
RRH2x60-21ARRH2x60-21A
RRH2x60-21A
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
9711/12 LR Cabinet 9711/12 LR Cabinet 9711/12 LR Cabinet
Up to 3x(2+2) cellsSTSR1+1 (up to 60W per carrier)STSR2+2 (up to 30W per carrier)
Up to 3x(2+2) cellsSTSR1+1 (up to 80W per carrier)STSR2+2 (up to 40W per carrier)
Up to 3x(2+2) cellsSTSR1+1 (up to 60W per carrier)STSR2+2 (up to 30W per carrier)
-
TRDU2x60-09MCTRX67-09
RAN Sharing configurations WCDMA 900MHz band
SR
A
N
D
S
U
M
X
A
N
D
A
N
D
SR
M
C
T
R
X
9
0
0
fan
M
C
T
R
X
9
0
0
M
C
T
R
X
9
0
0
RRH2x40-09
RRH2x40-09RRH2x40-09
RRH2x40-09
LR14.2 for 3G only mode
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
SR
A
N
D
S
U
M
X
A
N
D
A
N
D
SR
fan
M
C
T
R
X
9
0
0
M
C
T
R
X
9
0
0
M
C
T
R
X
9
0
0
9100 MBS9711/12 LR Cabinet
Up to 3x(2+2) cells with 2 MCTRX per sectorSTSR1+1 (up to 60W per carrier)STSR2+2 (up to 30W per carrier)
Note that STSR2 is also possible with 1 MCTRX per sector (up to 30W per carrier)
d2U
9711/12 LR Cabinet
Up to 3x(2+2) cellsSTSR1+1 (up to 40W per carrier)STSR2+2 (up to 20W per carrier)
Up to 3x(2+2) cellsSTSR1+1 (up to 60W per carrier)STSR2+2 (up to 30W per carrier)
-
5. UTRAN Sharing roadmap
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction. 24 | MS Product Support | April 2010
-
UTRAN sharing management evolution
Reports per PLMNid for configuration,
performance and availability
managemlent
Resources based access control per
PLMNID
MOCN already in code
UTRAN Sharing (MORAN) Support of 2 operators on one RNC / NodeB
Separated Iu interfaces
Compatible with IuFlex; can be used
independently per operator
1 carrier per operator (2+1 also possible)
CEM DCH resources can be pooled and/or
split
Per Operator differentiation through
Alcatel-Lucent Software UTRAN sharing Roadmap
UA5.1 UA07
LR14.2
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
UTRAN Sharing support for 4 operators 4 carriers support in one NodeB (STSR2+2)
UTRAN Sharing developments Both DCH & HSxPA resources can be split
and/or pooled
Iub traffic can be split and/or pooled
Per Operator differentiation through
separated Cell Level Configuration
Management
Performance reporting per PLMN (NPO)
UA06
MOCN Commercial Availability
For both 9370 RNC and 9771 WCE RNC
Only 2 operators configuration tested
LR14.2
-
UTRAN MORAN implemented to cover white zones with UMTS 900MHz
Deployed since 2011
UTRAN MORAN Implementation in France
1 frequency per operator with all
services (R99, HSxPA).
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
RF: sharing based on RRH and STSR2+2
Digital BBU:
1 modem shared between ORF and Free
1 modem shared between BYT and SFR
Controller shared between all
operators
Iu over IP with 1 port (1Gbps) per 4pGigaEthernet cards to carry the Iu traffic.
RNC IP Resiliency with Protected Default Route mechanism + SCTP heartbeat.
-
Backup
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction. 27 | MS Product Support | April 2010
-
178821 - Commercial Availability of MOCN
This feature is intended to commercialize Multi-Operator Core
Network (MOCN) functionality as was initially started by feature
PM28528.
MOCN is a solution where two (or more) operators share some
common Radio Access Network in certain areas or even in the
whole network but do not share their core networks.
LR14.2
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
The operators do not only share the radio network elements, but
may also share the radio resources themselves.
In general, the overall solution is required to support a minimum
of 2 operators and each operator can support up to 2 PLMNs. What
this means is that the 2 MOCN CN operators wont be supporting
more than 2 PLMNs (HPLMN + Common PLMN)
-
RF module Band Instantaneousbandwidth
Max Configurations Release
RRH60-21C 1 20MHz With 2 modules per sector:Up to 3x(2+2) cells
STSR1+1 (up to 60W per carrier)
STSR2+2 (up to 30W per carrier)
UA07.1
TRDU60-21B 1 20MHz UA07.1
RRH2x60-21-A 1 2x45MHzUp to 3x(2+2) cells
STSR1+1 (up to 60W per carrier)
STSR2+2 (up to 30W per carrier)
LR13.1W intro
LR14.2W IBW 45MHz
Up to 3x(2+2) cells
WCDMA RF modules capabilities
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
29
TRDU2x80-21 1 2x45MHzUp to 3x(2+2) cells
STSR1+1 (up to 80W per carrier)
STSR2+2 (up to 40W per carrier)LR14.2W
RRH2x40-09 825MHz total
(20MHz max per PA)
Up to 3x(2+2) cells
STSR1+1 (up to 40W per carrier)
STSR2+2 (up to 20W per carrier)
UA08.1 1PA 2G + 1PA 3G
LR13.3W 3G only
MC-TRX67-09 8 20MHz
With 2 MC-TRX per sector (in this
case, IBW 2x20MHz):
Up to 3x(2+2) cells
STSR1+1 (up to 60W per carrier)
STSR2+2 (up to 30W per carrier)
UA08.1
3G in 2G cab, MSR mode, 3G only
TRDU2x60-09 825MHz total
(20MHz max per PA)
Up to 3x(2+2) cells
STSR1+1 (up to 60W per carrier)
STSR2+2 (up to 30W per carrier)
LR13.3W 1PA 2G + 1PA 3G
LR14.2W 3G only
-
Features
PM Id Feature Title Release Description Value
18855 UTRAN Sharing UA05.1
This feature introduces: Support of UTRAN sharing for 2
operators (4 operators with feature 34699) on one RNC /
NodeB
-Separated Iu interfaces
-Compatible with IuFlex; can be used independently per
operator
-1 carrier per operator (2+1 also possible)
-CEM DCH resources can be pooled and/or split
-Per Operator differentiation through separated Cell Level
Configuration Management
-Performance reporting per PLMN (NPO)
UTRAN Sharing allows a significant reduction in the amount of up-
front network build expenses, coverage acceleration in low dense
areas, and can also cope with site acquisition issues.
Compared to other network sharing solutions, the Alcatel-Lucent
UTRAN sharing solution has the following benefits:
No terminal dependency
No core network dependency
Each operator uses its own spectrum and related radio
parameters can be tuned separately
34699UTRAN Sharing support for
UA05.1This feature introduces: UTRAN sharing supports up to 4
see 18855
Alcatel-Lucent InternalProprietary Use pursuant to Company instruction.
34699UTRAN Sharing support for
4 operatorsUA05.1
This feature introduces: UTRAN sharing supports up to 4
operators. See feature 18855see 18855
34105UTRAN Sharing
developmentsUA06
This feature provides the capability to share between up
to 4 operators the Iub resources (bandwidth pools) and
the CEM resources
Additional flexibility is added in network sharing operations
117732RAN sharing based on MC-
TRXUA08.1
RAN sharing based on MC-TRX is a solution that provides
the ability to operate 4 discontinuous carriers anywhere
in the 35 MHz of the UMTS 900 band. This is achieved by
configuring 2 WCDMA carriers per MC-TRX67-09 enabling
support of (STSR 2+2).
With a single 9100 MBS cabinet (indoor and outdoor version),
two operators can provide service up to 3 sectors with up to
2x30W carriers.Solution is based upon existing qualified Multi-
Carrier HW (MC-TRX67-09) where 3G support is provide via SW
upgrade.
178821Commercial availability of
MOCNLR14.2
This feature is intended to commercialize Multi-Operator
Core Network (MOCN). MOCN is a solution where two (or
more) operators share some common Radio Access
Network in certain areas or even in the whole network
but do not share their core networks.
MOCN will allow customers to share network infrastructure
between two or more license holders.
This solution is one approach for reducing overall business risk of
operating a 3G network. Use of MOCN configurations can
improve time to market and most importantly reduce the amount
of upfront network build expenses.