![background image](http://html1.mh-extra.com/html/u-blox/fw75-c200/fw75-c200_system-integration-manual_829464074.webp)
LISA-C2 series and FW75-C200 - System Integration Manual
UBX-13000620 - R21
Early Production Information
Features description
Page 74 of 103
3.5
Carrier Provisioning
3.5.1
Factory NAM settings
Factory Number Assignment Module (NAM) items are of interest when checking if the module is provisioned and
what carrier profile the unit is set up for. The NAM settings include:
•
MDN/MIN
•
Default PRL version
•
MIP Profile
The MDN/MIN from the factory has the format 000000XXXX, with six leading zeros and XXXX representing a
numeric value that may not be zero. After successful provisioning, the MDN/MIN will change to a subscriber
number assigned by the carrier. The $RTN command will restore the MDN/MIN number to the factory value and
format.
From the factory, a default PRL is loaded. This default PRL varies between carriers and changes over time.
Depending on the carrier and geographic location, the PRL may change upon successful provisioning. The $PRL
command is used to check what PRL version is presently loaded in the module. If the default PRL from the
factory has changed, the $RTN command does not restore the PRL to the original factory version that it came
with.
The MIP Profile is specific to each carrier and changes after provisioning. Use AT$QCMIPGETP to check the MIP
profile. Further details on the MIP profile are covered in both this chapter and
LISA-C200 & FW75-C200 AT
commands examples u-blox CDMA 1xRTT wireless modules Application Note
3.5.2
Sprint
3.5.2.1
OMA device management
The OMA device management feature is supported only by Sprint versions.
The OMA-DM process can be divided into three distinct operations:
•
Device configuration
•
PRL programming
•
Firmware update
Each operation can occur as the result of a network initiated trigger, a client initiated trigger, or as part of the
hands-free activation process.
3.5.2.2
Components
The OMA-DM implementation on u-blox CDMA devices is set up by an application library from Red Bend. This
library holds the needed SW components to establish an OMA-DM session for a successful completion of the
device’s provisioning.
The most relevant files involved in the OMA-DM provisioning procedure are: