advanced topics in telecommunications 1: nokia mobile internet technical architecture end-to-end...

Advanced Topics in Telecommunications 1:Nokia Mobile Internet Technical Architecture

End-to-End Solutions

Seminar 11


MITA vol. 2, p. 165-238

Copyright (C) 2003 Alexandrova, Eronen, Hakulinen, Hämäläinen, Kellokoski, Nurminen, Poikolainen

Nokia MITA



Overview

✶ Part 1:✶ Messaging✶ Instant Messaging✶ Presence✶ Wireless Village✶ Questions

✶ Part 2:✶ Multimedia Streaming✶ Content Downloading✶ Data Synchronization✶ Device Management✶ Machine-to-Machine✶ Questions



Messaging

MITA vol. 2, p. 165-182


Nokia MITA



Messaging Contents

✶ SMS and MMS:✶ Overview✶ Architecture✶ Message Content

✶ Value-Added Services in MMS✶ Comparison of SMS and MMS✶ Business Issues✶ References✶ Questions

SMS=Short Message Service, MMS=Multimedia Messaging Service



SMS – Overview

✶ SMS was an unforeseen success✶ Originally meant for pager-like functionality✶ Exploits unused signalling channel capacity

✶ This makes long messages impractical✶ Messages can be received and sent during calls✶ Supported by practically all handsets✶ The success of SMS wasn't a “built-in” property:

✶ Instead, it became successful because it fulfilled user's real needs, not artificial needs created for business models



SMS – Architecture

✶ SMSC is a key component✶ Store-and-forward✶ Incompatible SMSC-protocols

✶ CIMD, UCP/EMI, SMPP, OIS✶ Protocol converters between SMSCs were needed to ensure

interoperability✶ Anti-thesis of MITA ideals of openness

✶ Quaranteed delivery: delivery confirmation

SMSC=Short Message Service Center



SMS – Message Content

✶ Maximum length of 160 characters per message✶ Multiple messages can be “chained” together

✶ Smart Messaging, EMS✶ Binary messages are supported too:

✶ Ringtones, operator logos, etc. (Smart Messaging, EMS)✶ Well-suited for small messages with textual content

EMS=Enhanced Messaging Service



MMS – Overview

✶ MMS is hoped to equal the success of SMS✶ However, basic text will probably still be sent with SMS

✶ Very versatile message content:✶ Images, text, sound, videos, ...

✶ Can also be used as a “neutral” bearer, or “middleware” of complex content, e.g.:

✶ DRM-protected material✶ E-Mail (DNS-ENUM for addressing)

✶ Messages sent over GPRS, HSCSD, ...

DRM=Digital Rights Management, GPRS=General Packet Radio Service, HSCSD=High-Speed Circuit-Switched Data



MMS – Overview

✶ Network architecture uses extensively the standard Internet protocols, such as HTTP & SMTP

✶ Push and Pull messages, like in SMS✶ End-user usage:

✶ Like SMS, basically just write the message and send it✶ Easy to use, even though completely different technology

✶ User sees the message content as the biggest change when comparing to SMS

HTTP=Hypertext Transfer Protocol, SMTP=Simple Mail Transfer Protocol



MMS – Architecture 1

✶ MMSC (MMS Center)✶ MM-interfaces:

✶ MM3 (External legacy applications): SMTP/HTTP/fax/...✶ MM4 (MMSC interworking): SMTP✶ MM7 (Value-added services): proprietary/EAIF/HTTP/SOAP

✶ WAP gateway at MM1:✶ WAP WSP binary message encoding – more compact headers

✶ MMSC can interface with HLR (via MM5)✶ Enables location-based services

EAIF=External Application Interface, SOAP=Simple Object Access Protocol, WAP=Wireless Access Protocol, HLR=Home Location Register



MMS – Architecture 2

From ETSI TS 23.140 v6.3.0

VAS=Value-Added Services, UMS=Unified Messaging Service



MMS – Message Content

Optional presentation part Uses SMIL format

Content-Type header in content is directly mappable to the same MIME-header in SMTP messages

Maximum message size artificially limited to 100 kb

Interoperability between handsets Message structure:

From ETSI TS 23.140 v6.3.0

SMIL=Synchronized Multimedia Integration Language, MIME=Multipurpose Internet Mail Extensions



MMS – Value-Added Services

✶ Content transcoding✶ Provide content which is optimized for the handset

✶ Support for legacy devices✶ SMS with an URL delivered to the legacy device

✶ Permanent message storage✶ Keep your messages at the operator's server

✶ Voice messages delivered as MMS✶ Other services

URL=Uniform Resource Locator



SMS vs. MMS

SMS MMS

Bearer Signalling channel GPRS, HSCSD, ...

Message size 160 characters 100 kb (artificially limited)

Message content Text, binary Images, sound, text, videos, ...

Price (approximate, Sonera, including VAT)

0.12 e (to Sonera), 0.15 e (to other)

0.59 e = 4.9 x SMS or 3.9 x SMS

VAT=Value-Added Tax



Business Issues

✶ Charging must be done “right”✶ Fixed fee✶ User's must not pay for GPRS traffic or SMS notification

✶ Operators will try to ramp up MMS usage✶ Third party content✶ Support for legacy devices✶ Fixed fee per message✶ Phone bought from a store must be ready-to-use

✶ Device management



References

✶ ETSI TS 23.140 v6.3.0 (2003-09); MMS Functional Description. http://www.3gpp.org/ (Visited 1.11.2003)

ETSI=European Telecommunications Standards Institute, TS=Technical Specification



Messaging Questions

Exam✶ Differences of SMS and MMS?✶ Explain two MMS architecture components and their

purpose.

Philosophical✶ Will IP convergence and all-IP networks eat away these

specialized messaging schemes like SMS and MMS? Will there be a fallback to Internet-messaging such as e-mail, IRC, various IM tools, ...? Why? Why not?

IP=Internet Protocol, IRC=Internet Relay Chat, IM=Instant Messaging



Instant Messaging

MITA vol. 2, p. 183-196


Nokia MITA



IM Contents

✶ Overview✶ Technological factors✶ Success factors✶ Market potential✶ Revenue potential✶ Security issues✶ Mobile IM vs. desktop IM✶ References✶ Questions

IM=Instant Messaging



IM Overview

✶ A way of sending short and simple messages which are delivered to online users immediately

✶ Two technologies are combined:✶ IM✶ Presence

✶ Presence introduces the “see before you connect” idea✶ More about presence later

✶ IM services will always combine IM exchange and presence features



Mobile IM

✶ Access to IM services becomes ubiquitous✶ Users can access the service at any time

✶ In mobile domain presence is more than online/offline indicator

✶ Location, situation, state and mood of users✶ IM is not only about exchanging short messages

✶ Pictures, audio and video✶ Rich content offers new possibilities



Technological Factors

Mobile IM needs different enablers:

Presence GPRS, 3G, Packet data Messaging terminal &

dedicated client



Success Factors

✶ Mobile devices have large enough screens✶ Predictive text input✶ Mobile device is always with the user✶ Mobile device is becoming a personal trusted device✶ Transferred data amount is relatively small

✶ Does not need much bandwidth✶ Emerging business use of IM



Market Potential

✶ IM is popular in the PC-world✶ Number of registered users worldwide:

✶ MSN: > 100 M✶ AIM: > 195 M

✶ 1.6 billion instant messages sent daily✶ ICQ: 135 M

✶ ICQ is a brand of AOL, like AIM✶ Customer base is the keyword in Mobile IM

MSN=Microsoft Network, AIM=America Online Instant Messenger



Revenue Potentials

✶ Monthly fees✶ Mobile advertising

✶ Exploitation of presence (e.g. location)✶ Advanced messaging services

✶ Mobile payment with the assistance of IM✶ Presence subscription costs✶ Access fee to some group

✶ Data transfer costs



Security Issues

✶ Advanced presence awareness and related issues✶ Personal information stored in the network is not accessible

by others✶ Business use of IM corporates✶ High security level is essential



Mobile vs. Desktop

✶ Small screen and input methods slow down chatting

✶ Always online possibility✶ Costs of chatting

✶ Chatting is easier with a keyboard and a bigger screen

✶ Online only when sitting in front of a PC

✶ Free (sponsored) chatting



IM References

✶ International Engineering Consortium; Instant Messaging Tutorial. http://www.iec.org/online/tutorials/instant_msg/ (Visited 1.11.2003)

✶ AOL Instant Messenger. http://www.aim.com/ (Visited 1.11.2003)

✶ Yahoo! Messenger. http://messenger.yahoo.com/ (Visited 1.11.2003)

✶ ICQ. http://web.icq.com/ (Visited 1.11.2003)



IM Questions

Exam✶ What are the success factors in Mobile IM?✶ Why would desktop users start to use Mobile IM?✶ What technologies does Mobile IM need?✶ Why is presence so important in Mobile IM?



Presence

MITA vol. 2, p. 183-196


Nokia MITA



Presence Contents

✶ Overview✶ Mobile presence

✶ Mobile vs. Fixed presence✶ Presence layers✶ Possible architecture✶ Model for Mobile Presence✶ Mobile Presence enabled services

✶ Problems✶ References✶ Questions



Presence Overview 1

✶ Origins in fixed Internet

✶ Past✶ Online collaboration✶ Tools: talk, finger, .plan / .project✶ Visibility, reachability

✶ Today✶ ICQ, AIM, etc. have status, buddy lists✶ Availability for interaction in IM

✶ Future✶ Connected people/things? Everywhere, with everyone?✶ Mobile Presence?



Presence Overview 2

✶ Definition of presence✶ “Perception of a human being that some other human being

is close or nearby, mentally or physically.”✶ Transmitting presence information is a way of extending the

human senses✶ Technically: “Delivering notifications from a person's availability

and status to the recipient.”



Mobile Presence

✶ Enables a new communication paradigm✶ See before you connect

✶ Is omnipresent✶ Reflects the real user status✶ Will be one of the core enablers

✶ Enrich other services like call, messaging, IM



Mobile vs. Fixed Presence

✶ Independent service in its own right

✶ Richer information, “contextualized presence”

✶ Possibility to exploit location data

✶ Always online, close to the user

✶ Part of IM applications✶ Content: online/offline✶ “Buddy list application”✶ Tied to the desktop✶ Online only when

selected so



Presence Layers: Authorization



Possible Architecture

DB=Database, GW=Gateway, CSP=Client-Server Protocol, WTLS=Wireless Transport Layer Security



Model for Mobile Presence

Presentity Watcher



Mobile Presence Enabled Services

✶ Triggered conference call✶ Automatically established to a certain group of people✶ When everyone is available✶ When everyone are willing to receive a call

✶ Machine-to-Human over Presence✶ Status of your coffee maker✶ Alarm systems

✶ Information services✶ News, forecasts

✶ Location Presence✶ Notification when your friend comes nearby



Problems

✶ Security, authorization✶ How can I be sure of my privacy?✶ Who can see my presence?✶ Is the level of security enough for business use?

✶ Are users willing to pay?✶ Interoperability?



References

✶ VT 2003, 2G5565 Mobile Presence: Architectures, Protocols, and Applications. Course homepage. http://www.imit.kth.se/courses/2G1326/ (Visited 1.11.2003)

✶ Eurescom project P1204 Mobile Presence. Project overview. http://www.eurescom.de/message/messageSep2003/Contextualised_Mobile_Presence.asp (Visited 1.11.2003)



Questions

Exam✶ Why should users pay for Mobile Presence features? In the

Internet it used to be “free”?✶ SMS clearly addressed a user need. Is there a similar need

for users to maintain a continuous flow of real-time presence information?

✶ What is your opinion on the interoperability in Mobile Presence?



Wireless Village

The Mobile IMPS Initiative


IMPS=Instant Messaging and Presence

Nokia MITA



Wireless Village Contents

✶ Overview

✶ Services & Features

✶ Architecture

✶ Protocols

✶ Functional features

✶ Communication model

✶ Interoperability

✶ WV compliant products (December 2002)

✶ Characteristics of WV

✶ References

✶ QuestionsWV=Wireless Village



Wireless Village Overview

✶ Open industry initiative for mobile IMPS✶ Founded by Ericsson, Motorola and Nokia in April 2001✶ Consolidated into OMA in June 2002✶ Supported by mobile industry's major players✶ Aims to be The Solution for mobile IMPS

OMA=Open Mobile Alliance



WV Services & Features 1

✶ Application Service elements✶ Presence service element

✶ Presence information (client/user status attributes)✶ Contact lists (list of user IDs)✶ Authorization of presence attributes (proactive/reactive)✶ Delivery of presence values (subscribe, get, update)

✶ Instant messaging service element✶ Delivery (single/multiple user(s), group, contact-list. Push/Pull)✶ Offline messaging (store-and-forward)✶ Access control (grant, block)✶ Message content (plain unicode, MMS, EMS, vCard, vCal)




✶ Group service element✶ Group models (public, private)✶ Dynamic group features (join, leave, invite, search, notifications)✶ Static group features (create, delete, access control, properties)

✶ Shared Content service element✶ Invite mechanism for explicit content handling

✶ Service access point (SAP)✶ Access features

✶ Login/logout✶ Service and capability (delivery method, accepted content etc.)✶ Keep-alive✶ Get Service Provider info (name, logo, free text, URL)




✶ Common features✶ Search (users, groups)✶ Invite ( groups, presence information, content)

✶ Server interoperability features✶ Security✶ Transaction management✶ Session management✶ Service management✶ User profile management (IETF Internet-draft, CPIM)✶ Service relay – IMPS features



WV Architecture

CLI=Command Line Interface, CLP=Command Line Protocol,SMCNP=Server Mobile Core Network Protocol, SSP=Server-Server Protocol



WV Protocols

CPIM=Common Profile for IM, SIP=Session Initiation Protocol, WTP=Wireless Transaction Protocol, IPSec=IP Security Protocol, TCP=Transmission Control Protocol, UDP=User Datagram Protocol, WDP=Wireless Datagram Protocol



WV Functional Features



WV Communication Model

Separate data and signalling channels (w/o Keep Alive) Data channel bindings: WSP, HTTP, HTTPS and SMS. CIR channel bindings: WAP 1.2/2.0 Push (SMS, UDP/IP),

standalone UDP/TCP, standalone TCP/IP

CIR=Communication Initiation Request, HTTPS=Hypertext Transfer Protocol, Secure



WV Interoperability

✶ Interoperability testing events (3 events held so far)✶ Compliance statement from Wireless Village Interoperability

Committee (IOPCom)✶ Detailed compliance statement due to complexity of the

protocol



Compliant Products (Dec. 2002)

✶ Clients for several platforms:✶ J2ME, Symbian, PocketPC, Win32, proprietary environments

✶ Clients from:✶ Ecrio, Ericsson, Magic4, MIMT, Motorola, Nokia, OZ

Communications, Panasonic, Peramon, Sony Ericsson, WebMessenger

✶ Servers from:✶ Comverse, Critical Path, Ecrio, France Telecom, Followap,

Invertix, Logica, MessageVine, MIMT, Nokia, OpenWave, OZ Communications, Peramon, WebMessenger, Wiral



Characteristics of WV

✶ Complex protocol✶ Many open issues

✶ Achieving interoperability takes a lot of time✶ XML-based protocol should be a future-proof choice✶ Protocol is expandable

✶ On the other hand, this enables different implementations to NOT understand each other...



References

✶ OMA Wireless Village WWW-pages. http://www.openmobilealliance.org/WirelessVillage/ (Visited 1.11.2003)



Questions

Exam

✶ What is the Wireless Village initiative?

✶ How does it differ from existing IMPS solutions?

✶ Interoperability with existing systems?

✶ What kind of service elements and features does WV have?

Things to ponder before sleep

✶ Will Wireless Village be THE mobile IMPS solution?

✶ Coexistence of WV, SMS (EMS), MMS, and e-mail?



Multimedia Streaming

MITA vol. 2, p. 197-204


Nokia MITA



Multimedia Streaming Contents

✶ Overview✶ Elements✶ Protocols✶ Challenges



Overview

✶ Streaming is a pseudo-realtime consumption of multimedia content downloaded from a server

✶ The client can start displaying media as soon as enough data has been stored in a buffer

✶ This frees valuable device memory✶ Enables larger media files to be viewed✶ Enables support for live services

✶ Possible streaming applications:✶ News and information services✶ Entertainment✶ Communication and messaging



Elements

✶ Content creation tools, multimedia broadcast server, transmission network, media player in user's device



Protocols

✶ 3GPP streaming protocol is based on the IETF multimedia protocol stack

IETF=Internet Engineering Task Force, AMR=Adaptive Multirate, MPEG=Moving Pictures Expert Group, AAC=Advanced Audio Coding, RTP=Realtime Transfer Protocol, RTCP=Realtime Control Protocol, RTSP=Realtime Streaming Protocol, SDP=Session Description Protocol



Challenges

✶ Quality of service?✶ Edge Delivery Architecture – the carrier offers an additional node

in the distributed delivery network✶ Protection of content

✶ Digital Rights Management against saving, copying, altering, etc.✶ When the end-user is not trusted, and the end-user device is not

trusted, you can only semi-protect the content



Content Downloading

MITA vol. 2, p. 205-214


Nokia MITA



Content Downloading Contents

✶ Overview✶ Content Downloading in MITA✶ Discovery and promotion✶ Delivery and protection



Overview

✶ Delivery process has at least four elements:

✶ Source, Delivery, Discovery and Charging

✶ Promotion is more or less optional



Content Downloading in MITA

✶ Content-Type and memory requirements can be checked before download

✶ Successful downloads can be confirmed



Discovery and Promotion

✶ Discovery can be done in at least three different ways:✶ Send SMS to get desired content (pull)✶ Browsing with the mobile device✶ Internet browsing with the computer – content is delivered to the

mobile device using phone number✶ Promotion

✶ “Help consumers find content”✶ In practice, this means good old advertising + marketing✶ Combined promotion used to provide the best knowledge✶ New idea is to use individual marketing

✶ User resistance to personal spamming?



Delivery and Protection

✶ Basic elements of delivery:✶ Authentication (MSISDN, IMSI, username+password)

✶ Device recognition, if the device can inform about itself✶ Confirmation

✶ Important to both the user and the service provider✶ The user knows that only successfully provided content is charged✶ The service provider knows also about the unsuccessful

downloads✶ Charging, with pre-paid or post-paid

✶ Protection✶ DRM is needed✶ Must be easy to use and also give an adequate level of protection

MSISDN=Mobile Station International ISDN Number, IMSI=International Mobile Subscriber Identity, DRM=Digital Rights Management



Data Synchronization

MITA vol. 2, p. 215-219


Nokia MITA



Data Synchronization Contents

✶ Overview✶ Architecture✶ Example✶ Benefits



Data Synchronization Overview

MITA data synchronization tries to offer a complete solution for the synchronization of unknown devices

Key elements are SyncML and user-initiated synchronization

SyncML=Synchronization Markup Language, IrDa=Infrared Data



Data Synchronization Architecture

Client-Server based Server can also be a peer

Server synchronizes the database

Synchronization based on rules set by the user

SyncML is transport independent

Bearer can be HTTP, WSP, Object Exchange, TCP/IP, …



Data Synchronization Example

Example of one possible corporate usage Good points: synchronization is not limited to local

operation

POP3=Post Office Protocol v3, IMAP4=Internet Message Access Protocol v4



Data Synchronization Benefits

✶ Consumer✶ Sync with several devices and kinds of data

✶ Corporate✶ Information can be more easily shared and distributed

✶ Operators✶ Can provide the service relatively easily✶ No multiple server infrastructures

✶ Manufacturers✶ Common protocol and interoperability



Device Management

MITA vol. 2, p. 221-225


Nokia MITA



Device Management Contents

✶ Overview✶ Business drivers✶ Architecture✶ Future



Device Management Overview

✶ Device management is a generic term for technological tools used for in

✶ Remote parameter operations (browser settings)✶ Remote diagnostics and troubleshooting✶ Software operations (updates, installations)

✶ Done by 3rd party (carrier, service provider, corporate IT support) on behalf of end-users



Business Drivers

Correct settingsCorrect settings

From MITA vol. 2, p. 221

✶ Several business drivers exist for Device Management



✶ Architecture by WAP Forum✶ Bootstrapping

✶ Trusted relationship with management server, provisioning of key parameters, out-of-the-box functionality

✶ Continuous provisioning✶ Repetitive actions by trusted

management server, SyncML device management protocol is used

Device Management Architecture



Device Management Future

✶ Short-term: mobile devices will include more functional and richer applications

✶ Average consumer needs the correct operation “out-of-the-box”✶ Device Management can help

✶ Long term: mobile devices will become like PCs, needing updates and patches, this means gigantic amount of devices to be managed for corporations and carriers

✶ Device Management framework must have a realistic growth path to meet the demands of the future



Machine-to-Machine

MITA vol. 2, p. 227-238


Nokia MITA



M2M Contents

✶ Overview✶ Requirements✶ Technology✶ Business opportunities

M2M=Machine-to-Machine



M2M Overview

✶ For connecting people, devices and systems✶ Machine-to-machine, man-to-machine, machine-to-man

✶ In the mobile world, M2M is about combining wireless communication and information technology

✶ Typically used to collect information, set parameters and send indications

✶ Basically, to avoid physical visits or to provide real-time information



M2M Requirements

✶ Diverse requirements✶ M2M solutions vary from security and surveillance to vending

machines and cargo tracking✶ M2M applications may serve almost any business area and

physical environment✶ Applications must be reliable, upgradeable, and affordable



M2M Technology

✶ GSM is in most cases a suitable technology✶ Open, standardized, widespread✶ High number of different devices to fulfill varying needs✶ Already available✶ Evolution path to 3G business

✶ Several other network technologies✶ 802.11b/g, BlueTooth, Zigbee, RFID, UWB✶ These should also be considered when planning M2M solutions

RFID=Radio-Frequency Identification, UWB=Ultra Wide Band



M2M Business Opportunities

✶ M2M requires specific knowledge on several areas✶ Whole M2M chain is a joint effort of different specialists

✶ Corporate customers are users of M2M; they benefit from lesser manpower, shorter downtimes of systems, centralized updates, etc.

✶ Carriers and service providers offer network services, application development and system integration

✶ M2M solution providers “master the total M2M chain” and offer M2M-based solutions



References

✶ MITA vol. 2, p. 197-238✶ Nokia whitepapers.

http://www.nokia.fi/sijoittajat/raportit/whitepapers.html (Visited 1.11.2003)

✶ Multimedia Streaming✶ Data Synchronization



Questions

Exam✶ What is the difference between MITA content download and

“legacy Internet download”?✶ Data Synchronization benefits are quite clear to the end

user. How about operator and corporate, are they really benefitting from all this?

✶ What’s the main difference between SyncML based technologies’ Data Synchronization and Device Management?



That’s All, Folks

THANK YOU!

advanced topics in telecommunications 1: nokia mobile internet technical architecture end-to-end...

Documents