Connect the site.
Bring AI to the edge.

Participating devices connect through a private radio access network. iCore session control establishes identity, connectivity and traffic rules; the UPF carries application data between the radio network and local edge applications. iFabric observes the estate and gFabric governs configured workload or action policies alongside the traffic path.

1. Device. A participating cellular endpoint. Different views illustrate onboarding, a fleet device changing its serving cell, and a camera using a local application.
2. Cell A. The configured radio network carries control signaling toward iCore session control and user traffic toward the UPF.
3. Cell B. In the mobility view the device changes to a second serving cell, with a control/path update and a data path toward the same local UPF.
4. Session control. Grouped mobile-core control functions establish subscriber identity, session connectivity and service rules. They do not carry camera or fleet application payload.
5. UPF. The user-plane function carries application traffic between the serving radio network and the configured data network.
6. Edge application. The configured fleet or vision service receives device data over the established connection. Any subsequent operational action uses its own authorization workflow.

The selected paths explain different phases of a deployment, not live traffic. Dashed control links represent registration, session setup or a mobility update; solid links represent application data. Payload does not pass through session-control functions, iFabric or gFabric. The mobility example retains a local UPF while changing the serving cell; other architectures and procedures are possible. Physical movement, radio coverage and procedure timing are not simulated. gFabric workload/action policy is distinct from mobile-core session policy. iCore provides the core; radio and device interoperability depend on the selected integrations. No robotics safety-control function or uninterrupted service guarantee is implied.

Views

Device onboarding. Registration and subscriber authentication are followed by session establishment. Control rules are installed at the UPF; application data then follows the user-plane path. The change in line color separates control from application data.

Fleet mobility. Illustrative mobility from Cell A to Cell B. A control/path update establishes the selected serving-cell path toward the same local UPF and application. The diagram does not simulate RF coverage, physical movement, protocol exchanges or an interruption interval.

Camera traffic. After connectivity is established, camera data takes the solid user-plane path through the serving radio and UPF to a local vision application. It does not traverse the session-control or governance layer.