RAN Sharing Solution
Agenda 1.RAN 1. RAN Sharing Technical Technical Overview 2.Pilot 2. Pilot MORAN MORAN Solution Solution 3.RAN Sharing Reference
Agenda 1.RAN 1. RAN Sharing Technical Technical Overview 2.Pilot 2. Pilot MORAN MORAN Solution Solution 3.RAN Sharing Reference
Network Sharing Architectures
Carrier Configuration in RAN Sharing Dedicated Carrier Configuration
Shared Carrier Configuration
One / More Carriers Dedicated for one
One Carrier for multiple Operators
Operator
Transmit power shared between the
Carriers Not Shared between Operators
Operators.
Dedicated Carrier Configuration
Shared Carrier Configuration
Shared BSC/RNC
Shared BSC/RNC
Operator A Operator B
Operator A
f1 f2
f1 f2
Shared BTS/NodeB
f1
f1
Operator B
MORAN
MOCN
Shared BTS/NodeB
Challenges from Shared Carrier Configuration GSM MOCN vs 3GPP Release CN>=R10 BSC>=R10
CN
BSC>=R10
UE>=R10
OK
OK
UE
OK NITZ/SIM customization
At least one CN >R10 NITZ/SIM customization
BSC
UMTS MOCN vs 3GPP Release CN>=R6 RNC>=R6
CN
RNC>=R6
UE>=R6
OK
OK
UE
OK NITZ/SIM customization
At least one CN >R6 NITZ/SIM customization
RNC
Network Name Display in MOCN R6 UE Multi-PLMN broadcasting Pre-R6 UE
HPLMN ID
Common PLMN
Roaming UE Common PLMN
SIM Customization for common PLMN
Network Name display
NITZ from CN to UE Shared carrier
MOCN with Pre-R6 Terminal in UMTS MOCN: -
HLR C
MSC/SGSN C
MSC/SGSN B
MSC/SGSN A
Non-support UE
RNC
1.RRC Connection Established
At least one CN should support
3.Initial UE (Attach request, Redirect attempt flag)
3GPP Release >R6
2.Initial Direct Transfer
4.Identity Req
-
National and international preR6 users can not be recognized.
4.Identity Req IMSI Not allowed for HPLMN of IMSI
5.Re-router command
PLMN List in Radio:
6.Initial UE (Attach request, Redirect attempt flag, IMSI …) Not allowed for HPLMN of IMSI
7.Re-router command 8.Initial UE (Attach request, Redirect attempt flag, IMSI …) 9.Authraction & Ciphering
t
10.Re-router completed 11.Attach accpet 12. Attach Completed
GSM in R10 can support this procedure.
GSM RAN Sharing - MORAN Operator A
Shared BSC
Shared BTS Cell A
PLMN1
TRX1…
PLMN2
TRXm…
Cell B
Operator B
BSC and BTS for Multiple Operators Cells
Abis resource pools
Cells C1
Exclusive Pool P1
Cells C2
Exclusive pool P2
Cells with dedicated resource
Dynamically select
Dynamically select
Dynamically select Shared pool P3
Dedicated PCU resource
Other operators’ cells
Shared PCU resource
C1 belong to operator A C2 belong to operator B P1 is exclusive pool for operator A P2 is exclusive pool for operator B P3 is shared pool for A&B
Abis Transmission Sharing(V10R1)
PCU Resource Sharing (V10R1)
UMTS RAN Sharing
–
MORAN
RRU Unit
Multi-PLMN 4 carriers configured to 4 operators
20MHz RF Bandwidth 4 Carriers Supported
Operator A Operator B
5MHz
20MHz
RSU Module
20 MHz
Multi-PLMN configuration Operator A Operator B Operator C Operator D
R S U
1 RSU to 3 RSU
BBU S1+S1+S1+S1
R R R S S S U U U
BBU S111+S111+S111+S111
R R R R R R 3 RSU to 6 RSU S S S S S S U U U U U U
BBU S222+S222+S222+S222
UMTS RAN Sharing – Transmit Power in MOCN TP CS
TP user’s service experience is kept in priority.
CMPak users are serviced in best effort.
TP PS CMPak CS
> 内部公开
Example: TP CS > TP PS > CMPak CS > CMPak PS.
CMPak PS
Power CAC Threshold 100% 85%
TP CS/PS
75%
CMPak CS/PS
When cell power load is higher 80%, only TP users are accessed.
When TP PS users access and power is shortage:
CMPak PS downgrade-> CMPak CS downgrade(if allowed)-> TP PS downgrade.
When TP CS users access and power is shortage:
CMPak PS downgrade-> CMPak CS downgrade(if allowed)-> TP PS downgrade ->Lower priority TP CS downgrade (if allowed)
When power load by online users increases:
The lowest priority PS to downgrade-> The lowest priority PS to switch to FACH/RACH>The lowest priority onlines users to release the RRC connection.
UMTS RAN Sharing – HSUPA Number in MOCN CN of Operator A
CN of Operator B
Shared UTRAN HSUPA user of operator A
HSUPA user of operator B
UTRAN calculates E-DCH user of each MOCN operator in real time. Only the users which are from the operator that its total E-DCH online user number is under the pre-defined threshold are allowed to access.
The users which are from the operator that its total EDCH online user number is above the pre-defined threshold are not allowed to access.
MOCN
Benefits: Certain E-DCH resource allocated for each MOCN operator is guaranteed, based on pre-defined E-DCH user proportion, to get the most of E-DCH services.
> 内部公开
UMTS RAN Sharing – BP Resource Sharing CE resource partition For example A:B= 40%:60%
Operator A 40%
Operator B 60%
CE resource can be partitioned among
operators.
100%
No congestion
> 内部公开
Shared by Operator A and Operator B
All operators share the same pooled
capacity when the overall CE cost by traffic is below the total CE.
CE congestion happens.
Operator A 50%
Operator B 50%
When admission for a new call fails
for CE limited, congestion control is performed for the operator whose occupied CE is above the partitioned
Operator who occupied CE above the allocated ratio is force to release resource.
Operator A 45%
Operator B 55%
ratio.
The relived CE resource is used for the
new call admission.
UMTS RAN Sharing
–
Control Congestion
> Internal Only
Power CAC Threshold Established on RACH/FACH
100% 85% 82% 80%
CS RAB CS RRC PS RAB/PS RRC
Power is shortage for PS RRC 13.6kbps
Access PS RRC with 3.4kbps
Differential RRC signal priority. Higher CAC threshold for CS RRC signal.
When the load of power is high, CS RRC is access and PS RRC is bear on RACH/FACH
Power
Start RRC congestion control
If power is higher than the level of RRC signal congestion, the online PS data and PS signal with lower priority is selected to:
RRC signal congestion RRC signal congestion recover
Downgrade PS RAB bit rate.
Switch PS RAB to FACH/RACH.
Force PS RAB or PS RRC signal to release.
Time Stop RRC congestion control
Stop the actions until the power level below the recover threshold.
UMTS RAN Sharing Resource Congestion –
PLMN Based Operator QoS Priority
……
Operator A
……
Streaming
Operator B
Streaming
Voice/Video
……
Voice/Video
Service Priority A
Different 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.
Service Priority B Traffic Class Conversational _Voice/Video
SIP
Streaming
ARP(RAB)
Interactive(THP-Traffic Handling Priority)
Background
Op. A
Op. B
Op. A
Op. B
Op. A
Op. B
1~5 Op. A
1~5 Op. B
6~10 Op. A
6~10 Op. B
11~15Op. A
11~15Op. B
Op. A
Op. B
2
15
15
14
13
10
9
9
8
8
7
7
6
7
6
7
15
15
13
12
10
9
6
5
5
4
4
3
4
3
11
15
15
12
11
10
9
3
2
2
1
1
0
0
0
UMTS RAN Sharing - Mobility TP Cell
TP Cell
TP Cell
CMPaK Cell
CMPaK Cell
Shared Cell (MOCN) CMPaK Cell
Mobility in MOCN 1. 2.
Operator Oriented Handover procedure Shared Network Access Code
Mobility in MORAN
UMTS RAN Sharing Shared BTS/Node B
–
Transmission Operator A Operator B Operator C
Shared BSC/RNC
Trans. Dynamic Sharing IP Planning (Ether #1): 1. IP1@Operator1: 2G UP,2G CP 2. IP2@Operator2: 3G (n)rt-DCH, HSxPA 3. IP3@Operator3: 2G UP, 2GCP 4. IP4@Operator4: 2G/3G/MP
Transmission Sharing Strategy: 1. Common Dynamic pooling 2. Overbooking & Minimal Reservation 3. Service Priority
LTE RAN Sharing PLMN A
Shared eNodeB
Shared eNodeB Operator A
PLMN B
Frequency 1 Operator B
PLMN A + PLMN B
Frequency 1
Operator A + Operator B
Frequency 2
Dedicated Carrier (V2.1)
Shared Carrier (V2.1)
1. Maximum Four PLMNs per LTE RAN 2. Msg reroute as in GSM and UMTS Multiple PLMN Broadcasting
LTE RAN Sharing
–
RRC Resource
The feature will be available in LR15.
RRC user Partition in shared carrier
Each
operator can flexibly configure its RRC ratio and t he Slide Window radio to maximizing
utilization of RRC user resources. If
the number of RRC UEs of either of two operators does not exceed the ratio, the RRC users of
the two operators can be accessed properly. If the number of RRC users of operator A exceeds the predefined threshold, the eNodeB limits access of new RRC users of operator A, and continues access the RRC users of operator B.
LTE RAN Sharing
–
QoS
The feature will be available in LR15.
PLMN Based Operator Qos Priority Example of PLMN-level QoS mapping
LTE RAN Sharing Shared eNodeB
–
Transmission Operator A Operator B Operator C
Operator A
60%
Physical link OverBooking Operator B
40%
Trans. Dynamic Sharing IP Planning (Ether #1): S1/X2 user plane VLAN per operator S1/X2 control plane VLAN shared by operators OAM VLAN shared by operators
Transmission Sharing Strategy: 1. Common Dynamic pooling 2. Overbooking & Minimal Reservation 3. Service Priority
EMS in RAN Sharing
Host Operator
Guest Operator
Independent north-bound interfaces for multi-vendor. Possible NBI customization. Guest operator can have query rights, no creation, modification or deletion rights.
Intra/Inter Vendor Compatibility NMS
Admin
Other vendor
Core of operator A
Core of operator B
NMS
Admin
Issues: 1. Inter vendor Iur 2. North bound interface
Iu/Iur IOT Reference Interface
ZTE RAN Version
Vendor
Equipment
Version (1) MSC, HW: AXE MSC R12.1 SW: R 12.1 (2) MGW, HW: R6.1 SW: R6.1 (3) SGSN, HW: 2010B SW: 2010B (4) GGSN: HW: 2010B SW: 2010B HW: Mkvi SW: 13Bcp00
Iu
UR12
Ericsson
MSC MGW SGSN GGSN
Iu
UR12
Ericsson
SGSN
Operator
3GPP Bearer Version
Date
Country
2013/10
South Sudan
MTN
R8
IP
2013/10
Beijing ZhuYu Lab
China Unicom
R8
IP
2014/01
Algeria
Orascom Telecom
IP
IP
MSC HW: MSC9880
Iu
UR12
HW
MSC MGW SGSN
MSC SW:V100R009C00SPC700 MGW HW:UMG8900 MGW SW:V200R009C02SPC205 SGSN HW:SGSN9810 SGSN SW: V900R011C01SPC300
Iu
UR12
HW
SGSN GGSN
SGSN HW: USN9810 ATCA SGSN SW:V9 R10 GGSN HW:UGW9811 ATCA GGSN SW:V9 R9 MSC, HW: V100; SW: R009 C00 MGW, HW: V200; SW: R009C02 SGSN, SW: R09 GGSN, SW: R11
Iu
UR11.2
HW
MGW MSC SGSN GGSN
Iur Iur Iur Iur
UR12 UR11.2 UR12 UR11.2
Ericsson HW NSN NSN
RNC RNC RNC RNC
W12B V900R014C00 RU30-RN6.0_2.0 RNC2.0 CD1.0
2013/ 10
V elez uela
Telefonica Movistar
2012/07
Russia
Beeline
R8
IP
2013/09 2013/01 2013/09 2013/01
Sweden Thailand Sweden Thailand
Sweden AIS Hi3G AIS
R6 R8 R6 R8
IP IP IP IP
EMS-NMS IOT Reference Functi on
FM FM PM/CM FM PM/CM FM FM PM/CM PM/CM FM FM PM/CM PM/CM FM PM PM FM PM FM FM PM PM/CM PM FM FM PM PM CM CM FM PM/CM FM PM CM
I nte rfa ce
CORBA CORBA FILE CORBA FILE CORBA SNMP FILE DB ASCII CORBA FILE DB ASCII FILE FILE SNMP DB SNMP SNMP FILE FILE FILE CORBA DB DB FILE FILE FILE CORBA NBI SNMP FTP FTP
ZTE Product
NetNumen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 NetNumen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 NetNumen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 NetNumen-M31 NetNumen-M31 NetNumen-M31 NetNumen-M31 NetNumen-M31 NetNumen-M31 NetNumen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 Net Numen-M31 NetNumen-M31 NetNumen-M31 NetNumen-M31 NetNumen-M31
Radio Technology 2G/3G 3G 3G 2G 2G 3G 3G 2G/3G 2G 2G 3G 2G 2G 2G 3G 2G/3G 3G 3G 3G 2G/3G 2G/3G 2G/3G 2G/3G 2G/3G 2G/3G 2G/3G 2G 3G 3G 2G 2G/3G 2G/3G 2G/3G 2G/3G
3rd pa rty ve ndor
IBM HP Aircom HP Aircom Bright Oceans AIS Bright Oceans Bright Oceans Bright Oceans Bright Oceans Bright Oceans Bright Oceans Bright Oceans AIS Aircom HP Aircom HP HP Aircom Telkomsel PIWorks IBM Ucell Ucell Aircom AIS AVEA Nokia Siemens Telenor AIS AIS AIS
3rd pa rty Product
Country
Ope ra tor
NetCool TeMIP Optima TeMIP Optima NetWatch NMS NetWatch NetWatch NetWatch NetWatch NetWatch NetWatch NetWatch NMS Optima TeMIP Optima TeMIP TeMIP Optima SML NetworkCPR NetCool PQ PQ
Hong Kong Turkey Turkey Pakistan Pakistan China Thailand China China China China China China China Thailand South Africa Austria Austria Indonesia Portugal Portugal Indonesia Uzbekestan Uzbekestan Uz bek es tan Uz bek es tan Afghanistan Thailand Turkey Venezuela Hungary Thailand Thailand Thailand
CSL AVEA AVEA Telenor Telenor China Unicom AIS China Unicom China Unicom China Unicom China Unicom China Mobile China Mobile China Mobile AIS CellC H3G H3G Indosat Sonaecom Sonaecom Telkomsel Ucell Ucell Uc ell Uc ell Etisalat AIS AVEA Digitel Telenor AIS AIS AIS
Optima NMS NMS NetAct 5.1 Telenor NBI AIS selfmade AIS selfmade AIS selfmade
Agenda 1.RAN Sharing Technical Overview 2.Pilot MORAN Solution 3.RAN Sharing Reference
Intra/Inter Vendor Compatibility CMPak NMS
Core
EMS
CMPak
TP Core
FireWall FireWall
Trust Domain
NMS
NMS
EMS
EMS
Trust Domain
Untrust Domain
Untrust Domain
E///,Huawei
ZTE Inter-Vendor
TP Core
Core
FireWall
FireWall
NMS
EMS Trust Domain
Trust Domain
Untrust Domain
Untrust Domain
ZTE
ZTE Intra-Vendor
Networking: 1. EMS northbound interface for both CMPak and TP 2. Inter-vendor Iur is Optional.
Site Configuration
–
RRU
900MHz R8881
1800MHz R8882
CMPak
2100MHz R8881
CMPak
TP
CMPak
TP
PA1
PA
TP
PA2 882.5
905
880
906 889
915
1710 1717.5 Notes: Different RRU hardware, different Bandwidth available
IBW 40MHz 1765 1730 1737.5
1785
Site Configuration
–
BBU
CE resource partition For example A:B= 40%:60%
TP 40%
CMPak 60%
100%
No congestion
Shared by Operator A and Operator B
CE congestion happens.
TP 50%
CMPak 50%
Operator who occupied CE above the allocated ratio is force to release resource.
TP 45%
CMPak 55%
1. Site dimensioning needs to consider GSM TRX and UMTS Cell limitation 2. FS board limitation needs to consider if the number of RRU changes 3. Dedicated b d fo ch c ier is ok
Site Solution
–
uFFD022 uFFD022 uFFD023 uFFD024 uFFD025 uFFD026 uFFD027 uFFD028 uFFD029 uFFD030 uFFD022
51 54 63 52 56 62 57 53 55 61
R8881 S9000(B8B) R8882 S1800(B) R8861 S2100(B8B) R8881 S9000(B8B) R8882 S1800(B) R8861 S2100(B8B) R8881 S1800(B8B) R8881 S9000(B8B) R8882 S1800(B) R8861 S2100(B8B)
889
1710
UMTS Cell Number enough CE needs dimensioning based on traffic
915
1765
Site Solution
–
uFFD024
R8882-GUL9018D
uFFD024 uFFD024 uFFD024 uFFD024 uFFD024 uFFD024
52 62 63 51 61 53
R8882-GUL9018D R8861 S2100(B8B) R8861 S2100(B8B) R8882-GUL9018D R8861 S2100(B8B) R8882-GUL9018D
PA900
PA1800
889
1710
UMTS Cell Number enough CE needs dimensioning based on traffic
915
1765
Controller Configuration RNC Rack
1 2 3 4 5 6
–
RNC
Control Plane
7 8 9 10 11 12 13 14
R R R R U U U U P P P P E E G G P P B B
O M M E G B S
O O O R D C C C C M M M U M M M M M M P P P P P P P P E E E E E E G G G G A D B FSFS P P TI S B B
R R R R U U U U P P P P E E G G P P B B
R U P E G B S
R C C C U M M M P P P P E E E E G G G G B FSFS P S B
R R R R U U U U P P P P E E G G P P
C M P E G B
C C C C C D D D D M M M M M M M M M P P P P P P P P P E E E E G G G G B FSFS P
C D D D D M M M M M P P P P P E G P B
•
CMP is static allocated with each UMTS cell
DMP is resource pool, dynamically shared
•
User Plane •
RUP is resource pool, dynamically shared
Interface Card •
EGPB can be physically allocated btw operators.
•
EGPB can be one resource pool, dynamically shared
Switch and Clock •
•
EGBS and EGFS are switch boards, common part. OMP is for O&M, common part.
Controller Configuration Resource Sharing Solution –
Control Plane •
TP &CMPak can share same CMP pool, or physically
separated. •
DMP in one resource pool, dynamically shared btw TP &
CMPak
User Plane •
RUP in one resource pool, dynamically shared btw TP &
CMPak
Interface Card •
•
EGPB can be in one pool or physically separated. Suggestion: physically separation to simplify IP networking
Switch and Clock
Transmission Configuration
TP Core Switch
CMPak Core Switch
UMTS RAN Sharing
–
Access Procedure
TP Core Switch
CMPak Core Switch
UMTS RAN Sharing
–
TP RAN
Handover Procedure CMPak RAN
CMPak RNC TP RNC
CMPak User
UMTS RAN Sharing
–
Handover Procedure
TP RAN
CMPak RAN
CMPak RNC TP RNC
CMPak User
UMTS RAN Sharing
–
Handover Procedure
TP RAN
CMPak RAN
CMPak RNC TP RNC
CMPak User
EMS Sharing (TP as Host)
TP
CMPak
Independent North bound interface, Corba for FM, and FTP for CM/PM recommended TP Operator has complete rights. CMPak as guest, has only query rights, no creation, modify and etc.
UMTS RAN Sharing
–
Feature Control License Control based on PLMN ID
Feature authorization Cell Level
Capacity authorization
BSC/RNC Level
Operator A Features: E-EDGE Precise Paging HSDPA HSUPA ……
EMS
BSC/RNC
Operator B Features: GSM HR eMLPP MBMS AMR ……
EMS Level
BSC/RNC Level
Feature authorization: Different cell, BSC/RNC can be authorized with different function based on PLMN ID.
Capacity
authorization:
hardware capacity
Restrict
authorized
based on Cell.
Support
network capacity
reconfiguration without reactivation. E x a m p l e : Item
Level
Operator A
Operator B
Capacity
EMS Level
20K Cells
10K Cells
Feature
Cell Level
HSPA/E-EDGE
MBMS/HR
Agenda 1.RAN Sharing Technical Overview 2.Pilot MORAN Solution 3.RAN Sharing Reference
H3G: the Best Mobile Network in Austria
Customized Relocation Solution
Scope: 4,000+ BTSs/3,100 hops MW to be swapped
Reuse: NSN’s BTS cabinets and 10,000+ Operator Ts
Saving costs: 1,500 Euros per site
Target: LTE/DC-HSPA+ , covers 94% of Austria population
In Sep. 2011: Accomplished the cutover of all 4,000+ sites, 3 months ahead of schedule
The Best Mobile Network in Austria
H3G Austria topped No.1 in CONNECT test in 2011.
The best network in Austria, even in DACH region
In Dec. 2011：Commercial launch of
Subscriber increased by 26% within 1 year
the first HSPA+/LTE in Austria
The 10-fold increased in network throughput
The best LTE at the best price
H3G: Motivation of RAN Sharing Spectrum 1st PLMN (MIB)
A1
A2
H1
H2
H3
O1
O2
O3
PLMN1
PLMN-A
PLMN-H
PLMN-H
PLMN-H
PLMN-O
PLMN-O
PLMN-O
PLMN-T
PLMN-T
PLMN-T
2nd PLMN (MIB)
A3
H3G Austria H3GA
T-Mobile
Strong Points
PLMN-A
T1 PLMN-T
T2 PLMN-T
T3 PLMN-T
T-Mobile
Best UMTS network
Has a mature GSM coverage
in Austria
in Austria UMTS network is served by legacy equipment with
Motivation
Improve voice
service in indoor and rural area
Shared RAN of H3GA Shared RNC
Result
network
High ARPU subscribers need higher throughput
RAN Sharing Data service’s coverage and performance
be improved by
can be greatly improved by using H3G
roaming to partner’s
Austria’s UMTS network
network
Node B f1 f2 f3
legacy NodeBs can not provide a competitive
Solution Voice continuity can
Shared Node B & Carriers
limited performance
f1
Protect Investment
Benefit
Better user experience and higher service continuity
H3G: RAN Sharing Status Spectrum 1st PLMN (MIB)
A1
A2
H1
H2
H3
O1
O2
O3
PLMN1
PLMN-A
PLMN-H
PLMN-H
PLMN-H
PLMN-O
PLMN-O
PLMN-O
PLMN-T
PLMN-T
PLMN-T
2nd PLMN (MIB)
T-Mobile
H3G
Orange
Subscribers Information
PLMN-A
T1 PLMN-T
H3G
Shared RNC
T2 PLMN-T
Node B f1
Shared RNC
Phase 1: MOCN with T-Mobile
Node B
Node B f1 f2 f3 Shared Node B & Carriers
PLMN-T
PLMN-H PLMN-T PLMN-O
Traffic Migration to H3G
Shared Node B & Carriers
T3
T-Mobile
Shared RAN of H3GA
Shared RAN of H3GA
f1 f2 f3
A3
f1
Phase 2: Three Operators Shared Network after purchasing Orange
H3G: Key Technologies of RAN Sharing Cell with PLMN-H MPL PLMN-T MN
… …
H3G
Spectrums Dedicate carrier or shared carriers Wide band radio unit IOT between Different Vendors Rich IOT experience Standard solution for R6 CN Innovative solution for legacy CN Routing Technologies MPLMN IMSI based message routing
• •
• • •
T-Mobile Orange
H3G
• •
Handover and Neighbor Relationships Large scale NR design IMSI based HO Resource Management Shared network access control Operator specified CE resource Operator specified transmission
• •
QoS Assurance Operator QoS Priority
3G SIM IMSI = Operator B Target: Operator B 3G
Operator A 3G
• •
Operator specified RNC Resource
Operator A 3G
Operator A/B shared 3G
Operator B 3G
Summary
Two types carrier configuration, MORAN and MOCN
MORAN is simple solution, no need 3GPP upgrade on Core and
Terminals.
GERAN and UTRAN no software upgrade
New spectrum launch on BTS/NodeB needs considering the
limitation of transmit power, CE, Cell/TRX number and IBW.
