All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Erickson <gerickson@nuovations.com>
To: ofono@lists.linux.dev
Subject: [PATCH 0/7] Add AT&T, T-Mobile, and Verizon MVNO IoT/M2M APNs
Date: Wed,  5 Feb 2025 17:37:37 -0800	[thread overview]
Message-ID: <cover.1738805694.git.gerickson@nuovations.com> (raw)

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


             reply	other threads:[~2025-02-06  1:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06  1:37 Grant Erickson [this message]
2025-02-06  1:37 ` [PATCH 1/7] data: Add AT&T MVNO IoT/M2M 'Public' APN Grant Erickson
2025-02-06  1:37 ` [PATCH 2/7] data: Add AT&T MVNO IoT/M2M 'Private' APN Grant Erickson
2025-02-06  1:37 ` [PATCH 3/7] data: Add T-Mobile MVNO IoT/M2M 'Public' APN Grant Erickson
2025-02-06  1:37 ` [PATCH 4/7] data: Add T-Mobile MVNO IoT/M2M 'Private' APN Grant Erickson
2025-02-06  1:37 ` [PATCH 5/7] data: Add Verizon " Grant Erickson
2025-02-06  1:37 ` [PATCH 6/7] data: Add Verizon MVNO IoT/M2M 'Public' APN tag for KORE Wireless Grant Erickson
2025-02-06  1:37 ` [PATCH 7/7] data: Add Verizon MVNO IoT/M2M vzwims APN tags " Grant Erickson
2025-02-14  0:45 ` [PATCH 0/7] Add AT&T, T-Mobile, and Verizon MVNO IoT/M2M APNs Grant Erickson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1738805694.git.gerickson@nuovations.com \
    --to=gerickson@nuovations.com \
    --cc=ofono@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.