# Statement of Compliance

# Parlay X 2.1 Multimedia Messaging

The following chapter describes the standard Oracle Communications Services Gatekeeper communication services communication services and how the interfaces and protocols complies to standards.

- Parlay X 2.1 Multimedia Messaging Statement of compliance
- MM7 v 5.3 for Parlay X 2.1 Multimedia Messaging

## Parlay X 2.1 Multimedia Messaging Statement of compliance

This section describes the standards compliance for the communication services for Parlay X 2.1 Multimedia Messaging:

The Parlay X 2.1 interface complies to ETSI ES 202 391-5 V1.2.1 (2006-10) Open Service Access (OSA); Parlay X Web Services; Part 5: Multimedia Messaging (Parlay X 2).

See http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX21.html for links to the specification.

Table 7-1 Statement of Compliance, Parlay X 2.1 Multimedia Messaging
Method | Compliant (Yes | No) | Comment
--- | --- | ---
Interface: SendMessage
SendMessage | Y |
GetMessageDeliveryStatus | Y |
Interface: ReceiveMessage
GetReceivedMessages | Y |
GetMessageURIs | N | throws an exception ‘not supported’
GetMessage | Y |
Interface: MessageNotification
NotifyMessageReception | Y |
NotifyMessageDeliveryReceipt | Y |
Interface: MessageNotificationManager
StartMessageNotification | Y |
StopMessageNotification | Y |

## MM7 v 5.3 for Parlay X 2.1 Multimedia Messaging

The MM7 plug-in for Parlay for Parlay X 2.1 Multimedia Messaging acts as an MMS VAS Application towards an MMS Relay/Server using the MM7 interface. It connects to the MMS/Relay Server using SOAP 1.1 over HTPP. It supports HTTP Basic Authentication for authentication.

The plug-in itself may act as one single MMS VAS Application, or, alternatively, the Service Provider ID acts as the VASP (Value Added Service Provider) ID and the Application ID/Application Instance Group ID combination acts as the VAS (Value Added Service) ID.

### Standards Compliance

The plug-in complies to 3rd Generation Partnership Project; Technical Specification Group Terminals; Multimedia Messaging Service (MMS); Functional description; Stage 2 (Release 5), 3GPP TS 23.140 V5.3.0. Messages are compliant with XSD schemes defined with name space http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2

It also supports the 7-1-0 XSD, adapted to support delivery notifications, Rel5-mm7-1-2.xsd, and 7-1-5 XSD.

A link to the specification is found on http://www.3gpp.org/ftp/Specs/html-info/23140.htm

The plug-in support MSISDN (E.164) addresses and mailto URIs.

It supports authentication using HTTP Basic Authentication according to HTTP Authentication: Basic and Digest Access Authentication, IETF; RFC 2617.

Table 7-2 Statement of Compliance,MM7 v 5.3 for Parlay X 2.1 Multimedia Messaging
Operation | Compliant (Yes | No) | Comment
--- | --- | ---
Plug-in originated operations:
MM7_submit.REQ | Y |
MM7_cancel.REQ | N | Not used in this context
MM7_delivery_report.RES | Y |
MM7_deliver.RES | Y |
MM7_replace.REQ | N | Not used in this context
MM7_read_reply.RES | N | Not used in this context
MM7_VASP_error.RES | N | Not used in this context
MMSC originated operations:
MM7_submit.RES | Y |
MM7_cancel.RES | N | Not used in this context
MM7_delivery_report.REQ | Y |
MM7_deliver.REQ | Y |
MM7_RS_error.RES | Y |
MM7_replace.RES | N | Not used in this context
MM7_read_reply.REQ | N | Not used in this context