Академический Документы
Профессиональный Документы
Культура Документы
May 2013
Sharing Methods
NW sharing OSS
Q&A
HLR
MSS/ PS core
RNC/ BSC
Transmission
Base station
Antenna line
OP 1
OP 2
3G
Service Service Platforms Platforms
HLR HLR MSC/SGSN Service Platforms Service Platforms HLR Service Platforms
LTE
Service Platforms
HSS HSS
MME/S-P-GW MME/S-P-GW
BSC
RNC
BTS
BTS
BTS
NodeB
NodeB
NodeB
eNodeB
eNodeB
eNodeB
Sharing Methods
NW sharing OSS
Q&A
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
RAN1602 Flexible Iu
Operator 2 cells
Op2 PLMN ID
Shared NB
Shared Iub
Op1 PLMN ID
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
8 Nokia Siemens Networks
Sharing Methods
NW sharing OSS
Q&A
Non-shared resources:
Iu interfaces Core network elements and services Operator logo on the MS can be provided by NITZ (CN feature)
11
GSM
GSM
WCDMA
depend on connected core Works for home users and roaming users
WCDMA
12 Nokia Siemens Networks
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 HSDSCH, E-DCH and Rel99 DCH are included.
Shared NB Operator 1 Core Network
13
Supporting UEs decode Multiple PLMN List and take the information concerning available CN
operators in network and cell (re-)selection procedures
MP CV-GSM OP
14
15
Total attach/Location Update rejects sent by RNC to UE: one counter for each possible cause code:
16
#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
Redirections performed
Capabilities Can only read the Common PLMN Identity in the Master Information Block
Terminals
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
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
Rel. 6 or later
17
Sharing Methods
NW sharing OSS
Q&A
Characteristics
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-ids 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
Service Platforms
HLR
MSC/SGSN
MSC/SGSN
RNC RAN owned either by Operator A Operator B JV 3rd party (Network Provider)
NodeB
NodeB
NodeB
Dedicated frequencies
19
Cons
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
20
Characteristics
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 UEs 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
Service Platforms
HLR
MSC/SGSN
MSC/SGSN
RNC RAN owned either by Operator A Operator B JV 3rd party (Network Provider)
NodeB
NodeB
NodeB
Shared frequencies
21
Cons
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 IMSIbased handover
22
Sharing Methods
NW sharing OSS
Q&A
24
OSS
Operator A
PLMN 344
OSS
Managing Entity
Managed Services Joint Venture Op. A / Op. B Region
OSS
Operator B
PLMN 124
25
26
Sharing Methods
NW sharing OSS
Q&A
Contacts: Worapol.Wongsrichanalai@nsn.com
Thank you
28