Technical Guidelines for Satellite IoT Connectivity

Network Configuration

To establish a successful data session:

• The device APN must be configured to: flolive.net
• The device must support 3GPP Release 17 NTN
• Required certification must be completed

Understand Satellite-Specific Network Characteristics

Satellite connectivity introduces characteristics that differ from terrestrial networks.

These include:

• Longer propagation delays
• Higher latency compared to terrestrial networks
• Doppler effects due to satellite movement (particularly in LEO systems)
• Beam switching as satellites move relative to devices

These factors may impact application design, particularly for latency-sensitive or high-frequency transmission use cases.

Design Considerations

• Avoid frequent ping-ponging between TN and NTN.
• Configure Skylo attach profiles with longer PSM/eDRX cycles.
• Ensure network selection and switching behavior are properly validated to prevent unintended satellite usage.

Plan Hybrid Satellite–Terrestrial Architecture

It is important to configure deployments so that terrestrial cellular connectivity is prioritized, with satellite used as fallback when required.

Recommended Configuration:

• Prioritize terrestrial cellular connectivity
• Use satellite as fallback when cellular coverage is unavailable

Switching Methods:

Cellular → Satellite

• Can occur automatically based on signal conditions (if supported by the module)
• Can be triggered using device-level APIs controlling network selection

Satellite → Cellular

• Typically managed via device logic or API once terrestrial coverage is restored
• Switching logic should be defined and validated during device integration testing.

For more detailed support reach out to support@velocityiot.com

Connectivity Recovery & Network Selection Process - NTN Use Case

1. Normal Operation  

The device is operating within cellular coverage, maintains an active connection, and is transmitting data.  

2. Connection Loss  

• The cellular connection is dropped.  
• After a predefined timeout expires, the device initiates a network recovery sequence.  

3. Cellular Network Scan  

• The device scans for available cellular networks using the AT+COPS=? command.  
• If cellular networks are available:  

Allow the device to iterate through available IMSIs.  

Attempt registration on an alternate cellular network to restore connectivity.  

• If no cellular networks are available:  

Proceed to NTN fallback mode.  

4. NTN Fallback Procedure  

• Configure the modem to operate in NTN mode.  
• (Optional) Perform a network scan using the AT+COPS=? command.  
• If an NTN network is available:  

Configure the device for NTN-specific operation using the minimum required data profile.  

Cycle through IMSIs to reach the NTN-designated IMSI   

Or  

Manually configure the SIM to use the NTN IMSI.  

5. Periodic Cellular Availability Check  

• At a defined interval (every N minutes):  

1. Switch the modem to cellular mode.  
2. Scan for cellular networks using AT+COPS=?  

If no cellular network is found:  

Return the modem to NTN mode.  

Continue periodic cellular coverage checks.  

• If a cellular network becomes available:  

Switch the device back to normal cellular mode (full data-flow mode).  

Allow the SIM to cycle through IMSIs to register with a cellular carrier   

Or  

Manually configure the SIM to the appropriate cellular IMSI.  

For more detailed support reach out to support@velocityiot.com

Best Practices for Satellite Usage

Satellite connectivity should be optimized for low-throughput IoT use cases.

Recommended guidelines:

• Keep payload size under 1 KB where possible
• Limit total daily NTN data usage to approximately 100 KB
• Compress and batch data
• Resume high-volume transmissions once terrestrial coverage is restored

Velocity IoT’s Satellite NTN service supports data connectivity only. SMS, voice, and streaming services are not supported.

Satellite Connectivity Performance

• Maximum: 2 messages per minute
• Maximum payload per message: 256 bytes
• Expected uplink latency: 10–20 seconds
• Expected downlink latency: 3–15 seconds

Performance may vary depending on satellite position, signal conditions, and device configuration.