Preparing your result...
Loading...
Press Esc to dismiss this message

VoIP Traffic Simulator Architecture (25-Jun-2004)

Thumbnail
IP.com Prior Art Database Disclosure (Source: IPCOM)
Disclosure Number IPCOM000028322D dated 25-Jun-2004
Originally published in The IP.com Journal v4n6
Disclosed by: Siemens AG
Country: Portugal
Copyright: SIEMENS AG 2004
Related People
Juergen Carstens - CONTACT
juergen.carstens@siemens.com
+49-89-636-82995
Disclosure File: 2 pages / 25.6 KB / English (United States)

A special software architecture permits to simulate N independent Voice over Internet Protocol (VoIP). The software architecture is based on a multithread and multiprocess approach, where each pair of threads represents a peer of VoIP conversation. Each peer of the conversation is located in one independent machine. Figure 1 depicts the main architecture. The NTP server and NTP client blocks represent the processes responsible for the synchronization of the machines. The synchronization uses the protocol NTP (Network Time Protocol) and a proprietary algorithm that leads to a reduction of network delay and network asymmetry effects on the synchronization.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

S

VoIP Traffic Simulator Architecture

Idea: Elvino Rodrigues, PT-Lisbon; Nuno Silva, PT-Lisbon

A special software architecture permits to simulate N independent Voice over Internet Protocol (VoIP). The software architecture is based on a multithread and multiprocess approach, where each pair of threads represents a peer of VoIP conversation. Each peer of the conversation is located in one independent machine. Figure 1 depicts the main architecture.

The NTP server and NTP client blocks represent the processes responsible for the synchronization of the machines. The synchronization uses the protocol NTP (Network Time Protocol) and a proprietary algorithm that leads to a reduction of network delay and network asymmetry effects on the synchronization.

Two threads model each peer of the conversation. The master thread is responsible for sending the RTP (Real Time Protocol) voice packets, while the slave thread receives the voice packets from the other peer. The master thread at machine1 is also responsible for controlling the voice model. The voice model is based on artificial conversational speech concerning the standard ITU-T P.59 and coded accordingly a pre-defined codec. The codec used could be one of the following: G.723.1, G.729, G.728 and G.711.

The server and client major blocks represent a control layer, which allows to create the correct number of threads and to accomplish with the initial synchronization between peers. The server block is responsible for gathering...

(Source: IPCOM)
First page image
(Source: IPCOM)