Menu
← All productsIntelligent Connectivity Platform

iCore

The connectivity foundation
for intelligent operations.

iCore™ is Invences’ Intelligent Connectivity Platform, designed around cloud-native 4G, 5G and IMS connectivity for private networks and intelligent edge environments.

Explore iCore See architecture
Intelligent Connectivity Platform

iCore / In focus

Connect the environment.
Control the service.

Its mobile-core foundation connects participating cellular devices through mobility, identity and service policy. Other access technologies, including satellite-connected systems, require their defined integration paths.

Capabilities

01

Converge mobile connectivity

Bring 4G, 5G and IMS core capabilities into a cloud-native foundation for operator and enterprise environments.

02

Shape mobility and service policy

Manage connectivity, mobility and quality-of-service policies around the requirements of participating devices and workloads.

03

Connect the intelligent edge

Support private-network and edge deployments, with terrestrial and non-terrestrial access integrated as the architecture requires.

iCore / How it works

Control the session. Connect the workload.

Alternative 4G and 5G cores. Distinct control and data paths.

4G / 5G alternatives · Configured RAN & service integrations

iCore 4G, 5G and optional IMS architectureA device registers through the configured radio access network. The selected core authenticates the subscriber and establishes a session under service policy. User traffic then follows its user-plane gateway to the edge, a data network or an application. IMS is an optional IP service. Access and services depend on the validated integration. IMS uses established IP connectivity; ordinary application traffic does not pass through IMS. Access and User traffic represent control and payload phases at the same device and radio-access endpoint. Dashed session-control lines establish connectivity; user-data lines lead through the matching user-plane gateway. Control functions are grouped for readability. No mapping of other access technologies or emergency-service path is implied. Timing is illustrative.iCore / Control + session policy4G and 5G are alternatives · Configured radio accessUser dataRegister / authenticateRegister / authenticateaccess to control4gSession readySession readySession readySession readytraffic to user5gtraffic to user4guser5g to networkuser4g to networkOptional IP serviceOptional IP serviceA device reaches iCore through the configured 4G or 5G radio access network. This control path represents registration and session setup; it does not carry application payload through the control functions.AccessDevice + radio networkIllustrative grouping of 5G registration, subscriber authentication and session policy. AMF, AUSF and subscriber-data functions support access and identity; SMF and PCF support session and policy control. Functions and interfaces are collapsed for readability.5G controlAMF · AUSF · SMF · PCFAlternative 4G EPC path: MME, HSS and PCRF represent subscriber authentication, mobility, session coordination and service policy. A 4G session does not pass through the 5G control branch.4G controlMME · HSS · PCRFThe same device and radio access network now carry user traffic over the established session. The Session ready connection represents a control result, not payload routing through the control plane.User trafficEstablished sessionThe 5G user-plane function forwards the established session's user traffic between the radio access network and the configured data network under the applied session rules.5G user planeUPFThe 4G serving and packet-data network gateways carry user traffic for the established EPC session to the configured data network. This is an alternative to the 5G UPF path.4G user planeSGW · PGWEstablished IP connectivity reaches the configured edge environment, data network or application. An application can use this connection without an IMS service.Data networkEdge / applicationWhere integrated, IMS registration and service signaling use established IP connectivity. IMS service control is separate from the mobile-core control plane; the drawing does not route every application or media packet through IMS signaling functions.IMS serviceOptional IP serviceSupported access & services depend on integration.IMS is optional; applications can use the data network.Illustrative sequence · RepeatsiCore 4G, 5G and optional IMS architectureA device registers through the configured radio access network. The selected core authenticates the subscriber and establishes a session under service policy. User traffic then follows its user-plane gateway to the edge, a data network or an application. IMS is an optional IP service. Access and services depend on the validated integration. IMS uses established IP connectivity; ordinary application traffic does not pass through IMS. Access and User traffic represent control and payload phases at the same device and radio-access endpoint. Dashed session-control lines establish connectivity; user-data lines lead through the matching user-plane gateway. Control functions are grouped for readability. No mapping of other access technologies or emergency-service path is implied. Timing is illustrative.iCore / Configured mobile accessIllustrative architecture · No live trafficControlUser dataaccess to control5gaccess to control4gcontrol5g to trafficSession readySession readytraffic to user5gtraffic to user4guser5g to networkuser4g to networkOptional serviceOptional serviceA device reaches iCore through the configured 4G or 5G radio access network. This control path represents registration and session setup; it does not carry application payload through the control functions.AccessDevice + radio networkIllustrative grouping of 5G registration, subscriber authentication and session policy. AMF, AUSF and subscriber-data functions support access and identity; SMF and PCF support session and policy control. Functions and interfaces are collapsed for readability.5G controlAMF · AUSF · SMF · PCFAlternative 4G EPC path: MME, HSS and PCRF represent subscriber authentication, mobility, session coordination and service policy. A 4G session does not pass through the 5G control branch.4G controlMME · HSS · PCRFThe same device and radio access network now carry user traffic over the established session. The Session ready connection represents a control result, not payload routing through the control plane.User trafficEstablished sessionThe 5G user-plane function forwards the established session's user traffic between the radio access network and the configured data network under the applied session rules.5G user planeUPFThe 4G serving and packet-data network gateways carry user traffic for the established EPC session to the configured data network. This is an alternative to the 5G UPF path.4G user planeSGW · PGWEstablished IP connectivity reaches the configured edge environment, data network or application. An application can use this connection without an IMS service.Data networkEdge / applicationWhere integrated, IMS registration and service signaling use established IP connectivity. IMS service control is separate from the mobile-core control plane; the drawing does not route every application or media packet through IMS signaling functions.IMS serviceOptional IP serviceSupported access & services depend on integration.IMS is optional; applications can use the data network.Illustrative sequence · Repeats

Establish the session. Carry data through the UPF.

Session controlUser data / IP service

Access and services depend on the validated integration. IMS uses established IP connectivity; ordinary application traffic does not pass through IMS.

A device registers through the configured radio access network. The selected core authenticates the subscriber and establishes a session under service policy. User traffic then follows its user-plane gateway to the edge, a data network or an application. IMS is an optional IP service.

Architecture & operating boundaries

A device registers through the configured radio access network. The selected core authenticates the subscriber and establishes a session under service policy. User traffic then follows its user-plane gateway to the edge, a data network or an application. IMS is an optional IP service.

  1. Access. A device reaches iCore through the configured 4G or 5G radio access network. This control path represents registration and session setup; it does not carry application payload through the control functions.
  2. 5G control. Illustrative grouping of 5G registration, subscriber authentication and session policy. AMF, AUSF and subscriber-data functions support access and identity; SMF and PCF support session and policy control. Functions and interfaces are collapsed for readability.
  3. 4G control. Alternative 4G EPC path: MME, HSS and PCRF represent subscriber authentication, mobility, session coordination and service policy. A 4G session does not pass through the 5G control branch.
  4. User traffic. The same device and radio access network now carry user traffic over the established session. The Session ready connection represents a control result, not payload routing through the control plane.
  5. 5G user plane. The 5G user-plane function forwards the established session's user traffic between the radio access network and the configured data network under the applied session rules.
  6. 4G user plane. The 4G serving and packet-data network gateways carry user traffic for the established EPC session to the configured data network. This is an alternative to the 5G UPF path.
  7. Data network. Established IP connectivity reaches the configured edge environment, data network or application. An application can use this connection without an IMS service.
  8. IMS service. Where integrated, IMS registration and service signaling use established IP connectivity. IMS service control is separate from the mobile-core control plane; the drawing does not route every application or media packet through IMS signaling functions.

This is a simplified reference architecture, not live network activity. Access and User traffic show control and payload phases at the same device and radio access endpoint. Control functions establish and govern the session; application payload follows the user-plane gateways. The drawing groups functions and omits protocol detail. RAN interoperability, subscriber integration, service policy and IMS scope require deployment-specific validation. Other access technologies, including non-terrestrial access, need their defined integration paths and are not mapped here. Service behavior depends on the access network, configuration and operating environment. Animation timing is illustrative; repetition restarts the explanation, not subscriber registration.

Views

5G data. Illustrative 5G path: registration, authentication and session policy establish connectivity. User traffic from the same device and radio access network then uses the UPF to reach the configured data network or edge application.

4G data. Illustrative alternative 4G path: EPC control establishes the session. User traffic then uses the SGW and PGW to reach the configured data network. This path does not traverse the 5G core.

IMS service. Illustrative IMS path over the 5G connection shown here: establish the mobile data session, then reach the configured IMS service over IP. IMS can also be integrated with a supported 4G deployment. IMS is not a required hop for ordinary application traffic.

Put it into operation

Private 5G & Physical AI

Start with your environment.

Talk to our team
Our platform directionExplore the platforms iFabric · iCore · Powered by nLLM