otw overview

8/3/2019 OTW OverView

1/20

3G OTW Device Programming

APPL/ID: 3OS

CVS Module: 3OS

3OS_STUBS

Application Overview

09/09/2004


2/20

Introduction The OTW application automates what would be a tedious

manual process estimated at 1 hour per 3G device to a totaltime of less than 1 minute per device.

Serving primarily as a backup for IOTA at PCS retail storesand affiliates, OTW became the primary means forprovisioning devices at the warehouses for Logistics.

This 3 tier, enterprise wide application was designed and

built completely from scratch by the OTW developmentteam.

OTW uses XML for an easier, more open means ofexchanging data


3/20

Logistics / Warehouse Operations

Subscriber Equipment

Retail

Affiliates

Business Process Owners (BPO)


4/20

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

OTW Client/User Locations


5/20

Objectives: Eliminate need to visit 4 different PCS back

office systems to gather the more than 80 dataattributes, and the subsequent manual entryinto the 3G device.

Automate the association of a subscription

with an ESN for a two part activation.

Vendor device drivers would be written to astandard framework SDK specification. PCScan publish one standard for all vendors toadhere to.

Secure sensitive 3G NAI password data.

Reduce training time for end users.Track provisioning throughput to identify

source of failures and improve order entryprocess

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 minuteLess 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 loggedand tracked, allowing for useful statistics

to be gathered later.

Users dont have to kick off the

activation manually in the biller.

Objectives and Benefits


6/20

Technical Solution: 3 Tier client server utilizing BEA

Weblogic, MQ Series, Oracledatabase

OTW adheres to the Premiere

standard framework for thin client

application and J2EE technology. Clients utilize Spirent UPST/UMPP

thick client and PCS authored dataservices 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.

Requirements: Gather provisioning data from all

backend systems via EI BTs For the logistics flow, provision the order

in the billing system and associate anESN 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

Requirements and Solution


7/20

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

OTW Application Platform

Notes:

* The Application Platform is common across Premiere thin-client applications such as theXmlRpcListener webapp, PBS, RMS+ and BOF

* Provisioning Data transported in easier to use XML format


8/20

UMPP for Logistics


9/20

UPST for Retail / Affiliates


10/20

OTW Application Architecture

Sprint PCSDMZ Firewall is

crossed forAffiliate Access

Secondary Database

Server

OTW Thick Client Provisiong WorkstationsUMPP (Logistics / Warehouse)

UPST (Retail / Affiliates)

PCS Authored dlookup.dll for posting to provisioning serverPCS Authored blowfish.dll for decryption services

HTTP / XML Reply

MQSeriesviaPremierearchitecture

P2K

BLM

MQSeries

ODL

Production

BLM/ODL Production Server

HTTP / XML Post

SPM

ASI`

Veritas

NMS

Logistics

Database,

MQ Series

Retail /

Affiliate

Database,

MQ Series

External Disk Array

Handset VendorDlls interpret PCSXML provisioning

data, write todevices

Virtual IP207.40.65.58

Retail / AffiliatesWeblogic

instance - Port7000

LogisticsWeblogic

instance - Port8000

PrimaryApplication

Server

Veritas Failover Software Detectsoutages and migrates either

application or database to oneserver

TELESALES H/W


11/20

Example of XML Data


12/20

Transactions Used By OTW Provisioning(In Sequence):

GETDVCINFOBT (v1) - NMS

UPDORDINFOBT (v2) - ASI

GETSBSCRBRPRFLBT (v1) - SPM

PROVINVODRPHONEBT (v2) - P2K

GETINVORDERBT (v3) - P2K/or/SWAPDVCBT (v1) - P2K

UPDORDINFOBT (v2) - ASI

UPDSVCORDBT (v1) - SPM

Red indicates not used in the retail / affiliates flow


13/20

Transactions Used For MSL Retrieval:

GETDVCBT (v1) - NMS


14/20

External ASI

EI

P2K NMS

SPM

Vendor Provided Spirent UPST/UMPP Spirent Framework

OTW System Interfaces


15/20


16/20

Reporting Capabilities

All provisioning data related to both BT successes and failuresis 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 historyis available This data is currently accessed only by development and App

Admin for production support, but can be expanded to otherusers to provide searches based on MDN, ESN, SubID, etc.

This information is visible via a set of JSPs also included withthe web app.


17/20

Additional OTW Contributions The OTW development team has contributed as a technical

consultant and liaison between Subscriber Equipment andthe 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 forsuccessfully provisioned ESNs and a tool to test the vendordecryption.


18/20

OTW Application Administration Tools


19/20

Throughput Demonstration


20/20

Questions and Answers

otw overview

Documents