One addressing plan
120 vehicles are not 120 holes in the internet.
Fleet
The vehicle is a client of the company network, not a server at the roadside.
Location, status and, where used, video from the vehicle end on a platform you admit into the tunnel. The tracker as a device is described separately.
ExampleExample: a fleet of 120 service and municipal vehicles. Each has a SIM on the private APN and a router or a tracker. An illustrative scenario, not a client reference.
An edge in motion
Peplink: more than one SIM, SpeedFusion, Hot Failover as the manufacturer describes it.
On to the tracker
CAN, tachograph and theft alarm are on the tracker page.
What bounces off the edge
A fleet platform exposed “to the vehicle’s internet” reverses the direction: the vehicle should call the company, and the company should call the vehicle, through the tunnel.
The SIM gets a private address. The report goes to the platform at headquarters. A Peplink router in the vehicle bonds LTE/5G and, where the ground is empty, Starlink as well. InControl 2 shows those routers, including on the manufacturer’s GPS-enabled devices.
Security
- A vehicle with no public IP.
- The platform behind the firewall.
- A stolen SIM does not admit a foreign device if the list and the IMEI binding are set.
A fleet can be the service of a municipal or transport entity. Connectivity that stays up is an operational argument. It is not KSC compliance.
Peplink · SpeedFusion · InControl 2 Starlink How it works
Request a proposal APN types and connection types +48 698 355 667
Related
On the same path
-
MDM and private APN
Enrolment, the profile, and a console reached only from the APN.
-
FAMOC
FancyFon’s console on a phone or terminal that is already on the APN.
-
Samsung Knox
KME enrolment, Knox Manage policy and a Knox Configure role.
-
GPS trackers
The tracker stays on a SIM in the APN. A cab screen, if there is one, is MDM.