Mobility Management: Handoffs, Location Tracking & Roaming

TAKEAWAYS:

• Handoffs (horizontal/vertical) transfer a mobile device’s connection between base stations without dropping calls, using metrics like RSSI or SINR.
• Location management uses home/foreign agents and location updates to track mobile devices efficiently, balancing update cost vs. query delay.
• Roaming enables cross-network connectivity (e.g., Ncell ↔ NTC) via roaming agreements, AAA servers, and billing systems, but introduces latency and security risks.
• Mobility models (random walk, fluid flow) simulate user movement to test handoff algorithms—critical for designing smart city networks (e.g., Kathmandu traffic routing).
• IEEE 802.21 standardizes media-independent handoffs (MIH) for seamless Wi-Fi ↔ cellular transitions, used in Pathao’s delivery drones and eSewa’s mobile payments.
• Security challenges include man-in-the-middle attacks during handoffs and SIM cloning in roaming scenarios, mitigated by EAP-AKA and GBA.

1. Why Mobility Management? The Problem

Mobile devices (phones, IoT sensors, drones) move continuously. Unlike wired networks, wireless links are fragile:

• Signal degradation: Walls, distance, or interference (e.g., NTC 4G signal drops in hilly areas like Dhading).
• Base station (BS) coverage gaps: A call drops if the device moves out of range without a handoff.
• Network overload: Too many location updates slow down the system.

Real-world pain point: In Pathao’s delivery system, a rider’s phone must handoff smoothly between Wi-Fi (home) and 4G (road) to avoid order failures. A failed handoff = lost delivery = bad ratings.

2. Handoff (Hand-over) Mechanisms: How Devices Stay Connected

A handoff transfers an active connection from one BS to another. Two types:

A. Horizontal Handoff

• Definition: Transfer within the same network type (e.g., 4G → 4G or Wi-Fi → Wi-Fi).
• Example: Your phone switches from Ncell’s BS in Thapathali to one in Kageshwori as you walk.
• Key metrics for decision:

  Metric	Description	Example Threshold
  RSSI	Received Signal Strength Indicator (dBm). Lower = weaker signal.	Handoff if RSSI < -85 dBm
  SINR	Signal-to-Interference-plus-Noise Ratio. Higher = better quality.	Handoff if SINR < 5 dB
  RTT (Round Trip Time)	Delay in pinging the BS. Higher = farther or congested.	Handoff if RTT > 50 ms
  Velocity	Device speed (m/s). Faster = need proactive handoff.	Handoff if speed > 10 m/s

How it works (3-step process):

sequenceDiagram
    participant Device
    participant BS_A as Base Station A
    participant BS_B as Base Station B
    participant MSC as Mobile Switching Center

    Device->>BS_A: Monitors RSSI/SINR (drops below threshold)
    Device->>BS_A: Requests handoff to BS_B
    BS_A->>MSC: Authenticates & reserves resources for Device
    MSC->>BS_B: Allocates channel (e.g., 850 MHz)
    BS_B->>Device: Acknowledges handoff
    Device->>BS_B: Completes connection (call continues)

Worked Example: Ncell 4G Handoff in Kathmandu Traffic

• Scenario: You’re in a bus moving from Pulchowk to New Baneshwor (high velocity).
• Step 1: Your phone (RSSI = -90 dBm) detects BS in Pulchowk is weak.
• Step 2: It pings BS in New Baneshwor (RSSI = -75 dBm) and requests handoff.
• Step 3: Ncell’s MSC allocates a new channel (e.g., Band 3: 1800 MHz) and your call switches without dropping.
• Why it matters: If handoff fails, your WhatsApp call to a friend drops mid-conversation.

B. Vertical Handoff

• Definition: Switch between different network types (e.g., Wi-Fi → 4G or LTE → 5G).
• Example: eSewa app uses Wi-Fi at home but switches to NTC 4G when you step outside.
• Challenges:
  • Latency: Wi-Fi (low latency) → 4G (higher latency) can disrupt real-time payments.
  • Security: Unencrypted Wi-Fi hotspots risk SIM swapping attacks (common in Nepal).
  • Cost: Roaming between operators (e.g., Ncell → Smart) incurs extra charges.

Vertical Handoff Decision Algorithm (Simple Rule-Based):

flowchart TD
    A["Start"] --> B["Is RSSI < -80 dBm?"]
    B -->|"Yes"| C["Is network type Wi-Fi?"]
    C -->|"Yes"| D["Check if 4G RSSI > -70 dBm"]
    D -->|"Yes"| E["Initiate handoff to 4G"]
    D -->|"No"| F["Stay on Wi-Fi"]
    C -->|"No"| G["Check for better 4G/LTE signal"]
    G --> H["Handoff if SINR improves"]

Real-world use case:

• Pathao’s delivery drones use vertical handoffs between Wi-Fi (warehouse) and 5G (delivery route) to maintain GPS tracking.

3. Location Management: Tracking Mobile Devices

To route calls/sms, the network must know where a device is. Two key components:

A. Location Update (LU)

• Definition: The device informs the network of its current location area (LA) or routing area (RA).
• How it works:
  1. Device enters a new LA (group of BSs).
  2. It sends an LU message to its Home Location Register (HLR) via the Visitor Location Register (VLR).
  3. HLR updates the device’s location.
• Cost: Frequent LUs drain battery and overload the network.

Location Areas in Nepal’s Mobile Networks:

graph TD
    subgraph Kathmandu
        A["LA 1: Thapathali"] -->|"BS 1"| B["LA 2: Kageshwori"]
        A -->|"BS 2"| C["LA 3: New Baneshwor"]
        B -->|"BS 3"| D["LA 4: Pulchowk"]
    end

• Example: Your Ncell SIM’s HLR (stored in Ncell’s central database) knows you’re in LA 2 (Kageshwori) when you send a WhatsApp message.

B. Location Query (LQ)

• Definition: When you call a mobile number, the network queries the HLR to find the device’s current VLR.
• Problem: If LUs are rare, the HLR’s location data may be stale, causing delays.

Trade-off: LU frequency vs. LQ delay

Worked Example: Calling a Friend in Pokhara

1. You dial 98XXXXXX (Ncell number).
2. Your NTC network queries Ncell’s HLR: "Where is this device?"
3. HLR replies: "It’s registered in Pokhara’s VLR (LA 5)."
4. NTC routes the call via Pokhara’s MSC → BS in LA 5 → Friend’s phone.

4. Roaming: Crossing Network Boundaries

Definition: A mobile device uses a foreign network (e.g., Ncell in Pokhara while your SIM is from Kathmandu) via a roaming agreement.

How Roaming Works

sequenceDiagram
    participant User as User (Ncell SIM)
    participant ForeignBS as Foreign BS (NTC, Pokhara)
    participant HLR as Ncell HLR
    participant AAA as AAA Server (Authentication)
    participant Billing as Billing System

    User->>ForeignBS: Requests service (e.g., call)
    ForeignBS->>AAA: Authenticates via Ncell HLR (EAP-AKA)
    AAA-->>ForeignBS: Grants access
    ForeignBS->>User: Allows call
    ForeignBS->>Billing: Sends usage data (minutes, data)
    Billing->>Ncell: Bills user + roaming fee

Key Components:

• AAA (Authentication, Authorization, Accounting): Verifies the device via EAP-AKA (Extensible Authentication Protocol).
• Roaming Agreement: Ncell and NTC sign contracts to allow cross-network access (e.g., Ncell ↔ NTC roaming in Nepal).
• Billing System: Charges the user + roaming fee (e.g., Rs. 5/min for international roaming).

Real-world example:

• eSewa’s mobile payments work in remote villages via Nepal Telecom’s roaming network when Ncell signal is weak.

Challenges of Roaming

5. Mobility Models: Simulating User Movement

To test handoff algorithms, networks use mobility models that simulate how users move.

Worked Example: Kathmandu Traffic Mobility Model

• Scenario: Simulate 10,000 users moving from Thapathali to New Baneshwor during rush hour.
• Model: Fluid Flow with:
  • Speed: 10–30 km/h (average bus speed).
  • Density: 500 users/km² (peak hour).
• Output: Predicts handoff failures at signal intersections → Ncell adds more BSs there.

6. Standards and Protocols for Mobility

7. Security Challenges in Mobility

Real-world attack: In 2021, Ncell users in Pokhara reported fake BS attacks where scammers set up rogue towers to steal data. Solution: Ncell deployed EAP-AKA to verify BS authenticity.

In the Real World

1. Pathao’s Delivery System

   • Idea Used: Vertical handoffs (Wi-Fi ↔ 5G) and IEEE 802.21 MIH.
   • How: A delivery person’s phone switches from warehouse Wi-Fi to 5G on the road to maintain GPS tracking. If handoff fails, the order is marked as "lost."

2. eSewa Mobile Payments

   • Idea Used: Roaming + Location Management.
   • How: When you pay via Ncell in a remote village, eSewa’s server queries Ncell’s HLR to confirm your location (even if you’re roaming on Nepal Telecom). If the HLR data is stale, the payment fails.

3. NTC’s 5G Rollout in Kathmandu

   • Idea Used: Mobility models + handoff optimization.
   • How: NTC used fluid flow models to simulate traffic patterns and placed 5G BSs at high-mobility zones (e.g., Ring Road intersections). This reduced handoff failures by 40% compared to random placement.

Exam Tip

This unit is heavily tested in TU/PU exams with:

1. Diagram-based questions (50% weight):
   • Draw a handoff sequence diagram (like the one above).
   • Sketch a location area map with LAs and VLRs.
   • Compare horizontal vs. vertical handoff in a table.
2. Scenario-based problems (30% weight):
   • "A user moves from Thapathali to New Baneshwor. At what RSSI should handoff occur? Justify with Ncell’s thresholds."
   • "Explain how eSewa handles roaming when a user is in Pokhara but has a Kathmandu SIM."
3. Short-answer definitions (20% weight):
   • Define HLR, VLR, MIH, EAP-AKA, and roaming agreement.
   • Explain the trade-off between LU frequency and LQ delay.

Common mistakes to avoid:

• Confusing horizontal handoff (same network) with vertical handoff (different networks).
• Forgetting to mention AAA servers in roaming questions.
• Ignoring security risks (always mention MITM or SIM cloning in handoff discussions).

High-scoring tip: For 5-mark questions, use real examples (e.g., "Like in Pathao’s delivery system, vertical handoffs ensure..."). Examiners love Nepal-specific cases (Ncell, eSewa, Kathmandu traffic).