Migration guide for typical scenarios-IoT Platform (Deprecated)(IoT)-阿里云帮助中心

Scenario 1

Devices use unique-certificate-per-device authentication and a public instance domain name to connect to IoT Platform.
Devices use custom topics to report data, which is forwarded to your business servers through other cloud products by using the message forwarding feature.
The server calls the Pub API to send messages to devices.

No changes are required on the device side.
Use grayscale migration to verify devices in small batches.
During grayscale migration, configurations for products, message forwarding to cloud products, and AMQP server-side subscriptions are automatically migrated. Enterprise instances do not support MNS server-side subscriptions. Use AMQP server-side subscriptions instead.
Verify that the devices are online and can report data normally.
Verify the Pub API calls and check that your services are running as expected.

The Pub API supports Enterprise instance IDs. You can submit a ticket to request this feature and reduce server-side changes.
Use grayscale batch migration or full migration to migrate existing devices.

Devices use unique-certificate-per-device authentication and a public instance domain name to connect to IoT Platform.
Some devices connect to IoT Platform as sub-devices of a gateway device.
Devices use custom topics to report data, which is forwarded to your business servers through other cloud products by using the message forwarding feature.
The server calls the Pub API to send messages to devices.

No changes are required on the device side. For devices that connect as sub-devices of a gateway device, ensure that the topology remains unchanged during the migration.
Use grayscale migration to verify sub-devices in small batches.
During grayscale migration, configurations for products, message forwarding to cloud products, and AMQP server-side subscriptions are automatically migrated. Enterprise instances do not support MNS server-side subscriptions. Use AMQP server-side subscriptions instead.
Verify that the devices are online and can report data normally.
Verify the Pub API calls and check that your services are running as expected.

The Pub API supports Enterprise instance IDs. You can submit a ticket to request this feature and reduce server-side changes.
Use grayscale migration to verify gateway devices by following Steps 2, 3, 4, and 5.
Use grayscale batch migration or full migration to migrate existing devices.

Devices use unique-certificate-per-product pre-authentication and a public instance domain name to connect to IoT Platform.
Devices use custom topics to report data, which is sent to your business servers through an AMQP server-side subscription.
The server calls the Pub API to send messages to devices.

No changes are required on the device side.
Use grayscale migration to verify device information.
During grayscale migration, products are automatically migrated and a new AMQP server-side subscriber is generated. You must update and verify the server-side application.
Verify that the devices are online and can report data normally.
Verify the Pub API calls and the AMQP server-side subscription, and check that your services are running as expected.

The Pub API supports Enterprise instance IDs. You can submit a ticket to request this feature and reduce server-side changes.
After the grayscale verification is complete, if you have new devices, create them directly in the destination Enterprise instance and verify that your services are running as expected.
Use grayscale batch migration or full migration to migrate existing devices.

The product is defined by using the Thing Specification Language (TSL) model feature. Devices use unique-certificate-per-device authentication and a public instance domain name to connect to IoT Platform.
Devices use Alink topics to report data, which is forwarded to your business servers through other cloud products by using the message forwarding feature.
The server calls the InvokeThingService API to invoke services provided by devices.

No changes are required on the device side.
Use grayscale migration to verify devices in small batches.
During grayscale migration, configurations for products, message forwarding to cloud products, and AMQP server-side subscriptions are automatically migrated. Enterprise instances do not support MNS server-side subscriptions. Use AMQP server-side subscriptions instead.
Verify that the devices are online and can report data normally.
Verify the InvokeThingService API calls and check that your services are running as expected.

The InvokeThingService API supports Enterprise instance IDs. You can submit a ticket to request this feature and reduce server-side changes.
To migrate historical data for TSL model properties, events, and services, enable data synchronization and wait for 7 to 30 days.
After 7 to 30 days, use grayscale batch migration or full migration to migrate existing devices. After the migration, the devices in the Enterprise instance will have historical data from the last 7 to 30 days.