Part of: 4G / 5G & O-RAN
Amarisoft is a commercial 4G and 5G software stack. This page explains what it is, how its parts are laid out on COSMOS, which COSMOS hardware it uses, how its licence is shared, and which tutorial to take.
A mobile network has three parts: the phone (the UE), the base station (the eNB in 4G, the gNB in 5G), and the core network, which checks the SIM, hands out an IP address and forwards traffic to the internet. Amarisoft sells software for all three. Each runs as a program on an ordinary x86 server with a software-defined radio. The software is closed source and licensed per component; its documentation is in the Amarisoft Tech Academy and in the doc/ directory of each release.
Research groups use it for two reasons. It is a mature product whose base station, core and UE come from one vendor and are tested together, so it makes a reliable reference cell: when something fails, the cause is almost always the radio, the host or the licence, not interoperability. And its UE simulator, lteue, runs many independent UEs through one radio, each with its own identity and traffic, which makes it the tool for capacity and scheduling experiments. It is also the only stack on COSMOS that runs 4G LTE as well as 5G.
There are three programs, each with its own configuration file. The files use a JavaScript-like format with #define and #include; includes are relative, so each program is started from its own directory under /opt/amarisoft/.
| Part | What it does | Amarisoft component | Where it runs on COSMOS |
|---|---|---|---|
| Base station (eNB / gNB) | the whole radio protocol stack, from physical layer to RRC, in one process | lteenb, LTE eNB or 5G NR gNB by configuration; it reaches the radio through a TRX driver (trx_uhd for USRPs, trx_s72 for an O-RAN 7.2 O-RU) |
the RAN server: srv17.osc or srv1-lg1.sb1 |
| Core | 4G EPC and 5G core in one binary: AMF, SMF, UPF, the subscriber database and the address pool | ltemme |
the same RAN server |
| UE | one or many simulated UEs on a real radio, attaching over the air | lteue |
the UE bank, sdr1-in3.sb1 |
| Radios | RF | USRP N310, one for the base station and one for the UEs | in sb1, reached over each host's data network |
| Licence | grants each program a seat while it runs | a floating network licence, requested by tag (gNB/eNB, 5gC/4gC, ue) |
the COSMOS licence server |
Because there is no software radio link between lteenb and lteue, Amarisoft has no radio-less mode on COSMOS: every Amarisoft tutorial transmits.
Danger: There is one licence seat per tag for the whole testbed. A leftover
lteenb,ltemmeorlteueon any host in any domain holds its seat, and the next program that asks for the same tag is refused. A refused program crashes immediately with a segfault, with no licence error, so it looks like a broken binary. Coordinate with other users before you start, and always run the teardown when you finish.
amarisoft.ndz for the RAN server (lteenb and ltemme) and lte5gue.ndz for the UE host (lteue, UHD and trx_uhd). They currently point at amarisoft-20261009 and lte5gue-20261002, which run Amarisoft release 2026-09-11 by default and keep 2026-06-12 selectable with amari-select.srv17.osc (the default) or srv1-lg1.sb1; the UE bank is sdr1-in3.sb1. Both RAN servers drive the same two N310 radios, so choosing between them changes only the CPU. The rig therefore spans two domains, and the tutorial names its hosts itself.srv17.osc is 2× Intel Xeon Gold 6126 (24 cores / 48 threads); srv1-lg1.sb1 is 2× Intel Xeon Gold 6226 (24 cores, hyperthreading off).lteenb can also drive the LiteOn FlexFi O-RU with its trx_s72 driver. The COSMOS gNB licence allows 120 MHz of bandwidth × antenna ports per direction, so a 7.2 cell is 30 MHz with 4 ports, 60 MHz with 2 or 100 MHz with 1.pkill or killall: a name match kills other users' programs and their licence seats. The tutorial runs each program in its own systemd unit and stops only those.| Tutorial | Radio? | Domains | Time | What you learn |
|---|---|---|---|---|
| amarisoft | yes: two USRP N310 (base station and UE bank) | osc + sb1 |
30 min for a short sweep | running a complete LTE or 5G network with up to 64 simulated UEs; driving lteue through its remote API; measuring attach rate, attach time and throughput as load grows; telling a real capacity limit from a measurement artefact |
Step-by-step procedures that are not yet packaged as cosmos-tutorial runs (they are run by hand, and may be older):
Amarisoft has no radio-less mode, so if 5G is new to you, take a no-radio tutorial first (see the section landing page) so the attach sequence is familiar before radios are involved.
Measured throughput for every Amarisoft build, by radio and CPU platform, is on Amarisoft performance by build.
Glossary
- eNB / gNB — the 4G / 5G base station. EPC / 5GC — the 4G / 5G core.
lteenb,ltemme,lteue— Amarisoft's base station, core and UE simulator.- TRX driver — the plug-in that connects
lteenborlteueto a radio (trx_uhdfor USRPs).- Licence tag — the name of the licence a program asks for; one seat per tag on the whole testbed.
- Attach / registration — the sequence a UE runs to join the network: cell search, random access, RRC setup, authentication.
- PLMN — the network identity (
00101on COSMOS).
How every Amarisoft build performed, round by round, with one chart per radio, carrier and CPU platform (7 series, newest round 2026-10-23), is on Amarisoft performance trend by build. Every weekly rebake and test round adds to it.
lteenb, ltemme and lteue manuals; the copies under /opt/amarisoft/<release>/doc/ match the installed version.trx_uhd.Author(s): COSMOS team · Tags: amarisoft, lte, 5g, sa, ue-simulator, overview