Mm7 protocol analysis-1 Overview

MMS protocol interfaces include MM1 ~ There are 10 interface protocols in mm10, involving interaction between different entities. Of course, for application development, you generally only need to pay attention to the mm7 protocol, that is, the interaction protocol between mmsc and sp.

Interface Name	Connected object	Description
MM1	MMSC-WAP GW	3GPP and OMA have a very clear definition. infox mmsc is implemented through two Protocols, which are compatible and supported. Reading the report is a good example.
Mm2	Relay-Server	International regulations such as 3GPP are not clearly defined, and each manufacturer is a private agreement. Infox mmsc extends the mm2 interface to the interface and function of the software bus.
Mm3	Mmsc-E-Mail Server	SMTP-based interface. 3GPP and other international regulations are clearly defined. For the e-mail server, mmsc is an email server.
Mm4	MMSC-MMSC	For mmsc interconnection, most manufacturers follow the principle of "region service". mmsig is recommended for interconnection between different networks and different carriers. mmscig interfaces are provided on both sides.
MM5	MMSC-HLR	International regulations such as 3GPP are not clearly defined, but only mentioned: 1. mmsc is used to obtain the status of end users. 2. If you use SMS to carry notification messages, you can use the MM5 interface instead.
Mm6	MMSC-DB	International regulations such as 3GPP are not clearly defined, and each manufacturer is a private agreement.
Mm7	MMSC-SP	3GPP and other international specifications are clearly defined for mmsc and SP interaction.
Mm8	MMSC-OSS	3GPP and other international specifications are not clearly defined, and only some CDR suggestions and transmission protocols-FTP are provided.
Enum Interface	Mmsc-Enum Server	International regulations such as 3GPP are not clearly defined, and each manufacturer is a private agreement.
Dsmp Interface	MMSC-DSMP	This interface has many versions and has two main functions: 1. Authentication 2. Authentication billing (Sunday Project)

The mm7 protocol is carried over the HTTP protocol and transmitted using the SOAP protocol encapsulation.
The mm7 request should be transmitted in an http post request, and the mm7 response should be transmitted in an HTTP Response Message.
Message control information of mm7 is encapsulated in soap.
The message content of mm7 is encapsulated in MIME format.

Mm7 messages mainly use the following four types of messages:
Mm7_submit is used for downstream Mt messages.
Mm7_deliver is used for upstream Mo messages.
Mm7_delivery_report is used for the delivery report corresponding to the upstream Mt message.
Mm7_read_reply is used for reading reports corresponding to upstream Mt messages.

Mm7 request example:

POST / HTTP/1.1Host:127.0.0.1:9077Content-Type:multipart/related; boundary="--NextPart_0_2817_24856";type="text/xml";start="</tnn-200102/mm7-vasp>"Content-Transfer-Encoding:8bitAuthorization:Basic bW1zOm1tcw==SOAPAction:""MM7APIVersion:V1.5.3_20040621Connection: Keep-AliveContent-Length:6985Mime-Version:1.0this is a multi-part message in MIME format----NextPart_0_2817_24856Content-Type:text/xml;charset="UTF-8"Content-Transfer-Encoding:8bitContent-ID:</tnn-200102/mm7-vasp><?xml version="1.0" encoding="UTF-8"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header><mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-0" env:mustUnderstand="1">SUNTEK1-00259E534DD67D41F5125</mm7:TransactionID></env:Header><env:Body><SubmitReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-0"><MM7Version>6.3.0</MM7Version><SenderIdentification><VASPID>100009</VASPID><VASID>8809</VASID><SenderAddress>100020</SenderAddress></SenderIdentification><Recipients><To><Number>15627400428</Number></To></Recipients><ServiceCode>209</ServiceCode><DeliveryReport>true</DeliveryReport><Subject>this is a test mms</Subject><ChargedParty>ThirdParty</ChargedParty><ChargedPartyID>15627400428</ChargedPartyID></SubmitReq></env:Body></env:Envelope>----NextPart_0_2817_24856Content-Type:multipart/mixed;boundary="SubPart_7452684322002_77645"Content-ID:conentIdContent-Transfer-Encoding:8bit--SubPart_7452684322002_77645Content-Type:image/gifContent-Transfer-Encoding:8bitContent-ID:dog-picGIF89a===========================

Mm7 response example:

HTTP/1.1 200 OKConnection: Keep-AliveContent-Type: text/xml;charset=GB2312Content-Length: 535<?xml version="1.0"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header><mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-0">SUNTEK1-00259E534DD67D41F5125</mm7:TransactionID></env:Header><env:Body><SubmitRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-0"><MM7Version>6.3.0</MM7Version><Status><StatusCode>1000</StatusCode></Status><MessageID>061503554008542090000</MessageID></SubmitRsp></env:Body></env:Envelope>