3G OTW Device Programming

APPL/ID: 3OS CVS Module: 3OS 3OS_STUBS

Application Overview 09/09/2004

Introduction
The OTW application automates what would be a tedious manual process estimated at 1 hour per 3G device to a total time of less than 1 minute per device. Serving primarily as a backup for IOTA at PCS retail stores and affiliates, OTW became the primary means for provisioning devices at the warehouses for Logistics. This 3 tier, enterprise wide application was designed and built completely from scratch by the OTW development team. OTW uses XML for an easier, more open means of exchanging data

Business Process Owners (BPO)

Logistics / Warehouse Operations
Subscriber Equipment Retail Affiliates

OTW Client/User Locations

All PCS Retail Stores
Currently more than 450 locations

All PCS Affiliate Stores

Average of 50 provisioning workstations per affiliate

All PCS Distribution Center Warehouses

More than 80 provisioning workstations

Objectives and Benefits

Objectives:
Eliminate need to visit 4 different PCS back office systems to gather the more than 80 data attributes, and the subsequent manual entry into the 3G device. Automate the association of a subscription with an ESN for a two part activation. Vendor device drivers would be written to a standard framework SDK specification. PCS can publish one standard for all vendors to adhere to. Secure sensitive 3G NAI password data. Reduce training time for end users. Track provisioning throughput to identify source of failures and improve order entry process

Benefits:
Provisioned phones leave warehouse ready for use. Customers can walk out of retail and affiliate locations with a hot phone. Time savings from over 1 hour per provisioned device to approx. 1 minute Less manual entry, less error prone. More secure - users dont have access to sensitive provisioning data. Drives the clean up of the order entry process via the problem order log. All historical provisioning data is logged and tracked, allowing for useful statistics to be gathered later. Users dont have to kick off the activation manually in the biller.

Requirements and Solution

Requirements:
Gather provisioning data from all backend systems via EI BTs For the logistics flow, provision the order in the billing system and associate an ESN to the order Update the status of the order in ASI for proper inventory accounting Encrypt sensitive data in the XML and provide decryption service to vendors Track provisioning successes, failures, and attributes Scalable architecture Determine device characteristics and provision appropriately Clear, user defined error messages to automate problem order log resolution Log /Authenticate requesting workstations Provide ESN Swap functionality

Technical Solution:
3 Tier client server utilizing BEA Weblogic, MQ Series, Oracle database OTW adheres to the Premiere standard framework for thin client application and J2EE technology. Clients utilize Spirent UPST/UMPP thick client and PCS authored data services and decryption services .dlls XML is used as the data transport mechanism, making it easier for all parties (handset vendors, SEBU, NSP, etc.) to interpret the data.

OTW Application Platform

Servers Web/Application Server BEA Weblogic 7.0/MQ Series Database Server Oracle 8.1.7 Client Work Stations Thick - Spirent provided UMPP / UPST PCS authored data services data lookup and decryption services .dll (s) Thin - Calls to provisioning server via HTTP

Notes:
* The Application Platform is common across Premiere thin-client applications such as the
XmlRpcListener webapp, PBS, RMS+ and BOF
* Provisioning Data transported in easier to use XML format

UMPP for Logistics

UPST for Retail / Affiliates

OTW Application Architecture

Handset Vendor Dlls interpret PCS XML provisioning data, write to devices

HTTP / XML Post

OTW Thick Client Provisiong Workstations UMPP (Logistics / Warehouse) UPST (Retail / Affiliates) PCS Authored dlookup.dll for posting to provisioning server PCS Authored blowfish.dll for decryption services

HTTP / XML Reply

Sprint PCS DMZ Firewall is crossed for Affiliate Access

TELESALES H/W
Virtual IP 207.40.65.58

Retail / Affiliates Weblogic instance - Port 7000

Logistics Weblogic instance - Port 8000

MQ Series via Pre

miere architect ure

BLM/ODL Production Server BLM ODL Production

Primary Application Server

Ver ita

Secondary Database Server

MQ Series SPM Veritas Failover Software Detects outages and migrates either application or database to one server

External Disk Array

Logistics Database, MQ Series Retail / Affiliate Database, MQ Series

NMS P2K ASI`

Example of XML Data

Transactions Used By OTW Provisioning

(In Sequence):

GETDVCINFOBT (v1) UPDORDINFOBT (v2) GETSBSCRBRPRFLBT (v1) PROVINVODRPHONEBT (v2) GETINVORDERBT (v3) /or/ SWAPDVCBT (v1) UPDORDINFOBT (v2) UPDSVCORDBT (v1)

NMS ASI SPM P2K P2K P2K ASI SPM

Red indicates not used in the retail / affiliates flow

Transactions Used For MSL Retrieval:

GETDVCBT (v1) NMS

OTW System Interfaces

External
ASI EI P2K NMS SPM

Vendor Provided
Spirent UPST/UMPP Spirent Framework

Automate Lookup of Master Subsidy Lock

In addition to handset provisioning for Retail & Logistics (via DLookup.dll), the OTW application also includes functionality to retrieve the Master Subsidy Lock (MSL) (via ULookup.dll) for a device for such purposes as Reflash, PRL upgrades, etc

Benefits:
Eliminates manual process of looking up the MSL for each action. (reflash, PRL upgrade, etc)
*any activity requiring unlocking of the device software

Reporting Capabilities
All provisioning data related to both BT successes and failures is logged. All 3G provisioning attributes, as well as other attributes not written to the device are stored and available. ESN / MDN, subscription data and ESN provisioning history is available This data is currently accessed only by development and App Admin for production support, but can be expanded to other users to provide searches based on MDN, ESN, SubID, etc. This information is visible via a set of JSPs also included with the web app.

Additional OTW Contributions

The OTW development team has contributed as a technical consultant and liaison between Subscriber Equipment and the handset vendors to assist them with interpreting the Spirent SDK. The OTW Team created several tools for diagnostic purposes, such as a tool for retrieving the XML for successfully provisioned ESNs and a tool to test the vendor decryption.

OTW Application Administration Tools

Throughput Demonstration

Questions and Answers