Alibaba Cloud IoT Platform offers an event response service. You can configure scenario definitions and actions to receive notifications for device status changes and reported property data. This topic describes the workflow for using the event response service.
Features
The event response service is supported only by Enterprise instances and new public instances in the China (Shanghai) region. You can choose between the Free Edition and the Commercial Edition:
Free Edition: You can try the event response service for free.
Commercial Edition: You can purchase a resource plan to activate the Commercial Edition of the event response service.
Compared to the Free Edition, the Commercial Edition includes a paid text message notification feature and has higher specification limits.
For more information about billing for the Commercial Edition, see Service billing.
Limits
The specification limits for features differ between the Free Edition and the Commercial Edition. For more information, see the following table.
Specification | Description | Free Edition limit | Commercial Edition limit |
Scenario | The maximum number of scenarios that can be created per instance. | 20 | 200 |
Scenario event | The maximum number of events processed per hour per instance. Important If one event triggers multiple scenarios, it is counted multiple times. | 500 | 5000 |
Scenario action | The maximum number of actions executed per hour per instance. | 100 | 2000 |
Contact | The maximum number of contacts supported per instance. | 100 | 500 |
Contact group | The maximum number of contact groups supported per instance. | 10 | 50 |
Text message notification | The maximum number of text message notifications sent per instance. | Not supported | Limited by the purchased resource plan. For more information, see Service billing. |
The maximum number of text messages that can be sent to a single mobile number per day. | Not supported | 50 | |
DingTalk Robot notification | The maximum number of messages that a DingTalk Robot can send to a group per minute. | 20 Important If the number of messages exceeds 20, throttling is triggered for 10 minutes. | |
Scenarios
The event response service can be used for operations and maintenance (O&M) or business operations in complex Internet of Things (IoT) scenarios. For example:
Industrial scenarios
You can assess the health of production equipment by analyzing multi-dimensional data, such as temperature, vibration, noise, and speed from multiple devices. If the equipment's health becomes abnormal, the system promptly notifies an O&M engineer to inspect and repair it. This prevents production interruptions, defective products, and equipment damage from impacting production capacity.
Healthcare
You can monitor a patient's blood pressure, heart rate, and activity status, and combine this data with factors such as region, altitude, time, and temperature to determine if medical intervention is needed. This approach can reduce the medical burden on patients while ensuring their safety.
Workflow
Prerequisites
Activate IoT Platform. Ensure the service is a new public instance or an Enterprise instance.
NoteActivating the service is free. After activation, you can start a free trial of IoT Platform. For more information about the free trial, see IoT Platform products for Alibaba Cloud free trial. For more information about billing, see Billing overview. For more information about instances, see Instance overview.
Create a product and a device in your instance. Complete the device-side development and connect the device to IoT Platform.
Define a scenario
You can define the scenario in the Event Response Service console:
Optional: Create a contact or create a contact group.
If you plan to notify a contact or contact group when a scenario rule is triggered, you must first create the contact or contact group.
Configure scenario events, trigger conditions, and actions. If a device's behavior meets the specified events and conditions, the system executes the defined actions. For example, the system can notify a specific contact or contact group.
Start the scenario rule to activate it.
Event response
After a scenario rule is created and started, the system executes its defined actions when a scenario event is triggered. For example, if the action is to notify a contact, the system sends a notification to the specified contact or contact group using the configured channel and template.
Administrators can manage scenario rules for an instance in the event response console. For example, they can modify or delete scenario definitions and actions, or change the running status of a scenario. For more information, see Other scenario operations.