Joint Computation Offloading and Multidimensional Resource Allocation in Air–Ground Integrated Vehicular Edge Computing Network
Bibliographic record
Abstract
The integration of vehicle edge computing (VEC) and air-ground integrated network is considered as a key technology to achieve autonomous driving. It exploits the ubiquitous service coverage and enables tasks to be offloaded to various components, such as high-altitude platform (HAP), unmanned aerial vehicle (UAV), and roadside unit (RSU). In this article, we address the challenge of minimizing the overall task offloading delay in the air-ground integrated VEC network through a joint multicomputation equipment selection and multidimensional resource allocation (JCESRA) problem. Considering the nonconvexity inherent in the problem, we employ the fundamental idea of the block coordinate descent (BCD) method to tackle it. Initially, we exclude the HAP and decompose the primal problem into three subproblems: 1) low-altitude computation equipment selection; 2) joint bandwidth and computation resource allocation; and 3) UAV trajectory design. The first subproblem, which involves integer programming, is solved by using the many-to-one matching method. Meanwhile, we utilize the CVX and successive convex approximation (SCA) method to solve the last two subproblems, respectively. Considering the matching externality, we utilize the coalition game method to deal with it. Based on the solutions of the three subproblems, the JCESRA algorithm without considering the HAP has been proposed. Subsequently, we consider the HAP into the problem. Because the task offloading decision and computation resource allocation of the HAP problem can be viewed as a knapsack problem, we utilize the dynamic programming method to solve it. Because some tasks are offloaded to the HAP, there are some redundant computation resources in UAVs and RSU. We reallocate the computation resources of UAVs and RSU to further reduce the task offloading delay. At last, we present the complete JCESRA algorithm. The simulation results unequivocally indicate that the proposed JCESRA algorithm outperforms other algorithms by significantly reducing the task offloading delay.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".