Feasibility Value Function (FVF)
- Feasibility Value Function (FVF) is a metric that quantifies finite-horizon feasibility by measuring the minimal slack violation required to satisfy hierarchical MPC constraints.
- FVF leverages slack variables to relax constraints in lower-level MPC, yielding a precise zero-level set that delineates the admissible region.
- FVF enables modular, contract-based design in hierarchical control, facilitating model confidentiality while ensuring safe, provable system performance.
The Feasibility Value Function (FVF), denoted , is a predictive metric introduced to rigorously quantify finite-horizon feasibility in hierarchical model predictive control (MPC) architectures. Its construction leverages slack variables to relax state and reference-dependent constraints, providing an analytically tractable and contractible interface between hierarchical control layers. The zero-level set of precisely delineates the admissible region for the lower-level MPC, enabling provably safe modular design and execution, notably when model and cost structures are sequestered across control layers (Berkel et al., 16 Apr 2025).
1. Formal Definition and Mathematical Structure
Let represent the current lower-layer state, and a high-level reference trajectory, constant over fast-time blocks of size . Slack vectors relax state and reference-dependent constraints. The predictive feasibility value function is defined as
subject to the finite-horizon system dynamics and relaxed constraints: where . By definition, if and only if the corresponding hard-constrained MPC is feasible; otherwise, quantifies the minimal slack violation required (Berkel et al., 16 Apr 2025).
2. Theoretical Properties and Relationship to Viability Kernels
The FVF admits a direct interpretation in viability kernel theory. The set forms the finite-horizon viability set in state-reference space. For state/reference pairs outside , the value quantifies, in an -slack sense, the minimal aggregate violation necessary for admissibility under system constraints. This function acts as a cost-to-go: it is zero inside the viability kernel, strictly positive outside, and monotonically non-increasing under optimal (soft-constrained) control trajectories. The objective uniquely serves as the tightest violation margin to accommodate model and reference inconsistencies over the given horizon (Berkel et al., 16 Apr 2025).
3. Contract-Based Hierarchical Control Architecture
In the contract-based hierarchical control setting, a high-level planner (operating at slow timescale ) issues reference trajectories to a low-level, fast-sampled MPC. The low-level MPC minimizes
subject to the same relaxed system and reference constraints.
A contract function is exchanged offline: it is an explicit (often neural network-based) approximation of . Online, the high-level planner incorporates this contract in its optimization: with the option to enforce for strict lower-level feasibility. This enables the upper layer to proactively avoid references that violate the constrained capabilities of lower controllers, despite not possessing detailed model or constraint information from that layer (Berkel et al., 16 Apr 2025).
4. Explicit Function Approximation and Implementation
The FVF can be efficiently approximated via either look-up tables (LUT) or neural networks (NN), to facilitate online evaluation within the planner. For NNs, input features comprise a concatenated vector , with 2–4 hidden layers of 50–200 ReLU or tanh neurons, and a scalar output . Training proceeds by sampling states and reference sequences , then solving the slack value problem offline to generate targets . The standard loss is
where is a regularization parameter. By the universal-approximation theorem and the Lipschitz continuity of , a sufficiently wide/deep NN can achieve for arbitrary small . In practice, a positive safety margin may be set, and feasibility is conservatively enforced via (Berkel et al., 16 Apr 2025).
5. Case Study: Autonomous Driving Application
In the autonomous driving example, the lower-level controller employs a single-track dynamic vehicle model discretized at ms, with states and controls . Hard box constraints on velocity, steering, and acceleration are augmented by soft “tube” constraints: surrounding the planner’s path. The high-level planner operates on a simplified "constant-velocity + heading" model at a slower timescale and incorporates both quadratic target-tracking and nonconvex obstacle-avoidance costs.
Offline, for sampled , the FVF is solved and stored as a LUT or approximator . Online, the planner evaluates candidate reference pairs (), discards those with , and propagates only admissible trajectories. The paper illustrates two sample runs: one with leading to a collision (constraint violation), and one with where the controller enforces the corridor and avoids obstacles (Berkel et al., 16 Apr 2025).
6. Significance for Modular and Confidential Control Design
The introduction of FVF enables modular, decoupled design in hierarchical control systems. By using an explicit, contract-based interface, the high-level planner need not have explicit access to the lower-level model, cost, or constraint definitions. This modularity supports model confidentiality and IP protection—a substantive concern in industrial and safety-critical domains—while maintaining system-wide feasibility guarantees. The FVF’s role as a cost-to-go proxy for constraint satisfaction also links it to viability theory and enables further generalizations for scenarios with time-varying, nonlinear, or nonconvex constraints (Berkel et al., 16 Apr 2025).
Summary Table: Core Properties of the Feasibility Value Function
| Property | Mathematical Description | Control-Theoretic Significance |
|---|---|---|
| Zero-level set | Finite-horizon viability kernel | |
| Value outside kernel | Minimal total constraint violation needed | |
| Contractability | Explicit LUT or NN approximation possible | Modularization; enables offline exchange |
| Monotonicity | Non-increasing under optimal relaxed policy | Cost-to-go behavior, feasibility margin |