Safety-Critical Control with Guaranteed Lipschitz Continuity via Filtered Control Barrier Functions

This paper introduces Filtered Control Barrier Functions (FCBFs), a framework that integrates an input regularization filter with High-Order CBFs within a unified quadratic program to simultaneously guarantee system safety, control bounds, and Lipschitz continuity of control inputs, thereby preventing abrupt changes that could degrade performance or violate actuator limits.

Shuo Liu, Wei Xiao, Calin A. Belta

Published Wed, 11 Ma
📖 5 min read🧠 Deep dive

Imagine you are teaching a robot to drive a car through a busy city. You have two main rules for the robot:

  1. Don't crash: It must stay within the lanes and avoid hitting pedestrians or other cars.
  2. Don't jerk: The steering wheel and gas pedal shouldn't be slammed back and forth violently. If the robot jerks the wheel, the passengers get sick, the tires wear out, and the car might actually lose control.

For a long time, engineers had a great tool called a Control Barrier Function (CBF). Think of this as an invisible, magical force field that pushes the car away from danger. If the car gets too close to a wall, the force field instantly yanks the steering wheel to turn it away.

The Problem:
While this force field is great at keeping the car safe, it has a nasty side effect. Because it reacts so instantly to danger, it often tells the car to "Jerk left! Now jerk right! Now hard left!"
In math terms, the car's control inputs aren't "smooth." They are "abrupt." This is like a driver who panics and slams the brakes and steering wheel every time they see a pothole. It's safe in the sense that they don't hit the pothole, but it's terrible for the car and the passengers.

The paper you shared introduces a new, smarter way to drive called Filtered Control Barrier Functions (FCBFs).

The Analogy: The "Buffer Zone" Driver

Here is how the new method works, using a simple analogy:

1. The Old Way (Standard HOCBF):
Imagine a nervous driver who looks at the road and reacts instantly to every bump.

  • Scenario: A child steps out.
  • Reaction: The driver screams and slams the brakes and turns the wheel 90 degrees in 0.01 seconds.
  • Result: The car stops safely, but the passengers are thrown forward, and the suspension breaks. The math says the car is "safe," but the motion is chaotic.

2. The New Way (FCBF):
The authors introduce a Filter. Think of this as a "Buffer Zone" or a "Calm Co-Pilot" sitting between the nervous driver and the car's controls.

  • The Nervous Driver (The Original Algorithm): Still sees the danger and yells, "Turn left! Turn left NOW!"
  • The Calm Co-Pilot (The Filter): Instead of passing that panic directly to the car, the Co-Pilot says, "Okay, we need to turn left, but let's do it smoothly."
  • The Result: The Co-Pilot translates the "Jerk Left!" command into a "Gently turn the wheel over the next 2 seconds."

Why is this special?

In the world of math and engineering, there is a concept called Lipschitz Continuity. In plain English, this just means "No Sudden Jumps."

  • Smoothness usually just means the line doesn't break.
  • Lipschitz Continuity means the line doesn't just not break; it also guarantees that the speed at which the line changes is limited. It puts a "speed limit" on how fast the steering wheel can turn.

The paper proves that their new "Co-Pilot" (the Filter) guarantees this speed limit. No matter how crazy the situation gets, the robot's controls will never change faster than a specific, safe rate.

The "Magic" Trick

The clever part of this paper is how they built this Co-Pilot.
Instead of trying to rewrite the whole math of the robot (which is hard), they added a small, extra "virtual machine" (the filter) that sits in front of the robot.

  • The robot talks to the virtual machine.
  • The virtual machine talks to the car.
  • The virtual machine is programmed to only speak in smooth, gentle sentences.

Because of this setup, the whole system (Robot + Virtual Machine) can still be solved using a standard, fast computer program (called a Quadratic Program). This means the robot can still think fast enough to drive in real-time, but now it drives like a professional chauffeur instead of a panicked teenager.

The Results (The Race Car Test)

The authors tested this on a "Unicycle" robot (a robot that balances on one wheel, like a Segway).

  • The Test: Drive around a circular obstacle without hitting it.
  • The Competitors:
    1. Standard Method: Safe, but the robot jerks and shakes.
    2. Smoothness Penalty Method: They tried to force the robot to be smooth by adding a "punishment" in the math if it jerked. This often made the robot get stuck or fail to find a path at all.
    3. FCBF (The New Method): The robot drove smoothly, safely, and never got stuck. It moved like a fluid stream of water rather than a bouncing ball.

Summary

This paper solves a problem where safety algorithms were making robots move too jerkily. They added a "smoothness filter" that acts like a calm co-pilot, ensuring that the robot's controls change gradually and predictably. This keeps the robot safe from crashes and keeps the ride smooth, all without slowing down the computer's ability to make decisions.