Pricing-Related Metering Objects in Public Cloud¶
In the public cloud environment, EnOS Cloud Enterprise Edition will meter the basic services within an OU based on the number of messages. The metering will be performed using the count of messages as the basis for pricing.
Applicable Scope¶
The message count metering applies to the following scope:
only to the public cloud environment and not to the private cloud environment.
only to the Enterprise Edition and not to the Lightweight Edition.
EnOS Cloud version 2.4.0 and above.
The specific products, services, and functional modules to which it applies are determined by the contract terms.
Message Scope¶
Messages refer to the messages transmitted between the device side and the service side with EnOS Cloud, including:
Device-side messages:
Messages transmitted directly between devices and EnOS Cloud via the protocols such as MQTT and HTTP.
Messages transmitted between EnOS Edge or third-party Edge gateway devices and EnOS Cloud. Only messages transmitted between “gateway devices ↔ EnOS Cloud” are counted, excluding messages transmitted between “sub-devices ↔ gateway devices”.
Messages integrated in real-time or offline from third-party clouds or systems by EnOS Device Data Integration Service (input messages), as well as forwarded messages after processing (output messages).
Service-side messages: Messages returned by the APIs when applications or systems call EnOS services and data.
Message Definition¶
In Metering Management, the size of an EnOS standard message is 512 bytes. Metering Management will calculate the amount of data transmitted and convert it into the number of messages per hour based on 512 bytes/message. The part that is less than 512 bytes is counted as 1 message.
If a data transmission process includes a file, the file part will be converted into the number of messages based on its data size.
The amount of data returned by each API call will be converted into the number of messages.
For example, if a total of 523 bytes of MQTT data transmission is counted within an hour, in which the file part is 500 bytes and the other part is 23 bytes, it will be counted as 2 message.
Note
In EnOS Device Connection and Management, the message count is calculated based on the actual number of messages received and sent by EnOS Cloud, without considering the size of the transmitted data.
For example, if EnOS Cloud receives a message with a data size of 1,000 bytes, it will be counted as 1 message in Device Connection and Management. However, in Metering Management, it will be converted to 2 messages based on a calculation of 512 bytes per message.