ZTE RAN Sharing Solution For Workshop V1.1

RAN Sharing Solution
Agenda
1.RAN Sharing Technical Overview
2.Pilot MORAN Solution
3.RAN Sharing Reference
Network Sharing Architectures
ZTE Corporation. All rights reserved
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
MOCN
MORAN
4
Shared
BTS/NodeB
Challenges from Shared Carrier Configuration

GSM MOCN vs 3GPP Release
CN>=R10
BSC>=R10
CN<R10
BSC<R10
BSC>=R10
UE>=R10
OK
OK
UE<R10
OK
NITZ/SIM customization
At least one CN >R10

BSC<R10
UMTS MOCN vs 3GPP Release

CN>=R6
RNC>=R6
CN<R6
RNC<R6
RNC>=R6
UE>=R6
OK
OK
UE<R6
OK
At least one CN >R6

RNC<R6
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
ZTE Corporation. All rights reserved.
MOCN with Pre-R6 Terminal in UMTS

MOCN:
-
HLR C
MSC/SGSN C
MSC/SGSN B
MSC/SGSN A
1.RRC Connection
Established
At least one CN should support

3GPP Release >R6
National and international preR6 users can not be recognized.
Non-support
UE
RNC
3.Initial UE
(Attach request,
Redirect attempt flag)
2.Initial Direct
Transfer
4.Identity Req
4.Identity Req
IMSI
Not allowed for HPLMN of IMSI
5.Re-router
command
6.Initial UE (Attach request,
Redirect attempt flag, IMSI)
PLMN List in Radio:
Not allowed for HPLMN of IMSI

7.Re-router command
8.Initial UE (Attach request, Redirect attempt flag, IMSI)
9.Authraction & Ciphering
10.Re-router completed
12. Attach Completed
11.Attach accpet
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
Shared pool
P3
Cells with
dedicated resource
Dynamically select
Dedicated PCU
resource
Dynamically
select
Other operators
cells
Dynamically select
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 UU U
BBU
S222+S222+S222+S222
>
UMTS RAN Sharing Transmit Power in MOCN

TP CS
TP users 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%
100%
No congestion
CE congestion happens.
Operator who occupied CE

above the allocated ratio is
force to release resource.
Shared by Operator A and Operator B
Operator
A
50%
Operator
A
45%
Operator
B
50%
Operator
B
55%
>
CE resource can be partitioned among

operators.
All operators share the same pooled
capacity when the overall CE cost by
traffic is below the total CE.
When admission for a new call fails
for CE limited, congestion control is
performed for the operator whose
occupied CE is above the partitioned
ratio.
The relived CE resource is used for the
new call admission.
> Internal Only
UMTS RAN Sharing Control Congestion

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
RRC signal congestion

RRC signal congestion
recover
If power is higher than the level of RRC signal congestion, the online PS
data and PS signal with lower priority is selected to:
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.
13
UMTS RAN Sharing Resource Congestion

PLMN Based Operator QoS Priority
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.
Operator A
Streaming
Operator B
Streaming
Voice/Video
Voice/Video
Service Priority A
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
15
15
14
13
10
15
15
13
12
10
11
15
15
12
11
10
UMTS RAN Sharing - Mobility

TP Cell
TP Cell
TP Cell
CMPaK Cell
CMPaK Cell
Shared Cell
(MOCN)
CMPaK Cell
Mobility in MOCN
1.
2.
Mobility in MORAN
Operator Oriented Handover procedure

Shared Network Access Code
UMTS RAN Sharing Transmission

Shared
BTS/Node B
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
Operator A
+
Operator B
Frequency 1
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 the 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 Transmission

Shared
eNodeB
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
21
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
Iu
Iu
UR12
UR12
Date
Country
Operator
3GPP
Version
Bearer
2013/10
South
Sudan
MTN
R8
IP
2013/10
Beijing
ZhuYu Lab
China
Unicom
R8
IP
2014/01
Algeria
Orascom
Telecom
IP
IP
HW
MSC
MGW
SGSN
MSC HW: MSC9880

MSC SW:V100R009C00SPC700
MGW HW:UMG8900
MGW SW:V200R009C02SPC205
SGSN HW:SGSN9810
SGSN SW: V900R011C01SPC300
HW
SGSN
GGSN
SGSN HW: USN9810 ATCA

SGSN SW:V9 R10
GGSN HW:UGW9811 ATCA
GGSN SW:V9 R9
2013/10
Velezuela
Telefonica
Movistar
MSC, HW: V100; SW: R009C00

MGW, HW: V200; SW: R009C02
SGSN, SW: R09
GGSN, SW: R11
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
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
EMS-NMS IOT Reference

Function
Interface
ZTE Product
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
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
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
NetNumen-M31
Radio
Te chnology
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 vendor
3rd pa rty Product
Country
Ope rator
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
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
Optima
NMS
NMS
NetAct 5.1
Telenor NBI
AIS selfmade
AIS selfmade
AIS selfmade
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
Uzbekestan
Uzbekestan
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
Ucell
Ucell
Etisalat
AIS
AVEA
Digitel
Telenor
AIS
AIS
AIS
Agenda
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
NMS
FireWall
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.
3. FireWall for Inter Operator security
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
Case by case deployment
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 board for each carrier 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
915
1765
UMTS Cell Number enough

CE needs dimensioning based on traffic
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
915
1765
UMTS Cell Number enough

CE needs dimensioning based on traffic
Controller Configuration RNC

RNC Rack
Control Plane
1 2 3 4 5 6 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
B B
C
M
P
E
G
B
S
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
S
B
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

EGBS,EGFS, and OMP are common part
Transmission Configuration
TP Core Switch
CMPak Core Switch
UMTS RAN Sharing Access Procedure
TP Core Switch
CMPak Core Switch
UMTS RAN Sharing Handover Procedure

TP RAN
CMPak RAN
CMPak RNC
TP RNC
CMPak User

TP RAN
CMPak RAN
CMPak RNC
TP RNC
CMPak User

TP RAN
CMPak RAN
CMPak RNC
TP RNC
CMPak User
EMS Sharing (TP as Host)
TP
38
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
EMS Level
BSC/RNC Level
Feature authorization: Different cell, BSC/RNC can be

EMS
Operator A
Features:
E-EDGE
Precise Paging
HSDPA
HSUPA
BSC/RNC
Operator B
Features:
GSM HR
eMLPP
MBMS
AMR
authorized with different function based on PLMN ID.

Capacity
authorization:
Restrict
authorized
network
hardware capacity based on Cell. Support capacity

reconfiguration without reactivation.
Example:
Item
Level
Operator A
Operator B
Capacity
EMS Level
20K Cells
10K Cells
Feature
Cell Level
HSPA/E-EDGE
MBMS/HR
Agenda
H3G: the Best Mobile Network in Austria
Customized Relocation Solution
The Best Mobile Network in Austria
Scope: 4,000+ BTSs/3,100 hops MW to be swapped
Reuse: NSNs BTS cabinets and 10,000+ Operator Ts
H3G Austria
topped No.1
in CONNECT
test in 2011.
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

In Dec. 2011Commercial launch of
the first HSPA+/LTE in Austria
The best network in Austria, even in DACH region

Subscriber increased by 26% within 1 year
The 10-fold increased in network throughput
The best LTE at the best price
41
H3G: Motivation of RAN Sharing

Spectrum
1st PLMN (MIB)
A1
A2
H1
H2
H3
O1
O2
O3
A3
T1
T2
T3
PLMN1
PLMN-A
PLMN-H
PLMN-H
PLMN-H
PLMN-O
PLMN-O
PLMN-O
PLMN-A
PLMN-T
PLMN-T
PLMN-T
PLMN-T
PLMN-T
PLMN-T
2nd PLMN (MIB)
H3G Austria
H3GA
T-Mobile
Strong
Points
T-Mobile
Best UMTS network

in Austria
Has a mature GSM coverage

in Austria
UMTS network is served by legacy equipment with
limited performance
legacy NodeBs can not provide a competitive
network
High ARPU subscribers need higher throughput
Motivation
Improve voice
service in indoor and

rural area
Shared RAN of H3GA
Shared RNC
Solution
RAN Sharing
Voice continuity can
be improved by
roaming to partners
network
Shared Node B
& Carriers
f1
f2
f3
42
Result
f1
Node B
Protect Investment
Better user experience and higher service continuity
Benefit
Data services coverage and performance

can be greatly improved by using H3G
Austrias UMTS network
H3G: RAN Sharing Status

Spectrum
1st PLMN (MIB)
A1
A2
H1
H2
H3
O1
O2
O3
A3
T1
T2
T3
PLMN1
PLMN-A
PLMN-H
PLMN-H
PLMN-H
PLMN-O
PLMN-O
PLMN-O
PLMN-A
PLMN-T
PLMN-T
PLMN-T
PLMN-T
PLMN-T
PLMN-T
2nd PLMN (MIB)
T-Mobile
H3G
Orange
Subscribers
Information
Shared RNC
PLMN-H
PLMN-T
PLMN-O
Shared RNC
Traffic Migration
to H3G
Shared Node B &

Carriers
Node B
f1
Phase 1:
MOCN with T-Mobile
43
T-Mobile
Shared RAN of H3GA
Shared RAN of H3GA
f1
f2
f3
H3G
Node B
Node B
f1
f2
f3
Shared Node B
& Carriers
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
T-Mobile
H3G
Orange
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
Handover and Neighbor
Relationships QoS Assurance

3G SIM
Large scale NR design
Operator QoS Priority
IMSI = Operator B
IMSI based HO
Target: Operator B 3G
Resource Management
Shared network access control
Operator specified CE resource
Operator A/B shared 3G
Operator specified transmission
Operator specified RNC Resource
Operator specified Features
44
Operator A 3G
Operator A 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.
Thank you

ZTE RAN Sharing Solution For Workshop V1.1

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ZTE RAN Sharing Solution For Workshop V1.1

Încărcat de

Drepturi de autor:

Formate disponibile

RAN Sharing Solution

Network Sharing Architectures

ZTE Corporation. All rights reserved

Carrier Configuration in RAN Sharing

Shared Carrier Configuration

One / More Carriers Dedicated for one

One Carrier for multiple Operators

Transmit power shared between the

Carriers Not Shared between Operators

Dedicated Carrier Configuration

Shared Carrier Configuration

ZTE Corporation. All rights reserved

Challenges from Shared Carrier Configuration

At least one CN >R10

UMTS MOCN vs 3GPP Release

At least one CN >R6

Network Name Display in MOCN

ZTE Corporation. All rights reserved.

MOCN with Pre-R6 Terminal in UMTS

At least one CN should support

PLMN List in Radio:

Not allowed for HPLMN of IMSI

GSM in R10 can support this procedure.

GSM RAN Sharing - MORAN

BSC and BTS for Multiple Operators

Abis resource pools

Abis Transmission Sharing(V10R1)

PCU Resource Sharing (V10R1)

UMTS RAN Sharing MORAN

UMTS RAN Sharing Transmit Power in MOCN

TP users service experience is kept in priority.

CMPak users are serviced in best effort.

Power CAC Threshold

When TP PS users access and power is shortage:

When TP CS users access and power is shortage:

priority TP CS downgrade (if allowed)

When power load by online users increases:

>The lowest priority onlines users to release the RRC connection.

ZTE Corporation. All rights reserved.

UMTS RAN Sharing HSUPA Number in MOCN

UTRAN calculates E-DCH user of each MOCN operator in

UMTS RAN Sharing BP Resource Sharing

Operator who occupied CE

Shared by Operator A and Operator B

CE resource can be partitioned among

ZTE Corporation. All rights reserved.

> Internal Only

UMTS RAN Sharing Control Congestion

Access PS RRC with

RRC signal congestion

Downgrade PS RAB bit rate.

Switch PS RAB to FACH/RACH.

Force PS RAB or PS RRC signal to release.

ZTE Corporation. All rights reserved.

UMTS RAN Sharing Resource Congestion

Different operators could be set with

Interactive(THP-Traffic Handling Priority)

ZTE Corporation. All rights reserved.

UMTS RAN Sharing - Mobility

Operator Oriented Handover procedure

ZTE Corporation. All rights reserved.

UMTS RAN Sharing Transmission

Trans. Dynamic Sharing