> For the complete documentation index, see [llms.txt](https://docs.naorisquantumprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.naorisquantumprotocol.com/use-cases/telecom-and-iot.md). # Telecom & IoT **End-to-end trust across millions of devices.** Telecommunications and IoT estates are defined by scale and heterogeneity: many devices, many vendors, long replacement cycles, and limited per-device compute. ## Why it fits * **Scale** — API-first and container-ready, with post-quantum collaborative verification at scale * **No rip-and-replace** — deploys beneath existing infrastructure rather than requiring device replacement * **Continuous** — devices are verified continuously rather than at provisioning time only * **Vendor-neutral** — trust does not depend on any single manufacturer's attestation ## Typical applications * Network function and base station integrity * Subscriber equipment and edge device verification * Industrial IoT fleets * Smart metering and utility endpoints --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.naorisquantumprotocol.com/use-cases/telecom-and-iot.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.