Message communication billing-IoT Platform (Deprecated)(IoT)-阿里云帮助中心

IoT Platform charges for message communication based on the number of messages.

Billable items

The following table describes the billable items. For a list of billable API operations, see Appendix: Billable API operations.

Item	Description
Message fees (Device-side)	Messages that a device sends by calling the Pub API operation.
	Request messages that a device sends by calling an RPC API operation.
	Response messages that a device sends in response to a server-side revert-RPC (RRPC) call.
	Messages that a device receives by calling the Sub API operation.
	Messages that a device sends or receives through Thing Specification Language (TSL) model API operations.
Message fees (Server-side)	Messages that the server-side sends by calling the Pub or PubBroadcast API operations.
	Messages that IoT Platform pushes to your server when you use Advanced Message Queuing Protocol (AMQP) server-side subscription.
	Response messages that the server-side sends in response to a device RPC call.
	Messages that the server-side sends by calling an RRPC API operation.
	Messages that are generated when the server-side calls sub-device API operations.
	Messages that are generated when the server-side calls device shadow API operations.
	Messages that are generated when the server-side calls TSL model API operations.
Free messages	Connect Connect ACK Disconnect PingReq PingResp Publish ACK Subscribe Subscribe ACK Unsubscribe Unsubscribe ACK Messages forwarded by the data forwarding feature of the rules engine Note The data forwarding feature is free to use. However, if you forward data to other Alibaba Cloud services, you are charged for using those services.

Billing method

Tiered pricing.

Number of messages N (messages/month)	Unit price (CNY/million messages)
N ≤ 100,000,000	1.8
100,000,000 < N ≤ 1,000,000,000	1.4
N > 1 billion	1

Note For the first two months after you activate IoT Platform, you receive a free quota of 1 million messages. To calculate your fees for these two months, we subtract 1 million from your total number of billable messages.

Billing unit:

Charges are based on the number of messages.
Billing is based on the actual number of messages and is not rounded up to the nearest million.

Message count calculation:

A message up to 512 Bytes in size is counted as one message.
If a message exceeds 512 Bytes, it is counted as multiple messages.
The number of messages is calculated by dividing the actual message size in bytes by 512 and rounding the result up to the nearest integer.

Billing and settlement:

Message usage is calculated daily, and bills are settled daily.
Bills are accurate to two decimal places. Any digits beyond the second decimal place are truncated.

Note This information is for reference only. Your actual fees are based on your bill.

Appendix: Billable API operations

Table 1. Device-side billable API operations
Interface	Description
IOT_CMP_OTA_Start	You are charged when you call this API operation to send an MQTT message.
IOT_CMP_OTA_Get_Config
IOT_CMP_OTA_Request_Image
IOT_CMP_Send
IOT_MQTT_Publish
IOT_OTA_ReportVersion
IOT_OTA_RequestImage
IOT_OTA_ReportProgress
IOT_OTA_GetConfig
IOT_Shadow_Construct
IOT_Shadow_RegisterAttribute
IOT_Shadow_Push
IOT_Shadow_Push_Async
IOT_Shadow_Pull
IOT_Subdevice_Register
IOT_Subdevice_Unregister
IOT_Subdevice_Login
IOT_Subdevice_Logout
IOT_Gateway_Get_TOPO
IOT_Gateway_Get_Config
IOT_Gateway_Publish_Found_List
IOT_Gateway_Publish
IOT_Gateway_RRPC_Response
linkkit_answer_service
linkkit_invoke_raw_service
linkkit_trigger_event
linkkit_invoke_fota_service
linkkit_invoke_cota_get_config
linkkit_invoke_cota_service
IOT_CoAP_SendMessage	You are charged when you call this API operation to send a CoAP message.
IOT_HTTP_SendMessage	You are charged when you call this API operation to send an HTTP message.
IOT_CMP_Register	This API operation is free to call. However, you may be charged for the messages you receive after the call.
IOT_MQTT_Subscribe
IOT_Gateway_Subscribe
IOT_Gateway_RRPC_Register

Table 2. Server-side billable API operations
Interface	Description
Pub	Publishes a message to a specified topic.
PubBroadcast	Publishes a broadcast message.
RRpc	Sends a message for an RRPC call.
DeleteDevice	Deletes a sub-device and triggers a message to be sent to `/sys/${productKey}/${deviceName}/thing/delete`.
DisableThing	Disables a sub-device and triggers a message to be sent to `/sys/${productKey}/${deviceName}/thing/disable`.
EnableThing	Resumes a sub-device and triggers a message to be sent to `/sys/${productKey}/${deviceName}/thing/enable`.
NotifyAddThingTopo	Notifies the gateway that a topology relationship is added and triggers a message to be sent to `/sys/${productKey}/${deviceName}/thing/topo/add/notify` .
UpdateDeviceShadow	Updates a device shadow.
InvokeThingService	Calls a device service and triggers a message to be sent to `/sys/${productKey}/${deviceName}/thing/service/${tsl.service.identitier}`.
InvokeThingsService	Calls device services in a batch and triggers messages to be sent to `/sys/${productKey}/${deviceName}/thing/service/${tsl.service.identitier}` .
SetDeviceProperty	Sets device properties and triggers a message to be sent to `/sys/${productKey}/${deviceName}/thing/service/property/set`.
SetDevicesProperty	Sets device properties in a batch and triggers messages to be sent to `/sys/${productKey}/${deviceName}/thing/service/property/set`.