OTA Product Description

OTA V100R001 Product Description

Huawei Technologies Co., Ltd.

.

OTA Product Description Confidential

Contents

Chapter 1 OTA Overview................................................................................................................1

Chapter 2 System Architecture.....................................................................................................22.1 With ADD System Architecture...........................................................................................22.2 Without ADD System Architecture......................................................................................42.3 Module Functions................................................................................................................5

Chapter 3 Roles in the OTA System.............................................................................................73.1 System Administrator..........................................................................................................73.2 Customer Service Agent.....................................................................................................7

Chapter 4 System Features...........................................................................................................74.1 Configurable Profiles...........................................................................................................74.2 Adding and Editing WAP Settings.......................................................................................94.3 Adding and Editing Email Settings....................................................................................104.4 Adding and Editing Text SMS...........................................................................................104.5 Sending Profile..................................................................................................................114.6 Sending MMS Settings......................................................................................................114.7 Sending Email Settings.....................................................................................................114.8 Sending Bookmark Settings..............................................................................................124.9 Sending Text SMS............................................................................................................124.10 Configuring Videotelephony and Video Stream...............................................................134.11 Bulk Provisioning.............................................................................................................134.12 Web Help........................................................................................................................ 134.13 Open API......................................................................................................................... 134.14 Trigger Modes................................................................................................................. 14

Chapter 5 System Running Statistics and Reports...................................................................18

Chapter 6 Mobile Phone Support................................................................................................206.1 Online Upgrade of Mobile Phones....................................................................................206.2 Supported Mobile Phones.................................................................................................20

Chapter 7 Networking and External Interfaces..........................................................................217.1 Networking........................................................................................................................ 217.2 External Interfaces............................................................................................................21

Abbreviations.................................................................................................................................. 23

.

.

i

Chapter 1 OTA Overview

With the development of mobile communication technologies, mobile phones can support more and more value added services (VAS), such as SMS, GPRS, WAP, MMS, and E-mail. However, to support these services, subscriber needs to spend much time on parameters configuration.

Auto configuration is implemented over the short message service (SMS). The OTA specifications stipulate that the parameters are encapsulated in a certain format, and then sent to mobile phones as short messages. After being received by mobile phones, the short messages are converted to parameters. The configuration can be implemented easily.

The OTA specifications enable carriers to update parameters conveniently and facilitate the configuration on mobile phones. Through Huawei OTA solution, subscriber can configure their mobile phones by various means.

Currently, Huawei OTA can be supported by more than 1180 models of mobile phones, including the third generation (3G) mobile phones.

.

.

Page 1 of 26

Chapter 2 System Architecture

2.1 With ADD System Architecture

Figure 1-1 OTA with ADD

.

.

Page 2 of 26

Figure 1-2 OTA with ADD and EIR

OTA system with ADD consists of four modules, namely Automatically Device Detection (ADD), Advanced Device Capability System (ADCS), Mobile Configurator (MC), and Device Management Server (DMS).

EIR system is not provided by OTA system, if there is EIR system onsite, we need to integrate ADD with EIR system.

OTA service with ADD can be triggered by:

Switch-on auto detection SMS short code WEB portal

.

.

Page 3 of 26

2.2 Without ADD System Architecture

Figure 1-3 OTA without ADD

OTA system without ADD consists of three modules, namely the Device Capability System (DCS), Mobile Configurator (MC), and Device Management Server (DMS).

OTA service without ADD can be triggered by:

SMS short code WEB portal

2.3 Module Functions

2.3.1 ADCS

The ADCS module manages the IMEI data of mobile phones. It stores and maintains the names, models, and mapping with MSISDN of the registered mobile phones.

.

.

Page 4 of 26

Besides, it receives the information on the {IMEI, MSISDN, IMSI} combination reported by the ADD. Moreover, it maintains the mapping between IMSI, IMEI, and MSISDN. When the mapping between IMSI, IMEI, and MSISDN is changed, the ADCS sends a configuration command to the DMS through the SOAP interface on MC and thus triggers an automatic device configuration.

2.3.2 DCS

The DCS module manages the IMEI data of mobile phones. It stores and maintains the names, models, and mapping with MSISDN of the registered mobile phones.

2.3.3 MC

The functions of the MC are as follows:

MC is a graphic user interface (GUI) of the OTA system. Moreover, it acts as an interface between users and OTA system. Users can perform configurations on the OTA system through the MC.

As an adaptor between ADCS and DMS server, the MC interacts with the DMS server through the PAP protocol.

The MC encapsulates the service logics for mobile phone configuration. It also provides a SOAP interface for integrating with Portal system.

For example:

An administrator defines a group group A, which includes service configuration item X (MMS and GPRS).

The administrator also defines a group group B, which includes service configuration item Y (MMS, GPRS, E-mail and bookmark).

If the administrator allocates subscriber P900 to group A, the administrator sends an OTA Configuration containing MMS and GPRS to the subscriber.

If the administrator allocates subscriber P900 to group B, the administrator sends an OTA Configuration containing MMS, GPRS, E-mail and bookmark to the subscriber.

2.3.4 DMS

The DMS receives and resolves the OTA provisioning request, which is in the PAP format, sent from the MC through HTTP.

A provisioning request contains:

Target MS type SMSC Message type, such as WAP, MMS, and E-mail

The DMS server creates a configuration short message based on the provisioning request, and sends it to the bearer SMSC. Then, the SMSC forwards the short message to the mobile phone.

The DMS server and the MC communicate with each other through HTTP RPC. Therefore, users can choose the MC as the client GUI to logon the DMS server.

The DMS server can send messages based on any of the following SMSC protocols:

SMPP 3.3/3.4 UCP CIMD 2

2.3.5 Supported Standards and Protocols

OTA supports the following provisioning standards and protocols.

.

.

Page 5 of 26

Nokia-Ericsson OTA Specification 7.0/7.1 OMA-CP 1.1 Openwave Primary Provisioning Browser v3-6.x Smart Messaging 3.0.0 WAP 2.0 Provisioning Bootstrap

2.3.6 Supported Settings

OTA supports the following settings.

WAP MMS GPRS/APN/Internet Bookmarks Email Push to Talk Video Streaming Wireless Village Home Page Presence

.

.

Page 6 of 26

Chapter 3 Roles in the OTA System

In system design, the roles of OTA users are fully considered.

3.1 System Administrator

System administrators are authorized to use all the functions of the mobile configurator (MC), such as creating and updating the mobile phone information, configuration, and profile.

In addition, system administrators manage all the accounts and access points, namely the IP access points, of the system (It’s a security mechanism).

3.2 Customer Service Agent

Customer service agents can:

Send profiles. Send text SMS. Send WAP, MMS, E-mail configuration parameters. Provision the configuration in batches. Monitor the process status in batches.

For the sake of security, customer service agents are not allowed to add or edit system configuration or profiles.

The remote agents access the system through source IP address filtering. This enhances the system security.

Chapter 4 System Features

4.1 Configurable Profiles

Profiles are the aggregation of OTA messages.

The DMS provides flexible profile management. Each mobile phone model can have multiple profiles. Therefore,

Carriers can be provided with profiles no matter which services the carriers launched.

The workload of maintenance can be minimized. For example, if the access code is changed, the CSR administrator needs to change the setting of a profile, and the settings of other profiles are changed automatically.

.

.

Page 7 of 26

Figure 1-4 Configure Profile

The following figure shows how to create a profile with multiple components.

Figure 1-5 Profile components

The following components can be added to a profile at the same time or one by one:

WAP setting MMS E-mail server

.

.

Page 8 of 26

Phone 1Type: T68

Group 1ID:1Homepage:http://wap.telia.se

Configuration 1Gateway: 10.0.0.1Connection: GPRSAPN: wap.telia.seMMS: http//mms1.telia.seEtc.

Text SMS 1Text: Welcome to Telia Network.

Profile 11…n configurations：1…n Text SMS’s：1 Phone Type1 Group

1 1

nn

n

n

Email settingTitleIn serverOut serverPOP/IMAP

Text SMS

4.2 Adding and Editing WAP Settings

Figure 1-6 WAP Settings

The access parameters of bearer network are configured on this page. These

parameters are used in the configuration of other services.

4.3 Adding and Editing Email Settings

Figure 1-7 Email Settings

.

.

Page 9 of 26

The E-mail parameters are configured on this page, such as name, recipient server,

sender server, and protocol.

4.4 Adding and Editing Text SMS

Figure 1-8 SMS Settings

The text SMS can be added and edited on this page.

4.5 Sending Profile

After an administrator creates a profile, CSR administrators can select this profile. Then, they can choose to send all configurations or a part of the configuration on this page.

.

.

Page 10 of 26

Figure 1-9 Sending Profile

4.6 Sending MMS Settings

MMS profiles are similar to WAP profiles. However, in the MMS profiles, there is an MMS field. The settings of MMS are the same as that of WAP, because the transmission media of MMS is the same as that of WAP (GPRS/CSD/GSM Data). The MMS can be configured depending on the requirements of carriers.

For the sending of MMS profiles, refer to 4.5 .

4.7 Sending Email Settings

The Email configuration parameters can be sent to the mobile phone through a profile. Otherwise, they can be sent as an independent short message. Currently, this function is supported by some mobile phone models of Nokia and Ericsson.

The following information can be sent:

Destination MSISDN: recipient MSISDN User ID: ID of POP3/IMAP user Password: POP3/IMAP password Email address Incoming server: POP3/IMAP server Outgoing server: SMTP server Email protocol: POP3/IMAP

The previous information is stored in the mobile phone and bound with the WAP/ISP account.

.

.

Page 11 of 26

Figure 1-10 Sending Email Settings

4.8 Sending Bookmark Settings

A bookmark provided to subscribers includes:

Destination MSISDN: sender MSISDN Bookmark URL: http://www.test.com Destination model: mobile phone model of Nokia or Ericsson Bookmark name

Figure 1-11 Sending Bookmark Settings

4.9 Sending Text SMS

The MC can send text SMS to any users.

.

.

Page 12 of 26

1) Before an OTAC is sent, the MC prompts the user that the recipient will receive an OTAC message containing the configuration parameters.

2) After the OTAC is sent, the MC prompts the user that the recipient has received the configuration parameters and can use the data services.

4.10 Configuring Videotelephony and Video Stream

The OTA system also supports the configuration of videotelephony and video stream.

4.11 Bulk Provisioning

To facilitate the configuration of multiple mobile phones, the OTA system provides the bulk configuration function. Users need to input the phone numbers separated by commas, phone models, and profiles only.

The OTA system utilizes a Job Manager to realize this function, and the Job manager has the following functions:

Job Creation Job Scheduling and Execution Monitoring Job Execution

Job Creation - The Job Manager receives requests for the management, provisioning or updating of devices via the GUI or web services, and creates device management “jobs”.

Job Scheduling and Execution – The Job Manager maintains the queue and scheduling of jobs to be executed. It also manages the execution of jobs. For CP provisioning jobs, for example, it sends a request to the CP message factory to get the proper CP messages, and forwards them to the SMS gateway. As jobs are created and executed, the Job Manager also creates the database records to keep track of changes in the devices.

Monitoring Job Execution – The Job Manager provides information via the GUI and web services to allow real-time monitoring of job execution and status, especially useful for monitoring the progress and status of bulk provisioning and updates among large populations of devices. The Job manager also manages the cancelling of these jobs at the operator’s request.

4.12 Web Help

Uses can visit Web help pages through application program. Only the administrators and customer service agents can visit the Web help page.

4.13 Open API

The OTA system provides a lot of Web Services/XmlRpc interfaces for the further development of customer service portal and mobile phone auto detection. Open API is provided for integrating with other system.

.

.

Page 13 of 26

4.14 Trigger Modes

I. Triggered Through Switch-on Auto Detection

Figure 1-12 ADD Trigger

Step1:

The subscriber switches on the MS and attaches to the network.

Step 2:

The MSC/SGSN sends an Enhanced_Check_imei message to the ADD, which contains the triplet {IMSI, MSISDN, and IMEI} information.

Step 3:

The Enhanced_Check_imei message comes to the ADD, and the ADD delivers it to the OTA system via a TCP/IP connection.

Step 4:

The OTA system gets the forwarded request, and parses it. If the triplet is a new one or the mapping between IMSI, IMEI, and MSISDN is changed, the OTA system will send the configuration message over SMS to the subscriber via SMSC.

Step 5:

The configuration message comes to SMSC of operator, and the SMSC delivers the configuration message to the subscriber.

Step 6:

The MS receives the configuration message, and finishes OTA configuration.

.

.

Page 14 of 26

II. Triggered Through SMS Short Code

Figure 1-13 SMS Trigger

Step1:

The subscriber sends the specific format configuration request over SMS to service number (stands for OTA service), asks for service settings.

Step 2:

The request comes to SMSC of operator, and SMSC delivers the request to the OTA system.

Step 3:

The OTA system gets the forwarded request, and parses it, and then sends the configuration message over SMS to the subscriber via SMSC.

Step 4:

The configuration message comes to SMSC of operator.

Step 5:

The SMSC delivers the configuration message to the subscriber.

Step 6:

The MS receives the configuration message, and finishes OTA configuration.

.

.

Page 15 of 26

III. Triggered Through WEB Portal

Figure 1-14 WEB Trigger

Step1:

Customer Care inputs the subscriber’s phone number, and chooses subscriber’s mobile phone model and required data service type, and then submits the configuration request.

Step2:

The OTA system handles the configuration request, and parses it, and then sends the configuration message over SMS to the subscriber via SMSC.

Step 3:

The SMSC delivers the configuration message to the subscriber.

Step 4:

The MS receives the configuration message, and finishes OTA configuration.

IV. Triggered Through SIM Card

Step1:

Subscriber switches on the handset and SIM Card will send the SMS to SMSC automatically.

Step2:

SMSC forwards the SMS to OTA system

Step3:

OTA system gets the SMS and generates the settings

Step4:

OTA system sends the settings to SMSC

Step5:

.

.

Page 16 of 26

SMSC forwards the settings to subscriber

Step6:

The subscriber gets the settings and save the settings

V. Triggered Through IVR

Step1:

Subscriber calls the IVR and operates as the IVR instruction.

Step2:

IVR calls the OTA API and sends the command to OTA system

Step3:

OTA system gets the command and generates the settings

Step4:

OTA system sends the settings to SMSC

Step5:

SMSC forwards the settings to subscriber

Step6:

The subscriber gets the settings and save the settings

.

.

Page 17 of 26

Chapter 5 System Running Statistics and Reports

The DMS server records the system running statistics in table. The statistics are

stored in the database of the DMS server. Each OTA configuration short message

sent from the DMS server to the SMSC contains:

Sending time

Destination MSISDN

Source address: the number displayed in the From: field

The name of SMSC channel through which the DMS server sends SMS, for

example, SMSC1

Message ID: ID of an internal message

Message type: the type of an internal DMS message

Short message content: the text or binary code of a short message sent to

the SMSC.

The following statistics can be generated.

Sending time Destination number Phone model Message type

2003-02-28 13:58:10 +491729708883 SS45 otac

2003-02-28 15:49:15 +491726036681 N7650 otac

2003-03-03 19:00:43 +491773237022 N3330 otac

2003-03-04 11:20:53 +491738770705 N7650 otac

2003-03-04 14:06:26 +491733002891 SME45 otac

2003-03-04 14:29:43 +491738770705 N7650 otac

2003-03-04 14:30:57 +491738770705 N7650 otac

2003-03-04 14:33:15 +491738770705 N6310 otac

2003-03-04 14:37:36 +491738770705 ET68 otac

2003-03-04 16:19:10 +491726405140 N6310 otac

Figure 1-15 Statistics table

The following information can be extracted from the previous statistics:

Message number and types of a mobile phone

Message number and types of each SMSC

.

.

Page 18 of 26

Message number and type in a service of a mobile phone

MSISDN query

Message number and types in a specified period

The DMS system provides a report platform (optional, must purchase separately), the administrator can create and view the reports, the below is the primary reports template:

Successful Jobs per Type of Job

Successful Jobs per Type of Job for a given Carrier

Successful Jobs per Type of Job for a given Manufacturer

Number of OTA Messages Report

Number of OTA Messages each Phone Model Report

Number of Fail/Successful OTA Messages Report

Number of OTA Messages each Service Report

Number of Users each Phone Model

.

.

Page 19 of 26

Chapter 6 Mobile Phone Support

6.1 Online Upgrade of Mobile Phones

Without interrupting the system running or changing programs, the system can upgrade mobile phones online. Then the system can be supported by the latest phone models.

Upgrading mobile phones:

Figure 1-16 Online Upgrade of Mobile Phones

In addition, the system can roll back the upgrade. In this way, the system state before upgrade can be restored.

6.2 Supported Mobile Phones

To meet the marketing requirements, carriers need to add new phone models to the model list.

.

.

Page 20 of 26

Chapter 7 Networking and External Interfaces

7.1 Networking

Figure 1-17 Network Graphic

7.2 External Interfaces

The OTA system provides external interfaces with:

SMSC ADD BOSS Customer service/administrator

The following describes the functions and definitions of the external interfaces.

.

.

Page 21 of 26

7.2.1 Interface with ADD (IF1)

I. Interface Functions

ADD is the access server of the OTA. It collects the information on mobile phone switch-on from the core network and extracts {IMEI, MSISDN, and IMSI}. Then it sends the information to the ADCS.

II. Protocol

TCP/IP

7.2.2 Interface with BOSS (IF3)

I. Interface Functions

The OTA system support the FTP interface with Billing system, the OTA system can generate the fixed format CDR, by FTP interface OTA system can transfer the CDR to Billing system.

II. Protocol

FTP

7.2.3 Interface with Customer Service Center/Administrator (IF4)

I. Interface Functions

The customer service agents and administrators can manage, maintain, and trigger the service through this interface.

II. Protocol

HTTP

7.2.4 PUSH Interface with SMSC (IF5)

I. Interface Functions

The SMSC can push the OTA configuration parameters of mobile phones through this interface. After the DMS server is interconnected with the SMSC, the SMSC can send PUSH messages to subscribers, thus implementing the parameter configuration on mobile phones.

II. Protocol

SMPP3.3/SMPP3.4/CIMD/UCP

7.2.5 Interface with SMSC (IF6)

I. Interface Functions

The SMSC forwards short messages through this interface. After the MC is interconnected with the SMSC, the SMSC sends the SMS short code to the MC, thus resolving the service parameter configuration request from the mobile phone.

II. Protocol

SMPP3.3/SMPP3.4    

.

.

Page 22 of 26

Abbreviations

OTA Over-The-Air

GPRS General Packet Radio Service

GSM Global System for Mobile communications

GUI Graphic User Interface

HTTP Hyper Text Transport Protocol (RFC2616)

SMS Short Messaging Service

MMS Multimedia Messaging Service

SyncML Synchronized Machine Language

SyncML DM SyncML Device Management

WAP Wireless Application Protocol

HSCSD High Speed Circuit Switched Data

DMS Device Management Server

UCP Universal Computer Protocol

SMPP Short Message Peer to Peer

CSA Customer Service Agent

PAP Password Authentication Protocol

ODBC Open Database Connectivity

IMEI International Mobile Station Equipment Identity

ADCS Advanced Device Capability System

ADD Automatically Device Detect

.

.

Page 23 of 26