[PATCH 0/2] Add T-Mobile MVNO IoT/M2M 'Public/Private' APNs

[Grant Erickson <gerickson@nuovations.com>]

At least in North America / United States, there exist Cellular MVNOs
(particularly in the IoT / M2M veritical) that neither use mobile
virtual network operator (MVNO) service provider names (SPNs) nor use
unique home network identifiers (HNIs) (that is, mobile country code
(MCC) + mobile network code (MNC) pairs). Instead, they simply use the
HNI of the parent operator.

In addition, those MVNOs typically have two or three APN schemes:

    1. A "public" APN that is broadly used by one or more MVNOs for
       the parent operator that issues PUBLIC IP addresses and DOES
       NOT route through the MVNO's or parent operator's data center
       infrastructure.

    2. A "private" APN that may or may NOT be broadly used by one or
       more MVNOs for the parent operator that issues PRIVATE IP
       addresses and DOES route through the MVNO's or parent
       operator's data center infrastructure.

    3. A "private" APN that is used only by the MVNO that issues
       static or dynamic PRIVATE IP addresses, DOES route through the
       MVNO's data center infrastructure and, from there, via a VPN to
       the customer services infrastructure.

       These are sometimes called customer private networks
       (CPNs). These are sufficiently MVNO-specific where they do not
       or should not play a role in a generic Cellular provisioning
       database.

KORE Wireless is one such IoT / M2M MVNO that uses AT&T, T-Mobile, and
Verizon as parent network operators.

This adds a MNVO-generic IoT / M2M APN of type (1) and a MNVO-specific
IoT / M2M APN (2) above that is used by KORE Wireless for the
T-Mobile parent operator.

Grant Erickson (2):
  data: Add T-Mobile MVNO IoT/M2M 'Public' APN.
  data: Add T-Mobile MVNO IoT/M2M 'Private' APN.

 data/provision.json | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

-- 
2.45.0