Real-time communication

Source: Wikipedia, the free encyclopedia.
Not to be confused with Real-time computing or Real-time clock.

Real-time communication (RTC) is a category of software protocols and communication hardware media that gives real-time guarantees, which is necessary to support real-time guarantees of

protocols are dependent not only on the validity and integrity of data transferred but also the timeliness of the transfer. Real-time communication systems are generally understood as one of two types: Hard Real-Time (HRT) and Soft Real-Time (SRT).[2] The difference between a hard and soft real-time communication system is the consequences of incorrect operation. Safety-critical systems capable of causing catastrophic consequences upon a fault, such as aircraft fly-by-wire systems, are designated as hard real-time, whereas non-critical but ideally real-time systems, such as hotel reservation systems, are designated as soft real-time.[3]
The designation of a real-time communication system as hard or soft has significant influence on its design.

Hard real-time systems

Hard real-time communication systems are frequently electromechanically linked to a physical mechanism, often one that interfaces directly with people or property, which often contributes to or defines the potential danger of a fault. Due to their safety-critical nature, the communication protocols defined in a hard real-time system generally must be deterministic.[4] Hard real-time communication systems are particularly common in the transportation, industrial, and medical sectors. Common applications include control systems, automotive controllers, medical devices, and critical safety systems such as airbag firing computers.

Examples

  • The
    communication network SpaceWire supports real-time communication.[5]
  • Time-Triggered Ethernet supports real-time synchronous communication in complex multi-hop Ethernet networks.

Soft real-time systems

Unlike hard real-time communication systems, soft real-time communication systems generally do not have the capacity to cause catastrophic harm upon a fault, which allows for non-deterministic, less rigorous

Discord[7] and Google Meet.[8] Data transmitted over a soft real-time communication system is not stored in a centralized server, and peers are connected directly to one another rather than through a server, although intermediary connecting nodes between peers are allowed when a direct link cannot be established.[9]

Examples

  • WebRTC, an open-source real-time communication framework for mobile applications and web browsers, is the current most prominent implementation of real-time communication in the web-oriented telecommunications space.[10]

References

  1. ^ Sundaresan, Sharad; Bettati, Riccardo (11 July 1997). Distributed Connection Management for Real-Time Communication over Wormhole-Routed Networks. people.engr.tamu.edu (Technical report). Archived from the original on 17 December 2023. Retrieved 17 December 2023 – via Texas A&M University.
  2. ^ Doyle, Paula (May–June 2004). "Introduction to Real-Time Ethernet I" (PDF). The Extension: A Technical Supplement to Control Network. 5. Contemporary Control Systems, Inc: 1–4. Archived from the original (PDF) on 16 March 2023.
  3. ^ "IE304: Real Time Ethernet, Part 1". www.industrialethernetu.com. Retrieved 2022-03-26.
  4. doi:10.1016/S1474-6670(17)44865-8
    .
  5. ^ Dr Barry M Cook; Paul Walker. "Ethernet over SpaceWire - software issues". 2007.
  6. ISSN 1552-6607
    .
  7. ^ "How Discord Handles Two and Half Million Concurrent Voice Users using WebRTC". discord.com. Retrieved 2022-03-26.
  8. ^ "How does Hangouts use WebRTC? webrtc-internals analysis". webrtcHacks. 2014-07-29. Retrieved 2022-03-26.
  9. ^ "What is Real-Time Communications (RTC)?". www.realtimecommunicationsworld.com. Retrieved 2022-03-26.
  10. ^ Bubley, Dean (June 2018). "Emerging RTC use-cases" (PDF). Disruptive Analysis.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Real-time_communication&oldid=1195647784"