Release Notes Archive

New in 4.22 Generation 2 (January 2018)

Feature Description
Remove Unused Devices

A new DeleteDevices API method lets you remove deactivated devices from an account. Devices are removed immediately. You can use this method instead of contacting Verizon Customer Support to request device removal.

The DeviceService WSDL has been updated for this change, and UWS Explorer has been enhanced to include the new functionality.

New in 4.20 Generation 2 (November 2017)

Feature Description
Get account numbers and names

Account names and numbers are the same for most accounts, in the format ##########-##### (10 digits, a hyphen, then five more digits). Some accounts have different names, though, and you can use the new GetAccountInformation API to find out. You can provide either an account name or an account number in the request, and the response will contain both the name and number for the account.

The AccountService WSDL has been updated for this change, and UWS Explorer has been enhanced to include the new functionality.

Validate account ownership of devices

The GetDevicesInformation API accepts a list of devices and either an account name or number, and returns a validation of whether each device is in the account, plus a subset of information about each device. You can use this API to verify account ownership of devices before sending other API requests that would return errors if devices are not in a specified account.

The DeviceService WSDL has been updated for this change, and UWS Explorer has been enhanced to include the new functionality.

Find SIM-to-device mismatches

Original equipment manufacturers (OEMs) upload device information to Verizon, and for some devices that includes the ID of the device that a particular SIM card is expected to be installed in. SIMs may be moved between devices, though, so the expected pairing doesn't always occur, or may change once the SIM is in use. The new GetImeiMismatch API checks a provided list of devices to see if the SIMs were activated in different device during a specified time frame.

The DeviceService WSDL has been updated for this change, and UWS Explorer has been enhanced to include the new functionality.

New in 4.16 Generation 2 (July 2017)

Feature Description
SMS usage separated into mobile-originated and mobile-terminated messages

The GetDeviceUsageHistory response and the GetAggregateDeviceUsage callback now show separate totals for the number of SMS messages sent to devices (mobile terminated, or MT) and received from devices (mobile originated, or MO), as well as the total number of SMS messages during a reporting period.

There are no WSDL or schema updates required for this change, so the SDK has not been updated.

Roaming Country

The GetDeviceInformation and GetDeviceList responses now include a new RoamingCountry extended attribute that contains the name of a country if RoamingStatus = Roaming, or empty if NotRoaming.

There are no WSDL or schema updates required for this change, so the SDK has not been updated.

New in 4.15 Generation 2 (June 2017)

Feature Description
Pre-activation device availability check

The new CheckDeviceAvailability API enables you to verify that your devices are ready for new service before you request activations. The API checks that devices are certified for the Verizon Wireless Network, registered with Verizon by the manufacturer, and not already active with a mobile terminal number (MTN).

The asynchronous response is sent by a new DeviceService callback service.

The DeviceService WSDL has been updated for this change, and there is a new callback in the callback schema. UWS Explorer has also been updated to include the new functionality.

New in 4.13 Generation 2 (April 2017)

Feature Description
Callback retry enhancements

All callbacks now include CallbackCount and MaxCallbackThreshold parameters to provide information about callback retries for unsuccessful callbacks.

  • CallbackCount respresents the number of times the M2M Platform has attempted to send the current callback. The first attempt will have a value of 1. If the callback fails (that is, the receiving system does not acknowledge receiving it), the M2M Platform will try again in 5 minutes and the value will be incremented to 2. This will continue until the MaxCallbackThreshold value has been reached, and the callback will not be sent again after that.
  • MaxCallbackThreshold is the number of times that the M2M Platform will attempt to send a callback. It has a fixed value of 4.

There are no WSDL or schema updates required for this change, so the SDK has not been updated. The 4.7 SDK (October 2016) is still the most current version.

New in 4.7 Generation 2 (October 2016)

Feature Description
GetDeviceList response can include up to 2000 devices The GetDeviceList request now accepts an optional MaxNumberOfDevices parameter to specify the maximum number of devices that the customer wants included in each response. The default value is 500, which is the number of devices per response in versions 4.6 and earlier.

New in 4.4.6 Generation 2 (March 2016)

Feature Description
Customer Name returned in GetLeadInformation response

The customer name is now returned as an Extended Attribute in the response to a GetLeadInformation request.

There are no WSDL or schema updates required for this change.

Pagination support in GetDeviceGroupList response By default, GetDeviceGroupList returns a single response that contains information about the first 500 device groups in an account (sorted alphabetically by name). Optional input parameters in 4.4.6 let you paginate the response by specifying the number of groups that you would like returned in each "page" of the response, and which "page" of the total set you want.

New in 4.4.5 Generation 2 (November 2015)

Feature Description
Ability to reactivate 4G devices immediately after deactivation The Verizon M2M platform now supports immediate activation of prior deactivated 4G SIMs without an aging requirement. This enables M2M customers to reuse and deploy SIM cards in 4G devices immediately, i.e., even within the previously mandated 50 day aging period after deactivations.
Automatic retry of failed callbacks

Unacknowledged callback messages will be retried 3 times at 5 minute intervals, for a total of 4 attempts to send the message.

Failed callback messages will be archived for 30 days. During the 30 day period, customers can contact support with the Request ID of failed callbacks and ask for them to be resent.

New callback and device information about OTA completion

The IMEI and SKU associated with a SIM can change when a device completes the Over-The-Air (OTA) Activation procedure. To help customers track these changes:

  • The M2M Platform will send an ExternalProvisioningChanges callback when a device completes OTA activation.
  • The callback contains the values of the IMEI and SKU prior to OTA Activation, and the timestamp of the most recent OTA Activation.
  • The GetDeviceInformation and GetDeviceList APIs return new extended attributes containing the IMEI and SKU prior to OTA Activation and the timestamp of the most recent OTA Activation.
Callback port number restriction Beginning 11/18/2015, the M2M Platform will restrict the ports you can register with Callback Service to 80, 443, 9001 to 9006 and 50551 to 50559. Existing registered ports, even if not in the allowed range, will continue to work after 11/18/2015. However, if you attempt to register a new Callback URL after 11/18/2015, you must register using an in-range port.
Mediated Usage Data The data returned by the GetAggregateDeviceUsage and GetDeviceUsageHistory APIs is now mediated instead of raw, and can be used to better estimate usage during the billing cycle. These APIs provide data that is more in line with invoices than the data returned by the GetRatedDeviceUsage API, so the latter is being deprecated. It will continue to function in the 4.4.5 release, but will return an error message in the next release.
Change in Data Retention Policy

Beginning December 1, 2015, Verizon will begin deleting historical records from the M2M Platform database in keeping with the data retention policy outlined below. This action will limit the amount of historical data that you can access using the Wireless Network Services APIs.

System Logs The information contained in the Master Log, Transaction History Report and Notification Log will be kept for 12 months. Log data that is older than 12 months will be deleted.

Usage Reports The information contained in the Device Usage Report, Aggregated Usage Report and Rated Usage Report will be kept for 12 months. Log data that is older than 12 months will be deleted.

Connection Reports The information contained in the Connection History Report and Connected Session History Report will be kept for 3 months. Log data that is older than 3 months will be deleted.

If you want to retain historical data before it is deleted, please use the appropriate API to retrieve the data from the M2M Platform and store it on your local resources.

New in 4.4.4 Generation 2 (August 2015)

Feature Description
Support for device cost center codes

Cost center codes can be set when devices are activated, and can be updated or removed at any time.

  • The ChangeDeviceState-Activate API has been enhanced to allow assigning a cost center code when activating devices. All devices in an activation request will use the same cost center code value, if specified.
  • A new ChangeDeviceCostCenter API allows changing or removing a cost center code from one or more devices.
  • The GetDeviceInformation and GetDeviceList APIs have been enhanced to return the cost center code as an extended attribute.
SKU-based activations for 4G devices with embedded SIMs

4G devices with embedded SIMs can be activated by providing the SIM ICCID and a SKU that identifies the device type.

More devices per request The maximum number of devices for APIs that accept more than one device per request has been increased from 2,000 to 10,000. (AddDevices is still limited to 200 devices per request.)