Cellular tunnel interface
LRC to Application Server Tunnel Interface
This section describes the reports that are generated from the LRC to an Application Server.
OpenAPI contract
An OpenAPI contract is available for this API:
- OpenAPI v3.1: tunnel-lrc-to-as-cellular.openapi.yaml
- OpenAPI v3.0: tunnel-lrc-to-as-cellular.openapi-3.0.yaml
Uplink Frame Report
The purpose of this report is to tunnel:
-
An applicative payload received from a device in an uplink packet using message mode.
-
A session event notifying the creation, update or deletion of the device session.
-
A microflow event aggregating uplink and downlink direct IP mode usage on a given period.
Application Server to LRC Tunnel Interface
This section describes how the downlinks are sent from the AS to a device.
OpenAPI contract
An OpenAPI contract is available for this API:
- OpenAPI v3.1: tunnel-as-to-lrc-cellular.tpe-subscriber.openapi.yaml
- OpenAPI v3.0: tunnel-as-to-lrc-cellular.tpe-subscriber.openapi-3.0.yaml
Downlink Frame
Payload Encryption
The following HTTP/POST message format is used to tunnel the frame payload and associated metadata from the target application server to the LRC. The application server acts as an HTTP client and the reverse HTTP proxy (PROXY_HTTP server) acts as an HTTP server. Rerouting of the HTTP request to the primary LRC or the backup LRC is handled by the reverse HTTP proxy.
This POST command can be generated easily by tools such as curl or POSTman:
curl -H "Content-type:application/x-www-form-urlencoded" -X POST "https://api.thingpark.com/thingpark/lrc/rest/downlink?DevEUI=000000000F1D8693&MType=0&Payload=0102030405060708090A&RAN=CELLULAR"