[PATCH 0/2] data: Update Verizon APN Contexts

[PATCH 0/2] data: Update Verizon APN Contexts

[Grant Erickson]

Verizon has a number of different Cellular access point names (APNs)
and contexts, depending on the application, per their documentation
here:

    https://www.verizon.com/support/knowledge-base-72601/

Some of those contexts must be used for initial attach (IA). For Voice
over LTE (VoLTE) applications, the 'vzwims' APN is such an IA context
and is currently marked as such.

However, for Internet of Things (IoT) or machine-to-machine (M2M)
applications, the 'vzwinternet' APN is also such an IA context but is
not presently marked as such. This change adds the 'ia' type to this
APN context.

In addition, one partition of those contexts are appropriate for LTE
and/or VoLTE applications while another is appropriate for IoT or M2M
applications.

These changes add the 'ia' type to the 'vzwinternet' APN context and
add the 'iot', 'm2m', and 'volte' tags to the three current
Verizon APN contexts such that no tags or some combination of those
tags produce the desired set of APN contexts for the desired
application(s).

Grant Erickson (2):
  data: Add initial attach type to Verizon 'vzwinternet' context.
  data: Add tags to Verizon APN contexts.

 data/provision.json | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

-- 
2.45.0

[PATCH 1/2] data: Add initial attach type to Verizon 'vzwinternet' context.

[Grant Erickson]

Verizon has a number of different Cellular access point names (APNs)
and contexts, depending on the application, per their documentation
here:

    https://www.verizon.com/support/knowledge-base-72601/

Some of those contexts must be used for initial attach (IA). For Voice
over LTE (VoLTE) applications, the 'vzwims' APN is such an IA context
and is currently marked as such.

However, for Internet of Things (IoT) or machine-to-machine (M2M)
applications, the 'vzwinternet' APN is also such an IA context but is
not presently marked as such. This change adds the 'ia' type to this
APN context.
---
 data/provision.json | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/data/provision.json b/data/provision.json
index 50319cf33a51..9d65ac08b394 100644
--- a/data/provision.json
+++ b/data/provision.json
@@ -14291,7 +14291,8 @@
         "name": "4G LTE Contract",
         "apn": "vzwinternet",
         "type": [
-          "internet"
+          "internet",
+          "ia"
         ]
       },
       {
-- 
2.45.0

[PATCH 2/2] data: Add tags to Verizon APN contexts.

[Grant Erickson]

Verizon has a number of different Cellular access point names (APNs)
and contexts, depending on the application, per their documentation
here:

    https://www.verizon.com/support/knowledge-base-72601/

One partition of those contexts are appropriate for LTE and/or Voice
over LTE (VoLTE) applications while another is appropriate for
Internet of Things (IoT) or machine-to-machine (M2M) applications.

This applies the 'iot', 'm2m', and 'volte' tags to the three current
Verizon APN contexts such that no tags or some combination of those
tags produce the desired set of APN contexts for the desired
application.
---
 data/provision.json | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/data/provision.json b/data/provision.json
index 9d65ac08b394..b7072af256cf 100644
--- a/data/provision.json
+++ b/data/provision.json
@@ -14285,7 +14285,8 @@
         "type": [
           "ims",
           "ia"
-        ]
+        ],
+        "tags": "volte"
       },
       {
         "name": "4G LTE Contract",
@@ -14293,14 +14294,16 @@
         "type": [
           "internet",
           "ia"
-        ]
+        ],
+        "tags": "iot,m2m,volte"
       },
       {
         "name": "4G LTE Contract",
         "apn": "vzwapp",
         "type": [
           "wap"
-        ]
+        ],
+        "tags": "volte"
       }
     ]
   },
-- 
2.45.0