ZTE RAN Sharing Solution for Workshop V1.1

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

1/46

RAN Sharing Solution


2/46

1.RAN Sharing Technical Overvie

2.Pilot MORAN Solution

3.RAN Sharing Reference

Agenda


3/46

© ZTE Corporation. All rights reserved3

Network Sharing Architectures


4/46


Shared Carrier Con

One Carrier for multipl

Transmit power shared

Operators.

f1

Operator AOperator B

f

Dedicated Carrier Configuration

f1f2

Operator A

Operator B

f1f2

Dedicated Carrier Configuration

Shared BSC/RNC

Shared

BTS/NodeB

One / More Carriers Dedicated for oneOperator

Carriers Not Shared between Operators

Shared Carrier Co

MORAN MOCN

Carrier Configuration in RAN Sharing


5/46© ZTE Corporation. All rights reserved

5

GSM MOCN vs 3GPP Release

CN>=R10 CN=R10 BSC=R10 BSC

UE>=R10 OK OK

UER10

NITZ/SIM customization

Challenges from Shared Carrier Configuration

UMTS MOCN vs 3GPP Release

CN>=R6 CN=R6 RNC=R6 RN

UE>=R6 OK OK

UER6

NITZ/SIM customization


6/46© ZTE C

HPLMN ID

Common PLMN SIM Customization

for common PLMN

NITZ from

CN to UE

R6 UE

Pre-R6 UE

Roaming UECommon PLMN

Multi-PLMNbroadcasting

Network Name Display in MOCN


7/46© ZTE C

MOCN:

- At least one CN should support

3GPP Release >R6

- National and international pre-

R6 users can not be recognized.

MSC/SGSN A

3.Initial UE

(Attach requestRedirect attempt fl

4

4

Not allowed for HPLMN of IMSI

MSC/SGSN B

Not allowed for HPLMN of IMSI

MSC/SGSN CHLR C

7.Re-router command

6.Initial UE (Attach request,

Redirect attempt flag, IMSI…)

8.Initial UE (Attach request, Redirect attempt flag, IMSI…)

9.Authraction & Ciphering t

10.Re-router completed

5.Re-router

command

12. Attach Completed

GSM in R10 can support this procedure.

MOCN with Pre-R6 Terminal in UMTS

PLMN List in Radio:


8/46© ZTE C

GSM RAN Sharing - MORAN

TRX1…

TRXm…

Shared BTS

PLMN1

PLMN2

Shared BSCOperator A

Operator B

Cell A

Cell B

BSC and BTS for Multiple Operators

Cells

C1

Exclusive Pool

P1

Shared pool

P3

Cells

C2

Exclusive pool

P2

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

Cells Abis resource pools

Abis Transmission Sharing(V10R1)

Cells with

dedicated resource

Other operators’

cells

Dynamically select

Dynamically

select

Dynamically select

PCU Resource Sharing (V1


9/46© ZTE C

RRU Unit

RSU Module

Multi-PL

4 carriers configured

20 MH

Operator A Operator

S1+S1+S1+S1

20MHz

5MHz

20MHz RF Bandwidth

4 Carriers Supported

R

S

U

R

SU

R

SU

R

SU

S111+S111+S111+S111 S222+S

Multi-PLMN configuration

Operator D

Operator A

Operator BOperator C 1 RSU to 3 RSU 3 RSU to 6 RSU

BBU BBU

R

S

U

UMTS RAN Sharing – MORAN


10/46

TP CS/PS

CMPak CS/PS75%

85%

When cell power load is higher 80%, only TP users are accesse

When TP PS users access and power is shortage:

CMPak PS downgrade-> CMPak CS downgrade(if allowed)-> TP P

When TP CS users access and power is shortage: 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.

100%

Power CAC Threshold

TP CS

TP PS

CMPak CS

CMPak PS

TP user’s service experience is kept in priority.

CMPak users are serviced in best effort.

Example:

TP CS > TP PS

CMPak PS.

UMTS RAN Sharing – Transmit Power in MOCN


11/46

Shared UTRAN

MOCN

HSUPA user

of operator A

HSUPA user

of operator B

UTRAN calculates E-DCH user of each MOC

real time.CN of Operator A CN of Operator B

Only the users which are from the operato

E-DCH online user number is under th

threshold are allowed to access.

UMTS RAN Sharing – HSUPA Number in 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

The users which are from the operator th

DCH online user number is above th

threshold are not allowed to access.


12/46

Operator

A

40%

Operator

B

60%

100%

CE resource partition

For example A:B= 40%:60%

Shared by Operator A and Operator BNo congestion

CE congestion happens.

Operator who occupied CE

above the allocated ratio is

force to release resource.

CE resource can be par

operators. All operators share the

capacity when the overal

traffic is below the total

When admission for a

for CE limited, congestion

performed for the operat

occupied CE is above the

ratio.

The relived CE resource

new call admission.

Operator

A

50%

Operator

B

50%

Operator

A

45%

Operator

B

55%

UMTS RAN Sharing – BP Resource Sharing


13/46

© ZTE Corp13

CS RAB

PS RAB/PS RRC80%

85%

100%

Power CAC Threshold

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

CS RRC82% Power is shortagefor PS RRC

13.6kbps

Established on

RACH/FACH

Access PS RRC with

3.4kbps

Power

Time

Stop RRC

congestion

control

Start RRC

congestioncontrol

RRC signal congestion

RRC signal congestion

recover

If power is higher than the level of RRC signal cong

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.

Stop the actions until the power level below the r

UMTS RAN Sharing – Control Congestion


14/46

© ZTE C

……

Streaming

Voice/Video

Operator A

Operator B

……

PLMN Based Operator QoS Priority

……

Streaming

Voice/Video

Service Priority A Service Priority B

Traffic Class

ARP(RAB)

SIPConversational

_Voice/VideoStreaming Interactive(THP-Traffic Handling Priority)

Op. A Op. B Op. A Op. B Op. A Op. B1~5

Op. A

1~5

Op. B

6~10

Op. A

6~10

Op. B

11~15Op.

A

1

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

Different operator

different priorities, th

will be distributed tooperator first.

For each operator,

priority could be defi

UMTS RAN Sharing – Resource Congestion


15/46

© ZTE C

UMTS RAN Sharing - Mobility

Shared Cell

(MOCN)

1. Operator Oriented Handover procedure

2. Shared Network Access Code

CM

TP Cell

CMPaK Cell

TP Cell

CMPaK Cell

Mobility in MOCNMobility in MORA


16/46

© ZTE C

Trans. Dynamic Sharing

Transmission Sharing Stra

1. Common Dynamic poo

2. Overbooking & Minim

3. Service Priority

Shared

BTS/Node B

Shared

BSC/RNC

Operator A

Operator B

Operator C

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

UMTS RAN Sharing – Transmission


17/46

© ZTE C

LTE RAN Sharing

PLMN A

PLMN B

Operator A

Operator B

Shared eNodeB

Frequency 1

Frequency 2

PLMN A+

PLMN B

Shared

eNodeB

Frequency 1

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


18/46

© ZTE C

LTE RAN Sharing – RRC Resource

The feature will be available in LR15.

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.

RRC user Partition in shared carrier


19/46

© ZTE C

LTE RAN Sharing – QoS

The feature will be available in LR15.

PLMN Based Operator Qos Priority

Example of PLMN-level Q

h i i i


20/46

© ZTE C

Trans. Dynamic Sharing

Shared

eNodeB

Operator A

Operator B

Operator C

IP Planning (Ether #1):

S1/X2 user plane VLAN per operator

S1/X2 control plane VLAN shared by operators

OAM VLAN shared by operators

LTE RAN Sharing – Transmission

Physical link

Operator A

Operator B

Transmission Sharing Stra

1. Common Dynamic poo

2. Overbooking & Minim

3. Service Priority


21/46


Independent north-bound interfaces for multi-vendor.

Possible NBI customization.

Guest operator can have query rights, no creation, modification or deleti

EMS in RAN Sharing

Host Operator Guest Operator

I t /I t V d C tibilit


22/46

© ZTE C

Intra/Inter Vendor Compatibility

Core of operator A Core of operator B

Admin

NMS

Issues:

1. Int

2. NoOther vendor

I /I IOT R f


23/46

© ZTE C

Iu/Iur IOT ReferenceInterface

ZTE RAN

Version Vendor Equipment Version Date Country Oper

Iu UR12 Ericsson

MSC

MGW

SGSN

GGSN

(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

2013/10South

SudanMT

Iu UR12 Ericsson SGSN

HW: Mkvi

SW: 13Bcp00 2013/10 BeijingZhuYu Lab

ChUnic

Iu UR12 HW

MSC

MGW

SGSN

MSC HW: MSC9880

MSC SW:V100R009C00SPC700

MGW HW:UMG8900

MGW SW:V200R009C02SPC205

SGSN HW:SGSN9810

SGSN SW: V900R011C01SPC300

2014/01 AlgeriaOras

Tele

Iu UR12 HWSGSN

GGSN

SGSN HW: USN9810 ATCA

SGSN SW:V9 R10

GGSN HW:UGW9811 ATCA

GGSN SW:V9 R9

2013/10 VelezuelaTelefo

Mov

Iu UR11.2 HW

MGW

MSC

SGSN

GGSN

MSC, HW: V100; SW: R009C00

MGW, HW: V200; SW: R009C02

SGSN, SW: R09

GGSN, SW: R11

2012/07 Russia Bee

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

EMS NMS IOT R f


24/46

© ZTE C

Function Interface ZTE ProductRadio

Technology3rd party vendor 3rd pa rty Product Coun

FM CORBA NetNumen-M31 2G/3G IBM NetCool Hong K

FM CORBA NetNumen-M31 3G HP TeMIP Turk

PM/CM FILE NetNumen-M31 3G Aircom Optima Turk

FM CORBA NetNumen-M31 2G HP TeMIP Pakis

PM/CM FILE NetNumen-M31 2G Aircom Optima Pakis

FM CORBA NetNumen-M31 3G Bright Oceans NetWatch Chin

FM SNMP NetNumen-M31 3G AIS NMS Thaila

PM/CM FILE NetNumen-M31 2G/3G Bright Oceans NetWatch ChinPM/CM DB NetNumen-M31 2G Bright Oceans NetWatch Chin

FM ASCII NetNumen-M31 2G Bright Oceans NetWatch Chin

FM CORBA NetNumen-M31 3G Bright Oceans NetWatch Chin

PM/CM FILE NetNumen-M31 2G Bright Oceans NetWatch Chin

PM/CM DB NetNumen-M31 2G Bright Oceans NetWatch Chin

FM ASCII NetNumen-M31 2G Bright Oceans NetWatch Chin

PM FILE NetNumen-M31 3G AIS NMS Thaila

PM FILE NetNumen-M31 2G/3G Aircom Optima South A

FM SNMP NetNumen-M31 3G HP TeMIP Aust

PM DB NetNumen-M31 3G Aircom Optima Aust

FM SNMP NetNumen-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 IndonePM 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 Uzbeke

PM DB NetNumen-M31 2G/3G Ucell PQ Uzbeke

PM FILE NetNumen-M31 2G Aircom Optima Afghan

CM FILE NetNumen-M31 3G AIS NMS Thaila

CM FILE NetNumen-M31 3G AVEA NMS Turk

FM CORBA NetNumen-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

EMS-NMS IOT Reference


25/46



26/46

© ZTE C


EMS EMS

NMS NMS

E///,Huawei

EMS

NMS

CMPak CMPakTP

ZTE ZTE

CoreCore Core

Trust Domain

Untrust Domain

Trust Domain

Untrust Domain

Trust Domain

Untrust Domain

FireWall FireWall FireWall FireW

Networking:

1. EMS northbound interface for both CMPak and TP

2. Inter-vendor Iur is Optional.

3. FireWall for Inter Operator security

Inter-Vendor Intra-Vend

Site Configuration RRU


27/46

© ZTE C

Site Configuration – RRU

900MHz

R8881

1800MHz

R8882

210

R8

CMPakCMPak

TP

PA1

PA2

TP

PA

CMPak

880 906

889 915

1710 1765

1730 1785

IBW 40M

905882.5

Notes:

Different RRU hardware, different Bandwidth available

Case by case deployment

1717.5

1737.5

Site Configuration BBU


28/46

© ZTE C

Site Configuration – BBUTP

40%

CMPak

60%

100%

CE resource partition

For example A:B= 40%:60%

Shared by Operator A and Operator

BNo congestion

CE congestion happens.

Operator who occupied CEabove the allocated ratio is

force to release resource.

TP

50%

CMPak

50%

TP

45%

CMPak

55%

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.

Site Solution uFFD022


29/46

© ZTE C

Site Solution – uFFD022

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)

uFFD028 57 R8881 S1800(B8B)

uFFD029 53 R8881 S9000(B8B)

uFFD030 55 R8882 S1800(B)

uFFD022 61 R8861 S2100(B8B)

UMTS Cell Number enough

CE needs dimensioning ba

889

1710



30/46

© ZTE C


UMTS Cell Number enough

CE needs dimensioning ba

889

1710

uFFD024 52 R8882-GUL9018D

uFFD024 62 R8861 S2100(B8B)

uFFD024 63 R8861 S2100(B8B)

uFFD024 51 R8882-GUL9018D

uFFD024 61 R8861 S2100(B8B)

uFFD024 53 R8882-GUL9018D

R8882

PA900

PA1800

Controller Configuration – RNC


31/46

© ZTE C

Controller Configuration – RNCRNC Rack

1 2 3 4 5 6 7 8 9 10 11 12 13 14

R

U

P

R

U

P

R

U

P

R

U

P

O

M

M

O

M

M

O

M

P

O

M

P

R

U

P

D

M

P

C

M

P

C

M

P

C

M

P

C

M

P

EG

P

B

EG

P

B

EG

B

S

EG

B

S

EG

FS

EG

FS

EG

P

B

E A

P

B

ED

TI

R

U

P

R

U

P

R

U

P

R

U

P

R

U

P

R

U

P

C

M

P

C

M

P

C

M

P

C

M

P

D

M

P

D

M

P

D

M

P

D

M

P

E

G

PB

E

G

PB

E

G

BS

E

G

BS

E

G

FS

E

G

FS

E

G

PB

E

G

PB

R

U

P

R

U

P

R

U

P

R

U

P

C

M

P

C

M

P

C

M

P

C

M

P

C

M

P

C

M

P

D

M

P

D

M

P

D

M

P

D

M

P

E

G

P

B

E

G

P

B

E

G

B

S

E

G

B

S

E

G

FS

E

G

FS

E

G

P

B

Control Plane

• CMP is static allocated with each UMTS c

•DMP is resource pool, dynamically share

User Plane

• RUP is resource pool, dynamically shared

Interface Card

• EGPB can be physically allocated btw ope

• EGPB can be one resource pool, dynami

Switch and Clock

• EGBS and EGFS are switch boards, comm

• OMP is for O&M, common part.

Controller Configuration –Resource Sharing So


32/46

© ZTE C

Controller Configuration – Resource Sharing So

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

Transmission Configuration


38/46


EMS Sharing (TP as Host)

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.

TP CMPak

UMTS RAN Sharing – Feature Control


39/46

© ZTE C

Operator A

Features:

E-EDGE

Precise Paging

HSDPAHSUPA

……

Operator B

Features:

GSM HR

eMLPP

MBMS AMR

……

EMS

BSC/RNC

License Control based onPLMN ID

Feature authorization

Cell Level BSC/RNC Level

Capacity authorization

EMS Level BSC/RNC Level

Item Level Operator A

Capacity EMS Level 20K Cells

Feature Cell Level HSPA/E-EDGE

Feature authorization: Different cell,

authorized with different function based o

Capacity authorization: Restrict au

hardware capacity based on Cell.

reconfiguration without reactivation.

Example:

UMTS RAN Sharing Feature Control


40/46

1.RAN Sharing Technical Overvie2.Pilot MORAN Solution

3.RAN Sharing Reference

Agenda

H3G: the Best Mobile Network in Austria


41/46


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

In Dec. 2011：Commercial launch of

the first HSPA+/LTE in Austria

The best network in Austria, even in DAC

Subscriber increased by 26% within 1 yea

The 10-fold increased in network throug

The best LTE at the best price

H3G: Motivation of RAN Sharing

http://baike.baidu.com/image/32bb9c8b37fda3ebfc1f1038


42/46


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

f1

Shared Node B

& Carriers

f1

Shared RAN of H3GA

Shared RNC

Node B

f2

H3GA T-Mobile

f3

H3G Austria T-MobStrong

Points

Best UMTS network

in Austria

Has a mature GSM

in Austria

Motivation Improve voice

service in indoor and

rural area

UMTS network is serv

limited performance

legacy NodeBs can no

network

High ARPU subscribe

Solution

Result

Voice continuity can

be improved by

roaming to partner’s

network

Data service’s cove

can be greatly impro

Austria’s UMTS netw

RAN Sharing

BenefitProtect Investment

Better user experience and higher service

H3G: RAN Sharing Status


43/46


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: RAN Sharing Status

f1

Shared Node B &

Carriers

f1

Shared RAN of H3GA

Shared RNC

Node B

f2

H3G T-Mobile

f3

f1

Shared Node B

& Carriers

Shared RAN of H3GA

Shared RNC

f1

f2

H3G

f3

Orange

Node B

Subscribers

Information

Phase 1:MOCN with T-Mobile

Phase 2:Three Operators Shared Network after purchasing Ora

Traffic Migration

to H3G

H3G: Key Technologies of RAN Sharing


44/46


T-Mobile

H3G

Cell with

MPL

MN

PLMN-HPLMN-T……

H3G Orange

Spectrums

•Dedicate carrier or shared

•Wide band radio unit

IOT between Different Vendors

•Rich IOT experience

•Standard solution for R6 CN

•Innovative solution for lega

Routing Technologies

•MPLMN

•IMSI based message routin

Operator A/B shared 3G

3G SIMIMSI = Operator B

Target: Operator B 3G

Handover and Neighbor Relationships

• Large scale NR design

•IMSI based HO

Resource Management

•Shared network access control

•Operator specified CE resource

Operator specified transmission

Operator specified RNC Resource

Operator specified Features

QoS Assurance

Operator QoS Priority

H3G: Key Technologies of RAN Sharing

Summary


45/46

© ZTE C

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.


46/46

Thank you

ZTE RAN Sharing Solution for Workshop V1.1

Documents