Hi,
We are currently using AODT to investigate NTN propagation scenarios.
We observed that the number of detected ray paths decreases significantly as the RU altitude increases. In our experiments, the number of LoS paths starts to decrease at around 7 km, and no viable ray paths are detected above approximately 10 km.
[5km]
[8km]
We have a few questions regarding the ray-tracing configuration:
- Is it possible to configure the angular distribution or resolution of the initial rays, for example by restricting the ray search to a specific angular region toward the target UE, rather than only increasing the
sim_em_rays?
- The low-level EM Solver API provides
RTConfig::rx_sphere_radius_cm, but we could not find an equivalent option in the Python SimConfig API or YAML configuration. Is there a supported way to configure the UE reception sphere radius?
Thank you.
@mhseo10
Unfortunately, AODT cannot restrict the rays to a specific region. Note that a NLoS may appear from a location anywhere on the map, so restricting the rays to a angular distribution is not correct. You can add a directional antenna gain to increase the power of the rays.
With 1.5.0, you can shoot 10’s of millions of rays. Please try as large as your map/antenna configuration allows.
The UE reception sphere radius is not available via yaml (it will be exposed in 1.6). However you can overwrite its default value in assets/scenrio.json . This file is uploaded to the s3 bucket.
The above results were obtained using a map with an area of approximately 15km^2 and 40 million rays. Following your suggestion, we changed sim_em_sphere_radius in assets/scenario.json to 10 m, but the following error occurred:
Is there any way to configure sim_em_sphere_radius to a value larger than 2 m in the current version? Also, are there any plans to support NTN simulation scenarios in future releases, including configurations suitable for much longer propagation distances?
