Cloud API
REST API for RRC and NAS decoding at scale. Zero installation, zero dependencies: send a hex-encoded message, receive a structured JSON in under 200 ms. Built for platforms that need protocol decoding without embedding native libraries.
HiCellTek Cloud API is a REST API for decoding RRC (LTE TS 36.331, 5G NR TS 38.331) and NAS (EPS TS 24.301, 5GS TS 24.501) messages at scale. Zero installation required: send a hex payload via HTTP POST, receive a decoded JSON tree in under 200 ms. EU-hosted for GDPR compliance. Designed for IoT startups, SON/OSS platforms and R&D labs. Coming soon. Join the waitlist.
How it works
HTTP POST with the hex-encoded message, protocol type (RRC LTE, RRC NR, NAS EPS, NAS 5GS) and message type.
HiCellTek servers decode the message using the same ASN.1 libraries as the L3 SDK. Target latency under 200 ms.
Structured JSON response with the full decoded tree. Each IE (Information Element) is typed and named per 3GPP specifications.
Why a cloud API?
No native library to compile, no system dependency. A simple HTTP call from any language (Python, Node.js, Go, Java, curl).
Serverless architecture designed to absorb traffic spikes. Decode 10 messages or 10 million without changing your integration.
ASN.1 decoders are updated server-side. You automatically benefit from the latest 3GPP releases without redeployment.
Servers hosted in the European Union. Native GDPR compliance. Data never leaves European territory.
Who is it for?
Integrate protocol decoding into your cellular IoT fleet management platforms without embedding heavy native libraries.
Enrich your network optimization pipelines with RRC and NAS decoding at scale. Standard REST API, easy to integrate.
Decode test frames in batch from your Python scripts or Jupyter notebooks without setting up a C/C++ environment.
The Cloud API is under development. Join the waitlist to be notified at launch and receive early-adopter pricing. Beta access planned for H2 2026.
Frequently asked questions
Which protocols does the Cloud API decode?
The Cloud API decodes RRC LTE (TS 36.331), RRC 5G NR (TS 38.331), NAS EPS (TS 24.301) and NAS 5GS (TS 24.501) messages. Both ASN.1 UPER and APER encodings are supported. The response is a structured JSON with the full decoded tree.
What is the typical latency?
Target latency is under 200 ms per request for a standard RRC message. Complex messages (CellGroupConfig, UE Capabilities) may take up to 500 ms. The API is hosted in Europe (EU) for GDPR compliance.
When will the Cloud API be available?
The Cloud API is currently in development. Join the waitlist to be notified at launch and receive early-adopter pricing. Beta access is planned for H2 2026.
Does the Cloud API replace the L3 SDK?
No. The Cloud API is complementary. The L3 SDK is designed for real-time embedded decoding (on device or local server). The Cloud API is designed for decoding at scale with zero installation: ideal for web platforms, batch scripts and lightweight IoT integrations.