YateOTA is an OTA gateway system that provides the functions required to update SIM and mobile devices configurations using Over-The-Air messages over SMS.

It provides front-end, back-end and gateway functions to build SIM update campaigns and run them over a mobile network. YateOTA is a proprietary OTA server which is fully implemented in software and developed for operators of all sizes in any market and in any location.

What is YateOTA

General information about what YateOTA is and does.
OTA Parameters

OTA Parameters

YateOTA - product page

OTA gateway solution for remote updates

Licensing

Generic information about licensing system.

YateOTA Interface

This section contains information about YateOTA interface and how it works:

Create RFM campaign

Create RFM campaign using OTA Interface

Create RAM campaign

Create RAM campaign using OTA Interface

YateOTA configuration in MMI

Configure OTA from MMI

Sending custom OTA commands in Local mode

Testing configured product in Local mode
Sending custom OTA commands in OTA SMSC mode

Testing configured product in OTA SMSC mode

OTA – SIM Profiles

How to add a SIM profile or add it to another server

YateOTA API configurations & campaigns

This section contains information about how to use JSON API in different types of configurations for YateOTA

JSON API

General information about the JSON API.
JSON API for Control & Stats

Instructions on how to use the JSON API to control OTA Campaigns.

JSON API for OTA Campaigns

Instructions on how to use the JSON API to add/edit OTA Campaigns
JSON API to encode UD(s)/APDU(s)

Instructions on how to generate UD(s) and APDU(s)

JSON API for SIM Programmer

Low level JSON API for OTA in Local mode

YateOTA Integrations

This section contains information about YateOTA integrations and how it works:

YateOTA compatible keystore

Example API for YateOTA compatible keystore/middleware

Latest Changes

Tag number	Date	Release notes
6012	22.01.2026	Fixed stalling campaign building when multiple campaigns to the same msisdn were pushed sequencially
6011	25.11.2025	Increased allowed max active campaigns. Don't count campaigns that just have participants in waiting_por as active. Protect building campaigns because messsage could be duplicated when running on machines with multiple cores.
6010	24.06.2025	Fixed create campaign by imsi.
6009	28.05.2025	Implemented chronological running mode for campaigns and use it by default. Increased max participants per campaign to 5000. Implemented max number of active campaigns configuration and set default to 200. New campaigns will be rejected until number of active campaigns drops. Added documentation for almost all EFs in the interface, including 5Gs directory. Allow sending expanded format commands. Increased communication buffer between internal components so larger applets can be installed.
6008	31.07.2024	Added support for: campaigns per iccid, having pending campaigns for unallocated sims, rerun old campaigns when hook is callled in case of esim download profile. Obey Expires setting when delivering over SMPP by setting validity_period. Delay building/delivering when HSS not responding.
6007	16.04.2024	Increased max levels when building UPDATE APDUs for non-standard SIM card structures.
6006	07.04.2024	Copy just relevant files from sim_common to yate's share/scripts directory. Prefixed files from library with 'sim_common_'.
6005	02.04.2024	Increased scanning depth. Small fixes for older php versions compatibility.
6004	21.02.2024	Mark destination and orig numbers as international when sending sms in OTA SMSC MODE
6003	13.11.2023	Added option to generate custom_applet_commands campaign from API and Interface. Activate the new encoders/decoders for the following EFs: IMSI, SST/UST/EST/IST, ADN/FDN/SDN/LND/MSISDN, SMSP, IMSI, PLMNsel, PLMNwAcT/OPLMNwAcT/HTPLMNwAcT, FPLMN, CBMI, AD, EHPLMN, ePDGId, ePDGSelection, IMPU/IMPI/Domain.