/
IEEE1 904.3 IEEE1 904.3

IEEE1 904.3 - PowerPoint Presentation

phoebe-click
phoebe-click . @phoebe-click
Follow
361 views
Uploaded On 2017-04-17

IEEE1 904.3 - PPT Presentation

Radio over Ethernet update Jouni Korhonen IEEE 8021TSN Berlin 2015 1 Disclaimer T his is not an official IEEE 1904 WG output just an informal update what is happening regarding Radio over Ethernet in ID: 538368

1904 ieee f2f amp ieee 1904 amp f2f 2015 radio ethernet update telcos meeting mapper

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "IEEE1 904.3" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

IEEE1 904.3 Radio over Ethernet update

Jouni KorhonenIEEE 802.1TSN @Berlin 2015

1Slide2

Disclaimer

This is not an official IEEE 1904 WG output; just an informal update what is happening regarding Radio over Ethernet in IEEE 1904.3

.

2Slide3

What, when and where..

What:Standards development for Radio over Ethernet (RoE

) encapsulation and a CPRI mapper

.

Quite close what IEEE 1722 is for AVB..

When:

F2f meeting ~every second month.

Biweekly telcos to discuss technical details (information available in IEEE 1904.3 reflector).Where:Hosted by IEEE 1904 ANWG as a IEEE 1904.3 TF.IEEE 1904.3 is individual project and anyone can join.

3Slide4

Progress since Atlanta update

IEEE 1904.3 TF formed.First f2f held in Feb. 2015.

Mostly procedural to get things up & running.

Next in

April 1-3,

2015; Louisville

, CO

USA.Three telcos since the first f2f. Agreed on the baseline for the work (to be ratified in the f2f meeting):Fixed the mapper & encap/decap function assumptions;1 EtherType only; subtypes in the header;1 type flow per packet (e.g. one AxC);Prepare for supporting both CBR & VBR flows;

Both seqnos and timestamps needed;

Alignment with 1588 datatypes desirable;

Reference time set to TAI;

4Slide5

Q & A

5

More data available:

http://www.ieee1904.org/3/index.shtml

Related Contents


Next Show more