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

[PATCH 0/2] Add T-Mobile MVNO IoT/M2M 'Public/Private' 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 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

[PATCH 1/2] 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 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) 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 e74d42a2758b..568055b14233 100644
--- a/data/provision.json
+++ b/data/provision.json
@@ -14242,6 +14242,15 @@
           "ia"
         ],
         "tags": "iot"
+      },
+      {
+        "name": "T-Mobile LTE KORE Wireless MVNO IoT/M2M (Public)",
+        "apn": "iot.tmowholesale",
+        "type": [
+          "internet",
+          "ia"
+        ],
+        "tags": "kore-public"
       }
     ]
   },
-- 
2.45.0

[PATCH 2/2] 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 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-specific IoT / M2M APN of type (2) above that is used
by KORE Wireless for the T-Mobile parent network operator.
---
 data/provision.json | 9 +++++++++
 1 file changed, 9 insertions(+)

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

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

[patchwork-bot+ofono]

Hello:

This series was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:

On Thu, 13 Feb 2025 16:42:18 -0800 you 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.
> 
> [...]

Here is the summary with links:
  - [1/2] data: Add T-Mobile MVNO IoT/M2M 'Public' APN.
    https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=e43d8f1a272e
  - [2/2] data: Add T-Mobile MVNO IoT/M2M 'Private' APN.
    https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=5874690e03ae

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html