UMTS Network RAN Sharing Solution RAN Sharing Solution RAN Sharing Solution Overview of RAN Sharing Key Techniques in RAN Sharing ZTE RAN Sharing Solution Overview of RAN Sharing Key Techniques in RAN Sharing ZTE RAN Sharing Solution
UMTS Network RAN Sharing Solution
RAN Sharing SolutionRAN Sharing Solution
Overview of RAN Sharing
Key Techniques in RAN Sharing
ZTE RAN Sharing Solution
Overview of RAN Sharing
Key Techniques in RAN Sharing
ZTE RAN Sharing Solution
3
Market Driver
• Hard to acquire site
• Fast deployment in the initial stage
• Win additional revenue to provide network sharing
• Green and environmental concerns
Regulation Driver
• Government encourage network sharing to save resources and protect environment, provided that competition is not weakened
• Government encourage operators to share their infrastructure to expand coverage and foster the market in early 3G deployment
• Operators share one 3G license in some countries
Cost Driver
• Operators are facing challenges of cutting cost when ARPU decreases continuously
• Network sharing can save the rental and number of sites dramatically
• Coverage in rural areas is unprofitable
Drivers of Network Sharing
4
New entrant network cost structure
5%
36%
0%4%2%29%
24%Core Network
RAN
Billing System
Service Platform
NMS
Rollout Cost
Transimission
Incumbent network cost structure
2%
46%
1%5%2%
14%
30%
Source: Coleago Consulting
Typical European 3G site cost breakdown (FY07/08e) Source: Vodafone
Capex
Backhaul (microwave) 37%
RAN equipment 27%
Civil work 36%
Opex
Rentals/ leases 41%
Backhaul (leased lines) 21%
Maintenance 22%
Other (inc energy) 16%
Cost Analysis of Network Construct and Operating
5
RAN sharing is standardized in 3GPP release 6
Only shared carrier RAN sharing need to be standardized. Other forms of
network sharing has no impact on 3GPP standard, they are fully compliant with
pre-R6 standard.
3GPP specification TS 23.251 gives the technology specification of common
carrier RAN sharing, and defines the specification of UE, Node B, RNC and
Core network elements
Standardization of Network Sharing
Carrier ConfigurationNetwork Architecture
Carrier shared
Carrier dedicatedGWCN
Carrier shared
Carrier dedicatedMOCN
6
Network Architecture in RAN Sharing
RAN Sharing GWCN RAN Sharing MOCN Common sharing of RAN equipment and carrier
Gateway core network is shared
UE select operator based on PLMN ID
GW core routes message to the right operator
Common sharing of RAN equipment and
carrier 。
Independent core network
UE select operator based on PLMN ID
RNC routes message to the right operator
f1
Shared carrier
f1
Shared RAN
Shared RNC
Shared NodeB
GW CORE
(MSC/SGSN/MME)
f1
Shared carrier
f1
Shared RAN
Shared RNC
Shared NodeB
f2 f2
Core of operator A
(HLR,GGSN,VAS)
Core of operator B
(HLR,GGSN,VAS) Core of operator A
Core of operator B
7
Shared Carrier RAN sharing Further sharing of RNC and NodeB
Logical independent access network
with each operator has its own
frequency
Balance between cost saving and
network independence
Carriers Strategies in RAN Sharing
f1
F1 of operator A
and B
f1
Shared RAN
Shared RNC
Shared NodeB
CN
Dedicated Carrier RAN sharing
f1
f2
F1 of operator A
F2 of operator B
f1
f2
Shared RAN
Shared RNC
Shared NodeB
Further sharing of RNC and NodeB
Logical independent access network
with each operator has its own
frequency
Balance between cost saving and
network independence
CN
8
Operators Cooperation in RAN Sharing
Geography Sharing MVNO separated network that have different
geography coverage
Provide service to each other through
network sharing agreements
Used to provide national coverage for small
operators or in underserved areas
MVNO has no radio access network. It may
or may not have its own core network. It has
its own VAS platform
MVNO rent MNO’s network to provide
service, but it has its own brand and channel
RAN of operator A
RNC
sharing agreement
f1 f1
RAN of operator A RNC
NodeB
GW Core of operator A
Core of operator A
Core of operator B
RAN of operator B
Core of operator AMVNO
VAS
9
Operators Cooperation Scenarios-Both Operators own frequency resources
When operators have their own frequency resources
Dedicated Carrier MOCN RAN sharing is the most applicable solution
Dedicated Carrier GWCN RAN sharing is also a possible solution
CN A
RAN of B
Shared RAN
CN B
RAN of A
A and B share RAN in some areas.
CN A
RAN of B
Shared RAN
CN B
RAN of A
GW CORE
(MSC/SGSN)
A and B share RAN and part of CN in some areas.
10
Operators Cooperation Scenarios-Only One Operator has frequency resources
A provides shared RAN to B.
CN B
RAN BShared RAN
by B
CN A
RAN A Shared RAN
by A
A and B provide shared RAN in different geographical areas.
When one operator have not their own frequency resources
Shared Carrier MOCN RAN sharing is the most applicable solution
Shared Carrier GWCN RAN sharing has the least possibility.
CN A
RAN BShared RAN
by B
CN B
RAN A
11
Full sharing
Full sharing
National roamingSite sharing
Network Sharing in Europe – UK
Summary of the market
Adequate competition market with five mobile operators:
O2, Vodafone, Orange, H3G, T-Mobile
Operators hope to strengthen their market position through
network sharing
Regulation
UK Government encourage network infrastructure sharing
to improve coverage and service quality, but network
sharing should not threaten competition
Network sharing
T-Mobile and O2 began site sharing and H3G uses O2’s
network for national roaming from 2003
In June, 2007, Vodafone and Orange announced their
network sharing plan, having a long term object of
consolidate current network and jointly build out new
network, to improve coverage, quality and lower cost
In Dec, 2007, T-Mobile and H3G announced their 3G
network sharing plan, aiming at build the largest HSPA
network in Europe
12
Summary of the market Adequate competition market with four operators:
Teliasonera, Tele2, Telenor, HI3G Teliasonera and Tele2 are competitors share one 3G
license and jointly build the 3G network Regulation
Operators are obliged by regulators to provide 100% 3G coverage nationwide, 30% of the coverage must be provided by their own network and the other 70% can be provided by shared network
Network sharing Teliasonera and Tele2 setup their joint venture
Svenska UMTS Nät AB to build and operate their shared UMTS network
Telenor and H3G setup their joint venture 3GIS to build and operate their shared UMTS network, which covers 70% of the population
In April 2009, Telenor and Tele2 setup joint venture Net4Mobility to build their shared GSM and LTE network, and replace their own GSM outdated network
All shared network in Sweden are common carrier RAN sharing
SvenskaUMTS Nät
Net4Mobility3G Infrastructure
Services AB
Network Sharing in Europe – Sweden
13
Network Sharing in Asia
Regulation
Encourage and requires passive & active RAN sharing.
Spectrum sharing is not permitted in some countries.
Network sharing mode
MOCN/GWCN with dedicated carrier.
Renting mode is the main required operation mode.
Some operators’ require priority of resource utilization by dedicated
resource allocation.
Main Features required by Operators
Flexible dynamic resource sharing between operators.
Operator specific resource and license control and management.
Flexible carrier configuration, non continuous segment for example.
Overview of Network Sharing
Key Techniques in RAN Sharing
ZTE Success Stories
Overview of Network Sharing
Key Techniques in RAN Sharing
ZTE Success Stories
15
3GPP Consideration on RAN Sharing
Deploying RAN sharing in the
network, should face some key
issues: message router, PLMN
ID display and mobility
management
Regarding the various UE type
and compatibility, the network
should solve the issues on all
UE mode. And ZTE consider
the UE mode as pre-R6 mode
and R6 mode when they stay in
idle or connected status.
Key Technologies:
Message Routing & Network Logo display
16
3G Message Routing – GWCN with Support UE (R6)
GWCN:
―The system broadcasting information includes network sharing status. UE could selects the network which it can attach.
―Then UE send the request to the SGSN and the SGSN could determine if the UE belong to the any one of it’s shared operators.
―SGSN send back the accept or reject information.
17
3G Message Routing – GWCN with Non Support UE
GWCN:
―The system broadcasting information includes network sharing status. UE cannot decode the network sharing information, choose the common information and send to CN
―Then UE send the request to the SGSN and the SGSN could determine if the UE belong to the any one of it’s shared operators.
―SGSN send back the accept or reject information.
18
3G Message Routing – MOCN with Support UE
MOCN:
―The system broadcasting information includes network sharing status. UE decode the network sharing information, choose the correct CN
―Then RNC send the request to the correct SGSN depends on the sharing information decoded by the UE and the SGSN could determine if the UE belong to the any one of it’s shared operators.
―SGSN send back the accept or reject information.
19
3G Message Routing – MOCN with Non Support UE––Network Protocol Updating
Common frequency Sharing
In MOCN:
- Network update to support R6 signaling protocol with reroute command.
- Reroute command may repeat some times and increase the network load and time delay.
20
PLMN ID/Name Display Overview
The PLMN Name or
Operator Name is mapped
from the PLMN
ID(MCC+MNC).
How UE display the correct
PLMN ID is a key issue
because pre-R6 UE can only
read primary PLMN ID from
the broadcasting information.
RAN Updating and NITZ can be major methods for Name Display, and SIM Card customization can be auxiliary method.
21
PLMN ID/Name Display – SIM Card Updating
The UE could store at least 10 PLMN ID
and the corresponding operator name.
The operators write the sharing network
PLMN ID which is a common ID into the
SIM card. And UE could display the
correct operator name by the common ID.
i.e, Operator A PLMN ID = 460 01
i.e, Operator B PLMN ID = 460 03
If Operator A and Operator B have a
sharing network and make a common ID
for that, Common ID = 460 08
Then Operator A SIM store:
460 01 = 460 08 = “Operator A Name”
And Operator B store:
460 03 = 460 08 = “Operator B Name”
The Operator Name could display Operator A 460 01 Operator B 460 03
Common ID 460 08
Operator A & Operator B
460 01
460 08
Name A
Name A
460 03
460 08
Name B
Name B
Sharing
Operator A Operator B
22
PLMN ID/Name Display – RAN Updating to R6
Add a PLMN ID list in the broadcasting
information in MIB field which need RAN
Updating
R6 UE could read the whole list and find out
the correct PLMN ID and display the operator
name.
The pre-R6 UE could not read the list while
only read one PLMN ID, normally this ID will
be the common ID which is one of the sharing
operators’ ID. Then the UE perhaps could not
judge the correct operator’s name. That means
the UE could be allowed register but could not
display the correct operator name
460 01
460 03
460 01
Operator A Sharing Operator B
460 01
Operator A
23
PLMN ID/Name Display –NITZ
Network Supports NITZ, Network Identity Time Zone, which includes the local time , date and the operator name.
The NITZ information will include the correct PLMN ID and operator name after the UE register success.
UE decode the NITZ information and display the operator name, also synchronizing the time and date.
When UE dose not support NITZ, use the default content.
CMCC Sharing China Unicom
①
Register
Requirement
②
NITZ include Operator ID
After Register
③
Display the Operator Name
24
Mobility – Sharing Network Mobility Management
Handover
based on SNA
Location
Area Update
Cell Update
Based on SNA
• Area consisting of one or more LA’s to which access can be controlled. .
• CN sends SNA and LA mapping table to RNC, when RNC initiation.
• After UE attachment, the mapping among the SNA and TMSI is send to RNC and stored in RNC.
• During the connected status – CELL_DCH, handover is supported
– Handover between the shared network and the non shared network.
– Handover inside the shared network.
• Location area update and cell update are supported based on the SNA when UE is idle status or no connected status
– Update procedure between the shared network and the non shared network.
– Update procedure inside the shared network
SNA
( Shared Network Area )
Overview of Network Sharing
Key Techniques in RAN Sharing
ZTE RAN Sharing Solution
Overview of Network Sharing
Key Techniques in RAN Sharing
ZTE RAN Sharing Solution
26
Base Station Sharing
BP resource and RU sharing
Static/Dynamic Power Control
Large capacity and flexible configuration
Radio Network Controller Sharing Resource distribution and management
Transmission interface resource sharing
Main Investment
O&M Sharing Operation & maintenance mode
Access authorization control and management
Features launching and license
Base Station
Operation &
Maintenance
Radio network controller
ZTE RAN Sharing Solution Overview
27
Base Station-BBU Sharing
UMTS BP BoardUL 192CE, DL
192CE/BP
UL 15Mbps, DL
43.2Mbps/BP
Module Name Shared Dedicated Min/Max Configuration
CC Board Y N 1/2
FS Board Y Y 1/2
UBPG/BPC Board Y Y 1/5
SA/SE Y Y SA: 1/1, SE:0/1
PM Module Y N 1/2
FAM Y N 1/1
Some boards can
be dedicated for
multi-PLMN
28
Base Station-RRU Sharing
PLMN1 ID
PLMN3 ID PLMN4 ID
PLMN2 ID
Cell-1Cell-2Cell-3Cell-4
Operators can share one RRU based on cell level.Operators can share one RRU based on cell level.
BSC/RNC
RRU sharing:
Dedicated carrier:
Operators
distinguished by
frequency point.
Shared carrier:
operators
distinguished by
PLMN-id in cell
broadcasted
information.
Sector
PLMN-1PLMN-2PLMN-3
Sector
29
RRU Support Multi PLMN Configuration (3G)
RRU Unit
RSU Module
Multi-PLMN4 carriers configured to 4 operators
BBU
BBU
20 MHz
Operator AOperator B
BBU
BBU
S1+S1+S1+S1
20MHz
5MHz
20MHz RF Bandwidth4 Carriers Supported
RSU
RSU
RSU
RSU
RSU
RSU
RSU
RSU
S111+S111+S111+S111 S222+S222+S222+S222
Multi-PLMN configuration
BBU
BBU
RSU
RSU
RSU
RSU
RSU
RSU
RSU
RSU
RSU
RSU
RSU
RSU
Operator D
Operator A
Operator BOperator C
1 RU to 3 RU 3 RU to 6 RU
30
BP Resource Sharing Methods
BP Flexible BP Flexible AllocationAllocation
BP Hybrid BP Hybrid AllocationAllocation
BP Dynamic BP Dynamic SharingSharing
available available 09Q4 09Q4 09Q409Q4
BP resources dynamic shared by operators
BP resources static reserved by operators
Dynamic shared + Reserved shared
Operator COperator BOperator A
Operator BOperator ADynamic
Operator BOperator ABP PoolBP Pool
BP BoardBP Board BP BoardBP Board Three types of BP resources sharing for different scenarios
31
PA Output Power Sharing- Static Configuration
Static output
power
configuration
Static output
power
configuration
Average power allocation
Multi operators have same TOC.
Multi operators have un-equivalent TOC.
Un-equivalent power allocation
PA Output power
time
80W
32
RNC Sharing and Dedication
BGSN
BCTC
BPSN
Shared Shelf
BGSNOperator 1
BGSNOperator 2
RNCDedicated
Shelf Control plane sharing
User plane dedicated and sharing management
Interface dedicated and sharing management
33
ZTE innovative solution for Message Routing
RAN support NRI analysis, avoid CN upgrade
and reiterate message procedure
For initial access, MS will send IMSI to RNC,
and RNC will extract the PLMN-id from IMSI,
then the attach message is directly routed to
the correct CN.
For the Non-initial access, MS will send
TMSI to RNC, and RNC will get NRI through
TMSI.
If the NRI is valid, the NRI will be
analyzed, will be sent to corresponding
CN.
If the NRI is invalid or can not be
correctly decoded, such as roaming
subscriber’s H-PLMN is not matched in
NRI codes, RNC will reiterate all CN
supported by the carrier.
NRI Valid
NRI Invalid
CN A CN C
reiterate all CN
IMSI
PLMN ID
Find correct CN
TMSI
NRI
34
RNC Interface Resource Sharing & Dedication
Node B
Cell 1Cell3
Cel
l 2T
RX
2
TRX 1 SGSNSGSNMSCMSC
Resources Pool: dynamic sharing Dedicated interface: Static reservation (09’Q4)
RNC
Iu-CS
Iu-b
Iu-PS
Iu-r
Iu-b
Iu-r
All the interface
35
Iub Transmission Resource Dedication
ATM/IP(3G)
TDM/IP(2G)
BTS/NodeB BSC/RNC
Dynamic pooling Flexible partitioning Hybrid mode
—Shared bandwidth
—Operator A bandwidth
—Operator B bandwidth
Realized 10’Q4 10’Q4
Dynamic pooling: high usage efficiency. Flexible partitioning: Convenience to separate. The hybrid one : CAC bandwidth assignment and congestion avoidance.
36
QoS Level for operators by PLMN in RNC
ZTE BSC/RNC could provides the access
control, call control and load balance by the
operators’ QoS level
– Operators could be set with different priorities,
the system resource will be distributed to the
high priority operator first
– For each operator, the services priority could
be defined separately.
Services Priority
Operators Priority
When the limitation occur , for the transmission or the code resource, the lower level UE will be handed over to lower speed or other cells
128K
64K
37
QoS & SW Setting for N
ZXWR UTRAN Sharing Solution Roadmap
Operator B Operator N
Operator A
U9.2
V408
2010Q4
U10.1
2009Q4
2008UTRAN Sharing Phase1:
Multi PLMN Support
Basic RAN Sharing Support
RAN Sharing with Dedicated Carrier
Shared Networks Access Control
UTRAN Sharing Phase2:
RAN Sharing with Shared Carrier
Operator Specific FM/PM/CM
UTRAN Sharing Phase3:
Operator QoS Priority
Operator Specific Iub/Iur Transmission
Operator Specific Feature Control
ReleasedReleased PlannedPlannedPlanningPlanning
Operator N CN
Operator A CN
Total available resource:
BP CE, RNC capacity,
Backhaul bandwidth
Reserved resource for A
Reserved resource for B
Resource dynamically shared
Operator A
(Host)
Operator A
(Host)
Operator B
(Joint Venture)
Operator B
(Joint Venture)Operator N
(Renting)
Operator N
(Renting)
Read OnlyRead/Write
QoS & SW Setting for A
OMCOMC
38
Unified EMS System,Multiple North Bound Interface
Operator B NMS
Operator B NMS
Operator AOperator A
Shared RAN
Shared RAN
Ift-N InterfaceIft-N Interface
Operator A NMS
Operator A NMS
Operator BOperator B
Ift-N Interface
Ift-N InterfaceShared EMSShared EMS
•A shared NETNUMEN™M31 manages all O&M functions, mainly including:
RNC/BSC/Cell level configuration (Hardware, Transmission,)
RNC/BSC/Site level software upgrade and status query.
RNC/BSC/Site level FM and PM.
•LMT /EMS will not be distinguished according to different operators.
•Support independent NMS interface.
39
North-bound Interface
CM/PMCM/PM FM/IMFM/IM CM/PM/FM/IMCM/PM/FM/IM CM/PMCM/PM FM/IMFM/IM
Operator AOperator A Operator BOperator B Operator COperator C
The maximum number of concurrent connections to NMS is 4Cell-level FM/PM/CM can be distinguished on NBI for different operators
Host Operator A Partner Operator B Partner Operator C
Host Operator A’s cells R/W --- ---
Partner Operator B’s cells R/W R ---
Partner Operator C’s cells R/W --- R
EMS
40
2010-8-4
Resources & Features Control between Operators License control principleDate authorization:Network operation is valid until a defined date.
Feature authorization: Different cell, BSC or RNC can be authorized with different function.
Capacity authorization:Restrict authorized network hardware capacity based on TRX or Cell. Support capacity reconfiguration without reactivation.
All three methods can be used in conjunction with each other.
Operator A Operator B Implement Date
Capacity EMS Level 100K TRX 50K TRX 2008Q4
Feature Cell Level FR、HR、AMR FR、HR 2010Q4
License control type
Example:
41
Summary for Network Sharing
Architecture: GWCN and MOCN
Carrier: Dedicated or Shared
Network Sharing Specification detailed in R6
Options for Network Name Display in Pre-R6 Terminal
ZTE RAN Network can be fully shared, and Resources flexibly
controlled.
ZTE Innovative solution to avoid CN upgrade for pre-R6
terminals in RAN Sharing Solution.