Skip to content
AevornixAEVORNIX
PlatformsResearch

Network services

The connectivity layer a mobile platform needs to stand on its own: identity, provisioning, messaging and device-to-network services.

Aevornix Mobile View the roadmap
RVStack architecture

RVStack architecture, 7 layers from top to bottom: 01 Application, 02 Development toolchain, 03 Portable runtime, 04 Operating layer, 05 RISC-V architecture, 06 Device profile, 07 Deployment target.

  1. Application
    Games, tools and software targeting the Aevornix platform.
    .aev project format
  2. Development toolchain
    Compiler, linker, debugger, SDK and build systems.
    ELFDWARF
  3. Portable runtime
    Execution services shared across supported RISC-V targets.
  4. Operating layer
    System services, permissions, storage, networking and application lifecycle.
    POSIX-style system interfaces
  5. RISC-V architecturefoundation
    The open instruction-set foundation beneath the software stack.
    RV64GCRVA23
  6. Device profile
    Defined hardware capabilities used for emulation and compatibility testing.
  7. Deployment target
    Physical devices, virtual environments, cloud targets and certified platforms.
    linux-riscv64

Where this stands

Network services are part of the Aevornix Mobile research programme. There is no service to connect to and no operator integration. What exists is the architectural position: these services belong to the operating layer, above the portable runtime and below the applications, so a mobile device is not dependent on services tied to a specific chipset vendor.

Network services | Aevornix