On the Polynomial Kernelizations of Finding a Shortest Path with Positive Disjunctive Constraints

This paper investigates the parameterized complexity of the NP-complete Shortest Path problem with positive disjunctive constraints, establishing fixed-parameter tractability and providing polynomial kernelizations of size O(k5)O(k^5) and O(k3)O(k^3) based on the solution size kk and specific structural properties of the forcing graph.

Susobhan Bandopadhyay, Suman Banerjee, Diptapriyo Majumdar, Fahad Panolan

Published 2026-03-06
📖 6 min read🧠 Deep dive

Imagine you are a delivery driver trying to find the shortest route from your warehouse (Point A) to a customer's house (Point B). This is a classic problem that computers are usually very good at solving.

But now, imagine your boss gives you a very strange set of rules before you even start driving. These rules are called "Positive Disjunctive Constraints."

Here is the twist: Your boss hands you a list of pairs of roads. For every single pair on the list, you are forced to say: "You must take at least one of these two roads in your final route." You can't ignore both. You have to pick one, or maybe both, but you can't leave the pair behind.

This paper is about figuring out: Can we still find the shortest path quickly, even with these annoying "must-pick" rules? And if the rules are too complicated, can we simplify the map so a computer can solve it faster?

The Cast of Characters

To understand the paper, let's meet the three main players using a simple analogy:

  1. The Primary Graph (GG): This is your actual city map. It has streets (edges) and intersections (vertices). Your goal is to drive from ss to tt using the fewest streets possible.
  2. The Forcing Graph (GfG_f): This is a "Rule Book" or a "Constraint Map."
    • In this map, the vertices are actually the streets from your city map.
    • The lines connecting them represent the rules. If Street A and Street B are connected in the Rule Book, it means: "You must pick Street A OR Street B (or both)."
  3. The Solution: A valid route is a path from ss to tt that is short, AND it touches enough streets to satisfy every rule in the Rule Book. In math-speak, the set of streets you pick must be a "Vertex Cover" of the Rule Book (meaning every rule is "covered" by at least one street you drove on).

The Problem: It's Complicated!

The authors explain that if you have these "must-pick" rules, the problem becomes incredibly hard (NP-hard). Even if the rules are very simple (like just pairs of streets), finding the shortest path is a nightmare for computers.

The paper asks: Can we make this easier by looking at specific features?

The Two Main Strategies

The researchers tried two different ways to tame this problem, using the concept of Kernelization. Think of Kernelization as a "Data Shrinker."

Imagine you have a massive, messy map of a country with millions of roads. You want to find a route, but the map is too big to process. A "Kernel" is a magic tool that throws away all the irrelevant roads and towns, leaving you with a tiny, simplified map that still contains the answer. If you solve the problem on the tiny map, you've solved it for the big map.

Strategy 1: Counting the Solution Size (kk)

The first natural question is: "How many roads do we need to pick?" Let's call this number kk.

  • The Result: The authors proved that no matter how messy the city map or the rule book is, if you are only allowed to pick a small number of roads (kk), you can shrink the entire problem down to a manageable size.
  • The Magic: They showed that the problem can be reduced to a "kernel" (a tiny map) with about k5k^5 points. While k5k^5 sounds big, it's a fixed size based on your limit, not the size of the whole world. This means the problem is Fixed-Parameter Tractable (FPT). In plain English: "If your solution is small, we can solve it efficiently, even if the world is huge."

Strategy 2: Looking at the Structure of the Rules

The second strategy looks at the shape of the Rule Book (GfG_f).

  • The Planar City: If your city map is "planar" (meaning you can draw it on a piece of paper without any roads crossing each other, like a subway map on a flat sheet), the problem gets even easier. The authors found a way to shrink the map even further, down to k3k^3.
  • The Simple Rules: What if the Rule Book itself is simple?
    • Cluster Graph: Imagine the rules are grouped into tight little cliques (like a group of friends where everyone knows everyone).
    • Bounded Degree: Imagine no single street is involved in too many rules.
    • The Result: In these cases, the "Rule Book" is so structured that the problem becomes much simpler, and again, they can shrink the map to k3k^3.

The "Deletion" Twist

The paper also looks at a scenario where the rules are almost simple, but have a few "bad" rules that make them complicated.

  • The Analogy: Imagine the Rule Book is mostly a simple list of pairs, but someone scribbled a few extra confusing rules on it.
  • The Fix: If you can remove just a few of those confusing rules (a "modulator") to make the rest of the book simple, the problem becomes solvable again. The authors proved that if the "bad" part is small, the whole problem is still manageable.

Why Does This Matter?

In the real world, we often face optimization problems with extra constraints.

  • Logistics: "If you use Truck A, you must also use Route B."
  • Network Security: "To secure this network, you must patch at least one of these two vulnerabilities."
  • Scheduling: "If you schedule Meeting 1, you must also schedule Meeting 2."

This paper gives computer scientists a toolkit. It says: "Don't panic if the rules are complex. If the solution you are looking for is small, or if the rules have a specific structure, we can simplify the problem down to a tiny size and solve it quickly."

Summary in a Nutshell

  1. The Problem: Find the shortest path, but you must pick at least one road from every pair of roads listed in a "Rule Book."
  2. The Difficulty: This is usually very hard for computers.
  3. The Breakthrough: The authors showed that if the number of roads you need to pick is small, or if the "Rule Book" has a simple structure, you can shrink the entire problem into a tiny, solvable version.
  4. The Takeaway: Even with complex "either/or" rules, we can often find efficient ways to solve routing problems by simplifying the data first.

It's like being told, "You must visit at least one store from every pair of stores in the city." If you only need to visit a few stores total, or if the store pairs are organized in a simple way, you can ignore the rest of the city and just focus on a small neighborhood to find your answer!