# Statement of Compliance

# Native MM7

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

- Native MM7
- Native MM7 Service Facade Standards Compliance
- Native MM7 Service Enabler Standards Compliance

## Native MM7

This section describes the standards compliance for the communication service for Native MM7.

### Native MM7 Service Facade Standards Compliance

The MM7 Service Facade acts as an MMS Relay/Server. It is used by MMS VAS applications.

The Service Facade 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.

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

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

Table 14-1 Statement of Compliance Native MM7Service Facade
Operation | Compliant (Yes | No) | Comment
--- | --- | ---
MMS VAS application originated operations:
MM7_submit.REQ | Y |
MM7_cancel.REQ | N |
MM7_delivery_report.RES | Y |
MM7_deliver.RES | Y |
MM7_replace.REQ | N |
MM7_read_reply.RES | Y |
MM7_VASP_error.RES | N |
MM7 Service Facade originated operations:
MM7_submit.RES | Y |
MM7_cancel.REQ | N |
MM7_delivery_report.REQ | Y |
MM7_deliver.REQ | Y |
MM7_replace.RES | N |
MM7_read_reply.REQ | Y |
MM7_RS_error.RES | N |

### Native MM7 Service Enabler Standards Compliance

The Native MM7 Service Enabler acts as an MMS VAS application.

The Service Enabler 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-0

It supports the 7-1-0 XSD, adapted to support delivery notifications and 7-1-2 XSD.

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

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

Table 14-2 Statement of Compliance Native MM7Service Enabler
Operation | Compliant (Yes | No) | Comment
--- | --- | ---
MM7 Service Enabler originated operations:
MM7_submit.REQ | Y |
MM7_cancel.REQ | N |
MM7_delivery_report.RES | Y |
MM7_deliver.RES | Y |
MM7_replace.REQ | N |
MM7_read_reply.RES | Y |
MM7_VASP_error.RES | Y |
MMSC originated operations:
MM7_submit.RES | Y |
MM7_cancel.RES | Y |
MM7_delivery_report.REQ | Y |
MM7_deliver.REQ | Y |
MM7_replace.RES | N |
MM7_read_reply.REQ | Y |
MM7_RS_error.RES | Y |