Wireless Internetworking: Protocols, Standards & Integration

TAKEAWAYS:

• Wireless internetworking bridges Wi-Fi (802.11), cellular (4G/5G), and wired networks using interworking protocols (e.g., IEEE 802.21) for seamless handoffs.
• Roaming in Wi-Fi/cellular networks relies on Mobile IP and Fast Handover to maintain sessions (e.g., Pathao’s real-time GPS updates during rides).
• Security protocols (WPA3, EAP-TLS) protect data in transit, critical for eSewa’s encrypted transactions and Ncell’s IoT deployments.
• Standardization bodies (IEEE, 3GPP) define interoperability rules—e.g., 802.11k/v for Wi-Fi hotspot roaming and LTE-U for unlicensed spectrum sharing.
• Integration challenges include latency (e.g., Daraz’s order queues during Diwali sales) and spectrum conflicts (NTC’s 5G rollout vs. Wi-Fi 6E).
• Exam focus: Compare protocols (e.g., Mobile IP vs. Proxy Mobile IP), trace handover sequences, and analyze real-world failures (e.g., Kathmandu traffic congestion due to poor Wi-Fi/cellular handoffs).

1. Wireless Internetworking: Definitions and Scope

Wireless internetworking refers to the interconnection of wireless networks (Wi-Fi, cellular, Bluetooth, Zigbee) with wired networks (Ethernet, fiber) to enable seamless communication. Unlike standalone wireless networks (e.g., a home Wi-Fi router), internetworking requires:

• Protocol translation (e.g., converting Wi-Fi frames to IP packets).
• Mobility support (e.g., switching from Wi-Fi to 4G without dropping calls).
• Security and QoS (e.g., prioritizing video calls over email in Pathao’s app).

Why it matters:

• eSewa’s payment gateway uses HTTPS (TLS 1.3) over Wi-Fi/cellular to encrypt transactions between merchant terminals and the bank’s server.
• Pathao’s ride-hailing relies on LTE-V2X for real-time vehicle-to-infrastructure (V2I) communication to optimize routes and avoid traffic jams.
• NTC’s 5G rollout integrates non-standalone (NSA) 5G with existing 4G/LTE networks via EPC (Evolved Packet Core) for backward compatibility.

2. Key Standards and Protocols

Wireless internetworking is governed by IEEE, 3GPP, and IETF standards. The critical ones are:

sequenceDiagram
    participant Laptop as User Laptop
    participant AP as Wi-Fi AP (Ncell)
    participant Router as ISP Router
    participant Daraz as Daraz Server

    Laptop->>AP: Probe Request (802.11)
    AP-->>Laptop: Beacon (SSID: NcellWiFi)
    Laptop->>AP: Association Request (WPA3-PSK)
    AP->>Router: IP Packet (HTTP GET /product)
    Router-->>Daraz: Forwarded Request
    Daraz-->>Router: HTTP Response
    Router->>AP: IP Packet (Response)
    AP-->>Laptop: 802.11 Data Frame

A. IEEE 802.11 Standards for Wi-Fi Internetworking

The 802.11 family defines how Wi-Fi devices connect to wired networks (e.g., via a router or access point). Key standards:

Visual: Wi-Fi Frame Format Wi-Fi frames (802.11) carry data between devices and access points. The MAC header includes:

• Address 1 (DA): Destination MAC (e.g., router’s MAC).
• Address 2 (SA): Source MAC (e.g., your laptop).
• Address 3 (BSSID): AP’s MAC.
• Frame Control: Type (data, management, control), subtype (e.g., beacon, ACK).

Real-world trace: When you load Daraz’s website on Wi-Fi:

1. Your laptop sends a probe request (802.11 management frame).
2. The AP replies with a beacon (including SSID, supported rates).
3. Your laptop associates with the AP (authentication via WPA3-PSK).
4. The AP forwards your HTTP request (IP packet encapsulated in 802.11 frame) to the router.
5. The router routes it to Daraz’s server via Ethernet/fiber.

B. Mobile IP and Handover Protocols

Problem: How does a device (e.g., your phone) maintain an IP session when moving between networks (e.g., Wi-Fi → 4G)?

Solutions:

1. Mobile IP (RFC 5944):

   • Uses a home agent (HA) and foreign agent (FA) to tunnel packets.
   • Example: You’re on Ncell’s 4G but walk into a hotel Wi-Fi. Your phone’s IP address changes, but Mobile IP ensures your WhatsApp calls stay connected.
   • Drawback: High latency (~200ms handover delay).

2. Proxy Mobile IP (PMIP, RFC 5844):

   • The mobile node (MN) doesn’t need to signal; the local mobility anchor (LMA) handles it.
   • Example: Pathao drivers switch from NTC’s 5G to Wi-Fi at a pickup point without dropping the app.

3. IEEE 802.21 (Media Independent Handover, MIH):

   • Enables fast handover between Wi-Fi, WiMAX, and cellular.
   • Example: eSewa’s POS machines use MIH to switch from Wi-Fi to cellular backup during power outages.

Mermaid: Mobile IP Handover Sequence

sequenceDiagram
    participant MN as Mobile Node (Phone)
    participant FA as Foreign Agent (Wi-Fi AP)
    participant HA as Home Agent (ISP)
    participant CN as Correspondent Node (Daraz Server)

    MN->>FA: Agent Solicitation (Request IP)
    FA->>MN: Agent Advertisement (Offer IP)
    MN->>HA: Registration Request (New CoA)
    HA->>FA: Registration Reply (Update Binding)
    CN->>HA: Data Packet (Encapsulated)
    HA->>FA: Tunnel Packet to MN
    FA->>MN: Deliver Data

Worked Example: Pathao’s Handover

• Scenario: A Pathao driver is on Ncell’s 4G (IP: 192.168.1.100) but enters a hotel Wi-Fi zone (IP: 10.0.0.50).
• Steps:
  1. Driver’s phone detects weaker 4G signal and stronger Wi-Fi (via 802.11k/v).
  2. PMIP triggers a handover:
     • LMA (Ncell’s core) updates the binding cache.
     • Packets are tunneled from 4G to Wi-Fi.
  3. Latency: <50ms (vs. 200ms for Mobile IP).
• Outcome: The Pathao app shows real-time GPS updates without dropping the ride request.

C. Security Protocols in Wireless Internetworking

Security is critical when integrating wireless and wired networks. Key protocols:

Real-world failure:

• Kathmandu traffic jams during Dashain often cause Wi-Fi/cellular handover failures because:
  • Overloaded APs (too many devices in Thamel).
  • Poor PMIP implementation in NTC’s 4G network.
  • Solution: Deploy 802.11ax APs with better roaming algorithms.

3. Wireless Internetworking Architectures

Three main architectures enable wireless-wired integration:

A. Centralized Architecture

• Single controller (e.g., Wi-Fi controller like Cisco WLC) manages all APs.
• Pros: Easy to configure, centralized security (WPA3).
• Cons: Single point of failure (e.g., if TU’s Wi-Fi controller crashes, all APs go down).
• Example: PU’s campus Wi-Fi uses a centralized controller for all buildings.

B. Distributed Architecture

• Each AP is independent (no central controller).
• Pros: Scalable, no single point of failure.
• Cons: Harder to manage security (e.g., rogue APs in Daraz’s warehouse).
• Example: Home Wi-Fi routers (no controller).

C. Cloud-Based Architecture

• Controller runs in the cloud (e.g., Aruba Central, Ubiquiti UniFi).
• Pros: Remote management, AI-driven optimization (e.g., Pathao’s dynamic AP selection).
• Cons: Requires internet access (not ideal for rural areas).
• Example: Ncell’s 5G small cells use cloud controllers for real-time traffic routing.

Mermaid: Wireless Internetworking Layers

4. Challenges and Solutions

5. Real-World Applications

A. eSewa’s Payment Gateway

• Problem: Merchants need secure, low-latency transactions over Wi-Fi/cellular.
• Solution:
  • Wi-Fi 6 APs in shops for fast checkout.
  • Mobile IP for seamless handover if the merchant moves between networks.
  • TLS 1.3 for encryption (prevents skimming).
• Failure case: If WPA2 is used instead of WPA3, attackers can exploit KRACK vulnerabilities to steal payment data.

B. Pathao’s Ride-Hailing Routing

• Problem: Drivers and riders must stay connected during handoffs (e.g., Wi-Fi → 4G).
• Solution:
  • LTE-V2X for vehicle-to-network (V2N) communication.
  • PMIP for fast IP address changes.
  • 802.11k/v for AP selection (avoids weak signals).
• Worked Example:
  • Driver’s phone: 4G (IP: 203.123.45.67) → enters hotel Wi-Fi (IP: 10.0.0.1).
  • Handover time: 30ms (vs. 200ms for Mobile IP).
  • Result: No dropped rides, real-time GPS updates.

C. NTC’s 5G Integration with Wi-Fi

• Problem: 5G needs to coexist with Wi-Fi 6 without interference.
• Solution:
  • LTE-U (Licensed-Assisted Access) for unlicensed spectrum sharing.
  • MU-MIMO in both 5G and Wi-Fi 6 for better throughput.
• Example: NTC’s 5G trial in Kathmandu uses Wi-Fi 6E (6 GHz) to offload data from 5G.

6. Exam Tip: How This Unit is Tested

1. Protocol Comparisons (20% weight):

   • Compare Mobile IP vs. Proxy Mobile IP (signaling, latency, use cases).
   • Compare WPA2 vs. WPA3 (encryption, handshake, vulnerabilities).

2. Handover Traces (30% weight):

   • Draw a sequence diagram for 802.21 handover between Wi-Fi and 4G.
   • Calculate handover latency given Mobile IP’s 200ms delay vs. PMIP’s 50ms.

3. Real-World Scenarios (25% weight):

   • Explain how eSewa’s payment system uses TLS over Wi-Fi 6.
   • Analyze why Kathmandu traffic causes Wi-Fi handover failures (overloaded APs, poor PMIP).

4. Troubleshooting (15% weight):

   • Given a slow Daraz website on Wi-Fi, diagnose:
     • Root cause: AP congestion (2.4 GHz interference).
     • Fix: Upgrade to Wi-Fi 6E (6 GHz).

5. Diagrams (10% weight):

   • Must-draw:
     • Wi-Fi frame format (show DA, SA, BSSID).
     • Mobile IP handover sequence.
     • Layered architecture (OSI vs. wireless-specific layers).

Final Note:

• Memorize: IEEE 802.11 standards, Mobile IP/PMIP differences, WPA3 features.
• Practice: Trace a WhatsApp call from Wi-Fi to 4G using Mobile IP.
• Relate: Always tie answers to eSewa, Pathao, or NTC for full marks.

In the real world

• Pathao’s ride-hailing app uses PMIP (Proxy Mobile IP) for seamless handover between Ncell’s 5G and hotel Wi-Fi, ensuring real-time GPS updates without dropping the ride request (latency <50ms).
• eSewa’s merchant terminals rely on WPA3 + 802.1X for secure Wi-Fi authentication, encrypting transactions between POS machines and the bank’s server via IPSec tunnels during power outages.
• NTC’s 5G rollout integrates non-standalone (NSA) 5G with existing 4G/LTE networks via EPC, allowing backward compatibility while offloading data traffic to 5G for high-density areas (e.g., Thamel during Dashain).