Frontend
Physical Layer Security for Digital Semantic Communication: A Bit-Level Perspective
arXiv eess.SY0 views
arXiv:2611.23940v1 Announce Type: cross Abstract: Digital semantic communication requires reliable recovery of task-relevant information at a legitimate receiver while limiting source reconstruction by an eavesdropper. Uniform bit protection, however, does not account for the heterogeneous reliability and secrecy requirements of semantic bits. This paper proposes a bit-level physical layer security (PLS) framework that learns these requirements and incorporates them into physical-layer resource allocation. We first introduce a wiretap semantic feature channel whose two-stage training learns per-bit target bit-flip probabilities for the legitimate receiver (Bob) and the eavesdropper (Eve). These targets characterize the reliability requirements at Bob and the secrecy protection requirements against Eve. Based on the learned targets, we formulate a joint power and artificial-noise (AN) allocation problem for a multiple-input single-output wiretap channel under a worst-case angular-separation model. For a given target profile, the optimal information-AN power split admits a closed-form solution, and the per-bit power allocation is obtained by water-filling. We further develop a leakage-aware selection method among multiple learned-target profiles and extend the design to multiple-input multiple-output channels. Simulation results demonstrate that the proposed framework achieves a better trade-off between preserving reconstruction quality at Bob and degrading that at Eve than uniform power allocation and the evaluated learning-based secure semantic communication schemes.
Source:https://arxiv.org/abs/2611.23940PreviousAverting `Gravity': Launch Control and the Limits of Collision Avoidance in Low Earth Orbit OperationsNextOMNIS+: Semantic RAN Slicing and Quantization for Dynamic Split Neural Networks
Related posts
Why useReducer? Why do we need multiple functions to update a single state?
0dev.to React
Fix: “Next.js encountered the unstable value new Date()” in Next.js 16
0dev.to React
Cricket Form Trackers Fail When They Hide the Sample Size
0dev.to Python

Goodbye Notion: Why We Migrated Our Tech Content Ops to Git and Pydantic
0dev.to Python
The nginx HTTP/2 CVEs are out, OpenResty isn't patched yet: how we shipped the fix in a day (and the `| tee` bug that hid our updates)
0dev.to DevOps
Show HN: Zpup – Zdog style 3D scenes in JSON, SVG from any angle
0Hacker News Show