Skip to main content

Activating Subscribers on ThingPark Activation

As a Network Operator, the onboarding of the Subscriber must also allow the onboarding onto the ThingPark Activation platform.

Network Operator may use two options:

  • Allow a simple and unified user experience for her/his Subscriber and integrate the Operator portal with ThingPark Activation API.
  • Differentiate this additional service and provide a dedicated ThingPark Activation account to her/his Subscriber.

Using Key Manager APIs for MNO integration​

Using an Operator account or a dedicated Subscriber account, the Operator portal can perform OSS API in order to commission the Device in ThingPark Activation.

OSS API integration​

ASTK can be created with OSS API using:

POST /kmSubscriptions/{kmSubscription}/asKeys

For Operators integrated with OSS API, the Device can be claimed on ThingPark Activation using:

POST /kmSubscriptions/{kmSubscription}/devices/claim

And updated using:

POST /kmSubscriptions/{kmSubscription}/devices/{device}

With parameters

  • asKey: ASTK
  • homeNsNetID
  • hsmGroupID

Check the Tutorial for OSS API example.

Using Key Manager UI​

The Network Operator can also expose the ThingPark Wireless Key Manager User Interface to the Subscribers with a ThingPark Activation account.

Once logged in, the Subscriber can create new ASTK using AS Keys Create menu.

Create ASTK

It can then Claim Device ownership using Claim in the Devices’ menu, then input the DevEUI and ownerToken that were transmitted out-of-band.

Claim device 1

Claim device 2

Finally, ASTK and hNS NetId are associated with the Device in the Device edition.

Select ASTK

Last updated on