REVIEW 2 major objections 2 minor 1 cited by
SDAP-based QoS Flow Multiplexing Support in Simu5G for 5G NR Simulation
T0 review · 2 major / 2 minor · reviewed 2026-08-05 · deepseek-v4-flash
Pith's one-line read The paper gives Simu5G a modular, standards-based SDAP layer so 5G simulations can carry multiple QoS flows over shared radio bearers.
desk verdict Useful Simu5G tooling paper; novelty and validation rest on claims that the abstract alone can't back up. read the letter →
The pith
A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.
The reading
What carries the argument
The central object is the SDAP layer, the 5G protocol entity responsible for per-flow QoS marking above PDCP. The extension's working parts are QFI flow tagging, SDAP header insertion and removal, and configurable flow-to-DRB mapping. This layer carries the argument: by exposing these operations in the simulator, the design turns QoS flow multiplexing from a fixed assumption into a configurable, observable behavior.
What would settle it
Configure a scenario with two QoS flows mapped to one DRB, send packets through the SDAP module, and inspect the transmitted SDAP headers; if the QFI values do not match the configured mapping or the standard's encoding, the claim of correct SDAP behavior fails.
Extended reading notes
Core claim
The central claim is that an SDAP implementation can be added to Simu5G as a modular, standards-compliant layer between the core and radio stacks. The layer performs three load-bearing tasks: it tags each incoming packet with a QoS Flow Identifier, it inserts and removes the SDAP header, and it maps QoS flows to logical Data Radio Bearers according to configuration. Together these operations reproduce the 5G mechanism by which multiple QoS flows are multiplexed onto the same DRB. The validation results are offered as evidence that the implemented behavior is correct, enabling multi-QFI simulation scenarios that were previously missing.
Load-bearing premise
The claim of correct SDAP behavior rests on validation that compares the module's output to the standard's expected behavior, not merely to the authors' design choices.
Editorial extensions
If this is right
- Simu5G becomes usable for multi-QFI scenarios in which several QoS flows share one Data Radio Bearer.
- Researchers can implement and test flow-aware scheduling policies that use QFI information.
- The simulator can model latency-sensitive industrial traffic and per-flow isolation.
- The extension is modular and configurable, so QoS flow-to-DRB mappings can be adapted per simulation scenario.
Reading between the lines
- The abstract does not specify how validation was measured; a natural next step is to test the module against bit-level SDAP header encodings from the 5G standard to confirm conformance independently of the implementation's own tables.
- The same modular layer could be extended to implement reflective QoS or end-to-end flow delay accounting inside the simulator.
- A candidate extension is to add queueing statistics per QFI so flow-aware scheduling algorithms can be evaluated quantitatively.
Signed reviews
Editorial analysis
A structured set of objections, weighed in public.
Referee Report
Summary. The paper (available to this review only in abstract form) reports the design and implementation of an SDAP extension for the Simu5G 5G NR simulation framework. The claimed contribution is a modular, standards-compliant SDAP implementation supporting QFI flow tagging, SDAP header insertion/removal, and configurable mapping of QoS flows to DRBs. The abstract asserts that validation results confirm correct SDAP behavior and that the extension enables realistic multi-QFI simulations, differentiated QoS flows, flow-aware scheduling, per-flow isolation, and latency-sensitive industrial traffic.
Significance. If the implementation is genuinely standards-compliant and validated against an independent oracle, this would be a useful contribution to the 5G simulation community: Simu5G currently lacks SDAP support, and the ability to model QoS flow multiplexing over DRBs would enable studies of per-flow QoS, scheduling, and industrial traffic that are not otherwise possible in that framework. The claimed modularity and configurability of the QFI-to-DRB mapping are also valuable. However, because only the abstract is available, none of these claims can be verified. The significance is therefore conditional on the validation and implementation details that are not presented here.
major comments (2)
- [Abstract] The load-bearing assertion is "Validation results confirm correct SDAP behavior," but the abstract provides no validation methodology, no definition of the correctness oracle, no test coverage description, and no repository or artifact link. If "correct" behavior is checked against expectations derived from the same mapping tables and header-format code under test, the tests would pass even if the implementation deviates from 3GPP TS 37.324. The authors should specify that expected behavior was taken from an external standard or from an independent reference implementation, and should present concrete test cases covering QFI tagging, SDAP header insertion/removal, DRB mapping, and edge cases such as reflective QoS and end-marker handling. Without this, the standards-compliance claim is unsupported.
- [Abstract] The claim that the extension is "modular, standards-compliant" is not backed by any architectural detail in the abstract. The reader cannot tell how the SDAP layer interfaces with Simu5G's existing PDCP/RLC/MAC stack, how the 8-bit QFI is encoded in the SDAP header, how mapping configurability is exposed, or whether the implementation handles both UL and DL directions and reflective QoS. These details are essential because SDAP conformance is precisely a matter of header bytes and mapping decisions. The full paper must include an architecture description, a mapping to 3GPP specification clauses, and a discussion of any simplifications or deviations from the standard.
minor comments (2)
- [Abstract] Typo: "QoS Flow Identifer" should be "QoS Flow Identifier." Also, the framework is named "OMNeT++", not "OMNet++".
- [General] The abstract does not mention a public code repository or release version. For a simulation framework extension, an artifact link is helpful for reproducibility and for the community to adopt the code.
Circularity Check
No circularity identifiable from abstract; validation oracle is uninspectable but no reduction-by-construction is shown.
full rationale
This review is based only on the abstract, which describes an SDAP extension for Simu5G and reports that 'Validation results confirm correct SDAP behavior.' There is no derivation chain, equation, fitted parameter, or load-bearing self-citation in the abstract that would allow a specific circular step to be quoted and exhibited. The residual concern that the validation oracle might be self-referential (e.g., test expectations generated from the same QFI-to-DRB mapping tables the module implements) is a plausible evidential worry, but it is not demonstrated by any paper text. Under the hard rules, circularity cannot be claimed without quoting a specific reduction, so the appropriate finding is no significant circularity. The correctness and external validity of the validation remain unverifiable from the abstract alone, but that is an evidence-limitation issue, not a demonstrated circularity.
Assumptions & free parameters
assumptions (3)
- domain assumption The 3GPP SDAP specification (TS 37.324 or TS 38.324) is the normative reference for standards-compliant behavior
- domain assumption Simu5G's existing PDCP/RLC/MAC entities expose sufficient hooks to insert an SDAP layer and carry QFI end-to-end without distorting lower-layer behavior
- domain assumption The simulated traffic and configuration used in validation are representative of real 5G QoS operation
Cite this review
Pith. "Pith review of SDAP-based QoS Flow Multiplexing Support in Simu5G for 5G NR Simulation." pith.science (2026). https://pith.science/paper/V22MPCZP
@misc{pith2026250812785,
author = {Pith},
title = {Pith review of: SDAP-based QoS Flow Multiplexing Support in Simu5G for 5G NR Simulation},
year = {2026},
howpublished = {\url{https://pith.science/paper/V22MPCZP}},
note = {Machine review of arXiv:2508.12785}
}
read the original abstract
The Service Data Adaptation Protocol (SDAP) plays a central role in 5G New Radio (NR), acting as a bridge between the core and radio networks, by enabling QoS Flow multiplexing over shared Data Radio Bearers (DRBs). However, most 5G simulation frameworks, including the popular OMNet++-based Simu5G, lack SDAP support, limiting their ability to model realistic QoS behavior. This paper presents a modular, standardscompliant SDAP extension for Simu5G. The implementation includes core elements such as QoS Flow Identifer (QFI) flow tagging, SDAP header insertion/removal, and configurable logical DRB mapping. The proposed design supports multi-QFI simulation scenarios and enables researchers to model differentiated QoS flows and flowaware scheduling policies. Validation results confirm correct SDAP behavior and pave the way for advanced 5G simulations involving per-flow isolation, latency-sensitive traffic, and industrial QoS profiles.
Forward citations
Cited by 1 Pith paper
-
QoS-Aware Proportional Fairness Scheduling for Multi-Flow 5G UEs: A Smart Factory Perspective
An extended Simu5G with per-QFI modeling and a weighted proportional-fairness scheduler reduces deadline violations and improves fairness in a simulated private 5G smart factory.
Reviewed August 5, 2026 · model on record in the stance chip above.
Discussion (0). Continue with ORCID to comment.