The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 2.1 communication services and how the interfaces and protocols comply to standards.
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 Open Service Access (OSA); Parlay X Web Services; Part 5: Multimedia Messaging (Parlay X 2).
See Table 1-6, "Multimedia Messaging Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.
Table 6-1 Statement of Compliance, Parlay X 2.1 Multimedia Messaging
| Method | Compliant? | Comment |
|---|---|---|
|
Interface: SendMessage |
NA |
NA |
|
SendMessage |
Yes |
NA |
|
GetMessageDeliveryStatus |
Yes |
NA |
|
Interface: ReceiveMessage |
NA |
NA |
|
GetReceivedMessages |
Yes |
NA |
|
GetMessageURIs |
No |
Throws an exception not supported.' |
|
GetMessage |
Yes |
NA |
|
Interface: MessageNotification |
NA |
NA |
|
NotifyMessageReception |
Yes |
NA |
|
NotifyMessageDeliveryReceipt |
Yes |
NA |
|
Interface: MessageNotificationManager |
NA |
NA |
|
StartMessageNotification |
Yes |
NA |
|
StopMessageNotification |
Yes |
NA |
The MM7 plug-in for Parlay for Parlay X 2.1 Multimedia Messaging acts as an MMS VAS Application toward 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.
The plug-in complies to versions of the Multimedia Messaging Service (MMS), 3GPP TS 23.140 specifications listed in Table 1-1, "Audio Call Specification Compliance Table".
Messages are compliant with XSD schemes defined with name space
It also supports the 7-1-0 XSD, adapted to support delivery notifications, Rel5-mm7-1-2.xsd, and 7-1-5 XSD.
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? | Comment |
|---|---|---|
|
Plug-in originated operations: |
NA |
NA |
|
MM7_submit.REQ |
Yes |
NA |
|
MM7_cancel.REQ |
No |
Not used in this context |
|
MM7_delivery_report.RES |
Yes |
NA |
|
MM7_deliver.RES |
Yes |
NA |
|
MM7_replace.REQ |
No |
Not used in this context |
|
MM7_read_reply.RES |
No |
Not used in this context |
|
MM7_VASP_error.RES |
No |
Not used in this context |
|
MMSC originated operations: |
NA |
NA |
|
MM7_submit.RES |
Yes |
NA |
|
MM7_cancel.RES |
No |
Not used in this context |
|
MM7_delivery_report.REQ |
Yes |
NA |
|
MM7_deliver.REQ |
Yes |
NA |
|
MM7_RS_error.RES |
Yes |
NA |
|
MM7_replace.RES |
No |
Not used in this context |
|
MM7_read_reply.REQ |
No |
Not used in this context |
This section describes the MM7 plug-in's compliance with the specification. For the version 6.8.0 specification see:
http://www.3gpp.org/ftp/Specs/html-info/23140.htm
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 |
Yes |
|
MM7Version |
Mandatory |
Yes |
|
MessageType |
Mandatory |
Yes |
|
Sender Identification |
Optional |
Yes-SenderAddress,VASPID,VASID |
|
RecipientAddress |
Mandatory |
Yes |
|
ServiceCode |
Optional |
Yes |
|
LinkedID |
Optional |
No |
|
MessageClass |
Optional |
No |
|
TimeStamp |
Optional |
No |
|
ReplyChargingID |
Optional |
No |
|
EarliestDeliveryTime |
Optional |
No |
|
ExpiryDate |
Optional |
No |
|
DeliveryReport |
Optional |
Yes |
|
ReadReply |
Optional |
No |
|
Priority |
Optional |
Yes |
|
Subject |
Optional |
Yes |
|
ChargedParty |
Optional |
Yes |
|
ChargedPartyID |
Optional |
Yes |
|
DistributionIndicator |
Optional |
No |
|
Content |
Optional |
No |
|
Content-Type |
Mandatory |
Yes |
Table 6-4 Compliance for MM7 Submit Response Operation
| Parameter | Mandatory, Conditional, or Optional | Compliant? |
|---|---|---|
|
TransactionID |
Mandatory |
Yes |
|
MM7Version |
Mandatory |
Yes |
|
Status |
Mandatory |
Yes |
|
MessageID |
Conditional |
Yes |
Table 6-5 Compliance for MM7 Deliver Operation
| Parameter | Mandatory or Optional | Compliant? |
|---|---|---|
|
TransactionID |
Mandatory |
Yes |
|
MM7Version |
Mandatory |
Yes |
|
MMSRelayServerID |
Optional |
Yes |
|
LinkedID |
Optional |
No |
|
Sender |
Mandatory |
Yes |
|
Recipients |
Optional |
Yes |
|
TimeStamp |
Optional |
Yes |
|
ReplyChargingID |
Optional |
No |
|
Priority |
Optional |
Yes |
|
Subject |
Optional |
Yes |
|
Content |
Optional |
Yes |
|
Content-Type |
Mandatory |
Yes |
Table 6-6 Compliance for MM7 Deliver Response Operation
| Parameter | Mandatory or Optional | Compliant? |
|---|---|---|
|
TransactionID |
Mandatory |
Yes |
|
MM7Version |
Mandatory |
Yes |
|
ServiceCode |
Optional |
Yes |
|
Status |
Mandatory |
Yes |