QoS-enabled voice support in the next-generation Internet: issues, existing approaches and challenges

Bo Li, Mounir Hamdi, Dongyi Jiang, Xi Ren Cao, Y. Thomas Hou

Research output: Contribution to journalArticlepeer-review

44 Citations (Scopus)

Abstract

The Internet is under rapid growth and continuous evolution in order to accommodate an increasingly large number of applications with diverse service requirements. In particular, Internet telephony, or voice over IP is one of the most promising services currently being deployed. Besides the potentially significant cost reduction, Internet telephony can offer many new features and easier integration with widely adopted Web-based services. Despite these advantages, there still exist a number of barriers to the widespread deployment of Internet telephony such as the lack of control architectures and associated protocols for managing calls, a security mechanism for user authentication, and proper charging schemes. The most prominent one, however, is how to ensure the QoS needed for voice conversation. The purpose of this article is to survey the state-of-the-art technologies in enabling the QoS support for voice communications in the next-generation Internet. In this article, we first review the existing technologies in supporting voice over IP networks, including the basic mechanisms in the IETF Internet telephony architecture and ITU-T H.323-related Recommendations. We then discuss the IETF QoS framework, specifically the Intserv and Diffserv framework. Finally, we present two leading companies' (Cisco and Lucent) solutions to offering IP telephony services as examples to illustrate how real systems are implemented.

Original languageEnglish
Pages (from-to)54-61
Number of pages8
JournalIEEE Communications Magazine
Volume38
Issue number4
DOIs
Publication statusPublished - Apr 2000

Fingerprint

Dive into the research topics of 'QoS-enabled voice support in the next-generation Internet: issues, existing approaches and challenges'. Together they form a unique fingerprint.

Cite this