Exploring Bluetooth Communication Protocols in Internet-of-Things Software Development
Bibliographic record
Abstract
Internet of Things (IoT) development heavily depends on the connectivity of real-world objects. Bluetooth technology is widely applied to such connectivity in many IoT domains, such as smart home systems. Developing an integrated IoT system involves various stakeholders, e.g., mobile app developers and firmware developers. Discrepancies on the connectivity of the devices, i.e., how to communicate, may occur between different stakeholders in IoT development. Discrepancies occur when one group of developers misunderstand the communication protocols or incorrectly implemented them in the code. Such discrepancies may lead to unmet requirements and runtime connection errors. To help reduce such discrepancies, we perform a study to understand the current practices of designing Bluetooth communication protocols (BCPs) (i.e., by firmware developers) and how software developers manage the diverse BCPs in the code. Such understanding is a first step to provide tool support that can help developers better manage BCPs and detect (fault-indicating) discrepancies, aiding the maintenance effort of mobile applications.
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.008 | 0.041 |
| Meta-epidemiology (narrow) | 0.000 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.004 | 0.006 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| 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".