White Paper DMC en

a mcTEL whitepaper
The OTA & Mobile Device Management Whitepaper

Reference: LB-012-1.1-2006
SMS PUSH PULL PREMIUM MMS WAP VOCAL OTA SMSC FIXED SMSC SMS GATEWAY
Version: 1.2 Date: April 5, 2006
MCTEL (MONACO TELEMATIQUE)

41, Av. Hector Otto, P.O. 225, MC 98004 MONACO Cedex Tel: (+377) 9216 8888 Fax: (+377) 9216 8865 Web: http://www.mctel.net
MONACO TELEMATIQUE MCTEL

41, avenue Hector Otto, PO BOX 225 MC 98004 MONACO Cedex Tel: (+377) 9216 8888 Fax: (+377) 9216 8865 Sales support: sales@mctel.net Web: http://www.mctel.net
MCTEL Livre blanc "Device Management Center OTA"
v1.1
Diffusion restreinte
page i
MCTEL OTA Device Management White Paper
v1.1
Table of Contents
1 Introduction ....................................................................................................................4 1.1 General introduction .................................................................................................4 1.2 About the Authors.....................................................................................................4 Why a Device Management Center ? ...........................................................................6 2.1 Introduction...............................................................................................................6 2.2 Marketing Analysis (data-mining) .............................................................................7 2.3 Selective user information (selective broadcast)......................................................8 2.4 Over the Air terminal configuration (OTA) ................................................................9 2.5 Automatic Device Detection & Configuration (Automatic Device Configuration)....10 2.6 SIM OTA Configuration & Download......................................................................11 2.7 Error detection and correction ................................................................................12 2.8 Managing stolen and prohibited devices (Equipment Identity Register) ................12 2.9 Welcome to roamers ..............................................................................................13 2.10 Value Added Service Provider Interface for terminal type and capabilities informations........................................................................................................................13 2.11 Firmware update ....................................................................................................14 2.12 Enterprises Device Management ...........................................................................14 2.13 Upgrade of network equipment ..............................................................................15 Setting up a Device Management Center in practice................................................16 3.1 Introduction.............................................................................................................16 3.2 The barriers to DMC effectiveness.........................................................................16 3.2.1 OTA SMS Provisioning command throughput................................................17 3.2.2 Automatic IMEI Retrieval for device detection................................................17 3.2.3 Automatic Device Detection and Configuration ..............................................18 3.2.4 IMSI Automatic Retrieval ................................................................................18 3.2.5 Quality and updating of the mobile database .................................................18 3.2.6 OTA protocols support ...................................................................................19 3.3 Connecting in practice a DMC in the operator network..........................................19 3.3.1 Connecting to the SMS-Center for SMS Sending ..........................................19 3.3.2 SS7 connectivity .............................................................................................21 3.3.3 Equipment Identity Register network integration ............................................22 3.3.4 Welcome To Roamer support ........................................................................23 3.3.5 Automatic Device Detection and Configuration ..............................................23 3.3.6 Back office integration with OMC ...................................................................23 3.3.7 Help Desk Web integration.............................................................................24 3.3.8 Operator Web portal integration .....................................................................24 3.3.9 Open interfaces ..............................................................................................24 APPENDIX A: MCTEL Mobile Solutions.....................................................................26 Appendix B Handset database ................................................................................27
4 5
Confidentiel page ii
v1.1
Figures
Figure 1 MCTEL Mobile Solutions ........................................................................................5 Figure 2: Functional schematics of MCTEL Device Management Center ...............................7 Figure 3: Standard features offered by a Device Management Center without SS7 interworking: Device Configuration (without real time IMEI retrieval and automatic device detection). The OTA provisioning in done through the operator's SMS-Center with a low throughput..............................................................................................................................21 Figure 4: Features offered by a Device Management Center supporting direct SS7 connection: Automatic Device Detection and Configuration, Equipment Identity Register features, embedded very high throughput SMS-Center for efficient OTA provisioning .........22
Tables
Tableau 1: OTA capabilities according handset brands (there is only a summary table, according to precise handset models some differences may exist).......................................10 Tableau 2: Examples of SIM parameters that could be read or modified ..............................11 Tableau 3: Available features according to the SS7 support by the DMC .............................16 Tableau 4: Data to import for populating and updating the DMC subscriber database .........24
Confidentiel page iii
v1.1
1 Introduction
1.1 General introduction

Installing a Device Management Center on the operator networks allows to: provide Help Desk with the needed tools to answer efficiently subscribers requests. supply the Marketing department with a complete view of the devices used on the network with the characteristics and features, to better promote existing services and plan future ones. automaticallly configure Over-The-Air a single handset or the whole customer base. manage SIM cards offer new highly attractive services such directory backup/restore or Firmware update. prohibit stolen devices to access the network. This Whitepaper presents the general features of a Device Management Center, and how it could be installed in practice in the operator network.
1.2 About the Authors

It has been written by MCTEL Device Management Center staff experts, MCTEL has developed an Advanced Device Management Center integrating a SS7 interface in order to offer more advanced features, such: very high speed OTA handset configuration thanks to an integrated high speed SMS Center. Automatic Device Detection and Configuration as soon a new mobile handset is turned on. Interworking with Value Added Service Providers to transmit them the needed information on device type and capabilities. Equipment Identity Register (IER) feature allowing to prohibit network access to stolen devices. optional Welcome to Roamers feature.
(c) MCTEL
-4Disclosure or reproduction prohibited without MCTEL prior written approval
March 2006
41, avenue Hector Otto BP 225 98004 MONACO Cedex Tl: +377 9216 8888 Fax: +377 9216 8865 email: sales@mctel.net - Web: www.mctel.net
v1.1
Figure 1 MCTEL Mobile Solutions
(c) MCTEL
March 2006
v1.1
2 Why a Device Management Center ?
2.1 Introduction
Each month, new handsets are added to the thousands of different handset models used on mobile networks. Mobile network subscribers purchase, sell, exchange their handsets: very often the device is not correctly configured to access multimedia services. Multimedia and data services are growing at a fast rate and generate much higher ARPU than voice calls. However to realize this revenue growth, those new services and applications must work easily and reliably. Customers must be able to access and use them with little or no hassle. As mobile devices are becoming increasingly complex, supporting more diverse services, but often with incompatible protocols and formats, the operator must be able to manage and configure easily subscriber devices. This explains why, on a global scale, more than 30% of handsets are not correctly configured to access those highly remunerative services. On some networks this percentage may be much higher and sometimes on some networks up to 90% of the handsets are not properly configured. The mobile operators need to have a global view of their mobile subscribers handset database and to be able to provision those handsets, in order to: be able to planify and market new services according the current handset base (data-mining), thanks to a clear view of the currently installed handset base. inform selectively their subscribers of the availability of new services or promotional offers according to their handset brand and model (selective broadcast). configure over-the-air the devices, either individually, or by group, or for their whole subscriber base, e.g. to allow introduction of new services (MMS, Wap, SyncML, email) (OTA configuration). provide the tools to their help desk to efficiently assist their subscribers encountering problems accessing to new services. instantaneously detect stolen devices and abusive usage (GSM gateways) and block network access to those devices thanks to the Equipment Identity Register feature. take over application and terminal control, thanks to SIM OTA configuration and application downloading using either SIM download or SyncML. allow progressive network upgrade and adding new load balancing servers (such SMSC, MMSC) in order to get better prices from manufacturers. offer advanced new services such directory and application backup & restore or specific configuration of a company fleet. A Device Management Center integrates one or several modules allowing to offer new advanced services: Marketing Analysis (data-mining) Selective Broadcast Over the Air (OTA) configuration of handsets and SIM cards (OTA) (c) MCTEL -6Disclosure or reproduction prohibited without MCTEL prior written approval 41, avenue Hector Otto BP 225 98004 MONACO Cedex Tl: +377 9216 8888 Fax: +377 9216 8865 email: sales@mctel.net - Web: www.mctel.net
March 2006
MCTEL OTA Device Management White Paper Management of stolen and prohibited devices (Equipment Identity Register). Welcome to Roamers module Automatic Device Detection with Wireless Service Provider interface module. Firmware Update (FOTA Firmware Over The Air) Very high performance integrated SMS-Center (SMSC)
v1.1
Figure 2: Functional schematics of MCTEL Device Management Center
2.2 Marketing Analysis (data-mining)

To efficiently plan and promote new services, the Marketing department must have a clear view of the current handset base. Amongst the questions always in the mind of the marketing staff: How quickly check if a planned new service could be accessed easily by existing subscriber handsets? What are the handsets currently in use on my network? What have the changes been in the last 6 months? Is it time to introduce Edge or 3G value added services on my network such MMS Value Added Services, Video Mail, Streaming?
(c) MCTEL
March 2006
v1.1
Thanks to its Data-Mining module, the Device Management Center may perform a global instantaneous analysis (snapshot) of the current handset base. This analysis will return: the market share of all brands and various models of a selected brand. the compatibility of the handset base with the new services planned by the operator: o Wap and MMS support. o colour screen. o video and streaming video support. o integrated camera. o Java support and version the percentage of mobiles supplied by the operator (promotional offers) and also some idea on the percentage of mobile supplied by the competitve operator but used on the operator network (churn-in)1. comparison with previous snapshots will give a precise view of the market trends. The Device Management Center database includes most devices worldwide (ideally all devices) with all their characteristics, so it is possible to perform a specific marketing analysis on any of the desired characteristics (refer to Appendix for an example of device characteristics).
2.3 Selective user information (selective broadcast)

How to inform subscribers about the availability of a new service without boring or irritating them? How to explain them how to use it or recommend them if needed a promotional updated offer suited to them? During the launch of a new service only available to some handsets and therefore subscribers, the precise knownledge of the current subscriber handsets will allow to selectively target subscribers with relevant marketing information. The information being precisely suited to the customer handset will provide a real service to the subscriber and will not be perceived as spam or agressive marketing. For example, a network operator starting MMS service on its network could: compatible terminals: after automated OTA device provisioning, inform the subscriber of the availability of the new service thanks to a MMS: "Congratulation, your Nokia 7510i is now able to exchange MMS!". older terminals: inform their owners of the availability of a promotional upgrade: "Hello, your Nokia 3100 does not allow you to access MMS but a special upgrade offer is waiting for you this month!". If the DMC integrates its own SS7 links and integrated SMS Center, those SMS (as well OTA SMS) may be pushed at very high speed on the network, and it is therefore possible to inform millions of subscribers in a very short time (for example, the MCTEL DMC supports 500 to 2000 SMS/second)2 (refer to 1.1.9). A SMPP interface to the operator SMS Center could also be used, but those interfaces usually support low speed (5 SMS/second on average)
To this end, the operator must fill in a marketing database with the handsets brand and models distributed during promotional offers, including if possible their IMEI list. 2 The SS7 configuration of the hardware platform and the SS7 connectivity to the operator backbone must include a sufficient number of SS7 links to fully use this throughput.
1
(c) MCTEL
March 2006
v1.1
Selected data may also be exported at CSV format, allowing them to import them in external databases, for example to send personalised mails to the subscribers according to their device characteristics.
2.4 Over the Air terminal configuration (OTA)

I am installing new equipments (a new or additionnal MMS Center) or new services (Wap, Video, Push To Talk) on my network. How will I make them accessible right now from my subscriber base? How to allow my Help Desk to efficiently provide the needed assistance to my subscribers who have problems to access and use new services?
A Device Management may detect and recognize the precise handset model of a subscriber, but also automatically configure it Over the Air using commands sent or at least triggered by SMS. The parameters that could be provisioned depend on the phone brand and model, it is for example possible to configure: SMS-Center access number MMS-Center address GPRS or CSD Internet Access Point data. Wap and Web browsers, including Wap bookmarks. E-mail parameters. advanced multimedia services, such Push-To-Talk, Wireless Village, Device Synchronisation, etc. data or application stored on the SIM, e.g. des donnes stockes sur la SIM, for example the directory of abbreviated numbers on the SIM, the list of roaming networks on the SIM, SIM toolkit application (see below). etc. According the manufacturer and the device model, a more or less extended parameter range can be configured. The table below give a summary list of handset OTA capabilities. In practice, up to 80% to 90% of handset base may be provisioned. Even for very old devices not supporting any OTA commands, the DMC may nevertheless configure essential parameters in the SIM card (refer to 11).
(c) MCTEL
March 2006
MCTEL OTA Device Management White Paper Push To Talk Browser SyncML DS Video Streami Chat/IM Brand / capabilities OTA GPRS WAP CSD
v1.1
Email
MMS
Alcatel Benq Ericsson LG Motorola Nokia Panasonic Pantech Philips Sagem Samsung Sanyo Sendo Siemens Sharp SonyEricsson Smartphones
Tableau 1: OTA capabilities according handset brands (there is only a summary table, according to precise handset models some differences may exist)
The provisioning may be performed: fully automatically when a subscriber has inserted his/her SIM card in a new device, thanks to the Automatic Device Detection and Configuration described below. With this very advanced feature, a new device is configured in a fully automatic way as soon it is used. automatically on operator request for a part or the whole customer base. For example, when introducing a new MMS-Center, the operator will only configure MMS compatible terminals with the required parameters. by the customer care staff, thanks to the Web DMC Help Desk management interface. on subscriber request, from the operator Web access to the DMC user configuration Web tool. The customer may also send a configuration request by SMS. in case of incident automatically detected (see below)
2.5 Automatic Device Detection & Configuration (Automatic Device Configuration)

Thanks to its complete integration with the operator network, advanced DMC as MCTEL's may automatically detect, recognize and configure a new device as soon it is turned on on the mobile network.
(c) MCTEL
- 10 Disclosure or reproduction prohibited without MCTEL prior written approval
March 2006
OMA DM
v1.1
As soon a customer will insert his/her SIM in a new device and turn it on, the DMC will automatically detect it and provision it automatically so it could immediately use all network multimedia features. The network integration could be performed using two methods: a simple way is to install in the SIM card a specific application (SIM Toolkit, Smartrust WIB, Java applet) that will record in the SIM the current device IMEI and will send an alert to the DMC when the device model is changed. This method presents numerous drawbacks: o it requests the SIM cards to integrate either SIM toolkit, Java or a browser and such cards are more expensive. o it could not apply to the SIM cards currently used in the network (no backward capability). o the application will alert the DMC using SMS or better USSD requests that will cause unnecessary load on the network elements (such the SMSC). In some cases, the SMS may even be wrongly charged to the user. the most advanced way is to use a SS7 direct interconnect allowing the automatic device detection.
2.6 SIM OTA Configuration & Download

Vital informations are stored and managed by the SIM card. The Device Management Center may exchange commands and requests with the SIM card in order to: read SIM directory and files, allowing for example to perform backup/restore operations on the customer directory. update SIM data, such the roaming allowed or prohibited network, the SMSC number, and so on. download or update applications to the SIM. Parameters Language Preference Usage Allows to specify the user preferred language the handset will use. Allowed services Specify the services allowed to the subscriber: SMS, GPRS, MMS, abbreviated numbers, cell broadcast, and so on. Cell Broadcast For example activated Cell Broadcast channels Parameters SMS Center Parameters SMS Center access number Depersonalisation Used to unlock devices restricted to only one operator after the parameters required subscription period Preferred networks List of the preferred networks Prohibited networks List of the prohibited roaming networks Allowed or prohibited May restrict the subscriber to some numbers numbers lists Directory May be used to offer backup/restore service
Tableau 2: Examples of SIM parameters that could be read or modified
(c) MCTEL
March 2006
v1.1
Thanks to a SIM application, the downloading of large quantity of data may be triggered by a first SMS and them performed over IP (GPRS/UMTS) to increase the transfer speed (very useful to download large SIM application or backup/restore applications).
2.7 Error detection and correction

In most cases, a subscriber failing to access a new service (MMS, Wap) for the first time will not take the time to report the problem to the help desk. How to detect and correct those kind of problems when only 3 to 5% of subscribers report non-blocking problems to the Help Desk and when at least 30% of subscribers are unable to access multimedia services because their terminal is misconfigured? The first answer is of course to setup the Automatic Device Detection and Configuration that will automatically detect that a new device as soon as it is turned on to configure it accordingly. Another method is to use network probes, so that the DMC may detect problems caused by the terminal misconfiguration, e.g. unability to access a SMS-Center or MMS-Center. After checking the handset model, the DMC may then automatically send the appropriate OTA Provisioning command and associated explanation to ensure that the next try will process smoothly. The Automatic Device Detection and Configuration has the advantage to prevent the problem before it happens.
2.8 Managing stolen and prohibited devices (Equipment Identity Register)

How to comply with regulatory requirements and prohibit the use of stolen devices on my network? How to avoid having my network accessed by shared GSM Gateway granting free or low cost access to my network (and other networks) to numerous users using a single promotional subscription?
The use of stolen devices on mobile networks is a real cause of concern for operators, because: the subscribers are angered if their operator is not able to block the usage of their stolen device on its network. the regulatory organisms, in numerous countries, are requesting the mobile network operators to install in a short timeframe the necessary tools to detect and prohibit the use of stolen devices. the use of devices prohibited by the contracts such shared GSM Gateway accessing a single mobile subscription on behalf of numerous users cause direct loss of profit. Thanks to its EIR (Equipment Identity Register) the MCTEL Device Management Center solves those problems. It will directly connect to the SS7 network and will be accessed by the MSC/VLR before a subscriber is allowed to access the network3.
The operator must configure its MSC/VLR to have them send the MAP Check_IMEI request to the EIR during subscriber registration, this request is performed before HLR registration. If the
3
(c) MCTEL
March 2006
v1.1
The DMC/EIR will check its IMEI and subscriber database and will return the appropriate answer: IMEI or TAC in blacklist: this device could not access the network. IMEI or TAC in greylist: access is allowed, but the network usage will be tracked. IMEI in whitelist: access allowed (default). Those lists (black, grey, white) may include either full IMEI (therefore a unique mobile device) or only the TAC (Terminal Approval Code) specific to the handset brand and model. This allows to prohibit the access to all devices of this model (e.g. a GSM Gateway). The DMC/EIR may interconnect with the Central Equipment Identity Register of the GSM Association, located in Dublin, in order to share the blacklist of stolen devices with all EIR in service worldwide.
2.9 Welcome to roamers

The Welcome to Roamers module will complete EIR module by detecting automatically foreign subscribers roaming on the local network (roamers-in). It will then send them a welcome message that may inform those foreign subscribers of the specific services offered to them on the operator network (local help desk) in their own language. Such Welcome to Roamers will increase the roamer comfort and will help generate new income. Thanks to its EIR integration and direct access by MSC/VLR, this module does not require to install costly probes on the network.
2.10 Value Added Service Provider Interface for terminal type and capabilities informations
On numerous occasions, the Value Added Service Provider relies heavily on the subscriber device model knownledge to deliver the appropriate content to the device. The multiplicity of incompatible devices and supported media formats may cause a denial of service in more than 30% of the cases when this information is not known. Unfortunately, most operator VASP connection platforms are not able to transmit this information to the VASP. Asking the user (e.g. by SMS exchange) its device brand and model is a complicated procedure and most subscribers may know their device brand but not their device model (and there is wide discrepancies in format support between various models of a same brand). As a result, a denial of service may occur in more than 30% of the cases of multimedia content personalization downloading, because: o the multimedia content has been delivered in a format not compatible and will be ignored or not played by the handset.
Check_IMEI can transmit the IMSI optional parameter, the DMC/EIR may offer the Welcome To Roamers and Automatic Device Detection features.
(c) MCTEL
March 2006
MCTEL OTA Device Management White Paper o
v1.1
the VASP tried to deliver the content using a Wap Push not supported by the handset (numerous recent and advanced PDA-like handsets for example require a URL Web link instead of a Wap Push).
This denial of service is very badly accepted by the users, whom are very often billed for a content they could not use. This causes customer insatisfaction, help desk costs to manage users complaints and refund requests and huge loss of revenue from Premium service because the users stop using them. Thanks to its Automatic Device Detection feature, MCTEL Device Management Center may interwork with the Premium Gateway managing the VASP connection to the network in order to transmit to the VASP the needed information about the device. The VASP will be then able to supply the content in a format suitable to the customer handset. Associated with MCTEL Premium Gateway, MCTEL Device Management Center may deliver the useful information to the VASP in several forms: o TAC (Terminal Approval Code): this 8 digits (previously 6) will identify in a unique way the subscriber handset. However, the TAC databases associating a TAC number with the handset type are privileged information and most VASP are not able to translate the TAC to the actual device. o Handset brand and model in text format (e.g. "Nokia 8860"). Although most VASP are much easier to work with, they are not precisely aware of the device supported format and recommended push mechanism. o Terminal capabilities, according VASP profile: in this model, the Premium Gateway will send to the VASP (along with the request SMS-MO) or the VASP could query the Premium Gateway for terminal capabilities, e.g. ringtones supported media format.
2.11 Firmware update

The Firmware Over The Air (FOTA) feature of a Device Management Center provides a cost effective channel to ensure that subscriber's devices work smoothly. Without having to return or exchange the device, the subscriber may immediately download the latest firmware, either offering enhanced features or correcting a bug. FOTA will help the operator to introduce new services that need latest firmware releases and to reduce overall customer support costs. MCTEL Device Management Center integrates a FOTA module that will perform remote diagnosis and manage the firmware download for FOTA-compliant devices (the operator must negociate with the handset manufacturers the right to use/download the latest firmware releases).
2.12 Enterprises Device Management

Corporate subscriptions are much more lucrative than private users subscription, with higher mean invoice, higher ARPU, less unpaid invoices, increased use of data and multimedia services.
(c) MCTEL
March 2006
v1.1
To offer a better service to its corporate subscribers, the operator may propose to entreprises specific device management and configuration tools to perform customized provisioning of the entreprise handsets: email parameters provisioning. device synchronisation provisioning, allowing the synchronisation of the handset data with the enterprise data management center and the replication of the data. by providing enteprises with their own device management interfaces, a DMC can substantially reduce the operator's involvement in customising services to specific enterprises' needs.
2.13 Upgrade of network equipment

This feature allows the operator to more easily upgrade its network by installing new system in load balancing or specifically assigned to some customers. For example: an operator with an older and overloaded MMS-Center not offering some features (such on-the-fly video content rendering) may instead of replacing the MMS-Center by a costly new system, simply add another MMS-Center offering those video features. Only the handsets supporting video and needing those features will be configured with the new MMS Center parameters.
(c) MCTEL
March 2006
v1.1
3 Setting up a Device Management Center in practice

3.1 Introduction
On the paper, most DMC offer similar features. As we will see, the network integration and mechanisms are key points to ensure the installed DMC will offer effectively the needed functions. Feature Populating initially the DMC subscriber database Associating a mobile handset model with a subscriber DMC without SS7 support File import DMC with SS7 support File import Full Real-Time thanks to Automatic Device Detection over SS7
Offline (file import) Near-real time (CDR flow) Using a SIM application by asking the customer manually (*#06#) Sending Provisioning OTA Low-speed interworking (e.g. SMS commands to SMPP) with the operator SMS, leading to numerous handsets drawbacks pointed out in 3.2.1) Sending OTA commands Same to SIM File import Subscriber IMSI retrieval Management of stolen or Impossible prohibed devices (Equipment Identity Register) Impossible Welcome to Roamers
High-speed direct transmission on the network thanks to the integrated OTA SMS Center Direct sending of commands through integrated SMSC Real-time network retrieval Support of the Check_IMEI MAP command from MSC/VLR
Support of the Check_IMEI extended MAP command with IMSI (Roamers-in) interface, with User interface for the Web interface, the IMEI must Web operator call center and be retrieved manually or the automated IMSI and IMEI terminal model must be retrieval Web checked to ensure error free provisioning Configuration de parc pour Via une interface Web de Via une interface Web de management ddie management ddie flotte entreprise
Tableau 3: Available features according to the SS7 support by the DMC
3.2 The barriers to DMC effectiveness

In order to fully use the DMC features over the network, the following barriers must be anticipated:
(c) MCTEL
March 2006
v1.1
3.2.1 OTA SMS Provisioning command throughput

What is the interest to own a sophisticated Device Management Center if it loads the network operator SMS Center during days or even weeks to update a handset base? Many configuration settings may request up to 2 or 3 SMS to be performed, a more important update or SIM OTA may require much more. Let's take the example of an operator having 1 million of handsets to configure and wanting to send provisioning commands requiring 3 SMS. If the operator own a 30 SMS/second SMS-Center and want to reserve 33% of its throughput (so 10 SMS/second), the operation will take more than one week (depending on the handset model, the OTA configuration must be performed during the day not to awake the subscribers). This problem is usually the most important one, prohibiting in practice the use of the Device Management Center to perform quickly bulk device provisioning over the network on a significant part of the subscriber base, because: a DMC without integrated SS7 support and OTA SMSC must connect and interwork with the operator SMS-Center to send its SMS OTA commands. The connection is usually done using SMPP or UCP, such protocol seldom allow to exceed a sustained throughput of 5 SMS/second per link. Even with multiple links, the throughput could not exceed a few tens SMS/second. a part of the SMS Center throughput will be used, as most operators have SMSC licences between 25 and 100 SMS/second, a too high OTA throughput may impact Person to Person SMS. The SMSC throughput extension is usually very costly to setup. To avoid this drawback, MCTEL has integrated in its SS7 DMC 300 Device Management Center a very high throughput OTA-dedicated SMS-Center with First Delivery Attempt feature (Direct Delivery) allowing to push SMS up to 2000 SMS/second. All SMS sent by the Device Management Center, either OTA Provisioning or marketing broadcast has no longer to load the operator SMS Center, and the provisioning operations could be performed in hours instead of weeks. Based on the MCTEL High Performance SMS Center and using the HP OpenCall SS7 platforms (the most used by SMS Centers worldwide), this exclusive MCTEL feature offers the operator a Device Management Center that could be used in practice even on large networks.
3.2.2 Automatic IMEI Retrieval for device detection

It is of paramount importance for the Device Management Center to be able to retrieve immediately and automatically the handset model (through the IMEI) currently used by the subscriber, for all DMC features: allowing Help Desk to assist the user. performing the OTA Provisioning of handset settings. transmitting terminal type or supported features to a Value Added Service Provider (VASP).
(c) MCTEL
March 2006
v1.1
As subscribers often use several handsets and SIM cards, the information retrieved on the CDR (either off-line or even in near real-time mode) is often outdated. Only the instantaneous IMEI retrieval allows to make sure of the current handset uped by the subscriber. There is only a few ways to get the IMEI in real time: by asking it to the subscriber, that could type *#06# on the handset keyboard. This method is unfriendly and error-prone. as explained below, a SIM application on the SIM card may send a SMS or USSD command when the SIM card is inserted in a new handset. This method is effective but must be planned in advance to generalize those SIM to all subscribers, lead to increased SIM costs, and will load the network. Thanks to an Automatic Device Detection feature, based on MAP SS7 commands over the network (minimum MAP version required v.3). This method is instantaneous, does not request any user interaction, is error-safe.
3.2.3 Automatic Device Detection and Configuration

To ensure an easy customer access to all multimedia services with no hassle, the best solution is to automatically detect a new device as soon that the user turn on its new handset and to configure it automatically, as explained at 2.5 and 3.3.5. To this end, the Device Management Center must be completely integrated in the operator network, thanks to a direct SS7 interworking (although a specific SIM application may also be used with various drawbacks).
3.2.4 IMSI Automatic Retrieval

The DMC may need the susbcriber IMSI, as it is used as network key to perform the automatic configuration of latest handsets, without needed user confirmation or user entering a configuration key (the user may even not been informed of the configuration change if the operator chooses to). This function is needed to be able to update large number of terminals in bulk mode without having numerous users calling the Help Desk to request assistance or explanations. The IMSI may be transmitted to the DMC using a file transfer, or it could be retrieved automatically by the DMC using a SS7 request to the HLR.
3.2.5 Quality and updating of the mobile database

The Device Management Centers relies on their mobile terminals database to: find out the handset brand and model from the TAC (and in some cases the UserAgent). detect the OTA protocol to use to configure the handset and the kind of parameters that could be provisioned (CSD, GPRS, MMS, Email, Streaming video, Wireless Village, and so on). (c) MCTEL - 18 Disclosure or reproduction prohibited without MCTEL prior written approval 41, avenue Hector Otto BP 225 98004 MONACO Cedex Tl: +377 9216 8888 Fax: +377 9216 8865 email: sales@mctel.net - Web: www.mctel.net
March 2006
v1.1
retrieves detailed terminal characteristics for the marketing analysis (data-mining).
It is therefore of paramount importance for the mobile database to be: cognizant of all (or nearly) all handsets worldwide very regularly updated as new devices are always released on the market. storing very detailed characteristics for each terminal, including of course the OTA support and protocol and the device general characteristics. accurate. To check the quality of the database, the following questions must be asked: number of handsets defined in the database detailed listing of the terminal specifications data stored for each handset. DMC configuration capabilities updating frequency manufacturer commitment for database update, manual Web configuration data supply for manual configuration (e.g. for terminals without OTA capabilities), take in account "operator-branded" devices. Thanks to its activity in the Mobile Content delivery, MCTEL is maintaining since several years a very extensive detailed mobile terminals database, including more than 2,000 terminals.
3.2.6 OTA protocols support

It must be checked the DMC supports all provisioning protocols used by various devices and the manufacturer commitment to implement new protocols: Nokia Smart Messaging 3.0 Nokia OTA protocol (version 4.5 to 7.1) OpenWave Primary Provisioning Wap Forum Client Bootstrap OMA Provisioning Bootstrap, Provisioning Content, SyncML Device Management, Data Synchronization, FOTA, Provisioning Smarcard optional SIM OTA Support depending on the needs
3.3 Connecting in practice a DMC in the operator network

3.3.1 Connecting to the SMS-Center for SMS Sending
Most DMC do not have embedded SMSC capabilities and will need to rely on the operator SMS-Center for sending the OTA SMS Provisioning commands. The DMC connection to the DMC will be necessary for: sending the OTA SMS Provisioning commands if the DMC does not integrate an OTA SMSC. receive SIM cards replies to SIM OTA commands (handsets do not reply over SMS to the provisioning settings, the SIM card may reply depending on the command options). (c) MCTEL - 19 Disclosure or reproduction prohibited without MCTEL prior written approval 41, avenue Hector Otto BP 225 98004 MONACO Cedex Tl: +377 9216 8888 Fax: +377 9216 8865 email: sales@mctel.net - Web: www.mctel.net
March 2006
v1.1
The interworking with the SMS Center is usually performed over TCP/IP by SMPP or UCP for low-end DMC and may be performed over SS7 by advanced DMC. Over TCP/IP, the interworking uses the following characteristics: security: the DMC and SMSC usually share the same TCP/IP operator internal network. If this is not the case (e.g. DMC used in ASP mode), it is recommended to setup a VPN between both networks. shortcode configuration: for SIM OTA configuration only, usually shortcodes or specific MSISDN are allocated to the DMC to allow replies to be sent back to the DMC. Usually 2 or 3 shortcodes are created on the SMSC and routed to the DMC link, with the following characteristics: o DMC is allowed to proceed to OADC replacement (sending number specification). o The UCP or SMPP throughput class and windowing must be as high as possible. o To increase the throughput, one SMPP link must be used per shortid or even several if multiple bind are supported. It is difficult for a single SMPP link to manage more than 5 SMS/second in sustained operation. Billing and statistics: as this traffic concerns only the operator internal use, this traffic is usually not billed and statistics are only generated to check the SMSC statistics matches the DMC statistics. Usually DMC integrates their own statistical tools. When the interworking with the SMSC is performed over SS7, the SMSC may forward the SMS-MO from SIM cards to the DMC at a much higher throughput than those available using SMPP. When the DMC integrates its own OTA SMS-Center and is directly connected to the operator SS7 backbone, the operator SMS-Center is no longer used for OTA SMS-MT Provisioning commands and those commands may be transmitted at a much higher throughput. For example, the MCTEL Device Management Center integrates an Advanced SMS Center with Direct Delivery Attempt and may allow to achieve throughputs up to 2,000 SMS/second on the network.
(c) MCTEL
March 2006
v1.1
Figure 3: Standard features offered by a Device Management Center without SS7 interworking: Device Configuration (without real time IMEI retrieval and automatic device detection). The OTA provisioning in done through the operator's SMS-Center with a low throughput
3.3.2 SS7 connectivity

When the DMC integrates SS7 support (hardware and software), it could be connected to the SS7 operator network, the following operations must be performed: affecting a PC (Point Code) and GT (Global Title) to the DMC physical connection of the DMC to the SS7 network, usually over 2 MBps E1 with the desired number of links. A small number of SS7 links is usually enough for IMSI and IMEI retrieval, an higher number will be needed if the DMC is also configured as EIR (Equipment Identity Register) with Automatic Device Detection and Configuration or if a High Speed OTA SMS Center feature is to be used as in MCTEL DMC 300. In this case, we recommend to install at least 30 SS7 links or one SS7 E1 ClearChannel (unchannelized E1) per 500 SMS/second throughut step. The HP OpenCall SS7 interfaces may support up to 7,000 TPS per system (Front End Processor). configuring and authorizing the DMC in the network elements (HLR, MSC, and so on) to perform the required requests for the interworking (IMSI and IMEI retrieval, Check_IMEI, Push SMS-MT).
(c) MCTEL
March 2006
v1.1
Figure 4: Features offered by a Device Management Center supporting direct SS7 connection: Automatic Device Detection and Configuration, Equipment Identity Register features, embedded very high throughput SMS-Center for efficient OTA provisioning
3.3.3 Equipment Identity Register network integration

To allow the DMC to support the EIR (Equipment Identity Register) feature to manage stolen and prohibed devices, the operator must: connect the DMC to its SS7 backbone as described in 3.3.2. configure its MSC/VLR to make them performing the Check_IMEI MAP request to the EIR during subscriber initial registration on the network. According the IMEI, the EIR will allow or prohibit access to the network. The MSC must be configured in order to grant access by default in case of no reply from EIR (otherwise, the EIR may become a single point of failure and the hardware supplied must be fully fault tolerant). The Check_IMEI feature is usually an option sold by MSC supplier, check the option has been installed. proceed to interwork the EIR to the Central EIR of the GSM Association, located in Dublin, that stores all IMEI of devices signalled as stolen worldwide. setup the administrative procedures to record the stolen devices IMEI in the EIR, after collecting data from subscribers and law enforcement authorities. It is possible to prohibit the access to the network to unauthorized devices such GSM Gateways by entering simply their TAC in the EIR blacklist database. (c) MCTEL - 22 Disclosure or reproduction prohibited without MCTEL prior written approval 41, avenue Hector Otto BP 225 98004 MONACO Cedex Tl: +377 9216 8888 Fax: +377 9216 8865 email: sales@mctel.net - Web: www.mctel.net
March 2006
v1.1
3.3.4 Welcome To Roamer support

Some DMC/EIR such MCTEL DMC allow to offer a Welcome to Roamer feature to inbound roamers (foreign subscribers roaming on operator network), without needing to install expensive probes on the network. The only prerequisite is the MSC/VLR CheckIMEI commands are able to transmit the IMSI optional parameter additionally to the IMEI. The operator has then simply to configure for each partner network (identified by its Mobile Country Code MCC and Mobile Network Code MNC): user language. welcome message to send by SMS after successful roamer registration on the network. optional parameters such welcome message lifetime (to avoid for example that cross border subscribers receive several welcome messages a day each time they are switching networks).
3.3.5 Automatic Device Detection and Configuration

This very advanced feature allows to automatically detect a new device as soon the user inserts its SIM card in the handset and turns it on and to configure it automatically. It could be performed using several mechanisms: the easiest and most advanced way is to use a EIR/DMC SS7 module that will be informed by the network MSC as soon the new handset is turned on. The prerequisite is to have MSC supporting the CheckIMEI MAP request with the IMSI optional parameter (same than for the Welcome to Roamer features). another way is to use SS7 probes that may be also be used for other services. some operators use a SIM application (SIM Toolkit, Java applet, WIB or USAT Interpreter application) that checks each time SIM is activated the current handset and that will send a request to the DMC using either SMS or USSD command when the application detects the SIM has been inserted in a new handset. This solution is effective but present numerous drawbacks: o it must be planned well in advance and will be 100% effective only when all SIM cards will integrate the application. o it will increase the cost of the SIM card (that will require for example SIM Toolkit or Java support) and will make more difficult for the operator the switching of its SIM card supplier. o it will load the network with SMS or USSD requests. Near-real time device detection may also be achieved using the automatic processing of CDR flow. However, as the flow is not perfect real-time and as CDR are generated only after call completion, this solution could not ensure precise IMEI retrieval each time.
3.3.6 Back office integration with OMC

Backoffice integration with the operator OMC will allow to: (c) MCTEL - 23 Disclosure or reproduction prohibited without MCTEL prior written approval 41, avenue Hector Otto BP 225 98004 MONACO Cedex Tl: +377 9216 8888 Fax: +377 9216 8865 email: sales@mctel.net - Web: www.mctel.net
March 2006
v1.1
populate initially and update the subscriber database from the data exported by the operator and listing the essential data listed below (the IMEI and MSISDN being mandatory data). export the DMC data to technical or marketing ends. The DMC is able to export not only the raw data such IMEI but also interpreted data (terminal brand and model) or handset features and capabilities (supported media formats). Usage Subscriber MSISDN Subscriber handset IMEI (last known) Subscriber IMSI OTA SIM keys (if SIM OTA is needed) Subscriber group or kind of subscription Mandatory YES YES NO NO NO
Field MSISDN IMEI IMSI SIM OTA Keys Subscription Type
Tableau 4: Data to import for populating and updating the DMC subscriber database
3.3.7 Help Desk Web integration

Web menus allows the Help Desk staff to access the DMC features, and for example: retrieve subscriber configuration, settings, current handset to configure automatically or manually the subscriber handset. History logs will keep track of all provisioning performed by the DMC on a given subscriber handset.
3.3.8 Operator Web portal integration

The manual and automatic configuration tools of the DMC are usually easy to integrate in the operator Web portal to allow subscriibers themselves to configure their terminals. Appropriate safety mechanisms ensure the user is only able to configure its own terminal and could not exceed a given number of configuration tries per day.
3.3.9 Open interfaces

Open HTTP/SOAP Webservice interfaces allow external program or equipments to perform oprations on the DMC: to perform searches to retrieve either the subscriber raw data (IMEI) or the terminal brand, model and detailed capabilities. to request OTA configuration of a terminal. to perform an Automatic Device Detection on a given MSISDN. to request SyncML Device Synchronisation operations, such as downloading a new application, performing a backup/restore operation. This enables the operator to access and use the DMC features from other applications.
(c) MCTEL
March 2006
v1.1
APPENDIXES
APPENDIX A MCTEL Mobile solutions APPENDIX B Example of mobile handset characteristics
(c) MCTEL
March 2006
v1.1
4 APPENDIX A: MCTEL Mobile Solutions

Mobile Network Solutions Name MCTEL SMS-Center MCTEL F-SMS/MMS Center MCTEL MMS-Center MCTEL Premium Gateway MCTEL Device Management Center MCTEL Equipment Identity Register MCTEL IN Prepaid Platform MCTEL Content Delivery Platform MCTEL Multimedia Gateway VIDEOSMS Development Toolbox VIDEOSMS Application Gateway Interface VIDEOSMS Desktop SMS Other network interface Name VIDEOTELEFAX VIDEOTELEX Email gateway VTX/Gate, VTX/Web, VIDEONET Usage Fax Gateway Telex Gateway Email gateway Videotex Gateways Usage SMS-Center Fixed SMS/MMS-Center with SMS to Voice Text To Speech technology MMS-Center Premium Gateway, allowing to setup Premium SMS, MMS and Wap services and to connect Value Added Service Providers Device Management Center for handsets configuration Manage stolen or prohibited devices IN Prepaid platform Content Delivery Platform to deliver logos, ringtones, video, Java games using Premium SMS or IVR, Web and Wap Advanced SMS/MMS/Wap gateway for Value Added Service Providers Mobile multimedia toolbox to develop Value Added applications on the MCTEL Multimedia Gateway Web to Mobile translation tools PC SMS Sender
(c) MCTEL
March 2006
v1.1
5 Appendix B Handset database
The MCTEL handset database includes more than 2000 terminals and is daily updated with new devices. An updated database is supplied to MCTEL customers under contract every week. This handset database stores all terminal characteristics and is also used by our Content Delivery Platform to deliver appropriate content to the mobile subscriber according to the user request (ringtones, pictures, video, Java games), or by our MMS-Center for automatic media rendering and adapation. For each terminal packaged by the operator, MCTEL additionally provides information for configuration support to call centers operators and subscribers. Here is an extract of the database to show some characteristics maintained by the DMC for each mobile device. The actual database stores much more information, the detailed field list may be supplied after NDA signature. Characteristics Brand Model TAC Example General information Nokia 6610i 35379000, 35338100, 35536200, 35536600, 35434600, 35536500, 35434500, 35378900 Nokia6610i Network characteristics GSM 900/ GSM1800/ GSM1900 CSD, GPRS Class 6 Display characteristics 128 x 128 4096 20 8 Caractristiques multimdia 1.0 UTF-8, ISO-8859-1, Unicode JPEG, GIF, Animated GIF, PNG, BMP MIDI 4, SP-MIDI, Nokia-ring 3GPP None YES Wap characteristics YES - 27 Disclosure or reproduction prohibited without MCTEL prior written approval 41, avenue Hector Otto BP 225 98004 MONACO Cedex Tl: +377 9216 8888 Fax: +377 9216 8865 email: sales@mctel.net - Web: www.mctel.net
Comments
User-Agent Technology Bearers Size in pixels Colors Raws Lines MMS version Character sets Supported picture formats Supported audio formats Supported video formats Streaming support Integrated camera WML support (c) MCTEL
March 2006
MCTEL OTA Device Management White Paper WML version Deck size Push support Push maximum size Web support Browser UA Name Format Version Frames Tables iMode CHTML support Emoji support Etc... Java support MIDP version CLDC version DoJa version DRM supported 1.1, 1.2.1 5600 YES 685 XHTML browser characteristics YES Nokia XHTML Basic 1.0 NO YES iMode cHTML characteristics NO NO Java characteristics YES 2.0 2.0 1.0 DRM characteristics OMA DRM ForwardLock V1.0
v1.1
(c) MCTEL
March 2006

White Paper DMC en

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

White Paper DMC en

Încărcat de

Drepturi de autor:

Formate disponibile

a mcTEL whitepaper

The OTA & Mobile Device Management Whitepaper

Version: 1.2 Date: April 5, 2006

MCTEL (MONACO TELEMATIQUE)

MONACO TELEMATIQUE MCTEL

MCTEL Livre blanc "Device Management Center OTA"

MCTEL OTA Device Management White Paper

MCTEL OTA Device Management White Paper

Confidentiel page iii

MCTEL OTA Device Management White Paper

1.1 General introduction

1.2 About the Authors

-4Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

Figure 1 MCTEL Mobile Solutions

-5Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

2 Why a Device Management Center ?

Figure 2: Functional schematics of MCTEL Device Management Center

2.2 Marketing Analysis (data-mining)

-7Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

2.3 Selective user information (selective broadcast)

-8Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

2.4 Over the Air terminal configuration (OTA)

-9Disclosure or reproduction prohibited without MCTEL prior written approval

2.5 Automatic Device Detection & Configuration (Automatic Device Configuration)

- 10 Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

2.6 SIM OTA Configuration & Download

- 11 Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

2.7 Error detection and correction

2.8 Managing stolen and prohibited devices (Equipment Identity Register)

- 12 Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

2.9 Welcome to roamers

- 13 Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper o

2.11 Firmware update

2.12 Enterprises Device Management

- 14 Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

2.13 Upgrade of network equipment

- 15 Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

3 Setting up a Device Management Center in practice

3.2 The barriers to DMC effectiveness

- 16 Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

3.2.1 OTA SMS Provisioning command throughput

3.2.2 Automatic IMEI Retrieval for device detection

- 17 Disclosure or reproduction prohibited without MCTEL prior written approval

MCTEL OTA Device Management White Paper

3.2.3 Automatic Device Detection and Configuration

3.2.4 IMSI Automatic Retrieval

3.2.5 Quality and updating of the mobile database

MCTEL OTA Device Management White Paper

retrieves detailed terminal characteristics for the marketing analysis (data-mining).

3.2.6 OTA protocols support

3.3 Connecting in practice a DMC in the operator network

MCTEL OTA Device Management White Paper