Convergence of communications: Difference between revisions
imported>Howard C. Berkowitz No edit summary |
John Leach (talk | contribs) m (Text replacement - "]]" to "") |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{ | {{PropDel}}<br><br> | ||
{{Subpages}} | |||
{{ dambigbox| Convergence of communications | Convergence }} | |||
This definition of convergence does not attempt to standardize the applications themselves. Instead, it includes the technologies that enable application-specific communications to be transmitted over standard interfaces to information delivery systems using Internet Protocol, | '''Convergence of communications''', in varying and unfortunately not yet standard phrasings, is the goal of having all types of human-to-computer and computer-to-computer communications '''converge onto''' (i.e., all run over) a common infrastructure using Internet Protocol version 4 or Internet Protocol version 6. | ||
It is neither necessary, nor desirable from a security standpoint, that they all run over the public Internet. All of these services can be restricted to other than the Internet, such as intranets or extranets. | |||
This definition of convergence does not attempt to standardize the applications themselves. Instead, it includes the technologies that enable application-specific communications to be transmitted over standard interfaces to information delivery systems using Internet Protocol, Session Initiation Protocol, and similar protocols and interfaces.<ref name=AboutVoIP>{{citation | |||
| title = VoIP and Communications Convergence: What is Communications Convergence? | | title = VoIP and Communications Convergence: What is Communications Convergence? | ||
| first = Nadeem | last = Unuth | | first = Nadeem | last = Unuth | ||
Line 11: | Line 15: | ||
}}</ref> | }}</ref> | ||
Converged services may use custom software (e.g., | Converged services may use custom software (e.g., private branch exchange) on a purpose-built router, or a general-purpose computer. | ||
*{{r|Data (general)|Data|}} | *{{r|Data (general)|Data|}} | ||
Line 34: | Line 38: | ||
*{{r|Telemedicine||}} | *{{r|Telemedicine||}} | ||
*{{r|Multimedia||}} | *{{r|Multimedia||}} | ||
Line 47: | Line 48: | ||
**{{r|Broadcast radio||}} | **{{r|Broadcast radio||}} | ||
**{{r|Pay-per-view audio content||}} | **{{r|Pay-per-view audio content||}} | ||
**{{r|Telephone||}} using | **{{r|Telephone||}} using Voice over Internet Protocol (VoIP) | ||
*{{r|Television||}} | *{{r|Television||}} |
Latest revision as of 03:39, 5 April 2024
This article may be deleted soon. | ||
---|---|---|
This article is about Convergence of communications. For other uses of the term Convergence , please see Convergence (disambiguation).
Convergence of communications, in varying and unfortunately not yet standard phrasings, is the goal of having all types of human-to-computer and computer-to-computer communications converge onto (i.e., all run over) a common infrastructure using Internet Protocol version 4 or Internet Protocol version 6. It is neither necessary, nor desirable from a security standpoint, that they all run over the public Internet. All of these services can be restricted to other than the Internet, such as intranets or extranets. This definition of convergence does not attempt to standardize the applications themselves. Instead, it includes the technologies that enable application-specific communications to be transmitted over standard interfaces to information delivery systems using Internet Protocol, Session Initiation Protocol, and similar protocols and interfaces.[1] Converged services may use custom software (e.g., private branch exchange) on a purpose-built router, or a general-purpose computer.
References
|