Use cases

Use Case: Automotive & Telematics

An end-to-end walkthrough for connected vehicle deployments using the Stacuity Customer Portal.

---

Overview

This use case walks through the full configuration of a connected vehicle deployment, from creating a VSlice to commissioning vehicles at scale, using Vantiq Connect as the worked example.

Modern connected vehicles require a connectivity architecture that can simultaneously support multiple types of traffic, each with different network requirements:

Isolating these traffic types prevents consumer applications from interfering with critical vehicle systems and allows different security and routing policies to be applied independently, all on a single eSIM.

This deployment uses a multi-APN architecture, where a single endpoint can maintain multiple simultaneous data sessions across different APNs, each with independent routing and policies.

---

The Vantiq Connect Deployment

Vantiq Connect deploys eSIMs in connected passenger vehicles. Each vehicle carries one eSIM that must simultaneously handle:

All three run on the same eSIM simultaneously using Primary and Secondary Endpoint Groups.

APNs are defined within the VSlice configuration and assigned to Endpoint Groups.

---

Prerequisites

Before starting:

• You are logged in to the Customer Portal
• Your user role has configuration write access
• Your network team has provided IPSec parameters for your data centre VPN connections
• Your eSIM ICCIDs are allocated to your account (visible in Inventory → Endpoints as Pending)

---

Step 1: Create the VSlice

Everything belongs to a VSlice.

1. Go to Configuration → VSlices → Add
2. Fill in:
   • Name: Vantiq Connect
   • PDN Type: IPv4
   • DNS Mode: Auto
   • IP Allocation Type: Auto/Static (Static ensures endpoints retain the same IP across sessions; Auto may change between sessions)
3. Click Create
4. Click Edit → Subnets → Add Subnet:
   • Name: vantiq-connect-main
   • Moniker: vc-main
   • Subnet: 10.101.0.0/16
   • Type: Static
5. Save

The VSlice must have at least one subnet before Endpoint Groups can be created.

---

Step 2: Create Routing Targets

Create two VPN targets and one internet breakout.

Target A: Telematics VPN

• Name: vc-telematics-vpn
• Type: IPSec VPN
• Destination: Vehicle backend network (e.g. 10.50.0.0/16)

Enter IPSec parameters provided by your network team.

---

Target B: OTA VPN

• Name: vc-ota-vpn
• Type: IPSec VPN
• Destination: OTA infrastructure (separate from telematics)

---

Target C: Internet Breakout

• Name: vc-internet-eu
• Type: Internet

Traffic is routed to the internet via a managed breakout.

---

Step 3: Create Routing Policies

Each APN has its own routing policy.

Telematics Policy

• Forward traffic to telematics VPN
• Drop all other traffic

---

OTA Policy

• Allow HTTPS (TCP 443) to OTA servers only
• Drop all other traffic

---

Infotainment Policy

• Allow all traffic to internet breakout

---

Step 4: Create the Primary Endpoint Group

• Name: vantiq-connect-primary
• Type: Primary
• Routing Policy: telematics
• Regional Policy: EU region

This group holds all endpoints and carries the primary (telematics) APN.

---

Step 5: Create Secondary Endpoint Groups

OTA Group

• Name: vantiq-connect-ota
• Type: Secondary
• APN: ota.vantiq.flex
• Routing Policy: OTA policy

---

Infotainment Group

• Name: vantiq-connect-infotainment
• Type: Secondary
• APN: infotainment.vantiq.flex
• Routing Policy: infotainment policy

---

Step 6: Associate Secondary Groups

Associate both Secondary groups to the Primary group.

Endpoints in the Primary group will now have access to all configured APNs.

---

Step 7: Commission Vehicles

Assign endpoints to the Primary group:

1. Go to Inventory → Endpoints
2. Filter by Pending
3. Select endpoints
4. Assign to vantiq-connect-primary

Endpoints become Active when devices connect to the network.

---

Step 8: Verify

After commissioning:

• Events show network attachment and session creation
• Endpoint Status shows Active or Idle
• IP Addresses show up to three IPs (one per APN), depending on active sessions
• Endpoint Events confirm activity across APNs

---

Ongoing Operations

Moving Vehicles Between Groups

Reassigning an endpoint to another group immediately applies new routing and policy configuration.

---

Troubleshooting Connectivity

• Use Events to identify network activity
• Check APN-specific behaviour
• Validate routing policies and targets

---

Decommissioning

Terminate the endpoint when the vehicle is retired.

---

Configuration Summary