← Back to tutorial library

6G RESEARCH STUDIO · Examples & Tutorials

Advanced NTN / Multi-Satellite

Run link and mobility related analysis for NTN / multi-satellite data.

Learn how to use 6G Research Studio for Advanced NTN / Multi-Satellite with real, manually matched screenshots. This tutorial covers setup, execution, result interpretation and practical checks.

What this tutorial covers

Run link and mobility related analysis for NTN / multi-satellite data.

Before you start:You need access to the product and should ideally follow the tutorial using your own real parameters or data. The screenshots below were manually rematched to avoid the image/topic mismatches seen in the previous version.
Advanced NTN / Multi-Satellite - Open the relevant module and confirm the starting state.
Open the relevant module and confirm the starting state.
Advanced NTN / Multi-Satellite - Configure the key inputs that match the topic.
Configure the key inputs that match the topic.
Advanced NTN / Multi-Satellite - Run the workflow and inspect the result/status.
Run the workflow and inspect the result/status.

Step-by-step workflow

1Open the module

Open Advanced NTN / Multi-Satellite from Network & Mobility. Confirm that the visible page really matches the tutorial topic before changing any settings.

2Configure the input

Prepare and check NTN link/trajectory data, time fields and measurement parameters.

3Run and watch the status

Map the fields and run the analysis. Watch the visible status, plot or log area while the workflow is running.

4Inspect the result

Pay special attention to latency, SNR, handover and other related results.

5Verify and iterate

With real trajectories, verify that time and unit-related fields are mapped correctly. Change one meaningful parameter and rerun so you can verify whether the output changes in the expected direction.

How to read the result

  • The main output of this workflow is latency, SNR, handover and other related results.
  • Read the result together with the exact inputs used for the run; a screenshot alone rarely tells the whole story.
  • With real trajectories, verify that time and unit-related fields are mapped correctly.

Troubleshooting & practical tips

  • If nothing changes, first confirm that the correct module is open.
  • If the output looks unrealistic, check units, field mapping and input scale first.
  • For comparisons, change one key parameter at a time whenever possible.