Help Center> IoT Device Access> User Guide> Message Communications> M2M Communications> Usage
Updated on 2024-01-17 GMT+08:00
View PDF

Usage

Process

This section takes one-to-one communications between devices as an example.

Figure 1 M2M communication process

  1. Rule and topic setting: Create an M2M data forwarding rule and set a forwarding topic on the console.
  2. Policy configuration: On the console, configure policies to allow devices that send and receive data to publish and subscribe to data.
  3. Device authentication: Devices A and B initiate connection authentication requests. For details about authentication parameters, see Device Connection Authentication.
  4. Topic subscription: Device B subscribes to a cloud-based topic that is set during the data forwarding rule creation. If the subscription is successful, the platform returns an ACK message.
  5. Data reporting: Device A publishes data through the cloud-based topic. If the publishment is successful, the platform returns an ACK message.
  6. Data receiving: If the data forwarding is successful, device B receives the data from device A.

Procedure

The following example describes how to create a data forwarding rule on the platform. You can modify the rule for different scenarios.

  1. Access the IoTDA service page and click Access Console. In the navigation pane, choose Rules > Data Forwarding.

    Figure 2 Data forwarding page

  2. Click Create Rule, configure the parameters based on the service requirements, and click Create Rule. The following figure shows an example.

    Figure 3 Creating a data forwarding rule
    Table 1 Parameters for creating a data forwarding rule

    Parameter Description

    Rule Name

    Customize a value, for example, test. The value can contain up to 128 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed.

    Description

    Description of the rule, which is user-defined.

    Data Source

    Data source of the forwarding rule. You can select multiple data sources from the drop-down list. In the M2M scenario, select Device message.

    Trigger

    Available trigger events vary with the data sources. In the M2M scenario, select Device message reported.

    Resource Space

    Select an existing resource space from the drop-down list or create a Resource Space first.

    SQL Filter Statements

    You can use SQL statements to filter data. For details, see SQL Statements. In the example figure, notify_data.body.topic IN ('/test/M2M') in the WHERE statement indicates that only the data whose topic is /test/M2M will be forwarded.

  3. Go to the second stage. You can set the data forwarding target, topic, and cache time. In M2M scenario, select Device for Forwarding Target, set the parameters based on service requirements, and click OK.

    Figure 4 Setting the forwarding target
    Table 2 Parameters for setting a forwarding target

    Parameter Description

    Forwarding Target

    Select a forwarding target from the drop-down list. In the M2M scenario, select Device.

    Topic

    Customize a data forwarding topic with up to 128 characters. The value cannot start with $oc or end with dollar signs ($) or slashes (/). If this parameter is set to $topic(), the data input topic is used.

    ttl

    The platform caches messages when a device is offline, and delivers them when the device comes back online. ttl is the data cache time whose value ranges from 0 to 1440 (one day) minutes and must be a multiple of 5. When the value is set to 0, data is not cached.

  4. Go to the third stage and enable the rule. The rule creation is complete.

    Figure 5 Enabling the rule

Parent topic: M2M Communications