What is M2M Messaging?
Machine-to-Machine (M2M) is a process that implies wireless communication between two or more physical assets. There is no human interaction in the Machine-to-Machine campaign. Subscriber-facing campaigns are prohibited when selecting the Machine-to-Machine use case.
The main purpose of machine-to-machine communication is to collect data and transmit it to a network. For example, a vending machine can message the distributors network, or machine, when a particular item is running low to send a refill.
It’s essential to understand that message programs involving IoT (Internet of Things), often utilize both M2M messages and subscriber-facing messages (e.g., user alert notifications). Below are a few examples of different message programs with an IoT use case.
|
IoT Use Case
Example
|
M2M Text
Example
|
User-Facing
Text Example
|
|
Security Alarms Panel
Monitor security systems designed to protect homes, businesses, and other properties.
|
A central system exchanges information via text to a remote garage door sensor node for status updates and other sensor readings.
|
A central system texts the end user that the garage door is open.
|
|
Fleet Management
Real-time monitoring, tracking, and optimization of various aspects of fleet operations.
|
A central system exchanges information via text to sensors in a vehicle to monitor various mechanical and operations parameters.
|
A central system texts the fleet manager that a vehicle’s tire pressure is too low.
|
|
Inventory Management
RFID-enabled products in a retail store track their location and stock levels.
|
An inventory management system exchanges information via text to RFID-enabled products for a presence status update to determine stock levels.
|
The inventory management system notifies the store owner via text of low-stock levels.
|
|
Cattle Agricultural
Monitoring
Track and manage the well-being and behavior of cattle for various purposes.
|
A central system sends a text to initiate a device-wakeup function towards sensor nodes embedded in the cattle to run vital signs such as heart rate and temperature.
|
A central system will message the farmer when it detects signs of distress of cattle due to elevated temperatures and heart rate.
|
In alignment with industry best practices and standards, M2M message programs should never interact with the end consumer. As a result, these must be separate messaging programs used for IoT into two different campaigns:
- An IoT message program to facilitate M2M messages
- An IoT message program to handle user-facing messages
Campaign Requirements for USER-Facing IoT Programs:
For IoT user-facing messaging programs, follow the standard 10DLC Compliance Guidance check list.
- Brand details need to align, such as, brand/company being registered, support email, website domain, etc.
- CTA/Message Flow needs to be clear with required disclosures.
- Opt in MT, Stop MT, and Help MT are required with necessary compliance disclosures and help details. (Phone number, email or contact us page.)
- PP and TCs are to be vetted as normal.
- Example messages need to identify brand name and include STOP statement and align with use case described.
Campaign Requirements for M2M IoT Programs:
- Messaging should be templated.
- Should be 1-way messaging.
- Opt In MT is not required for M2M use cases.
- Opt Out MT is not required for M2M use cases.
- Help MT is still required for ALL use cases per TCR.
- PP and TC’s do not need to be vetted for M2M use cases.
- The use case should be as detailed as possible to confirm it is indeed M2M and there is no subscriber interaction.
- The client should describe in detail how the process works. What machines are communicating with one another, what is the purpose, etc.
- The registered brand details should align. Brand name, point of contact, support email, etc., to ensure the legitimacy of the company.
