LSP3 device (Sprint LTE) activation

NOTE: This section applies to Sprint LTE devices (such as MTCAP-LSP3 models).

Sprint has one network which supports receiving APN via OMA-DM (aka OTA or Over-The-Air Activation) and a second network which does not. Below is information regarding Sprint networks and activation.

Sprint IoT Network / Platform (Curiosity)

The IoT Network does NOT support OMA -DM. You must set APN manually via AT command.

  1. To determine that you are on the IoT Network, send AT command AT+CIMI to device.
    • If first 6 digits start with 311882:  Account/SIM is configured for use on the Curiosity Network.
  2. This network does NOT support receiving the APN OTA via OMA DM.
  3. The user or application must configure device to use the PDP context which contains the data APN stored via AT command. Verify that you have the correct PDP Context before configuring.
  4. The user or application is required to set data APN “internet.curiosity.sprint.com” into module via AT command. Set both the PDP context (first value) and APN (third value), use the following AT command:
    • AT+CGDCONT= 2, “ipv4v6″, ”internet.curiosity.sprint.com”

Sprint Legacy Network / Platform (Sprint Command Center and Sprint Vision/Ensemble)

The Legacy Network does support OMA-DM. The APN is set automatically.

  1. To determine that you are on the Legacy Network, send AT command AT+CIMI to device.
    • If first 6 digits start with IMSI start with 310120: Account/SIM is configured for use on the Command Center Platform.
    • If first 6 digits start with IMSI start with 312530 : Account/SIM is configured for use on Vision/Ensemble Platform.
  2. Devices with those IMSI digits both support receiving the data APN OTA via OMA DM. Once you have verified your account on the Legacy network and installed your SIM, device activation OTA should occur.
    • The user or application is not required to set data APN into module via AT command as it should be obtained OTA via OMA-DM.
    • The PDP context where DATA APN is populated may be PDP context 2 or PDP context 3.
  3. The user or application must configure device to use the correct PDP context which contains the data APN received during OMA-DM. (Refer to steps below.)

Determining PDP Context on Sprint Legacy Network

  1. Issue the following command to the device cellular module
    AT+CGDCONT?
  2. Based on location of APN determine which PDP Context to use for data connection.
    Example output #1:
    AT+CGDCONT?
    +CGDCONT: 1,”IP”,”otasn”,”",0,0,0,0
    +CGDCONT: 2,”IP”,”cc.m2m.ispsn”,”",0,0,0,0
    +CGDCONT: 3,”IPV4V6″,”",”",0,0,0,0
    +CGDCONT: 4,”IPV4V6″,”ims”,”",0,0,0,0In above example, PDP context 3 would be used for data connection establishment because it contains the data APN and no APN exists in context 3.
    AT#SGACT=2,1                           If using module internal IP stack
    AT*99***2#                                    If using external IP stackExample output #2
    AT+CGDCONT?
    +CGDCONT: 1,”IP”,”otasn”,”",0,0,0,0
    +CGDCONT: 3,”IPV4V6″,”n.ispsn”,”",0,0,0,0
    +CGDCONT: 5,”IPV4V6″,”ims”,”",0,0,0,0In above example, PDP context 3 would be used for data connection establishment because it contains the data APN and PDP context 2 does not exist.
    AT#SGACT=3,1                           If using module internal IP stack
    AT*99***3#                                   If using external IP stack

For further details on Sprint Activation through their legacy network, see the Sprint DG-OMADM AT Command Guide.