5-08 Ericsson Parsons MEF Survey on Sync · 2018. 11. 5. · radio site RRU MEF 22.2 Terminology Base station site Marco RBS Network controller / gateway site SGW, MME Small cell

Slide title 70 pt

CAPITALS

Slide subtitle minimum 30 pt

MEF survey sync for Mobile backhaul

Glenn Parsons

Slide title 44 pt

Text and bullet level 1 minimum 24 pt

Bullets level 2-5 minimum 20 pt

Characters for Embedded font: !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~¡¢£¤¥¦§¨©ª«¬®¯°±²³´¶·¸¹º»¼½ÀÁÂÃÄÅÆÇÈËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăąĆćĊċČĎďĐđĒĖėĘęĚěĞğĠġĢģĪīĮįİıĶķĹĺĻļĽľŁłŃńŅņŇňŌŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŮůŰűŲųŴŵŶŷŸŹźŻżŽžƒȘșˆˇ˘˙˚˛˜˝ẀẁẃẄẅỲỳ–—‘’‚“”„†‡•…‰‹›⁄€™ĀĀĂĂĄĄĆĆĊĊČČĎĎĐĐĒĒĖĖĘĘĚĚĞĞĠĠĢĢĪĪĮĮİĶĶĹĹĻĻĽĽŃŃŅŅŇŇŌŌŐŐŔŔŖŖŘŘŚŚŞŞŢŢŤŤŪŪŮŮŰŰŲŲŴŴŶŶŹŹŻŻȘș−≤≥fifl

ΆΈΉΊΌΎΏΐΑΒΓΕΖΗΘΙΚΛΜΝΞΟΠΡΣΤΥΦΧΨΪΫΆΈΉΊΰαβγδεζηθικλνξορςΣΤΥΦΧΨΩΪΫΌΎΏ

ЁЂЃЄЅІЇЈЉЊЋЌЎЏАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯЁЂЃЄЅІЇЈЉЊЋЌЎЏѢѢѲѲѴѴҐҐəәǽẀẁẂẃẄẅỲỳ№

Do not add objects or text in the footer area

MEF MBH Survey | Public | © Ericsson AB 2016 | 2016-06-07 | Page 2

Mef 22.2 concepts

Carrier Ethernet Mobile Backhaul Service

•  Standard Demarcation

•  Standard & Scalable Services with Quality of Service

•  Service Management & Reliability

RAN Radio Access Network

RAN BS RAN Base Station

RAN NC RAN Network Controller

RAN CE RAN Customer Edge –Mobile network node/site

RNC Radio Network Controller

CEN Carrier Ethernet Network

Service Provider

CEN UNI

RAN CE

UNI

RAN BS

UNI

RAN BS RAN NC

RAN CE

RAN CE

RAN NC

RAN CE

UNI

Customer (Subscriber) is Mobile Operator & needs Mobile Backhaul between RAN CEs

Service Provider (SP) offers Mobile Backhaul Service between demarcation points

Standard Demarcation

Slide title 44 pt








Remote radio site

RRU

MEF 22.2 Terminology

Base station site

Marco RBS

Network controller / gateway site

SGW, MME

Small cell site

Small RBS

Fronthaul Backhaul

Midhaul Backhaul

Backhaul – macro/small cell to core

Midhaul – small cell to macro

Fronthaul – remote radio to baseband unit

Slide title 44 pt








MBH IA Timeline

2009 2010 2011 2012 2013 2014 2015 2016 2017

MEF 22

MEF 22.1

MEF 22.2.1

WD

MEF 22.2.1

LB

MEF 22.3 LB

Phase 1 – 2G/3G Phase 3 - Time/Phase Synchronization

Phase 2 – LTE (frequency synchronization)

Optional Roll-up

MEF 22.1.1

MEF 22.2

Phase 3 – multi-CEN

Phase 3 – Small cells

Slide title 44 pt








› After the publication of MEF 22.1.1, MEF conducted a MBH survey of its members

– Over 75% of respondents regularly worked on MBH

– Nearly 60% of respondents were from operators

› 15 questions were asked – Several were focused on

synchronization

MEF survey 2015

Slide title 44 pt








Which of the following radio technologies are being used for the mobile backhaul networks that you are working on?

0

2

4

6

8

10

12

10

7

9

8

12

8

10

1

2

8

6

LTE-‐FDD

LTE-‐TDD

LTE-‐A FDD

LTE-‐A TDD

UMTS

CDMA

GSM

TD SCDMA

Other

Not relevant

Radio Technology

Slide title 44 pt








How many Ethernet classes of service (MEF 23.1, MEF 22.1) does your company offer/use in mobile backhaul networks?

25

6

9

13

25

22

1 2 3 4 Not relevant Don't know

Multi CoS

Slide title 44 pt








Where there are two or more backhaul providers for a mobile backhaul service, what is the service provided between the RAN base staJon site (macro or small cell) and the RAN core?

0

2

4

6

8

10

12

14

16

18 17

7 7

9

1

8

6

E-‐Line, E-‐LAN, E-‐Tree and/or E-‐Access

IP VPN

SDH/OTN

MPLS L2VPN

Other

Not relevant

Service Type

Slide title 44 pt








What applicaJons will drive the accuracy requirement for Jme of day synchronizaJon at the RAN base staJon site?

0

2

4

6

8

10

12

14

6

10 10

3

6

1

3

4

2

13

CPRI

LTE-‐A TDD

LTE-‐TDD

MBMS

CDMA

OTDOA

eICIC

CoMP features

Other

Not relevant

Time synchronization

Slide title 44 pt








How is primary Jme synchronizaJon typically expected to be delivered?

53 34

3

9 Via the backhaul link (PTP, NTP)

At the mobile site (GPS)

Other

Not relevant

Sync delivery

Slide title 44 pt








When providing Jme sync over the backhaul link, do you expect that the backhaul provider or the mobile operator will provide the Jme service (i.e. Own the grand master)? That is, who will own the grand master?

44

9

28

19

Mobile operator

Backhaul provider

Mobile and backhaul operator

Not relevant

Sync as a Service

Slide title 44 pt








If GPS is the primary source of Jme sync, do you typically expect to have GPS backup (E.g. with Jming support over the backhaul network)?

50

25

25

Yes No Not relevant

GPS Backup

Slide title 44 pt








What are the three biggest challenges in mobile backhaul?

0

2

4

6

8

10

12

14

16

18

20 19

15 15

7 8

3

11

5 4

3

Time sync

Delay requirements

Bandwidth requirements Site acquisi\on

Small cells site acquisi\on Fronthaul availability

Availability of backhaul

Availability of backhaul for small cells Other

Challenges

Slide title 44 pt








›  If GNSS is the primary source of time sync, a)  do you typically expect to have GNSS backup, and b)  if yes what solution?

›  Is security (specifically authentication of the timing master and integrity of the timing signal) and reliability of timing considered a concern for PTP based solutions?

›  In the case that the mobile operator owns the time sync master:

– Is timing across a backhaul operator network expected to be handled with full on-path timing support or via partial on-path timing support?

› Are you interested in partial timing support (some network segments are timing unaware)?

MEF survey 2016 AddiJonal quesJons for an upcoming survey.

Slide title 44 pt








MEF 22.2.1 – time sync

Mobile Operator RAN BS site

Mobile Operator RAN NC site

UNI UNI

CEN

UNI-N UNI-N

RAN CE RAN CE

UNI-C UNI-C

Use case (2): MO owns PRTC

PRTC

Mobile Operator RAN BS site

Mobile Operator RAN NC site

UNI UNI

CEN

UNI-N UNI-N

RAN CE RAN CE

UNI-C UNI-C

Use case (1): CEN owns PRTC

PRTC

Slide title 44 pt








› Time synchronization has newly increased importance – Need to combine different solutions – Packet solutions aligning with ITU-T Recommendations

› MEF moving to define solutions to offer “sync as a service” – MEF 22.2.1 will be the enabler

› Fronthaul: – Sync related aspects might be addressed in the future by MEF – Work ongoing in other relevant bodies, e.g. IEEE 802.1CM needs to

be completed first

› MEF Survey 2016 questions: – Comments and suggestions welcome

summary

Documents

5-08 Ericsson Parsons MEF Survey on Sync · 2018. 11. 5. · radio site RRU MEF 22.2 Terminology Base station site Marco RBS Network controller / gateway site SGW, MME Small cell