Appendix "A2" - Message types - Operator logo XML
Introduction
Operator logos are graphical images that are displayed on a phone when the phone signs into a GSM network. An operator logo is identified by a country code and a mobile network code. The GSM handsets supporting this technology can store more then one images at a time, and when the handset roams between networks, it can display the appropriate operator logo.
An operator logo is an OTA bitmap. The OTA bitmap is a black and white picture with a gray scale level of 1 to 255. OTA bitmap has a header and a body. The header has a predefined width and a height field, that specifies, how the stream of bits in the body should be broken into lines.
When designing operator logos, the designer must keep in mind, that different handset support operator logos with different dimensions. The most common bitmap size for operator logos is 72x14 pixels.
Support for Operator Logos in Ozeki Message Server 6
Because an operator logo has several parameters in addition to the bitmap stream, Ozeki uses an XML format to represent it. The following example illustrates the structure of this XML file:
<operatorlogo> <version>0</version> <mcc>123</mcc> <mnc>45</mnc> <otabitmap> 00480E00 FFFFFFFFFFFFFFFF FF00000000000000 0000FFFFFFFFFFFF FFFFFF0000000000 0000000010F00000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 000000000001 </otabitmap> </operatorlogo>
version |
The operator logo version number |
mcc | Mobile Country Code |
mnc | Mobile Network Code |
otabitmap |
OTA bitamap data (The bit stream containing the data. Note: ozeki message server 6 will remove any spaces from the hexadecimal character string) |
Sending an operator logo in SMS
To send an operator logo message with Ozeki Message Server 6, you need to specify a message type, that tells the software that the following message is an operator logo. To send the above example, you would use the following message type:
SMS:OPLOGOXML
In this case, the message type is made up from two sections. The first section tells the message server thatthis is an SMS message. This way only the drivers supporting SMS will be considered to deliver the message. The second section is used by the driver to use the operator logo encoder. This encoder will parse the XML file and create the protocol data unit (PDU) that will be sent as an SMS messages. After the message type has been set, the message content should be created in the proper XML format.
ExampleIf you use the database plugin, to send and receive SMS messages in Ozeki Message Server 6, you can use the following SQL statement to send an Operator Logo message:
insert into ozekimessageout (receiver,msgtype,msg,status) values ('+36205222245','SMS:OPLOGO','<operatorlogo><version>0</version>< mcc>123</mcc><mnc>45</mnc>< otabitmap>00480E00FFFFFFFFFFFFFFFFFF000000000000000000FFFFFFFFFFFFFFFFFF 00000000000000000010F000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000001</otabitmap></operatorlogo>','send');
More information
- A1 - OTA Bitmap
- A2 - Operator logo I
- A3 - Operator logo II
- A4 - Ringtone
- A5 - Wappush
- A6 - VCalendar
- Appendix "A7" - Message types - VCard
- A8 - Barcode
- B - Service providers
- C - SMSC numbers
- D - GSM Operators
- E - SMS alphabet
- Appendix "F" - GSM error codes
- G - Conn strings
- H - References
- I - MMSC information
- Frequently asked questions
- K - SMS Format