1. Home
  2. Docs
  3. IoTGtw Introduction
  4. Supported Service Access Points (SAP) for IoT Devices

Supported Service Access Points (SAP) for IoT Devices

A SAP is a service connector through which your IoT device can access the IoTGtw data orchestration services.
To make use of one or more service access point(s) the IoT device simply configures the gateway’s IP address and Port as its target IP address. In addition It is recommended for IoT devices to be configured with the correct SAP that provides the required encryption (i.e. DTLS), transport (i.e. UDP or TCP) and application protocols such as CoAP, MQTT-SN, LwM2M etc.:

Shared SAP

By default a number of shared SAP are freely accessible. These SAP can be freely used and requires no special subscriptions.

 

Private SAP

Private SAPs are SAP deidcated to specific customer accounts. Dedicated SAPs comes in all the supported SAP protocol and framework combinations and in any service region(s) according to the customer preference. A private SAP is only visible in the customer account, it enforces strict device access policy and restricts access only to the customer devices or subset of the customer devices depending on the customer service template configurations.

 

Note:

  • TCP Usage: Available for Private SAP only
  • MQTTSN 1.2:  QoS Supported: QoS -1 (additional QoS: 0 or 1 also supported).
  • CoAP Service: Based on IETF core-coap-18 specification.
  • SimplyTiny service: Is a simple string format designed to convey IoT messages in a wide range of use cases even simply tiny sensors can use it out of the box (no special libraries required).
  • SimplyTiny provides support for: Device Authentication, Device bootstrapping, Message Acknowledgement, Periodic Auth token update/refresh, Keep-alive, SAP list retrieval by device (list configurable by the device service template), Device shadow copy update which can be directly viewed on the portal and portal map as well as retrieved via APIs. Device shadow copy includes gps coordinates, signal strength information, power usage information, device timestamp, etc.
  • CUSTOM JSON: Provides support for extracting the required key and values from customer specific JSON structure such as AWS IoT shadow JSON structure or any JSON formatted IoT content.

 

Advanced Details (SAP Configurations)

Protocols and Data Frameworks
  • SimplyTiny over raw socket (raw_simplytiny)
  • SimplyTiny over CoAP         (coap_simplytiny)
  • SimplyTiny over MQTT-SN  (mqttsn_simplytiny)
  • LwM2M                                (coap_LwM2M)
  • Blob over CoAP                   (coap_blob)
  • Blob over MQTT-SN            (mqttsn_blob)
  • Blob over Raw Socket         (raw)
  • CUSTOM JSON framework over any of the above protocols and or framework
  • All the above Transported over TCP or UDP or DTLS/UDP

 

Private SAP and Shared SAPs are available in different setups to support broad range of IoT devices and customer use cases.

Shared SAPs are freely available on all accounts and come in configuration: #2, #4, #6

Private SAPs are customer specific and come in all configuration: #1, #2, #3, #4, #5, #6.

 

1# [RAW Socket]

This SAP type is purely for opaque data pass through

Device identified by either

  •  static_ip
  •  static_ip + pre-defined SAP(s)
  •  static_ip + static_port + pre-defined SAP(s)

Device Application Data: Blob / Any

Application Data Transport: Blob directly over TCP or UDP

Acknowledgement Supported: Yes – Device Assisted Ack (if required)

Device Shadow Copy Supported: No

 

#2 [RAW_SimplyTiny]

This SAP type supports opaque data pass through + meta-data ingestion for the Device shadow copy service

Device identified by: udid + device_token

Device Application Data:  Blob + Meta-data (optional)

Application Data Transport: Blob + Meta-data inserted in SimplyTiny (transported over TCP or UDP)

Acknowledgement Supported: Yes

Device Shadow Copy Supported: Yes

 

#3 [MQTT-SN Blob]

This SAP type is purely for opaque data pass through

Device identified by either

  • static_ip
  • static_ip + pre-defined SAP(s)
  • static_ip + static_port + pre-defined SAP(s)

Device Application Data: Blob

Application Data Transport: Blob inserted in MQTT-SN (transported over UDP or TCP)

Acknowledgement Supported: Yes

Device Shadow Copy Supported: No

 

#4 [MQTT-SN SimplyTiny]

This SAP type supports opaque data pass through + meta-data ingestion for the Device shadow copy service

Device identified by: udid + device_token

Device Application Data: Blob + Meta-data (optional)

Application Data Transport: Blob in SimplyTiny, SimplyTiny in MQTT-SN (Transported over UDP or TCP)

Acknowledgement Supported: Yes – Single Ack or Dual Ack (SimplyTiny Ack and or MQTT-SN Puback)

Device Shadow Copy Supported: Yes 

 

#5 [CoAP Blob]

This SAP type is purely for opaque data pass through

Device identified by either

  • static_ip
  • static_ip + pre-defined SAP(s)
  • static_ip + static_port + pre-defined SAP(s)

Device Application Data: Blob

Application Data Transport: Blob inserted in CoAP (transported over UDP or TCP)

Acknowledgement Supported: Yes

Device Shadow Copy Supported: No

 

 

#6 [CoAP SimplyTiny]

This SAP type supports opaque data pass through + meta-data ingestion for the Device shadow copy service

Device identified by: udid + device_token

Device Application Data: Blob + Meta-data (optional)

Application Data Transport: Blob in SimplyTiny, SimplyTiny in CoAP (Transported over UDP or TCP)

Acknowledgement Supported: Yes – Single Ack or Dual Ack (SimplyTiny Ack and or CoAP Ack)

Device Shadow Copy Supported: Yes 

 

 

 

 

Was this article helpful to you? Yes No

How can we help?