Part of: Duranta on COSMOS · 4G / 5G & O-RAN · Optional branch after duranta-soft
Run a Release-17 5G Non-Terrestrial Network (NTN) — a cell whose radio link goes through a satellite — entirely in software on one COSMOS server. The Duranta gNB (nr-softmodem) broadcasts the satellite's position and timing in SIB19; the Duranta software UE (nr-uesoftmodem) uses it to pre-compensate the delay and the Doppler shift; and the radio simulator (RFsim) puts a geostationary (GEO) or low-earth-orbit (LEO) channel between them. Attach the UE, ping through a half-second satellite round trip, and measure what TCP, UDP and HARQ make of it, next to a terrestrial baseline on the same cell.
A terrestrial cell assumes the UE is a few kilometres away: the round trip is microseconds, the gNB measures the timing advance during random access, and a lost transport block is retransmitted a few milliseconds later. A GEO satellite 35,786 km up makes the radio round trip about 477 ms; a LEO satellite at 600 km is much closer but moves at 7.6 km/s, so the delay drifts by tens of microseconds per second and the carrier arrives tens of kilohertz off. This tutorial runs four scenarios on one 5 MHz cell — terrestrial, GEO with HARQ feedback disabled, GEO with 32 HARQ processes, and a LEO pass — so you can watch the Release-17 mechanisms cope with each. It needs no radio and no radio reservation: the satellite is simulated.
Concepts
- Transparent payload — the satellite is a bent pipe that only frequency-converts and amplifies; the gNB stays on the ground behind a gateway. The gateway–satellite hop is the feeder link, the satellite–UE hop the service link. It is the only NTN architecture Release 17 standardises, and the one simulated here.
- SIB19 — a system information block carrying
ntn-Config-r17: the satellite's position and velocity (its ephemeris), the common timing advance ta-Common and its drift, the scheduling offset Koffset, and how long the UE may extrapolate before re-reading it.- Koffset — an offset added to every "N slots after the grant" timing relation, so the UE's uplink lands after the round trip. It must be at least the round trip: 478 ms for this GEO cell, 40 ms for the LEO cell.
- HARQ — per-process stop-and-wait retransmission. Release 17 allows 32 processes and lets the network disable HARQ feedback so a process is free immediately, leaving recovery to RLC.
- RFsim — OAI's radio simulator: the gNB is a TCP server, the UE connects to it, and the channel (a fixed delay for GEO, a moving delay and Doppler for LEO) is applied in between.
ntn-Config-r17 in the cell configuration, SIB19 at the DU, longer timers, and the HARQ options (disable_harq, num_dlharq / num_ulharq).position0), the RFsim satellite delay, and for LEO the channel model plus the drift and Doppler options.Everything runs on one server:
| Part | Role | Here |
|---|---|---|
| Ground segment | schedules as if the UE were far away (Koffset) and announces the satellite (SIB19) | nr-softmodem, unit duranta-ntn-gnb, RFsim server on TCP port 4043 |
| Space segment | applies the satellite channel: the downlink leg on the UE side, the uplink leg on the gNB side | RFsim: a fixed prop_delay (238.74 ms each way) for GEO, the SAT_LEO_TRANS model for LEO (600 km circular orbit, delay and Doppler recomputed continuously) |
| User terminal | knows its own position, corrects its timing and frequency before transmitting | nr-uesoftmodem, unit duranta-ntn-ue, tunnel oaitun_ue1 |
| Core | unchanged: NTN is entirely a RAN feature | OAI CN5G containers, with oai-ext-dn as the data network and iperf3 server |
The one carrier for all four scenarios is band n254 (an NTN S-band, FDD), 25 PRB = 5 MHz, 15 kHz subcarrier spacing, with the modulation capped at MCS 9 by the configuration files that ship in Duranta's source tree. Nothing radiates.
RFsim is not real time. The gNB and UE exchange samples as fast as the CPU allows: this light 5 MHz cell runs several times faster than real time, and the LEO channel model is expensive enough to run slower than real time. Everything inside the RAN — frames, HARQ timers, Koffset, the satellite delay — runs on this simulated clock; ping and iperf3 run on the wall clock. The tutorial measures the ratio for every measurement window: the gNB prints Frame.Slot <f>.0 every 128 frames (1.28 s of simulated time), and counting those lines across a window gives scale = simulated s / wall s. Then:
What this does not fix: TCP's congestion control runs in the host kernel on the wall clock, so in the GEO scenario TCP sees a round trip of about 90 ms instead of about 550 ms. The TCP-versus-UDP gap you measure is therefore smaller than over a real GEO link.
| Domains | any domain - the node checks below decide |
| Nodes | 1, named in OMF_NODES |
| On the console | python3, ansible-playbook, ssh, tar |
cosmos-tutorial check duranta-ntn verifies, on each node:
Not in the package - you provide:
You will also need:
LD_LIBRARY_PATH, the dynamic AMF address, the UE's carrier arguments;No radio, no radio reservation and no licence are involved. The LEO channel model is CPU-heavy, so use a server-class node.
On the console of your domain, name your node and ask whether the tutorial can run. The check is read-only.
export OMF_NODES="<node>"
cosmos-tutorial check duranta-ntn
It ends with RUNNABLE or NOT RUNNABLE and the reasons: the Duranta gNB and UE builds, the upstream NTN configurations in the Duranta tree, the OAI CN5G compose files, Docker and the subscriber SQL, AVX-512, and no other gNB or soft UE running. If the image is missing, load it first:
omf load -i duranta.ndz -t <node> -r 0 -o 2400 -b 600
omf tell -a on -t <node>
export OMF_NODES=<node>
cosmos-tutorial check duranta-ntn
cosmos-tutorial run duranta-ntn # ansible
cosmos-tutorial run duranta-ntn --mode manual # manual
cosmos-tutorial jupyter duranta-ntn # jupyter
cosmos-tutorial run duranta-ntn --mode parity # parity
cosmos-tutorial run duranta-ntn --mode teardown # teardown
The tutorial ships the same experiment three ways. All three copy the same two node-side helpers to the node (duranta-ntn_mkconf.py, which renders the configurations, and duranta-ntn_node.sh, which starts, measures and stops), read one parameter file, and write the same JSON result into ~/cosmos-runs/duranta-ntn/<UTC>-<mode>/ on the console. One run of all four scenarios takes about 10 minutes.
The playbook runs a preflight check, copies the helpers, starts the core and provisions the subscriber, then for each scenario renders the configurations, starts the gNB and the UE as named systemd units, measures, and stops them. It ends with the result table.
The manual mode runs the commands below for you, one scenario at a time. They are shown for GEO; the other scenarios differ only where noted. Log in to the node first and copy the two helpers there from $(cosmos-tutorial which duranta-ntn) on the console:
ssh root@<node>
mkdir -p /root/duranta-ntn && cd /root/duranta-ntn # duranta-ntn_mkconf.py + duranta-ntn_node.sh go here
Step 1 — Start the core. Exactly as in duranta-soft: the core is NTN-agnostic.
cd /opt/oai-cn5g/oai-cn5g-fed/docker-compose
docker compose -f docker-compose-basic-nrf.yaml up -d
docker exec -i mysql sh -c 'mysql -uroot -p"$MYSQL_ROOT_PASSWORD" oai_db' < /root/duranta/provision.sql
docker ps --format '{{.Status}}' | grep -c healthy # at least 8
Step 2 — Render the NTN configurations from the image's own files. Duranta's source tree ships a GEO and a LEO gNB configuration for band n254. They carry a test PLMN and the addresses of their CI network, so the renderer copies them with only the PLMN, the AMF address and the gNB's N2/N3 bind address changed (the bind address is the server's leg of the core's Docker bridge, found from the AMF's subnet), and builds the UE configuration from the image's own test SIM plus the UE position and the RFsim channel. diff shows that nothing else changed.
cd /root/duranta-ntn
AMF=$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' oai-amf)
NG=$(ip -4 -o addr show | awk -v a="${AMF%.*}." '$4 ~ "^"a {split($4,x,"/"); print x[1]; exit}')
python3 duranta-ntn_mkconf.py --scenario geo --out-dir conf --amf $AMF --ng-addr $NG
diff /opt/duranta/ci-scripts/conf_files/gnb.sa.band254.u0.25prb.rfsim.ntn.conf conf/gnb-geo.conf
The NTN part of the gNB file is what turns an ordinary cell into a satellite cell:
disable_harq = 1; # Rel-17 downlinkHARQ-FeedbackDisabled: no HARQ ACK/NACK, no retransmissions
du_sibs = [19]; # the DU broadcasts SIB19
ntn-UlSyncValidityDuration-r17 = 240; # s; re-read SIB19 at least this often
cellSpecificKoffset_r17 = 478; # >= the 477.5 ms round trip
ta-Common-r17 = 58629666; # x 4.072 ns = 238.74 ms
positionZ-r17 = 32433846; # x 1.3 m = 42,164 km from the Earth's centre: GEO
TIMERS : { sr_ProhibitTimer_v1700 = 512; t300 = 2000; t301 = 2000; t319 = 2000; ... };
MACRLCs = ({ ... dl_max_mcs = 9; ul_max_mcs = 9; });
rfsimulator = ({ ... prop_delay = 238.74; }); # the UL leg of the simulated satellite (the DL leg is set on the UE)
and the UE file adds position0 = { x = 0.0; y = 0.0; z = 6377900.0; } (ECEF, metres: on the surface, under the satellite) and prop_delay = 238.74 for its downlink leg.
Other scenarios: --scenario tn drops the *-r17 lines, du_sibs and disable_harq and sets prop_delay = 0 — the same cell on the ground. geo-harq32 replaces disable_harq = 1 with num_dlharq = 32; num_ulharq = 32;. leo uses the LEO file (Koffset 40, ta-Common 18.84 ms, ta-CommonDrift −46 µs/s, a moving ephemeris, 32 HARQ processes, the SAT_LEO_TRANS channel model) and gives the UE the same channel model.
Step 3 — Start the gNB. It runs as a named systemd unit with LD_LIBRARY_PATH set, because the build was relocated to /opt/duranta.
B=/opt/duranta/cmake_targets/ran_build/build; mkdir -p /tmp/duranta-ntn/geo
systemd-run --unit=duranta-ntn-gnb --collect --working-directory=$B --setenv=LD_LIBRARY_PATH=$B \
bash -c "exec $B/nr-softmodem -O /root/duranta-ntn/conf/gnb-geo.conf --rfsim > /tmp/duranta-ntn/geo/gnb.log 2>&1"
grep -aE 'activate SIB19|is in service|Command line parameters for OAI UE' /tmp/duranta-ntn/geo/gnb.log
Step 4 — Start the UE and watch it read SIB19. The UE takes its carrier arguments from the gNB's log line, as in duranta-soft.
ARGS=$(grep -a 'Command line parameters for OAI UE' /tmp/duranta-ntn/geo/gnb.log | head -1 | sed -E 's/.*OAI UE: *//; s/\x1b\[[0-9;]*m//g')
systemd-run --unit=duranta-ntn-ue --collect --working-directory=$B --setenv=LD_LIBRARY_PATH=$B \
bash -c "exec $B/nr-uesoftmodem -O /root/duranta-ntn/conf/ue-geo.conf --rfsim $ARGS > /tmp/duranta-ntn/geo/ue.log 2>&1"
until ip -br addr show oaitun_ue1 2>/dev/null | grep -q 192.168.100; do sleep 0.25; done
grep -aE 'Found SIB19|k_offset|TA_COMMAND|PDU Session Establishment Accept' /tmp/duranta-ntn/geo/ue.log
For LEO, the UE needs three things SIB19 cannot give it before it has synchronised, so they go on its command line (ntn_leo_ue_args, exactly what upstream CI passes):
... $ARGS --time-sync-I 0.1 --ntn-initial-time-drift -46 --initial-fo 57340 --cont-fo-comp 3
| Option | What it does |
|---|---|
--ntn-initial-time-drift -46 |
the downlink timing drift in µs/s, used during initial sync before SIB19 is read |
--initial-fo 57340 |
the downlink frequency offset in Hz to remove up front: the Doppler at the start of the pass |
--cont-fo-comp 3 |
continuous frequency-offset estimation, treated as Doppler for the uplink pre-compensation without folding the residual downlink offset into it |
--time-sync-I 0.1 |
the integral gain of the UE's time-tracking loop, needed to follow a delay that drifts continuously |
Step 5 — Measure. Every window is bracketed by the gNB's frame counter, so each has its own time scale. -W 5 on the ping, because a GEO reply takes about 0.5 s of simulated time. The receiver line of each iperf3 run is the measurement.
DN=$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' oai-ext-dn)
docker exec -d oai-ext-dn iperf3 -s -p 5201
ping -I oaitun_ue1 -c 10 -W 5 $DN
iperf3 -c $DN -p 5201 -B 192.168.100.2 -t 10 -i 0 -R # TCP DL
iperf3 -c $DN -p 5201 -B 192.168.100.2 -t 10 -i 0 -u -b 40M -R # UDP DL, offered above capacity
duranta-ntn_node.sh measure geo 10 10 5201 40M runs the full set (TCP and UDP, both directions) with the time-scale bracketing. Use the UE's actual address after -B if it is not 192.168.100.2.
Step 6 — Stop, and move to the next scenario.
systemctl stop duranta-ntn-ue duranta-ntn-gnb
The notebook runs on the console and drives the node over SSH. It performs the same steps and adds RTT and throughput plots per scenario. It can also be run non-interactively with papermill, which writes an executed copy to a new file.
The parity mode runs Ansible, manual and Jupyter one after the other on the same node and compares their results. In every mode and scenario the cell must be in service and the UE attached, and the NTN scenarios must show SIB19 on both sides. The simulated ping RTT must sit in a band set by geometry — GEO at least 477 ms (two 238.74 ms legs), LEO 40–400 ms, terrestrial at most 200 ms — and the modes must agree within 40 %. The simulated UDP downlink must be above a floor per scenario and the modes must agree within 80 % (RFsim is CPU-bound and the modes run minutes apart), except GEO with 32 HARQ processes, which must only stay below 1 Mbit/s because its rate is erratic by nature. The harness tears down on every exit.
After Step 3, the cell is an NTN cell and is in service. --CO -873500000 is the FDD uplink offset (uplink at 1614.9 MHz); the UE needs it because n254 is not a band from which it can derive the uplink on its own:
[NR_MAC] Command line parameters for OAI UE: -C 2488400000 --CO -873500000 -r 25 --numerology 0 --band 254 --ssb 60
[GNB_APP] activate SIB19 at DU
[NR_RRC] cell PLMN 001.01 Cell ID 12345678 is in service
After Step 4, the UE found SIB19 before random access and set its timing advance to 3,667,039 samples — 477.5 ms at 7.68 Msample/s, the whole round trip, computed from ta-Common plus its own position. The gNB's closed-loop TA_COMMAND 30 afterwards is one step from the neutral value 31: the open-loop estimate was right to within a fraction of a symbol.
[NR_RRC] Found SIB19
[PHY] k_offset: 478ms, N_Common_Ta: 238.740000ms, drift: 0.000000µs/s, variant: 0.000000µs/s², timing_advance_ntn: 3667039 samples, DL Doppler shift: 0.000000kHz, UL Doppler shift: 0.000000kHz
[NR_MAC] [791.0] Received TA_COMMAND 30 TAGID 0 CC_id 0
[NAS] Received PDU Session Establishment Accept, UE IPv4: 192.168.100.2
In LEO, the UE log shows the moving satellite, and successive NTN Config Rxd lines carry a shrinking N_Common_Ta as RFsim updates SIB19 the way an operator's ephemeris feed would:
[HW] Downlink delay 18.859594 ms, Doppler shift SAT->UE 57.341449 kHz
[PHY] k_offset: 40ms, N_Common_Ta: 18.826412ms, drift: -46.086200µs/s, ... DL Doppler shift: 57.341116kHz, UL Doppler shift: 37.211877kHz
Typical values on the simulated clock (2× Intel Xeon Gold 6126):
| terrestrial | LEO (600 km) | GEO, HARQ feedback off | GEO, 32 HARQ | |
|---|---|---|---|---|
| ping RTT, simulated ms | 45–53 | 120–160 | 520–565 | 1005–1050 |
| UDP downlink, simulated Mbit/s | 3.7–3.8 | 2.4–2.55 | 3.75–3.83 | 0.03–0.26 |
| time scale during ping (simulated s per wall s) | about 8 | 0.7–0.85 | about 6 | about 6 |
A parity run ends with PARITY: PASS:
=== duranta-ntn parity ===
mode tn.ping_rtt_sim_ms tn.udp_dl_sim_mbps geo.ping_rtt_sim_ms geo.udp_dl_sim_mbps geo_harq32.ping_rtt_sim_ms geo_harq32.udp_dl_sim_mbps leo.ping_rtt_sim_ms leo.udp_dl_sim_mbps
ansible 44.5 3.81 542.3 3.78 1016.6 0.05 158.4 2.44
manual 52.1 3.75 536.5 3.77 1033.1 0.26 120.3 2.51
jupyter 52.8 3.73 521.7 3.8 1007.1 0.05 119.3 2.45
...
geo.ping_rtt_sim_ms spread max/min = 1.04 (tol 1.40)
leo.ping_rtt_sim_ms spread max/min = 1.33 (tol 1.40)
PARITY: PASS (same experiment in all modes; all checks green)
(Real output from 2026-10-22, 2× Intel Xeon Gold 6126.)
Change any of these with cosmos-tutorial run duranta-ntn --params my.yml. An unknown key or a wrong type is refused. cosmos-tutorial params duranta-ntn prints the file.
| Key | Default | Meaning |
|---|---|---|
duranta_build_dir |
/opt/duranta/cmake_targets/ran_build/build |
Relocated build: every launch needs LD_LIBRARY_PATH= (set by the node helper). |
duranta_core_dir |
/opt/oai-cn5g/oai-cn5g-fed/docker-compose |
The core the image ships (already running on a Duranta node is fine: up -d is idempotent). |
duranta_core_compose |
docker-compose-basic-nrf.yaml |
|
duranta_provision_sql |
/root/duranta/provision.sql |
|
ntn_node_dir |
ntn |
Both live in the run's node dir /var/tmp/cosmos/, never in /root/duranta: this tutorial never edits the image's own configs, and a run never reads the previous run's files. |
ntn_node_log_dir |
raw |
the per-run raw logs fetched to the console; relative = in the run's node dir |
ntn_ue_tun |
oaitun_ue1 |
|
duranta_plmn |
00101 |
|
duranta_imsi |
001010123456780 |
|
ntn_scenarios |
tn,geo,geo-harq32,leo |
Run in this order. |
ntn_leo_ue_args |
--time-sync-I 0.1 --ntn-initial-time-drift -46 --initial-fo 57340 --cont-fo-comp 3 |
Extra nr-uesoftmodem arguments for the LEO run (exactly what upstream CI passes in 2026.w39, ci-scripts/yaml_files/5g_rfsimulator_ntn_leo/docker-compose.yaml). |
ntn_ping_count |
10 |
|
ntn_iperf_secs |
10 |
|
ntn_iperf_port |
5201 |
|
ntn_udp_rate_tn |
40M |
UDP offered load (wall clock). |
ntn_udp_rate_geo |
40M |
|
ntn_udp_rate_geo_harq32 |
3M |
|
ntn_udp_rate_leo |
6M |
|
duranta_core_timeout_s |
150 |
|
ntn_gnb_timeout_s |
90 |
|
ntn_attach_timeout_s |
180 |
To change a parameter, put only the keys you change in a file of your own and pass it to any mode. A key the tutorial does not have, or a value of the wrong type, is refused before anything starts:
cat > my.yml <<'EOF'
ntn_scenarios: "tn,geo"
EOF
cosmos-tutorial run duranta-ntn --params my.yml
To change the tutorial itself, cosmos-tutorial copy duranta-ntn puts an editable copy in the current directory, which then takes precedence over the installed one.
ntn-Config-r17 and Koffset scheduling at the gNB; HARQ feedback disabling and 32 HARQ processes; at the UE, SIB19 reception, timing advance from SIB19 (or autonomously, --autonomous-ta, not used here), and downlink Doppler compensation with uplink pre-compensation; and in RFsim, the GEO delay and the transparent and regenerative LEO models. The image also carries sample NTN configurations for bands n255, n256 and n512 (FR2 NTN), not used here.| Symptom | Cause | Fix |
|---|---|---|
A GEO UE (geo or geo-harq32) logs thousands of synch Failed, never Cell Detected, while the gNB is in service |
on images older than duranta-w44 the UE lacks the COSMOS initial-sync patch: the 238.74 ms GEO delay can place the SSB across every two-frame capture, so in about 1 start phase in 20 the UE never syncs (tn and leo are not affected) |
use the current duranta.ndz; on older releases the tutorial's own guard covers it: it restarts the UE after 400 failed sync attempts, up to twice, and keeps the failed start's log as ue-nosync-<n>.log (tune with NTN_SYNC_MAX_FAILS / NTN_SYNC_RESTARTS in the node environment) |
A GEO UE logs synch Failed for minutes and the gNB's frame counter barely moves |
RFsim fell to a crawl (0.08× real time instead of about 6×) | stop the scenario (duranta-ntn_node.sh stop) and start it again |
| GEO ping shows 100 % loss but the UE is attached | ping -W 2 gives up before a ~0.5 s (simulated) reply arrives when RFsim runs near real time |
-W 5 or more |
The LEO UE never finds the cell (no Found SIB19, no RRC) |
it started without the drift and Doppler options | add ntn_leo_ue_args (Step 4) |
| The UE asserts at start about the frequency range | the carrier arguments are missing | pass the gNB's Command line parameters for OAI UE line, including --CO |
iperf3 -u uplink never returns in GEO with 32 HARQ or in LEO |
the offered UDP load fills the UE's buffers and the iperf3 control messages queue behind it |
offer less (the tutorial uses 3M and 6M) and allow a timeout of at least the test plus 60 s |
iperf3: error … Connection refused or unable to receive control message after an aborted GEO test |
the server in oai-ext-dn exited or wedged |
restart it (docker exec -d oai-ext-dn iperf3 -s -p 5201); the measure step restarts it and retries once |
Random access failed, Msg3 never decoded after you changed the delay |
the delay the UE assumes differs from the channel's by more than the RAR timing advance can correct (upstream issue #513 makes this worse) | keep ta-Common, the UE position and prop_delay consistent; do not change one alone |
The disable_harq cell stays at one MCS |
upstream issue #123: link adaptation is inoperative with HARQ feedback off | expected; this cell caps MCS at 9 and is noiseless anyway |
| Wall-clock numbers look too good for a satellite | RFsim runs faster than real time | use the simulated-clock values (…_sim_… in the result) |
| A stale unit holds RFsim port 4043 and the next scenario's gNB will not start | a previous run did not stop its units | systemctl stop duranta-ntn-ue duranta-ntn-gnb, or run the teardown |
After any mode, run the teardown from the console. It stops the two named units and the iperf3 server; the core is stopped only when you ask for it:
OMF_NODES=<node> cosmos-tutorial run duranta-ntn --mode teardown
After the manual steps, systemctl stop duranta-ntn-ue duranta-ntn-gnb on the node stops exactly the tutorial's two processes and nothing else on the host, and docker compose -f /opt/oai-cn5g/oai-cn5g-fed/docker-compose/docker-compose-basic-nrf.yaml down stops the core. Then power the node off from the console:
omf tell -a offh -t <node>
Package cosmos-experiments-duranta 0.1.0-25 - on every console it is released to (cosmos-tutorial list shows the installed version). The code is installed on the console in /usr/share/cosmos-experiments/duranta-ntn/. To change anything, cosmos-tutorial copy duranta-ntn puts an editable copy in the current directory, and cosmos-tutorial run duranta-ntn then runs that copy instead of the installed one (cosmos-tutorial which duranta-ntn shows which will run). Repository (GitLab account needed, not needed to run or change it): packages/cosmos-experiments-duranta/usr/share/cosmos-experiments/duranta-ntn.
Last verified 2026-11-01 on duranta-w44-20261101 (Duranta 2026.w44, which carries the UE sync fix), with the tutorial sources released in cosmos-experiments-duranta 0.1.0-20, cold start (all devices off), on osc (2× Intel Xeon Gold 6126): three-mode parity PASS, all scenarios. Earlier: three-mode parity PASS on 2026-10-28 from the installed cosmos-experiments-duranta package, with 30 of 30 GEO attaches in a stress run, and on 2026-10-22, 2026-10-10 and 2026-10-08. Results by build are on Duranta performance by build.
References: Duranta NTN guide · RFsimulator · Duranta source (issues #123, #513) · OAI RAN documentation · 3GPP Release 17: TS 38.300 §16.14 (NR NTN), TS 38.331 (SIB19, NTN-Config-r17), TS 38.213 §4.2 (timing advance, Koffset), TS 38.211 §4.3.1, TS 38.321 §5.3.2 (HARQ), TS 38.101-5 (satellite UE radio), TR 38.811 and TR 38.821 · RFC 3135 (performance-enhancing proxies) · on this wiki: Duranta on COSMOS · duranta-soft · 5G SA fundamentals · OAI CN5G.
Author(s): COSMOS team · Package: cosmos-experiments-duranta (cosmos-tutorial run duranta-ntn) · Tags: duranta, oai, ntn, satellite, geo, leo, sib19, rfsim, 5g, rel-17