Skip to main navigation Skip to search Skip to main content

A self-configuring communication virtual machine

  • S. Masoud Sadjadi
  • , Selim Kalayci
  • , Yi Deng

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

3 Scopus citations

Abstract

Today's communication-based applications are mostly crafted in a stovepipe development paradigm, which is inflexible to be used by various domain-specific applications and costly in the development phase. In a previous paper [1], we proposed a new design called CVM (Communication Virtual Machine) to overcome these problems by having a high-level API which can be reused and extended easily for user-centric applications in any domain. Within CVM framework, we came across a practical issue, which is actually the case for any end-to-end multimedia communication, namely the NAT-traversal (network address translation) problem that limits the reliability and availability of CVM and variants of CVM. In this paper, we explain about the necessity of self-configuration for the NAT-traversal problem in end-to-end communications, and propose a solution within the core CVM framework.

Original languageEnglish
Title of host publicationProceedings of 2008 IEEE International Conference on Networking, Sensing and Control, ICNSC
Pages739-744
Number of pages6
DOIs
StatePublished - 2008
Externally publishedYes
Event2008 IEEE International Conference on Networking, Sensing and Control, ICNSC - Sanya, China
Duration: 6 Apr 20088 Apr 2008

Publication series

NameProceedings of 2008 IEEE International Conference on Networking, Sensing and Control, ICNSC

Conference

Conference2008 IEEE International Conference on Networking, Sensing and Control, ICNSC
Country/TerritoryChina
CitySanya
Period6/04/088/04/08

Keywords

  • Autonomic computing
  • Communication virtual machine
  • Network address resolution
  • Self-configuration

Fingerprint

Dive into the research topics of 'A self-configuring communication virtual machine'. Together they form a unique fingerprint.

Cite this