Elective Data Communication

Data CommunicationUnit 611 min read

Transmission Impairments & Error Control: Noise, Attenuation, CRC, ARQ, Flow Control

Unit 6 of Data Communication covers how signals degrade during transmission (attenuation, distortion, noise), error detection/correction methods (parity, CRC, Hamming codes), flow control mechanisms (stop-and-wait, sliding window), and real-world applications in Nepalese systems like eSewa’s transaction retries and Nce

TAKEAWAYS:

  • Transmission impairments (attenuation, distortion, noise) degrade signal quality and must be mitigated via repeaters, equalizers, or error control.
  • Error detection uses parity bits, checksums, and CRC (cyclic redundancy checks) to identify corrupted frames (e.g., eSewa’s transaction failures).
  • Error correction employs Hamming codes or ARQ (Automatic Repeat reQuest) to recover lost data (e.g., Ncell’s call retries).
  • Flow control (stop-and-wait, sliding window) prevents buffer overflow in protocols like TCP (used in Daraz’s order processing).
  • Real-world ties: NTC’s fiber-optic backhaul reduces noise; Khalti’s CRC checks prevent fraudulent transactions.
  • Exam focus: Compare ARQ vs. FEC, calculate CRC remainders, and explain how impairments affect media (copper vs. fiber).

1. Transmission Impairments: Why Signals Fail

Data communication systems suffer from three primary impairments that distort or lose information during transmission. These are inherent to the medium and signal type, requiring mitigation strategies.

1.1 Attenuation: The Fading Signal

Definition: Loss of signal strength over distance due to resistance in the medium (e.g., copper cables) or absorption in wireless channels. How it works:

  • Cause: Energy dissipates as heat (copper) or spreads out (wireless).
  • Effect: Bits become indistinguishable (e.g., a 1 weakens to 0.3V instead of 5V).
  • Mitigation:
    • Repeaters: Amplify the signal (e.g., NTC’s fiber-optic repeaters every 80 km).
    • Regenerators: Retime and reshape signals (used in DSL modems).
graph LR
    A["Signal Source"] -->|"Attenuation"| B["Weak Signal"]
    B -->|"Repeater"| C["Amplified Signal"]
    C -->|"Regenerator"| D["Reshaped Bits"]

Real-world example:

NTC’s backbone network uses optical amplifiers every 80 km to combat attenuation in its 100Gbps links between Pokhara and Birgunj.


1.2 Distortion: The Bent Signal

Definition: Signal waves change shape, causing intersymbol interference (ISI) where one bit overlaps another. Types:

Type Cause Example
Amplitude Unequal gain across frequencies Phone line calls sounding "muffled"
Phase Delay differences in frequencies Wi-Fi signals losing sync
Delay Different path lengths (multipath) GPS signals arriving out of order

Mitigation:

  • Equalizers: Filter out distorted frequencies (used in DSL modems).
  • Echo cancellation: Removes reflected signals (e.g., VoIP apps like Pathao’s driver calls).

Worked Example: A 10 Mbps signal travels through a copper cable with 10% amplitude distortion. If the original amplitude is 5V, what’s the received amplitude for a 1 bit? Solution: Distortion reduces amplitude by 10% → 5V * 0.9 = 4.5V. Real tie: Daraz’s website load times slow if the ISP’s equalizer fails, causing packet distortion.


1.3 Noise: The Unwanted Signal

Definition: Random or man-made interference that adds errors to the signal. Types:

Type Source Effect
Thermal Electron motion in conductors White noise in all media
Crosstalk Adjacent wires interfering Phone calls hearing neighbor’s line
Impulse Lightning, switches Sudden bit flips (e.g., power surges)
Intermodulation Nonlinear mixing of frequencies Cable TV channel overlap

Mitigation:

  • Shielding: Copper cables use braided shielding (e.g., Ethernet CAT6).
  • Spreading: Wireless uses frequency hopping (Bluetooth) or spread spectrum (Wi-Fi).
  • Error control: Detect/correct errors (next section).

Real-world example:

Ncell’s 4G towers use shielded coaxial cables to prevent crosstalk between base stations, ensuring clear calls in crowded areas like Thamel.


2. Error Detection: Catching the Mistakes

Even with clean signals, errors slip through. Error detection identifies corrupted frames before they’re processed.

2.1 Parity Bits: The Simple Check

How it works:

  • Add a parity bit (0 or 1) to make the total number of 1s even (even parity) or odd (odd parity).
  • Limitations: Detects only odd-numbered errors (e.g., 1-bit flips).

Example: Transmit 1010 (even parity):

  • 1s: 2 → already even → parity bit = 0 → frame = 10100.
  • If received as 10110, parity fails (3 1s → error detected).

Real tie: eSewa uses parity checks in its initial transaction handshake to detect if a user’s payment request was corrupted during transmission.


2.2 Checksum: Summing Up the Data

How it works:

  • Divide data into 16-bit blocks, sum them, and transmit the 16-bit checksum.
  • Receiver recalculates; if mismatch → error.

Example: Data: 1010 1100 0011 0000 Sum: 1010 + 1100 + 0011 + 0000 = 10001 (16-bit wrap-around). Transmit checksum: 10001. Real tie: WhatsApp uses checksums to verify message integrity when you see "Message sent" but the recipient’s phone is offline.


2.3 Cyclic Redundancy Check (CRC): The Gold Standard

How it works:

  • Treat data as a binary polynomial (e.g., 1001101 = x⁶ + x⁴ + x² + 1).
  • Divide by a generator polynomial (e.g., x³ + 1).
  • Append the remainder as the CRC.

Example: Divide 1001101 (data) by 1011 (x³ + x + 1):

1001101000 ÷ 1011 = 1101 with remainder 100 → CRC = 100.

Transmit: 1001101100. Receiver recalculates; if remainder ≠ 0 → error.

Worked Example (from past exams): Frame: x⁴ + x³ + 1 (100101), Generator: x³ + 1 (1001). Solution:

  1. Align and divide:
    100101000 ÷ 1001 → 111 remainder 100 → CRC = 100.
    
  2. Transmit: 100101100.
  3. Receiver checks: 100101100 ÷ 1001 → remainder 0 = valid.

Real-world tie: Khalti’s transaction IDs use CRC to ensure your payment isn’t altered in transit. If the bank’s server detects a CRC mismatch, it rejects the transaction.


3. Error Correction: Fixing the Errors

Detection alone isn’t enough—error correction recovers lost data.

3.1 Hamming Codes: The Math Behind Correction

How it works:

  • Add redundant bits at positions that are powers of 2 (1, 2, 4, 8…).
  • Calculate parity for each bit position to locate errors.

Example (3-bit data + 4 parity bits): Data: 101 → 1101011 (with parity bits). If received as 1111011, the parity bits show bit 3 is flipped → correct to 1101011.

Real tie: Ncell’s error-correcting codes in 4G modems use Hamming-like schemes to fix bit flips during calls in noisy areas (e.g., mountain regions).


3.2 Automatic Repeat reQuest (ARQ): Retransmission

How it works:

  • Sender transmits a frame; receiver sends ACK (acknowledgment) if correct, NAK (negative acknowledgment) if not.
  • Variants:
    • Stop-and-Wait: Sender waits for ACK before next frame (simple but slow).
    • Go-Back-N: Sender transmits N frames; if any fail, resends from that frame.
    • Selective Repeat: Only resends corrupted frames.

Mermaid Diagram: Stop-and-Wait ARQ

sequenceDiagram
    Sender->>Receiver: Frame 1
    Receiver-->>Sender: ACK
    Sender->>Receiver: Frame 2
    Receiver-->>Sender: NAK (error)
    Sender->>Receiver: Frame 2 (retransmit)

Real-world example:

Daraz’s order processing uses Go-Back-N ARQ: If your order packet (Frame 5) is lost, Daraz resends Frames 5–10, not just Frame 5.


4. Flow Control: Preventing Overwhelm

Definition: Ensures the sender doesn’t flood the receiver with data faster than it can process. Mechanisms:

Method How It Works Example
Stop-and-Wait Sender waits for ACK before next packet Old modems (300bps)
Sliding Window Sender transmits N unacknowledged frames TCP (Internet), Daraz’s order queue
Credit-Based Receiver advertises free buffer space HTTP/2, WhatsApp media uploads

Worked Example: A receiver has a buffer of 5 frames. Using sliding window (window size = 3), trace the exchange:

  1. Sender sends Frames 1–3.
  2. Receiver ACKs 1–2 → sender slides window to 3–5.
  3. Frame 4 is lost → receiver ACKs only 3 → sender resends 4–5.

Real tie: Pathao’s driver app uses sliding window flow control to manage ride requests: If your request (Frame 1) is lost, Pathao resends it (retransmit) and doesn’t overwhelm the server with new requests until the buffer clears.


5. Comparing Error Control Methods

Method Detection Correction Overhead Use Case
Parity Single-bit ❌ No Low Simple systems (eSewa handshakes)
Checksum Multi-bit ❌ No Medium UDP, DNS queries
CRC High ❌ No High Ethernet, Wi-Fi, Khalti transactions
Hamming Single-bit ✅ Yes Very High Space communications, Ncell 4G
ARQ (Stop-and-Wait) Any ✅ Retransmit Low Old modems, eSewa retries
Sliding Window Any ✅ Retransmit Medium TCP, Daraz order processing

6. Real-World Applications in Nepal

System Impairment Mitigation Error Control Used
eSewa Uses CRC for transaction IDs Retries failed payments (ARQ)
Ncell 4G Shielded cables + Hamming codes Corrects bit flips in calls
NTC Fiber Optical amplifiers (attenuation) CRC for backbone routing
Khalti Checksums for payment data Rejects corrupted transactions
Daraz Sliding window flow control Prevents order queue overload

Exam Tip: How to Score Full Marks

  1. Definitions: Always define impairments (e.g., "Attenuation is the loss of signal strength over distance due to...").
  2. Diagrams: Draw CRC division or ARQ sequences in exams (use Mermaid-style text if hand-drawn is messy).
  3. Comparisons: For ARQ vs. FEC, use a table with speed vs. reliability trade-offs.
  4. Worked Examples:
    • For CRC: Show polynomial division steps (e.g., "100101000 ÷ 1011 → remainder 100").
    • For flow control: Trace sliding window steps with frame numbers.
  5. Real-World Links: Mention Ncell, eSewa, or NTC to show practical understanding (examiners love this!).
  6. Avoid: Vague answers like "errors happen." Always explain how and why.

Common Pitfalls:

  • Forgetting to append the CRC remainder to the data.
  • Confusing Go-Back-N (resend from failed frame) with Selective Repeat (resend only failed frame).
  • Ignoring units in attenuation questions (e.g., "dB/km" for fiber).

Final Visual Summary:

mindmap
  root((Transmission Impairments & Error Control))
    Attenuation
      Cause: Distance/Resistance
      Fix: Repeaters/Amplifiers
    Distortion
      Types: Amplitude/Phase/Delay
      Fix: Equalizers
    Noise
      Types: Thermal/Crosstalk/Impulse
      Fix: Shielding/Error Control
    Error Detection
      Parity: Simple but weak
      CRC: Strong (polynomial division)
    Error Correction
      Hamming: Math-based fixes
      ARQ: Retransmission (Stop-and-Wait/Sliding Window)
    Flow Control
      Stop-and-Wait: Slow but simple
      Sliding Window: Efficient (TCP/Daraz)

Based on the PU BE Computer (PU) syllabus for Data Communication, unit 6.

Discussion

Loading…