Glossary
This glossary defines public AosEdge terminology.
Use these terms consistently across customer-facing documentation.
Platform terms
AosEdge
The overall platform for managing software-defined functionality across connected Units.
AosEdge combines cloud-side management through AosCloud with edge-side execution through AosCore.
AosCloud
The cloud-side management layer of AosEdge.
AosCloud is used for fleet management, deployment orchestration, user and role management, verification, monitoring, alerts, and operational control.
AosCore
The runtime layer installed on a Unit.
AosCore receives instructions from AosCloud, applies them locally, manages Deployable Items, reports actual state, and supports monitoring and troubleshooting.
Unit and fleet terms
Unit
A connected edge system managed by AosEdge.
A Unit may represent a vehicle, ECU-based system, industrial gateway, or another OEM-controlled connected product.
Node
A computing element inside a Unit.
A Unit may contain one or several Nodes depending on the hardware architecture.
Fleet
A group of Units managed together.
Fleets can represent ownership, operational scope, product line, region, or another business grouping.
Unit Set
A logical subset of Units.
Unit Sets can be used for staged operations, limited-scope verification, rollout planning, or operational grouping.
Deployment terms
Deployable Item
A unit of delivery content that can be delivered, installed, managed, and monitored on a Unit.
Deployable Item is the unified public-facing term for managed delivery content in AosEdge documentation.
Deployment Bundle
A group of Deployable Items that must be delivered or managed together.
Deployment Bundles help control related delivery content as one deployment scope.
Verification
A controlled check before broader deployment.
Verification helps confirm that delivery content behaves correctly on a limited scope before being rolled out more widely.
Campaign
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 terms
Target state
The state that AosCloud expects a Unit or a group of Units to reach.
Target state describes the intended platform outcome at product level.
Actual state
The state reported by a Unit after processing platform instructions.
Actual state helps users understand whether the Unit matches the intended outcome or requires attention.
Reported state
Information sent from a Unit to AosCloud about its current condition, deployment result, health, or operational status.
Reported state is part of the feedback loop between the edge and the cloud.
Roles and organizations
OEM
The organization that owns or controls the connected product ecosystem.
The OEM is usually responsible for governance, lifecycle management, deployment control, and visibility across Units and fleets.
Service Provider
An organization that delivers software-defined functionality into OEM-managed environments.
The Service Provider works within the access and governance model defined by the OEM.
Fleet Owner
An organization or user group responsible for operating assigned Units.
The Fleet Owner focuses on day-to-day fleet operation, monitoring, and controlled participation in deployment workflows.
Admin
A user responsible for platform-level setup, organizations, users, access, and configuration.
Exact Admin capabilities depend on the configured access model.
Monitoring and operations
Alert
A notification that indicates a condition requiring attention.
Alerts may relate to Unit health, deployment state, connectivity, resource usage, or other operational conditions.
Telemetry
Operational data reported by Units.
Telemetry helps users monitor health, resource usage, connectivity, and behavior across the managed environment.
Log
A record of events or runtime behavior.
Logs help users investigate operational issues and support troubleshooting.
Provisioning
The process of preparing a Unit or related platform entity so it can be securely managed by AosEdge.
Provisioning usually includes identity, registration, and connection-related setup.
Certificate
A cryptographic identity artifact used to establish trust between platform components and users.
Certificates are part of secure communication and identity management.
mTLS
Mutual Transport Layer Security.
mTLS is a communication security mechanism where both sides of a connection authenticate each other using certificates.
Legacy or lower-level terms
The terms in this section may appear in older documentation, source-level descriptions, UI labels, API names, tickets, or implementation-specific sections.
Do not use them as the main product model in top-level AosEdge documentation.
Use Deployable Item and Deployment Bundle as the unified public-facing terminology.
SOTA
Legacy or lower-level term for software-oriented delivery.
Top-level AosEdge documentation should describe this area through Deployable Items and Deployment Bundles instead.
FOTA
Legacy or lower-level term for firmware-oriented delivery.
Top-level AosEdge documentation should describe this area through Deployable Items and Deployment Bundles instead.
Service
Legacy or implementation-specific term for a type of software functionality.
In top-level AosEdge documentation, use Deployable Item when referring to managed delivery content in general.
Component
Legacy or implementation-specific term for a type of platform or system content.
In top-level AosEdge documentation, use Deployable Item when referring to managed delivery content in general.
Layer
Legacy or implementation-specific term for supporting software content.
In top-level AosEdge documentation, use Deployable Item when referring to managed delivery content in general.
Related documentation
For concept explanations, see Key Concepts.
For the high-level platform model, see Platform Model.
For role explanations, see Roles and Responsibilities.
For deeper technical details, see AosCloud documentation and AosCore documentation.