MM1 Phone To MMSC Protocol - NowSMS · nowsms mmsc training: phone to mmsc protocol (mm1) november 2015 ©2015 nowwireless limited nowsms mmsc training: phone to …

NowSMSMMSCTraining:PhonetoMMSCProtocol(MM1)NOVEMBER2015©2015 NOW WIRE L ES S L IM I T ED

NOWSMSMMSCTRAINING:PHONETOMMSCPROTOCOL(MM1)– ©2015NOWWIRELESS 1

MMSProtocolsOverallArchitecture:3GPPTS23.140http://www.3gpp.orgOver-the-AirPhonetoMMSC:OpenMobileAlliance(OMA)– MMSEncapsulationProtocolhttp://www.openmobilealliance.orgExternalConnectivityProtocols:3GPPTS23.140◦MM4– Interoperator◦MM7– ValueAddedServiceProvider


MM1OverviewMM1istheover-the-airprotocolforMMSmessagetransmissionbetweenaphoneandthenetwork.DefinedbyOpenMobileAlliance(OMA)– MMSEncapsulationProtocolhttp://www.openmobilealliance.orgBasedonHTTP,WAPPushandMIMEtechnologies


MultimediaMessagingService(MMS)DesignedtocomplimentSMSbyprovidingsupportformultimediacontent◦ Text◦ Images◦ Video◦ Audio◦ ContactObjects◦ CalendarObjects◦ SMILPresentation(legacysupport)


MMSC(MMSCentre)Providesstore-and-forwardMMSMessagingServiceformobilephonesubscribers

TemporarilystoresMMSmessagesawaitingsubscriberretrieval

MayinterconnectwithMMSCsforothernetworkoperators,eitherwithdirectconnections,orviaanaggregator

MayconvertMMSmessagestootherformats(e.g.,SMSwithweblink)fornon-subscribersorexternalrecipients

MayallowMMSsubmissionsfromValueAddedServiceProviders

Mayapplycontentadaptationonmessagecontentbaseduponcapabilitiesofthereceivingdevice


MMSandGroupMessagingSupportsmultiplerecipientsandgroupconversationsThebiggestdriverofMMSmessagetrafficgrowthhasbeenitsuseinmodernsmartphonesforgroupmessagingEvenwhenthecontentistextonly,MMSispreferredforgroupmessagingbecauserecipientscanreplyall,allowingallgroupmemberstoseeallmessages.


MM1ProtocolDataUnits(PDUs)PDUsarethedataelementsthatareexchangedbetweenamobilephoneandtheMMSCPDUsareencodedusingtheMIMEtypeapplication/vnd.wap.mms-messagePDUsaretransferredasthepayloadofHTTPrequests,HTTPresponses,orWAPpushmessagesExample(HTTPPOST):POST / HTTP/1.1Content-Type: application/vnd.wap.mms-messageContent-Length: 99999


MM1PDUKindsTherearethreekindsofMM1PDUs:1. Request:Denotedastype-name.req2. Confirmation (Response):Denotedastype-name.conf3. Indication (notification):Denotedastype-name.ind (not

confirmed)


MM1PDUTransmissionWhentheclientneedstosendaPDU(RequestorIndication)totheMMSC,italwaysusesHTTPPOST.◦ IftheMMSCreceivesaRequestPDUviaHTTP,itgeneratesanappropriateConfirmationPDUintheHTTPresponse.

◦ IftheMMSCreceivesanIndicationPDUviaHTTP,itgeneratesanemptyHTTPOKresponse(statuscode200or204).

WhentheMMSCneedstosendaPDU(Indicationonly)toaclient,itonlyusesWAPPush.


WAP1.xClientConsiderationsOlderMMSclientsbasedupontheWAP1.xprotocolusetheWirelessSessionProtocol(WSP)insteadofHTTP.TheseclientsmustuseaWAPGatewaywhichconvertsbetweenWSPandHTTP.TheMM1interfaceattheMMSCisalwaysHTTPbased.


MM1PDUsTransaction PDUTypeName Originated By Transport

SendMessage m-send.req (.conf) Client HTTP POST

NewMessage ReceivedNotification m-notification.ind MMSC WAPPUSH

Acknowledge NewMessageReceivedNotification(optional)

m-notifyresp.ind Client HTTPPOST

RetrieveMessage HTTPGET/m-retrieve.conf Client HTTPGET

Acknowledge RetrieveMessageComplete(optional)

m-acknowledge.ind Client HTTPPOST

DeliveryReport m-delivery.ind MMSC WAPPUSH

Read ReportfromClient m-read-rec.ind Client HTTP POST

ReadReporttoClient m-read-orig.ind MMSC WAPPUSH

ForwardMessage m-forward.req (.conf) Client HTTPPOST


MMSMessageStructureAnMMSMessagehasasimilarstructuretoanSMTPE-MailMessageStructurebaseduponSMTPandMultipartInternetMailExtensions(MIME)◦ Envelope– Recipientsforin-transitmessageinstance.◦ Headers– Sender,DisplayedRecipients,Subject,otherattributes◦ Content– MIMEencodedmultipartcontent.Oneormoremultimediaobjects(text,image,video,etc.)


MMSEnvelopeRoutingAttributes(senderandrecipient)foraninstanceofanin-transitmessage.

Example:Amessageissenttomultiplerecipients,someofwhicharesubscribersofadifferentmobilenetwork.ThemessagemaybesplitbytheMMSCfordeliverytoanotherMMSC.TheMMSenvelopeforthemessageinstancesenttotheotherMMSCwillbeonlytheremoterecipients.TheenvelopelistofrecipientstellstheotherMMSCwhichrecipientstodeliverthemessageto.

TheMMSHeaderwillstillcontainalistofallrecipientstoprovidefullgroupmessagingsupport.

InMM4/SMTPthesearerepresentedbyMAILFROM:/RCPTTO:commands.


MMSHeadersSenderRecipients(To/CC/BCC)SubjectPriorityMessageClass(Personal,Advertisement)MessageType(canbedeliveryreportorreadreport)MessageID


MMSContentMultipart(MIME)objectcontainingoneormoreofthefollowing:◦ Text◦ Images◦ Video◦ Audio◦ ContactObjects◦ CalendarObjects◦ SMILPresentation(legacysupport)



MM1MessageEncodingNoMMSEnvelope:AllrecipientsareinMMSHeadersTheMMSEncapsulationProtocoldefinestheMIMEtypeapplication/vnd.wap.mms-message,whichconsistsofheadersandanoptionalcontentbody.MMSHeadersareencodedinabinaryformat,followingtheWAPSessionProtocol(WSP)◦ WSPdefinesasinglebytecodeforcommonheadernamesandvaluestoreducemessagesize

◦ X-MMS-Message-Type:m-retrieve.conf reducesfroma36characterstringtotwobytes:8C84


MM1MessageEncodingMMSContent isencodedasmultipartMIMEobject.Themultipartobjectis areencodedinabinaryformat,followingtheWAPSessionProtocol(WSP)◦ application/vnd.wap.multipart.related isusedinplaceofmultipart/related

◦ application/vnd.wap.multipart.mixed isusedinplaceofmultipart/mixed


MM1Transaction:Step1SenderactivatesdataconnectiontoMMSAPN

(APNsettingconfiguredinthephone)


MobileNetwork

WAPGWorHTTPProxy

MMSC

ICAP

SMSC

PushProxyGateway

Sender

Receiver

1

MM1Transaction:Step2GGSNsendsRADIUSaccountingmessagetonotifythenetworkaboutthedeviceIPassignment.

WAPGatewayorICAPservermaintainstableofactivedeviceIPaddresses.


MobileNetwork

WAPGWorHTTPProxy

MMSC

ICAP

SMSC

PushProxyGateway

Receiver

RADIUS

1

2

Sender

MM1Transaction:Step3SendingphonesubmitsanMM1m-send.req totheMMSC.(MMSCServerURLconfiguredinphone.)MMSCreceivesm-send.req inHTTPPOST

Phonemaysubmit:• WAP1/WSPPOSTvia

WAPGW• WAP2/HTTPPOSTvia

Proxy• HTTPPOSTdirectto

MMSC


MobileNetwork

WAPGWorHTTPProxy

MMSC

ICAP

SMSC

PushProxyGateway

Receiver

RADIUS

m-send.req

HTTPPOST

1

2

3

Sender

MM1Transaction:Step4MMSCmustidentifyandauthenticatesender

MM1doesnotdefinehowthisisdone

Twooptions:

• WAPGWorHTTPProxyinsertsX-MSISDNHTTPheader

• MMSCrequestsMSISDNusingICAP


MobileNetwork

WAPGWorHTTPProxy

MMSC

ICAP

SMSC

PushProxyGateway

Receiver

RADIUS

m-send.req

HTTPPOST

ICAP

1

2

3

4b

Sender

MM1Transaction:Step5TheMMSCacceptsandprocessesthecontentoftheMMSmessage.Iftoalocalrecipient,theMMSCstoresandmakesitavailableasadynamicallygeneratedURLlink.TheMMSCgeneratesanMMSnotificationmessage(m-notification.ind),whichissentviaWAPPushoverSMStotherecipient(s).ThisMMSnotificationmessagecontainsaURLpointertothedynamicallygeneratedMMScontent.


MobileNetwork

WAPGWorHTTPProxy

MMSC

ICAP

SMSC

PushProxyGateway

Receiver

RADIUS

m-send.req

HTTPPOST

ICAP

1

2

3

4b

Sender

MM1Transaction:Step5(continued)m-notification.ind WAPpushmaybesubmittedtoaPushProxyGatewayusingthePushAccessProtocol(PAP)

OritmaybeencodeddirectlytoSMSformatandsubmittedusingSMPP

SMSmessagegeneratedisusuallya2partlongmessage


MobileNetwork

WAPGWorHTTPProxy

MMSC

ICAP

SMSC

PushProxyGateway

Receiver

RADIUS

m-send.req

HTTPPOST

ICAP

1

2

3

4b

PAP

SMPP5

SMS

m-notification.ind

Sender

MM1Transaction:Step6TherecipientphoneactivatesdataconnectiontoMMSAPN.(APNsettingconfiguredinthephone)

TherecipientphoneperformsanHTTP(orWSP)GETtoretrievetheMMSmessagecontentURLfromtheMMSC.

TheHTTPresponseistheMMSmessageinanm-retrieve.conf PDU.


MobileNetwork

WAPGWorHTTPProxy

MMSC

ICAP

SMSC

PushProxyGateway

Receiver

HTTPGET

m-retrieve.conf

6

Sender

MM1Transaction:Step7Ifthesenderrequestedadeliveryreport,theMMSCgeneratesanMMSdeliveryreport(m-delivery.ind),whichissentviaWAPPushoverSMStotheoriginalsender.


MobileNetwork

WAPGWorHTTPProxy

MMSC

ICAP

SMSC

PushProxyGateway

Receiver

HTTPGET

m-retrieve.conf

PAP

SMPP7

m-delivery.ind

6SMS

Sender

MM1Transaction:Step8Ifthesenderrequestedareadreport,thereceivermaygenerateareport(m-read-rec.ind)whenthesubscriberreadsthemessage.(Thisisdependentonclientconfiguration.)

TheMMSCtranslatestheformatofthereadreport(m-read-orig.ind),whichissentviaWAPPushoverSMStotheoriginalsender.


MobileNetwork

WAPGWorHTTPProxy

MMSC

ICAP

SMSC

PushProxyGateway

Receiver

HTTPPOST

m-read-rec.ind

PAP

SMPP9

m-read-orig.ind

8SMS

Sender

MMSMO(Mobile-Originated)Flow1. SenderactivatesdataconnectiontoMMSAPN.(APNsettingconfiguredinthephone)

2. GGSNsendsRADIUSaccountingmessagetonotifythenetworkaboutthedeviceIPassignment.

3. SendingphonesubmitsanMM1m-send.req totheMMSC.(MMSCServerURLconfiguredinphone.)

4. MMSCmustidentifyandauthenticatesender(X-MSISDNheaderinsertedbyWAPGWorICAP)

5. TheMMSCacceptsandprocessesthecontentoftheMMSmessage.Iftoalocalrecipient,theMMSCstoresandmakesitavailableasadynamicallygeneratedURLlink.


MMSMT(Mobile-Terminated)Flow1. TheMMSCgeneratesanMMSnotificationmessage(m-notification.ind),whichissentvia

WAPPushtotherecipient(s).ThisMMSnotificationmessagecontainsaURLpointertothedynamicallygeneratedMMScontent.

2. TherecipientphoneactivatesdataconnectiontoMMSAPN.(APNsettingconfiguredinthephone)

3. TherecipientphoneperformsanHTTP(orWSP)GETtoretrievetheMMSmessagecontentURLfromtheMMSC.

4. Deliveryreportand/orreadreportactivitymayoccur


WhatisWAPPush?SMSsupportsaconceptofportnumberstoallowapplicationstoregistertoreceivemessagesthataresenttoaspecificportnumber.(WAPPushusesSMSportnumber2948)WAPPushmessagesarebinarymessagesthatcancontaindifferentbinarycontenttypes,oneofwhichisanMMSnotificationtype.WhenthisMMSnotificationmessageisreceived,thephoneroutesittotheMMSclientforprocessing.


AboutWAPPushWAPPushplaysakeyroleintheMMSdeliveryprocess.Bydefault,theNowSMSMMSCexpectstobeabletosendMMSNotificationviaitsbuilt-inWAPPushProxyGateway(PPG),whichdeliversMMSNotificationsusingWAPPushoverSMS.ForGSM/UMTS/WCDMAenvironments,NowSMSautomaticallygeneratesUDH(userdataheader)intheSMSmessages.ForCDMA/CDMA2000environments,theNowSMSSMPPimplementationsupportsWDPAdaptationsothatMMSnotificationmessagescanbedeliveredviaSMSusingtheWAPteleservice.Forotherenvironments,NowSMScanusethePushAccessProtocol(PAP)tosendMMSnotificationmessagesviaaseparateWAPPushProxyGateway(PPG).


MM1UserAuthenticationIssuesTheMM1ProtocoldoesnotdefinehowtheMMSCidentifiesandauthenticatesthesubscriberwhentheMMSclientonamobiledevicesendsorreceivesamessage.TheMMSCisexpectedtointerfacewithotheroperatornetworkcomponentstoidentifyandauthenticatethesubscriber.


HTTPHeaderEnrichmentMMSclientssendHTTPPOSTrequeststotheMMSCoverTCP/IP.AcceptedindustrypracticeistouseHTTPHeaderEnrichmentservicestoinsertadditionalHTTPheadersintotheserequeststoprovideuseridentificationandauthentication.Forexample,thesubscriberMSISDN,isfrequentlyinsertedintooneofthefollowingheaders:◦ X-MSISDN:

◦ msisdn:◦ X-MDN:◦ X-Device-MIN:


WhoperformsHTTPHeaderEnrichment?ThefirstIP-basedmobileoperatorserviceswerebasedonWAPtechnologies,whereaWAPGatewayactedasaproxyforallIP-basedservices.TheseWAPgatewaysoftenperformedHTTPHeaderEnrichmenttoallowIP-basedservicestoidentifysubscribers.TheusualprocessistoconfiguretheGGSNtosendRADIUSAccountingmessagestotheWAPGWeverytimeasubscriberconnectstoordisconnectsfromtheGGSN.TheWAPGWmaintainsatableofactiveconnectionsthatallowittomapIPaddressestodevicephonenumberforHTTPHeaderEnrichment.


HTTPHeaderEnrichmentwithoutaGWAsmobileusagehasgrown,gatewaysandproxieshavebecomenetworkbottlenecks.TheICAPprotocolallowsanHTTPbasedservicetorequestHTTPHeaderEnrichmentondemand,withoutforcingclientstointerfacethroughagatewayorproxy.TheNowSMSMMSCcanbeconfiguredtorequestHTTPHHEviaICAP,andNowWAP canbeconfiguredtoprovidethisICAPbasedservice.


Documents

MM1 Phone To MMSC Protocol - NowSMS · nowsms mmsc training: phone to mmsc protocol (mm1) november 2015 ©2015 nowwireless limited nowsms mmsc training: phone to …