Microsoft Word - Accuris Networks OTA Solution Description - v1.0

AccuPROFILE OTA
For SMART Telecom
Solution Description
CONFIDENTIAL
Document Version: 1.0

Document Status: Approved
Document Release Date: 10/09/2009
Copyright
© Accuris Networks, April 2009

O’Connell Bridge House,
D’Olier Street,
Dublin 2,
Ireland.
All rights reserved. This document or any part thereof may not, without the prior
consent of Accuris Networks, be copied, reprinted or reproduced in any material form
including but not limited to photocopying, transcribing, transmitting or storing it in any
medium or translating it into any language, in any form or by any means, be it
electronic, mechanical, xerographic, optical, magnetic or otherwise.
The information contained in this document is proprietary and confidential and all
copyright, trade marks, trade names, patents and other intellectual property rights in the
documentation are the exclusive property of Accuris Networks and our partners unless
otherwise specified. The information (including but not limited to data, drawings,
specification, documentation, software listings, source or object code) shall not at any
time be disclosed directly or indirectly to any third party without Accuris Networks prior
written consent.
Whilst the greatest care has been taken to ensure the accuracy of the information
contained herein, Accuris Networks does not warrant the accuracy of same. Accuris
Networks expressly disclaims all and any liability to any person, whether a purchaser of
the publication or not, in respect of anything and of the consequences of anything, done
or omitted to be done by any person in reliance upon the whole or any part of the
contents of this publication. The information contained herein is subject to change
without notice.
Table of Contents
Copyright ...................................................................................................................... ii
Preface ......................................................................................................................... 4
Introduction ................................................................................................................. 7
1.1 Over-the-Air Function (OTAF) ..................................................................................... 7
AccuPROFILE OTA for CDMA ........................................................................................ 7
1.2 Overview ...................................................................................................................... 7

1.3 OTAP Components ..................................................................................................... 7
CSC Provisioning Interfaces......................................................................................... 8
1.4 OTA Service Provisioning Protocol (OSPP) ................................................................ 8

1.5 CBOSS Interface (OTASP in HTTP) ........................................................................... 9
1.6 IVR Interface .............................................................................................................. 10
OTAPA Interface......................................................................................................... 10
1.7 OTAPA in SMPP Protocol ......................................................................................... 10

1.8 OTAPA for MS Activation .......................................................................................... 11
Operational Provisioning............................................................................................ 11
1.9 PRL ............................................................................................................................ 11

1.10 NAM Templates ......................................................................................................... 11
Integration Call Flows ................................................................................................ 12
1.11 OTASP in HTTP ........................................................................................................ 12

1.12 IVR Interface .............................................................................................................. 16
1.13 OTAPA MS Activation ............................................................................................... 18
SNMP Aggregation ..................................................................................................... 19
1.14 System Elements ....................................................................................................... 19

1.15 ZTE NMS Integration ................................................................................................. 19
1.16 SNMP Historical Store ............................................................................................... 19
1.17 SNMP MiBs ............................................................................................................... 19
Confidential and Copyright © Accuris Networks 2009

Preface
Purpose
This document describes the OTA solution proposed to Acision for SMART PTT.
Audience
The intended audience for this document is Accuris Networks resellers and customers and
provides sufficient detail for the network planning and marketing organizations to understand
the content of the release and to make decisions regarding its deployment in their network.
Scope
This Solution Description provides a first glance at the product and its context and relation to
other product and contains a description of the functionality and interfaces to external systems.
High-level implementation details are also included.

Typographic conventions
In this document, the typographic conventions are listed below.
Typeface or Symbol Meaning/Used for Example

Courier Refers to a keyboard key, system The directory data contains…
command, label, button, filename,
window, or other computer Click the Close button to…
component or output.
<courier> Serves as a placeholder for Use the file name <entity>.cfg
variable text that the user will for...
replace as appropriate to its
context.
[] Refers the user to external [ETSI 03.38]
documentation listed in the
References section.
Italic Emphasises a new word or term of Jumpstart, the install procedure on a

significance. SUN T1,
% Denotes a Unix regular-user % ls
prompt for C shell.
# Denotes a Unix super-user prompt # ls
for any shell.
\ Denotes line continuation; the % grep searchforthis \
character should be ignored as the data/*.dat
user types the example, and Enter
$ search [.data]*.dat -
should only be pressed after the
searchforthis
last line.
- Bridges two keystrokes that should If Ctrl-C does not work, use Ctrl-
be pressed simultaneously. Alt-Del.
Denotes a “note”, a piece of text Note that the system is usually...

alongside the normal text requiring
extra attention.

Introduction
1.1 Over-the-Air Function (OTAF)
The Over-the-Air Function (OTAF) is a network element which enables CDMA mobile handsets
to be activated and programmed remotely. AccuPROFILE OTA is Accuris Network’s
implementation of an OTAF node in CDMA networks. An Over-the-Air platform has two main
components:
Initial activation is used to remotely activate mobile phones by sending messages
containing information which identifies the phone, authenticates it on the network and
provides details about roaming information relevant to that carrier. Once they have
purchased the phone, the initial activation is initiated by the subscriber.
Re-programming is used to update the roaming database within the phone but can also
be used to update other parameters relevant to the subscriber. This service is initiated by
the network operator and does not require user intervention.
AccuPROFILE OTA for CDMA

1.2 Overview
Within the CDMA network environment, the two main OTA functions are referred to as:
OTASP (Over-the-air Service Provisioning) which is used to remotely activate mobile
phones. OTASP supports an initial activation where a MIN (and also other data) is assigned
to a subscriber, and reprogramming of a subscription for a previously activated mobile
phone. An OTASP message transmitted to a phone can contain information such as Numeric
Assignment Module and Preferred Roaming data. Subscribers initiate OTASP using their
mobile handset and AccuPROFILE OTA can be configured to automatically send a welcome
message to the mobile phone after an initial activation has been performed.
OTAPA (Over-the-air Handset Programming) is used to perform both the download of
Preferred Roaming Lists to the handset and reprogramming of NAM data. The network
operator initiates OTAPA from either a Customer Service Centre, Home Location Register, or
from the AccuPROFILE OTA platform.
1.3 OTAP Components
Within the context of mobile networks, OTAF is the node which enables CSC applications to
manage OTASP and OTAPA sessions.
AccuPROFILE OTA is comprised of the following components:

System Core - responsible for message acceptance, storage, routing and reattempt of
failed deliveries. The CSC interface and the network interface components communicate via
the core.
CSC Interface - a TCP/IP-based interface used to submit messages to OTAP for
subsequent delivery to mobile handsets.
Mobile Network Interface - containing the software components to support CDMA-based
networks. AccuPROFILE OTA supports the following services:
⋅ OTA to handset - defined by IS-683-X;

⋅ OTA to network - defined by IS-725A. Two variants of the SS7 stack are supported as
follows:
⋅ ANSI SS7 MTP (1992), ANSI SS7 SCCP (1992), ANSI SS7 TCAP (1992); and
⋅ ITU SS7 MTP, ITU SS7 SCCP (1992), ANSI SS7 TCAP (1992);
System Administration and Management Interfaces are user interfaces for operation,
administration, and maintenance of the system. There is also a service activation terminal
(CSAT) which provides data entry, data validation, and data display screens for OTA
provisioning process. CSAT is a Java-based graphical user interface.
As part of this proposal Accuris Networks will extend the provided interfaces to allow for
easy integration with SMART’s current CBOSS provisioning system.
The following diagram illustrates at a high level, the interaction between the main components
and network elements:
Figure 1: High Level Overview
CSC Provisioning Interfaces

CSC provisioning interfaces refers to customer ‘facing’ interfaces to AccuPROFILE.
1.4 OTA Service Provisioning Protocol (OSPP)
AccuPROFILE OTA supports two provisioning interfaces which allows integration with other
systems in the customer service centre so that they can perform provisioning operations. These
CSC-based systems connect to AccuPROFILE through a LAN or WAN over TCP/IP for OTASP
and OTAPA provisioning.
The OTASP interface is referred to as OTA Service Provisioning Protocol. OSPP is an open
protocol designed to provide an application interface to an Over-the-Air Platform. It is Accuris
Network’s primary provisioning protocol for interfacing between AccuPROFILE and CSC-based
OTA applications and it enables OTA-based applications to submit OTASP based requests to
AccuPROFILE and provides return responses for each application-initiated operation. Up to 100
CSC links are included in all initial configurations of AccuPROFILE OTA.
The OSPP interface is published by Accuris Networks and is freely available on request. The
OSPP interface enables the following operations (refer to the OSPP specification for further
detail):
Bind – makes a connection to AccuPROFILE OTA and authenticates the CSC user.

Attach – initiates call to the handset using the Temporary Reference Number (TRN) to
identify the MSC to which the handset is connected.
Proceed – verifies the data received.
Download – sends data to the handset. (e.g. NAM Data blocks, PRL, New directory number,
IMSI. It is also possible to unlock the phone and/or reprogram SPC as part of the
download.)
Commit – Write data to permanent memory of handset.
Detach – terminate session.
1.5 CBOSS Interface (OTASP in HTTP)
As mentioned, as part of this proposal Accuris Networks will extend the current provisioning
interfaces to allow for easy integration with the CBOSS provisioning system.
In this context the current CBOSS application will act as the CSC for the OTAP.
Figure 2: Proposed CBOSS Interface
The proposed extension is called OTASP in HTTP. An appropriately formatted HTTP GET
request is serviced by AccuPROFILE at a pre-defined URL on the AccuPROFILE server(s).
Primary and Secondary URL’s will be available for redundancy / traffic balancing.
The following actions will be available:
• (Auto) Program Device
o TRN provided in HTTP GET request
o MDN/MIN provided in HTTP GET request
o NAM and PRL selected automatically by AccuPROFILE
• Program Device

o MDN/MIN provided in HTTP GET request
o NAM Template ID in HTTP GET request
o PRL ID provided in HTTP GET request
• (Auto) PRL Download
o PRL selected automatically by AccuPROFILE
• PRL Download
o PRL ID provided by CBOSS
A technical description of this proposed interface is detailed in Appendix A.
1.6 IVR Interface
As part of this proposal Accuris Networks will include an IVR to automated provisioning of
handsets and manual PRL updates.
In this context the VoxPilot IVR application will act as the CSC for the OTAP.
The following options will be available from the IVR:
• (Auto) Program Device
o User prompted for PIN
o The Device ID will be retrieved by AccuPROFILE from the handset.
o The Device ID and PoC will be used to select an available MDN/MIN from the
CBOSS system and initiate a HLR update.
Note: PoC will have been stored by AccuPROFILE from the initial
Registration Notification.
o NAM and PRL selected automatically by AccuPROFILE.
• (Auto) PRL Download
o User prompted for PIN
o PRL selected automatically by AccuPROFILE
Note: a technical description of the CBOSS Oracle API is pending from CBOSS.
OTAPA Interface
1.7 OTAPA in SMPP Protocol
The OTAPA interface is referred to as “OTAPA in SMPP”. “OTAPA in SMPP” is an open

protocol designed to provide an ESME or SMPP application interface to the Over-the-Air
Platform. It is Accuris Network’s primary provisioning protocol for interfacing between
10

AccuPROFILE and batch OTA applications and it enables ESME applications to submit OTAPA
requests to AccuPROFILE.
The “OTAPA in SMPP” interface is published by Accuris Networks and is freely available on
request.
The “OTAPA in SMPP” interface enables the following operations:

• NAM Download
• Basic PRL Numbering Download
• Extended PRL Numbering Download
• Default PRL Numbering Download
• Basic PRL Numbering Download with Old SPC
• Extended PRL Numbering Download with Old SPC
• Default PRL Numbering Download with Old SPC
• SPC Management
• A-Key Generation with Optional Procedures
• A-Key Generation with Optional Procedures and PRL
1.8 OTAPA for MS Activation
In addition to the standard OTAPA functionality an additional trigger will be provided to

provision ESN/MEID for activation handsets.
Operational Provisioning
1.9 PRL
Binary PRLs are created by the operator as appropriate to their roaming requirements.
Binary PRLs will be provisioned on the AccuPROFILE system. Refer to the AccuPROFILE
System Administration Guide for full details on PRL provisioning.
1.10 NAM Templates
NAM Templates provide a set of default value for provisioning the NAM data block on a phone
or RUIM card.
Templates are provisioned on the AccuPROFILE system. Refer to the AccuPROFILE System
Administration Guide for full details on NAM Template provisioning.
11

Integration Call Flows
1.11 OTASP in HTTP
Figure 3: (Auto) Program Device
12

Figure 4: Program Device
13

Figure 5: (Auto) PRL Download
14

Figure 6: PRL Download
15

1.12 IVR Interface
Figure 7: (Auto) Program Device
Note: Device ID previously provisioned in AccuPROFILE as an Activation Device via OTAPA in

SMPP. Device currently registered on AccuPROFILE AHLR.
16

Figure 8: PRL Download
17

1.13 OTAPA MS Activation
Figure 9: OTAPA for MS Activation
18

SNMP Aggregation
1.14 System Elements
The following elements in the AccuPROFILE solution produce SNMP traps:
• AccuPROFILE OTA and AHLR
• VoxPilot IVR
• Oracle 10g
• HP ProCurve Switches
• HP DL380 / Red Hat Linux
1.15 ZTE NMS Integration
To ease the integration into the existing ZTE NMS we propose providing an SNMP aggregator
as part of our solution to SMART.
All elements will be configured to forward traps to the aggregator. The aggregator will save the
trap in a historical store and relay it to the ZTE NMS.
Figure 10: SNMP Aggregator
This provides a single point of integration to the ZTE NMS for SNMP trap management.
1.16 SNMP Historical Store
All traps will be logged in a format to be agreed with ZTE. The logs will be retrievable in the
event of a failure in communications with the NMS to allow for trap re-synch.
1.17 SNMP MiBs
A full set of MIBs for the system accompanies this document.
19

Appendix A. OTASP in HTTP
(Auto) Program Device
The Request URI contains the TRN and selected MDN
http://ota.smart.com/OTAConsole/OTAAction.do?action=csc&operation=programMDN
&mdn=123456789&trn=1147290899
Request Method: GET

Request URI:
/OTAConsole/OTAAction.do?action=csc&operation=programMDN&mdn=123456789&trn=1
147290899
Request Version: HTTP/1.0
Host: 192.168.1.1:8080\r\n
Accept: */*\r\n
User-Agent: WIC\r\n
\r\n
Program Device
The Request URI contains the TRN, selected MDN, selected NAM Template ID,
selected PRL
http://ota.smart.com/OTAConsole/OTAAction.do?action=csc&operation=programMDN
&mdn=123456789&trn=1147290899&prlid=12345&namid=1
Request Method: GET

Request URI:
/OTAConsole/OTAAction.do?action=csc&operation=programMDN&mdn=123456789&trn=1
147290899&prlid=12345&namid=1
Host: 192.168.1.1:8080\r\n
Accept: */*\r\n
User-Agent: WIC\r\n
\r\n
(Auto) PRL Download
The Request URI contains the TRN
http://ota.smart.com/OTAConsole/OTAAction.do?action=csc&operation=downloadPR
L&trn=1147290899
20

Request Method: GET
Request URI:
/OTAConsole/OTAAction.do?action=csc&operation=downloadPRL&trn=1147290899
Host: 192.168.1.1:8080\r\n
Accept: */*\r\n
User-Agent: WIC\r\n
\r\n
PRL Download
The Request URI contains the TRN and PRL ID
http://ota.smart.com/OTAConsole/OTAAction.do?action=csc&operation=downloadPR
L&trn=1147290899&prlid=1234
Request Method: GET

Request URI:
/OTAConsole/OTAAction.do?action=csc&operation=downloadPRL&trn=1147290899&prl
id=12345
Host: 192.168.1.1:8080\r\n
Accept: */*\r\n
User-Agent: WIC\r\n
\r\n
Successful Response from AccuPROFILE
Hypertext Transfer Protocol

HTTP/1.1 200 OK\r\n
Response Code: 200
Path=/OTAConsole\r\n
ETag: W/"71-1078353310000"\r\n
Last-Modified: Tue, 06 May 2009 22:35:10 GMT\r\n
Content-Type: text/html\r\n
Content-Length: 71\r\n
Date: Thu, 07 May 2009 15:58:18 GMT\r\n
Server: libhttpd/1.1\r\n
Connection: close\r\n
\r\n
Line-based text data: text/html
programming-result=0000&programming-result-desc=OTA Programming Success
Error Response from AccuPROFILE
Hypertext Transfer Protocol

HTTP/1.1 200 OK\r\n
21

Response Code: 200
Path=/OTAConsole\r\n
ETag: W/"71-1078353310000"\r\n
Last-Modified: Tue, 06 May 2009 22:35:10 GMT\r\n
Content-Type: text/html\r\n
Content-Length: 71\r\n
Date: Thu, 07 May 2009 15:58:18 GMT\r\n
Server: libhttpd/1.1\r\n
Connection: close\r\n
\r\n
Line-based text data: text/html
programming-result=0001&programming-result-desc=OTA Programming Failure
22

Appendix B. CBOSS Oracle API
TBC – Awaiting information from CBOSS.
23

Appendix C. PoC / HLR Areas
Current list of PoC / HLR areas.
Jawa Island
Jakarta - SDC
- BSD
Bandung
Semarang
Yogyakarta
Surabaya
Malang
Sumatra
Medan
Palembang
Sulawesi
Makassar
24

Microsoft Word - Accuris Networks OTA Solution Description - v1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Microsoft Word - Accuris Networks OTA Solution Description - v1.0

Uploaded by

Copyright:

Available Formats

AccuPROFILE OTA

For SMART Telecom

Document Version: 1.0

© Accuris Networks, April 2009

1.1 Over-the-Air Function (OTAF) ..................................................................................... 7

AccuPROFILE OTA for CDMA ........................................................................................ 7

1.2 Overview ...................................................................................................................... 7

CSC Provisioning Interfaces......................................................................................... 8

1.4 OTA Service Provisioning Protocol (OSPP) ................................................................ 8

1.7 OTAPA in SMPP Protocol ......................................................................................... 10

1.9 PRL ............................................................................................................................ 11

Integration Call Flows ................................................................................................ 12

1.11 OTASP in HTTP ........................................................................................................ 12

SNMP Aggregation ..................................................................................................... 19

1.14 System Elements ....................................................................................................... 19

Confidential and Copyright © Accuris Networks 2009

Confidential and Copyright © Accuris Networks 2009

Typeface or Symbol Meaning/Used for Example

Italic Emphasises a new word or term of Jumpstart, the install procedure on a

Denotes a “note”, a piece of text Note that the system is usually...

Confidential and Copyright © Accuris Networks 2009

AccuPROFILE OTA for CDMA

1.3 OTAP Components

AccuPROFILE OTA is comprised of the following components:

Confidential and Copyright © Accuris Networks 2009

Figure 1: High Level Overview

CSC Provisioning Interfaces

1.4 OTA Service Provisioning Protocol (OSPP)

Confidential and Copyright © Accuris Networks 2009

1.5 CBOSS Interface (OTASP in HTTP)

Figure 2: Proposed CBOSS Interface

The following actions will be available:

• (Auto) Program Device

o TRN provided in HTTP GET request

o MDN/MIN provided in HTTP GET request

o NAM and PRL selected automatically by AccuPROFILE

Confidential and Copyright © Accuris Networks 2009

o MDN/MIN provided in HTTP GET request

o NAM Template ID in HTTP GET request

o PRL ID provided in HTTP GET request

• (Auto) PRL Download

o TRN provided in HTTP GET request

o PRL selected automatically by AccuPROFILE

o TRN provided in HTTP GET request

o PRL ID provided by CBOSS

A technical description of this proposed interface is detailed in Appendix A.

1.6 IVR Interface

The following options will be available from the IVR:

• (Auto) Program Device

o User prompted for PIN

o The Device ID will be retrieved by AccuPROFILE from the handset.

o NAM and PRL selected automatically by AccuPROFILE.

• (Auto) PRL Download

o User prompted for PIN

o PRL selected automatically by AccuPROFILE

The OTAPA interface is referred to as “OTAPA in SMPP”. “OTAPA in SMPP” is an open

Confidential and Copyright © Accuris Networks 2009

The “OTAPA in SMPP” interface enables the following operations:

In addition to the standard OTAPA functionality an additional trigger will be provided to

1.10 NAM Templates

Confidential and Copyright © Accuris Networks 2009

Figure 3: (Auto) Program Device

Confidential and Copyright © Accuris Networks 2009