USSD Services For Interactive Mobile Users.. 11038 An

User Manual: 11038

Open the PDF directly: View PDF .
Page Count: 17

Download
Open PDF In Browser	View PDF

Small Logo

USSD Services for
Interactive Mobile Users
Application Note

Building User-Friendly Mobile
Telephony Applications Using
Dialogic Distributed Signaling
Interface Components
®

USSD Services for Interactive Mobile Users

Application Note

Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

Executive Summary
The application note describes the implementation of an interactive Unstructured Supplementary Service Data
(USSD) service for GSM mobile users. Information is provided to describe how service providers who decide to use
the power of USSD to provide mobile users with menu-driven, interactive services such as mobile account balance
checking and top up, sports scores, and news and weather information can do so via current technologies and
signaling.
An overview of the network architecture and a description of interactive USSD services are presented, as well as
signaling requirements for such services. Sample code also shows an application that can be developed using the
Dialogic Distributed Signaling Interface (DSI) MAP Layer.
®

Finally, system design considerations are discussed, showing how high-performance USSD application platforms
can be developed with Dialogic DSI Components, enabling system designers to offer interactive USSD services
worldwide.
®

USSD Services for Interactive Mobile Users
Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

Table of Contents
Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Network Architecture for USSD Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
USSD Signaling Requirements  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Example Menu-Driven USSD Application  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
How to Format USSD Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Formatting a USSD Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Creating USSD Applications  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
MAP Services for USSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
MAP Parameters for USSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Information for System Design: Working with MAP USSD Signaling  . . . . . . . . . . . . . . . . . . . . 8
Code Modifications to the Dialogic “MTU” Example Application . . . . . . . . . . . . . . . . . . 8
®

Dialogic DSI Components for USSD Services  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
®

Summary  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
For More Information  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1

Application Note

Application Note

USSD Services for Interactive Mobile Users
Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

Introduction

• A real-time “session” is initiated between the mobile user
and the USSD application platform when the service is
invoked, allowing data to be sent back and forth between
the mobile user and the USSD application platform until
the USSD service is completed.

Unstructured Supplementary Service Data (USSD) is a
capability built into GSM phones, much like the Short Message
Service (SMS).
USSD differs from SMS as follows:

This concept of a real-time data session is particularly useful if
opting to build an interactive menu-driven application, such as
a mobile-initiated “Balance Enquiry and Top Up” application,
as described in the Example Menu-Driven USSD Application
section.

• SMS uses a “store and forward” technique to deliver text
messages:
A text message is first sent to a sender’s Short Message
Service Center (SMSC) before the SMSC tries to deliver
the text message to the recipient. The sender receives an

Note: A USSD service could be invoked by either the mobile
user or the USSD platform [GSM TS 23.090 Unstructured
Supplementary Service Data (USSD) - Stage 2].

indication of whether the text was successfully received by
the SMSC; however, the text message is not guaranteed to
reach the recipient instantly.

Network Architecture for USSD Signaling

 Note: The “SMS Router” concept can be used to improve

USSD services use the existing architecture of GSM networks. A
user dialing a USSD service code initiates a dialog with a USSD
application residing in a mobile network, as detailed in Figure
1. The “Network Node,” shown in Figure 1, could be either an
MSC, VLR, HLR, or other network entity, such as an application
platform, which has access to the specific USSD service.

SMS delivery time in some instances.
• USSD information is sent directly from a sender’s mobile
handset to an application platform handling the USSD
service. The USSD service can be located either in the
sender’s mobile network or in a visited mobile network.
Mobile User

MMI

Application

USSD Handler

USSD Handler

Mobile Station

Network Node

Source: European Telecommunications Standards Institute (ETSI)

[TS 23.090]: “The Unstructured Supplementary Service Data (USSD) mechanism allows
the Mobile Station (MS) user and a PLMN operator-defined application to communicate
in a way which is transparent to the MS and to intermediate network entities.”
Figure 1. Handling of USSD

2

USSD Services for Interactive Mobile Users

Application Note

Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

3GPP TS 22.090 details specific “MMI strings” or telephone
numbers that could be dialed from a user’s “mobile station”
(mobile handset) to initiate USSD services. Specifically, the
following number range is defined as being allocated in GSM
networks for USSD services residing in the user’s Home Public
Land Mobile Network (HPLMN):

An example of such an application could be as follows:
1. A mobile user initiates the “Balance Enquiry and Top Up”
service by dialing the USSD string defined by the service
provider; for example, *#123#.
 Note: See [3GPP TS 22.090] for more details regarding
USSD string formats.

[3GPP TS 22.090]:
“1, 2 or 3 digits from the set (*, #) followed by 1X(Y), where
X=any number 0-4, Y=any number 0-9, then, optionally “*
followed by any number of any characters”, and concluding
with # SEND”.

2. The USSD application receives the service request from the
user and responds by sending the user a menu of options.
3. The user responds by selecting a “current balance” option.

For example, a user could dial *#123# from the user’s mobile
handset to reach a specific USSD service, where the USSD
application itself resides in the user’s HPLMN.

4. The USSD application sends back details of the mobile
user’s current account balance and also gives the option
to top up the balance.

In this way, the application developer could decide to build,
install, and advertise use of a USSD service such as a menudriven application (see the Example Menu-Drive USSD
Application section) within a particular mobile network. The
new USSD service would be available worldwide to subscribers
to that mobile service via the USSD service number, which
follows the rules detailed in 3GPP TS 22.090.

5. The user selects to top up his/her account.
6. The application responds by asking how much credit to
add?
7. The mobile user responds with the amount to add.

USSD Signaling Requirements
Example Menu-Driven USSD Application

8. The USSD application responds by sending an updated
balance and ends the session.

One could decide to develop a mobile-initiated “Balance
Enquiry and Top Up” application using USSD signaling,
enabling a mobile user to interact with an application via the
user’s handset, in order to view his/her current mobile account
balance and top up as needed.

Figure 2 shows an example of the MAP/TCAP message
sequence required to realize the data transfers between a
mobile user’s handset and the USSD application to implement
the “Balance Enquiry and Top Up” service described above.

3

Application Note

USSD Services for Interactive Mobile Users
Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

Mobile
Handset

1.

User dials
*#123#

USSD Application
Platform

TCAP Begin
invoke
MAP_PROCESS_UNSTRUCTURED_SS_REQUEST

2.
TCAP Continue
invoke
MAP_UNSTRUCTURED_SS_REQUEST

3.

Welcome to XYZ Telecom
Press:
(1) Balance Notification
(2) Top Up service

User presses 1
TCAP Continue
return result (last)
MAP_UNSTRUCTURED_SS_REQUEST

4.
TCAP Continue
invoke
MAP_UNSTRUCTURED_SS_REQUEST

5.

Your current balance is: 5.50
Press:
(1) to Top Up
(2) to end

User presses 1
TCAP Continue
return result (last)
MAP_UNSTRUCTURED_SS_REQUEST

6.
TCAP Continue
invoke
MAP_UNSTRUCTURED_SS_REQUEST

7.

XYZ Telecom Top Up
Please enter:
The amount to Top Up
e.g. 10.00

User presses 15.00
TCAP Continue
return result (last)
MAP_UNSTRUCTURED_SS_REQUEST

8.
TCAP End
return result (last)
MAP_PROCESS_UNSTRUCTURED_SS_REQUEST

Thank you for using XYZ
Top Up! Your current
balance is: 20.50

Figure 2. Mobile-Initiated “Balance Enquiry and Top Up” Service (adapted from Figure 6.2, [3GPP TS 24.090])

Notes on the USSD MAP/TCAP numbered message sequence shown in Figure 2:
1. The mobile-initiated USSD service commences with a mobile user dialing the USSD string (for example, *#123#). A TCAP
dialogue is initiated following this, with a MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service component sent to the
USSD application platform.
2. The USSD application platform receives the request to initiate a USSD service from the mobile user. The platform determines
the specific USSD service requested by checking the USSD string dialed.

4

USSD Services for Interactive Mobile Users

Application Note

Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

The USSD platform requests additional information from the mobile user (balance notification or top up?) via the MAP_
UNSTRUCTURED_SS_REQUEST service.
3. The USSD platform receives the user’s response within a MAP_UNSTRUCTURED_SS_REQUEST return result component.
4-7. The USSD application could request additional information from the mobile user several times for the same TCAP dialogue,
each time the MAP_UNSTRUCTURED_SS_REQUEST service would be used, as shown in sequence 4 through 7.
8. Finally, the network USSD application platform ends the TCAP dialogue, sending MAP_PROCESS_UNSTRUCTURED_SS_
REQUEST return result (Thank you for using XYZ…).
In the above example, the USSD platform requests further information from the mobile user via the MAP_UNSTRUCTURED_SS_
REQUEST service. If the USSD platform did not require any further information from the mobile user, the USSD application could
respond by sending a MAP_PROCESS_UNSTRUCTURED_SS_REQUEST return result component (as shown in Figure 2, point
8) and ending the TCAP dialogue.
For more information on mobile- (and network-) initiated USSD operations and the use of MAP USSD services, refer to [3GPP
TS 24.090] in the References section.

How to Format USSD Text
In the “Balance and Top Up” service example shown in Figure 2, the network USSD application responds to inputs from the
mobile user with various menus and questions. Figure 3 shows an example of a menu on a mobile handset.

Welcome to XYZ Telecom
Press:
1. Balance Notification
2. Top Up Service

Figure 3. USSD Menu Example on a Mobile Handset

Formatting a USSD Menu
How Is Menu Information Sent to the User?
The menu, as it appears on the screen of the mobile handset, is actually a straightforward text string broken up using carriage
return  characters as shown in Figure 4.

5

Application Note

USSD Services for Interactive Mobile Users
Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

The text string:
Welcome to XYZ TelecomPress:1. Balance Notification 2. Top Up Service
Will be presented on the handset as ...

Welcome to XYZ Telecom
Press:
1. Balance Notification
2. Top Up Service

Figure 4. Formatting a USSD Menu for Display on a Handset

Creating USSD Applications
MAP Services for USSD
As shown in Figure 2, MAP services “MAP_UNSTRUCTURED_SS_REQUEST” and “MAP_PROCESS_UNSTRUCTURED_SS_
REQUEST” are used to deliver text that forms the menus, questions, and answers between a network USSD application platform
and a mobile user’s handset.
Note: MAP services PROCESS_UNSTRUCTURED_SS_REQUEST and UNSTRUCTURED_SS_REQUEST are defined in [3GPP TS
29.002].
These two MAP services both use parameters “USSD Data Coding Scheme” and “USSD String” as detailed in Figure 5.
UNSTRUCTURED_SS_REQUEST
Parameter

Class

PROCESS_UNSTRUCTURED_SS_REQUEST
Context

Parameter

Class

Context

Primitive type octet

M

V1, V2

Primitive type octet

M

V1, V2

Timeout (default = 600 seconds)

O

V1, V2

Timeout (default = 600 seconds)

O

V1, V2

Invoke ID

M

V1, V2

Invoke ID

M

V1, V2

USSD Data Coding Scheme

M

V1, V2

USSD Data Coding Scheme

M

V1, V2

USSD String

M

V1, V2

USSD String

M

V1, V2

Alerting pattern

O

V2

Alerting pattern

O

V2

MSISDN

O

V2

MSISDN

O

V2

Ellipsis

O

V2

Figure 5. USSD MAP Service Definitions from [MAP Programmer’s Manual]

6

USSD Services for Interactive Mobile Users

Application Note

Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

MAP Parameters for USSD
USSD Data Coding Scheme
As defined in 3GPP TS 29.002, this parameter details “the alphabet and the language used for the unstructured information in
an Unstructured Supplementary Service Data operation.”
Encoding is according to 3GPP TS 23.038 section “Cell Broadcast Data Coding Scheme”. A typical encoding scheme used is as
follows:
“GSM 7 bit default alphabet”, encoded within the parameter as “00001111”.
The following code sample shows how the “GSM 7 bit default alphabet” USSD Data Coding scheme parameter could be encoded
within a customer application:
/* USSD coding parameter */
bit _ set(req.pi, MAPPN _ USSD _ coding);
/*
* USSD coding set to ‘GSM default alphabet’ 00001111
* see 3GPP TS 23.038 ‘Cell Broadcast Data Coding Scheme’
* for further detail
*/
bit _ to _ byte(req.ussd _ coding.data, 0x1, 0);
bit _ to _ byte(req.ussd _ coding.data, 0x1, 1);
bit _ to _ byte(req.ussd _ coding.data, 0x1, 2);
bit _ to _ byte(req.ussd _ coding.data, 0x1, 3);
bit _ to _ byte(req.ussd _ coding.data, 0x0, 4);
bit _ to _ byte(req.ussd _ coding.data, 0x0, 5);
bit _ to _ byte(req.ussd _ coding.data, 0x0, 6);
bit _ to _ byte(req.ussd _ coding.data, 0x0, 7);
req.ussd _ coding.num _ bytes = 1;
For more information, see [3GPP TS 23.038] listed in the References section.
USSD String
USSD characters are packaged using a 7 bit encoding scheme, much like SMS characters, as defined in 3GPP TS 23.038.
The Dialogic source code sample software, “MAP Test Utility”, contains a function example called “MTU_str_to_def_alph()”.
®

The function MTU_str_to_def_alph() converts an ascii string into “GSM 7 bit default alphabet” encoding, following rules defined
in [3GPP TS 23.038] (also see Note: Support for USSD Character Packing below). This function can be useful, such as if creating
a USSD string text to send over a GSM network based upon user input.
To test usage of the MTU_str_to_def_alph() function, the following code sample (based upon MTU source code) encodes a USSD
string menu text similar to that which was previously discussed:

7

USSD Services for Interactive Mobile Users

Application Note

Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

/* USSD string parameter */
bit _ set(req.pi, MAPPN _ USSD _ string);
/*
* USSD string
*/
mtu _ args.message=
“Welcome to XYZ Telecom\n Press:\n 1. Balance Notification\n 2. Top Up Service”;
num _ da _ chars = MTU _ str _ to _ def _ alph(mtu _ args.message,
					
&req.ussd _ string.data[req.ussd _ string.num _ bytes],
					
&da _ len,
					
MAX _ DATA _ LEN - req.ussd _ string.num _ bytes);
Note the use of “\n” to encode a carriage return, as required for menu type text displays.
Note: Support for USSD Character Packing — 3GPP TS 23.038 (defined in the “USSD packing” section) details two USSD text
cases that the supplied example function MTU_str_to_def_alph() does not support. In the two cases, the user could extend the
MTU_str_to_def_alph() function source code as follows:
1. “If the total number of characters to be sent equals (8n-1), where n=1,2,3, etc., then there are 7 spare bits at the end of the
message. To avoid the situation where the receiving entity confuses 7 binary zero pad bits as the @ character, the carriage
return or  character … shall be used for padding in this situation, just as for Cell Broadcast.”
2. “If  is intended to be the last character and the message (including the wanted ) ends on an octet boundary, then
another  must be added together with a padding bit 0.”
See [3GPP TS 23.038] for more information on these two cases, in order to develop a complete str_to_def_alph() function.

Information for System Design: Working with MAP USSD Signaling
Code Modifications to the Dialogic “MTU” Example Application
®

The following section has an example of a function that can be used to send the service MAP_PROCESS_UNSTRUCTURED_SS_
REQUEST to initiate a USSD session, as previously shown in Figure 2.
The code is based upon the structure of existing code for other MAP services supplied for the MAP Test Utility (MTU) example,
as part of the Dialogic User Part Development package [MTU and MTR User Guide].
®

This code sample indicates how to set the MAP service name for MAP_PROCESS_UNSTRUCTURED_SS_REQUEST and includes
the USSD specific parameters “USSD Data Coding Scheme” and “USSD String” previously described.

8

Application Note

USSD Services for Interactive Mobile Users
Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

Code Sample to Send
MAP_PROCESS_UNSTRUCTURED_SS_REQUEST
static int MTU _ process _ uss _ req
u16 dlg _ id;			
/*
u8 invoke _ id;		
/* invoke
{
MTU _ DLG *dlg;			
/*
MTU _ MSG req;			
/*
u8 da _ len;			
/*
u8 num _ da _ chars;		
/*

(dlg _ id, invoke _ id)
dialogue ID */
ID */

/* USSD */

dialogue data structure */
structured form of request message */
length of formatted u-data */
number of formatted*/

dlg = &(dlg _ data[dlg _ id]);
/*
* The following parameters are set in the
* MAP _ PROCESS _ UNSTRUCTURED _ SS _ REQUEST:
*
ussd-DataCodingScheme
*
ussd-string - this will be entered by the user e.g. *#123#
*/
memset((void *)req.pi, 0, PI _ BYTES);
req.dlg _ id = dlg _ id;
req.type = MAPST _ PRO _ UNSTR _ SS _ REQ _ REQ;
req.invoke _ id = invoke _ id;
bit _ set(req.pi, MAPPN _ invoke _ id);
/* USSD coding parameter */
bit _ set(req.pi, MAPPN _ USSD _ coding);
/*
* USSD coding set to ‘GSM default alphabet’ 00001111
* see 3GPP TS 23.038 ‘Cell Broadcast Data Coding Scheme’
* for further detail
*/
bit
bit
bit
bit
bit
bit
bit
bit

_
_
_
_
_
_
_
_

to
to
to
to
to
to
to
to

_
_
_
_
_
_
_
_

byte(req.ussd
byte(req.ussd
byte(req.ussd
byte(req.ussd
byte(req.ussd
byte(req.ussd
byte(req.ussd
byte(req.ussd

_
_
_
_
_
_
_
_

coding.data,
coding.data,
coding.data,
coding.data,
coding.data,
coding.data,
coding.data,
coding.data,

0x1,
0x1,
0x1,
0x1,
0x0,
0x0,
0x0,
0x0,

req.ussd _ coding.num _ bytes = 1;
/* USSD string parameter */
bit _ set(req.pi, MAPPN _ USSD _ string);

9

0);
1);
2);
3);
4);
5);
6);
7);

USSD Services for Interactive Mobile Users

Application Note

Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

/*
* USSD string
*/
req.ussd _ string.num _ bytes = 1; /* USSD string, allow byte for data length */
num _ da _ chars = MTU _ USSD _ str _ to _ def _ alph(mtu _ args.ussd _ string,
					
&req.ussd _ string.data[req.ussd _ string.num _ bytes],
					
&da _ len,
					
MAX _ DATA _ LEN - req.ussd _ string.num _ bytes);
/*
* fill in the ussd _ string, the number of formated default alphabet
characters
*/
req.ussd _ string.data[req.ussd _ string.num _ bytes - 1] = num _ da _ chars;
req.ussd _ string.num _ bytes += da _ len;
/*
* Operation timeout - 15 seconds
*/
bit _ set(req.pi, MAPPN _ timeout);
req.timeout = 15;
MTU _ send _ srv _ req(&req);
return(0);
} /* end of MTU _ process _ uss _ req() */
Encoding Application Context for USSD Version 2 Operations
The following code sample can be used to add support within MTU for the USSD version 2 application context, as defined in
[3GPP TS 29.002].
Add the following definition to mtu.c:
/* new application context networkUnstructuredSsContext-v2 */
static u8 networkUnstructuredSsContextV2[AC _ LEN] =
{
06,		
/* object identifier */
07,		
/* length */
04,		
/* CCITT */
00,		
/* ETSI */
00,		
/* Mobile domain */
01,		
/* GSM network */
00,		
/* application contexts */
19,		
/* map-ac networkUnstructuredSs */
02			
/* version 2 */
};
10

Application Note

USSD Services for Interactive Mobile Users
Building User-Friendly Mobile Telephony Applications Using
Dialogic Distributed Signaling Interface Components
®

Add the following code to mtu.c function “MTU_open_dlg” to make use of the USSD version 2 application context:
case MTU _ PROCESS _ USS _ REQ:
/*
* Send MAP _ PROCESS _ UNSTRUCTURED _ SS _ REQUEST
*/
for (i=0; i
Source Exif Data: 
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
XMP Toolkit                     : Adobe XMP Core 4.0-c316 44.253921, Sun Oct 01 2006 17:08:23
Instance ID                     : uuid:2235a851-8477-45fa-9536-76ac312c6201
Document ID                     : adobe:docid:indd:98133c2d-58ac-11dd-ab46-9ce0073d8572
Rendition Class                 : proof:pdf
Derived From Instance ID        : 98133c2c-58ac-11dd-ab46-9ce0073d8572
Derived From Document ID        : adobe:docid:indd:702deb43-4f32-11dd-8399-cf0d53daae11
Manifest Link Form              : ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream, ReferenceStream
Manifest Placed X Resolution    : 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00
Manifest Placed Y Resolution    : 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00, 72.00
Manifest Placed Resolution Unit : Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches, Inches
Manifest Reference Instance ID  : uuid:B08DC49F3DE111DD8AF19161450DDD36, uuid:33900D3CE83D11DCBBF3BF4C46937C79, uuid:196E31253D3B11DD9534961109BE0B88, uuid:196E31253D3B11DD9534961109BE0B88, uuid:196E31253D3B11DD9534961109BE0B88, uuid:375C3A094F6711DD8322A6D32C764664, uuid:196E31253D3B11DD9534961109BE0B88, uuid:196E31253D3B11DD9534961109BE0B88, uuid:1E6ED85E503011DDAB219ADA3797E73A, uuid:196E31253D3B11DD9534961109BE0B88, uuid:1181DF915EEC11DDBC36FD32AAC40EFE, uuid:196E31253D3B11DD9534961109BE0B88, uuid:1181DF915EEC11DDBC36FD32AAC40EFE, uuid:196E31253D3B11DD9534961109BE0B88, uuid:196E31253D3B11DD9534961109BE0B88, uuid:196E31253D3B11DD9534961109BE0B88, uuid:196E31253D3B11DD9534961109BE0B88, uuid:196E31253D3B11DD9534961109BE0B88, uuid:1E6ED866503011DDAB219ADA3797E73A, uuid:196E31253D3B11DD9534961109BE0B88, uuid:EF2A027D6B50DD11B029C3505A6992F8, uuid:196E31253D3B11DD9534961109BE0B88, uuid:196E31253D3B11DD9534961109BE0B88, uuid:1E9CE701E7AB11DCB08AA542D7C9790D
Manifest Reference Document ID  : uuid:B08DC49E3DE111DD8AF19161450DDD36, uuid:1E9CE705E7AB11DCB08AA542D7C9790D, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:375C3A074F6711DD8322A6D32C764664, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:02F884A2502011DDAB219ADA3797E73A, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:1E6ED861503011DDAB219ADA3797E73A, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:1E6ED861503011DDAB219ADA3797E73A, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:7D1B36ED564BDD11AB40FC2369053CF8, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:7D1B36ED564BDD11AB40FC2369053CF8, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:07F74E5AEDDB11DC9E2BCE4959B40A51, uuid:1E9CE700E7AB11DCB08AA542D7C9790D
Create Date                     : 2008:07:30 09:43:09-04:00
Modify Date                     : 2008:07:30 09:45:08-04:00
Metadata Date                   : 2008:07:30 09:45:08-04:00
Creator Tool                    : Adobe InDesign CS3 (5.0.2)
Thumbnail Format                : JPEG
Thumbnail Width                 : 256
Thumbnail Height                : 256
Thumbnail Image                 : (Binary data 6669 bytes, use -b option to extract)
Format                          : application/pdf
Title                           : USSD Services for Interactive Mobile Users..
Creator                         : Dialogic Corporation
Description                     : Application Note
Subject                         : USSD, Unstructured Supplementary Service Data Services, mobile, GSM, Dialogic, Distributed Signaling Interface, DSI, menu-driven, interactive services, Short Message Service, SMS, DSI Signaling Servers, DSI SS7HDE Network Interface Boards, PCIe, PCI Express, DSI SS7HDC Network Interface Boards, cPCI, DSI SS7HDP Network Interface Boards, SPCI4 Network Interface Boards PCI
Startup Profile                 : Print
Producer                        : Adobe PDF Library 8.0
Trapped                         : False
Keywords                        : USSD, Unstructured Supplementary Service Data Services, mobile, GSM, Dialogic, Distributed Signaling Interface, DSI, menu-driven, interactive services, Short Message Service, SMS, DSI Signaling Servers, DSI SS7HDE Network Interface Boards, PCIe, PCI Express, DSI SS7HDC Network Interface Boards, cPCI, DSI SS7HDP Network Interface Boards, SPCI4 Network Interface Boards PCI
Page Count                      : 17
Author                          : Dialogic Corporation
Warning                         : [Minor] Ignored duplicate Info dictionary

EXIF Metadata provided by EXIF.tools