6 Parlay X 2.1 Multimedia Messaging

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 2.1 communication services and how the interfaces and protocols comply 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 ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip for links to the specification.

Table 6-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 mail to URIs.

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

Table 6-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

MM7 v 6.8.0 for Parlay X 2.1 Multimedia Messaging

This section describes the MM7 plug-in's compliance with the specification. See

http://www.3gpp.org/ftp/Specs/html-info/23140.htm

for the version 6.8.0 specification.

Services Gatekeeper supports all mandatory parameters described in the MM7 specification. It also supports some optional parameters through plug-in mbean attributes or as context attributes as part of the Parlay X request.

The plug-in supports the following operations and parameters.

Table 6-3 Compliance for MM7 Submit Operation

Parameter	Mandatory or Optional	Compliant
TransactionID	Mandatory	Y
MM7Version	Mandatory	Y
MessageType	Mandatory	Y
Sender Identification	Optional	Y-SenderAddress,VASPID,VASID
RecipientAddress	Mandatory	Y
ServiceCode	Optional	Y
LinkedID	Optional	N
MessageClass	Optional	N
TimeStamp	Optional	N
ReplyChargingID	Optional	N
EarliestDeliveryTime	Optional	N
ExpiryDate	Optional	N
DeliveryReport	Optional	Y
ReadReply	Optional	N
Priority	Optional	Y
Subject	Optional	Y
ChargedParty	Optional	Y
ChargedPartyID	Optional	Y
DistributionIndicator	Optional	N
Content	Optional	N
Content-Type	Mandatory	Y

Table 6-4 Compliance for MM7 Submit Response Operation

Parameter	Mandatory, Conditional,or Optional	Compliant
TransactionID	Mandatory	Y
MM7Version	Mandatory	Y
Status	Mandatory	Y
MessageID	Conditional	Y

Table 6-5 Compliance for MM7 Deliver Operation

Parameter	Mandatory or Optional	Compliant
TransactionID	Mandatory	Y
MM7Version	Mandatory	Y
MMSRelayServerID	Optional	Y
LinkedID	Optional	N
Sender	Mandatory	Y
Recipients	Optional	Y
TimeStamp	Optional	Y
ReplyChargingID	Optional	N
Priority	Optional	Y
Subject	Optional	Y
Content	Optional	Y
Content-Type	Mandatory	Y

Table 6-6 Compliance for MM7 Deliver Response Operation

Parameter	Mandatory or Optional	Compliant
TransactionID	Mandatory	Y
MM7Version	Mandatory	Y
ServiceCode	Optional	Y
Status	Mandatory	Y

Table 6-7 Compliance for MM7 Delivery Report Operation

Parameter	Mandatory or Optional	Compliant
TransactionID	Mandatory	Y
MM7Version	Mandatory	Y
MMSRelayServerID	Optional	Y
MessageID	Mandatory	Y
Recipient	Mandatory	Y
Sender	Mandatory	Y
Date	Mandatory	Y
MMStatus	Mandatory	Y

Table 6-8 Compliance for MM7 Delivery Report Response Operation

Parameter	Mandatory or Optional	Compliant
TransactionID	Mandatory	Y
MM7Version	Mandatory	Y
Status	Mandatory	Y