Toward 6G Sidelink Reliability: MAC PRR Modeling for NR Mode 2 SPS and ns-3 Validation

This paper presents an analytical MAC-layer model for 5G NR Sidelink Mode 2 that explicitly incorporates standardized Semi-Persistent Scheduling features to derive closed-form expressions for packet reception ratio, which are validated against ns-3 simulations to provide design insights for enhancing 6G sidelink reliability.

Liu Cao, Zhaoyu Liu, Lyutianyang Zhang

Published Tue, 10 Ma
📖 6 min read🧠 Deep dive

Imagine a busy highway where cars (User Equipment, or UEs) need to talk to each other directly to avoid accidents, without asking a traffic cop (a cell tower) for permission every time they speak. This is the world of 5G and 6G Sidelink communication.

In this paper, the authors are trying to solve a very specific problem: How do we make sure these cars don't crash into each other when they try to speak at the same time?

Here is a breakdown of the paper using simple analogies.

1. The Setting: The "Self-Driving" Highway

In the old days, cars had to wait for a traffic light (the base station) to tell them when to go. But in Mode 2, cars are like self-driving vehicles in a remote area with no traffic lights. They have to decide for themselves: "Okay, I'm going to send a message now. Which lane (frequency) and which second (time slot) should I use?"

They use a system called SPS (Semi-Persistent Scheduling). Think of it like this:

  • The Sensing: Before you pick a lane, you look around to see which lanes are already occupied by other cars.
  • The Reservation: You pick a free lane and say, "I'm going to use this lane for the next 10 seconds."
  • The Counter: You have a little countdown timer (the Reselection Counter). Every second, the timer goes down. When it hits zero, you have to look around again and pick a new lane.

2. The Problem: The "Double-Booking" Crash

The main issue the paper tackles is Collisions. A collision happens when two cars pick the exact same lane and time slot. When that happens, neither message gets through.

The authors realized that existing math models were too simple. They treated collisions like isolated accidents. But in reality, these collisions are more like traffic jams that last for a while.

They identified two main ways these "traffic jams" happen:

  • Collision Event 1: The "Simultaneous Re-Entry"
    Imagine two cars, Car A and Car B, both finish their 10-second reservation at the exact same moment. They both look at the map, see the same empty lane, and both decide to grab it. Crash! They are now stuck fighting for that lane for the next several seconds.
  • Collision Event 2: The "Stubborn Driver"
    Imagine Car A and Car B crashed in the last round. Car A's timer hits zero, and it decides to stick with the same lane it was using before (because the rules say it can keep the lane with some probability). Car B is still using that same lane because its timer hasn't hit zero yet. They are now stuck in a loop, crashing into each other repeatedly until one of them finally decides to switch lanes.

3. The Solution: A New "Traffic Law" Calculator

The authors built a new mathematical model (a calculator) to predict exactly how often these crashes happen.

  • The "Resource Keeping" Knob (pkp_k): There is a setting that decides how likely a car is to keep its current lane vs. switching to a new one.

    • Analogy: If you set the knob to "Always Switch," cars are constantly looking for new lanes. This causes a lot of chaos (Event 1) because everyone is looking at the same map at the same time.
    • If you set the knob to "Always Stay," cars rarely switch. This reduces the chaos of switching, but if two cars do crash, they get stuck in that crash for a very long time (Event 2).
    • The Finding: The authors found a "Goldilocks" zone. You need a mix of switching and staying to minimize crashes.
  • The "Duplicate Message" Trick (NSeN_{Se}):
    To make sure a message gets through, you can send the same message twice (like shouting the same thing twice in a noisy room).

    • Good News: In a lightly crowded highway, sending duplicates works great. If one copy crashes, the other might get through.
    • Bad News: In a super crowded highway (Saturation), sending duplicates actually makes things worse! It's like everyone shouting twice; the noise level becomes so high that nothing gets heard. The math shows that once the road is too full, sending duplicates hurts reliability.
  • The "Minimum Lane Requirement" (XX):
    The rules say: "You must only pick a lane if at least 20% of the lanes are empty."

    • The authors tested if raising this requirement (e.g., "Wait until 50% of lanes are empty") would help.
    • The Surprise: It didn't help! In fact, it just made cars wait longer without actually reducing crashes. It's like telling drivers to only drive when the highway is half-empty; you just end up with a lot of cars sitting in the parking lot, but the ones on the road are still crashing.

4. The Proof: The Video Game Simulation

To prove their math was right, the authors didn't just do equations on a whiteboard. They built a video game simulation (using a tool called ns-3) that mimics a real 5G network.

  • They created a virtual world with up to 200 cars.
  • They let the cars drive and talk for 100 seconds.
  • The Result: Their math predictions matched the video game results almost perfectly when the road wasn't too crowded. When the road got super crowded, the math started to drift a little (because real-world physics like signal interference start to matter more than just the "lane selection" rules).

The Big Takeaway

This paper gives engineers a manual for tuning 6G networks.

  1. Don't be too stubborn: If cars stay on the same lane too long, they get stuck in crashes.
  2. Don't be too jittery: If cars switch lanes too often, they bump into each other while looking for new spots.
  3. Don't over-send: Sending duplicate messages is a great safety net, but only when the network isn't already full.
  4. Keep the rules simple: Raising the minimum requirement for "empty lanes" doesn't actually make the network safer.

By understanding these "traffic laws," we can design 6G networks that are incredibly reliable, ensuring that critical messages (like "Brake!" or "Turn!") get through even in chaotic, infrastructure-less environments.