2015 IEEE Global Communications Conference (GLOBECOM) 2014
DOI: 10.1109/glocom.2014.7417599
|View full text |Cite
|
Sign up to set email alerts
|

A Performance Study of CPRI over Ethernet with IEEE 802.1Qbu and 802.1Qbv Enhancements

Abstract: There has been a debate on whether or not Ethernet, a highly cost effective technology, could meet the stringent latency and jitter requirements imposed by CPRI. To facilitate the discussion, we conducted simulations to understand how Ethernet performs when carrying CPRI traffic with the two Ethernet enhancements, currently being standardized by IEEE, namely frame preemption (802.1Qbu) and scheduled traffic (802.1Qbv). Our simulation results led to two conclusions: 1) Ethernet networks with or without frame pr… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
5

Citation Types

0
15
0

Year Published

2017
2017
2022
2022

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(15 citation statements)
references
References 10 publications
0
15
0
Order By: Relevance
“…Some works in the literature elaborate the requirements and implementation of the real-time scheduled traffic in TSN networks. For instance, references [3] and [4] give examples of applying Ethernet and scheduled TSN to in-vehicle and wireless communication systems, emphasizing the importance of scheduling. The evaluation in [3] proves that Ethernet is able to transport the traffics mixing of different vehicle functions but scheduling is necessary in the overload situations.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…Some works in the literature elaborate the requirements and implementation of the real-time scheduled traffic in TSN networks. For instance, references [3] and [4] give examples of applying Ethernet and scheduled TSN to in-vehicle and wireless communication systems, emphasizing the importance of scheduling. The evaluation in [3] proves that Ethernet is able to transport the traffics mixing of different vehicle functions but scheduling is necessary in the overload situations.…”
Section: Introductionmentioning
confidence: 99%
“…The evaluation in [3] proves that Ethernet is able to transport the traffics mixing of different vehicle functions but scheduling is necessary in the overload situations. In [4], results show that it is difficult for conventional Ethernet to fulfill the jitter requirements of Common Public Radio Interface (CPRI), while this problem could be solved by implementing enhanced scheduled traffic. The paper [5] proposed simulations of scheduled traffic in Audio Video Bridging (AVB) network.…”
Section: Introductionmentioning
confidence: 99%
“…For the latter, minimizing (or completely removing), any latency variation (including contention-induced) is important for achieving proper accuracy. Some work in the literature has been carried out to analyze the effects of contention with TSN features [13][14] in an Ethernet fronthaul and its effects on KPIs. Specifically [13] is an implementation of a time-aware shaper (TAS) in NS3 focusing on CPRI performance, while [14] presented an initial TAS implementation in Opnet with limited features.…”
Section: Introductionmentioning
confidence: 99%
“…Some work in the literature has been carried out to analyze the effects of contention with TSN features [13][14] in an Ethernet fronthaul and its effects on KPIs. Specifically [13] is an implementation of a time-aware shaper (TAS) in NS3 focusing on CPRI performance, while [14] presented an initial TAS implementation in Opnet with limited features. This work focuses on the scheduling of traffic in an Ethernet fronthaul network and presents a model implementation in Opnet of a TAS based on IEEE 802.1Qbv.…”
Section: Introductionmentioning
confidence: 99%
“…A number of papers have analysed the effects of contention, with [12][13][14] and without [15] scheduling, in an Ethernet fronthaul and its effects on KPIs. In this work, timeaware shaper (TAS) and SP models are built and configured, respectively, in OPNET.…”
Section: Introductionmentioning
confidence: 99%