Workflow

From commit to certification in six steps

Every run on AEON Cloud executes on physical TTCN-3 infrastructure — LimeSDR and Ettus B210 lanes inside shielded enclosures. Nothing is emulated. Nothing is faked.

  1. STEP 01

    Upload build

    Push firmware via CLI, HTTPS API, or the web. Every artifact is versioned with checksum, tag, and provenance.

    aeon CLI
    $ aeon builds push ./ue-v2.4.1.tar.gz --tag rc3
  2. STEP 02

    Reserve tester

    Pick a region (EU / US / APAC) and a lane (LimeSDR or Ettus B210). Booking is minutes, not weeks.

    aeon CLI
    $ aeon lanes reserve --region eu-west-1 --sdr lime
  3. STEP 03

    Secure tunnel

    Your workstation opens a mutual-TLS tunnel to the reserved lab. No inbound firewall changes required.

    aeon CLI
    $ aeon tunnel open --lane tester-eu-03
  4. STEP 04

    Deploy & run

    The lane flashes your UE and executes the selected TTCN-3 campaign against 3GPP Release 15–18 suites.

    aeon CLI
    $ aeon exec run --suite NR_5GS_Registration
  5. STEP 05

    Monitor live

    Stream verdicts, MSC sequences, PCAPs, and console logs. Pause, resume, or cancel from the dashboard.

    aeon CLI
    $ aeon exec tail --id 4821
  6. STEP 06

    Report & analyze

    Export PDF / CSV / JSON / XLSX with 3GPP traceability. Ask the AI Copilot why a testcase failed.

    aeon CLI
    $ aeon reports export 4821 --format pdf

Who uses this workflow

One flow, four roles

Protocol engineer

Iterate on NAS / RRC / PDCP fixes with a shared tester pool and live MSCs.

Validation engineer

Run TTCN-3 campaigns across Release 15–18 with reproducible verdicts.

Certification manager

Track coverage, verdicts, and clause traceability across builds.

Engineering leadership

Certification cycles compressed from months to days, on OpEx.

Ready to run your first campaign?