Although the Multitenancy Private APN functionality of Enea IoT Connectivity Control Service (IoT CCS) delivers the same function as a Private APN, it is not a Private APN. The separation of the traffic to different enterprises is not happening in the mobile core but instead in IoT CCS. Traditional, IoT CSPs create a customer-unique APN and map it to an Enterprise VPN to create a Private APN. With IoT CCS, the IoT CSPs only use one APN that is routed to IoT CCS through an IPSec tunnel. IoT CCS then routes the traffic to the correct Enterprise VPN. So, if the customer wants the traffic to go to another Enterprise VPN, all they have to do is change the routing in the customer self-care portal you provide as an IoT CSP. The device will keep the same APN name. This will save significant time and cost for customers having thousands of devices that do not need to be re-configured.