[PATCH 0/7] Add AT&T, T-Mobile, and Verizon MVNO IoT/M2M APNs

[PATCH 0/7] Add AT&T, T-Mobile, and Verizon MVNO IoT/M2M APNs

[Grant Erickson]

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 MVNOs or parent operator 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 MVNOs or parent operator
       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 data center infrastructure and, from there, via a VPN to
       the customer services infrastructure.

       These are sufficiently MVNO-specific where they do not or
       should not play a role in a generic provisioning database.

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

This adds a MNVO-generic IoT / M2M APN of type (1) and (2) above that
are used by KORE Wireless as well as by other MVNOs for the AT&T,
T-Mobile, and Verizon parent operators.

Grant Erickson (7):
  data: Add AT&T MVNO IoT/M2M 'Public' APN.
  data: Add AT&T MVNO IoT/M2M 'Private' APN.
  data: Add T-Mobile MVNO IoT/M2M 'Public' APN.
  data: Add T-Mobile MVNO IoT/M2M 'Private' APN.
  data: Add Verizon MVNO IoT/M2M 'Private' APN.
  data: Add Verizon MVNO IoT/M2M 'Public' APN tag for KORE Wireless.
  data: Add Verizon MVNO IoT/M2M vzwims APN tags for KORE Wireless.

 data/provision.json | 52 ++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 49 insertions(+), 3 deletions(-)

-- 
2.45.0

[PATCH 1/7] data: Add AT&T MVNO IoT/M2M 'Public' APN.

[Grant Erickson]

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 MVNOs or parent operator 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 MVNOs or parent operator
       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 data center infrastructure and, from there, via a VPN to
       the customer services infrastructure.

       These are sufficiently MVNO-specific where they do not or
       should not play a role in a generic provisioning database.

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

This adds a MNVO-generic IoT / M2M APN of type (1) above that is used
by KORE Wireless as well as by other MVNOs for the AT&T parent
operator.
---
 data/provision.json | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/data/provision.json b/data/provision.json
index 50319cf33a51..fb80cd839b80 100644
--- a/data/provision.json
+++ b/data/provision.json
@@ -14191,6 +14191,15 @@
           "ia"
         ],
         "tags": "m2m"
+      },
+      {
+        "name": "AT&T MVNO IoT/M2M (Public)",
+        "apn": "broadband",
+        "type": [
+          "internet",
+          "ia"
+        ],
+        "tags": "kore-m2m-public"
       }
     ]
   },
-- 
2.45.0

[PATCH 2/7] data: Add AT&T MVNO IoT/M2M 'Private' APN.

[Grant Erickson]

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 MVNOs or parent operator 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 MVNOs or parent operator
       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 data center infrastructure and, from there, via a VPN to
       the customer services infrastructure.

       These are sufficiently MVNO-specific where they do not or
       should not play a role in a generic provisioning database.

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

This adds a MNVO-generic IoT / M2M APN of type (2) above that is used
by KORE Wireless as well as by other MVNOs for the AT&T parent
operator.
---
 data/provision.json | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/data/provision.json b/data/provision.json
index fb80cd839b80..751e1ea6e1df 100644
--- a/data/provision.json
+++ b/data/provision.json
@@ -14200,6 +14200,15 @@
           "ia"
         ],
         "tags": "kore-m2m-public"
+      },
+      {
+        "name": "AT&T MVNO IoT/M2M (Private)",
+        "apn": "10569.mcs",
+        "type": [
+          "internet",
+          "ia"
+        ],
+        "tags": "kore-m2m-private"
       }
     ]
   },
-- 
2.45.0

[PATCH 3/7] data: Add T-Mobile MVNO IoT/M2M 'Public' APN.

[Grant Erickson]

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 MVNOs or parent operator 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 MVNOs or parent operator
       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 data center infrastructure and, from there, via a VPN to
       the customer services infrastructure.

       These are sufficiently MVNO-specific where they do not or
       should not play a role in a generic provisioning database.

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

This adds a MNVO-generic IoT / M2M APN of type (1) above that is used
by KORE Wireless as well as by other MVNOs for the T-Mobile parent
operator.
---
 data/provision.json | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/data/provision.json b/data/provision.json
index 751e1ea6e1df..bd10068f6b3e 100644
--- a/data/provision.json
+++ b/data/provision.json
@@ -14250,6 +14250,15 @@
           "ia"
         ],
         "tags": "iot"
+      },
+      {
+        "name": "T-Mobile LTE MVNO IoT/M2M (Public)",
+        "apn": "iot.tmowholesale",
+        "type": [
+          "internet",
+          "ia"
+        ],
+        "tags": "kore-m2m-public"
       }
     ]
   },
-- 
2.45.0

[PATCH 4/7] data: Add T-Mobile MVNO IoT/M2M 'Private' APN.

[Grant Erickson]

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 MVNOs or parent operator 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 MVNOs or parent operator
       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 data center infrastructure and, from there, via a VPN to
       the customer services infrastructure.

       These are sufficiently MVNO-specific where they do not or
       should not play a role in a generic provisioning database.

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

This adds a MNVO-generic IoT / M2M APN of type (2) above that is used
by KORE Wireless as well as by other MVNOs for the T-Mobile parent
operator.
---
 data/provision.json | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/data/provision.json b/data/provision.json
index bd10068f6b3e..c0dcc7b37c9f 100644
--- a/data/provision.json
+++ b/data/provision.json
@@ -14259,6 +14259,15 @@
           "ia"
         ],
         "tags": "kore-m2m-public"
+      },
+      {
+        "name": "T-Mobile LTE KORE Wireless MVNO IoT/M2M (Private)",
+        "apn": "c1.korem2m.com",
+        "type": [
+          "internet",
+          "ia"
+        ],
+        "tags": "kore-m2m-private"
       }
     ]
   },
-- 
2.45.0

[PATCH 5/7] data: Add Verizon MVNO IoT/M2M 'Private' APN.

[Grant Erickson]

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 MVNOs or parent operator 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 MVNOs or parent operator
       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 data center infrastructure and, from there, via a VPN to
       the customer services infrastructure.

       These are sufficiently MVNO-specific where they do not or
       should not play a role in a generic provisioning database.

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

This adds a MNVO-generic IoT / M2M APN of type (2) above that is used
by KORE Wireless as well as by other MVNOs for the Verizon parent
operator.
---
 data/provision.json | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/data/provision.json b/data/provision.json
index c0dcc7b37c9f..cda4b6e532f4 100644
--- a/data/provision.json
+++ b/data/provision.json
@@ -14336,6 +14336,14 @@
         "type": [
           "wap"
         ]
+      },
+      {
+        "name": "4G LTE Contract (Private)",
+        "apn": "wyleslte.gw7.vzwentp",
+        "type": [
+          "internet"
+        ],
+        "tags": "kore-m2m-private"
       }
     ]
   },
-- 
2.45.0

[PATCH 6/7] data: Add Verizon MVNO IoT/M2M 'Public' APN tag for KORE Wireless.

[Grant Erickson]

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 MVNOs or parent operator 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 MVNOs or parent operator
       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 data center infrastructure and, from there, via a VPN to
       the customer services infrastructure.

       These are sufficiently MVNO-specific where they do not or
       should not play a role in a generic provisioning database.

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

This adds a KORE Wireless-specific tag to the Verizon APN of type (1).
---
 data/provision.json | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/data/provision.json b/data/provision.json
index cda4b6e532f4..7bd9da27aaeb 100644
--- a/data/provision.json
+++ b/data/provision.json
@@ -14324,11 +14324,12 @@
         ]
       },
       {
-        "name": "4G LTE Contract",
+        "name": "4G LTE Contract (Public)",
         "apn": "vzwinternet",
         "type": [
           "internet"
-        ]
+        ],
+        "tags": "kore-m2m-public"
       },
       {
         "name": "4G LTE Contract",
-- 
2.45.0

[PATCH 7/7] data: Add Verizon MVNO IoT/M2M vzwims APN tags for KORE Wireless.

[Grant Erickson]

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 MVNOs or parent operator 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 MVNOs or parent operator
       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 data center infrastructure and, from there, via a VPN to
       the customer services infrastructure.

       These are sufficiently MVNO-specific where they do not or
       should not play a role in a generic provisioning database.

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

Verizon appears to require that devices first attach to 'vzwims' and
then 'vzwinternet'. This adds a KORE Wireless-specific public (1) and
private (2) tags to the Verizon attach APN to ensure that happens when
either the public or private APNs are used with (or without) tags.
---
 data/provision.json | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/data/provision.json b/data/provision.json
index 7bd9da27aaeb..82b16ba0ea38 100644
--- a/data/provision.json
+++ b/data/provision.json
@@ -14321,7 +14321,8 @@
         "type": [
           "ims",
           "ia"
-        ]
+        ],
+        "tags": "kore-m2m-public,kore-m2m-private"
       },
       {
         "name": "4G LTE Contract (Public)",
-- 
2.45.0

Re: [PATCH 0/7] Add AT&T, T-Mobile, and Verizon MVNO IoT/M2M APNs

[Grant Erickson]

On Feb 5, 2025, at 5:37 PM, Grant Erickson <gerickson@nuovations.com> wrote:
> 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 MVNOs or parent operator 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 MVNOs or parent operator
>       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 data center infrastructure and, from there, via a VPN to
>       the customer services infrastructure.
> 
>       These are sufficiently MVNO-specific where they do not or
>       should not play a role in a generic provisioning database.
> 
> KORE Wireless is one such IoT / M2M MVNO that uses AT&T, T-Mobile, and
> Verizon as parent operators.
> 
> This adds a MNVO-generic IoT / M2M APN of type (1) and (2) above that
> are used by KORE Wireless as well as by other MVNOs for the AT&T,
> T-Mobile, and Verizon parent operators.
> 
> Grant Erickson (7):
>  data: Add AT&T MVNO IoT/M2M 'Public' APN.
>  data: Add AT&T MVNO IoT/M2M 'Private' APN.
>  data: Add T-Mobile MVNO IoT/M2M 'Public' APN.
>  data: Add T-Mobile MVNO IoT/M2M 'Private' APN.
>  data: Add Verizon MVNO IoT/M2M 'Private' APN.
>  data: Add Verizon MVNO IoT/M2M 'Public' APN tag for KORE Wireless.
>  data: Add Verizon MVNO IoT/M2M vzwims APN tags for KORE Wireless.
> 
> data/provision.json | 52 ++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 49 insertions(+), 3 deletions(-)
> 
> -- 
> 2.45.0

This patch set can be ignored / abandoned; it has been superseded by subsequent patch sets.

Best,

Grant
-- 
Principal
Nuovations

gerickson@nuovations.com
https://www.nuovations.com/