Connect+

Separate firmware lifecycle from campaign roadmap.

OTA

OTA is presented as an interface-first firmware campaign path. Current public copy can describe the firmware lifecycle foundation already represented by upload, enablement, rollout query/report, cancel, and download routes, while the implemented scheduled, time-window, user-consent, and archive policy surfaces are promoted as available campaign behavior. Approval workflow, dashboards, analytics, and staged percentage rollout stay clearly labeled as roadmap work.

Firmware campaign interface contract

Discuss OTA All Features
Enterprise operations console showing firmware rollout, device registry, fleet health charts, and alert panels.

Highlights

What this service covers

  • Available firmware lifecycle foundation for upload, catalog, target enablement, rollout status, report, cancel, and download
  • Available campaign policy surfaces for schedule, time-window, user-consent, and archive operations
  • Roadmap framing for approval workflow, dashboards, analytics, and staged percentage rollout

Capabilities

Platform building blocks

  • Use existing firmware routes as the available implementation boundary instead of implying a complete campaign engine
  • Promote scheduled, time-window, user-consent, and archive behavior as available campaign policy vocabulary now that backend and SDK support has landed
  • Keep cancel available as lifecycle behavior while treating approval workflow, dashboards, analytics, and staged percentage rollout as roadmap scope

Outcomes

Why product teams use it

  • Keep OTA campaign vision visible without overclaiming phase-one implementation
  • Give firmware, SDK, backend, and product teams one shared availability vocabulary
  • Make buyer conversations explicit about what is available now, implemented, or roadmap

Availability Labels

Map each OTA concept to the right implementation status

Realtek Connect+ uses the firmware campaign contract as shared vocabulary while separating available lifecycle behavior and implemented policy surfaces from later campaign operations.

Concept Status Public copy stance Follow-up boundary
Firmware lifecycle foundation Available foundation Firmware upload/catalog, target enablement, device rollout status, report, cancel, and download can be discussed as current baseline behavior. A richer campaign engine still needs owner-repo implementation before stronger public claims.
Scheduled policy Available foundation Describe as an available campaign vocabulary for a supported start time or maintenance schedule. Richer operator UX can extend the supported surface later.
Time-window policy Available foundation Explain as an available campaign time-window constraint for eligible installs. Time-zone handling and device/app behavior can extend the supported surface later.
User-consent policy Available foundation Name it as a supported policy surface rather than a placeholder consent experience. Mobile UX refinements can extend the supported surface later.
Cancel Available foundation Keep cancel tied to stopping eligible pending firmware rollouts in the current lifecycle foundation. Do not imply broader campaign pause, approval, or analytics workflows.
Archive Available foundation Describe archive as an available campaign-management surface for closing or hiding completed campaigns without deleting audit history. Active campaign views can extend the supported surface later.

Available Foundation

Use the current firmware lifecycle as the implementation boundary

The OTA story starts with the firmware surfaces that exist today, not with a claim that the full commercial campaign engine is complete.

  • Describe publish, enablement, whitelist, rollout query/report, cancel, and download behavior as the available firmware lifecycle foundation.
  • Keep release metadata, model and version checks, target enablement, and device-reported rollout status tied to the existing backend route inventory.
  • Treat force and normal policy language as basic delivery vocabulary unless a deeper campaign policy engine is explicitly implemented.

Implemented Policy Surfaces

Promote the campaign policy surfaces that are now implemented

The campaign contract defines policy names so teams can align implementation, and the now-implemented scheduled, time-window, user-consent, and archive surfaces can be described as available rather than roadmap.

  • Scheduled and time-window OTA are available campaign-policy surfaces with backend enforcement and SDK handling in place.
  • User-consent-required OTA is now a supported policy surface rather than a placeholder mobile UX.
  • Archive is available for closing or hiding completed campaigns without deleting audit history.

Roadmap Guardrails

Keep phase-two operations out of available-now claims

The page preserves the commercial OTA direction while clearly marking unsupported campaign operations as follow-up scope.

  • Approval workflow, operator dashboards, analytics, and success-rate reporting are roadmap capabilities, not phase-one availability claims.
  • Staged percentage rollout and automatic cohort ramping stay out of the available feature list until a campaign engine implements them.
  • Device firmware install protocol, firmware signing policy, and mobile consent UX remain owned by their implementation layers rather than this public website.

Next step

Evaluate OTA for your product roadmap.

Share your product category, target deployment, and cloud requirements with the Realtek Connect+ team.

Talk to sales