3GPP2 X.S0016-370 Version 1.0.0
Version Date: April 3, 2003
MMS MM7 VASP Interworking Stage 3 Specification Revision: 0
COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.
i
1 2 3 4 5 6 7 8 9
Revision History
Revision Date 10 11 12 Rev. 0 13 14 15
16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57
ii
Initial Publication
April 2003
X.S0016-370 v1.0
MMS MM7 Stage 3
CONTENTS
1
Introduction............................................................................................................................................1 1.1 1.2 1.3 1.4 1.5 2 2.1 2.2
Scope...............................................................................................................................................1 References......................................................................................................................................2 Terminology...................................................................................................................................3 Glossary..........................................................................................................................................3 Abbreviations.................................................................................................................................3 Introduction (Informative)...........................................................................................................4 Stage 2 Amendments (Normative)...............................................................................................4
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
MM7 Stage 3 VASP Interworking Specification...................................................................................4
2.3 Stage 3 Implementation of the MM7 Abstract Messages (Normative).....................................4 2.3.1 SOAP Message Format and Encoding Principles...................................................................4 2.3.2 MM7 Addressing Considerations............................................................................................7 2.3.3 Status Reporting......................................................................................................................8 2.3.4 Request and Error Status Codes..............................................................................................8 2.4 Mapping of Information Elements to SOAP Elements (Normative)......................................11 2.4.1 MM7_submit Information Element Mappings......................................................................12 2.4.2 MM7_deliver Information Element Mappings......................................................................15 2.4.3 MM7_cancel Information Element Mappings.......................................................................17 2.4.4 MM7_replace Information Element Mappings.....................................................................19 2.4.5 MM7_delivery_report Information Element Mappings........................................................20 2.4.6 MM7_read_reply Information Element Mappings................................................................21 2.4.7 MM7 Error Response Information Element Mappings.........................................................21 2.5 2.6 2.7
MM1, MM4 <=> MM7 header mapping (Informative)...........................................................22 MM7 XML Schema (Normative)...............................................................................................28 Exceptions (Informative)............................................................................................................34
i
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57
MMS MM7 Stage 3 X.S0016-370 v1.0
FOREWORD
This Technical Specification has been produced by the 3rd Generation Partnership Project 2 (3GPP2). This specification contains portions of material copied from 3GPP specification “TS 23.140”. The copyright on the 3GPP specification is owned by the Organizational Partners of 3GPP (ARIB – Association of Radio Industries and Businesses, Japan; CWTS – China Wireless Telecommunications Standards group, China; ETSI – European Telecommunications Standards Institute, Committee T1, USA; TTA – Telecommunications Technology Association, Korea; and TTC – Telecommunication Technology Committee, Japan), which have granted license for reproduction and use by 3GPP2 and its Organizational Partners.
ii
X.S0016-370 v1.0
MMS MM7 Stage 3
1 Introduction
The MMSE may support Value Added Services in addition to the basic messaging services defined for MMS. These Value Added Services may be provided by the network operator of the MMSE or by third-party Value 1 2 3 4 5 6 7 Added Service Providers (VASP). This section defines the technical realization of the interworking between the MMS Relay/Server and the VASP.
The following figure (taken from the 3GPP2 MMS Stage 2 Functional Specification [MMS Stage2]) illustrates an example data-flow of the
message exchange involved in a VAS distribution of a MM as outlined by the abstract messages specified in [MMS Stage2]:
VASPMMS Relay/OriginatorRecipient-1ServerMMS UARecipient-mMMS UAMM7_submit.REQMM7_submit.RESMM1_notification.REQMM7_delivery_report.REQMM1_notification.RES(rejected)MM7_delivery_report.RESMM1_notification.REQMM1_notification.RES (deferred)MM1_retrieve.REQMM1_retrieve.RESMM7_delivery_report.REQMM1_acknowledgement.REQMM7_delivery_report.RESFigure 1 - Sample data flow of MM7 message distribution Subsequent sub-sections will specify the technical realizations of the abstract messages that are defined for the MM7 interface. 1.1 Scope This document describes the technical realization (Stage 3) of the Value-Added Service Provider (VASP) interface, also known as the MM7 reference point. 1 8 9 10 11 12 13 14 15 16 17 18
19 20 21 22 23 24
25 26 27 28 29 30 31
32 33 34
35 36 37 38
39 40
41 42 43
44 45 46 47 48 49 50
51 52 53 54 55
56 57 58
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57
MMS MM7 Stage 3 X.S0016-370 v1.0
1.2 References
3GPP2
[MMS Stage1] S.R0064-0, Multimedia Messaging Services (MMS) Stage
1 Requirements, October 2002, 3GPP2. [MMS Stage2] X.S0016-200/TIA-934-200, Multimedia Messaging
Services (MMS) Stage 2 Functional Specifications, April 2003, 3GPP2. ITU [E.164]
ITU-T Recommendation Series E: E.164: The
international public telecommunication numbering plan; May 1997.
IETF [RFC2387]
RFC 2387, The MIME Multipart/Related Content-type, IETF. http://www.ietf.org/rfc/rfc2387 RFC 2376: \"XML Media Type\http://www.ietf.org/rfc/rfc2376.txt
RFC 2616: “Hypertext Transfer Protocol, HTTP/1.1”, IETF. http://www.ietf.org/rfc/rfc2616.txt
[RFC2376]
[RFC2616]
World-Wide-Web Consortium (W3C) [SMIL]
SMIL, Synchronized Multimedia Integration Language (SMIL) 1.0 Specification, June 1998, W3C. http://www.w3.org/TR/REC-smil W3C Note 08, \"Simple Object Access Protocol (SOAP) 1.1\http://www.w3.org/TR/SOAP
[SOAP]
[SOAPMSGS] W3C Note 11, \"SOAP Messages with Attachments\
December 2000, W3C. http://www.w3.org/TR/SOAP-attachments
2
X.S0016-370 v1.0
MMS MM7 Stage 3
1.3 Terminology
This document uses the following “verbal forms” and “verbal form definitions”:
1. “shall” and “shall not” identify items of interest that are to be strictly followed and from which no deviation is recommended, 2. “should” and “should not” indicate items of interest that are highly desirable and particularly suitable, without identifying or excluding other items; or (in the negative form) indicate items of interest that are not desirable, are not particularly suitable, or are not recommended but not prohibited, and 3. “may” and “may not” indicate items of interest that are optional but permissible within the limits of this recommendation.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
1.4 Glossary
In addition to the glossary items in [MMS Stage1] and [MMS Stage2], the following items used within this document.
SOAP Attachment: Multimedia content, e.g. audio, image, text,
presentation or a combination of different media types and/or formats, transferred from an MMS VASP to an MMS Relay/Server or vice versa.
21 22 23 24 25 26 27 28 29 30 31 32 33
1.5 Abbreviations
For the purposes of the present document, the following abbreviations apply in addition to those defined in [MMS Stage1] and [MMS Stage2]:
HTTP Hypertext Transfer Protocol IETF Internet Engineering Task Force MIME Multipurpose Internet Mail Extensions MM Multimedia Message MMS Multimedia Messaging Service MMSE MMS Environment (under a single administrative
control)
OMA Open Mobile Alliance RFC Request for Comments VASP Value-Added Service Provider
34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
3
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57
MMS MM7 Stage 3 X.S0016-370 v1.0
2
MM7 Stage 3 VASP Interworking Specification
2.1 Introduction (Informative)
Reference point MM7 is used to transfer MMs between an MMS
Relay/Server to MMS VAS applications. This reference point, which is elaborated in the sections below, is based on SOAP 1.1 [SOAP] transported over HTTP [RFC2616].
Address formats for MM7 are also specified in the MMS Stage 2
Functional Specification [MMS Stage2], but are basically email addresses or [E.164] (MSISDN) addresses. Short codes may also be supported in some implementations.
2.2
None
Stage 2 Amendments (Normative)
2.3
Stage 3 Implementation of the MM7 Abstract Messages (Normative)
The interface between a VASP and the MMS Relay/Server, over the MM7 reference point, shall be realized using SOAP 1.1 [SOAP] as the
formatting language. The VASP and the MMS Relay/Server shall be able to play dual roles of sender and receiver of SOAP messages. HTTP
[RFC2616] shall be used as the transport protocol of the SOAP messages. The SOAP message shall bind to the HTTP request/response model by providing SOAP request parameters in the body of the HTTP POST
request and the SOAP response in the body of the corresponding HTTP response.
2.3.1 SOAP Message Format and Encoding Principles
The following principles shall be used in the design of the SOAP implementation of the MM7 interface:
• The schema shall be based on the W3C SOAP 1.1 schema . The schema shall include an indication of the version of the MM7 specification that is supported.
4
X.S0016-370 v1.0
MMS MM7 Stage 3
NOTE: The W3C SOAP 1.1 schema will be published by the 3GPP. The
URI shall be
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
• The MM7 SOAP messages shall consist of a SOAP envelope, SOAP Header element and SOAP Body element, as described in [SOAP]. • The SOAP EncodingStyle [SOAP] should not be used.
• Transaction management shall be handled in the SOAP Header element. The TransactionID shall be included as a SOAP Header
entry. The SOAP actor [SOAP] attribute should not be specified in the SOAP Header entry. The SOAP mustUnderstand [SOAP] attribute should be specified with value “1”. • All MM7 information elements, except for the TransactionID, shall be included in the SOAP Body element. • XML element names shall use Upper Camel Case convention, where words are concatenated to form an element name with the first letter of each word in upper case (e.g. EarliestDeliveryTime). The only exception to this rule is where an acronym (e.g. VASP) is used - in such cases all of the letters of the acronym shall be in upper case (e.g. VASPHeader). 2.3.1.1
Binding to HTTP
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
MM7 request messages shall be transferred in an HTTP POST request. MM7 responses shall be transferred in an HTTP Response message. The media type “text/xml” [RFC2376] shall be used for messages containing only the SOAP envelope.
MM7 requests that carry a SOAP attachment shall have a
“multipart/related” [RFC2387] Content-Type. The SOAP envelope shall be the first part of the MIME message and shall be indicated by the Start parameter of the multipart/related Content-Type. If a SOAP attachment is included it shall be encoded as a MIME part and shall be the second part of the HTTP Post message. The MIME part should have the
appropriate content type(s) to identify the payload. Figure 2 and Figure 3 provide few examples of the message structure. This MIME part shall have two MIME headers - Content-Type and Content-ID fields. The
Content-ID shall be referenced by the MM7 request 5 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 StartContent-type: multipart/relatedSOAP EnvelopeSOAP AttachmentContent-type: multipart/relatedContent-IDStartpresentationimage/jpegtext/plainaudio/AMR Figure 2 - Message structure for a message with a SOAP Attachment (multipart/related payload) 6 X.S0016-370 v1.0 MMS MM7 Stage 3 StartdSOAP Envelopeetalerd/eSOAP AttachmenttrxaipmContent-IDi/ttlruampi timage/jpeg:leupym t:-tenptext/plaineyttn-tonCetnoaudio/AMRC Figure 3 - Message structure for a message with a SOAP Attachment (multipart/mixed payload) For specific examples see the section describing SOAP HTTP examples. 2.3.1.2 SOAPAction Header Field The SOAPAction HTTP request header field [SOAP] should be set to the NULL string (i.e. “”). 2.3.2 MM7 Addressing Considerations In order to bind properly to HTTP, the MMS Relay/Server and the VASP shall be addressable by a unique URI type address [RFC2616]. This address shall be placed in the host header field in the HTTP POST method. In the SOAP body, when the recipient MMS User Agent is addressed, the address-encoding scheme for MM1 shall be used. For these purposes the VASP shall be identified by a MM1 addressable address. 7 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 2.3.3 Status Reporting The MM7 response messages shall be carried within a HTTP Response. The response may carry status at three levels: – network errors shall be indicated by the HTTP level, e.g. as an HTTP 403 “Server not found” and shall be carried in the HTTP response back to the originating application. – request processing errors shall be reported as a SOAP Fault as defined in [SOAP]. The SOAP fault shall include the faultcode [SOAP], faultstring [SOAP], and detail [SOAP] elements. The detail element shall include the status elements described below and in Table 1. Errors relating to the TransactionID shall be reported as a SOAP Fault. The faultcode shall be “Client.TransactionID” and the faultstring shall be used to indicate the human-readable description of the error. No detail element shall appear. – success or partial success shall be reported in a MM7 response message that will include the following status elements. All status responses shall be reported with three XML elements in the response, i.e. the details of the SOAP Fault and the status of the MM7 response message – • StatusCode shall indicate a numerical code that identifies different classes of error or successful completion of the operation. The StatusCode is a four-digit number of which the two high-order digits are defined in Section 2.3.4, the two low-order digits are implementation specific. • StatusText shall contain a predefined human readable description of the numerical code that indicates the general type of the error. • Details, optionally, gives particular details of the error or partial success, e.g. indicates the address that cannot be resolved or message-id that is not recognized. The format of the details element is implementation specific. 2.3.4 Request and Error Status Codes The StatusText element (for application-level situations) shall be used to carry a human readable explanation of the error or success situation, e.g. partial success. In Table 1 below the status text should be used by the VASP or MMS Relay/Server when indicating status information to the originator. In addition to this there will be status codes consisting of a four digit numeric value. The first digit of the status code indicates the class of the code. There are 4 classes: 8 X.S0016-370 v1.0 MMS MM7 Stage 3 • • • • 1xxx: Success in the operation, 2xxx: Client errors, 3xxx: Server errors, 4xxx: Service errors. 1 2 3 4 5 6 7 8 9 10 11 Status codes are extensible. The VASP and the MMS Relay/Server must understand the class of a status code. Unrecognised codes shall be treated as the x000 code for that class. Codes outside the four defined class ranges shall be treated as 3000. For implementation specific codes, the numbers in the range x500-x999 shall be used. The following Table 1 shows the StatusCodes and StatusTexts that are currently defined. 9 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 Table 1: StatusCode and StatusText Status Code 1000 1100 Success Partial success StatusText Meaning This code indicates that the request was executed completely This code indicates that the request was executed partially but some parts of the request could not be completed. Lower order digits and the optional Details element may indicate what parts of the request were not completed. Client made an invalid request The request was refused due to lack of permission to execute the command. The address supplied in the request was not in a recognized format or the MMS Relay/Server ascertained that the address was not valid for the network because it was determined not to be serviced by this MMS Relay/Server. When used in response-result, and multiple recipients were specified in the corresponding push submission, this status code indicates that at least one address is incorrect. The address supplied in the request could not be located by the MMS Relay/Server. This code is returned when an operation is requested on a previously submitted message and the MMS Relay/Server cannot find the message for the address specified. The server could not parse the MIME content that was attached to the SOAP message and indicated by the Content element or the content size or media type was unacceptable. This code is returned when an operation is requested on a previously submitted message and the MMS Relay/Server cannot find the message for the message ID specified or when the VASP receives a report concerning a previously submitted message and the message ID is not recognized. This code is returned when a LinkedID was supplied and the MMS Relay/Server could not find the related message. An element value format is inappropriate or incorrect. The server failed to fulfill an apparently valid request. The request could not be carried out because it is not possible. This code is normally used as a result of a cancel or status query on a message that is no longer available for cancel or status query. The MMS Relay/Server has recognized the message in question, but it cannot fulfill the request because the message is already complete or status is no longer available. Server could not complete the service requested. The MMS Relay/Server does not support this operation on multiple recipients. The operation MAY be resubmitted as multiple single recipient operations. The requested service cannot be fulfilled. Identification header of the request does not uniquely identify the client (either the VASP or MMS Relay/Server). The version indicated by the MM7 Version element is not supported. The server does not support the request indicated by the MessageType element in the header of the message. The SOAP and XML structures could not be parsed, mandatory fields are missing, or the message-format is not compatible to the format specified. Details field may specify the parsing error that caused this status. The operation caused a server (either MMS Relay/Server or VASP) failure and should not be resent. This indication may be sent by the server when service is temporarily unavailable, e.g. when server is busy The client does not have permission or funds to perform the requested operation. 2000 2001 2002 Client error Operation restricted Address Error 2003 Address Not Found 2004 Multimedia content refused 2005 Message ID Not found 2006 2007 3000 3001 LinkedID not found Message format corrupt Server Error Not Possible 3002 3003 Message rejected Multiple addresses not supported 4000 General service error 4001 Improper identification 4002 4003 4004 Unsupported version Unsupported operation Validation error 4005 4006 4007 Service error Service unavailable Service denied 10 X.S0016-370 v1.0 MMS MM7 Stage 3 2.4 Mapping of Information Elements to SOAP Elements (Normative) 1 2 3 4 The following subsections detail the mapping of the information elements of the abstract messages to SOAP elements. The full XML Schema definition of the MM7 reference point appears in Section 2.6. Specification of the format of SOAP element values appear in the schema. 5 6 7 8 9 11 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 2.4.1 MM7_submit Information Element Mappings Table 2 - MM7_submit.REQ mapping Information Element Transaction ID Message Type Location SOAP Header SOAP Body ElementName TransactionID MessageType Comments Defined as Root element of SOAP Body MM7 Version SOAP Body MM7Version Value is number of this specification, e.g. 5.2.0 VASP ID SOAP Body VASPID VAS ID SOAP Body VASID Sender Address SOAP Body SenderAddress Recipient Address SOAP Body Recipients Different address format will be specified as part of element value Service code SOAP Body ServiceCode Information supplied for billing purposes – exact format is implementation dependent Linked ID SOAP Body LinkedID Message-ID of linked message Message class SOAP Body MessageClass Enumeration – possible values: Informational, Advertisement, Auto Date and time SOAP Body TimeStamp Time of Expiry SOAP Body ExpiryDate Earliest delivery time SOAP Body EarliestDeliveryTime Delivery report SOAP Body DeliveryReport Boolean: True or False Read reply SOAP Body ReadReply Boolean: True or False Reply-Charging SOAP Body ReplyCharging No value – presence implies True! Reply-Deadline SOAP Body replyDeadline Attribute of ReplyCharging element Date format – absolute or relative Reply-Charging-Size SOAP Body replyChargingSize Attribute of ReplyCharging element Priority SOAP Body Priority Enumeration – possible values: High, Normal, Low Subject SOAP Body Subject Adaptations SOAP Body allowAdaptations Attribute of Content element Boolean: True or False Charged Party SOAP Body ChargedParty Enumeration – possible values: Sender, Recipient, Both, Neither Message Distribution SOAP Body DistributionIndicator Boolean: True or False Indicator Content type MIME header – Content-Type Attachment Content SOAP Body Content href:cid attribute links to attachment 12 X.S0016-370 v1.0 = MMS MM7 Stage 3 = Table 3 - MM7_submit.RES mapping Location SOAP Header SOAP Body SOAP Body = 1 Information Element Transaction ID Message Type MM7 Version Message ID Request Status Request Status Text ElementName TransactionID MessageType MM7Version MessageID StatusCode StatusText & Details Comments Defined as Root element of SOAP Body Value is number of this specification, e.g. 5.2.0 See section 2.3.4 See section 2.3.4 2 3 4 5 6 7 8 9 10 11 12 13 14 SOAP Body SOAP Body SOAP Body 2.4.1.1 Sample message submission and response (Informative) 15 16 17 POST /mms-rs/mm7 HTTP/1.1 18 Host: mms.omms.com Content-Type: multipart/related; boundary=”NextPart_000_0028_01C19839.84698430\"; 19 type=text/xml; 20 start”” 21 Content-Length: nnnn SOAPAction: “” 22 =23 --- NextPart_000_0028_01C19839.84698430 24 Content-Type:text/xml; charset=”utf-8” 25 Content-ID: 26 27 28 29 vas00001-sub 32 xmlns:mm7=\"http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1”> 36 39 40 42 43 46 47 49 50 53 54 57 13 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 --- NextPart_000_0028_01C19839.84698430 Content-Type: multipart/mixed; boundary=”StoryParts 74526 8432 2002-77645” Content-ID:< SaturnPics-01020930@news.tnn.com> --- StoryParts 74526 8432 2002-77645 Content-Type: text/plain; charset=\"us-ascii\" Science news, new Saturn pictures... -- StoryParts 74526 8432 2002-77645 Content-Type: image/gif; Content-ID: R0lGODdhZAAwAOMAAAAAAIGJjGltcDE0OOfWo6Ochbi1n1pmcbGojpKbnP/lpW54fBMTE1RYXEFO … --- StoryParts 74526 8432 2002-77645 -- ---_NextPart_000_0028_01C19839.84698430-- The response message is sent by the MMS Relay/Server back to the VASP for the VAS application in a HTTP Response message. HTTP/1.1 200 OK Content-Type: text/xml; charset=”utf-8” Content-Length: nnnn 14 X.S0016-370 v1.0 MMS MM7 Stage 3 2.4.2 = MM7_deliver Information Element Mappings Table 4 - MM7_deliver.REQ Mapping 1 2 3 4 Information Element Transaction ID Message Type Location SOAP Header SOAP Body ElementName TransactionID MessageType Comments 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Defined as Root element of SOAP Body MM7 Version SOAP Body MM7Version Value is number of this specification, e.g. 5.2.0 MMS Relay/Server ID SOAP Body MMSRelayServerID Linked ID SOAP Body LinkedID Message-ID of linked message Sender address SOAP Body Sender Recipient address SOAP Body Recipients If none appear then Sender Address is used Date and time SOAP Body TimeStamp Reply-Charging-ID SOAP Body ReplyChargingID Should correspond to an ID that appeared in previous MM7_submit.REQ Priority SOAP Body Priority Enumeration – possible values: High, Normal, Low Subject SOAP Body Subject Content type MIME header of Content-Type attachment Content SOAP Body Content href:cid attribute links to attachment Table 5 - MM7_deliver.REQ Mapping Information Element Transaction ID Message Type MM7 Version Service code Request status Request status text Location SOAP Header SOAP Body SOAP Body SOAP Body SOAP Body SOAP Body ElementName TransactionID MessageType MM7Version ServiceCode StatusCode StatusText & Details Comments Defined as Root element of SOAP Body Value is number of this specification, e.g. 5.2.0 See section 2.3.4 See section 2.3.4 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 2.4.2.1 Sample Deliver request and response (Informative) 48 49 50 51 52 53 54 55 56 57 58 POST /mms/weather.xml HTTP/1.1 Host: www.yahoo.com Content-Type: multipart/related; boundary=”NextPart_000_0125_01C19839.7237929064\"; type=text/xml; start”” Content-Length: nnnn SOAPAction: “” --- NextPart_000_0125_01C19839. 7237929064 Content-Type:text/xml; charset=”utf:8” Content-ID: 15 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 --- NextPart_000_0125_01C19839. 7237929064 Content-Type:text/plain;charset=”utf-8” Content-ID: Los Angeles, Calif, USA ---NextPart_000_0125_01C19839. 7237929064-- = The deliver response message might look like this (with an application error code): HTTP/1.1 200 OK Content-Type: text/xml; charset=”utf-8” Content-Length: nnnn 16 X.S0016-370 v1.0 MMS MM7 Stage 3 2.4.3 MM7_cancel Information Element Mappings = 1 2 3 4 Table 6 - MM7_cancel.REQ mapping Information Element Transaction ID Message Type MM7 Version VASP ID VAS ID Sender Address Message ID Location SOAP Header SOAP Body SOAP Body SOAP Body SOAP Body SOAP Body SOAP Body Element-name TransactionID MessageType MM7Version VASPID VASID SenderAddress MessageID Comments Defined as Root element of SOAP Body Value is number of this specification, e.g. 5.2.0 5 6 7 8 9 10 11 12 13 14 15 16 17 Table 7 - MM7_cancel.RES mapping Information Element Transaction ID Message Type MM7 Version Request status Request status text Location SOAP Header SOAP Body SOAP Body SOAP Body SOAP Body ElementName TransactionID MessageType MM7Version StatusCode StatusText & Details Comments Defined as Root element of SOAP Body Value is number of this specification, e.g. 5.2.0 See section 2.3.4 See section 2.3.4 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 2.4.3.1 MM7 cancel request and response example (Informative) 33 34 The following shows an interchange of an MM7_cancel.REQ and an MM7_cancel.RES to illustrate a SOAP message that does not include a multimedia content part. POST /mms-rs/mm7 HTTP/1.1 Host: mms.omms.com Content-Type: text/xml; charset=”utf-8” Content-Length: nnnn SOAPAction: “” 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 17 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 HTTP/1.1 200 OK Content-Type: text/xml; charset=”utf-8” Content-Length: nnnn = = 18 X.S0016-370 v1.0 MMS MM7 Stage 3 2.4.4 MM7_replace Information Element Mappings Table 8 - MM7_replace.REQ mapping 1 2 3 4 Information Element Transaction ID Message Type Location SOAP Header SOAP Body Element Name TransactionID MessageType Comments 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 Defined as Root element of SOAP Body MM7 Version SOAP Body MM7Version Value is number of this specification, e.g. 5.2.0 VASP ID SOAP Body VASPID VAS ID SOAP Body VASID Sender address SOAP Body SenderAddress Message ID SOAP Body MessageID Service code SOAP Body ServiceCode Information supplied for billing purposes – exact format is implementation dependent Date and time SOAP Body TimeStamp Earliest delivery time SOAP Body EarliestDeliveryTime Date format – absolute or relative Read reply SOAP Body ReadReply Boolean – true or false Adaptations SOAP Body allowAdaptations Attribute of Content element Boolean – true or false Content type MIME part Header Content-Type Content SOAP Body Content href:cid attribute links to attachment Message Distribution SOAP Body DistributionIndicator Boolean: True or False Indicator Table 9 - MM7_replace.RES mapping Information Element Transaction ID Message Type MM7 Version Request status Request status text Location SOAP Header SOAP Body SOAP Body SOAP Body SOAP Body Element Name TransactionID MessageType MM7Version StatusCode StatusText & Details Comments Defined as Root element of SOAP Body Value is number of this specification, e.g. 5.2.0 See section 2.3.4 See section 2.3.4 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 19 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 2.4.5 MM7_delivery_report Information Element Mappings Table 10 - MM7_delivery_report.REQ mapping Information Element Transaction ID Message Type MM7 Version MMS Relay/Server ID Message ID Recipient address Sender address Date and time MM Status Location SOAP Header SOAP Body Element Name TransactionID MessageType Comments Status text Defined as Root element of SOAP Body SOAP Body MM7Version Value is number of this specification, e.g. 5.2.0 SOAP Body MMSRelayServerID SOAP Body MessageID SOAP Body Recipient SOAP Body Sender SOAP Body TimeStamp SOAP Body MMStatus Enumeration – possible values: Expired, Retrieved, Rejected, Indeterminate, Forwarded SOAP Body StatusText Table 11 - MM7_delivery_report.RES mapping Information Element Transaction ID Message Type MM7 Version Request Status Request Status text Location SOAP Header SOAP Body SOAP Body SOAP Body SOAP Body Element Name TransactionID MessageType MM7Version StatusCode StatusText & Details Comments Defined as Root element of SOAP Body Value is number of this specification, e.g. 5.2.0 See section 2.3.4 See section 2.3.4 20 X.S0016-370 v1.0 MMS MM7 Stage 3 2.4.6 MM7_read_reply Information Element Mappings Table 12 - MM7_read_reply.REQ mapping 1 2 3 4 Information Element Transaction ID Message Type MM7 Version MMS Relay/Server ID Message ID Recipient address Sender address Date and time Read Status Location SOAP Header SOAP Body Element Name TransactionID MessageType Comments 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Status text Defined as Root element of SOAP Body SOAP Body MM7Version Value is number of this specification, e.g. 5.2.0 SOAP Body MMSRelayServerID SOAP Body MessageID SOAP Body Recipient SOAP Body Sender SOAP Body TimeStamp SOAP Body MMStatus Enumeration – possible values: Indeterminate, Read, Deleted without Read SOAP Body StatusText Table 13 - MM7_read_reply.RES mapping Information Element Transaction ID Message Type MM7 Version Request status Request status text Location SOAP Header SOAP Body SOAP Body SOAP Body SOAP Body Element Name TransactionID MessageType MM7Version StatusCode StatusText & Details Comments Defined as Root element of SOAP Body Value is number of this specification, e.g. 5.2.0 See section 2.3.4 See section 2.3.4 24 25 26 27 28 29 30 31 32 33 34 35 36 2.4.7 MM7 Error Response Information Element Mappings Table 14 - MM7_RS_error.RES mapping 37 38 39 40 41 42 43 Information Element Transaction ID Message Type MM7 Version Error status Error status text Location SOAP Header SOAP Body SOAP Body SOAP Body SOAP Body Element Name TransactionID MessageType MM7Version StatusCode StatusText & Details Comments Defined as Root element of SOAP Body Value is number of this specification, e.g. 5.2.0 See section 2.3.4 See section 2.3.4 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 21 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 Table 15 - MM7_VASP_error.RES mapping Information Element Transaction ID Message Type MM7 Version Error status Error status text Location SOAP Header SOAP Body SOAP Body SOAP Body SOAP Body Element name TransactionID MessageType MM7Version StatusCode StatusText & Details Comments Defined as Root element of SOAP Body Value is number of this specification, e.g. 5.2.0 See section 2.3.4 See section 2.3.4 2.5 ====MM1, MM4 <=> MM7 header mapping (Informative) This section maps the abstract messages from MM1 and MM4 to MM7 = and the corresponding information elements found on MM1 and MM4 = onto the information elements of MM7. The mappings between MM1 and MM7 abstract messages are: MM1_Submit.REQ <> MM7_Deliver.REQ MM7_Submit.REQ <> MM1_Notification.REQ and MM1_Retrieve.RES MM1_Read_Reply_Recipient.REQ <> MM7_Read_Reply_Report.REQ MM1_Forward.REQ <> MM7_Deliver.REQ == The mappings between MM4 and MM7 abstract messages are: MM4_Forward.REQ > MM7_Delivery_Report.REQ > MM7_Read_Reply.REQ The tables below shows the mapping and are provided to give an end-to-end description of MMS. There is a table for each MM1, MM4 abstract message that maps to a MM7 abstract message. In many cases there is no mapping between MM1, MM4 and MM7 information elements, this is according to specifications. These information elements are included in the tables below in order to give a complete picture of how the information elements are handled. There are also several abstract messages over MM1, MM4 that have no relevant mapping to MM7 and vice versa. These abstract messages are omitted from this annex. 22 MMS MM7 Stage 3 Table 16 - Mapping MM1_submit.REQ -> MM7_deliver.REQ Information elements in Information elements MM1_submit.REQ in MM7_deliver.REQ Recipient address, - Recipient address, - (NOTE 1) Content type Content type Sender address Sender address, - (NOTE 2) Message class - Date and time Date and time Time of Expiry - Earliest delivery time - Delivery report - Reply-Charging - Reply-Deadline - Reply-Charging-Size - Priority Priority Sender visibility - Store - MM State - MM Flags - Read reply - Subject Subject Reply-Charging-ID Reply-Charging-ID Content Content - Transaction ID - Message type - MM7 version - MMS Relay/Server ID - Linked ID NOTE 1:The recipient address over MM1 may or may not be mapped to recipient address over MM7. The recipient address over MM7 may also be independent of the recipient address over MM1. NOTE 2: If the Sender Visibility flag is set over MM1, the Sender address from MM1 is not mapped onto MM7. 23 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 X.S0016-370 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 Table 17 - Mapping MM7_submit.REQ -> MM1_notification.REQ, MM1_Retrieve.RES Information elements Information elements in Information elements in in MM7_submit.REQ MM1_notification.REQ MM1_retrieve.RES Message class Message class Message class Time of Expiry Time of expiry - Subject Subject Subject Priority Priority Priority Sender address Sender address Sender address Reply-Charging Reply-Charging Reply-Charging Reply-Deadline Reply-Deadline Reply-Deadline Reply-Charging-Size Reply-Charging-Size Reply-Charging-Size Transaction ID - - Message type - - MM7 version - - VASP ID - - VAS ID - - Recipient address - Recipient address Service code - - Linked ID - - Date and time - Date and time Earliest delivery time - - Delivery report - - Read reply - Read reply Adaptations - - Content type - Content type Content - Content Message Distribution Indicator Message Distribution Indicator - Charged Party - - - Message size - - Message Reference - - Stored - - Delivery report Delivery report - Reply-Charging-ID - - Element-Descriptor - - - Message ID - - MM State - - MM Flags - - Status - - Status Text - - Previously-sent-by - - Previously-sent-date-and-time 24 X.S0016-370 v1.0 MMS MM7 Stage 3 Table 18 - Mapping MM1_read_reply_recipient.REQ -> MM7_read_reply_report.REQ Information elements in Information elements in MM1_read_reply_recipient.REQ MM7_read_reply_report.REQ Recipient address Recipient address Originator address Originator address Message-ID Message-ID Date and Time Date and Time Read Status Read Status - Transaction ID - Message Type - MM7 Version - MMS Relay/Server ID - Status text Table 19 - Mapping MM1_Forward.REQ -> MM7_Deliver.REQ Information elements in Information elements MM1_Forward.REQ in MM7_Deliver.REQ Recipient address Recipient address Forwarding address Sender address Date and time Date and time Time of Expiry - Earliest delivery time - Store - MM State - MM Flags - Delivery report - Read reply - Message Reference Subject, Priority (NOTE) - Transaction ID - Message type - MM7 version - MMS Relay/Server ID - Linked ID NOTE: The message reference is used to map fields and content from the original MM. The mapping of these fields is identical to the MM1_Submit.REQ/MM7_Deliver.REQ mapping in Table 16. 25 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 26 MMS MM7 Stage 3 X.S0016-370 v1.0 Table 20 - Mapping MM4_Forward.REQ -> MM7_Deliver.REQ Information elements in Information elements in MM4_Forward.REQ MM7_Deliver.REQ 3GPP MMS Version - Message Type - Transaction ID - Message ID, - Linked ID, - (NOTE 1) Recipient(s) address Recipient address Sender address Sender address (NOTE 2) Content type Content type Message class - Date and time Date and time Time of Expiry - Delivery report - Priority Priority Sender visibility - Read reply - Subject Subject Acknowledgement Request - Forward counter - Previously-sent-by - Previously-sent-date and-time - Content Content - Transaction ID - Message type - MM7 version - MMS Relay/Server ID - Recipient address - Reply-Charging-ID NOTE 1: The Message ID over MM1 may or may not be mapped to the Linked ID over MM7. The Linked ID over MM7 may also be independent of the Message ID over MM1. NOTE 2: If the Sender Visibility flag is set over MM4, the Sender address from MM4 is not mapped onto MM7. X.S0016-370 v1.0 MMS MM7 Stage 3 Table 21 - Mapping MM7_Submit.REQ -> MM4_Forward.REQ Information elements in Information elements in MM4_Forward.REQ MM7_Submit.REQ 3GPP MMS Version - Message Type - Transaction ID - Message ID - Recipient(s) address Recipient address Sender address Sender address Content type Content type Message class Message class Date and time Date and time Time of Expiry Time of Expiry Delivery report Delivery report Priority Priority Sender visibility - Read reply Read reply Subject Subject Acknowledgement Request - Forward counter - Previously-sent-by - Previously-sent-date and-time - Content Content - Transaction ID - Message type - MM7 version - VASP ID - VAS ID - Service code - Linked ID - Earliest delivery time - Delivery report - Reply-Charging - Reply-Deadline - Reply-Charging-Size - Adaptations Table 22 - MM4_delivery_report.REQ -> MM7_delivery_report.REQ Information elements in Information elements in MM4_delivery_report.REQ MM7_delivery_report.REQ 3GPP MMS Version - Message Type - Transaction ID - MM Message ID Message ID Recipient address Sender address Sender address Recipient address MM Date and time Date and time Acknowledgement Request - MM Status Code MM Status Status Text Status text - Transaction ID - Message Type - MM7 Version - MMS Relay/Server ID 27 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 Table 23 - MM4_Read_reply_report.REQ -> MM7_read_reply_report.REQ Information elements in Information elements in MM4_Read_reply_report.REQ MM7_read_reply.REQ 3GPP MMS Version - Message Type - Transaction ID - Recipient address Recipient address Sender address Sender address Message-ID Message-ID Date and time Date and time Acknowledgement Request - Read Status Read Status Status text Status text - Transaction ID - Message Type - MM7 Version - MMS Relay/Server ID 2.6 MM7 XML Schema (Normative) xmlns:tns=\"http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1\" elementFormDefault=\"qualified\" attributeFormDefault=\"unqualified\"> 28 X.S0016-370 v1.0 MMS MM7 Stage 3 =\"ReplaceRsp\" type=\"tns:genericResponseType\"> xs:documentation =\"DeliveryReportReq\" type=\"tns:deliveryReportReqType\"> recipients xs:annotation > =\"DeliveryReportRsp\" type=\" tns:genericResponseType\"> VASP VASP to MMS: Response to a delivery report delivered to the xs:documentation =\"ReadReplyReq\" type=\"tns:readReplyReqType\"> recipients < xs:annotation<> MMS to VASP : Delivery Report from one of the MM > < xs:element< name> =\"ReadReplyRsp\" type=\"tns:genericResponseType\"> VASP xs:annotation > > =\"RSErrorRsp\" type=\" tns:genericResponseType\"> MMS Relay/Server =\"VASPErrorRsp\" type=\"tns:genericResponseType\"> VASP < xs:annotation<> >VASP to MMS: Error response to a any bad request sent to the name=\"senderIDType\"> < xs:sequence name=\"VASPID\" type=\"tns:entityIDType\" minOccurs=\"0\"/> =\"submitReqType\"> < xs:complexContent =\"tns:genericVASPRequestType\"> < xs:sequence name=\"Recipients\" < minOccurs=\"0\"/>default < xs:complexType name=\"replyChargingSize\" type=\"xs:positiveInteger\" 29 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 30 X.S0016-370 v1.0 MMS MM7 Stage 3 =\"deliveryReportReqType <\"> xs:complexContent> < xs:extension base=\"tns:genericRSReqType\"> < xs:sequence < xs:element name name=\"=\"MessageIDRecipient\"\" type type=\"=\"tns:messageIDType\"/> > < xs:complexType< name=\"readReplyReqType\"> xs:complexContent =\"tns:genericRSReqType \"> < < 0\"/> =\"genericRSReqType VASP < xs:annotation \"> >base for all request messages from R/S to > name=\"MM7Version\" type=\" \" minOccurs=\"0\"/> < xs:complexType >Base type for all requests from VASP to R/S xs:element name=\"MM7Version\" type=\"tns:versionType\"/> name =\"SenderIdentification\" type=\"tns:senderIDType\"/> xs:complexType < xs:annotation name =\"genericResponseType\"> >Any simple response sent name=\"MM7Version name =\"Status\" type\" type=\"tns:responseStatusType=\"tns:versionType\"/> \"/> xs:complexType name=\"StatusCode\"> < xs:simpleType base=\"tns:statusCodeType\"/> < =\"StatusText\" type=\"tns:statusTextType\"/> > name=\"Details\" type=\"tns:anyDataType\" minOccurs=\"0\"/> 31 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 32 X.S0016-370 v1.0 MMS MM7 Stage 3 xs:extension ##other\" processContents=\"lax \"/> > >String used to identify the VAS, VASP and >At least one of To,CC,Bcc < xs:sequencexs:annotation > =\"unbounded\"> xs:simpleType >>Message class < xs:restriction \"/> < > =\"priorityType\"> > > =\"relativeOrAbsoluteDateType\"> < xs:annotation >Date which can be relative or absolute =\"xs:dateTime xs:duration\"/> < xs:simpleType name=\"chargedPartyType\"> for transmission < xs:annotation > =\" < > < xs:annotation name=\"versionType\"> >Version number in the format of x.y.z =\"xs:string\"> > =\"statusCodeType\"> 33 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 MMS MM7 Stage 3 X.S0016-370 v1.0 2.7 Exceptions (Informative) None. 34 因篇幅问题不能全部显示，请点此查看更多更全内容