November 12, 2024
Is there a standard for SatCom?
Traditionally, Satellite Communication used proprietary solutions from SatCom service providers. But if SatCom is to be more widespread, it will have to be standardized and interoperable (among multiple service providers). And such standards for SatCom already exist. The biggest name in this regard is “NTN” – Non-terrestrial Networks, as defined by the standards organization 3GPP (the same organization that defined 3G and 4G LTE and is now defining 5G).
NTN was introduced in 3GPP’s Release 17 (the standards are published in versions or “releases” that build upon the previous releases) and allowed Narrowband IoT operation in two designated bands (n255 around 1.5 GHz and band n256 around 2 GHz). That means that with R17, devices could directly communicate with satellites operating in this band and exchange small amounts of data like SMS.
In further 3GPP releases, more bands and more capabilities are/will be added to NTN. The goal is to achieve broadband internet type of service using SatCom. Though, even if we reach the broadband data-rates, the latencies (delays) can’t be as small as land-based (“terrestrial”) networks. But that will already be extremely useful for non-real-time applications like data download and to some extent (if the user has the patience for it), some real-time applications like an audio call.
Is SpaceX’s SatCom also NTN? If no, what is it?
SpaceX’s “Direct to Cell (DTC)” service is a prime example of SatCom. DTC allows mobile phones, your normal 4G mobile phones to connect with a satellite in a 4G LTE band, just like you would connect to a 4G base station located on earth. How is this possible without special devices?
SpaceX collaborated with T-Mobile (Deutsche Telekom) for this. Probably, SpaceX provided the satellite and the launching space part and T-Mobile provided the base station on-board satellite part. And while it’s a cool thing for the mobile phone user, it’s not entirely NTN. It uses a band that is not defined by 3GPP for NTN. But it does (and must) comply with 4G LTE specifications by 3GPP. It’s not clear if the solution supports a handover from satellite base-station to terrestrial base-station though … and without a call drop!
So, will the industry choose NTN or a proprietary solution?
Well, that’s for the industry to decide. NTN is usually a safe and trusted solution because a) it’s standardized and well tested and b) it allows interoperability among multiple service providers. But these standards take time to be developed and also restrict (to some extent) the use of “create” proprietary solutions by companies. That’s why proprietary solutions can be a great alternative. Yes, they might bind you to one specific company’s products/services but if those products/services are great, you don’t mind that. Plus, such proprietary solutions can be developed more quickly and can also be preferred due to the “exclusiveness” factor they offer (Apple has proven it for decades).
So, nobody can really say right now if the SatCom world would come to be dominated by NTN or proprietary solutions. It is quite likely that some industries might continue to leverage the existing (or new) proprietary solutions while others prefer NTN. We’ll just have to wait and see!
WirelessMobility is a producer of electronic modules for wireless communications (4G, 5G, Wi-Fi, NB IoT, Bluetooth etc.) and is already developing NTN Satellite Communication modules for the automotive industry. You can’t have SatCom without NTN-enabled devices and WirelessMobility is there to provide them.
