India's Telecom Regulations

India's multi-year system requiring registration of entities, headers, and content templates for bulk SMS, using Distributed Ledger Technology, along with Do Not Disturb registration for consumers.

← Back to The Australian Government to Require SMS/MMS Sender ID Registraion

India’s long-standing telecom regulations require all bulk SMS senders, including international entities, to register their headers and content templates on a Distributed Ledger Technology (DLT) platform to ensure only authorized messages reach consumers. This structured system integrates a "Do Not Disturb" registry and utilizes specific alphabetic identifiers to help users easily distinguish between promotional, service-related, and government communications. While the framework is effective at rejecting ad hoc or unregistered messages, some observers note that similar results can be achieved through traditional databases without the added complexity of a blockchain-based system.

3 comments tagged with this topic

View on HN · Topics
In India this has been the regulation for several years, and has helped along with the Do Not Disturb (DND) registration by the end user and rules for senders/callers. Anyone sending bulk SMSes, even if the sending is done through a third party provider like AWS from another country/region, will have to register. [1] The entity, the header, content template (which allows two or three variables/placeholders) need to be registered. A Distributed Ledger (DLT) is used to store these. Ad hoc messages without a registered template are expected to be rejected by the telco. [1]: https://trai.gov.in/advice-to-senders
View on HN · Topics
And as we can see from Australia, this doesn’t need a blockchain.
View on HN · Topics
India has something similar, and even goes a step further by having last alphabet as an identifier for Promotional, Services, Govt. etc. https://www.trai.gov.in/advice-to-senders