Skip to content
#software testing Open access

CALM: Confidence-Aware Beam Training With Reliability-Weighted Decoding and Adaptive Pilot Allocation for RIS-Assisted Initial Access

Nov 2026 · IEEE Internet of Things Journal · Vol 13, pp. 53136-53152 · 1 citation · 41 references

TL;DR

The results support confidence-aware coded beam training as a physical-layer access mechanism whose pilot savings can be mapped to concrete benefits for Internet of Things/cyber–physical systems (IoT/CPS)—including reduced per-device access latency and increased device density under fixed frame budgets—while broader wideband, hardware, and system-level validation remain future work.

Abstract

Reconfigurable intelligent surfaces (RISs) can improve coverage and energy efficiency, but their practical value depends on reliable initial access before alignment is established. In that phase, the training signal-to-noise ratio (SNR) at the user can be low, making hierarchical and hard-decision coded beam-training vulnerable to error propagation. This article develops confidence-aware layered matching (CALM), a receiver-centric beam-training framework that extracts soft reliability information from the four beam-tuple measurements collected at each training layer. CALM-JD (joint decoding) performs reliability-weighted decoding of the base station (BS) and RIS hypotheses from the shared layer measurements instead of committing to brittle layer-wise hard decisions. CALM-APA (adaptive pilot allocation) further reallocates extra pilots only to the least reliable layers, while CALM-APA+KCONF (top- $K$ confirmation) adds a bounded top- $K$ tuple-confirmation stage to improve robustness without losing runtime predictability. The resulting methods preserve the low-overhead layered structure of coded beam training while addressing low-SNR reliability and bounded online latency. Complexity analysis and relative software runtime profiling are reported alongside achievable-rate and misalignment results. For a 28-GHz BS–RIS–user link with a 64-antenna BS and a $16\times 16$ RIS, the dominant-path baseline shows that the proposed CALM variants significantly reduce misalignment probability in the low-SNR regime and, in the simplified narrowband dominant-path setting studied here, approach the exhaustive-search rate ceiling with roughly two orders-of-magnitude fewer pilots than exhaustive search. Additional narrowband robustness tests with richer sparse multipath (up to eight physical paths per hop), RIS phase quantization, and angular off-grid mismatch preserve the same qualitative ordering, with CALM-APA+KCONF retaining the strongest rate under the tested nonidealities. These results support confidence-aware coded beam training as a physical-layer access mechanism whose pilot savings can be mapped to concrete benefits for Internet of Things/cyber–physical systems (IoT/CPS)—including reduced per-device access latency and increased device density under fixed frame budgets—while broader wideband, hardware, and system-level validation remain future work.

Read PDF

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

Microsoft Research Blog Nov 12, 2026

Microsoft Research Focus – Edition #98

What's new in research at Microsoft? Host Anson Ho explores the latest, including AI-powered universal translation, a breakthrough in a 31-year-old mathematics challenge, and advances making AI coding agents faster and more efficient.  The post Microsoft Research Focus – Edition #98 appeared first on Microsoft Research.

Microsoft Research Blog Nov 5, 2026

Formally verifying agent-written full-stack web apps with PDD Kit

AI agents can generate code at a scale that’s hard for humans to review line-by-line. PDD Kit helps ensure the code is doing what the developer intended by creating formal specifications and testing against them. It converts developer intent into a Verus specification, proves AI-generated code meets it for every input, and uses tests where proofs aren't practical. Developers review intent, not every line. The post Formally verifying agent-written full-stack web apps with PDD Kit appeared first o…

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.