Skip to main content
Version: v1.1

Key Concepts

This page explains the main AosEdge concepts used across the documentation.

The Glossary provides short definitions. This page explains how the concepts relate to each other and why they exist.

Platform concepts​

AosEdge​

AosEdge is the overall platform for managing software-defined functionality across connected Units.

It combines cloud-side management through AosCloud with edge-side execution through AosCore.

AosCloud​

AosCloud is the cloud-side management layer.

It provides the place where users manage organizations, fleets, Units, deployment planning, verification, monitoring, alerts, and operational visibility.

AosCloud is where users define what should happen across the managed environment.

AosCore​

AosCore is the runtime layer installed on a Unit.

It receives instructions from AosCloud, applies them locally, manages Deployable Items, reports the Unit state, and supports monitoring and troubleshooting.

AosCore is where cloud-side intent becomes local edge-side behavior.

Unit and fleet concepts​

Unit​

A Unit is a connected edge system managed by AosEdge.

A Unit may represent a vehicle, ECU-based system, industrial gateway, or another OEM-controlled connected product. The exact hardware depends on the OEM product architecture.

Node​

A Node is a computing element inside a Unit.

A simple Unit may have one Node. A more complex Unit may include several Nodes with different capabilities or responsibilities.

Fleet​

A Fleet is a group of Units managed together.

Fleets help organize Units according to ownership, operation, customer scope, geography, product line, or another business structure.

Unit Set​

A Unit Set is a smaller logical group of Units.

Unit Sets can be used for staged operations, limited-scope verification, rollout planning, or operational grouping inside a fleet.

Deployment concepts​

Deployable Item​

A Deployable Item is a unit of software-defined functionality that can be delivered, installed, managed, and monitored on a Unit.

This is the general public-facing term for managed delivery content in AosEdge documentation.

Deployment Bundle​

A Deployment Bundle groups several Deployable Items that must be delivered or managed together.

Deployment Bundles are useful when functionality depends on several related pieces of content and should be controlled as one delivery scope.

Verification​

Verification is a controlled check before broader deployment.

It helps confirm that a Deployable Item or Deployment Bundle behaves correctly on a limited scope before it is rolled out more widely.

Campaign​

A Campaign is a planned deployment operation.

Campaigns help control how Deployable Items or Deployment Bundles are rolled out across Units, Unit Sets, or fleets.

State and lifecycle concepts​

Target state​

Target state describes what AosCloud expects a Unit or a group of Units to have or run.

It is the cloud-side intent for the managed environment.

Actual state​

Actual state describes what the Unit reports back after processing cloud-side instructions.

AosEdge uses this feedback to show whether the Unit matches the target state, needs attention, or reports operational problems.

Monitoring data​

Monitoring data helps users understand the operational condition of Units and deployed functionality.

It may include health, resource usage, connectivity, logs, alerts, and deployment results depending on the available platform configuration.

Organization and role concepts​

OEM​

The OEM owns or controls the connected product ecosystem and defines how Units are managed.

The OEM is usually the primary stakeholder for governance, lifecycle management, and operational control.

Service Provider​

A Service Provider delivers software-defined functionality into OEM-managed environments.

The Service Provider works within the access and governance model defined by the OEM.

Fleet Owner​

A Fleet Owner operates Units assigned by the OEM.

The Fleet Owner focuses on day-to-day fleet operation, monitoring, and controlled participation in deployment workflows.

Admin​

An Admin manages organizations, users, access, and platform-level settings.

Exact permissions are described in detailed AosCloud documentation.

For a high-level introduction, see AosEdge Overview.

For the overall system model, see Platform Model.

For scenario examples, see Typical Use Cases.

For role explanations, see Roles and Responsibilities.

For short definitions, see Glossary.