handoverlab 2.2.0__tar.gz → 2.3.0__tar.gz

{handoverlab-2.2.0 → handoverlab-2.3.0}/CHANGELOG.md

@@ -7,6 +7,77 @@ All notable changes to this project are documented in this file. The format foll
 
 ## [Unreleased]
 
+## [2.3.0] - 2026-10-22
+
+### Added
+
+- User-plane buffers at handover as an option (`protocol.buffers`: `am` or `um`, off by default): one downlink
+  bearer per user whose PDCP data wait in a FIFO at the gNB, data forwarding over Xn (`protocol.forwarding`,
+  `protocol.xn_delay_s`) for baseline handover, CHO and LTM / CLTM (late forwarding after HANDOVER SUCCESS unless
+  `protocol.early_forwarding`) and DAPS (the source keeps sending, copies to the target), re-establishment with
+  and without forwarding, the PDCP discard timer of TS 38.331 (`protocol.discard_timer_s`), and with the slot
+  scheduler the HARQ data at a MAC reset (lost with RLC UM, re-sent with AM) and TBs lost after the last HARQ
+  transmission. Sources: TS 38.300 V19.4.0 9.2.3.1-9.2.3.7, TS 38.322 V19.2.0 4.4 / 5.1.2, TS 38.323 V19.1.0
+  5.1.2 / 5.3 / 5.5. New metrics `pdcp_delivered_kbyte_pm`, `pdcp_lost_*`, `pdcp_forwarded_*`, `pdcp_delay_ms`,
+  `pdcp_delay_p95_ms`, `pdcp_delay_forwarded_ms` (0 without the option). Base engine only. With the option off
+  every result is unchanged. Guide: `docs/guides/buffers.md`.
+- Suburban macro (SMa) of TR 38.901 V19.5.0 (`radio.pathloss: sma`, 0.5-37 GHz): the LOS and NLOS path loss of
+  Table 7.4.1-1 (h = 10 m, W = 10 m; the NLOS row is used as printed, without a max() with the LOS loss, so for a
+  UT high up close to a site NLOS can lie below LOS) and the LOS probability of Table 7.4.2-1 with the vegetation
+  density `radio.vegetation` (0, 0.1, 0.2); heights checked against the applicability ranges (25-35 m, 1-14 m).
+- O2I building penetration loss of indoor users (TR 38.901 clause 7.4.3.1): a speed group with `indoor: true`
+  marks indoor users; each gets PL_tw + 0.5 d2D-in + N(0, sigma_P^2) on all its links, drawn once
+  (`radio.o2i_model`: `low`, `high`, `low_a` for SMa, or `mixed`; `radio.o2i_d_in_max_m`; SMa residential /
+  commercial buildings 90 % / 10 %), from its own random stream; an indoor user gets no car penetration loss.
+  The LOS state and the shadowing of an indoor user stay those of its position (stated abstraction, measured by
+  `verify`).
+- `radio.building_los: false` on the street grid: sites above the rooftops, the LOS state from the LOS probability
+  alone (TR 37.885 clause 6.2.1); `radio.env_height_m`: one effective environment height for the UMa / UMi
+  breakpoint (TR 37.885: 0.25 m).
+- Scenario cards `urban-macro-tr37885-4ghz` (the TR 37.885 urban grid below 6 GHz with 500 m macro sites on the
+  hexagonal layout of TR 36.885 Figure A.1.3-1, UMa at 4 GHz, h_E 0.25 m, vehicles at 60 km/h; the wrap-around is
+  replaced by the lattice sites within 1000 m of the grid) and `suburban-sma-7ghz` (11 SMa sites at 1299 m,
+  7 GHz, 80 % indoor users with the low-loss A model, 20 % in cars). Guide: `docs/guides/suburban-o2i.md`.
+- Optional `verify` group `scenarios` (`--only scenarios`; criteria fixed before the first run), reported as it
+  came: 7 pass, 3 fail. The urban macro coupling gain lies 0.3-1.2 dB below an independent computation around
+  the median in every block of seeds (cause open; the LOS share close to the sites is a little low); the check
+  of the outdoor SMa users fails on sampling noise (40 seeds pooled: within 0.54 dB); a TR-exact treatment of
+  indoor users (LOS at d2D-out, O2I shadowing 8 dB) gives a 2.0 dB wider upper tail (95 % point) than the
+  simulator's abstraction, with the median within 0.1 dB.
+- Scenario card `hst-fr2-28ghz`: the FR2 high-speed train of TR 38.854 V18.0.0 as its system-level mobility
+  study sets it up (Table 6.3.8.1-1): one train with one roof-mounted CPE at 350 km/h on a straight track, an RRH
+  every 700 m on one side, 10 m from the track (Scenario-A), one panel of 8 x 8 elements with one SSB beam per RRH
+  pointing along the track at the next RRH, every RRH its own cell (L3 handover, no DPS), 28 GHz, 50 MHz,
+  120 kHz, 31 dBm, TR 38.901 RMa LOS only, no inter-cell interference, N310 = N311 = 2 and the TS 38.133
+  measurement periods of the legacy requirements (480 ms). Guide: `docs/guides/high-speed-train.md`, with the
+  pre-registered comparison against the TR's results.
+- `radio.beams.am_db`: A_m of the TR 38.901 Table 7.3-1 element pattern (default 30 dB, unchanged results); a
+  larger value lowers the back lobe, as the antenna "without back lobe" of the TR 38.854 mobility study.
+- Dual connectivity as an option (`protocol.dc`, off by default): NR-DC of TS 37.340 V19.3.0 with the master cell
+  group on the scenario's other carriers and a secondary cell group (one PSCell) on the cells of one layer of
+  `radio.layers`: SN addition on event A4 (clause 10.2), PSCell change on event A3 (clauses 10.5, 10.6) and SN
+  release (clause 10.4), each prepared between the nodes and sent over the MCG, random access on the PSCell under
+  T304; separate radio-link monitoring and SCG radio-link failure (TS 38.331 5.3.10.3); SCG failures reported to
+  the MN, which releases the SCG (clause 7.7); an MCG failure releases the SCG (TS 38.331 5.3.7.2); at an MCG
+  handover the SN is kept or released (`on_mcg_ho`, clause 10.7). The MCG behaves exactly as without the SCG.
+  New metrics `sn_additions_pm`, `sn_addition_failures_pm`, `pscell_changes_pm`, `pscell_change_failures_pm`,
+  `sn_releases_pm`, `scg_rlf_pm`, `scg_failures_pm`, `scg_released_by_mcg_pm`, `scg_time_share`,
+  `scg_rate_mbps`, `pscell_change_interruption_s_pm`, `dc_rrc_messages_pm` (zero without the option). Guide:
+  `docs/guides/dual-connectivity.md`, with what is left out.
+
+### Documentation
+
+- Fresh held-out check N3 of the failure model on 40 new ns-3 runs, limits fixed before the runs: a fixed
+  link-monitoring interferer load (`protocol.lm_load` 0.15, chosen on the earlier runs) raises the failure level
+  from 0.16 to 0.47 of ns-3's and the failure order from 0.78 to 0.95; the level check (0.67-1.5) fails, so the
+  setting is reported, not adopted. The recovery time after a failure is set against the bounds of TS 38.133
+  clause 6.2.1.2.1 (about 0.28-1.55 s), which the default 1.0 s meets. `docs/calibration.md`.
+
+### Not done
+
+- The 7 GHz large-scale calibration of TR 38.901 clause 7.8.1 (Table 7.8-1A): the TR gives the results only by
+  reference to R1-2506406, which this release does not include.
+
 ## [2.2.0] - 2026-10-22
 
 ### Added
@@ -934,7 +1005,8 @@ First alpha release (stage 1: the core simulator).
 - Documentation: README, user guide, contribution guide, citation file; CI on Linux, Windows and
   macOS with Python 3.9-3.12.
 
-[Unreleased]: https://github.com/mjs19971997/handoverlab/compare/v2.2.0...HEAD
+[Unreleased]: https://github.com/mjs19971997/handoverlab/compare/v2.3.0...HEAD
+[2.3.0]: https://github.com/mjs19971997/handoverlab/compare/v2.2.0...v2.3.0
 [2.2.0]: https://github.com/mjs19971997/handoverlab/compare/v2.1.0...v2.2.0
 [2.1.0]: https://github.com/mjs19971997/handoverlab/compare/v2.0.0...v2.1.0
 [2.0.0]: https://github.com/mjs19971997/handoverlab/compare/v1.12.0...v2.0.0

{handoverlab-2.2.0 → handoverlab-2.3.0}/CITATION.cff

@@ -11,7 +11,7 @@ abstract: >-
   measurement chain, a radio-link failure model, an outcome label for every handover attempt,
   a plug-in interface for handover rules, equal-budget tuning studies with paired statistics,
   and verification against hand-computed values, golden event-log fingerprints and ns-3 / 5G-LENA.
-version: "2.2.0"
+version: "2.3.0"
 doi: 10.5281/zenodo.23409131
 identifiers:
   - type: doi

{handoverlab-2.2.0 → handoverlab-2.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: handoverlab
-Version: 2.2.0
+Version: 2.3.0
 Summary: System-level handover simulator for 5G-Advanced and beyond-5G research
 Author: Mostafa Jalili Sanjarani, Yasser Elmi Sola
 License-Expression: MIT
@@ -142,10 +142,12 @@ event D2 of Release 18:
 - **Scenarios**: the TR 37.885 urban street grid (configurable number of blocks; 433 m x 250 m
   pitch, 20 m streets) with sites on the pavement, an open area with a hexagonal site grid, the
   TR 37.885 highway (since 1.11.0 with wrap-around, LOS-only links and both site layouts of
-  TR 36.885, below and above 6 GHz), the TR 38.901 indoor office, rural macro cells, a LEO satellite with
+  TR 36.885, below and above 6 GHz), the TR 37.885 urban grid with 500 m macro sites (since 2.3.0), the
+  TR 38.901 indoor office, rural and suburban (SMa, since 2.3.0) macro cells, a LEO satellite with
   earth-moving beams (since 2.0.0, TR 38.811 and TR 38.821), explicit site lists, and built-in scenario
   cards (`handoverlab scenarios`).
-- **Channel**: TR 38.901 UMi street canyon, UMa, RMa and InH-Office path loss (LOS/NLOS); line of sight from the
+- **Channel**: TR 38.901 UMi street canyon, UMa, RMa, SMa (since 2.3.0) and InH-Office path loss (LOS/NLOS); O2I
+  building penetration loss of indoor users (since 2.3.0); line of sight from the
   building geometry plus the spatially consistent LOS state, hard or soft; spatially correlated shadowing; a
   time-varying component; L1 measurement error; beam gain and load-coupled interference;
   optionally a penetration loss per user (in-car loss of TR 38.901); or, since 1.12.0, your own radio
@@ -189,10 +191,10 @@ the clause-by-clause detail is in [standard compliance](https://github.com/mjs19
 
 | Part | Modelled | Abstracted | Not modelled |
 |---|---|---|---|
-| Layouts | `street_grid` (TR 37.885 urban grid), `open_area`, `highway` (TR 37.885 / TR 36.885, wrap-around), `indoor` (TR 38.901 office), `ntn` (one LEO satellite, TR 38.821); explicit site lists | sites on the pavement with small cells (urban cards) | the 500 m macro grid of the TR 37.885 urban scenario, several satellites |
-| Channel | TR 38.901 path loss and LOS (UMi, UMa, RMa, InH), LOS from buildings, spatially consistent LOS and shadowing, penetration loss, radio maps from a file (clause 8), TR 38.811 for the satellite | received power per site and step with a slow time-varying component; optional TDL fast fading with effective SINRs (clause 7.7.2, since 2.2.0) | CDL and the full fast-fading model of clause 7.5, MIMO |
-| Beams and carriers | SSB beams per sector, cell quality from beams, beam failure detection and recovery, several carriers with gaps and Event A5 | the TR 38.901 antenna element and DFT beams; isotropic UE | UE-side beamforming, dual connectivity and PSCell change |
-| Mobility | street-following vehicles (60 km/h, two lanes), highway lanes at 70/140 km/h, random waypoints, pedestrians | constant speed per user | handheld rotation and body blockage |
+| Layouts | `street_grid` (TR 37.885 urban grid), `open_area`, `highway` (TR 37.885 / TR 36.885, wrap-around), `indoor` (TR 38.901 office), `ntn` (one LEO satellite, TR 38.821); explicit site lists | sites on the pavement with small cells (urban cards); the TR 37.885 urban macro grid without wrap-around (`urban-macro-tr37885-4ghz`) | several satellites |
+| Channel | TR 38.901 path loss and LOS (UMi, UMa, RMa, SMa, InH), LOS from buildings, spatially consistent LOS and shadowing, car and O2I building penetration loss, radio maps from a file (clause 8), TR 38.811 for the satellite | received power per site and step with a slow time-varying component; indoor users keep the LOS state and shadowing of their position; optional TDL fast fading with effective SINRs (clause 7.7.2, since 2.2.0) | CDL and the full fast-fading model of clause 7.5, MIMO |
+| Beams and carriers | SSB beams per sector, cell quality from beams, beam failure detection and recovery, several carriers with gaps and Event A5; dual connectivity (NR-DC: SN addition, PSCell change, SN release, SCG failure; option since 2.3.0) | the TR 38.901 antenna element and DFT beams; isotropic UE; the SCG as one PSCell with a full-buffer share | UE-side beamforming, conditional PSCell change, fast MCG recovery |
+| Mobility | street-following vehicles (60 km/h, two lanes), highway lanes at 70/140 km/h, a train at 350 km/h (TR 38.854), random waypoints, pedestrians | constant speed per user | handheld rotation and body blockage |
 | Traffic and load | constant rates per 5QI, full buffer, periodic, FTP model 3; cell load drives interference | rate from SINR (Shannon-type mapping), no scheduler | slot scheduler, HARQ, RLC/PDCP, TCP and applications |
 | Measurements | L1 samples with error, TS 38.331 L3 filter, TS 38.133 measurement periods and gaps (option) | wideband RSRP; SS-RSRP per resource element with beams/carriers | RSRQ, CSI reporting |
 | Procedures | baseline (A3), CHO, DAPS, LTM, conditional LTM, CHO with D1/D2 for satellites, A3/A5 between carriers; rules `a3`, `a3a5`, `a3_mro`, `a3_bandit`, `dqn`, `cho`, `cho_d2`, `daps`, `ltm`, `cltm` | fixed preparation, command and execution delays; re-establishment always succeeds after a fixed outage | condEventT1, RACH-less NTN handover, Xn signalling in detail |
@@ -201,7 +203,8 @@ the clause-by-clause detail is in [standard compliance](https://github.com/mjs19
 
 Built-in cards: `smoke`, `urban-grid-10ghz`, `fr3-urban-15ghz`, `urban-grid-28ghz-beams`, `dense-urban-2layer`,
 `open-area-10ghz`, `ns3-urban-3.5ghz`, `highway-tr37885-4ghz`, `highway-tr37885-30ghz`, `indoor-office-4ghz`,
-`rural-700mhz`, `ntn-leo600-2ghz`; each names the source of every value and its own limitations.
+`rural-700mhz`, `ntn-leo600-2ghz`, `urban-macro-tr37885-4ghz`, `suburban-sma-7ghz`, `hst-fr2-28ghz`; each
+names the source of every value and its own limitations.
 
 ## Scope: 5G-Advanced and beyond 5G
 

{handoverlab-2.2.0 → handoverlab-2.3.0}/README.md

@@ -84,10 +84,12 @@ event D2 of Release 18:
 - **Scenarios**: the TR 37.885 urban street grid (configurable number of blocks; 433 m x 250 m
   pitch, 20 m streets) with sites on the pavement, an open area with a hexagonal site grid, the
   TR 37.885 highway (since 1.11.0 with wrap-around, LOS-only links and both site layouts of
-  TR 36.885, below and above 6 GHz), the TR 38.901 indoor office, rural macro cells, a LEO satellite with
+  TR 36.885, below and above 6 GHz), the TR 37.885 urban grid with 500 m macro sites (since 2.3.0), the
+  TR 38.901 indoor office, rural and suburban (SMa, since 2.3.0) macro cells, a LEO satellite with
   earth-moving beams (since 2.0.0, TR 38.811 and TR 38.821), explicit site lists, and built-in scenario
   cards (`handoverlab scenarios`).
-- **Channel**: TR 38.901 UMi street canyon, UMa, RMa and InH-Office path loss (LOS/NLOS); line of sight from the
+- **Channel**: TR 38.901 UMi street canyon, UMa, RMa, SMa (since 2.3.0) and InH-Office path loss (LOS/NLOS); O2I
+  building penetration loss of indoor users (since 2.3.0); line of sight from the
   building geometry plus the spatially consistent LOS state, hard or soft; spatially correlated shadowing; a
   time-varying component; L1 measurement error; beam gain and load-coupled interference;
   optionally a penetration loss per user (in-car loss of TR 38.901); or, since 1.12.0, your own radio
@@ -131,10 +133,10 @@ the clause-by-clause detail is in [standard compliance](https://github.com/mjs19
 
 | Part | Modelled | Abstracted | Not modelled |
 |---|---|---|---|
-| Layouts | `street_grid` (TR 37.885 urban grid), `open_area`, `highway` (TR 37.885 / TR 36.885, wrap-around), `indoor` (TR 38.901 office), `ntn` (one LEO satellite, TR 38.821); explicit site lists | sites on the pavement with small cells (urban cards) | the 500 m macro grid of the TR 37.885 urban scenario, several satellites |
-| Channel | TR 38.901 path loss and LOS (UMi, UMa, RMa, InH), LOS from buildings, spatially consistent LOS and shadowing, penetration loss, radio maps from a file (clause 8), TR 38.811 for the satellite | received power per site and step with a slow time-varying component; optional TDL fast fading with effective SINRs (clause 7.7.2, since 2.2.0) | CDL and the full fast-fading model of clause 7.5, MIMO |
-| Beams and carriers | SSB beams per sector, cell quality from beams, beam failure detection and recovery, several carriers with gaps and Event A5 | the TR 38.901 antenna element and DFT beams; isotropic UE | UE-side beamforming, dual connectivity and PSCell change |
-| Mobility | street-following vehicles (60 km/h, two lanes), highway lanes at 70/140 km/h, random waypoints, pedestrians | constant speed per user | handheld rotation and body blockage |
+| Layouts | `street_grid` (TR 37.885 urban grid), `open_area`, `highway` (TR 37.885 / TR 36.885, wrap-around), `indoor` (TR 38.901 office), `ntn` (one LEO satellite, TR 38.821); explicit site lists | sites on the pavement with small cells (urban cards); the TR 37.885 urban macro grid without wrap-around (`urban-macro-tr37885-4ghz`) | several satellites |
+| Channel | TR 38.901 path loss and LOS (UMi, UMa, RMa, SMa, InH), LOS from buildings, spatially consistent LOS and shadowing, car and O2I building penetration loss, radio maps from a file (clause 8), TR 38.811 for the satellite | received power per site and step with a slow time-varying component; indoor users keep the LOS state and shadowing of their position; optional TDL fast fading with effective SINRs (clause 7.7.2, since 2.2.0) | CDL and the full fast-fading model of clause 7.5, MIMO |
+| Beams and carriers | SSB beams per sector, cell quality from beams, beam failure detection and recovery, several carriers with gaps and Event A5; dual connectivity (NR-DC: SN addition, PSCell change, SN release, SCG failure; option since 2.3.0) | the TR 38.901 antenna element and DFT beams; isotropic UE; the SCG as one PSCell with a full-buffer share | UE-side beamforming, conditional PSCell change, fast MCG recovery |
+| Mobility | street-following vehicles (60 km/h, two lanes), highway lanes at 70/140 km/h, a train at 350 km/h (TR 38.854), random waypoints, pedestrians | constant speed per user | handheld rotation and body blockage |
 | Traffic and load | constant rates per 5QI, full buffer, periodic, FTP model 3; cell load drives interference | rate from SINR (Shannon-type mapping), no scheduler | slot scheduler, HARQ, RLC/PDCP, TCP and applications |
 | Measurements | L1 samples with error, TS 38.331 L3 filter, TS 38.133 measurement periods and gaps (option) | wideband RSRP; SS-RSRP per resource element with beams/carriers | RSRQ, CSI reporting |
 | Procedures | baseline (A3), CHO, DAPS, LTM, conditional LTM, CHO with D1/D2 for satellites, A3/A5 between carriers; rules `a3`, `a3a5`, `a3_mro`, `a3_bandit`, `dqn`, `cho`, `cho_d2`, `daps`, `ltm`, `cltm` | fixed preparation, command and execution delays; re-establishment always succeeds after a fixed outage | condEventT1, RACH-less NTN handover, Xn signalling in detail |
@@ -143,7 +145,8 @@ the clause-by-clause detail is in [standard compliance](https://github.com/mjs19
 
 Built-in cards: `smoke`, `urban-grid-10ghz`, `fr3-urban-15ghz`, `urban-grid-28ghz-beams`, `dense-urban-2layer`,
 `open-area-10ghz`, `ns3-urban-3.5ghz`, `highway-tr37885-4ghz`, `highway-tr37885-30ghz`, `indoor-office-4ghz`,
-`rural-700mhz`, `ntn-leo600-2ghz`; each names the source of every value and its own limitations.
+`rural-700mhz`, `ntn-leo600-2ghz`, `urban-macro-tr37885-4ghz`, `suburban-sma-7ghz`, `hst-fr2-28ghz`; each
+names the source of every value and its own limitations.
 
 ## Scope: 5G-Advanced and beyond 5G
 

{handoverlab-2.2.0 → handoverlab-2.3.0}/docs/calibration.md

@@ -22,11 +22,38 @@ registered (2.1.0 defaults gave the same verdicts):
 | Recovery: time without connection per failure | 0.09 s | 1.0 s (`reest_s`) | ratio 0.67-1.5 | fails |
 | Execution failures | none in any cell | 0-5 % | needs 10 in ns-3 | not measurable |
 
-The two failing parts explain much of the failure gap: HandoverLab's full-buffer load always fills
-every cell, so interference is far higher than with ns-3's offered traffic (ns-3 has fewer failures
-at full traffic, 90 to 34 and 13 to 3; HandoverLab many more, 18 to 521 and 4 to 175), and a
-re-establishment takes a fixed second. A traffic-driven load and a recovery time from the standard
-texts are the next steps; they need new ns-3 runs to be judged, as these runs have now been seen.
+ns-3's full traffic is an overload too (more than a cell can carry), so both simulators fill the
+cells; the difference is what link monitoring sees. In ns-3 its SINR hardly moves with the data
+load; in HandoverLab it follows the data load by default (ns-3 has fewer failures at full traffic,
+90 to 34 and 13 to 3; HandoverLab many more, 18 to 521 and 4 to 175). TS 38.133 V19.6.0 clause 8.1
+evaluates the link on a hypothetical PDCCH, and the neighbours' control channels and reference
+signals are sent whatever the data load; `protocol.lm_load` gives link monitoring such a fixed
+interferer load.
+
+On recovery, the standard does not fix one value: TS 38.133 V19.6.0 clause 6.2.1.2.1 bounds the
+re-establishment delay by 50 ms + T_identify_intra_NR (known FR1 cell: max(200 ms, 5 T_SMTC), Table
+6.2.1.2.1-1) + T_SI-NR + T_PRACH (at most the SSB-to-PRACH association period + 10 ms, TS 38.213
+Table 8.1-1), followed by RRCReestablishment processing of 10 ms (TS 38.331 V19.4.0 Table 12.1-1).
+That is about 0.28 s when the system information is already held and about 1.55 s with the T_SI of
+1280 ms of the test case A.6.3.2.1.1.2. HandoverLab's `reest_s` of 1.0 s lies inside; ns-3 (ideal
+RRC) takes 0.09 s, below both. The recovery time was therefore not changed towards ns-3.
+
+**Fresh held-out check N3 (2.3.0).** One setting was chosen on the light-traffic N2 cells above
+(`protocol.lm_load` 0.15, with `protocol.exec_can_fail` false, as ns-3 has ideal execution) and
+tested on 40 new ns-3 runs (seeds 301-305, ISD 200 / 400 m, 12 / 24 m/s, TTT 100 / 640 ms, light
+traffic), with limits fixed before the runs:
+
+| Check | Limit | Fixed link-monitoring load 0.15 | Default link monitoring |
+|---|---|---|---|
+| Failure level, sum HandoverLab / sum ns-3 | 0.67-1.5 | 0.47, fails | 0.16, fails |
+| Failure order over the 8 cells (Spearman) | at least 0.8 | 0.95, passes | 0.78, fails |
+| Handover rate, median ratio | 0.8-1.25 | 0.93, passes | 0.96, passes |
+| Direction of the TTT effect on failures | 3 of 4 | 4, passes | 4, passes |
+
+At TTT 100 ms the fixed load gives ns-3's failure counts (17 against 14, 11 against 10); at
+TTT 640 ms it gives about half of them (84 against 180, 68 against 193), the known effect of ns-3's
+slow out-of-sync detection (below). As fixed in advance, the setting is not adopted because the
+level check fails; it is reported here, and no further tuning was done on these runs.
 
 **Summary (1.5.0).** Handover and unnecessary-handover rates of HandoverLab agree with ns-3 /
 5G-LENA. For failure rates, the order of settings and conditions agrees on part A and on both

handoverlab-2.3.0/docs/guides/buffers.md

@@ -0,0 +1,117 @@
+# User-plane buffers at handover
+
+By default HandoverLab counts the time a handover interrupts the data (`interruption_s_pm`) but not
+what happens to the data themselves. Since 2.3.0 the option `protocol.buffers` adds a simplified
+PDCP / RLC model of the downlink: every user has one data radio bearer whose data wait in a FIFO at
+the gNB that holds its PDCP entity, are forwarded to the target cell over Xn, and may be lost or
+delayed by the interruption. It works with every procedure (baseline handover such as A3, CHO,
+DAPS, LTM and conditional LTM). It is off by default; with it off every result of 2.2.0 is
+unchanged bit for bit (the new metrics are 0).
+
+```yaml
+scenario:
+  base: smoke
+  traffic: {model: periodic}      # periodic, ftp3 or fixed (constant-rate arrivals); not full_buffer
+  protocol:
+    buffers: am                   # RLC mode of the bearer: am or um; null: off
+    forwarding: true              # the source forwards its data to the target over Xn
+    early_forwarding: false       # CHO and LTM: forward before the execution instead of after it
+    xn_delay_s: 0.005             # one-way Xn delay [s] (assumption)
+    discard_timer_s: null         # PDCP discard timer [s]: null (infinity) or a TS 38.331 value
+    sdu_bytes: null               # SDU size for the SDU counts (null: packet_bytes or 1500)
+```
+
+It combines with the slot scheduler (`protocol.scheduler`, see [scheduler](scheduler.md)): the data
+in the HARQ processes then take part (see section 2).
+
+## 1. What happens at a handover
+
+| Procedure | Source | HandoverLab |
+|---|---|---|
+| Baseline handover (A3, A3/A5, ...) | TS 38.300 V19.4.0 9.2.3.2.1 NOTE 2 (forwarding may start with the command), 9.2.3.2.2, 9.2.3.2.3 | when the UE leaves the source, the source forwards its FIFO and the data arriving until the completion; the target can send them `xn_delay_s` after they were forwarded and sends them before new data |
+| CHO | 9.2.3.4.2 NOTE 2, 9.2.3.4.3, 9.2.3.4.4 | late forwarding: the source forwards once HANDOVER SUCCESS tells it the target, so the data are at the target 2 x `xn_delay_s` after the completion; `early_forwarding`: the data are at the target when the UE arrives |
+| LTM, conditional LTM | 9.2.3.5.2 step 9a, NOTE 4, NOTE 5; 9.2.3.5.3; 9.2.3.7.1 | every cell of HandoverLab is its own gNB, so a cell switch is inter-gNB LTM: late or early forwarding as for CHO |
+| DAPS | 9.2.3.2.2 (DAPS), 9.2.3.2.3 | the forwarding tunnel always exists; the source keeps sending during the execution and forwards every SN-assigned SDU as a copy; the target sends the rest at the completion, without loss or wait; a fallback keeps the data at the source |
+| Failure and re-establishment | 9.2.3.3 steps 6/7 | with forwarding the data of the last gNB move to the new cell and can be sent `xn_delay_s` after the re-establishment; a recovery into a prepared cell (CHO, LTM) is forwarded as an execution of that procedure; without forwarding the data are lost in another cell and kept in the same cell |
+| Discard timer | TS 38.323 V19.1.0 5.3; TS 38.331 PDCP-Config discardTimer | data older than `discard_timer_s` are discarded (lost) |
+
+Without forwarding (`forwarding: false`) the data at the source and the data arriving there until the
+completion are lost at every execution (not with DAPS, which always forwards).
+
+## 2. AM and UM
+
+The RLC mode matters for the data that the lower layers hold when the UE leaves: with the slot
+scheduler, the data in the HARQ processes. An RRC handover needs a MAC reset and an RLC
+re-establishment (TS 38.300 9.2.3.1; TS 38.322 V19.2.0 5.1.2 discards the RLC PDUs). With RLC AM
+these data are not acknowledged, so they are forwarded and sent again by the target (9.2.3.2.2:
+the target re-transmits all forwarded data); with RLC UM no PDCP SDU is re-transmitted in the
+target, so they are lost. A transport block lost after the last HARQ transmission is sent again by
+RLC ARQ with AM and lost with UM (ARQ exists only for AM, TS 38.322 4.4). Without the slot
+scheduler the rate model delivers at once, there are no data in the lower layers, and AM and UM give
+the same results.
+
+## 3. Delay
+
+The data plane keeps the measurement interval of the rate model or the scheduler (40 ms by
+default), and a user executing at a measurement instant gets no data in that interval, as in 2.2.0.
+Within an interval the data of a user leave the FIFO as a fluid, at the larger of its round-robin
+share of the free carrier at its spectral efficiency and the rate needed to send what the interval
+delivers; data arrive at the start of their interval. The PDCP delay of a byte is its delivery time
+minus its arrival at the gNB; `pdcp_delay_ms` is the byte-weighted mean, `pdcp_delay_p95_ms` the
+95th percentile (1 ms bins) and `pdcp_delay_forwarded_ms` the mean over the data that a target sent
+after forwarding. The fluid leaves out the slot and HARQ latency of the air interface, so without a
+handover small packets see delays far below 1 ms; the delay metrics mainly show what interruptions,
+forwarding and links below Qout (no data in the rate model) add.
+
+## 4. Metrics
+
+| Metric | Unit | Meaning |
+|---|---|---|
+| `pdcp_delivered_kbyte_pm` | kbyte/UE-min | data delivered |
+| `pdcp_lost_kbyte_pm`, `pdcp_lost_share` | kbyte/UE-min, 1 | data lost, and the lost share of what arrived |
+| `pdcp_lost_handover_kbyte_pm` | kbyte/UE-min | lost at executions (no forwarding; HARQ data with UM) |
+| `pdcp_lost_failure_kbyte_pm` | kbyte/UE-min | lost at failures and re-establishments |
+| `pdcp_lost_discard_kbyte_pm` | kbyte/UE-min | discarded by the discard timer |
+| `pdcp_lost_harq_kbyte_pm` | kbyte/UE-min | transport blocks lost after the last HARQ transmission with UM |
+| `pdcp_lost_sdus_pm`, `pdcp_forwarded_sdus_pm` | 1/UE-min | lost and forwarded data in SDUs of `sdu_bytes` |
+| `pdcp_forwarded_kbyte_pm` | kbyte/UE-min | data forwarded over Xn (DAPS: the copies, duplicates included) |
+| `pdcp_delay_ms`, `pdcp_delay_p95_ms`, `pdcp_delay_forwarded_ms` | ms | PDCP delay |
+
+## 5. Assumptions and limits
+
+- Assumptions (not in the texts): the Xn delay; whether the network forwards ("may"); that the gNB
+  uses the discardTimer values for its downlink data (TS 38.323 defines the timer for the
+  transmitting entity); SN assignment on arrival at the source (DAPS forwards SN-assigned SDUs);
+  1500-byte SDUs for the SDU counts of non-periodic traffic; copies sent by early forwarding to
+  candidates that are not used are not counted.
+- Downlink only, one bearer per user; no PDCP reordering or duplicates at the UE, no PDCP status
+  report, no path-switch delay (the path switches at the completion), no intra-CU LTM.
+- The interruption in the data plane is quantised to the measurement interval (as the rate of
+  2.2.0); a DAPS source that has a radio link failure during the execution stops sending.
+- This version needs the base engine (no beams, layers, NTN or TS 38.133 periods) and is not run in
+  the batched engine; `full_buffer` traffic is rejected (no arrivals, no delay).
+
+## 6. An example
+
+`smoke` card, 15 users, 30 s, two seeds, RLC AM, periodic traffic (100-byte packets every 20 ms):
+
+| Rule | forwarded kbyte/UE-min | lost share without forwarding | mean PDCP delay | delay of forwarded data |
+|---|---|---|---|---|
+| A3 | 6.2 | 2.1 % | 2.9 ms | 123 ms |
+| CHO (late / early forwarding) | 4.2 | 1.4 % | 1.3 ms | 80 / 70 ms |
+| DAPS | 6.2 (copies) | 0 | 2.6 ms | 157 ms |
+| LTM | 1.6 | 0.5 % | 0.6 ms | 92 ms |
+
+With forwarding nothing is lost. Late forwarding adds the 2 x 5 ms wait for CHO; for LTM the wait
+ends before the next measurement instant and does not show. DAPS gains little here: most of its
+executions start with the source SINR already below Qout, where the rate model sends nothing, so the
+data left for the target are the oldest ones.
+
+## 7. Checks
+
+`tests/test_buffers.py` holds the criteria fixed before the code: hand-computed cases for every procedure (forwarded bytes, losses,
+delays with and without the late-forwarding wait, DAPS, HARQ data with AM and UM, the discard timer,
+re-establishment with and without forwarding), conservation (arrived = delivered + lost + queued,
+checked at the end of every run with the option) for A3, CHO, DAPS, LTM and CLTM with AM and UM,
+with and without the slot scheduler, HARQ losses with UM and none with AM, a delay below one
+interval without handovers, and that the option off changes no fingerprint.

handoverlab-2.3.0/docs/guides/dual-connectivity.md

@@ -0,0 +1,114 @@
+# How to study dual connectivity (NR-DC)
+
+Since 2.3.0 a user can hold a secondary cell group (SCG) next to its master cell group (MCG): the
+NR-DC case of TS 37.340 V19.3.0 clause 4.1.3.3, one gNB as master node (MN) and another as secondary
+node (SN). The option `protocol.dc` is off by default; with it off every result stays as it was.
+
+The model is the simplest consistent subset that a system-level simulator needs: when an SCG is
+added, changed or lost, what that costs in signalling and interruption, and how much time the
+user spends with a second link. The MCG behaves exactly as without dual connectivity: its handover
+rule, radio-link monitoring, failures and re-establishment do not see the SCG (a test checks that the
+MCG event log is the same whether an SN is ever added or not).
+
+## 1. Turn it on
+
+The SCG lives on the cells of one entry of `radio.layers`, on a carrier that no MCG cell uses. The
+built-in `dense-urban-2layer` card has a 4 GHz macro layer and a 30 GHz micro layer, which makes
+an FR1 MCG and an FR2 SCG:
+
+```yaml
+# dc.yaml
+schema: 1
+scenario:
+  base: dense-urban-2layer
+  protocol:
+    dc: {scg_layer: micro-30ghz}
+seeds: [1, 2, 3]
+rules:
+  - {rule: a3, off_db: 3.0, ttt_s: 0.16}
+output: results/dc.csv
+```
+
+```bash
+handoverlab run dc.yaml
+```
+
+| Key of `protocol.dc` | Default | Meaning |
+|---|---|---|
+| `scg_layer` | first entry of `radio.layers` | layer whose cells form the SCG |
+| `add_thresh_dbm`, `add_ttt_s` | `-110`, `0.16` | SN addition: event A4, the best SCG cell's L3 SS-RSRP per RE above the threshold for the time-to-trigger |
+| `change_off_db`, `change_ttt_s` | `3`, `0.16` | PSCell change: event A3 among the SCG cells |
+| `release_thresh_dbm`, `release_ttt_s` | `-120`, `0.16` | SN release: the PSCell's L3 SS-RSRP below the threshold |
+| `prep_s`, `exec_s` | `protocol.prep_s`, `protocol.exec_s` | preparation between the nodes; random access on the PSCell |
+| `on_mcg_ho` | `keep` | at an MCG handover the target MN keeps the SN (`keep`) or releases it (`release`) |
+
+The MCG uses the base layer and any other layer; it never hands over to an SCG cell, so
+`inter_frequency_handovers_pm` counts only handovers between MCG carriers.
+
+## 2. What is modelled (TS 37.340 V19.3.0, TS 38.331 V18.11.0)
+
+| Procedure | Clause | In HandoverLab |
+|---|---|---|
+| SN addition, initiated by the MN on its measurements | 7.2, 10.2.2 | A4 held for `add_ttt_s` while the MCG is connected; `prep_s` (SN Addition Request / Acknowledge); RRC reconfiguration over the MCG; random access on the new PSCell after `exec_s`; the SCG joins when the PSCell SINR reaches Qout while T304 runs |
+| SN change and PSCell change within the SN | 10.5.2, 10.6 | A3 among SCG cells, then the same steps; no SCG data from the command until the target is joined |
+| SN release | 10.4.2 | PSCell below `release_thresh_dbm` for `release_ttt_s`, released after `prep_s` |
+| SCG radio-link failure | 7.7; TS 38.331 5.3.10.3 | own Qout / Qin filters, N310 / N311 indications and T310 on the PSCell, with the protocol's constants |
+| SCG failure handling | 7.7; TS 38.331 5.7.3 | SCG RLF and failed additions or changes are reported to the MN (SCGFailureInformation) instead of a re-establishment; the MN releases the SCG |
+| MCG failure | 7.7; TS 38.331 5.3.7.2 | re-establishment, which performs the MR-DC release |
+| Inter-MN handover | 10.7 | `on_mcg_ho`: the SN is kept or released |
+
+Every SCG reconfiguration is sent over the MCG (SRB1). One that falls due while the MCG is not
+connected or its T310 runs is dropped (the trigger starts again). The SCG cells' L1 samples enter
+an L3 filter of their own (TS 38.331 5.5.3.2 with the reference period of the SCG carrier). The
+PSCell sends on its strongest SSB beam of the current L1 instant (ideal SCG beam management), and
+the other cells of the SCG carrier interfere with their load.
+
+**SCG data.** An SCG user receives W x min(log2(1 + SINR), se_max) x (1 - background load of the
+PSCell) / (SCG users of that PSCell): a full-buffer share of the PSCell, reported as
+`scg_rate_mbps`. The MCG rate (`rate_mbps`) is computed as without dual connectivity; the two are
+not split by a bearer model.
+
+## 3. Metrics
+
+`sn_additions_pm`, `sn_addition_failures_pm`, `pscell_changes_pm`, `pscell_change_failures_pm`,
+`sn_releases_pm`, `scg_rlf_pm`, `scg_failures_pm` (RLF + failed additions + failed changes),
+`scg_released_by_mcg_pm`, `scg_time_share`, `scg_rate_mbps`, `pscell_change_interruption_s_pm` and
+`dc_rrc_messages_pm` (see [the metric reference](../reference/metrics.md)). With the event-log level
+`full` the procedure trace has the SCG events `sn_add_request` (value: the time the A4 condition was
+entered), `sn_add`, `sn_add_failure`, `pscell_change`, `pscell_change_failure`, `scg_rlf`,
+`sn_release`, `scg_release_mcg_failure` and `scg_release_mcg_ho`.
+
+## 4. What is left out
+
+- Other MR-DC options (EN-DC, NGEN-DC, NE-DC) and SCells in either cell group.
+- Fast MCG link recovery (T316); SCG deactivation and activation (clause 7.13).
+- Conditional PSCell addition and change (CPA, CPC, subsequent CPAC; clause 10.2.3), SCG LTM, CHO with
+  candidate SCGs (clauses 10.19, 10.20).
+- Split SRB and SRB3 (clauses 7.5, 7.6): every SCG message goes over the MCG.
+- Bearer types, PDCP duplication, data forwarding, the SN status transfer and the path switch.
+- The MN's choice to keep or change the SN after an SCG failure (the model always releases it) and
+  to change the SN at an inter-MN handover.
+- Measurement gaps for the SCG carrier and UE capability coordination; the uplink; SCG beam management
+  (the strongest beam is used).
+
+## 5. Pre-registered checks (2.3.0)
+
+Criteria fixed before the runs. World: `dense-urban-2layer` with `protocol.dc: {scg_layer: micro-30ghz}`
+(20 users, 120 s, 100 s measured), rule A3 3 dB / 160 ms, seeds 1-3.
+
+| Check | Result |
+|---|---|
+| D1: with `protocol.dc` unset every existing test and golden fingerprint is unchanged | pass |
+| D2: the MCG event log is the same with an SN never added (`add_thresh_dbm: 1000`) and with `on_mcg_ho: release` | pass (4 of 4 comparisons, seeds 1 and 2; also a test) |
+| D3: every started addition or change ends once as success, failure or drop | pass (test) |
+| D4: addition timing = A4 entry + TTT + preparation + random access; PSCell changes happen; an MCG failure releases the SCG | pass (tests) |
+| D5a: a 10 dB lower addition threshold raises the SCG time share | **fail**: no change at all (0.953 both). In this dense micro layer the best SCG cell is above -110 dBm everywhere, so the A4 threshold never binds; the time without SCG comes from MCG failures (each releases the SCG) and the addition delay. |
+| D5b: more PSCell changes than MCG handovers (9 micro sites per macro site) | pass (20.2 vs 18.0 per UE-min) |
+| D5c: more SCG failures at 60 km/h than at 30 km/h | pass (0.25 vs 0.03 per UE-min) |
+
+Mean of the three seeds at 30 km/h (default thresholds, SN kept at MCG handovers): SCG time share 0.95,
+20.2 PSCell changes and 1.3 SN additions per UE-min, 1.3 SCG releases per UE-min by MCG failures,
+0.03 SCG failures per UE-min (all failed additions or changes, no SCG radio-link failure), SCG rate
+184 Mbit/s per user next to an MCG rate of 10 Mbit/s. At 60 km/h: time share 0.91, 30 PSCell changes,
+0.25 SCG failures and 2.5 releases by MCG failures per UE-min. With `on_mcg_ho: release` the SN is
+re-added after every MCG handover (17-18 additions per UE-min) and the time share falls to 0.85.

handoverlab-2.3.0/docs/guides/high-speed-train.md

@@ -0,0 +1,102 @@
+# How to study a high-speed train in FR2
+
+Since 2.3.0 the built-in card [`hst-fr2-28ghz`](../scenarios/hst-fr2-28ghz.md) follows the FR2
+high-speed train deployment of TR 38.854 V18.0.0 as its system-level mobility study sets it up
+(Table 6.3.8.1-1, Scenario-A, unidirectional RRHs, without DPS):
+
+| | TR 38.854 | Card |
+|---|---|---|
+| Track and RRHs | one train on one straight track, RRHs on one side, Ds 700 m, Dmin 10 m, 12 sites (Tables 5.1-1, 5.2-1, 6.3.8.1-1) | highway layout with one track, 12 sites 700 m apart at 10 m, wrap-around |
+| RRH | 15 m, 31 dBm, panel [1, 1, 8, 8, 2], one SSB beam into the boresight, the panel pointing at the track where the next site is | one sector, one SSB beam, 8 x 8 panel, azimuth 180.82 deg, zenith 90.82 deg |
+| CPE | 5 m, panel [1, 1, 4, 4, 2] of 5 dBi elements pointing to the RRHs, 350 km/h | one gain of 17.04 dB, 97.22 m/s |
+| Carrier, channel | 28 GHz, 50 MHz, 120 kHz, TR 38.901 RMa LOS only, one CPE, no inter-cell interference, DL full buffer | the same, no background load |
+| Handover, RLM | A3 3 dB, TTT 80 ms, SMTC 20 ms, measurement period 480 ms (N = 8), N310 = N311 = 2, Qout / Qin -8 / -6 dB, 600 / 300 ms | rule `{a3, off_db: 3, ttt_s: 0.08}`, TS 38.133 periods, the same RLM values |
+
+Each RRH is its own cell ("each BBU has only one RRH", TR 38.854 clause 6.3.4.1), so the train hands
+over at every RRH: about every Ds / v = 700 m / 97.2 m/s = 7.2 s.
+
+## 1. Run it in both directions
+
+All RRHs of the card point west. A train going east travels towards the serving beams (the
+"opposite direction" of the TR: train east, RRHs west), a train going west away from them ("same
+direction"). The card has one train per run and draws its direction from the seed; pointing the
+RRHs east on the same seeds gives the other direction on the same trajectories:
+
+```yaml
+# hst.yaml
+schema: 1
+scenario: hst-fr2-28ghz
+seeds: {first: 1, last: 20}
+rules:
+  - {rule: a3, off_db: 3.0, ttt_s: 0.08}
+output: results/hst-west.csv
+```
+
+and a second file `hst-east.yaml` with the RRHs pointing east (`359.18 = -atan(10 / 700)` degrees):
+
+```yaml
+schema: 1
+scenario: {base: hst-fr2-28ghz, radio: {beams: {sector_az0_deg: 359.18}}}
+seeds: {first: 1, last: 20}
+rules:
+  - {rule: a3, off_db: 3.0, ttt_s: 0.08}
+output: results/hst-east.csv
+```
+
+```bash
+handoverlab run hst.yaml
+handoverlab run hst-east.yaml
+```
+
+Scenario-B (Dmin 150 m) is an override: `layout.site_offset_m: 149.98` and the beams aimed again.
+
+## 2. What the TR describes, and what HandoverLab gives
+
+Criteria fixed before the runs (pre-registered); 40 seeds x 2 RRH orientations, 100 s measured per run
+(4000 CPE-seconds per direction), rule A3 3 dB / 80 ms. The TR's values are read from its bar charts
+(Figures 6.3.4.1.1.1-1 to -4, legacy requirements, uni-directional Scenario-A without DPS).
+
+| | Same direction: TR / HandoverLab | Opposite direction: TR / HandoverLab |
+|---|---|---|
+| Handovers per CPE-second, no DRX | 0.152 / 0.139 | 0.150 / 0.145 |
+| Time of stay in a cell [s] | 6.54 / 7.22 | 6.66 / 6.92 |
+| Ping-pong handovers [%] | 3.95 / 0.0 | 3.36 / 0.35 |
+| Mobility failures (RLF + HOF) [% of handovers and failures] | 0 / 0 | 2.1 / 0 |
+| Time below Qout or interrupted [% of time] | about 0.7 / 0.55 | 1.8 / 2.4 |
+
+| Check | Result |
+|---|---|
+| H1: received power from the serving RRH >= -50 dBm along its stretch (TR 6.3.3.1.1) | **fail as registered**: from 43 m to 700 m in front of the RRH it is -45.8 dBm or more, but within 10-42 m of the RRH it drops to -115 dBm, in the vertical null of the 8-element column (the CPE passes 10 m below the beam's tilt). The TR's statement does not cover the area under the RRH. |
+| H2: handovers per CPE-second in [0.125, 0.181] in both directions | pass (0.139 same, 0.145 opposite) |
+| H3: no failure in the same direction | pass (0 in 40 runs) |
+| H4: with DRX-40 periods, failures only in the opposite direction | **fail**: no failure in either direction. The emulation registered for it (`rx_sweep_n: 24`) did not lengthen the L3 measurement period, which in TS 38.133 Table 9.2.5.2-2 is ceil(M_meas) T_SMTC with M_meas = 24 already containing N = 8; the runs were identical to those without DRX except for the RLM windows. |
+
+Exploratory, after that finding (not pass/fail): the DRX-40 period of 1440 ms through
+`protocol.ssb_period_s: 0.06` with the RLM windows of 3.6 / 1.8 s, 20 seeds per orientation:
+still no failure in either direction. With the element back lobe removed as in the TR's mobility study
+(`radio.beams.am_db: 100`), the opposite direction spends 28.8 % of the time below Qout (same
+direction 0.6 %; TR at DRX 40: 40.3 % and about 0.7 %), but none of it ends in a radio-link failure:
+radio-link monitoring averages the linear SINR over 3.6 s, and the strong signal before the RRH keeps
+that average above Qout. With the 480 ms measurement period of no DRX, removing the back lobe raises the opposite direction's
+time below Qout from 2.4 % to 8.6 %, again without failure.
+
+What this means for a study with the card:
+
+- The geometry, link budget and handover rhythm follow the TR: one handover per RRH, about 7 s apart,
+  and the asymmetry of the two directions shows in the time below Qout.
+- The failure side of the TR's result (2.1 % without DRX, about 70 % at DRX 40 in the opposite
+  direction) is not reproduced. Two simplifications are the likely reason (not tested one by one): the CPE has one gain towards all RRHs
+  (in the TR the CPE panel faces the serving RRHs, so the source RRH falls behind the panel once the
+  CPE passes it), and radio-link monitoring is a smoothed SINR threshold, not the BLER of a hypothetical PDCCH.
+  Use the card for handover timing, rates and outage; do not read absolute failure rates from it.
+
+## 3. Limits
+
+- One gain for the CPE towards every RRH: the RRHs behind the CPE get the same gain as those in front,
+  which overstates the received power right after the CPE passes an RRH.
+- The RRH element has the back lobe of TR 38.901 Table 7.3-1 (A_m 30 dB, as TR 38.854 Table 6.1.1.1);
+  the TR's mobility study used "an antenna model without back lobe" (clause 6.3.4.1.3).
+  `radio.beams.am_db` raises A_m.
+- No DRX, DPS / SFN, multi-TRP, Doppler or fast fading, uplink timing, tunnels or cell-detection delay.
+- Radio-link monitoring on the SSB link quality with the CSI-RS evaluation periods of the TR as time
+  constants.