Skip to main content

Example of Integration with ThingPark Wireless

Provisioning application​

Actility demonstrated a fully integrated activation workflow with the following architecture.

ThingPark Activation workflow

Device-specific information is recorded in a QR-code:

  • DevEUI
  • AppEUI
  • ownerToken

An iOS application was developed as a User Portal, so the Subscriber can login with her/his accounts:

  • ThingPark Activation account for JS commissioning
  • ThingPark Wireless account for NS commissioning
  • Busit account for AS commissioning [was hard-coded in the demo]

The User Portal is configured with the following information:

  • Routing Profiles information, indexed by ID
  • Device Profiles info, indexed by ID
  • Mapping AppEUI ð Device Profile ID
  • hNS ID
  • HSM Group ID

When the user logs in the User Portal, it performs the following actions:

  • Application logs into ThingPark Wireless and retrieves available Connectivity Plans.
  • Application logs into ThingPark Activation and creates an ASTK.

When the application scans the QR-code, it performs the following actions:

  • Application queries the user on which Routing Profile ID should be selected.
  • Read DevEUI and ownerToken, use OSS API to claim device ownership.
  • Read AppEUI and map it to Device Profile ID.
  • Call OSS API to provision ThingPark Activation with DevEUI, AppEUI, hNS ID, HSM Group ID and ASTK ID.
  • Call OSS API to provision ThingPark Wireless with DevEUI, AppEUI, Device Profile, Connectivity Plan ID and Routing Profile.
  • Call Busit API to provision AS with DevEUI and ASTK.

The device can then be activated on the ThingPark Wireless network, and only the user accounts and AS Routing Profile ID were queried from the user. All other information was either embedded in a QR-code or retrieves from configuration and APIs.

Last updated on