Messaging Intro UMTS MMS IMS

5/9/2018 Messaging Intro UMTS MMS IMS - slidepdf.com

http://slidepdf.com/reader/full/messaging-intro-umts-mms-ims 1/54

1

Messaging in GPRS / 3G networks:

Introduction to Multimedia messaging

Service (MMS), Wireless Application

Protocol (WAP) and IP MultimediaSubsystem (IMS)

© Jouko Kurki, 4.4.2005



2

Development of messaging (1)

Short Message Service (SMS):

q Started year 1992

q Published commercially 1996

q Messages transmitted using

SS7 signaling channelsq Limited size on properties of the

message

q Cheap and easy way tocommunicate -> very popular



3


Enhanced Messaging Service (EMS):

q Follower of SMS

q Works is the same infrastructure

as SMS -> cheap investment to

operatorsq Mode developed messaging

properties

l Simple pixel pictures

l Simple melodies

l Possible to modify message

propertiesl Animations



4


Multimedia Messaging Service (MMS):

q Latest step in mobile messagingevolution

q Messaging possibilities: Text,audio, pictures, video and anycombination of these

q Expected to become the mostpopular way of messaging

q Messages use same trafficchannels as speech

q Nearly unlimited messagingproperties

q

Brings new network elements tomobile networks



5

Service capabilities in versions of UMTS standards



6

UMTS Quality service classes and differentiation

• Background, no QoS priorities

• Interactive, QoS Priorities, e.g. web browsing• Streaming QoS, e.g. video streaming

• Conversational QoS, e.g. VoIP



7

UMTS QoS classes

Mapping QoS classes to UMTS channels

Protocols for services



8

Some UMTS services



9

Video sharing

Real time video sharing



10

Push to talk over Cellular (PoC) service

Features:



11

VoIP & streaming



12

Scope of Rec. H.264 for video telephony



13

Multimedia Messaging Service (MMS)



14

Multimedia Messaging Service architecture

MMS User Agent = MMS enabled mobile terminal

Foreign MMS Relay/Server = e.g. another operator’s MMS Center

MM1 – MM7 = standardized interfaces between the MMS network elements

MMS User

DatabasesHLR

MMS User

Agent A

Foreign MMSRelay/Server

MMS User

Agent B

ExteralServer #1

(e.g. e-mail)

ExteralServer #2

(e.g. Fax)

ExtrernalServer #N

(e.g. UMS)

MMS VAS

Applications

MMS Center (MMS-C)

Relay Server

MM5

MM1

MM7

MM6

MM3

MM1

MM4

(UMS = UnifiedMessagingSystem)

(VAS = ValueAdded Services)



15

Multimedia Messaging Service Center

The ”Heart” of the Multimedia Messaging Service is Multimedia

Messaging Service Center (MMS-C)q MMS system is composed of many nodes that perform specific

tasks:

q MMS-C offers:

l Support to various interfaces of the network

l

Message storage servicesl Charging information

l Subscriber information

l Generally: MMS-C enables transmission, transport and

reception of messages in mobile networks



16

MMS Network Architecture and interfaces

MMS Client

External Message

Application Servers2GMobileNetworkA

MMSE

Message Storage

3GMobileNetworkA

MMS Client

RoamingMMS Client

MobileNetworkB

External VASapplications

MMS Server

MMS Relay

User DBSubscription

ProfilesMMSC

IP networkMM1

MM1

MM3

MM1

MMS Client

MM6

MM7



17

Service Architecture

MMS clients in mobile terminals: originator, recipientMMS Environment (MMSE):

q All necessary service elements for MM delivery, storage and noti ficationq MMSE can be based 2G and 3G networks

Multimedia Messaging Service Centre (MMSC) is composed of MMS re lay andMMS server

MMSE interfaces:MM1 interface between MMS Relay and MMS client

MM2 interface between MMS server and MMS Relay (MMSC internal)

MM3 interface between MMSC and external serversMM4 interface between MMSCs

MM5 interface between MMSC and external network elements (HLR, DNS)

MM6 not standardized

MM7 interface between MMSC and external Value Added Service (VAS) a pplications

MM8 interface enables interactions between MMSC and billing system

MMS uses WAP as the bearer technology. MMS network is built on top of WAP

architecture.WAP GW provides HTTP, push services, over-the-air (OTA) security and terminal

capability negotiations



18

MMS architecture details

2G or 3Gnetwork

Internet

InternetRemote

2G or 3Gnetwork



19

Wireless Application Protocol (WAP)

MMS can use WAP protocols to provide multimedia services. WAP is intended to workas a platform to run applications over various wireless environments. Main ideas are:

• Interoperability• Scalability

• Efficiency• Reliability• Security

WAP technology provides an application model close to World Wide WEB model (knowas web model). In web model contents is presented using standard ized descriptionformats. Also the web browsers used to retrieve content use stan dardized transport

protocols. Following are key elements of web model:

Standard naming model. Objects available on the web are identified by UniformResource Identifiers (URI)

Content type: Objects in the web are typed. Thus web browsers ca n correctly identifythe type to which the content belongs

Standard content format. Browsers support standard content forma ts, e.g. HyperTextMarkup Language (HTML)

Standard protocols: Browsers support standard content retrieval protocols, e.g.HyperText Transfer Protocol (HTTP).



20

WAP features

WAP ideology is based on WEB model of accessing services, but to cope with

requirements of mobile environment it add following features:



21

Generic WAP architecture

Wireless

NetworkInternet

SecureNetwork



22

WAP 1.x Legacy configuration

WAE (Wireless

Application Environment)

WSP (Wireless SessionProtocol)

WTP (WirelessTransaction Protocol)

WTLS (Wireless TransportLayers Security)

WDP (Wireless DataProtocol).



23

WAP protocol stack

• WAE (Wireless Application Environment): General purpose application

environment to build wireless applications.• WSP (Wireless Session Protocol): provides features as in HTTP, e .g.

requests and corresponding responses. Also supports long lived session

and suspend / resume sessions.

• WTP (Wireless Transaction Protocol) lightweight transaction oriented

protocol. Provides reliability to underlying datagram services by providingacknowledgement and retransmission (corresponds to TCP in the In ternet

protocol stack). WTP has no explicit connection set-up or release. WTP ismessage oriented and suitable to e.g. browsing Segmentation and

reassembly (SAR) can be supported.

• WTLS (Wireless Transport Layers Security). WTLS is optional and provides

secure transport service.

• WDP (Wireless Data Protocol). A general datagram service using

underlying wireless bearer services. WDP offers service equivalent to UDP

(Internet User Datagram Protocol)



24

WAP 1.x configuration for MMS



25

Wireless Access Protocol (WAP) Architecture for MMS

GSM/GPRS networkWAP Gateway

Internet,CorporateIntranet

WAPTerminals

Contentadaptation

TCP/IP &WAP protocolstack

Protocolconversions

Identification

Push Proxy

WEB Server

Network serversincl. MMSC

Application Servers

SMSC

Wireless profiled HTTP/TCP/IP

WAP 1.x

HTTP/ TCP/IP

WAP Push



26

WAP 2.0 Implementation of MMS

IP

WP-HTTPor HTTP

IP

TCP

IP

TCP

HTTP

IP

TCP

IP

TCP

MM TransferProtocol B

MMS Client MMS Relay MMS Server

MMS

Comm

Messaging Protocol A Payload

HTTP

MMSApp Svcs

MMSUI

MM TransferProtocol B

MM ProtocolB

Messaging Application Framework

Messages

MMSApp Model

MM Data

WAP Gateway

Wired Wired WiredWirelessBearer WiredWirelessBearer

IP

TCP orWP-TCP

TCP orWP-TCP

WP-HTTP = Wireless profiled HTTP



27

WAP Implementation of MMS

WAP transport protocols are used for MMS:

q

Multimedia message (MM) sending over WAP Wireless Session Protocol, WSP(WAP 1.x) or WP-HTTP (WAP 2.0)

q WAP browser is not involved in MMS

MMS Client traffic to MMS Relay: Client is sending message over WSP or WP-HTTP to

WAP Gateway and then over HTTP from the WAP Gateway to the MMS Relay.

HTTP POST method is used for message sending, WAP Push protocols and for data

originating at the MMS Relay.

WAP Gateway provides standard WAP services needed to implement M MS, theseinclude:

q Translation of requests from the WAP protocol stack (WSP) to the WWW

protocol stack (HTTP) for communication with the MMS Relay.

q PUSH services used by the MMS Relay to provide MMS notification and MMS

delivery reports to the MMS User Agent.

q

OTA security with WTLS (Wireless Transport Layer Security) with WAP 1.xq OTA security with TLS (Transport Layer Security) with WAP 2.0

q Capability Negotiations (UAProf). WAP GW inform the MMSC of the

capabilities and preferences of the MMS User Agent.



28

MMS Message sending, notification and retrieval

1 Message submission 2 Message notification

3 Message retrieval4 Delivery report

5 Read report

6 Read report

OriginatorMM1

Recipient

MM1

OriginatorMMS client

MMSCRecipient

MMS client



29

MMS Message Sending

The user composes the multimedia message with MMS capable deviceThe user defines the MM recipients

Originator MMS client transfers the MM to the MMSC of the user ’s MMSEMMS Client traffic to MMS Relay: Client is sending message over WSP or WP-

HTTP to WAP Gateway and then over HTTP from the WAP Gateway to t heMMS Relay.

(WSP/)HTTP POST method is used for data originating from the MMS ClientOriginating MMSC performs the checking of message format, suffic ient

prepaid credit, possible barring conditions

If message submission is accepted, the originator MMSC transfers the MM tothe recipient MMSC(s).Every message has a validity period defined by user or originati ng MMSC

Message sending can also include:q Request to store the message on the network (“album service”)

q Hidden originator address

q Charging indication

q Delivery timeq Report request (delivery and read)



30

MMS Message notification and retrieval

MMSC PUSH is implemented by using the notification-pull method.

The delivery of MM from MMSC to MMS Client is two-phased:

MM notification is delivered to the user agent

q MMS server uses PUSH technology to provide MMS notification and MMS

delivery reports to the MMS Client with WAP Push (non -confirmed

connectionless push technique)

q Push data does not contain the message itself, but reference (UR I) to it.

q Notification sending shall apply sufficient authentication and security.

q SMS/ WAP push is used as the bearer for the notification.

When the terminal receives the notification, it automatically retrieves themultimedia message, based on its capabilities (deferred retrieval)

q Notification is used to alert a MMS client that a new message has arrived at the

MMSC.

q MMS client will open a session to the relevant MMSC and retrieve (PULL) the

MM from the MMSC over WSP.q In this retrieval, the HTTP GET method is invoked in the MMS ser ver over a

connection-oriented WAP session.



31

Multimedia Message Box

q Multimedia Message Box (MMBox) is the area in which MMS userscan store messages to free up the memory on their MMS terminals,and keep their messages long-term.

q MMBox (“Multimedia Album”) can be accessed either via a Webinterface or a WAP interface.

q Users can compose and send MM using Album service, browseexisting stored messages, retrieve a previously stored messages

from the Album onto the MMS terminal and forward a retrievedmessage to either an email address or another phone (MSISDNaddress).

q User can delete MMS from Multimedia Album using either WAP or

Web interface.

q Multimedia Albums for legacy users is a part of legacy terminal

support.



32

Multimedia Message

MM Header includes:

q Address of the originator

q Address of the recipient(s)

q Priority

q Class

q Date and time

q Validity period

q Reply charging parameters

q Request for reports

q Message subject

q Sender visibility

q Earliest delivery time

q Message distribution indicator

q MMBox status

MMS content: text, image, audio and video clip

MMS content is encapsulated in a body part container:

q the only mandatory parameter Content type



33

Multimedia Message

q MMS terminal can support several media types, each requiring a

specific format and respective codec:q standard image formats such as GIF and JPEG,

q video formats such as MPEG 4

q audio formats such as MP3 and MIDI.

q MMS speech codecs: AMR (Adaptive Multirate Codec) in use, 13-K(OMA)

q Full interoperability guaranteed for Core MM Content Domain: text,image basic, image rich, video basic and video rich content classes

q Standard MM Content Domain includes MMs content compliant withMMS standards but content classes are left for vendors’

implementations: e.g. animation basic, animation rich and music

basic content classesq Unclassified MM content domain gives full freedom to create

multimedia messages

MMS I l i i GPRS k



34

MMS Implementation in GPRS network

q Multimedia messaging requires high transmission speeds,which can be provided by GPRS and 3G.

q MMS is the key business case driver for GPRS (GeneralPacket Radio Service) and is also the central driver of the 3Gbusiness case

q Specific GPRS Access Point shall be used for MMSCconnection and for other WAP services (support for phones

with one PDP context)q GPRS roaming is required for MMS interoperability between

operators (IREG IR.34 Specification by InternationalRoaming Expert Group)



35

IP Multimedia Subsystem (IMS)

IP M lti di S b t (IMS) O i



36

IP Multimedia Subsystem (IMS) Overview

IMS architecture is a standardized access independent IP basedarchitecture.

IMS architecture makes it possible to establish peer-to-peer IPcommunications between all types of clients in 2G / 3G networksas defined in the 3GPP release 5 specifications.

IMS architecture (3GPP rel5) includes:q Network entities and reference points

q Signaling: routing principles, registration, session management,signaling compression

q Security: IMS AKA (authentication and key agreement), integrityprotection of signaling messages, network domain security

q Quality of service: policy control between IMS and GPRS network

q Service provisioning

IMS architecture (3GPP rel6) additions:q Interworking with CS, WLAN and other IP networks

q

Group management and conferencingq Presence, messaging

q Local services

IP M lti di C



37

Service plane

SIP Service Creation and Management,Presence and other application servers

IP Multimedia Core – 3GPP Rel5

Gateway plane

Control plane

PSTN

MSC

ISN

ADM/TM

Internet

IP MultimediaCore

3G

MSC

2GSGSN

3GSGSN

MGW

GSM/EDGE/WCDMA

SDH/PDH/DWDM

QoS-awareIP backbone

MSCor

MSCServer

CPSCPS

3GPP HSS

HLR IMRIMR IMR = IP MultimediaRegister

CPS = ConnectionProcessing

Server

IP Multimedia Subsystem Network Configuration



38

IP Multimedia Subsystem, Network Configuration

Internet

HLR OSSProvisioning Charging&Billing

ISC/SIP

Rf, Ro

Cx

Go

FWNAT

CPSCPSIMRIMRSIP

GGSN

WLANCableDSL

WLANCableDSL

GSM/EDGEWCDMA

GSM/EDGEWCDMA PSTN

DSLAM/

ER

SIP-EnabledTerminals

SIP-EnabledTerminals

IP Transport

MGW

MSC

Server

MSC

Server

ApplicationServers e.g:PoCPresenceMessaging GW

Push ServerGroup Server

Application

Servers

Application

Servers

IMR = IP MultimediaRegister

CPS = Connection

ProcessingServer

IP Multimedia Subsystem (IMS) Principles



39

IP Multimedia Subsystem (IMS) Principles

q Supporting user and terminal mobility.

q Enables establishing IP connections between terminals using the

SIP (Session Initiation Protocol).

q Targeted for handling of voice calls and multimedia sessions in

packet based mobile networks.

q Access independent: the access network can be 2G GPRS

(GSM), 3G GPRS (WCDMA, EDGE), WLAN or wireline IPnetwork.

q Flexible service creation platform, application servers can beconnected to the IMS through ISC interface.

q User and control plane are separated in IMS: SIP signaling is

routed via IMS, the multimedia user data during session in adifferent route over IP network.

IMS Network Elements: CPS



40

IMS Network Elements: CPS

q Connection processing server (CPS) for multimedia sessioncontrol is using SIP (session initiation protocol)

q CPS includes the connection processing engine(CPE) thatimplements call state control functions (CSCFs):

q Policy decision function (PDF) interacts with GPRS network(QoS, charging correlation, PDP context reservation)

IMS Network Elements: IMR



41

IMS Network Elements: IMR

q IP Multimedia Register(IMR) consists of UMS and SLFfunctionalities

q Home subscriber server (HSS) functionality as defined in 3GPPRel.5 includes the existing home location register (HLR) and UserMobility Server (UMS)

q UMS is the main subscriber and service data storage of IMS:identification data, registration status and services provided

q User Mobility Server (UMS) of IMR stores the user identities:

q Private user identity used for registration and authentication

q Public user identity used for communication requests

q UMS handles also location management parameters, roamingauthorization and S-CSCF selection

q Subscription Locator Function (SLF) is gives the HSS address ofthe subscriber to the I-CSCF

q Cx interface between CPS and UMS supports the transfer ofservice parameters of the subscriber from UMS to CSCF

IMS Functional Elements



42

IMS Functional Elements

q Call State Control Function (CSCF)

q Home Subscriber Server (HSS): HLR+UMS+SLF

q Media Gateway Control Function (MGCF)

q Media Gateway Function (MGW)

q Multimedia Resource Function (MRF)

q MSC Server

q Gateway MSC Server

Session Initiation Protocol (SIP)



43

Session Initiation Protocol (SIP)

q SIP as a protocol is standardized by the IETF (InternetEngineering Task Force), while 3GPP is standardizing the way

SIP is used in mobile networks.

q SIP is the signaling protocol for IP Multimedia sessions.

q SIP supports multiparty multimedia sessions.

q SIP supports IMS based multimedia messaging.

q SIP user agents in terminals.

q SIP session is established between SIP user agents.

q User and control plane are separated in IMS: SIP signaling isrouted via IMS, the multimedia user data during session in adifferent route over IP network.

SIP Session Establishment CSCF Functionalities



44

SIP Session Establishment, CSCF Functionalities

I-CSCF

S-CSCF

Home of B subscriber

HSS

Home of A subscriber

HSS

Number analysis

and Service Control

P-CSCF

Terminating Network

P-CSCF

Originating Network

S-CSCF

INVITE

INVITE

I N VI T E

INVITE

I N VI T E

I N VI T E

HSS Query

Service Control

SIP session establishment and ending



45

CPSINVITE

100 Trying INVITE

183 Session Progress

200 OK

200 OK

183 Session ProgressPRACK

PRACK

UPDATEUPDATE200 OK

200 OK

200 OK200 OK

180 Ringing180 RingingPRACK

PRACK

200 OK

200 OK

ACK ACK

SIP session establishment and ending,

3GPP

SIP session establishment and ending



46

CPS

INVITE

100 Trying

INVITE

180 Ringing180 Ringing

200 OK200 OK

BYE BYE

200 OK200 OK

ACK ACK ……

SIP session establishment and ending,

RFC 3261 (IETF)

IMS Service Categories



47

g

Person-to-person Interactive applications

q Tools and means for new kind of interactivity between users, such as

Interactive Games, Content Sharing, Real Time Video Sharing

q Mobile clients and PC clients will interconnect!

Application server supported applicationsq Added value and control in the network (e.g. PoC, Presence,

Conferencing, Messaging)

Session control servicesq

supplementary services to IMS users regardless of terminal andapplication in use

IMS Domain

CPSIMR

PoC

SIP

SIP

Generic SIP AppSe

Presence Server

IMGW, MMSC …

Content Sharing



48

Browse content in your friends’ phone

Direct file sharing between terminals

Can be used to transfer files between users or laterbetween group of users

Sharing also between PC & mobile

Real Time Video Sharing



49

Share the moment instantly in real-time, ‘See What I See’

Enables spontaneous behaviorShare the camera view or video clip whilst in an ongoing sessionUnidirectional mobile video streaming between peer usersEnables convergence with SIP PC clients

Ideal service for WCDMA and EDGE (DTM) networks

InviteInvite

Video& audio streamVideo& audio stream

AA BBOngoing sessionOngoing session

Voice Instant Messaging



50

Instant messaging with audio content

Voice messages created in terminal and sent via IMS to recipients as SIP

MESSAGE

Instant Messaging Gateway (IMGW) to provide Store & Forward func tionality

q Store messages if the recipient is unavailable at the moment

q Forward messages via MMSC to non-IMS subscribers

Can be easily implemented with IMS in any packet network (e.g. GPRS)

Enables convergence with PC clients



51

Example of IM Store&Forward delivery

B UEB UECPSCPSA UEA UE IMGWIMGW

1. User sends a voicemessage

2. MESSAGE

2. CPS determines user is notregistered and sends themessage to the S&F with theS&F indication

4. MESSAGE

6. 202 Accepted

7. IMS Registration

9. 200 OK

Event PA = Event Publication Agent

8. MESSAGE

5. MESSAGE (repeated periodically)

3. User B becomesavailable whenregistering

presence info canbe used as trigger

for resending

SIP Game Examples



52

SIP Game Examples

MAD MAC SIP

MM is a 3D two-player online action/strategy game. Each player will control a t eam of animated robots

battling each other using cannons, missiles, rockets, etc. After full release, new battle fields, weapons,characters, etc. can be downloaded from the carriers ’ platforms. Players with new updates can pass

them to friends via SIP.

TREASURES SIP

Treasures SIP is a 2D two -player turn based board game. The rules are similar to Minefield : twoplayers face a grid map with hidden treasures. At the beginning, the entire grid is covered. Two

players choose to dig at a grid turn by turn. When digging, a gr id will show either a treasure ortreasure grid number near this grid. When the map is entirely uncovered, the player who findsthe most treasures win.

Genre: Action/Strategy

Memory space: <800Kb

Runtime memory: <3.5M

Genre: Board Game

Memory space: <400Kb

Runtime memory: <2.5M



53

Content PushNews Service Use Case

Person A downloads the Content Pushapplication

Downloading via Web or WAP

Person A opens the Content Push

application

Person A selects from the menu “Update

content catalog” or updated

automatically

Person A selects the wanted content

and defines the parameters for

content delivery -> delivery activated

Person A gets a notification when new

content available

Person A checks the new content

Person A sees a news item thatinterests her and clicks it to read

more

3G mobile terminal (an example of SIP client)



54

3G mobile terminal (an example of SIP client)

q 3G speed with series 60 built on the Symbian OS

q WCDMA: maximum download 384kbps, upload 128kbpsq EGPRS (class B, Multislot class 10) - maximum download 236.8kbps,

upload 118.4kbps

q 1.3 megapixel camera sensor, effective resolution 1.23 megapixels forimage capture (1280 x 960 pixel resolution)

q 6x smooth digital zoom and sequence modeq 10 MB internal dynamic memory with hot swap and 64 MB reduced size

MultiMediaCard (MMC)

q Multimedia messaging: combine image, video, text and voice clip andsend as MMS to a compatible phone or PC

q Video recording time up to 1 hour per clip

q WAP 2.0 XHTML/HTML multimode browserq Via Bluetooth: images, video clips, graphics and business cards

q Downloadable java™ MIDP 2.0, CLDC 1.1 applications

q 3d API (JSR-184)q Dual stack ipv4/ipv6

q SIP stackq SIP application SW

Documents

Messaging Intro UMTS MMS IMS