Technology and Research
Intel® Technology Journal Home
Volume 10, Issue 01
Converged Communications
Table of Contents
Technical Reviewers
About This Journal
Intel Published Articles
Read Past Journals
Subscribe
E-Mail this Journal to a Colleague
Main Visual Description
Intel Technology Journal - Featuring Intel's Recent Research and Development
Converged Communications
Volume 10    Issue 01    Published February 15, 2006
ISSN 1535-864X    DOI: 10.1535/itj.1001.01

  Section 7 of 11  
Enterprise Converged Network–One Network for Voice, Video, Data, and Wireless
DISCUSSION

Converged networks offer great promise for converged communications by integrating voice, video, and data on LAN and mobile networks. As such, converged networks show great promise for the enterprise. However, the challenges are considerable in the areas of business, finance, and technology.

Should enterprises today take the plunge? We believe there is no simple answer to this question and the important thing to remember is that "one size does not fit all" anymore. In deciding whether converged networks are right for an enterprise, we offer the following advice:

  • Core vs. edge–Core services are normally centralized and controlled more closely than the edge; therefore, starting the move to convergence at the core is sometimes easier. Moreover, a lot of the immediate financial benefits are more easily seen on the core, since long-distance networks are a major part of the network discretionary spending, and convergence at the core can reduce spending considerably. On the other hand, the core is one of the most sensitive and mission-critical environments, if not the most.
  • New/Greenfield vs. legacy sites–When going into new construction an enterprise has to think ahead at least three years. We believe by this time converged networks are going to be the rule rather than the exception. Therefore, we would recommend considering using converged networks at new sites and campuses. Making the case for retrofitting existing infrastructures is much harder.
  • Risk taking–Making major changes to an existing environment is risky. In making the decision one has to weigh the risk vs. the gain. Starting convergence in a mission-critical manufacturing plant, design center, or customer support center is quite different from making that move in a standard office environment. Start small and expand as you gain experience and confidence.
  • Standard based vs. proprietary–Using standards offer a much better chance of interoperability, but some of the standards may still be in the certification track. Using existing proven proprietary protocols may be required as an interim step. The timetable for implementation will determine this choice ultimately.
  • Network management–Being successful in converged networks requires new capabilities for managing the converged networks including QoS management, security management, and real-time troubleshooting tools. Having this kind of management is crucial to success in this complex task.
  • Staff and technical expertise–Moving to converged networks requires a lot of talent and knowledge, radically different talent and knowledge gained from working with legacy networks. Making the change requires paying close attention to skill levels and training for both design and operations personnel.

  Section 7 of 11  

In This Article
Abstract
Introduction
LAN Readiness for Converged Communication
Folsom LAN and Voice Converged Network
Challenges
Results
Discussion
Conclusion
Acknowledgments
References
Authors' Biographies
Download a PDF of this article.   
Email This Page
Back to Top