Ericsson introduced its Integrated Sensing and Communication, or ISAC, System on November 2, 2026. The announcement places selected small-scale, sensing-only commercial pilots in 2027 and broader sensing deployments from 2028. For an operator or venue planning a project, those are different stages with different decisions attached.
Ericsson’s November 2 announcement and phased introduction
What the initial sensing capability means
Ericsson describes detecting and tracking moving objects, including drones that are not connected to the network, using sensing-capable 5G radios and processing. It says the system complements radar and other sensors. The release places integrated communications capability later, as the solution evolves toward 6G. A sensing pilot should therefore retain its stated scope when it enters a project plan.
Demonstration evidence has a date and a setting
Ericsson’s product page points to a July 2026 demonstration with AT&T outside AT&T Stadium in Texas. That is useful US context for understanding the development work. The page’s demonstration description does not provide a service-start commitment for another venue.
Ericsson’s product page: capabilities and demonstration references
When reviewing a demonstration, keep a short evidence record: who conducted it, when it happened, which capability was shown and which source describes it. Then write a separate question about your own site’s eligibility and timing. Reusing the demonstration’s date as a proposed installation date would obscure the decision still required.
Turn the roadmap into a bounded planning exercise
Imagine a fictional venue preparing its technology budget for 2027. Its team can ask about participating in a sensing-only pilot while leaving any wider rollout date uncommitted. The team’s proposal should describe what it wants to learn, the responsible owner and the evidence needed to decide what comes next. This is an invented planning example, not an announced customer project.
- Ask whether the actual location and organization can participate in the proposed pilot phase.
- Request the specific offered functions, provider responsibilities, prerequisites and current schedule in writing.
- Keep pilot costs, later deployment costs and ongoing operating costs separate in the proposal.
- Define who will review the pilot’s results and authorize a subsequent project decision.
- Record unresolved availability questions as pending, and revisit them when the supplier updates its plans.
A useful first deliverable is a dated supplier response to those questions. A general product introduction can justify investigating an option; the supplier response determines whether it belongs in a particular budget or project dependency. Avoid making another project’s deadline depend on a rollout that has not been agreed for the site.
Keep the planning record current
Before committing funds, recheck the published introduction stages and the supplier’s current offer. Save the source date alongside the assumptions used in the proposal. This guide reports Ericsson’s stated timing and suggests a planning method; it does not establish site coverage, detection performance, pricing or a completed deployment. No demonstration, network or customer installation was independently tested.