What problems does IMT CC actually solve?
Series Building with the Iridium 9704 Part 2 of 10
In short
Cloud queues, message tracking, re-ringing, large-file segmentation and storage.
IMT is designed for the cloud, which also means the back end is yours to build. For most hardware teams, that half of the work is as large as the device itself:
| Task | Do it yourself | With IMT CC |
|---|---|---|
| Cloud queues | Your own AWS account, Topics requested from a provider, queues and cross-account permissions | Already set up by N3D; send and receive with a token |
| Where is my message? | Log sending, queueing, delivery and failure yourself | Each message's progress follows Iridium's actual reports |
| Device missed the ring | Decide when and how often to ring again | The platform rings again after an interval |
| Order of several MTs | Queue them yourself so a device does not get several at once | One at a time per device; one stuck device does not hold up the rest |
| Files over 100 KB | Design segmentation, reassembly and gap filling | Delivered in segments by the platform, currently at no extra charge |
| Your server goes down | Messages may be lost | Uncollected messages are kept for 7 days; with storage on, a one-year backup |
| Development and debugging | Write your own test tools | Web console for text, images and voice; dev kit round-trip tests; one-click firmware updates |
The biggest benefit: one thing at a time
During development, IMT CC is your back end. Once the firmware is solid, your server calls the same API and nothing changes on the device. When a message does not arrive, the console shows which step it is stuck at, so you do not have to guess whether the device or the server is at fault.
Your data stays yours
You decide in the console whether messages are stored, and N3D staff cannot change it for you. By default, content is deleted once delivered; with storage on, messages are backed up for a year and can only be retrieved through your own channels.
Sources
- Features and storage rules: N3D IMT CC product page.
- Topics, Amazon SQS, cross-account authentication: Iridium, "Iridium Messaging Transport (IMT)".
If I later connect to CloudConnect myself, does the device change?
The device sends standard IMT messages, so changing the back end does not change the device. Large-file segmentation is an IMT CC feature, though, so you would have to build it yourself.
I already have a server. Do I still need IMT CC?
Having a server is not the same as having the CloudConnect part. IMT CC sits between the two, and your server only calls the API.
All parts in this series
From developer kit to certified product: what an Iridium 9704 product needs, the limits of the developer kit, why certification matters, how to choose hardware, where it fits, and measured timing and power. Ten parts, in order, each readable on its own.
- What do you need to build an Iridium 9704 product?
- What problems does IMT CC actually solve?
- What are the limits of the Iridium 9704 Launch Pad?
- Why do 9704 products need certification, and what does it cover?
- Who is the RockBLOCK 9704 for?
- Launch Pad, N-9704, RockBLOCK 9704 or your own design: which should you choose?
- Where can the IMT 9704 be used? Mountain rescue, maritime and monitoring
- How should power be designed for the 9704?
- Why can an IMT message take several minutes?
- How does the Iridium 9704 compare with Starlink and OneWeb?
Related notes
Related hardware
Related services
Updated 2026-10-27
N3D supplies satellite communication for alpine and industrial use. See services