11/17/08

Wireless Telephony Application (WTA)

  Collection of telephony specific extensions
  Extension of basic WAE application model
  content push
  server can push content to the client
  client may now be able to handle unknown events
  handling of network events
  table indicating how to react on certain events from the network
  access to telephony functions (WTAI)
  any application on the client may access telephony functions
  Example
  calling a number (WML)
wtai://wp/mc;07216086415
  calling a number (WMLScript)
WTAPublic.makeCall("07216086415");

WTA logical architecture

other telephone networks
WTA server
client
WML
scripts mobile WTA
WTA & WML network user agent
server
WML
decks
WAP gateway repository
WTA
services
encoders
& device
network operator decoders specific
trusted domain other functions
servers

third party
firewall
servers

Voice box example

WTA-User-Agent WTA-Gateway WTA-Server Mobile network Voice box server
Indicate new voice message

Generate new deck

Service Indication Push URL
Display deck;
user selects
WSP Get HTTP Get

Respond with content

Binary WML WML

Display deck;
user selects
WSP Get HTTP Get
Respond with card
WML for call
Binary WML
Play requested voice message
Wait for call
Call setup
Setup call
Setup call
Accept call
Accept call Accept call
Voice connection

1
 11/17/08

WTAI - example with WML only

  <?xml version="1.0"?>
  <!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
  "http://www.wapforum.org/DTD/wml_1.1.xml">
  <wml>
  <card id="card_one" title="Tele voting">
  <do type="accept">
  <go href="#card_two"/>
  </do>
  <p> Please choose your candidate! </p>
  </card>
  <card id="card_two" title="Your selection">
  <do type="accept">
  <go href="wtai://wp/mc;$dialno"/>
  </do>
  <p> Your selection:
  <select name="dialno">
  <option value="01376685">Mickey</option>
  <option value="01376686">Donald</option>
  <option value="01376687">Pluto</option>
  </select>
  </p>
  </card>
  </wml>

WTAI - example with WML and WMLScript I

  function voteCall(Nr) {
  var j = WTACallControl.setup(Nr,1);
  if (j>=0) {
  WMLBrowser.setVar("Message", "Called");
  WMLBrowser.setVar("No", Nr);
  }
  else {
  WMLBrowser.setVar("Message", "Error!");
  WMLBrowser.setVar("No", j);
  }
  WMLBrowser.go("showResult");
  }
 

WTAI - example with WML and WMLScript II

  <?xml version="1.0"?>
  <!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
  "http://www.wapforum.org/DTD/wml_1.1.xml">
  <wml>
  <card id="card_one" title="Tele voting">
  <do type="accept"> <go href="#card_two"/> </do>
  <p> Please choose your candidate! </p>
  </card>
  <card id="card_two" title="Your selection">
  <do type="accept">
  <go href="/myscripts#voteCall($dialno)"/> </do>
  <p> Your selection:
  <select name="dialno">
  <option value="01376685">Mickey</option>
  <option value="01376686">Donald</option>
  <option value="01376687">Pluto</option>
  </select> </p>
  </card>
  <card id="showResult" title="Result">
  <p> Status: $Message $No </p>
  </card>
  </wml>

2
 11/17/08

WAP push architecture with proxy gateway

  Push Access Protocol
  Content transmission between server and PPG
  First version uses HTTP
  Push OTA (Over The Air) Protocol
  Simple, optimized
  Mapped onto WSP

Push Proxy Push

Push OTA Gateway Access
Client Push Initiator
Protocol Protocol

User Agents Server

Coding,
application
checking

Push/Pull services in WAP I

  Service Indication
  Service announcement using a pushed short message
  Service usage via a pull
  Service identification via a URI

  <?xml version="1.0"?>
  <!DOCTYPE si PUBLIC "-//WAPFORUM//DTD SI 1.0//EN"
  "http://www.wapforum.org/DTD/si.dtd">
  <si>
  <indication href="http://www.piiiizza4u.de/offer/salad.wml"
  created="2002-10-30T17:45:32Z"
  si-expires="2000-10-30T17:50:31Z">
  Salad special: The 5 minute offer
  </indication>
  </si>

Push/Pull services in WAP II

  Service Loading
  short message pushed to a client containing a URI
  User agent decides whether to use the URI via a pull
  Transparent for users, always looks like a push

  <?xml version="1.0"?>
  <!DOCTYPE sl PUBLIC "-//WAPFORUM//DTD SL 1.0//EN"
  "http://www.wapforum.org/DTD/sl.dtd">
  <sl
  href="http://www.piiiizza4u.de/offer/salad.wml">
  </sl>

3
 11/17/08

Examples for WAP protocol stacks (WAP 1.x)

WAP standardization
WAE user agent

outside WAP
WAE

transaction based
WSP application

datagram based
WTP WTP application

WTLS WTLS WTLS

UDP WDP UDP WDP UDP WDP

IP non IP IP non IP IP non IP

(GPRS, ...) (SMS, ...) (GPRS, ...) (SMS, ...) (GPRS, ...) (SMS, ...)

1. 2. 3.

typical WAP application

pure data application with/
with complete protocol
without additional security
stack

i-mode – first of all a business model!

  Access to Internet services in Japan provided by NTT DoCoMo
  Services
  Email, short messages, web, picture exchange, horoscope, ...
  Big success – more than 50 million users
  Many use i-mode as PC replacement
  For many this is the first Internet contact
  Very simple to use, convenient
  Technology
  9.6 kbit/s (enhancements with 28.8 kbit/s), packet oriented (PDC-P)
  Compact HTML plus proprietary tags, special transport layer (Stop/go, ARQ, push,
connection oriented)

mobile terminal mobile network gateway content provider

cHTML + tags cHTML + tags
HTTP(S) HTTP(S)
TL TL TCP TCP TCP TCP
IP IP IP IP
PDC-P PDC-P L2 L2 L2 L2
L1 L1 L1 L1

Email example: i-mode push with SMS

Popular misconception:
application WAP was a failure, i-mode is different
WSP
and a success – wrong from a
technology point of view, right from a
WTP business point of view…
WDP

SMS i-mode as a business model:

-  content providers get >80%
Operator sends an SMS containing a of the revenue.
push message if a new email has -  independent of technology
arrived. If the user wants to read the (GSM/GPRS in Europe,
email, an HTTP get follows with the PDC-P in Japan – but also
email as response. UMTS!)

4
 11/17/08

i-mode – technical requirements

Functions Descriptions Status Requirement
WEB Access Portal Site / Internet Access M i-mode HTML (cHTML+tags)
E-mail Internet e-mail and inter-terminal email M HTTP 1.1
Security End-End security O SSL (Version 2, 3), TLS 1
Java Java application made available O Compatible i-mode JAVA
Ringing tone download Ringing melody download M SMF based
Image download Stand-by screen download M GIF (O: JPEG)
Voice call notification during i- Voice termination notified and responded during i-mode M 3GPP standard system
mode session communications
Content charge billing Per content charge billed to user M Specifications depend on each
operator’s billing system
Third party payment collection Content charge collection on behalf of Content Provider M Specifications depend on each
operator’s billing system
Reverse billing Packet usage charges can be billed to third party O Specifications depend on each
operator’s billing system
Subscriber ID transmission Hashed subscriber ID from the operator’s portal to the CP M The ID generation algorithm
transmission on each content access should be determined by each
operator and has to be secret
Number of characters per e- Number of characters (byte) per e-mail M To be defined by operators (e.g.
mail 500 byte, 1K byte, 10K byte)
Character code set supported Character code set supported by browser and used to develop content M To be defined by operators
User Agent Browser specifications to be notified M HTTP 1.1
i-mode button Dedicated button O Hard or soft key

WAP 2.0 (July 2001)

  New for developers
  XHTML
  TCP with „Wireless Profile“
  HTTP

  New applications
  Color graphics
  Animation
  Large file download
  Location based services
  Synchronization with PIMs
  Pop-up/context sensitive menus

  Goal: integration of WWW, Internet, WAP, i-mode

WAP 2.0 architecture

Service Security Multimedia Messaging Content
Application
framework

discovery services (Email) formats

External Crypto WAE/WTA User Agent

Push
services EFI libraries (WML, XHTMLMP)

Authenti-
Provisioning
Session

cation Capability Negotiation

Push Cookies
Navigation OTA Synchronisation
Identification
Discovery
Protocol framework
Transfer

Service Hypermedia transfer Strea-

PKI MMS
Lookup (WTP+WSP, HTTP) ming
Transport

Secure Connections
Datagrams
transport (TCP with
(WDP, UDP)
wireless profile)

Secure IPv4 CSD USSD GPRS ...

Bearer

bearer
IPv6 SMS FLEX MPAK ...

5
 11/17/08

WAP 2.0 example protocol stacks

WAP device WAP gateway Web server
WAE WAE
WSP WSP WAP device WAP proxy Web server
HTTP HTTP
WTP WTP WAE WAE
WTLS WTLS TLS TLS HTTP‘ HTTP‘ HTTP HTTP
WDP WDP TCP TCP TCP‘ TCP‘ TCP TCP
bearer bearer IP IP IP IP IP IP

WAP 1.x Server/Gateway/Client WAP HTTP Proxy with profiled TCP and HTTP

WAP device WAP proxy Web server

WAE WAE WAP device Web server
HTTP HTTP WAE WAE
TLS TLS HTTP IP router HTTP
TCP‘ TCP‘ TCP TCP TCP TCP
IP IP IP IP IP IP IP IP

WAP Proxy with TLS tunneling WAP direct access

WAP “Killer Apps”?

  Location-based services
  Real-time traffic reporting, Event/restaurant recommendation
  Enterprise solutions
  Email access, Database access, “global” intranet access
  Information updates “pushed” to WAP devices
  Financial services
  Banking, Bill-paying, Stock trading, Funds transfers
  Travel services
  Schedules and rescheduling, Reservations
  Gaming and Entertainment
  Online, real-time, multi-player games
  Downloadable horoscopes, cartoons, quotes, advice
  M-Commerce
  Shopping on the go
  Instant comparison shopping
  Location-based special offers and sales

M-Commerce
  The Problem
  San Francisco buses have difficulty keeping up with the posted
schedule, especially during rush hours
  The scheduled times become meaningless
  The Solution
  San Francisco implemented a system called NextBus (nextbus.com)
  The system tracks public transportation buses in real time
  NextBus calculates the estimated arrival time of the bus to each bus
stop on the route
  Arrival times are displayed in real time on:
  Internet-enabled wireless device
  The Internet and on a public screen at each bus stop
  GPS satellites let the NextBus information center know where a bus is
located making it possible to calculate arrival times

6
 11/17/08

Nextbus

Nextbus
  The Results
  Worries about missing the bus are diminished
  A bus company can also use the system to improve scheduling,
arrange for extra buses when needed, and make its operations more
efficient
  What we can learn…
  location-based e-commerce, a major part of mobile commerce
  EC services are provided to customers wherever they are
located
  exemplifies pervasive computing—services are seamlessly
blended into the environment without the user being aware of
the technology behind the scenes

M-Commerce
  Mobile commerce (m-commerce, m-business): Any e-
commerce done in a wireless environment, especially
via the Internet
  Mobile devices create an opportunity to deliver new services to
existing customers
  Examples
  Mobile financial applications
  Mobile advertising
  Mobile inventory management
  Proactive service management
  Product locating and shopping
  Mobile auction
  Mobile entertainment services
  Mobile office
  Mobile distance education
  Mobile music (on demand)

7
 11/17/08

M-Commerce
  Specific attributes of m-commerce
  Mobility
  Broad reach
  Benefits of value-added attributes
  Ubiquity
  Convenience
  Instant connectivity
  Personalization
  Localization of products and services

M-Commerce
  Drivers of m-commerce
  Widespread availability of devices
  No need for a PC
  The handset culture
  Vendors’ push
  Improvement of bandwidth
  What’s needed?
  Cellular (mobile) phones, PDAs, pagers, etc.
  Wireless network
  A Web server with wireless support and a WAP gateway
  Application or database server (e-commerce)
  GPS
  WAP

L-Commerce
  Location-based commerce (L-commerce): M-commerce
transactions targeted to individuals in specific locations,
at specific times
  L-commerce offers:
  Safety
  Convenience
  Productivity
  L-commerce basic services revolve around five key
areas:
1.  Location
2.  Navigation
3.  Tracking
4.  Mapping
5.  Timing

8
 11/17/08

L-Commerce

L-Commerce

L-Commerce
  Examples
  Automatic crash notification (ACN): Device that automatically
sends the police the location of a vehicle that has been
involved in a crash
  Telematics: The integration of computers and wireless
communications to improve information flow using the
principles of telemetry
  Barriers to l-commerce
  Accuracy
  The cost-benefit justification
  The bandwidth of GSM networks
  Invasion of privacy