mms protocol overview - nowsms protocol overview november 2015 ©2015 nowwireless limited ... •...

MMSOverviewMMSArchitectureOverviewMMSDeliveryProcessIntegrationWithOtherNetworkComponents◦ SMS- SMPP◦UserAuthentication- WAPGW/RADIUS/ICAP◦ Accounting&Charging- HTTP/DIAMETER◦MNP&MessageRouting


MMSC(MMSCentre)Providesstore-and-forwardMMSMessagingServiceformobilephonesubscribers

TemporarilystoresMMSmessagesawaitingsubscriberretrieval

MayinterconnectwithMMSCsforothernetworkoperators,eitherwithdirectconnections,orviaanaggregator

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

MayallowMMSsubmissionsfromValueAddedServiceProviders

Mayapplycontentadaptationonmessagecontentbaseduponcapabilitiesofthereceivingdevice


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


MMSandGroupMessagingSupportsmultiplerecipientsandgroupconversationsThebiggestdriverofMMSmessagetrafficgrowthhasbeenitsuseinmodernsmartphonesforgroupmessagingEvenwhenthecontentistextonly,MMSispreferredforgroupmessagingbecauserecipientscanreplyall,allowingallgroupmemberstoseeallmessages.


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)


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


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


MMSProtocols• MM1thruMM11

• Someprotocolsarefullydefined(MM1,MM4,MM7)

• Otherprotocolsarelooselydefined,conceptual,andimplementationdependent

• Definedby3GPPTS23.140


/MM9

MM1• Interfacebetweenmobile

stationandMMSC

• BasedonHTTP,WAPPushandMIME

• MMScontentencodedasMIMEpayloadusingWAP/WSPbinaryencoding

• DefinedbyOpenMobileAlliance(OMA)– MMSEncapsulationProtocol


/MM9

MM2• Conceptualinterface

betweentwointernalelementsofanMMSC

• NoactualAPIorprotocoldefined

• MMSRelayprovidesclientinterfaces

• MMSServerprovidesstorageservices

• CommercialMMSCimplementationscombinefunctions


/MM9


betweenMMSCandexternalserverssuchasE-Mail,FAXandVoiceMail

• NoactualAPIorprotocoldefined– useofSMTPsuggested


/MM9

MM4• Interfacebetween

multipleMMSCs

• SMTPbasedprotocoldefinedby3GPPTS23.040

• AdditionalX-MMSSMTPheadersdefined

• DifferentPDUsmappedtoSMTPheaders


/MM9


betweenMMSCandHLRformessageroutinglookup


• HLRlookupdoesnotprovideroutinginfoforsubscriberMMSC

• NowSMSMMSCusesHTTP-basedroutingcallbacks


/MM9


MMSCandsubscriberdatabase


• NowSMSMMSCusesHTTP-basedaccountingcallbacks


/MM9

MM7• InterfacebetweenMMSC

andValueAddedServiceProvider(VASP)applications.

• SOAP/XML/HTTPbasedprotocoldefinedby3GPPTS23.040

• MMScontentencodedasMIMEpayload

• Bi-directionalHTTPPOST– MMSCandVASPcanbothinitiateconnections


/MM9

MM8&MM9• InterfacebetweenMMSC

andbilling/chargingsystems

• Billinggenerallyreferstopost-paidCDRgeneration

• Charginggenerallyreferstorealtimechargingrequiredbypre-paid

• NowSMSMMSCsupportsHTTPbasedaccountingcallbackswhichsomecustomersusetogenerateCDRs

• NowSMSMMSCsupportsDIAMETERCreditControlorBaseAccounting


/MM9

MM10• Interfaceformessage

servicecontrolandfiltering

• Relativelynew,noknowncommercialimplementations

• DIAMETERbasedprotocol

• NotimplementedbyNowSMSMMSC


/MM9


betweenMMSCandexternaltranscoder


/MM9

KeyProtocols• MM1– Phone<->MMSC

• HTTPPOST• BinaryWSPMIME• WAPPush

• MM4– MMSC<->MMSC• SMTP/MIME

• MM7– VASP<->MMSC• HTTPPOST• SOAP/XMLRequest• MIMEMMSContent

• MM9– Accounting/Billing/Charging• HTTPCallbacks• DIAMETER


/MM9

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


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.)


REVIEW

MMSEnvelopeRoutingAttributes(senderandrecipient)foraninstanceofanin-transitmessage.

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

TheMMSHeaderwillstillcontainalistofallrecipientstoprovidefullgroupmessagingsupport.

InMM4/SMTPthesearerepresentedbyMAILFROM:/RCPTTO:commands.


REVIEW

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


REVIEW

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


REVIEW


REVIEW

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.


MM4– MMSCInterconnectTheMM4protocolisusedtointerconnectMMSCs.• SMTPbasedprotocoldefinedby3GPPTS23.040• AdditionalX-MMSSMTPheadersaredefined• DifferentPDUsaremappedtoSMTPheadersWhenasubscribersendsanMMSmessagetoasubscriberonadifferentnetwork,theMM4protocolisusedtotransferthemessagebetweenMMSCs


MM4– MMSCInterconnectMM4connectionscanexistdirectlybetweenmobileoperators.FrequentlyasingleMM4connectiontoaninterconnectproviderisused.MM4isnotusedforroaming,onlyforinterconnect.


MM4MessageEncodingTheMMSEnvelopecontainsRoutingAttributes(senderandrecipient)foraninstanceofanin-transitmessage.InMM4,thisenvelopeisrepresentedbythestandardSMTPMAILFROM:andRCPTTO:commands.

TheMMSHeadersarerepresentedasSMTPHeaders,withMMSspecificheadersprefixedbyX-MMS- (e.g.,X-MMS-Message-Type:).Theseheadersaredefinedin3GPPTS23.140.

TheMMSContent isencodedasastandardSMTPMIMEmultipartobject.Notethatevenifthereisonlyasinglecontentobject(e.g.,imageonly),manyimplementationsstillexpectaMIMEmultipartwithonly1part.


SampleMM4TransactionSMTPAUTHisoptionalandrarelyused


SampleMM4Message


MM4PDUKindsTherearetwokindsofMM4PDUs:1. Request:DenotedasMM4_type-name.REQ2. Response:DenotedasMM4_type-name.RES

(OftenreferredtoasACKsoracknowledgments)


MM4PDUTransmissionMM4PDUsaresentusingSMTP.BecausetheSMTPprotocolisuni-directionalandcontainslimitedstatusreportcapability,requestsandtheirassociatedresponsecanneverbetransmittedoverthesameconnection,WhenanMMSChasarequesttotransmittoanotherMMSCoverMM4,itinitiatesanSMTPconnectiontothatMMSCtotransfertherequestPDU.ThereceivingMMSCmusttheninitiateanSMTPconnectionbacktotherequestingMMSCtotransfertheresponsePDU.


MM4PDUsTransaction PDUTypeName

SendMessage MM4_forward.REQ

MM4_forward.RES

DeliveryReport MM4_delivery_report.REQ

MM4_delivery_report.RES

ReadReport MM4_read_reply_report.REQ

MM4_read_reply_report.RES


MM4Transaction:SimplifiedStep1

StandardMM1MMSMOLogicFlow

MM1m-send.req fromsendingclienttotheiroperatorMMSC

MM1m-send.conf confirmsMMSCacceptanceofmessage


MobileNetworkA

MMSCNetworkA

Receiver

Sender

MobileNetworkB

MMSCNetworkB

MM1:m-send.req /m-send.conf1


MMSCinitiatesMM4connectiontootheroperatorMMSCandusesMM4_forward.REQtransactiontotransfermessage.

OtherMMSCinitiatesMM4connectionbacktooriginatorMMSCandusesMM4_forward.REStransactiontoconfirmMMSCacceptanceofmessage


MobileNetworkA

MMSCNetworkA

Receiver

Sender

MobileNetworkB

MMSCNetworkB

MM1:m-send.req /m-send.conf

MM4:MM4_forward.REQMM4_forward.RES

1

2


StandardMM1MMSMTLogicFlow

ReceiverMMSCpostsMM1m-notification.ind toreceivingdeviceoverWAPPush


MobileNetworkA

MMSCNetworkA

Receiver

Sender

MobileNetworkB

MMSCNetworkB



MM1:m-notification.ind

1

23

MM4Transaction:SimplifiedTherecipientphoneperformsanHTTP(orWSP)GETtoretrievetheMMSmessagecontentURLfromtheMMSC.

TheHTTPresponseistheMMSmessageinanm-retrieve.conf PDU.


MobileNetworkA

MMSCNetworkA

Receiver

Sender

MobileNetworkB

MMSCNetworkB



MM1:m-notification.ind

1

23

HTTPGET/MM1:m-retrieve.conf 4

MM4Transaction:SimplifiedAfterMMSdelivery,ifadeliveryreportwasrequested:

ReceiverMMSCinitiatesMM4connectiontooriginatorMMSCandissuesMM4_delivery_report.REQ.

OriginatorMMSCinitiatesMM4connectionbacktoreceiverMMSCandusesMM4_delivery_report.REStransactiontoconfirmMMSCacceptanceofdeliveryreport.

MM1deliveryreportispushedtosender.


MobileNetworkA

MMSCNetworkA

Receiver

Sender

MobileNetworkB

MMSCNetworkB

MM4:MM4_delivery_report.REQMM4_delivery_report.RES

5

HTTPGET/MM1:m-retrieve.conf 4

MM1:m-delivery.ind6

MM4Transaction:SimplifiedAfterMMSisread,ifareadreportwasrequestedandreceiverallowsreadreports:ReceiverpostsanMM1m-read-rec.ind totheirMMSCReceiverMMSCinitiatesMM4connectiontooriginatorMMSCandissuesMM4_read_reply_report.REQ.OriginatorMMSCinitiatesMM4connectionbacktoreceiverMMSCandusesMM4_read_reply_report.REStransactiontoconfirmMMSCacceptanceofdeliveryreport.MM1readreport(m-read-orig.ind)ƒs ispushedtosender.


MobileNetworkA

MMSCNetworkA

Receiver

Sender

MobileNetworkB

MMSCNetworkB

MM4:MM4_read_reply_report.REQMM4_read_reply_report.RES

8

MM1:m-read-rec.ind 7

MM1:m-read-orig.ind9

MM7– ValueAddedServiceProviders• InterfacebetweenValueAddedServiceProvider(VASP)applicationsandMMSC.

• SOAP/XML/HTTPPOSTbasedprotocoldefinedby3GPPTS23.040• MMSheadersencodedasXMLdocument• MMScontentencodedasMIMEmultipartobject• Bi-directionalHTTPPOST– MMSCandVASPcanbothinitiateconnections


MM7VariationsandInteroperabilityEarlyversionsofthe3GPPTS23.140specificationdefinedMM7onlyasaconceptualprotocol.ThisleadseveralvendorstodefinetheirownMM7protocols(Ericsson,LogicaCMGandNokia).DifferentversionsoftheMM7specificationhavedefinedmorethan10differentXMLschemaswithsomesignificantdifferencesandincompatibilities.Themostsignificantproblemsarerelatedtointernationalnumberencodingandsenderaddressformats.


SOAP=SimpleObjectAccessProtocolSOAPisalightweightprotocolfortheexchangeofinformationindistributedenvironments.SOAPtransactionsarerepresentedusingXML.ASOAPtransactioncontainsaSOAPheader,SOAPbodyandanoptionalSOAPattachment.MMSheadersareencodedintheSOAPheaderandSOAPbody.MMScontentisplacedintheSOAPattachmentasaMIMEmultipart.


SOAPMIMETypesWhenaSOAPtransactioncontainsonlyaSOAPheaderandbody(noMMScontentobjects),suchasadeliveryorreadreport,theMIMEtypetext/xmlisused.WhenaSOAPtransactioncontainsaSOAPattachment(oneormoreMMScontentobjects),theMIMEtypemultipart/relatedisused.Thismultipartwillalwaysconsistofexactlytwoparts,eveniftheMMSmessagecontainsmorethanonecontentobject.Onepartisthetext/xmlSOAPheaderandbody.TheotherpartisamultipartobjectcontainingtheMMScontentobjects.Thiscanbeconfusingasonemultipartobjectisnestedinsideanother.


SampleMM7MessageThefirstobjectintheoutermultipartobjectistheSOAPheaderandbody,whichisanXMLdocumentcontainingMMSheaders


SampleMM7Message(continued)ThesecondobjectintheoutermultipartobjectistheSOAPattachment,whichcontainstheMMScontentobjects.Thisisamultipartobjectencodedinsideanothermultipartobject.


MM7PDUKindsTherearetwokindsofMM7PDUs:1. Request:DenotedasMM7_type-name.REQ2. Response:DenotedasMM7_type-name.RES


MM7PDUTransmissionMM7PDUsaresentusingHTTPPOST.ThepayloadoftheHTTPrequestcontainstheMM7Request.ThepayloadoftheHTTPresponsecontainstheMM7Response.


MM7PDUsTransaction Flow ofTransaction PDUTypeName

SubmitMessage POST:VASPtoMMSC MM7_submit.REQ

ResponsefromMMSC MM7_submit.RES

DeliverMessage POST:MMSCtoVASP MM7_deliver.REQ

ResponsefromVASP MM7_deliver.RES

DeliveryReport POST:MMSCtoVASP MM7_delivery_report.REQ

ResponsefromVASP MM7_delivery_report.RES

ReadReport POST:MMSCtoVASP MM7_read_reply_report.REQ

ResponsefromVASP MM7_read_reply_report.RES

MMSCError ResponsefromMMSC MM7_RS_error.RES

VASPError ResponsefromVASP MM7_VASP_error.RES


MM9– Billing&ChargingInterface• Billinggenerallyreferstopost-paidCDRgeneration• Charginggenerallyreferstorealtimechargingrequiredbypre-paid• NowSMS MMSCsupportsHTTPbasedaccountingcallbackswhichsomecustomersusetogenerateCDRs(orcanbeusedforrealtimecharging)

• NowSMS MMSCsupportsDIAMETERCreditControlorBaseAccountingforrealtimecharging.


DIAMETER/MM9NowSMS MMSCimplementsDiameterCreditControlforchargingbaseduponthefollowingspecifications:◦ [DIAMBASE]– RFC3588– DiameterBaseProtocol◦ [DIAMCCA]– RFC4006– DiameterCreditControlApplication◦ [3GPPDIAM]– 3GPPTS32.299– 3GPPDiameterChargingApplications◦ [SCAPv2]– EricssonCCNSCAPv2


DIAMETER/MM9(continued)[3GPPDIAM]definesastandardformatforimplementingMMSchargingoverDiameter,knownasMM9intheMMSprotocolspecifications.WhiletheMMSCpreferenceistouseMM9,itisalsopossibletoconfiguretheMMSCtousegenericchargingprimitivesdefinedin[DIAMCCA]inordertofacilitateinteroperabilitywithawiderbaseofchargingsystems.Optionally,DiameterextensionsdefinedinEricsson’s[SCAPv2]protocolcanbeenabled.


DIAMETER/MM9(continued)TheMMSCDiameterMM9implementationishighlyconfigurable,withconfigurationsettingsthatallowtheDiameterrequeststobetunedtomeettherequirementsofdifferentchargingsystems.ThecoreDiameterchargingrequestsuseCredit-Control-Requestasdefinedin[DIAMCCA].SeveralextensionsetsaredefinedthatprovideadditionalDiameterparameterstobeincludeinthechargingrequest.Formaximumflexibility,XMLtemplatefilesareusedtodefinetheunderlyingDiameterrequests,allowingforcustomparameterstobeaddedordeletedasrequired.Asanexampleofthisflexibility,templateshavebeencreatedtosupportEricssonSCAPv1,whichusesDiameterBaseAccountinginsteadofDiameterCreditControl.


DIAMETER/MM9(continued)Moreonthewebsiteathttp://www.nowsms.com/mmsc-diameter-mm9-implementation


MMSCAccountingCallbacksMMSCaccountingcallbacksprovideaninterfacebetweentheNowSMSMMSCandexternalbillingandchargingsystems.TheseMMSCaccountingcallbacksareHTTP-based.Whenaccountingcallbacksareenabled,theMMSCwillissueHTTPrequeststoacustomersuppliedURLinordertointerfacewiththecustomerbillingandchargingsystems.ToenableMMSCaccountingcallbacks,itisnecessarytomanuallyedittheMMSC.INIconfigurationfile,anddefinethecallbackURLunderthe[MMSC]sectionheader,usingthefollowingconfigurationparameter:MMSAccountingURL=http://server/path


MMSCAccountingCallbacks(continued)WhenevertheMMSCprocessesanMMSmessage,itissuesanaccountingcallbackbyissuinganHTTPtransactiontothecallbackURL.VariablesdescribingtheMMStransactionareappendedtotheMMSAccoutingURL asHTTPGETCGI-stylevariables,withstandardURLescapingappliedforencodingreservedcharacters.Forexample:http://server/path?PreAuth=Yes&Type=MMSSend&From=%2B449999999999&To=%2B447777777777&MsgCount=1


MMSCAccountingCallbacks(continued)Mostoftheaccountingcallbacksareinformationalonly,andexisttorecordcharginginformationaftertheMMSChasprocessedatransaction.However,therearealsopre-authorisation callbackswhichoccurbeforetheMMSCprocessesatransaction.Thesepre-authorisationcallbacksexisttoallowthecustomerbillingsystemtodecidewhetherornotthetransactionshouldbeallowed.Inthisscenario,thecallbackcouldcheckavailablecreditandrejectanMMSmessagetransactionbeforeitisacceptedbytheMMSC.


MMSSend PreAuth CallbackThiscallbackisexecutedwhenanMMSsubscriber,ValueAddedServiceProvider(VASP)orMMSCinterconnectpartner,isrequestingtosendamessage.Thisisa“pre-authorisation”request,anddoesnotmeanthatthemessagewillactuallybeacceptedbyNowSMS fordelivery.IfNowSMS cannotsuccessfullyconnecttotheaccountingURL,ortheURLreturnsaresponseotherthanastandard“HTTP200OK”response,theuserrequesttosendamessagewillbeblocked.A“PreAuth”requesttosendamessagewillalsobeblockediftheHTTPresponsecontentincludesthetext“PreAuth=Deny”.


MMSSend PreAuth Callback (continued)ThefollowingparametervariablesmaybesetfortheMMSSend pre-authorisation request:

PreAuth=Yes

Thepresenceofthisparameterindicatesthatthiscallbackisapre-authorisation request.

Type=MMSSend

ThetransactiontypeisMMSSend,indicatingthatarequestisbeingmadetosendanMMSmessage.

From=SenderPhoneNumber

Thisparametercontainsthephonenumberofthesubscriberthatissendingthemessage.NotethatURLescapingrulesrequirethe“+”symboltobeencodedas“%2B”.

To=RecipientPhoneNumber (maybeacommadelimitedlistwithmultiplerecipients)

Thisparametercontainsoneormorerecipientphonenumbers.Ifmorethanonephonenumberispresent,thiswillbeacommadelimitedlistofrecipientphonenumbers.(NotethatURLescapingrulesrequirethe“,”symboltobeencodedas“%2C”.)


MMSSend PreAuth Callback(continued)VASPIN=MmscVaspName

ThisparameterispresentifthemessageisarrivingfromaValueAddedServiceProviderorMMSCinterconnectpartner.Thevalueofthisparameterreferstotheaccountnameasdefinedinthe“MMSCVASP”list.

NotethatsomeversionsofNowSMS mayprefacetheMmscVaspName withthetext“VASP:”.

VASP=MmscOutboundRoute (maybeacommadelimitedlistifmultiplerecipients)

ThisparameterispresentiftheMMSChasdeterminedthatthemessagemustberoutedviaanexternalroutefordelivery.Thevalueofthisparameterreferstotheaccountnameasdefinedinthe“MMSCRouting”list.

Ifthemessageisbeingsenttomultiplerecipients,thisfieldmaycontainacommadelimitedlistofrouteswitharoutelistedforeachrecipient.Ifthereisamixoflocalandremoterecipients,localrecipientswillhaveablankentrywithinthecommadelimitedlistofroutes.


MMSSend PreAuth Callback(continued)MsgCount=####

ThisparameterspecifiesthenumberofrecipientsforthisMMSmessagetransaction.

(NotethattheMMSSend PreAuth callbackisissuedonlyonceifanMMSmessageisbeingsenttomultiplerecipients.TheMMSSend Chargingcallback,whichrecordsbillingandcharginginformationaftertheMMSChasacceptedthemessage,issuesaseparatecallbackforeachrecipient.)

Size=####

ThisparameterspecifiesthesizeoftheMMSmessageinbytes.


MMSSend PreAuth Callback(continued)Dependingonsystemconfiguration,additionalparameterssuchasSGSNAddress,SGSNMCCMNC(usedtodetectroamingsubscribers)andIMSImayalsobeavailabletothecallback. Forinformationontheseparameters,see DetectingRoamingSubscribers athttp://www.nowsms.com/operator-mmsc-accounting-detecting-roaming-subscribers

Additionalcallbackdocumentationcanbefoundathttp://www.nowsms.com/doc/advanced-configuration-settings/mms-accounting-callbacks


MM5/MNP/MMSRoutingTheNowSMS MMSCimplementsadynamicMMSroutingcallbackfacilityforenvironmentswheremoreadvancedMMSroutingcapabilitiesarerequired.

ThestandardNowSMS MMSCconfigurationallowsforMMSroutingbaseduponphonenumberprefixes.However,inMNPenvironments,itmaybenecessarytoqueryHLRoradatabasetodeterminehowtoproperlyrouteanMMSmessage.

WhentheMMSRoutingcallbackisenabledinNowSMS,eachtimetheMMSCreceivesamessage,itwillconnecttoaconfigurablecustomer-providedroutingcallbackURL,passingthemessagerecipienttotheURL.ThecustomerprovidedURLcanreturnaresponsetoindicatethatthemessageshouldberoutedviaaspecificroutedefinedinthe“MMSCRouting”pageoftheNowSMS configurationdialog,ortheresponsecanindicatethatthemessageshouldberejected.


MM5/MNP/MMSRouting(continued)TheMMSroutingcallbackURLisdefinedintheMMSC.INIfile,underthe[MMSC]sectionheader:

MMSRoutingURL=http://server.name/path

ThevariableslistedbelowwillbeaddedtotheMMSRoutingURL whentheURLisexecutedbythegatewayasHTTPGET(CGI-style)parameters.

Type=MMSRouteCheck (Note:Future“Type”valuesmaybeaddedinthefuture.)

From=SenderPhoneNumber ore-mailaddressVASPIN=VASPname (presentifthemessagewasreceivedviaaspecificaccountdefinedinthe“MMSCVASP”list)

To=RecipientPhoneNumber


MM5/MNP/MMSRouting(continued)Example:

http://server.name/path?Type=MMSRouteCheck&From=%2B1234567&VASPIN=test&To=%2B9999999999

(Note:The“%2B”intheaboveexamplesisstandardURLescapingforthe“+”character.)

Tospecifywhichoftheroutesdefinedinthe“MMSCRouting”listshouldbeusedtoroutethismessage,theURLmustreturnastandardHTTP200OKresponse,andincludethefollowingtextsomewhereintheresponse:

Route=xxxxxxx

“xxxxxxx”shouldmatchan“AccountName”definedinthe“MMSCRouting”list,oritcanusethepredefinedvaluesof“Direct”(signifyingMMSCDirectDelivery),“WAPPush”(signifying“ConverttoMultimediaWAPPush”),or“BlockMessage”(signifyingtheMMSCshouldrejectthemessage).


mms protocol overview - nowsms protocol overview november 2015 ©2015 nowwireless limited ... •...

Documents