CommonPublicRadioInterface

eCPRIpresentation

2017EricssonAB,HuaweiTechnologiesCo.Ltd,NECCorporationandNokia.
Background1/2
1.OperatorviewofCPRIfeatures

AlthoughCPRIhasbeenthemainFronthaulinterfacestandard,manyoperatorsstarted
toquestionitssuitabilitytohighbandwidth5Gusecases.
Improvementstoefficiencyandlinkcapacityutilizationwererequested.
AlsoadvancednetworkingandOAMfeaturesofmainstreampackettransport
standardswererequested.
Background2/2
2.HighriskofFragmentationforFHStandardization

Anincreasingnumberofproposalsforanewfunctionalsplitsbetweenthebaseband
andradiostartedtoemerge.
SeveralstandardizationbodiesannouncedactivitiestodefinenewFronthaul
Interfaces.

High - Low - High - Low - High -

RRC PDCP Low - PHY RF
RLC RLC MAC MAC PHY

Data Option 1 Option 2 Option 3 Option 4 Option 5 Option 6 Option 7 Option 8

High - Low - High - Low - High -

RRC PDCP Low - PHY RF
RLC RLC MAC MAC PHY

Options in 3GPP RAN3 discussions

Data
TargetsagreedforthenewCPRI
Specification:
1. Significantreductionofrequiredbandwidth
2. Moreefficientutilizationofavailable
bandwidth
3. Enableevolutionforradioprocessingand
supportofsophisticatedcoordination
algorithmstoguaranteebestpossibleradio
performance
4. Carefullyselectthefunctionalitiesoftheradio
unitinordertoenableevolutionbySW
updatesandlonglifespanoftheradiounits
5. Utilizeexistingmainstreamtechnologiesto
minimizeduplicatedspecificationwork
6. Encourageutilizationofexistingtechnologies
forOAMandnetworking
7. Befirsttothemarket,becomingthe
prevailingfronthaulstandardandminimizing
fronthaulstandardsfragmentation
eCPRIkeyFeatures:
1. ~10foldreductionofrequiredbandwidth
2. Requiredbandwidthcanscaleflexibly
accordingtotheuserplanetraffic
3. FunctionalsplitinsidePHYlayerenables
supportofsophisticatedcoordination
algorithms
4. SplitinPHYkeepsmostofthefunctionalityin
basebandenablingnewfeatureintroduction
withoutchangesintheradioequipment
5. EncourageutilizationofEthernetandIP,thus
guaranteeingfutureevolution
6. UseEthernet/IPtechnologiesencouraged
7. eCPRIspecificationV1.0publishedandopenly
availabletodownloadfromwww.cpri.info
CPRIreminder
WhatisCPRI?

AdigitalinterfacestandardtotransportantennasamplesbetweenaRadioEquipment(RE)and
aRadioEquipmentControl(REC)performingthedigitalprocessingofthesesignals
AntennassignalsareinterleavedinaTDMlikefashionsupportedbyaConstantBitRate
transportsolution
CPRIv7.0bitratesrangefrom614Mbit/s(Rate1)upto24330Mbit/s(Rate10)
MixofRadioAccessTechnologiesissupported
ProvidetimeandsynchronizationinformationfortheRadioAirInterface
Originallyspecifiedforpointtopointtopology
Maximumlatencyassumingnointermediatenodes
Multipointtopologiessupportedbutnetworkingmanagementlefttotheapplicationlayer
Interoperabilitylimitedtothelowlayerscoveredbythespecification
CPRIdefinehowtoexchangetheradiosignaldatanotthedatacontentitselfnorthe
associatedmanagementplane
CPRIreminder
CPRIProtocolStack

Control &
User Plane Management SYNC Levelofspecification
Plane

L1 Inband Protocol
Vendor Specific

Ethernet
IQ

HDLC
Layer 2
Data WelldefinedinCPRI
UMTS;CPRIV1andV2
Wimax ;CPRIV3
LTE;CPRIV4
GSM;CPRIV5

Time Division Multiplexing FullyspecifiedinCPRI

Layer 1
Electrical Optical Informativeonly,except
Transmission Transmission
clockrate
CPRIreminder
CPRIFrameStructure
eCPRIintroduction
eCPRIsystemarchitecture

eCPRIispacketbasedfronthaulinterfacedevelopedbyCPRIforum
SamelevelofinteroperabilityasCPRI
Ethernet/IPnetworking,synchronizationandsecurityrelyingonexistingstandards
eCPRIintroduction
eCPRImaincharacteristics

eCPRIdoesnotconstraintheuseofspecificnetwork anddatalinklayerprotocolstoformthe
network
AnytypeofnetworkcanbeusedforeCPRI,providedeCPRIrequirementsarefulfilled.
RequirementsfortheeCPRITransportNetworkaimtoensurethateCPRIsystemscan:
Usepacketbasedtransportnetworksolutions
Complywiththerequirementsassociatedwiththemorestringentradiotechnologies
featuresintermsof:
Timingandfrequencyaccuracy
Bandwidthcapacity,

eCPRIalsoencouragestheuseofexistingdefacto/dejurestandardprotocolsasmuchas
possiblewhereavailable
IncaseeCPRIUserPlaneoverEthernet directly, eCPRImessagesshallbetransmittedin
standardEthernetframes.ThetypefieldoftheEthernetframeshallcontaintheeCPRI
Ethertype (AEFE16)
eCPRIintroduction
eCPRIprotocolstackoverIP/Ethernet
eCPRI Services
other Connection
User Real-Time
eCPRI C&M Synchronization
Data Control
services OAM

e.g.
eCPRI protocol layer PTP SyncE
SNMP

UDP, TCP,
UDP SCTP, etc.
UDP

IP
ICMP
IPsec

Ethernet MAC VLAN (priority tag) MACsec

Ethernet
OAM
Ethernet PHY

eCPRIdoesnotrestricttheTransportNetworktobeEthernetorIPbased
eCPRIintroduction
eCPRInodefunctionaldecomposition

eCPRIenablesflexiblefunctionaldecompositionwhilelimitingthecomplexityofthe
eRE
SplitpointslocatedatthePHYlevel isonesetofexamplescoveredintheeCPRI
specification
eCPRIintroduction
eCPRIfunctionaldecomposition MAC MAC

Coding De-coding

Rate Matching Rate Matching

Scrambling De-scrambling

D Modulation De-modulation

iDFT

Layer Mapping Equalization

Diversity Combiner

Precoding TX Power Channel Estimation

D Resource Element Mapping

U Resource Element Demapping

Beamforming Port Expansion Port Reduction

iFFT FFT

Cyclic Prefix Insertion Cyclic Prefix Removal

RF RF
eCPRIintroduction
eCPRItypicalbandwidthestimationsassumptions

Throughput:3/1.5Gbps (DL/UL,enduserdatarate,transportblockfrom/toMAC)
Airbandwidth:100MHz(5*LTE20)>500PRB
NumberofdownlinkMIMOlayers:8
NumberofuplinkMIMOlayers:4(with2diversitystreamsperuplinkMIMOlayer)
MUMIMO:No
TTIlength:1ms
DigitalbeamformingwhereBFcoefficientscalculationisperformedineREC.
Ratematchingassumptions:Coderate:~0.80
Modulationscheme(Downlink&Uplink):256QAM
Numberofantennas:64
Subcarrierspacing:15kHz
IQsamplingfrequency:122.88Msps (3.84*32)
IQformat:30bitsperIQsample
NoIQcompression
eCPRIintroduction
eCPRItypicalbandwidthestimations

SplitD SplitID SplitIID SplitE

User Control User Control User Control User
Data Data Data Data
[Gbps] [Gbps] [Gbps] [Gbps] [Gbps] [Gbps] [Gbps]

eREC eRE
3 <<1 <4 <10 ~20 <10 236
(assumption)

SplitD SplitIU SplitE

eRE eREC
1.5 <<1 ~20 <10 236
(assumption)
eCPRIUserPlanemessages
eCPRIMessagesCommonHeaderformat

4byteeCPRIcommonheaderfollowedbyavariablelengtheCPRIpayload
Byte

1 eCPRI

2 Common Header

3
Bytes
transmitted
4 eCPRI Payload (First Byte) from top
to bottom

4..65539 eCPRI Payload (Last Byte)

0 7

MSB LSB
eCPRIUserPlanemessages
eCPRIMessagesCommonHeaderformat

CistheeCPRImessagesconcatenationindicator:
C=0indicatesthattheeCPRImessageisthelastoneinsidetheeCPRIPDU
C=1indicatesthatanothereCPRImessagefollowsthisonewithintheeCPRIPDU
eCPRIUserPlanemessages
eCPRIMessagesCommonHeaderformat:concatenationindicator
eCPRIUserPlanemessages
eCPRIMessagesCommonHeaderformat:concatenationindicator

0-3Byte(s)
Padding
eCPRIUserPlanemessages
eCPRIMessagetypes

MessageType# Name
0 IQData
1 BitSequence
2 RealTimeControlData
3 GenericDataTransfer
4 RemoteMemoryAccess
5 OnewayDelayMeasurement
6 RemoteReset
7 EventIndication
8 63 Reserved
64 255 VendorSpecific
eCPRIUserPlanemessages
eCPRIMessagetypesfordatatransfer:#0,#1,#2and#3

MessageType#0:IQData
TotransfertimedomainorfrequencydomainIQsamplesbetweenPHYprocessingelementssplit
betweeneCPRInodes
MessageType#1:BitSequence
TotransferuserdatainformofbitsequencebetweenPHYprocessingelementssplitbetweeneCPRI
nodes
MessageType#2:RealTimeControlData
TotransfervendorspecificrealtimecontrolmessagesbetweenPHYprocessingelementssplitbetween
eCPRInodes(eRECandeRE).Thismessagetypeaddressestheneedtoexchangevarioustypesofcontrol
informationassociatedwithuserdata(informofIQsamples,bitsequence,etc.)betweeneCPRInodesin
realtimeforcontrol/configuration/measurement
MessageType#3:Generic DataTransfer
TotransferuserplanedataorrelatedcontrolbetweeneCPRInodes(eRECandeRE)providingextended
datasynchronizationsupportforgenericdatatransfers.
eCPRIUserPlanemessages
eCPRIUserPlanemessageformats
eCPRIUserPlanemessages
MessageType#3:GenericDataTransfersequencediagramexample

eCPRI eCPRI
Node 1 Real Node 2
- Tim
e Co
n
for P trol infor
User C _ID= matio
data a n
(PC_ for O
ID=a FDM sym
, SEQ b
_ID= ol#0
User 0)
data
(PC_ for OFD
ID=a M
, SEQ symbol#
_ID= 1
5) TTI or
subframe
User
data
(PC_ for OFD
ID=a M
, SEQ symbol#
_ID= N
N-1) -1
eCPRIUserPlanemessages
eCPRIMessagetypesforRemoteMemoryAccess:#4

MessageType#4:RemoteMemoryAccess
ThemessagetypeRemoteMemoryAccessallowsreadingorwritingfrom/toaspecific
memoryaddressontheoppositeeCPRInode.Theserviceissymmetrici.e.anysideof
theinterfacecaninitiatetheservice.
Theserviceisconceivedinagenericwaytohandledifferentkindsofwriteandread
accessthatdependonthehardwareusedinaspecificimplementation.Itisuptothe
driverroutinesforanimplementationtomapawrite/readrequesttoitshardware
implementation.
Areadorwriterequest/responsesequenceisanatomicprocedure,i.e.arequester
needstowaitfortheresponsefromthereceiverbeforesendinganewrequesttothe
samereceiver.Awriterequestwithoutresponseisalsodefined,thisprocedureisa
onemessageprocedure.
eCPRIUserPlanemessages
MessageType#4:RemoteMemoryAccess
Byte

0 Remote Memory Access ID

1 Read/Write Req/Resp

2
Element ID
3

Address

10
Length = L
11

12 Data (first byte)

11+L Data (last byte)

0 7
MSB LSB
eCPRIUserPlanemessages
MessageType#4:RemoteMemoryAccesssequencediagramexample
eCPRIUserPlanemessages
eCPRIMessagetypesforOneWayDelayMeasurement:#5

MessageType#5:OneWayDelayMeasurement
ThemessagetypeOneWaydelaymeasurementisusedforestimatingtheonewaydelay
betweentwoeCPRIportsinonedirection.Theonewaydelaymeasurementcanbe
performedwithoutorwithaFollow_Up message(1Stepand2Stepversions).Thedecision
ofwhichversiontouseisvendorspecific.

Theserviceassumesthatbothnodesaretimesynchronizedtoacommontimewithan
accuracysufficientfortheeCPRIservice.

TheusageofeCPRImessagetypeOneWaydelaymeasurementregardingwhichnode
initiatesatransmission,thefrequencyofmeasurements,responsedeadline,etc.isvendor
specific.
eCPRIUserPlanemessages
eCPRIMessagetypesforOneWayDelayMeasurement:#5

Twocompensationvaluesareusedtosetthemeasurementsreferencepointsassuited
foraspecificimplementation.Theexactlocationsofthereferencepointsarevendor
specific.
TheOneWaydelayvalueiscalculatedaccordingtofollowingequation:
tD =(t2 tCV2) (t1 +tCV1)
eCPRIUserPlanemessages
MessageType#5:OneWayDelayMeasurement
Byte

0 Measurement ID
1 Action Type
2

TimeStamp

11

12

Compensation Value

19

20 Dummy bytes (first byte)

19+L Dummy bytes (last byte)

0 7

MSB LSB
eCPRIUserPlanemessages
eCPRIMessageType#5:OneWayDelayMeasurementsequencediagramexample

eCPRI Node 1 eCPRI Node 2

t1
tCV1 OneWayDe
layMeasure
ment(ID, Re
qu est,t1,tCV )
1
t2
tCV2

2 CV2 tD =(t2 tCV2) (t1 +tCV1)

tD =(t2 tCV2) (t1 +tCV1)

OneWayDe
layMeasure
m ent(ID,Rem
o teRequest)

t1 tCV1

eque st,t1,tcv1)
e layM ea su rement(ID,R
OneWayD
tCV2 t2

OneWayDe
tD =(t2 tCV2) (t1 +tCV1) layMeasure
ment(ID,Re
sponse,t ,t
2 CV2)
tD =(t2 tCV2) (t1 +tCV1)
eCPRIUserPlanemessages
eCPRIMessageType#5:OneWayDelayMeasurementsequencediagramexample

eCPRI Node 1 eCPRI Node 2

t1
tCV1 OneWayDelay
Measurement(
ID,Requestwfu
,0,0)

OneWayDelay tCV2
Measurement( t2
ID,Follow_Up,
t1,tCV1)
tD =(t2 tCV2) (t1 +tCV1)
2 CV2

tD =(t2 tCV2) (t1 +tCV1)

OneWayDelay
Measurement(
ID,RemoteRe
qu estwfu)
t1 tCV1

1 CV1
tCV2 t2

tD =(t2 tCV2) (t1 +tCV1) OneWayDelay

Measurement(
ID,Response,t
2,tCV2)
tD =(t2 tCV2) (t1 +tCV1)
eCPRIUserPlanemessages
eCPRIMessagetypesforRemoteReset:#6

MessageType#6:RemoteReset
ThismessagetypeisusedwhenoneeCPRInoderequestsresetofanothernode.A
RemoteResetrequestsentbyaneRECtriggersaresetofaneRE.

Byte

0
eCPRI Node 1 eCPRI Node 2
Reset ID
1 eCPR
I Rem
ote R
2 Reset Code Op= Request/Indication Requ eset/
est
3 Vendor Specific Payload (first byte) /
ote Reset
m
L bytes

I Re
eCPR esponse
R

2+L Vendor Specific Payload (last byte)

0 7

MSB LSB
eCPRIUserPlanemessages
eCPRIMessagetypesforEventIndication:#7

MessageType#7:EventIndication
ThemessagetypeEventIndicationisusedwheneithersideoftheprotocolindicatestothe
otherendthataneventhasoccurred.Aneventiseitheraraisedorceasedfaultora
notification.TransientfaultsshallbeindicatedwithaNotification.
Faults/NotificationssentoneCPRIlevelshouldberelevanttotheeCPRIservices.
OneEventIndicationcaneithercontainoneormorefaults,oroneormorenotifications.
TheEvent/FaultIndicationmessagecouldbesentfromaneCPRInodeatanytime.
AneCPRInodeismodelledasconsistingofNElements,afaultornotificationisconnectedto
1Element.ThedetailedmappingofaspecificimplementationofHWandSWtoElements
andtheirassociatedfaults/notificationisvendorspecific.
Forconsistencycheckasynchronizationrequestprocedureisdefined.
 Byte

eCPRIUserPlanemessages
MessageType#7:EventIndication
0 Event ID
1 Event Type
2 Sequence Number
3 Number of Faults/Notif = N
4
Element ID #1
5

6 Raise/Cease #1 Fault/Notif #1 MSB

7 Fault/Notif #1 LSB
8

9
Additional Information #1
10

11

12+8x(N-1)
Element ID #N
13+8x(N-1)

14+8x(N-1) Raise/Cease #N Fault/Notif #N MSB

15+8x(N-1) Fault/Notif #N LSB
16+8x(N-1)

17+8x(N-1)
Additional Information #N
18+8x(N-1)

19+8x(N-1)

0 7

MSB LSB
eCPRIUserPlanemessages
MessageType#7:EventIndicationsequencediagramexample
eCPRI Node 1 eCPRI Node 2

Event Ind
ication(ID
, Sync_Re
q)

k)
atio n(ID , Sync_Ac
ic
Event Ind

One synchronization procedure

))
S eq_N r, Fault Ind(s
ault,
ent Indication(ID, F
Ev
Event Ind
ication(ID
, Fault_Ac
k, Seq_Nr
)

d(s))
, Seq_N r, Fault In
, Fault
ication(ID
Event Ind
Event Ind
ication(ID
, Fault_Ac
k, Seq_N
r)
ync _End)
ent Indic ation(ID, S
Ev
eCPRIC&M
ControlandManagementServiceAccesspoint

The C&M information will not be transmitted via the eCPRI specific protocol.
The details of this information flow are out of the scope of the eCPRI specification.
This information flow can use protocols (e.g. TCP) over the IP protocol but any other
solution is not precluded.

The C&M information flow will be considered as nontimecritical and utilize a small part
of the total bandwidth between eCPRI entities.

The majority of this information flow will be considered as background traffic, the rest is
interactive traffic needed to keep control of the eCPRI node.
The eCPRI specification highlights some considerations regarding relative priorities of the
different flows.
eCPRISynchronization
SynchronizationServiceAccesspoint

eCPRI nodes shall recover the synchronization and timing from a synchronization
reference source, and the air interface of the eRE shall meet the 3GPP synchronization
and timing requirements.

The synchronization information will not be transmitted via the eCPRI specific protocol.
The details of this information flow are out of the scope of the eCPRI specification.
This information flow can use protocols (e.g. SyncE, PTP) but any other solution is not
precluded.

The synchronization information flow will be considered as timecritical and will utilize a
small part of the total bandwidth between eCPRI nodes.
eCPRINetworking(1/2)
CPRInetworkingreminder

CPRI networking example

eCPRINetworking(2/2)
eCPRInetworkingprinciple

eCPRI networking example