A service profile (further referred to as service template) is used to define the service configuration profile that can be applied to one or more devices. Every device must be associated to a service template. Multiple devices can re-use the same service template.When a message is received from the IoT device or from the customer upstream application, the services configuration settings of the service template linked to the device is used to determine what services, rules and or features are required to be applied.
For example, based on the service template configuration, the service determines whether service access point restriction is enabled, what notification events are enabled, the flow control to use for data transmission to the device, determine if or at what point traffic transformation is required and whether to store and or terminate data flows to customer applications, etc.
When a service template state is set to “disabled”, the devices linked to that service template are considered temporarily disabled and cannot use the IoTGtw services.
Further, the service templates configuration is used to determine which Upstream Application to use for terminating uplink messages to the customer systems.
Multiple Upstream Applications Profiles can be specified on the service template. When the application endpoint defined in the primary Upstream Application profile is unreachable, the application configured in the secondary profile (if configured) will be used as the upstream application endpoint for the uplink message. Otherwise the uplink message is stored for later delivery/retrieval, that is if the storage services are enabled in the meta-data and or payload storage policy section of the service template).
Other services that are can be configured on the Service Template are:
Default Downlink Delivery Settings
- This section defines the default settings to use for delivering downlink messages received from your upstream applications to the device.
- The parameters (such as target device port) providded in individual incoming downlink messages will take precedence over the default values.
Refer to the service template parameter section for an overview of the service template configuration fields and descriptions.