Dokumen - Tips - Zte Ran Sharing Solution For Workshop v11

8/19/2019 ZTE RAN Sharing Solution for Workshop V1.
RAN Sharing Solution
http://slidepdf.com/reader/full/zte-ran-sharing-solution-for-workshop-v11 1/46
8/19/2019 ZTE RAN Sharing Solution for Workshop V1.1
Agenda
1.RAN Sharing Technical Overvie

2.Pilot MORAN Solution
3.RAN Sharing Reference
Network Sharing Architectures
http://slidepdf.com/reader/full/zte-ran-sharing-solution-for-workshop-v11
© ZTE Corporation. All rights reserved 3/46
3
Carrier Configuration in RAN Sharing
Dedicated Carrier Configuration Shared Carrier Con
 One / More Carriers Dedicated for one  One Carrier for multipl
Operator  Transmit power shared
 Carriers Not Shared between Operators Operators.
Dedicated Carrier Configuration Shared Carrier Co
Shared BSC/RNC
Operator A
Operator A
Operator B
Shared
f1 f1 BTS/NodeB f1 f
f2 f2
Operator B
MORAN MOCN
© ZTE Corporation. All rights reserved
4 4/46
Challenges from Shared Carrier Configuration

GSM MOCN vs 3GPP Release
CN>=R10 CN<R10
BSC>=R10 BSC<R10 BSC>=R10 BSC

UE>=R10 OK OK
UE<R10 OK At least one CN >R10

NITZ/SIM customization NITZ/SIM customization
UMTS MOCN vs 3GPP Release

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

NITZ/SIM customization NITZ/SIM customization
5 5/46
Network Name Display in MOCN
R6 UE
Multi-PLMN HPLMN ID
broadcasting
Pre-R6 UE SIM Customization
Common PLMN
for common PLMN
Roaming UE
Common PLMN NITZ from
CN to UE
http://slidepdf.com/reader/full/zte-ran-sharing-solution-for-workshop-v11 6/46© ZTE C

MOCN with Pre-R6 Terminal in UMTS

HLR C MSC/SGSN C MSC/SGSN B MSC/SGSN A
MOCN:
- At least one CN should support 3.Initial UE
(Attach request
Redirect attempt fl
3GPP Release >R6
4
- National and international pre- 4
R6 users can not be recognized. 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 t
10.Re-router completed
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 Exclusive Pool Dynamically select

C1 P1 Cells with
dedicated resource
Dynamically
Cells Exclusive pool
select
C2 P2
Dynamically select
Shared pool Other operators’
P3
cells
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 (V1

UMTS RAN Sharing MORAN
RRU Unit
Multi-PL
20MHz RF Bandwidth
4 carriers configured
4 Carriers Supported
5MHz Operator A Operator
20MHz 20 MH
RSU Module
Multi-PLMN configuration
Operator A R R R R R
Operator B S S S S
Operator C 1 RSU to 3 RSU 3 RSU to 6 RSU S
U U U U U
Operator D
BBU BBU
S1+S1+S1+S1 S111+S111+S111+S111 S222+S

UMTS RAN Sharing – Transmit Power in MOCN
TP CS
Example:
 TP user’s service experience is kept in priority. TP PS
TP CS > TP PS
 CMPak users are serviced in best effort. CMPak CS CMPak PS.
CMPak PS
Power CAC Threshold

 When cell power load is higher 80%, only TP users are accesse
100%  When TP PS users access and power is shortage:
 CMPak PS downgrade-> CMPak CS downgrade(if allowed)-> TP P
85% TP CS/PS

When TP CS users access and power is shortage:
75% CMPak CS/PS  CMPak PS downgrade-> CMPak CS downgrade(if allowed)-> TP PS
priority TP CS downgrade (if allowed)
 When power load by online users increases:

 The lowest priority PS to downgrade-> The lowest priority PS to s
>The lowest priority onlines users to release the RRC connection.
UMTS RAN Sharing – HSUPA Number in MOCN
UTRAN calculates E-DCH user of each MOC

CN of Operator A CN of Operator B real time.
Only the users which are from the operato

E-DCH online user number is under th
Shared UTRAN threshold are allowed to access.
HSUPA user HSUPA user

of operator A of operator B
The users which are from the operator th
DCH online user number is above th
threshold are not allowed to access.
MOCN
Benefits: Certain E-DCH resource allocated for each MOCN operator is gu

based on pre-defined E-DCH user proportion, to get the most of E-DCH se
UMTS RAN Sharing – BP Resource Sharing
Operator Operator
CE resource partition A B
40% 60%  CE resource can be par
For example A:B= 40%:60%
100% operators.
 All operators share the
No congestion Shared by Operator A and Operator B

capacity when the overal
traffic is below the total
 When admission for a
Operator Operator
CE congestion happens. A B for CE limited, congestion
50% 50%
performed for the operat
occupied CE is above the
Operator who occupied CE Operator Operator ratio.
above the allocated ratio is A B
45% 55%
force to release resource.  The relived CE resource
new call admission.
UMTS RAN Sharing
8/19/2019
Control Congestion
ZTE RAN Sharing Solution for Workshop V1.1
Power CAC Threshold

Established on
100% RACH/FACH
85%
82% CS
CS RAB
RRC Power is shortage
Access PS RRC with
for PS RRC
80% PS RAB/PS RRC 3.4kbps
13.6kbps
 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/FA
Start RRC  If power is higher than the level of RRC signal cong
Power congestion
control data and PS signal with lower priority is selected to
RRC signal congestion
 Downgrade PS RAB bit rate.
RRC signal congestion
recover  Switch PS RAB to FACH/RACH.
Time
Stop RRC  Force PS RAB or PS RRC signal to release.

congestion
control
 Stop the actions until the power level below the r
http://slidepdf.com/reader/full/zte-ran-sharing-solution-for-workshop-v11 13 © ZTE Corp

13/46
UMTS RAN Sharing Resource Congestion
–
PLMN Based Operator QoS Priority

 Different operator
…… Operator A …… different priorities, th
will be distributed to
Streaming Operator B Streaming
operator first.
Voice/Video Voice/Video  For each operator,
……
priority could be defi
Service Priority A Service Priority B
Traffic Class
Conversational
SIP _Voice/Video
Streaming Interactive(THP-Traffic Handling Priority)
ARP(RAB)
1~5 1~5 6~10 6~10 11~15Op. 1
Op. A Op. B Op. A Op. B Op. A Op. B
Op. A Op. B Op. A Op. B A
2 15 15 14 13 10 9 9 8 8 7 7
7 15 15 13 12 10 9 6 5 5 4 4
11 15 15 12 11 10 9 3 2 2 1 1
© ZTE C
UMTS RAN Sharing - Mobility
TP Cell
TP Cell
Shared Cell
(MOCN) CMPaK Cell

CMPaK Cell CM
Mobility in MOCN
Mobility in MORA
1. Operator Oriented Handover procedure
2. Shared Network Access Code
© ZTE C
UMTS RAN Sharing
8/19/2019
Transmission
–
Operator A
Shared Operator B
Shared
BTS/Node B Operator C BSC/RNC
Trans. Dynamic Sharing
IP Planning (Ether #1): Transmission Sharing Stra

1. IP1@Operator1: 2G UP,2G CP 1. Common Dynamic poo
2. IP2@Operator2: 3G (n)rt-DCH, HSxPA 2. Overbooking & Minim
3. IP3@Operator3: 2G UP, 2GCP 3. Service Priority
4. IP4@Operator4: 2G/3G/MP
© ZTE C
LTE RAN Sharing
Shared
Shared eNodeB
PLMN A eNodeB
Operator A
Frequency 1 PLMN A
PLMN B + Frequency 1
PLMN B
Operator B
Frequency 2
Dedicated Carrier (V2.1) Shared Carrier (V2.
1. Maximum Four PLMNs per LTE RAN

2. Msg reroute as in GSM and UMTS
Multiple PLMN Broa
© ZTE C
LTE RAN Sharing
8/19/2019
– 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 ma
utilization of RRC user resources.
If the number of RRC UEs of either of two operators does not exceed the ratio, the
the two operators can be accessed properly. If the number of RRC users of operator
predefined threshold, the eNodeB limits access of new RRC users of operator A, and
access the RRC users of operator B.
© ZTE C
LTE RAN Sharing
8/19/2019
– QoS
The feature will be available in LR15.
PLMN Based Operator Qos Priority
Example of PLMN-level Q
© ZTE C
LTE RAN Sharing
8/19/2019
– Transmission
Operator A
Shared Operator A
Operator B Physical link
eNodeB Operator C Operator B
Trans. Dynamic Sharing
IP Planning (Ether #1): Transmission Sharing Stra

S1/X2 user plane VLAN per operator 1. Common Dynamic poo
S1/X2 control plane VLAN shared by operators 2. Overbooking & Minim
OAM VLAN shared by operators 3. Service Priority
© ZTE C
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 deleti
21
Intra/Inter Vendor Compatibility
NMS
Core of operator A Core of operator B
Admin
Issues:
1. Int
Other vendor 2. No
© ZTE C
Iu/Iur IOT Reference
ZTE RAN
Interface Vendor Equipment Version Date Country Oper
Version
MSC (1) MSC, HW: AXE MSC R12.1 SW : R 12.1
MGW (2) MGW, HW: R6.1 SW: R6.1 South
Iu UR12 Ericsson 2013/10 MT
SGSN (3) SGSN, HW: 2010B SW: 2010B Sudan
GGSN (4) GGSN: HW: 2010B SW: 2010B
HW: Mkvi
Iu UR12 Ericsson SGSN SW: 13Bcp00 2013/10 Beijing Ch
ZhuYu Lab Unic
MSC HW: MSC9880
MSC SW:V100R009C00SPC700
MSC
MGW HW:UMG8900 Oras
Iu UR12 HW MGW 2014/01 Algeria
MGW SW:V200R009C02SPC205 Tele
SGSN
SGSN HW:SGSN9810
SGSN SW: V900R011C01SPC300
SGSN HW: USN9810 ATCA

SGSN SGSN SW:V9 R10 Telefo
Iu UR12 HW 2013/ 10 V elez uela
GGSN GGSN HW:UGW9811 ATCA Mov
GGSN SW:V9 R9
MGW MSC, HW: V100; SW: R009 C00
MSC MGW, HW: V200; SW: R009C02
Iu UR11.2 HW 2012/07 Russia Bee
SGSN SGSN, SW: R09
GGSN GGSN, SW: R11
Iur UR12 Ericsson RNC W12B 2013/09 Sweden Swe
Iur UR11.2 HW RNC V900R014C00 2013/01 Thailand A
Iur UR12 NSN RNC RU30-RN6.0_2.0 2013/09 Sweden Hi3
Iur UR11.2 NSN RNC RNC2.0 CD1.0 2013/01 Thailand A
© ZTE C
EMS-NMS IOT Reference
Radio
Functi on I nte rfa ce ZTE Product 3rd pa rty ve ndor 3rd pa rty Product Coun
Technology
FM CORBA NetNumen-M31 2G/3G IBM NetCool Hong K
FM CORBA Net Numen-M31 3G HP TeMIP Turk
PM/CM FILE Net Numen-M31 3G Aircom Optima Turk
FM CORBA Net Numen-M31 2G HP TeMIP Pakis
PM/CM FILE Net Numen-M31 2G Aircom Optima Pakis
FM CORBA Net Numen-M31 3G Bright Oceans NetWatch Chin
FM SNMP Net Numen-M31 3G AIS NMS Thaila
PM/CM FILE NetNumen-M31 2G/3G Bright Oceans NetWatch Chin
PM/CM DB Net Numen-M31 2G Bright Oceans NetWatch Chin
FM ASCII Net Numen-M31 2G Bright Oceans NetWatch Chin
FM CORBA Net Numen-M31 3G Bright Oceans NetWatch Chin
PM/CM FILE Net Numen-M31 2G Bright Oceans NetWatch Chin
PM/CM DB Net Numen-M31 2G Bright Oceans NetWatch Chin
FM ASCII Net Numen-M31 2G Bright Oceans NetWatch Chin
PM FILE Net Numen-M31 3G AIS NMS Thaila
PM FILE NetNumen-M31 2G/3G Aircom Optima South A
FM SNMP Net Numen-M31 3G HP TeMIP Aust
PM DB Net Numen-M31 3G Aircom Optima Aust
FM SNMP Net Numen-M31 3G HP TeMIP Indone
FM SNMP NetNumen-M31 2G/3G HP TeMIP Portu
PM FILE NetNumen-M31 2G/3G Aircom Optima Portu
PM/CM FILE NetNumen-M31 2G/3G Telkomsel SML Indone
PM FILE NetNumen-M31 2G/3G PIWorks NetworkCPR Uzbeke
FM CORBA NetNumen-M31 2G/3G IBM NetCool Uzbeke
FM DB NetNumen-M31 2G/3G Ucell PQ Uz bek e
PM DB NetNumen-M31 2G/3G Ucell PQ Uz bek e
PM FILE Net Numen-M31 2G Aircom Optima Afghan
CM FILE Net Numen-M31 3G AIS NMS Thaila
CM FILE Net Numen-M31 3G AVEA NMS Turk
FM CORBA Net Numen-M31 2G Nokia Siemens NetAct 5.1 Venez
PM/CM NBI NetNumen-M31 2G/3G Telenor Telenor NBI Hung
FM SNMP NetNumen-M31 2G/3G AIS AIS selfmade Thaila
PM FTP NetNumen-M31 2G/3G AIS AIS selfmade Thaila
CM FTP NetNumen-M31 2G/3G AIS AIS selfmade Thaila
© ZTE C
Intra/Inter Vendor Compatibility
CMPak TP CMPak
NMS Core Core NMS NMS Core
FireWall FireWall FireWall FireW

EMS EMS EMS
Trust Domain Trust Domain Trust Domain
Untrust Domain Untrust Domain Untrust Domain
E///,Huawei ZTE ZTE

Inter-Vendor Intra-Vend
Networking:
1. EMS northbound interface for both CMPak and TP
2. Inter-vendor Iur is Optional.
3. FireWall for Inter Operator security
© ZTE C
Site Configuration
8/19/2019 – RRU
900MHz 1800MHz 210

R8881 R8882 R8
CMPak TP CMPak CMPak
PA PA1
TP
PA2
882.5 905
880 906
889 915 IBW 40M
1710 1717.5 1765

Notes:
Different RRU hardware, different Bandwidth available
1730 1737.5 1785
Case by case deployment
© ZTE C
Site Configuration
8/19/2019
– BBU
TP CMPak
CE resource partition
40% 60%
For example A:B= 40%:60%
100%
Shared by Operator A and Operator

No congestion B
TP CMPak
CE congestion happens. 50% 50%
Operator who occupied CE TP CMPak

above the allocated ratio is
45% 55%
force to release resource.
1. Site dimensioning needs to consider GSM TRX and UMTS Cell lim
2. FS board limitation needs to consider if the number of RRU chang
3. Dedicated board for each carrier is ok.
© ZTE C
Site Solution
8/19/2019
– uFFD022 ZTE RAN Sharing Solution for Workshop V1.1
uFFD022 51 R8881 S9000(B8B)

uFFD023 54 R8882 S1800(B)
uFFD024 63 R8861 S2100(B8B)
uFFD025 52 R8881 S9000(B8B)
uFFD026 56 R8882 S1800(B)
uFFD027 62 R8861 S2100(B8B)
889
uFFD028 57 R8881 S1800(B8B)
uFFD029 53 R8881 S9000(B8B)
uFFD030 55 R8882 S1800(B)
uFFD022 61 R8861 S2100(B8B)
1710
UMTS Cell Number enough

CE needs dimensioning ba
© ZTE C
Site Solution
8/19/2019
– uFFD024 ZTE RAN Sharing Solution for Workshop V1.1
R8882
uFFD024 52 R8882-GUL9018D
uFFD024 62 R8861 S2100(B8B)
uFFD024 63 R8861 S2100(B8B)
uFFD024 51 R8882-GUL9018D
PA900 889
uFFD024 61 R8861 S2100(B8B)
uFFD024 53 R8882-GUL9018D
PA1800
1710
UMTS Cell Number enough

CE needs dimensioning ba
© ZTE C
Controller Configuration
8/19/2019
– RNC
RNC Rack  Control Plane

1 2 3 4 5 6 7 8 9 10 11 12 13 14
R R R R O O O O R D C C C C • CMP is static allocated with each UMTS c
U U U U M M M M U M M M M M
P P P P M M P P P P P P P P • DMP is resource pool, dynamically share
E E E E E E E E E
G G G G G G G A D  User Plane
P P B B FSFS P P TI
B B S S B B • RUP is resource pool, dynamically shared
R R R R R R C C C C D D D D  Interface Card
U U U U U U M M M M M M M M
P P P P P P P P P P P P P P • EGPB can be physically allocated btw ope
E E E E E E E E
G G G G G G G G • EGPB can be one resource pool, dynami
P P B B FSFS P P
B B S S B B  Switch and Clock
R R R R C C C C C C D D D D • EGBS and EGFS are switch boards, comm

U U U U M M M M M M M M M M
P P P P P P P P P P P P P P • OMP is for O&M, common part.
E E E E E E E
G G G G G G G
P P B B FSFS P
B B S S B
© ZTE C
Controller Configuration Resource Sharing So
8/19/2019
–
 Control Plane
• TP &CMPak can share same CMP pool,
separated.
• DMP in one resource pool, dynamically

CMPak
 User Plane
• RUP in one resource pool, dynamically
CMPak
 Interface Card
• EGPB can be in one pool or physically
• Suggestion: physically separation to sim
 Switch and Clock
• EGBS,EGFS, and OMP are common par
© ZTE C
Transmission Configuration
© ZTE C
UMTS RAN Sharing
8/19/2019
Access Procedure
© ZTE C
UMTS RAN Sharing
8/19/2019
Handover Procedure
TP RAN CMPak R
TP RNC
CMPak User
© ZTE C
UMTS RAN Sharing
8/19/2019
Handover Procedure
TP RAN CMPak R
TP RNC
CMPak User
© ZTE C
UMTS RAN Sharing
8/19/2019
Handover Procedure
TP RAN CMPak R
TP RNC
CMPak User
© ZTE C
EMS Sharing (TP as Host)
TP CMPak
 Independent North bound interface, Corba for FM, and FTP for CM/PM reco
 TP Operator has complete rights.
 CMPak as guest, has only query rights, no creation, modify and etc.
38
UMTS RAN Sharing

– Feature Control 38/46

License Control based on

PLMN ID
Feature authorization Capacity authorization
Cell Level BSC/RNC Level EMS Level BSC/RNC Level
 Feature authorization: Different cell,
Operator A EMS Operator B authorized with different function based o

Features: Features:  Capacity authorization: Restrict au
 E-EDGE  GSM HR
 Precise Paging  eMLPP hardware capacity based on Cell.
HSDPA MBMS
reconfiguration without reactivation.
HSUPA AMR
……
BSC/RNC ……
 Example:
Item Level Operator A
Capacity EMS Level 20K Cells
Feature Cell Level HSPA/E-EDGE
© ZTE C
8/19/2019
Agenda ZTE RAN Sharing Solution for Workshop V1.1
1.RAN Sharing Technical Overvie

2.Pilot MORAN Solution
3.RAN Sharing Reference
H3G: the Best Mobile Network in Austria

Customized Relocation Solution The Best Mobile Network
 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 network in Austria, even in DAC
 In Dec. 2011：Commercial launch of  Subscriber increased by 26% within 1 yea
the first HSPA+/LTE in Austria  The 10-fold increased in network throug
 The best LTE at the best price

41
H3G: Motivation of RAN Sharing

Spectrum A1 A2 H1 H2 H3 O1 O2 O3 A3 T
1st PLMN (MIB) PLMN1 PLMN-A PLMN-H PLMN-H PLMN-H PLMN-O PLMN-O PLMN-O PLMN-A PLM
2nd PLMN (MIB) PLMN-T PLMN-T PLMN-T
H3G Austria T-Mob

Strong Best UMTS network Has a mature GSM
H3GA T-Mobile Points in Austria in Austria
UMTS network is serv
limited performance
 Improve voice
Motivation legacy NodeBs can no
service in indoor and
network
rural area
 High ARPU subscribe
Shared RAN of H3GA
Shared RNC
Solution RAN Sharing
 Voice continuity can Data service’s cove
Shared Node B be improved by can be greatly impro
& Carriers Result
roaming to partner’s Austria’s UMTS netw
Node B network
f1 f1
 Protect Investment
f2
f3 Benefit  Better user experience and higher service
42 © ZTE Corporation. All rights reserved
H3G: RAN Sharing Status
Spectrum A1 A2 H1 H2 H3 O1 O2 O3 A3
1st PLMN (MIB) PLMN1 PLMN-A PLMN-H PLMN-H PLMN-H PLMN-O PLMN-O PLMN-O PLMN-A PL
2nd PLMN (MIB) PLMN-T PLMN-T PLMN-T
H3G T-Mobile Orange Subscribers H3G

Information
Shared RAN of H3GA Shared RAN of H3GA
Shared RNC Shared RNC

Traffic Migration
Shared Node B & to H3G
Carriers Node B
Node B
f1 f1 f1 f1
f2 f2
f3 f3
Shared Node B
& Carriers
Phase 1: Phase 2:
MOCN with T-Mobile Three Operators Shared Network after purchasing Ora
H3G: Key Technologies of RAN Sharing
Cell with
 Spectrums
PLMN-H
MPL
PLMN-T
MN Dedicate carrier or shared
•
H3G … Wide band radio unit

•
…
 IOT between Different Vendors
Rich IOT experience

•
Standard solution for R6 CN

•
Innovative solution for lega

•
T-Mobile
 Routing Technologies
H3G Orange
MPLMN •
IMSI based message routin

•
 Handover and Neighbor Relationships  QoS Assurance

Large scale NR design
•  Operator QoS Priority 3G SIM
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
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.
© ZTE C
Thank you

Dokumen - Tips - Zte Ran Sharing Solution For Workshop v11

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dokumen - Tips - Zte Ran Sharing Solution For Workshop v11

Uploaded by

Copyright:

Available Formats

8/19/2019 ZTE RAN Sharing Solution for Workshop V1.

RAN Sharing Solution

1.RAN Sharing Technical Overvie

Network Sharing Architectures

Carrier Configuration in RAN Sharing

Dedicated Carrier Configuration Shared Carrier Con

Dedicated Carrier Configuration Shared Carrier Co

Challenges from Shared Carrier Configuration

BSC>=R10 BSC<R10 BSC>=R10 BSC

UE<R10 OK At least one CN >R10

UMTS MOCN vs 3GPP Release

RNC>=R6 RNC<R6 RNC>=R6 RN

UE<R6 OK At least one CN >R6

Network Name Display in MOCN

http://slidepdf.com/reader/full/zte-ran-sharing-solution-for-workshop-v11 6/46© ZTE C

MOCN with Pre-R6 Terminal in UMTS

- National and international pre- 4

R6 users can not be recognized. Not allowed for HPLMN of IMSI

PLMN List in Radio: Not allowed for HPLMN of IMSI

9.Authraction & Ciphering t

12. Attach Completed

GSM in R10 can support this procedure.

PLMN2 TRXm… Cell B

BSC and BTS for Multiple Operators

Cells Exclusive Pool Dynamically select

Abis Transmission Sharing(V10R1) PCU Resource Sharing (V1

http://slidepdf.com/reader/full/zte-ran-sharing-solution-for-workshop-v11 8/46© ZTE C

S1+S1+S1+S1 S111+S111+S111+S111 S222+S

Power CAC Threshold

 When power load by online users increases:

UTRAN calculates E-DCH user of each MOC

Only the users which are from the operato

HSUPA user HSUPA user

Benefits: Certain E-DCH resource allocated for each MOCN operator is gu

No congestion Shared by Operator A and Operator B

Power CAC Threshold

Stop RRC  Force PS RAB or PS RRC signal to release.

http://slidepdf.com/reader/full/zte-ran-sharing-solution-for-workshop-v11 13 © ZTE Corp

PLMN Based Operator QoS Priority

(MOCN) CMPaK Cell

Trans. Dynamic Sharing

IP Planning (Ether #1): Transmission Sharing Stra

Dedicated Carrier (V2.1) Shared Carrier (V2.

1. Maximum Four PLMNs per LTE RAN

The feature will be available in LR15.

The feature will be available in LR15.

PLMN Based Operator Qos Priority

eNodeB Operator C Operator B

Trans. Dynamic Sharing

IP Planning (Ether #1): Transmission Sharing Stra

Host Operator Guest Operator

 Independent north-bound interfaces for multi-vendor.

SGSN HW: USN9810 ATCA

NMS Core Core NMS NMS Core

FireWall FireWall FireWall FireW

E///,Huawei ZTE ZTE

900MHz 1800MHz 210

1710 1717.5 1765

Shared by Operator A and Operator

Operator who occupied CE TP CMPak

uFFD022 51 R8881 S9000(B8B)

UMTS Cell Number enough

UMTS Cell Number enough