Expeto xRouter⚓︎

Expeto xRouter is a public 3/4/5G core which can route traffic to public/private xCores and connect to IPX networks for public roaming use.

xRouter is distributed and installed and configured using Helm charts and Kubernetes.

As a containerized 3GPP compliant core with IPX and BGP support xRouter is optimised for for ease of deployment into enterprise-controlled cloud or bare metal environments, supporting connectivity using both public and private networks

The Expeto xRouter acts as the “home network”, receiving traffic redirected from a mobile network operator, then securely sends the traffic to Expeto xCore sites for public, or hybrid public/private implementations. The Expeto xRouter assumes the tasks of subscriber authentication, policy management, and network routing before connecting to the Public Expeto xCore.

Expeto xRouter features: - Enables seamless roaming of Subscribers between segmented Systems. - Secures sensitive data by controlling data path within geographic boundaries. - BGP route exchange for both north and south bound links - Dynamic Linear scalability of dataplane components for increased throughput and flexible cost efficient deployment - Built-in high availability using Kuberenetes flatform - Geographic failover and traffic optimisation for lower latency and increased availability

Policy & Traffic Engines⚓︎

The Policy Engine maintains a database of all subscriber related information needed for routing policy decisions. The Policy Engine keeps the database in sync with all other xRouters and xCores. The Traffic Engine routes device (IMSI) connections to different destinations depending on metadata rules, these rules can be based on any part of the connection information including IMEI or IMSI value itself. It can also reject a device that fails to meet allow list criteria.

The Traffic Engine acts as a PGW/UPF towards the mobile network operator’s SGW/SMF. From the SGW/SMF perspective the Expeto xRouter is the terminating PGW/UPF. It then acts as a SGW/SMF sending traffic to a Public Expeto xCore. The Public Expeto xCore can then forwards data to the Private Expeto xCore or distributes it to local Systems (PGW/UPFs).

Subscriber Repository (HSS/AUSF/UDR/UDM)⚓︎

The Subscriber Service Repository is a multi-tenant subscriber repository for all signalling traffic from the public/private radio networks. It contains the SIM database that represents subscriber registrations.

Expeto Agent⚓︎

Expeto xRouter, like Expeto xCore, also includes Expeto Agent which synchronizes configuration between the Subscriber Repository and Expeto xControl to quickly create and expand 4G or 5G global networks. The Kubernetes based platform allows you to install multiple instances in different combinations across your network, enabling global coverage, high availability, performance scaling, test environments, and network evolution. Expeto network components can be installed behind a corporate firewall, on a DMZ, in a private cloud and at geographically remote sites according to your needs. Enterprises and Operators can manage the entire network from a browser through Expeto xControl or through the Expeto API.