Abstract
Modern cellular networks utilising the Long–Term Evolution (LTE) set of standards face an ever–increasing demand for mobile data from connected devices. Header compression is employed to minimise the overhead for IP–based cellular network traffic. In this paper, we evaluate the three header compression implementations used by such networks with respect to their potential throughput increase and complexity for different mobile service scenarios. We compare RTP, UDP and TCP profile compressions regarding their compression gain and complexity. Specifically, we consider header compression as defined by (i) IP Header Compression (RFC 2507), (ii) Robust Header Compression version 1 (RFC 3095), and (iii) the recently updated Robust Header Compression version 2 (RFC 5225) with TCP/IP profile (RFC 6846). This paper presents the performance evaluation of these header compression schemes for UDP, RTP and TCP, for both IPv4 and IPv6 streams in error–free and error–prone scenarios. A comparison between the Robust Header Compression methods and IP Header Compression is also provided. Our results show that all implementations have great potential for saving bandwidth in IP–based wireless networks, even under varying channel conditions. We also present for the first time an analysis of certain RTP header fields which, depending on the transmission characteristics, could have high impact on the overall compression gain.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
More From: Periodica Polytechnica Electrical Engineering and Computer Science
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.