Comms RCCA/CAPA (Network Engineering) Flashcards

Question

What is the recommended PLL bandwidth after achieving near-zero error?

Answer 1

About 0.5–1% of symbol rate

Answer 2

settle time ≈ a few / (2π × bandwidth)

Answer 3

±20 kHz ## Footnote These defaults work for typical LEO passes with TCXO-class space clocks.

Answer 4

Residual frequency offset and cycle-slip count

Answer 5

Capture too small or FLL too narrow

Answer 6

Stage A (coarse) follows Doppler ramps; Stage B (fine) reduces noise/EVM

Answer 7

< 25–40% of your AFC capture

Answer 8

5–10% of PLL bandwidth

Answer 9

Zero at mid-elevation; rare at AOS/LOS

Answer 10

Comfortably < preamble length

Answer 11

≥ 2× worst-case Δf(_res) at AOS

Answer 12

Update TLEs daily (≤ 24 h old)

Answer 13

Push to 6–12 h cadence or switch to high-rate ephemerides

Answer 14

Within ±10 ms

Answer 15

Single, version-locked SGP4 implementation

Answer 16

GS programs its LO schedule from prediction; SDR AFC cleans residual

Answer 17

600–800 Hz @ UHF

Answer 18

Widen capture or increase TLE cadence

Answer 19

Increase FLL BW or smooth steps

Answer 20

residuals, cycle-slip counters, elevation, profile hash

Answer 21

Mixed time scales (GPS vs UTC) cause time shifts

Answer 22

Pick one owner per link direction

Answer 23

±80–100 kHz

Answer 24

Loop hunts

Answer 25

To avoid jerk that loops have to chase

Answer 26

Apply a static PPM correction

Answer 27

±8–10 kHz in ≤ 300 ms

Answer 28

1. Match/VSWR proxy 2. PA behavior 3. Delivered EIRP proxy ## Footnote Match/VSWR proxy involves forward vs reflected power or |Γ|/RL if a reflectometer is available. PA behavior includes drain current/voltage and temperature. Delivered EIRP proxy is based on ground-measured SNR/Eb/N0 at a fixed elevation.

Answer 29

RL = -20 log10(|Γ|) ## Footnote |Γ| is calculated as sqrt(P_refl/P_fwd) after applying coupler/directivity calibration.

Answer 30

* Good: RL ≥ 14 dB (VSWR ≤ 1.5:1) * Caution: RL 10–14 dB (VSWR ≈ 1.9–1.5) * Action: RL ≤ 9.5 dB (VSWR ≥ 2:1) * Critical: RL ≤ 6 dB (VSWR ≥ 3:1) ## Footnote Investigate if RL is ≤ 9.5 dB as the risk of foldback rises quickly.

Answer 31

To compute d(RL)/dT and d(VSWR)/dT per vehicle ## Footnote A rising slope indicates detuning with temperature.

Answer 32

Eb/N0 (or SNR) normalized for range and system noise ## Footnote This helps track a per-sat normalized EIRP index over time.

Answer 33

Match degradation rather than propagation ## Footnote It is essential to normalize for range and system noise.

Answer 34

* VNA S-parameter sweep * Cable/connector health checks * Temperature detuning characterization ## Footnote These methods include measuring S11 across frequency and temperature, TDR for impedance steps, and checking S11(T) in TVAC.

Answer 35

Rising PA temperature → PA current dips or output detector drops → ground Eb/N0 falls without extra path loss ## Footnote This indicates the PA's VSWR/thermal protection engaging.

Answer 36

Back-off TX power (3–6 dB) or switch to lower-crest modulation ## Footnote This helps mitigate the immediate issue while monitoring temperature.

Answer 37

* |Γ| = sqrt(P_refl/P_fwd) * RL = -20 log10(|Γ|) dB * VSWR = (1 + |Γ|) / (1 - |Γ|) ## Footnote These equations are essential for computing the respective values.

Answer 38

* RL = 14 dB ↔ VSWR ≈ 1.5:1 (good) * RL = 9.5 dB ↔ VSWR ≈ 2.0:1 (watch) * RL = 6.0 dB ↔ VSWR ≈ 3.0:1 (bad; expect foldback) ## Footnote These landmarks help identify the status of RF matching.

Answer 39

* Swap to C0G/NP0 RF caps * Choose wider-band or temperature-stable antenna elements * Add strain relief and locking torque on RF connectors ## Footnote These changes help improve reliability and performance.

Answer 40

* Add telemetry for P_fwd, P_refl, or PA current + output detector * Compute and log RL/VSWR and dRL/dT * Set alerts at RL ≤ 10 dB or VSWR ≥ 2:1 * Record Eb/N0 at fixed elevation per pass * TDR/VNA every harness * Create a one-page baseline ## Footnote This checklist ensures all critical parameters are monitored effectively.

Answer 41

True ## Footnote This method helps validate the performance of the RF chain.

Answer 42

2–3 dB ## Footnote This is measured during the VNA S-parameter sweep.

Answer 43

Z_{target}(omega) le dfrac{Delta V_{max}}{Delta I_{PA}} ## Footnote Typical target is (Z(omega) lesssim 10–50~mΩ) across the PA’s envelope bandwidth.

Answer 44

3–6 dB below (P_{1dB}) ## Footnote Higher back-off may be needed if the crest factor is high.

Answer 45

UVLO + 5–10% guard above worst droop + temp/aging effects ## Footnote This ensures reliable operation during voltage dips.

Answer 46

MOSFET, power resistor, scope, current probe or shunt, low-inductance probes ## Footnote These tools allow for measuring rail impedance effectively.

Answer 47

Place pulse load as close as possible to PA supply pins ## Footnote This minimizes inductance in the measurement.

Answer 48

Inject a small AC current into the rail and measure V/I from 1 kHz to a few MHz ## Footnote This provides a full Z(ω) Bode plot.

Answer 49

Fraction of time the envelope is above a threshold ## Footnote This is crucial for understanding rail stress.

Answer 50

Crest factor (dB) = 10 log_{10} (P_{peak}/P_{avg}) ## Footnote It quantifies the peak-to-average power ratio.

Answer 51

To get AM/AM, AM/PM, EVM curves ## Footnote This helps in optimizing the PA's performance.

Answer 52

* Regulator UVLO * Radio/PA UVLO * System brownout reset ## Footnote These ensure the system operates reliably under varying conditions.

Answer 53

Increase back-off (3–6 dB for QPSK) ## Footnote This indicates the PA is in compression.

Answer 54

Add bulk near PA, reduce ESL, damp resonance ## Footnote This helps to stabilize the rail during high demand.

Answer 55

Measure Z(ω) at PA pins (step-load now; FRA when available) ## Footnote This is crucial for understanding rail performance.

Answer 56

C_{bulk} gtrsim dfrac{Delta I cdot T_{on}}{Delta V} ## Footnote This ensures nearby bulk caps can supply the needed energy.

Answer 57

Auto back-off TX or switch to lower-crest mode ## Footnote This helps maintain reliable operation as voltage approaches guardbands.

Answer 58

To provide design strategies for improving rail performance ## Footnote These strategies help mitigate issues related to rail impedance and TX bursts.

Answer 59

EVM goes down, and packet-loss bursts disappear ## Footnote This highlights the importance of maintaining stable rail voltage.

Answer 60

Carrier over noise plus interference

Answer 61

C/(N+I), not idealized C/N

Answer 62

* Measured NF and equivalent noise temperature * Measured preselector passband * Interference inventory * Linearity/IP3 limits * C/(N+I) vs elevation plot and I/N penalty

Answer 63

Y-factor with a calibrated noise source

Answer 64

* Calibrated noise diode * Power meter/SDR with known RBW * Attenuators

Answer 65

T_e = (T_hot - Y * T_cold) / (Y - 1)

Answer 66

Noise Figure

Answer 67

* VNA/Tracking generator * Injection with the receiver

Answer 68

To quantify passband for noise bandwidth calculation and out-of-band interference

Answer 69

* Run span ≥ 5–10× your passband * Log for 24 hours to catch diurnals

Answer 70

P_dBW/Hz = P_dBm - 30 - 10log10(RBW Hz)

Answer 71

To measure linearity and identify where distortion occurs in the front-end

Answer 72

To measure the degradation of SNR/BER due to a strong single-tone blocker

Answer 73

NF ≲ 1–2 dB

Answer 74

Combine C/N and C/I using linear equations and convert back to dB-Hz

Answer 75

Δ_I = 10log10(1 + I₀/N₀) dB

Answer 76

* Move LNA to the mast * Cut pre-LNA loss * Pick a lower-NF LNA

Answer 77

Frequency, peak/average power, duty cycle, occupancy, and bearing/elevation

Answer 78

* Measure NF * Sweep S21 of the preselector * 24-h waterfall log * Two-tone IP3 and blocking tests * Build a C/(N+I) calculator * Update the link budget

Answer 79

The site penalty compared to the ideal C/N curve

Answer 80

P_dBW/Hz = P_dBm - 30 - 10log10(RBW)

Answer 81

Treat every SDR setting like code: declare it, hash it, stamp it into every log/packet, and block anything that isn’t an approved profile.

Answer 82

* Rx & Tx parameters * Front-end/DSP settings * Ops settings

Answer 83

* center_freq * if_bandwidth * sample_rate * decimation * gain_plan * rrc.rolloff * rrc.taps * samples_per_symbol * timing_loop.bandwidth_hz * timing_loop.type * pll.bandwidth_hz * pll.type * afc.capture_hz * agc.mode * agc.target_dBFS * llr.scale * fec.code * interleaver.depth * framer * iq_centering * clock_ref * ppm_trim

Answer 84

To keep the whole config in a text profile and maintain consistency across different versions.

Answer 85

* meta.name * meta.mission * meta.version * meta.created_utc * rf settings * gain settings * agc settings * rrc settings * timing loop settings * carrier settings * fec settings * arq settings

Answer 86

A stable ID computed from the TOML configuration, such as a SHA-256 hash.

Answer 87

The SDR loads a profile, derives the profile_id, and writes it to telemetry lines, IQ filenames, and logs.

Answer 88

To ensure that the SDR operates only with approved configurations and rejects any unauthorized changes.

Answer 89

* Golden I/Q replay * Cross-site parity checks * Dashboards for pass metrics

Answer 90

To prove parity and identify RF/site issues versus config drift.

Answer 91

SELECT DISTINCT profile_id, meta.name, meta.version FROM passes WHERE utc > now()-30d

Answer 92

* Runtime assertions * PPM calibration SOP * Profile watermarking

Answer 93

[code deploys]

Answer 94

* Freeze a schema * Create profiles for each active waveform/mode * Add a SHA generator and telemetry stamping * Lock SDR loader to run only approved profiles * Stand up golden replay and nightly CI * Add a Grafana panel for PER vs elevation

Answer 95

To ensure that each ground station produces identical bytes and KPIs within tolerances.

Answer 96

Packet Error Rate

Answer 97

It indicates RF/site issues, not config.

Answer 98

To prevent unapproved changes unless an override is explicitly supplied.

Answer 99

The exact “bit plumbing” ## Footnote This refers to understanding the framing, scrambler, CRC, and MAP/VC usage for effective data recovery.

Answer 100

* Cooperative path * Black-box path

Answer 101

Fastest discovery when you control the radio

Answer 102

Command 'clean beacons' (no encryption, no compression)

Answer 103

* Frame length * Standard (CCSDS TM/TC variant) * ASM/sync marker ID * Randomizer enable + polynomial/seed * FECF (CRC) on/off + polynomial * MAP enabled? VCIDs in use?

Answer 104

* Randomizer OFF/ON * CRC OFF/ON (if optional) * Different VCIDs

Answer 105

* A minute of raw bitstream for each mode * Exact parser settings (framer + scrambler + CRC)

Answer 106

Clean symbol decisions (post-FEC) and a stable bit clock

Answer 107

Find the frame Sync/ASM and frame length

Answer 108

Sliding correlation & histograms

Answer 109

0x1ACFFC1D

Answer 110

The correct bit polarity hypothesis

Answer 111

To remove randomization that whitens payload and hides structure

Answer 112

Bit entropy and run-length distribution of the payload region

Answer 113

A polynomial/seed that consistently de-whitens the payload

Answer 114

Validates frame integrity and locks the exact header/payload boundaries

Answer 115

They might be CRC/FECF

Answer 116

One CRC definition matches all frames when computed over the same bit/byte order

Answer 117

* SCID * VCID * Sequence counters * MAP

Answer 118

Presence of multiple VCIDs in a pass

Answer 119

To ensure the parser consumes a continuous bitstream with zero desync

Answer 120

Ensure correct assumptions about NRZ-L vs NRZ-M and differential encoding

Answer 121

* GNU Radio / gr-ccsds * crcany / pycrc * LFSR/PN finders * Kaitai Struct

Answer 122

To confirm that all steps in the process have been completed successfully

Answer 123

[2–5 minutes] of clean I/Q at high elevation

Answer 124

To identify the ARQ flavor and recover window size/timers.

Answer 125

* Cooperative * Passive * Black-box fallback

Answer 126

RTT = t_rx_echo_at_GS − t_tx_probe_at_GS

Answer 127

To reduce RF confounds.

Answer 128

Bandwidth Delay Product

Answer 129

BDP = rate × RTT

Answer 130

* ~1 outstanding frames * 1:1 ack semantics * Retransmit next frame after timeout * No duplicate ACK bursts

Answer 131

GBN retransmits k, k+1, ... on loss; SR retransmits only missing seq.

Answer 132

* Plot outstanding frames vs time * Inspect ACK payloads * Observe retransmit behavior on dropped frames

Answer 133

Count max outstanding frames before a stall or ACK catch-up.

Answer 134

Retransmission Timeout

Answer 135

RTO ≈ t(first retransmit of k) − t(first tx of k)

Answer 136

Measure t(NACK for k) − t(first gap at k).

Answer 137

W ≥ 2·BDP in frames

Answer 138

You are window-limited, not RF-limited.

Answer 139

Measure RTT_min/med/95th via passive ACK correlation.

Answer 140

That queues are not in your path.

Answer 141

Indicates timer/window problem.

Answer 142

RTT_med + 3–5× jitter

Answer 143

BDP (frames) = R_payload × RTT / frame_payload_bits

Answer 144

* BDP (frames) = R_payload × RTT / frame_payload_bits * W_target ≈ 2 × BDP (frames) * RTO_good ≈ RTT_med + 4 × σ_RTT

Answer 145

To set interleaver depth ≥ burst-95th percentile and unlock FEC gain

Answer 146

A CDF of burst length (symbols) and key numbers: (N_{90}), (N_{95}), (N_{99})

Answer 147

D ≥ 1.2–(1.5 × N_{95})

Answer 148

Symbol rate (R_s) and a time-stamped stream of SNR or E_b/N_0 estimates, EVM, decoder outcome, and optional dual-pol branch SNRs

Answer 149

A contiguous time interval where the channel quality is below the code’s working threshold

Answer 150

N = R_s × T

Answer 151

Pick a quality metric: per-window (E_b/N_0) or EVM

Answer 152

E_b/N_0^{ ext{thr}} at the knee + 0.3 dB margin

Answer 153

Median/boxcar over 2–3 windows

Answer 154

Setting values below threshold to 1 (in-fade) and above to 0

Answer 155

It encodes the 1's to get burst durations (T_i) in seconds

Answer 156

A histogram/CDF

Answer 157

Build a binary error trace: 1 for a failed frame, 0 for a good frame

Answer 158

A contiguous run of 1's in the binary error trace

Answer 159

T = K × T_{ ext{frame}}

Answer 160

For BPSK/QPSK + strong LDPC: ~1.5–2.5 dB; for Conv/RS moderate code: ~4–6 dB

Answer 161

Compute both per-branch bursts and combined bursts

Answer 162

Exclude intervals where the radio paused; only count RF-present periods

Answer 163

The duration of the burst equals the unlock time

Answer 164

Smooth, mask, run-length encode, convert to symbols, build histogram/CDF

Answer 165

Latency: one-way interleaver delay (approx D/R_s)

Answer 166

* Add diversity * Lower R_s * Stronger code

Answer 167

To verify the E_b/N_0 threshold by matching BER waterfall

Answer 168

Re-compute monthly and check for polarization/attitude or site interference changes

Answer 169

Extract runs from SNR/EVM/LLR or frame errors, convert time to symbols, build a CDF, and set interleaver depth

Answer 170

1. code rate/length 2. decoder iteration budget/schedule 3. soft-decision LLR scaling

Answer 171

{code_family, block_length n, info_length k, rate R=k/n, interleaver, puncture/shorten map, quant bits, LLR scale s, max_iter, stop_rule}

Answer 172

The 5th-percentile elevation from the link budget

Answer 173

CCSDS LDPC

Answer 174

* Low latency: n≈1024–2048 * Best coding gain: n≈4096–8160

Answer 175

* 1/2 * 2/3 * 4/5

Answer 176

Mission latency

Answer 177

To bail early in deep fades when no progress is made

Answer 178

All parity checks satisfied or CRC-aided stop

Answer 179

s = 2/σ²

Answer 180

* Pilot-aided * Decision-directed * From E_b/N_0 estimator

Answer 181

5–7 bits

Answer 182

Var(L) ≈ 2, E[|L|]

Answer 183

≤0.2 dB gap at FER (10^{-3})

Answer 184

Pick (R, n) from your link budget + burst CDF

Answer 185

Robust noise estimator; subtract I/N; tighten preselection

Answer 186

LLR under-scaled; too few iterations; wrong roll-off

Answer 187

Increase ±Lmax to 7–8; go to 6–7 bits; check interleaver order

Answer 188

No early-stop; poor scaling

Answer 189

≥ 1.2–1.5× your measured burst-95th

Answer 190

(widehat{E_b/N_0}) per frame from SDR ## Footnote It uses pilot-aided or decision-directed approaches with the same matched filter as the modem.

Answer 191

* EVM% → (E_s/N_0) → (E_b/N_0) via demapper's mapping * Decoder-internal softs: average LDPC iterations or syndrome density ## Footnote These can be used to sanity-check the estimate.

Answer 192

\boxed{\widehat{m} = \widehat{E_b/N_0} - E_b/N_0^{\text{req}}(\text{MCS}) - \Delta_{\text{impl}} - \Delta_{I/N}} ## Footnote This includes factors for implementation and interference.

Answer 193

To smooth noisy estimates and prevent flaps ## Footnote This includes outlier clipping and an Exponential Moving Average (EMA) filter.

Answer 194

100–300 ms ## Footnote This should scale with coherence time and vehicle dynamics.

Answer 195

Freeze decisions if Eb/N0 drops >3 dB for <200 ms ## Footnote This prevents micro-fades from causing mode drops.

Answer 196

* Effective throughput * Crossing points of throughput vs (E_b/N_0) * Margin thresholds with safety ## Footnote The thresholds are adjusted using up-switch and down-switch formulas.

Answer 197

* Up-switch: (M_{\uparrow}=+0.7) to +1.0 dB * Down-switch: (M_{\downarrow}=+0.3) to +0.5 dB ## Footnote Asymmetry in these values helps prevent flaps.

Answer 198

To create a gap between up-switch and down-switch thresholds ## Footnote Typically, a gap of 1.0–1.5 dB is recommended.

Answer 199

* Up-dwell: 500–1000 ms * Down-dwell: 150–400 ms ## Footnote These ensure stable operation and protect the link.

Answer 200

utc, mode, m_hat_dB, m_smooth_dB, EbN0_dB, EVM_pct, PER_win, avg_iter, burst_flag, up_timer, down_timer, last_switch_utc ## Footnote This data helps identify issues and optimize performance.

Answer 201

Too little hysteresis or short dwell or noisy estimator ## Footnote Solutions include increasing hysteresis and dwell times.

Answer 202

* Estimate margin against the right waterfall * Filter and drive a Schmitt trigger with dwell & cooldown * Place thresholds at throughput curve crossings ## Footnote This strategy helps maintain optimal throughput and stability.

Answer 203

≥300 ms ## Footnote This prevents rapid mode changes or 'ping-pong' effects.

Answer 204

True ## Footnote The formula is T_i(\gamma)= R_{\text{payload},i} \cdot (1 - \text{PER}_i(\gamma)).

Answer 205

Without uniform, time-aligned telemetry, you can’t explain PER spikes

Answer 206

To tie each success/failure to instantaneous link state and exact SDR config

Answer 207

One row per decoded frame and optionally per failed frame

Answer 208

* `utc` * `sat_id` * `gs_id` * `profile_id` * `mode`

Answer 209

Boolean indicating CRC/FEC success

Answer 210

fail_reason

Answer 211

To provide a sliding window PER estimate

Answer 212

1 Hz or 5–10 Hz if light while receiving

Answer 213

To correlate PER to slow physics without exploding data volume

Answer 214

* `snr_branchH_dB` * `site_temp_C` * `loss_of_lock_events`

Answer 215

To provide a quick health assessment and stable metrics for trend dashboards

Answer 216

* `frames_total` * `frames_ok` * `PER_overall` * `ebn0_median_dB`

Answer 217

* `utc` * `sat_id` * `gs_id` * `profile_id` * `mode`

Answer 218

To make joins trivial

Answer 219

Always UTC; sync GS clocks (≤10 ms)

Answer 220

Margin; it correlates directly with PER waterfall

Answer 221

They indicate ephemeris/clock fidelity

Answer 222

[decoded frame]

Answer 223

Log 1-in-N successes but all failures

Answer 224

PER vs elevation, colored by `profile_id`

Answer 225

To capture foldback/brownout signatures vs PER bursts

Answer 226

To control config drift and ensure site-dependent PER matches

Answer 227

Conduct nightly sanity checks and store pass/fail results

Answer 228

To provide an optional pointer to IQ file and byte offset for replay parity

Answer 229

* TX source bits (pre-FEC) * Air bits (on-the-wire after framing/scramble/FEC) * Baseband I/Q (complex, post-RRC) * IF/RF capture (optional, for end-to-end) ## Footnote Each artifact has a specific file format and includes detailed metadata.

Answer 230

Fixed-seed PRBS (or a small known pattern) of exact length (k) ## Footnote This file represents the TX source bits before Forward Error Correction (FEC) is applied.

Answer 231

Exactly what leaves the framer (bit order documented) ## Footnote This file captures the air bits after framing, scrambling, and FEC.

Answer 232

Complex int8 or float32 I/Q at a fixed sample rate and samples/symbol, with ASF/VRT/JSON sidecar describing all DSP knobs ## Footnote This file contains the baseband I/Q data after root raised cosine filtering.

Answer 233

Real or complex int16 around some IF (e.g., 1.25 MHz), again with sidecar metadata ## Footnote This file is optional and is used for end-to-end captures.

Answer 234

To ensure that PRBS and scrambler outputs are consistent across replays ## Footnote Specific seeds for PRBS and polynomial scrambler must be documented.

Answer 235

* profile_id * mode * src_bits * framer * fec * modem * carrier * sampling * channel * hash * notes ## Footnote This metadata is crucial for understanding the context of the generated artifacts.

Answer 236

FER vs Eb/N0 must match the lab/spec curve within ≤ 0.2 dB at FER (10^{-3}) ## Footnote This test ensures that the performance metrics align with expected specifications.

Answer 237

To use a single, audited reference implementation to produce all artifacts ## Footnote This method ensures that the generation process is standardized and verifiable.

Answer 238

Running the same bits through the flight modem or SDR TX in a shield box / cabled loopback ## Footnote This method captures real-world performance and checks for discrepancies.

Answer 239

* PER: exact at high SNR; ±0.2 in (10^{-3}) FER bins * EVM: ±0.5 % abs. ## Footnote These tolerances help in validating the performance of the SDR stack.

Answer 240

To ensure all ground stations replay the same golden and upload results for verification ## Footnote Any mismatches indicate configuration drift or site issues.

Answer 241

slicing ## Footnote This method helps in obtaining a real-world performance snapshot.

Answer 242

True ## Footnote This structure facilitates easy access and management of generated artifacts.

Answer 243

Checksums for all files in the directory ## Footnote This file helps verify the integrity of the generated artifacts.

Answer 244

PER == 0 for 'high_snr', and within bands at each Eb/N0 bin ## Footnote This ensures that the system performs as expected under controlled conditions.

Answer 245

Replaying the closest-mode golden on the ground station when a real pass has anomalies ## Footnote This helps diagnose whether issues are due to local configuration or RF conditions.

Answer 246

Easier to sanity-inspect and detect slips ## Footnote Structured patterns help in identifying errors more effectively than random blobs.

Answer 247

It verifies that the SDR pipeline processes the golden files correctly ## Footnote This serves as a template for automated testing of the SDR stack.

Answer 248

PER vs elevation and C/(N+I) ## Footnote It should not be based on folklore.

Answer 249

Maximize delivered bytes by integrating instantaneous throughput over elevation ## Footnote It must respect AOS/LOS setup, RTT/ARQ window limits, ACM thresholds, and handover costs.

Answer 250

Time/site/polarization with combining rule and backhaul/clocking defined

Answer 251

Measured cross-pol fades and burst-length CDF

Answer 252

* PER & Eb/N0 vs elevation from flight SDR logs * I/N penalty vs az/el at each site * Burst-length CDF single-pol vs dual-pol * Doppler rate vs elevation * RTT, ARQ window W, mode ladder * Antenna patterns and axial ratio vs angle * Weather/ionosphere risk per band/site * Backhaul latency/jitter between GSs

Answer 253

Data-driven, per site, per link direction ## Footnote Empirical mask from pass data, physics cross-check, and special masks.

Answer 254

Build PER vs elevation curves at constant configuration

Answer 255

Lowest elevation where post-FEC PER ≤ target and median margin ≥ 3 dB for at least two adjacent bins

Answer 256

Urban UHF sites often need 10–15° DL, 20–25° UL; quiet rural can run 5–10°

Answer 257

Add azimuthal notches for a direction-dependent mask

Answer 258

Maximize delivered bytes, not contact minutes

Answer 259

Bytes(p)=∫_{t∈p}! T_{ ext{eff}}(Eb/N0(t), ACM, W, RTT),dt

Answer 260

Passes whose peak elevation lands where modes step up

Answer 261

Overlap stations by ≥20–30 s around handover

Answer 262

* Selection combining * Soft combining

Answer 263

GPSDO/NTP to ≤10 ms

Answer 264

Dual-linear (H/V) with selection or MRC; or circular with ~3 dB penalty

Answer 265

GS circular, matching sense is ideal; add dual-circular only if sense flips

Answer 266

* PER/EbN0 vs elevation * I/N vs az/el * Burst-length CDF (single vs dual-pol)

Answer 267

Margin(e)=Eb/N0(e)-Eb/N0^{ ext{req}}-Δ_{ ext{impl}}-Δ_{I/N}(e) ≥ 3 dB

Answer 268

T_{ ext{eff}} = min(T_{ ext{PHY}}(e)·(1-PER(e)), payload_bits·W/RTT)

Answer 269

+1–3 dB median SNR and shorter bursts

Answer 270

Enable selection combining or soft combining if you have LLR transport

Answer 271

* Build PER/EbN0 vs elevation plots per site * Extract I/N penalty vs az/el from 24-h waterfalls * Compute burst-length CDFs single-pol vs dual-pol * Set DL/UL masks with +3 dB margin criterion * Implement pass scoring * Pick GS polarization per site * Trial a two-site overlap pass * Bake masks & polarization into scheduler config

Answer 272

{task, priority, period/jitter, WCET, CPU%, stack headroom, queue depth}

Answer 273

{kick period, timeout, jitter, reset cause stats}

Answer 274

tx/rx/HK/control and collision ledger

Answer 275

To prove 'SW stall' or clear SW of blame by correlating PER spikes with CPU, ISR latency, queue depth, WDT jitter

Answer 276

To provide a single monotonic µs clock in a shared header for all hooks

Answer 277

t_enter, t_exit, execution time, jitter, priority, core_id, preempted_by

Answer 278

{depth, high_watermark, dropped} and time-in-queue when popping

Answer 279

Every kick time (t_kick) and the configured timeout

Answer 280

HK start/end, payload size, affected buses, radio lock claims, collision flag

Answer 281

CPU time, missed deadlines, stack watermark, malloc fails

Answer 282

q.max ≥ λ·RTT_frames + burst_margin (where λ = offered frame rate)

Answer 283

Timeout should be ≥ 3× the 99th-percentile kick interval

Answer 284

≤ 50–100 µs; 95th ≤ 2×

Answer 285

high watermark ≤ 80% at peak; drops = 0 in 24 h

Answer 286

ISR > radio DMA > PHY/deframer > ARQ > HK > logging

Answer 287

To log entry and exit times for tasks and ISRs

Answer 288

Events where HK overlaps radio-critical sections

Answer 289

To see if kick jitter and queue depth cause PER at constant Eb/N0

Answer 290

utc, hk_task, rf_task, mutex, blocked_ms

Answer 291

Holding RF-critical mutex/bus for >1 ms contiguous

Answer 292

Enable priority inheritance and split long HK jobs into short chunks

Answer 293

Burst HK at 5–10× normal cadence for 10 s

Answer 294

Directional coupler (or reflectometer) ## Footnote It measures forward power (P_fwd) and reflected power (P_refl) with a directivity of ≥ 25–30 dB.

Answer 295

PA drain voltage (V_D) and current (I_D), PA case/die temperature ## Footnote The ADC shared across rails should be ≥ 10–50 kS/s.

Answer 296

Cross-checks P_out vs coupler and catches detector/coupler drift.

Answer 297

It allows alignment with Eb/N0/EVM at the ground.

Answer 298

|Γ| = √(P_refl / P_fwd) ## Footnote This is a key step in deriving RL and VSWR.

Answer 299

RL (dB) = -20 log_{10} |Γ|

Answer 300

Voltage Standing Wave Ratio; VSWR = (1 + |Γ|) / (1 - |Γ|)

Answer 301

10–20 Hz for P_fwd, P_refl, V_D, I_D, PA Temp.

Answer 302

To increase the sampling rate up to 100 Hz for 5–10 s when specific thresholds are crossed.

Answer 303

Low-pass it with a short 50–150 ms EMA to reduce ADC speckle.

Answer 304

EVM%, (E_b/N_0), residual CFO/timing, PER.

Answer 305

(P_out) flattens, EVM rises, (I_D) climbs faster than (P_out).

Answer 306

RL worsens (≤ 10 dB), then PA current or reported target power drops.

Answer 307

PA Temp crosses a knee, I_D and/or P_out step down periodically.

Answer 308

Sweep output load VSWR with a tunable mismatch.

Answer 309

(P_{1dB}) and EVM vs output power at real waveform across temperature.

Answer 310

VSWR ≥ 2.0:1 or RL ≤ 9.5 dB for >200 ms.

Answer 311

Back-off TX 3–6 dB or switch to lower-crest mode when VSWR ≥ 3:1.

Answer 312

EVM rises > +1.5 % abs while (E_b/N_0) within ±0.3 dB and (I_D) rising.

Answer 313

T_PA exceeds knee and duty-modulated EVM spikes appear.

Answer 314

PA (I_D) + output detector trend, normalized GS (E_b/N_0) as EIRP proxy.

Answer 315

utc, sat_id, pass_id, PA_T_C, V_D_V, I_D_A, P_fwd_dBm, P_refl_dBm, RL_dB, VSWR, comp_flag, foldback_flag, cal_hash.

Answer 316

RL ≥ 14 dB (VSWR ≤ 1.5:1).

Answer 317

Expect EVM hits; consider back-off.

Answer 318

Set soft-alert at (T_knee - 5°C), hard at vendor limit.

Answer 319

Coupler fwd/refl, PA (V_D)/(I_D), PA Temp at 10–20 Hz.

Answer 320

To store all calibration constants in NVM and include in telemetry.

Answer 321

Decide on the jurisdiction(s), ITU region, service classification, bands in use, and list of ground stations ## Footnote This helps determine which rules apply to each link direction.

Answer 322

* Licence/authorization or coordination letter * Allocation table entries * Emission limits * Site permit conditions * IARU coordination record (if amateur) ## Footnote These documents are crucial for compliance and should be archived.

Answer 323

To extract and summarize the numerical limits for each link and site in a structured format ## Footnote This matrix facilitates the design process for RF and SDR teams.

Answer 324

B_occ ≈ R_s(1 + α) ## Footnote This relationship is essential for determining symbol rates based on bandwidth limitations.

Answer 325

The ITU emission designator (e.g., `200K0G7D`) based on final Rs/α/FEC/framing ## Footnote This ensures that the design complies with authorization.

Answer 326

* Analyzer settings: RBW per rule * Detector RMS * Span ≥ 3× OBW * PASS: OBW ≤ limit − margin ## Footnote This ensures that the system meets regulatory bandwidth requirements.

Answer 327

* Confusing OBW methods * PA compliance at only room temperature * Spur near IF/LO frequencies * GS filter too wide ## Footnote Recognizing these can prevent compliance issues.

Answer 328

* Fill the Regulatory Dossier * Build the compliance matrix * Compute max Rs and required PA back-off * Specify GS preselector BW and notches * Run bench tests and archive results * Encode regulatory gates in SDR profile * Update scheduler/ACM ## Footnote Completing these tasks ensures compliance and operational readiness.

Answer 329

It allows for maximal MCS/rate choices within the law and ensures GS filters are tight enough to avoid compliance surprises ## Footnote This is critical for maintaining spectrum access.

Answer 330

* Allocation & service * Authorized center frequency * Max EIRP * Max bandwidth/channelization * Occupied BW definition * In-band mask * OOB mask * Spectral density limit * Duty/ID requirements * Polarization * Site-specific filters ## Footnote This comprehensive view helps in ensuring all limits are respected.

Answer 331

False ## Footnote The SDR must refuse any settings that breach regulatory limits.

Answer 332

One or two flipped bits typically make the entire packet fail authentication and get dropped.

Answer 333

* Scheme & parameters * Overhead * Latency * Bit-error sensitivity

Answer 334

* crypto.alg * crypto.key_bits * crypto.tag_bytes * crypto.nonce_bytes * crypto.aad_schema * crypto.pad_mode * crypto.frag.mtu_bytes * crypto.replay.window

Answer 335

Overhead = IV/nonce + auth tag + pad + headers

Answer 336

* Compute time * Buffering * Queueing

Answer 337

PacketSuccess ≈ (1−p)^{L_bits}.

Answer 338

p_* ≈ -ln(1-P_drop)/L_bits

Answer 339

(10^{-7}) to (10^{-8}) range

Answer 340

Reuse can pass tags but break security.

Answer 341

+32 bytes/packet (no padding)

Answer 342

~0.5–2 ms per 1 kB

Answer 343

* Capture plaintext length (P) * Capture ciphertext length (C) * Analyze based on known patterns

Answer 344

* crypto_alg * tag_bytes * nonce_bytes * aad_len * replay_drop * auth_fail

Answer 345

* Lower MCS / add margin * Increase interleaver depth * Use a stronger code * Reduce packet size

Answer 346

Align plaintext sizes to integer FEC block multiples.

Answer 347

To produce PacketSuccess vs BER plots.

Answer 348

Higher false-accept risk, but negligible vs BER.

Answer 349

1. What exactly gets stored (I/Q + metrics) and for how long 2. Whether you can physically move those captures where they’re needed 3. How to keep it compliant (privacy, licensing, export, access) ## Footnote These factors are crucial for data governance and compliance in data management.

Answer 350

`cs8` (interleaved int8 I then Q) with a sidecar JSON metadata file ## Footnote This format is preferred due to its small size and compatibility across toolchains.

Answer 351

rate = f_s × SPS × 2 × 1 byte ## Footnote This formula helps in estimating the data rate based on sampling frequency (f_s) and samples per second (SPS).

Answer 352

`cf32` (float32 complex) for lab math; derive from `cs8` when needed ## Footnote It is recommended not to store both formats long-term.

Answer 353

* Tier 0: edge ring-buffer (20–60 s) * Tier 1: last 7–30 days of snapshots * Tier 2: last 6–12 months of snapshots * Tier 3: legally/mission-required archive (1–5 years) ## Footnote These tiers help manage data efficiently and prevent data overload.

Answer 354

t ≈ S / throughput ## Footnote This formula helps in estimating the time required to upload data based on its size and the available bandwidth.

Answer 355

* utc * sat_id * gs_id * profile_id * vcid * seq * ok * EbN0_dB * EVM_pct * PER_window * AFC_residual_hz * timing_err_ui * SNR_branch(H/V)_dB ## Footnote These metrics provide crucial context for root-cause analysis.

Answer 356

* Radio: loss of lock, AFC capture exceeded, PLL cycle slip, EVM > threshold * RF chain: RL/VSWR breach, PA foldback flag * Ops: ACM mode switch, profile change, handover start/end ## Footnote These triggers help ensure that important events are captured for analysis.

Answer 357

To document precise durations, owners, and deletion methods for data storage ## Footnote A retention policy ensures compliance and efficient data management.

Answer 358

* profile_id * fs_hz * center_hz * sps * rrc_alpha * rrc_taps * gain_plan * clock_ref * ppm_trim * capture_reason * utc_start * duration_s * sha256 ## Footnote These keys provide essential metadata for the I/Q captures.

Answer 359

AES-256 server-side encryption for object storage ## Footnote This method ensures data security and compliance with standards.

Answer 360

Role-Based Access Control ## Footnote RBAC is critical for managing user permissions and ensuring data security.

Answer 361

False ## Footnote Data minimization recommends storing only short, context-rich windows around events.

Answer 362

To list all I/Q parts, hashes, byte ranges, and metric files ## Footnote A pass manifest facilitates data organization and retrieval.

Answer 363

time duration of the capture in seconds ## Footnote This calculation helps estimate the data size based on the duration of the capture.

Answer 364

* Always compress metadata & CSV * Do not compress `cs8` * Dedup by hash * Nightly sync for routine uploads * Priority lanes for anomaly snapshots * Resume-safe object storage ## Footnote These strategies help streamline data transfer and minimize bandwidth usage.

Answer 365

* Pick formats for I/Q and metrics * Implement a 60-s ring buffer * Define retention tiers with durations * Compute site bandwidth & schedule transfers * Enable RBAC + encryption * Stand up a catalog and deterministic naming * Conduct nightly replay smoke tests * Publish a one-pager policy ## Footnote This checklist helps ensure compliance and efficient data management practices.

Answer 366

Store what’s necessary and sufficient to recreate the pass, with deterministic metadata and hashes ## Footnote This principle guides effective data management and compliance.

Answer 367

Criteria that the SDR must meet before fleet-wide rollout.

Answer 368

* PER vs elevation * Acquire/lock times * Minimum throughput at the 5th-percentile elevation * Recovery time after slips

Answer 369

Packet Error Rate

Answer 370

To prove the real-world PER curve matches design once C/(N+I) is accounted for.

Answer 371

Collect ≥ 5 clean passes per site, bin frames by elevation, compute post-FEC PER per bin.

Answer 372

* PER ≤ 1e-3 for robust mode * PER ≤ 5e-3 for high-rate mode

Answer 373

To evaluate the time taken to acquire and lock onto a signal.

Answer 374

Time from AOS timestamp to first valid decoded frame.

Answer 375

Time from signal detect to PLL/AFC locked state.

Answer 376

* ≤ 2.0 s cold * ≤ 0.8 s warm

Answer 377

The median effective payload throughput within ([e_5±2°]).

Answer 378

Build instantaneous throughput from logs and report median and p10.

Answer 379

* Median (T(t)) ≥ X kbps * p10 (T(t)) ≥ 0.8 × X

Answer 380

Conditions leading to a state where PLL is not locked or loss of lock occurs.

Answer 381

Time from slip event to first contiguous K good frames.

Answer 382

≤ 300 ms to 5 good frames.

Answer 383

To summarize the metrics and gates for acceptance in deployment.

Answer 384

* PER rises at mid-elev * Slow AOS * Throughput short at (e_5) * Recovery slow

Answer 385

[e_5±2°]

Answer 386

* utc * elev * mode * ok * seq * vcid * EbN0 * EVM * afc_state * pll_state * afc_residual_hz * timing_err_ui

Answer 387

* Replay goldens at several Eb/N0 * Inject slip/fade scenarios * Store KPI snapshots

Answer 388

To ensure bounded recovery times for various slip events.

Answer 389

Known-good I/Q for each mode with Eb/N0 annotation.

Answer 390

Sample rates, loop BWs, filters, FEC, ACM thresholds, power, masks ## Footnote SDR profiles are treated as software and must go through a release process.

Answer 391

To store text files (e.g., TOML) for each mode ## Footnote The profiles repository uses git for version control.

Answer 392

JSON Schema ## Footnote The schema file is named `profile.schema.json`.

Answer 393

`profile_id = sha256(profile_file)` (short 12-hex for display) ## Footnote This ensures unique identification of profiles.

Answer 394

I/Q snippets + expected KPIs (PER/EVM/iter/lock time) at several Eb/N0 ## Footnote These assets are per-mode and used for testing.

Answer 395

Mask limits, max Rs/α, PA back-off, PFD/PSD caps ## Footnote This ensures regulatory compliance during operation.

Answer 396

Author opens a PR changing only text profiles ## Footnote Optionally, goldens/compliance may also be changed.

Answer 397

Motivation & risk, exact deltas, compatibility, rollback plan, validation checklist ## Footnote This ensures thorough review and understanding of changes.

Answer 398

Lint & schema validation, golden replays, hardware-in-the-loop, unit tests for ACM/ARQ ## Footnote These checks help to ensure quality and compliance.

Answer 399

Mid-elev PER ↑ > 0.5% abs, AOS p95 acquire > spec, golden replay fails, regulatory flags exceedance ## Footnote These conditions are monitored closely to prevent issues.

Answer 400

Every packet/metric includes `profile_id` ## Footnote This helps track which profile was used during operations.

Answer 401

Live proof before fleet rollout with one GS + one sat for 24–72 hours ## Footnote It allows for testing in a controlled environment before full deployment.

Answer 402

Release version, changes, rationale, impact, ops action, rollback information, compliance status ## Footnote This information is crucial for operational awareness.

Answer 403

The station auto-quarantines and no pass operations are allowed ## Footnote This helps prevent operational issues caused by configuration errors.

Answer 404

environment allow-list

Answer 405

Signed builds, immutability of profiles, audit trail, post-release snapshot ## Footnote These measures maintain the integrity of the SDR profile management process.

Answer 406

DEV, STAGE, CANARY, FLEET ## Footnote Each stage serves a specific purpose in testing and deployment.

Answer 407

To ensure all critical checks are performed before merging a PR ## Footnote This helps maintain quality and compliance in profile changes.

Answer 408

Rejects uploads from unknown `profile_id`s ## Footnote This is a security measure to prevent unauthorized profiles.

Answer 409

To label each loss as RF-induced, Software/Queue/ARQ-induced, or both.

Answer 410

* `ok` (CRC/FEC) * `seq` * `vcid` * `mode` * `profile_id` * `EbN0_dB` * `EVM_%` * `afc_state` * `pll_state` * `afc_residual_hz` * `timing_err_ui` * `loss_of_lock_events`

Answer 411

* `RF_MarginDrop` * `Loop_Unlocked` * `Interf_Spike` * `Pol_Fade`

Answer 412

`tx_q_depth > 0.8·q_max` OR `tx_q_dropped > 0` in the last second.

Answer 413

* Eb/N0↓, EVM↑ in lockstep * `search`, `unlock`, residual jumps in AFC/PLL * Best-vs-worst branch gap widens * I/RBW spikes * Normal queues/CPU/ISR * Normal ARQ/Window unless RF loss triggers NACKs

Answer 414

[Software-induced]

Answer 415

* Tighten preselector or enable notch * Lower PA back-off if legal mask allows * Switch site/diversity * Consider circular/dual-pol if `Pol_Fade`.

Answer 416

Scores for RF, Software, and ARQ flags based on assigned weights.

Answer 417

* Flat Eb/N0, EVM steady * Locked AFC/PLL * No change in diversity * Normal I/RBW * TX/RX depth ↑, drops ↑, ISR latency ↑ * Normal ARQ/Window

Answer 418

To decide in one pass whether issues are RF, Software, or ARQ related.

Answer 419

Retransmissions fire on timer cadence with no RF flags.

Answer 420

* Gate producers * Separate TX queues * Raise radio task priority * Enlarge queue to keep ≤80% high-water * Remove blocking FS/HK in radio path.

Answer 421

Stacked bars by label (RF/SW/ARQ) with confidence; clicking shows the fired flags.

Answer 422

Combined SNR dips but best branch significantly better than the worst branch by ≥4 dB.

Answer 423

Set W ≥ 2·BDP(frames).

Answer 424

f_D,max = (v_rel / c) f_c at AOS; add XO error (f_c·PPM) ## Footnote v_rel is the relative velocity, c is the speed of light, and PPM stands for parts per million.

Answer 425

F_cap ≥ 1.2 * (|f_D,max| + f_c·PPM_max) ## Footnote This ensures the loop can effectively track the frequency offset.

Answer 426

LEO S/L: ±5–20 kHz; UHF 437 MHz, 2–3 ppm XO: ±6–10 kHz

Answer 427

B_{n,PLL} ≈ 0.005–0.02 * R_s ## Footnote Use higher end for fast recovery mode and lower end for steady tracking.

Answer 428

B_{n,TED} ≈ 0.003–0.01 * R_s

Answer 429

D ≥ 1.2–1.5 × N_{95} ## Footnote N_{95} is the burst-length CDF in symbols.

Answer 430

* AWGN waterfalls for codes * Crypto drop budget * ACM throughput crossings

Answer 431

Lowest back-off that passes the tightest mask with ≥2–3 dB margin at hot ## Footnote EVM ≤ spec (e.g., ≤5–8% for QPSK).

Answer 432

Margin(e) = E_b/N_0^meas(e) - E_b/N_0^req(mode) - Δ_impl - Δ_{I/N}(e)

Answer 433

6–9 dB back-off from P1dB for clean masks

Answer 434

Margin ≥ +3 dB

Answer 435

* Max CFO at AOS * CFO slew * Symbol rate

Answer 436

To cover elevation margin tiers and optimize throughput

Answer 437

* Attack: 1–5 ms * Decay: 50–200 ms

Answer 438

t_int ≈ D / R_s

Answer 439

Frame Error Rate

Answer 440

Add XO PPM to derive AFC capture.

Answer 441

500–2000 Hz

Answer 442

N_{95}=1200–2500 symbols

Answer 443

B_{n,FLL} ≥ √(|dot f_D,max|/π) and clamp ≤ 0.05 * R_s

Answer 444

The ratio of Carrier power (C) to the sum of thermal noise (N) and in-band interference (I) ## Footnote Components: Carrier power (C), thermal noise (N), in-band interference (I).

Answer 445

N = kTB · NF ## Footnote Where k is Boltzmann constant, T is temperature, B is bandwidth, and NF is Noise Figure.

Answer 446

* C/N (no interference) * C/(N+I) (real-world) * E_b/N_0 (energy/bit normalization)

Answer 447

ΔSNR = 10log10(1 + I/N) ## Footnote This represents effective loss due to interference.

Answer 448

* Narrowband (CW) * Wideband * Impulsive

Answer 449

Carrier power spectral density vs noise spectral density

Answer 450

C/N₀ = SNR + 10log10(B) ## Footnote Used for acquisition thresholds and GPS-style links.

Answer 451

Interference spectral density ## Footnote Used to convert to C/(N+I) with C/N₀ and I₀.

Answer 452

Decibels relative to full scale

Answer 453

Reflection coefficient (|Γ|) and forward/reflected power

Answer 454

RL = -20log10|Γ|

Answer 455

Total EIRP and occupied bandwidth

Answer 456

EIRP*dBW/Hz = EIRP*dBW - 10log10(B_occ)

Answer 457

Transmit EIRP, path loss, geometry, polarization loss

Answer 458

PFD = EIRP/(4πR²)

Answer 459

Major/minor axes of polarization ellipse

Answer 460

* Linear (AR→∞) * Circular (AR≈1–3 dB) * Elliptical

Answer 461

Acquisition of Signal

Answer 462

* Predictor time * Initial CFO/timing uncertainty * Search strategy

Answer 463

Line of Sight

Answer 464

Temporarily widened loop BWs, higher loop gains, reduced averaging

Answer 465

* Loop order (2nd, 3rd) * Natural frequency (ω_n) * Damping ζ * Loop gain

Answer 466

Coarse pull-in; handoff to PLL

Answer 467

* Early-late samples * Interpolation filter * Timing error estimate

Answer 468

Fraction of symbol period; maps to sampling phase jitter

Answer 469

Estimator bias, Doppler rate, XO drift

Answer 470

* Interpolator accuracy * Decimator ratios * FPGA budget

Answer 471

Logical mapping & differential coding impact; affects inversion/diff ambiguity

Answer 472

Phase ambiguity resolution; impacts BER in cycle slips

Answer 473

Parity equations; zero syndrome ⇒ codeword candidate

Answer 474

Outer CRC; halts iterations when CRC passes

Answer 475

Preserve MI while minimizing memory/compute

Answer 476

Mutual information between bits & LLRs; maps LLR variance to MI

Answer 477

Spacecraft ID (global) and Virtual Channel ID (per stream)

Answer 478

Cumulative ACK repeats; indicates hole earlier in window

Answer 479

ACK coalescing to save uplink; latency/throughput tradeoff

Answer 480

Keep W ≥ 2·BDP (in frames) to fill pipe with RTT variability

Answer 481

Thresholding metric (Eb/N0, EVM, LLR variance), RLE of below-threshold spans

Answer 482

Tag length (t bits) ⇒ (2^{-t}) false accept

Answer 483

Sequence window W; drops replays or out-of-order beyond W

Answer 484

PA temperature thresholds; automatic power reduction

Answer 485

* Specified attenuation at frequency offsets * Interpolation rules * Measurement RBW

Answer 486

Encoded mask/power/PSD/PFD gates; profile validation gate in CI/runtime

Answer 487

Manage per-packet schema keys, context, loss-of-lock events

Answer 488

Deterministic decodes, expected PER/EVM/lock time bands

Comms RCCA/CAPA (Network Engineering) Flashcards

(541 cards)