nsn_nw sharing moran and mocn for 3g_revised
DESCRIPTION
MORAN/MOCNTRANSCRIPT
1 © Nokia Siemens Networks
Network sharing MORAN and MOCN for 3G May 2013
2 © Nokia Siemens Networks
Mobile Broadband | SON
Sharing Methods MORAN for
3G / I-HSPA MOCN for 3G / I-HSPA
MORAN and MOCN Pros vs.Cons
NW sharing OSS
Q&A
3 © Nokia Siemens Networks
Common
OSS
Dedicated
OSS
HLR MSS/
PS core
RNC/ BSC
Transmission Base
station
Antenna line
Gray colour is shared OP 1 OP 2
Passive RAN sharing (site w-w/o transmission sharing)
Active RAN
sharing
Roaming
based sharing
Degree of network control
Degree of network
sharing and cost savings
Solutions for each business need Sharing Methodologies
4 © Nokia Siemens Networks
• Areas with high business potential
• Heavy competition between OPs
• Full control of own network assets
• High potential need for service and performance differentiation
• Starting point for network consolidation
• Areas with moderate business potential
• Partial control of network assets
Active RAN sharing
Passive RAN / site based sharing
Roaming based sharing
• Areas with low business potential
• Lowest-cost approach to fulfill regulatory coverage requirements
• No service or performance differentiation
Solutions for each business need Use cases
5 © Nokia Siemens Networks
Solution for every RAN technology
MORAN / MOCN** for HSPA (dedicated frequencies / shared spectrum)
MSC/SGSN
MSC/SGSN
HLR
HLR
RNC
NodeB
2G 3G LTE
Service Platforms Service
Platforms
Service Platforms
* 3GPP Rel. 10 & 11 (MOCN)
** 3GPP Rel. 6 (MOCN)
*** 3GPP Rel. 8 (MOCN)
NodeB NodeB
Service Platforms
MOBSS / MOCN* for GSM (dedicated frequencies/shared spectrum)
BSC
BTS
MSC/SGSN
MSC/SGSN
HLR
HLR
Service Platforms
Service Platforms
BTS BTS
MORAN / MOCN*** for LTE (dedicated frquencies / shared spectrum)
eNodeB
MME/S-P-GW
MME/S-P-GW
HSS
HSS
Service Platforms
Service Platforms
eNodeB eNodeB
6 © Nokia Siemens Networks
Mobile Broadband | SON
MORAN for 3G / I-HSPA
Sharing Methods
MOCN for 3G / I-HSPA
NW sharing OSS
MORAN and MOCN Pros vs.Cons
Q&A
7 © Nokia Siemens Networks
3G Network sharing Multi-Operator RAN General feature information
• RAN1452 Multi-operator RAN feature enables RAN sharing between two or more operators with dedicated spectrum
• Each operator sharing the RAN has its own core network. The core does not need support 3G MORAN
• RAN1602 Fixible Iu with MORAN can be used for multiple connections to each operators’ core networks (Current behaviour still does not allow for overlapping NRI values among operators)
• RAN1274 can be used to define Dedicated BB per operator
MORAN prerequisites
Shared RNC
Shared
NB Shared Iub
Operator 1 cells Op1 PLMN ID
Operator 2 cells Op2 PLMN ID
RA
N1602
Fle
xib
le I
u
Operator 1
Core Network
Operator 2
Core Network
8 © Nokia Siemens Networks
3G Network sharing MORAN General feature information
• Shared resources:
– Iub interface (feature being defined for resource splitting)
– NB HW (dedicated spectrum and cells for the sharing operators)
– RNC
– Feeder cables and antennas (combiner if needed)
– Racks, power supply and batteries at a NB level
• Non-shared resources:
– Scheduler
– Iu interfaces
– BB capacity
– Licensed frequencies
– Core network elements and services
– Cell level parameter settings (dedicated PLMN ID is broadcasted)
– Operator logo on the MS
Shared vs. non-shared resources
10 © Nokia Siemens Networks
Mobile Broadband | SON
MOCN for 3G / I-HSPA Sharing
Methods MORAN and MOCN Pros vs.Cons
MORAN for 3G / I-HSPA
NW sharing OSS
Q&A
11 © Nokia Siemens Networks
3G Network sharing MOCN General feature information
• Shared resources:
– Licensed frequencies
– Cell level parameter settings (a common PLMN and a Multiple PLMN list are broadcasted)
– Iub interface
– NB HW
– RNC
– Feeder cables and antennas (combiner if needed)
– Racks, power supply and batteries at a NB level
– BB capacity
• Non-shared resources:
– Iu interfaces
– Core network elements and services
– Operator logo on the MS can be provided by NITZ (CN feature)
Shared vs. non-shared resources in 3G MOCN
12 © Nokia Siemens Networks
3G Network sharing MOCN IMSI Based Handover
• Used in MOCN with geographical split where operators also have dedicated (non shared) networks • End-user served by home network as soon as in coverage area • Separate neighbour lists for different IMSI ranges (users from different PLMNs)
IMSI based Handover
WCDMA
GSM GSM GSM GSM GSM
WCDMA WCDMA
WCDMA
WCDMA
GSM GSM GSM GSM GSM
GSM GSM
WCDMA WCDMA
WCDMA
Operator 1
Core Network
Operator 2
Core Network Dedicated
NB
Shared
NB
Dedicated
NB
Shared RNC
• New RNC functionality:
• Neighbor target cells depend on connected core
• Works for home users and roaming users
13 © Nokia Siemens Networks
3G Network sharing MOCN MOCN Traffic statistics (RAN)
• Cell Throughput counter
• This measurement provides the radio resource throughput per cell in the serving RNC (SRNC).
• Provides a way for sharing operators to monitor and measure used capacity
• Works with all UEs. No restriction for pre Rel.6 UEs
• Measurements are based on the counters list on the right
• The counters are updated irrespective of the used channel type, so all channel types HS-DSCH, E-DCH and Rel99 DCH are included.
Operator 1
Core Network
Operator 2
Core Network
Shared NB
Shared RNC
Cell Throughput counters per PLMN
14 © Nokia Siemens Networks
3G Network sharing MOCN PLMN selection by the terminals
• In a shared RAN, each cell shall broadcast information of the available core network operators in the shared area.
• A Common PLMN to both operators is broadcasted as PLMN identity IE present in the Master information block
– MOCN non-Supporting UEs are only able to read PLMN Identity which is the “Common PLMN” in the shared RAN area
▪ Non supporting UEs are 3GPP Pre-Rel.6 UEs or
▪ Non supporting UEs are 3GPP Rel. 6 UEs or above which have the MOCN feature deactivated. The MOCN feature is optional and many times is not activated.
– Supporting UEs decode Multiple PLMN List and take the information concerning available CN operators in network and cell (re-)selection procedures
Information Element/Group name Need Type and reference Version
CN information elements
Supported PLMN types MP PLMN Type
PLMN Identity CV-GSM PLMN Identity
Multiple PLMN List OP Multiple PLMN List Rel-6
Master Information Block
Used by Non-supporting UEs to
select CN
Used by Supporting UEs to
select CN
15 © Nokia Siemens Networks
3G Network sharing MOCN MOCN Capacity Assurance
HSDPA Capacity split enforcement
• BTS HSDPA scheduler divides resources between operators
• RNC indicates the operator for each call to the BTS scheduler
• BTS scheduler divides the HSDPA resources according to defined quota between operators
• Resource split is enforced by modifying the scheduling weights for each user, based on total number of users per operator in the scheduler
• In the figure (slide 3) is illustrated example case with three operators, each having 33% of capacity reserved
PLMN Grouping
• In addition to capacity assurance, also support for PLMN grouping is provided with this feature
• According to defined mapping table RNC can identify PLMN:s of the same "group" and use preferred CN
MOCN Capacity Assurance
16 © Nokia Siemens Networks
3G Network sharing MOCN MOCN additional counters
Additional counters to monitor the MOCN (Multi Operator Core Network) feature
• Total attach/Location Update rejects sent by CN to RNC:
• One counter for each possible reject cause code: • #11 PLMN not allowed
• #12 Location Area not allowed
• #13 Roaming not allowed
• #14 GPRS services not allowed in this PLMN
• #15 No Suitable Cells In Location Area
• others
• Total attach/Location Update rejects sent by RNC to UE:
• one counter for each possible cause code: • #11 PLMN not allowed
• #12 Location Area not allowed
• #13 Roaming not allowed
• #14 GPRS services not allowed in this PLMN
• #15 No Suitable Cells In Location Area
• Others
• Total attach/LU redirections performed
Attach and Location Update counters per single CN and MOCN
Rejects sent by CN to RNC
Rejects sent by RNC to UE
Redirections performed
17 © Nokia Siemens Networks
3G Network Sharing – MOCN Terminal Capabilities
3GPP Rel. Capabilities Implications
Te
rmin
als
Pre-Rel. 6 Can only read the Common PLMN Identity in the
Master Information Block RNC has to make the Core Network selection.
Rel. 6 or later
In case MOCN feature in the terminal is deactivated.
UE can only read the Common PLMN Identity in the
Master Information Block
RNC has to make the Core Network selection.
Rel. 6 or later
In case MOCN feature in the terminal is activated.
UE can read both Common PLMN Identity and PLMN
list I in the Master Information Block
No Impact. In dedicated cells PLMN ID as in
non shared networks
18 © Nokia Siemens Networks
Mobile Broadband | SON
MORAN and MOCN Pros vs. Cons
Sharing Methods
MOCN for 3G / I-HSPA
MORAN for 3G / I-HSPA
Q&A NW sharing OSS
19 © Nokia Siemens Networks
3G Network sharing – MORAN Dedicated radio frequencies, Independent Core
Sharing one or more physical RNC and
NodeB between multiple operators
Operators can have both shared RAN and
own dedicated RAN networks
simultaneously
Dedicated carrier unit per operator in
NodeB
Own PLMN-id’s and frequencies
Own cell level parameters
Common site level parameters
Up to 4 operators with own
licensed frequencies
core networks
services
operator-dedicated RAN from any
vendor in non-shared areas
RAN owned either by
• Operator A
• Operator B
• JV
• 3rd party (Network
Provider)
Dedicated frequencies
Scenario Characteristics
MSC/SGSN MSC/SGSN
HLR HLR
RNC
NodeB
Service Platforms
Service Platforms
NodeB NodeB
20 © Nokia Siemens Networks
3G Network sharing – MORAN Dedicated radio frequencies, Independent Core
Minimum joint configuration is 2 carriers
Application SW in radio needs to be
jointly agreed
Part of the radio parameters need to be
common
QoS Strategies still difficult IF Iub is
bottleneck
Certain capacity upgrades still need to be
jointly coordinated / costs agreed
Reduction in equipment volume in low traffic areas
100% increased rollout speed with given cost
Reduced network and site operating costs
In low traffic areas long term cost advantage
Operators name always visible on phone display
Operators partly maintain control of their own network
traffic (quality & capacity)
Radio QoS for data traffic can be applied
Independence in roaming agreements
(operators broadcast their own PLMN Id)
Compatible with any core network
No CN features required
Independent CN services
No specific terminal requirements
Cons Pros
21 © Nokia Siemens Networks
3G Network sharing – MOCN Fully Shared Radio, Independent Core
RAN owned either by
• Operator A
• Operator B
• JV
• 3rd party (Network
Provider)
CN / EPC form different operators can be
connected to the same RNC / eNodeB
sharing fully all RAN resources
Operators can have shared RAN and
own dedicated RAN networks
Multiple operators use one or more
shared carriers
Common site and cell level parameters
RNC / eNodeB routes the UE’s initial
access to one of the available CN / EPC
nodes
Rel-6 / 8 UEs are connected directly to
own CN / EPC
For legacy UEs the RNC re-routing
functionality is used to find the correct
CN
Characteristics
Shared frequencies
Scenario
MSC/SGSN MSC/SGSN
HLR HLR
RNC
NodeB
Service Platforms
Service Platforms
NodeB NodeB
22 © Nokia Siemens Networks
3G Network sharing – MOCN Fully Shared Radio, Independent Core
Significant reduction in equipment
volume in low traffic areas (1+1+1
config possible)
100% increased rollout speed with
given cost
Reduced network and site operating
costs
In low traffic areas long term cost
advantage
Operators name visible on phone
display possible (supporting UEs)
Independent CN services
Regulator acceptance for spectrum sharing required
Shared radio resource; increased traffic for one is
increased blocking for other
No differentiation in radio features
QoS strategies for data users difficult to use =>
lower data revenue
Sharing partners need to coordinate
all RAN-related operational aspects
RAN planning aspects
equipment vendor selection and equipment
decisions
SIM based Operator logo or NITZ solution required
(non-supporting UEs)
IFHO (exp. take UEs to own network) requires IMSI-
based handover
Cons Pros
23 © Nokia Siemens Networks
Mobile Broadband | SON
NW sharing OSS Sharing
Methods MOCN for 3G / I-HSPA
MORAN for 3G / I-HSPA
Q&A
MORAN and MOCN Pros vs.Cons
24 © Nokia Siemens Networks
Network Sharing management overview
• Management of the shared network doesn’t differ from any other network from
shared network operator point of view – similar tasks and processes can be
utilized
• Processes need to be agreed and developed between sharing operators and
shared network operator – these processes differ from ordinary processes
• Shared network operator is in responsible of taking care of network security and
integrity – a gate keeper role
• Management of shared network is a process issue, good processes in
place will guarantee successful network sharing
Management in network sharing / M. Karhuluoma / September 15, 2010
25 © Nokia Siemens Networks
Network Sharing OSS
• Indirect Management: Common network
domain managed by separate OSS
• Operational responsibility must be
agreed between operators • Neutral 3rd party Managed Services
solution
• Joint venture
• One of the sharing operators
• Sharing operators do not have direct
access to the shared network
• Information sharing between the shared
network operator & the sharing
operators depends upon the solution,
e.g. • On-line automatic data forwarding
• Off-line regular reporting upon a request
• According to mutually agreed processes
• Data intimacy with Joint Venture OSS
for shared part
MIB1:
PLMN ‘344’
MIB1:
PLMN ‘344’
PLMN ‘124’
Common PLMN ‘444’
OSS
OSS Managing Entity
OSS
Filtered Information per
operator
Filtered Information per
operator
Managed Services
Joint Venture
Op. A / Op. B Region
MIB1:
PLMN ‘124’
• Although the example show 3G MOCN shared
network, from an OSS and operational
responsibility perspective the same happens for
MORAN or for LTE and 2G network sharing.
Operator B PLMN ‘124’
Operator A PLMN ‘344’
26 © Nokia Siemens Networks
Joint Venture or trusted 3rd party
What does joint venture or trusted 3rd party do in network sharing management?
• Facilitate smooth and efficient cooperation (esp. governance)
• Meet regulatory requirements (“Walls” between sharing operators)
• Improve operations by re-engineering of processes & best-in-class practices
• Additional economies of scale & scope from global operations
• Risk reduction
• Shorter time-to-market through Build-Operate services
• New business models and structured finance opportunities
Management in network sharing / M. Karhuluoma / September 15, 2010
27 © Nokia Siemens Networks
Mobile Broadband | SON
Q&A Sharing Methods
MOCN for 3G / I-HSPA
MORAN for 3G / I-HSPA
NW sharing OSS
MORAN and MOCN Pros vs.Cons