Obtaining Resources
Platform Connection Information
Before connecting applications and devices to the IoT platform, you must obtain platform access addresses.
|
Platform Environment |
How to Obtain |
|---|---|
|
IoT Device Access |
Log in to the IoTDA console, access the Overview page, and view the device and application access addresses.
Figure 1 Shared domain name
For users who have subscribed to IoTDA since 00:00 on July 14, 2020 (Beijing time), the platform allocates a unique region-level ID to each user based on the shared domain name. Users can connect to the platform using their independent domain names. If you want to change a device from Basic Edition to Enterprise Edition and use a domain name for device access, you do not need to modify devices. Contact Huawei engineers to migrate data.
Figure 2 Independent domain names
Note: You can still use the shared domain name to access the platform. |
|
Log in to the IoTDA console, choose , click Details to open the instance details page, and click Preset Access Credential to preset the accessCode and accessKey.
|
Device Development Resources
The platform allows device access using MQTT or LwM2M over CoAP. Devices can connect to the platform by calling APIs or integrating with SDKs.
|
Resource Package |
Description |
Download Link |
|---|---|---|
|
IoT Device SDK (Java) |
Devices can connect to the platform by integrating the IoT Device SDK (Java). The demo provides sample code for calling SDK APIs. For details, see IoT Device SDK (Java). |
|
|
IoT Device SDK (C) |
Devices can connect to the platform by integrating the IoT Device SDK (C). The demo provides sample code for calling SDK APIs. For details, see IoT Device SDK (C). |
|
|
IoT Device SDK (C#) |
Devices can connect to the platform by integrating the IoT Device SDK (C#). The demo provides sample code for calling SDK APIs. For details, see IoT Device SDK (C#). |
|
|
IoT Device SDK (Android) |
Devices can connect to the platform by integrating the IoT Device SDK (Android). The demo provides sample code for calling SDK APIs. For details, see IoT Device SDK (Android). |
|
|
IoT Device SDK Tiny (C) |
Devices can connect to the platform by integrating the IoT Device SDK Tiny (C). The demo provides sample code for calling SDK APIs. For details, see IoT Device Tiny SDK (C). |
|
|
Native MQTT or MQTTS access example |
Devices can be connected to the platform using the native MQTT or MQTTS protocol. The demo provides sample code for SSL-encrypted link setup, TCP link setup, data reporting, and topic subscription. |
|
|
Product model template |
Product model templates of typical scenarios are provided. You can customize product models based on the templates. For details, see Developing a Product Model Offline. |
|
|
Codec example |
Demo codec projects are provided for you to perform secondary development. For details, see Offline Codec Development. |
|
|
Codec test tool |
The tool is used to check whether the codec developed offline is normal. |
|
|
NB-IoT device simulator |
The tool is used to simulate the access of NB-IoT devices to the platform using LwM2M over CoAP for data reporting and command delivery. For details, see Developing Products on the Console. |
|
|
IoT Link Studio (originally named IoT Studio) |
IoT Link Studio is an integrated development environment (IDE) developed for the IoT Device SDK Tiny. It provides one-stop development capabilities, such as compilation, programming, and debugging, and supports multiple development languages like C, C++, and assembly language. For details, see Developing a Smart Street Lamp Using NB-IoT BearPi. |
Application Development Resources
The platform provides a wealth of application-side APIs to ease application development. Application development is the process in which an application calls platform APIs to implement service scenarios such as secure access, device management, data collection, and command delivery.
|
Resource Package |
Description |
Download Link |
|---|---|---|
|
Application API Java Demo |
You can call application-side APIs to experience service functions and service processes. For details, see Java Demo. |
|
|
Application Java SDK |
You can use Java methods to call application-side APIs to communicate with the platform. For details, see Java SDK. |
|
|
Application C# SDK |
You can use C# methods to call application-side APIs to communicate with the platform. For details, see C# SDK. |
|
|
Application Python SDK |
You can use Python methods to call application-side APIs to communicate with the platform. For details, see Python SDK. |
Certificates
To connect a device to the platform in some scenarios, you must load a certificate to the device.
This certificate applies only to the platform and must be used together with the device access domain name.
The table below describes the certificate type, format, and usage.
|
Certificate Package Name |
Certificate Type |
Certificate Format |
Description |
Download Link |
|---|---|---|---|---|
|
certificate (Basic edition in CN North-Beijing4) |
Device certificate |
pem, jks, and bks |
Used by a device to verify the platform identity. The certificate must be used together with the device access domain name. Note: The old domain name (iot-acc.cn-north-4.myhuaweicloud.com) must be used together with the old certificate. |
|
|
certificate (Standard edition in CN North-Beijing4) |
Device certificate |
pem, jks, and bks |
Used by a device to verify the platform identity. The certificate must be used together with the device access domain name. |
|
|
certificate (Standard edition in CN East-Shanghai1) |
Device certificate |
pem, jks, and bks |
Used by a device to verify the platform identity. The certificate must be used together with the device access domain name. |
|
|
certificate (CN North-Beijing4) |
Application certificate |
pem |
Used by the application to verify the platform identity in the subscription/push scenario. |
Last Article: Before You Start
Next Article: Product Development
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.