Data traffic:
Data networks are predominantly packet switched and probabilistic in nature. Probabilistic networks operate on best-effort delivery unlike deterministic networks, which guarantee delivery. Each message to be transmitted through the network is first divided into a number of smaller, self-contained message units known as packets that are then routed to their destination. Each packet may take a different route from origin to destination, traveling along network circuits that are shared with packets from other messages. Packet switching mandates that each packet should have its own header information, to ensure proper routing and to reconstruct the message in its correct sequence at the destination. Transmission of data through the network may be on a virtual circuit basis, or on a datagram basis, depending on the implementation. Packet switched networks are known for economic utilization of network resources. One of the largest data networks known today is the Internet. Other examples are X.25, Frame-Relay and corporate IP networks.
The most important factors that contribute to the success of any leading-edge technology are commercial viability and technical feasibility. It should make good business sense and be able to be implemented with minimal disruption to the existing network
There are cost reduction benefits in terms of toll bypass like overcoming long distance charges. Packetizing voice communications into IP packets and sending them over the existing corporate WAN infrastructure can significantly reduce telephone bills. This is accomplished by interleaving the voice packets into the pockets of bandwidth created by the "bursty" nature of data traffic. One of the largest segments of a corporation's telecommunications bill is international fax charges. These costs can be greatly reduced by sending the fax traffic over the corporate Voice over IP infrastructure.
Most corporate WANs are provisioned to support the high-end of the normal traffic load. Most of the times there will be an excess of capacity in the WAN environment that would normally be sitting idle, waiting for the "peak periods" of traffic. Leveraging the existing IT infrastructure to take advantage of its excess of resources can provide clear, crisp voice communication that is cost effective.
Collaborative Computing/Unified Messaging-voice, data and multimedia messages can be a part of a communication. All three media types can be stored in a common message store or database, enabling easy voice annotation of e-mail or inclusion of a video clip into an e-mail message. A single interface to the message store, either a desktop device or a phone, can access either type of message. Now voice messages can be retrieved from your e-mail user interface and played over your PC's speakers. Or, you can have your e-mail read to you over the phone as you are rushing to catch a plane. With a simple phone command, you can forward a critical e-mail message to an assistant to respond to in your absence, providing faster closure of key business issues.
Reliable phone to phone, PC to phone and PC to PC communication voice conversations can be established from a PC to a PC, a PC to an internal or external phone, or between two phones with access to a Voice over IP gateway. Some service providers (ISPs and telcos) are beginning to offer these gateway services.
For any technology to be widely implemented, endorsement from standards bodies is an absolute necessity. VoIP has the blessings of ITU (International Telecommunications Union), IETF (Internet Engineering Task Force), VoIP (Voice Over Internet Protocol) Forum, ETSI (European Telecommunications Standards Institution) and IMTC (International Multimedia Teleconferencing Consortium).
Ever since the 1970s, there were attempts to converge voice and data networks. The evolution of the digital PBX in the early '70s and CTI in the late '80s, and all the lessons learned thereafter through the triumphs and failures, has culminated in an open and a standards-based VoIP solution.
Contemporary LANs had shared backbones with probabilistic access mechanisms. Today's switched backbones are an absolute Star topology with dedicated bandwidth to the desktops. Voice Local Area Networks (PBX wiring) are also absolute Star topology. Conclusion: Similar topologies and more deterministic LAN.
Every Wide-Area data Network is connection-oriented, or if connectionless, is built on reliable media. As an example, X.25 has elaborate error correction mechanisms up to Layer 3, and Frame-Relay is built under the assumption of total reliable error free media. ATM is totally connection-oriented. Conclusion WAN links were always made to be more deterministic.
Consider closely a T-1/ E-1 line that is provisioned by your carrier. A T1 line has 24 channels of 64 Kbps.
Have you wondered why T1 is 1.544 Kbps (E1 is 2.048 Kbps)? Every line that is provisioned and/or conditioned by your carrier has something to do with voice. The underlying premise for sampling at 8000 times a second (that is, every 125 microseconds) comes from the Nyquist criterion for voice bandwidth. For T1, 193 bits are used per sample, 8000 times a second, which is nothing more than 1.544 Mbps. E1 uses 256 bits per sample every 8000 times a second, which is 2.048 Mbps. Conclusion: Every data trunk that exists today is built on voice based parameters.
The ability to make a voice call over an IP-based network poses a lot of challenges. This section elaborates all the challenges.
-
High bandwidth required for a toll quality call (64 Kbps/call).
-
Low end-to-end delay (<250 ms).
-
Connection-oriented voice call on connection-less network.
Quality of voice is a highly subjective parameter. MOS (Mean Opinion Score) is a widely used methodology to define quality of voice. MOS is measured on a scale of 1 to 5, where 5 is the best quality. MOS between 4 and 5 is considered toll quality, and 3.5 to 4 is considered acceptable communication quality.
To achieve toll quality, dedicated bandwidth of 64 Kbps per voice channel is required. This type of coding technique is called PCM (Pulse Code Modulation). This bandwidth is almost impossible to dedicate in a data network. Various compression algorithms are being used to reduce this stringent bandwidth requirement. ADPCM (Adaptive Differential Pulse Code Modulation) further reduces the bandwidth required to 32 Kbps. Digital Signal Processing (DSP) based Code Excited Linear Prediction (CELP) can further reduce the bandwidth required per voice channel to 5.6 Kbps. Various standards as defined by ITU exists today. By far the most popular standard is the G.723.I. This technique is part of H.323 (Video on IP) standard. But solving the bandwidth problems creates another major Issue.
Compressing voice to lower bandwidths results in a lower MOS rating and higher delay. Acceptable delay should be less than 250 ms. Various sources of delay are listed in the next section.
Delay can be categorized into two components: namely, fixed and variable.
Fixed/Controllable delay:
-
Compression Delay
-
Processing Delay
-
Buffering/Queuing Delay
-
Transmission Delay
-
LAN Network Delay
-
Decompression Delay
Compression and decompression delay is small, and is a maximum of 50 ms. The use of higher memory and better processors can reduce processing and buffering delays in a router. The LAN delay that comes into picture for a Web-based voice application can be kept to a minimum limit by using point-to-point switched topology. The end-to-end sum of fixed delays is usually less than 130 ms.
Variable or network delay is the delay in the IP/WAN/Internet cloud, which is out of our control. The next section deals with solving this problem.
Network delay was by far the most hindering factor in the voice-data convergence. This section analyzes some of the contributing factors for convergence. Running real time voice to voice applications on a probabilistic IP data network has its own challenges. However, the number of enabling factors far outweigh the disadvantages.
Technically speaking, advances in the field of QOS, which have contributed to the IP stack, tend to make a probabilistic data network more deterministic. The most promising solution to this problem was developed and standardized by the IETF. Resource ReSerVation Protocol (RSVP) can prioritize and guarantee latency to specific IP traffic streams. RSVP enables a packet-switched network to emulate a more deterministic circuit-switched voice network. (It should be noted that RSVP still works on best effort delivery.) RSVP is an OSI Layer3 protocol with routing support, and thus can be seamlessly integrated into an IP-based router/switch/network. With the advent of RSVP, VoIP has become a reality today. Most of the VoIP product vendors support RSVP. Details on this protocol are described in RFC 2208. In summary, with RSVP enabled for a voice stream, we can accomplish voice communication with tolerable delay on a data network.
The recent advance in data networking over the past decade has made VoIP a feasible technical alternative to PSTN for corporate voice communications. There are still some legal and regulatory hurdles to be crossed in some countries. It is at least safe to say that companies can employ VoIP for PBX-to-PBX networking. Reducing the bandwidth required per voice channel and having a greater control over the delay factor on the network, combined with significant cost benefits, have finally culminated into a unified voice-data network. Most large enterprises and service providers are investigating VoIP as a way to maximize utilization of existing TCP/IP infrastructure, minimize international telecommunications charges and enable the use of other converged applications, such as video and data conferencing, Web-based call centres and Unified Messaging. |