Oracle® Communications Services Gatekeeper

Statement of Compliance

Release 6.1

E64634-01

September 2016

Oracle Communications Services Gatekeeper Statement of Compliance, Release 6.1

E64634-01

Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

1 Services Gatekeeper Compliance Reference Table

- Communication Service Specification Compliance

2 OAuth Compliance

- Supported OAuth Specification

- Supported SAML Specification

3 Parlay X Web Services Address List Management Compliance

- Parlay X Web Services Address List Management

- Standards Compliance

4 Parlay X 2.1 Audio Call Compliance

- Parlay X 2.1 Audio Call Statement of Compliance

- SIP for Parlay X 2.1 Audio Call

- Standards Compliance

5 Parlay X 2.1 Call Notification Compliance

- Parlay X 2.1 Call Notification Statement of Compliance

- SIP for Parlay X 2.1 Call Notification

- Standards Compliance

6 Parlay X 2.1 Multimedia Messaging Compliance

- Parlay X 2.1 Multimedia Messaging Statement of compliance

- MM7 Parlay X 2.1 Multimedia Messaging

- Standards Compliance

- MM7 v 6.8.0 for Parlay X 2.1 Multimedia Messaging

7 Parlay X 2.1 Presence Compliance

- Parlay X 2.1 Presence

- SIP for Parlay X 2.1 Presence

- Standards Compliance

8 Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance

- Parlay X 2.1 Short Messaging Statement of compliance

- SMPP v3.4/5.0 for Parlay X 2.1/Extended Web Services Binary SMS

- Standards Compliance

9 Parlay X 2.1 Terminal Location/SIP Compliance

- Parlay X 2.1 Terminal Location

- Understanding Parlay X 2.1 Terminal Location Latitude and Longitude Value Precision

- SIP for Parlay X 2.1 Terminal Location

- Standards Compliance

10 Parlay X 2.1 Terminal Status Compliance

- Parlay X 2.1 Terminal Status

- SS7/MAP Terminal Status

- Standards Compliance

11 Parlay X 2. 1 Third Party Call Compliance

- Parlay X 2.1 Third Party Call Statement of compliance

- SIP for Parlay X 2.1 Third Party Call

- Standards Compliance

- SS7/INAP for Parlay X 2.1 Third Party Call

- Standards Compliance

12 Parlay X 3.0 Application Subscription Management Compliance

- Application Subscription Management Statement of Compliance

- Supported Operations

13 Parlay X 3.0 Device Capabilities and Configuration Compliance

- Parlay X 3.0 Device Capabilities and Configuration

- LDAP for Device Capabilities and Configuration

- Standards Compliance

14 Parlay X 3.0 Payment Compliance

- Parlay X 3.0 Payment

- Standards Compliance

- Diameter for Parlay X 3.0 Payment

- Standards Compliance

15 Parlay X 4.0 Application-Driven Quality of Service /Diameter Compliance

- Parlay X 4.0 Application-Driven QoS Statement of Compliance

- Diameter Gx Statement of Compliance

- Diameter Rx Statement of Compliance

- Standards Compliance

- Supported Rx AA-Request AVPs

- Supported Rx AA-Answer AVPs

- Supported Rx Re-Auth-Request AVPs

- Supported Rx Re-Auth-Answer AVPs

- Supported Rx Session-Termination-Request AVPs

- Supported Rx Session-Termination-Answer AVPs

- Supported Rx Abort-Session-Request AVPs

- Supported Rx Abort-Session-Answer AVPs

- Non-Standard Supported Diameter AVPs

16 Extended Web Services WAP Push Compliance

- Extended Web Services WAP Push

- WAP Push for Extended Web Services WAP Push

- Standards Compliance

17 Extended Web Services Subscriber Profile Compliance

- Extended Web Services Subscriber Profile

- LDAP for Extended Web Services Subscriber Profile

- Standards Compliance

18 Native MM7 Compliance

- Native MM7

- Native MM7 Service Facade Standards Compliance

- Native MM7 Service Enabler Standards Compliance

19 Native SMPP Compliance

- Native SMPP

- Native SMPP Service Facade Standards Compliance

- Native SMPP Service Enabler Standards Compliance

- Native SMPP Version 5.1 Standards Compliance

20 Native UCP Compliance

- Native UCP

21 OneAPI Multimedia Messaging Compliance

- OneAPI Multimedia Messaging Interface

- Standards Compliance - RESTful Bindings

- Standards Compliance - RESTful Bindings Schema

- RESTful Bindings Data Structure Compliance

22 OneAPI Terminal Location Interface Compliance

- OneAPI Terminal Location Interface

- Standards Compliance - RESTful Bindings

- Standards Compliance - RESTful Bindings Schema

- RESTful Bindings Data Structure Compliance

23 OneAPI Payment Compliance

- OneAPI Payment Interface

- Standards Compliance - RESTful Bindings

- Standards Compliance - RESTful Bindings Schema

- RESTful Bindings Data Structure Compliance

24 OneAPI Short Messaging Compliance

- OneAPI Short Messaging Interface

- Standards Compliance - RESTful Bindings

- Standards Compliance - RESTful Bindings Schema

- RESTful Bindings Data Structure Compliance

25 RESTful Anonymous Customer Reference Compliance

- Anonymous Customer Reference Specification

Preface

This document is a statement of compliance for the specifications supported by the Oracle Communications Services Gatekeeper communication services and other features.

Audience

This document is for system administrators who manage Services Gatekeeper, as well as managers, support engineers, sales, and marketing.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in this documentation set:

- Oracle Communications Services Gatekeeper Application Developer's Guide

- Oracle Communications Services Gatekeeper Communication Service Reference Guide

- Oracle Communications Services Gatekeeper Concepts

- Oracle Communications Services Gatekeeper OAuth Guide

1 Services Gatekeeper Compliance Reference Table

This chapter serves as a quick-reference to the specifications that the various Oracle Communications Services Gatekeeper components support.

Communication Service Specification Compliance

Table 1-1 lists the Services Gatekeeper audio call communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-1 Audio Call Specification Compliance Table

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Audio Call

API: Parlay X 2.1 Audio Call/SIP

API Interface: SOAP

ETSI ES 202 391-11 V1.2.1 (2006-12) Open Service Access (OSA); Parlay X Web Services; Part 11: Audio Call (Parlay X 2), available from the 3GPP website:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-11/29199-11-650.zip

Yes. See Parlay X 2.1 Audio Call for details.

SIP

RFC 3261, available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes. See "Services Gatekeeper Compliance Reference Table" for details.

Audio Call

API: RESTful Audio Call / SIP

API Interface: REST

NA

NA

SIP

RFC 3261 available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes. See "Parlay X 2.1 Audio Call Compliance" for details.

Table 1-2 lists the Services Gatekeeper call notification communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-2 Call Notification Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Call Notification

API: Parlay X 2.1 Call Notification/SIP

API Interface: SOAP

ETSI ES 202 391-3 V1.2.1 (2006-12) Open Service Access (OSA); Parlay X Web Services; Part 3: Call Notification (Parlay X 2), available from the 3GPP website:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

Yes. See "Parlay X 2.1 Call Notification Compliance" for details.

SIP

RFC 3261, available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes. See "Parlay X 2.1 Call Notification Compliance" for details.

Call Notification

API: RESTful Call Notification/SIP

API Interface: REST

NA

NA

SIP

RFC 3261, available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes. See "Parlay X 2.1 Call Notification Compliance" for details.

Table 1-3 lists the Services Gatekeeper cross cutting services communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-3 Cross Cutting Services Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Cross Cutting Services

API: Parlay X 3.0 Address List Management Interface

API Interface: SOAP

Parlay X Web Services Part 13: Address List Management (3GPP TS 29.199-13 version 7.0.2 Release 7, available from the ETSI website:

http://www.etsi.org/deliver/etsi_ts/129100_129199/12919913/07.00.02_60/ts_12919913v070002p.pdf

Yes

NA - no network interface for this API

NA

See "Parlay X Web Services Address List Management Compliance"

Cross Cutting Services

API: RESTful Anonymous Customer Reference

API Interface: REST

Anonymous Customer Reference RESTful NetAPI, available from these websites:

API:

http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/rest-netapi-acr-v1-0

Specification:

http://technical.openmobilealliance.org/Technical/release_program/docs/REST_NetAPI_ACR/V1_0-20130625-C/OMA-TS-REST_NetAPI_ACR-V1_0-20130625-C.pdf

Yes

NA - no network interface for this API

NA

NA

Table 1-4 lists the Services Gatekeeper device capabilities communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-4 Device Capabilities Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Device Capabilities

API: Parlay X 3.0 Device Capabilities/LDAPv3

API Interface: SOAP

ETSI ES 202 504-18 V1.1.1(2008-05), available from the ETSI website:

http://www.etsi.org/deliver/etsi_es/202500_202599/20250418/01.01.01_60/es_20250418v010101p.pdf">>http://www.etsi.org/deliver/etsi_es/202500_202599/20250418/01.01.01_60/es_20250418v010101p.pdf

Partial, see "Parlay X 3.0 Device Capabilities and Configuration Compliance" for details

LDAP

LDAP v3, RFC 4510, available from the IETF website:

http://tools.ietf.org/html/rfc4510

Partial, see "Parlay X 3.0 Device Capabilities and Configuration Compliance" for details

Device Capabilities

API: RESTful Device Capabilities / LDAP

API Interface: REST

NA

NA

LDAP

LDAP v3, RFC 4510, available from the IETF website:

http://tools.ietf.org/html/rfc4510

Partial, see "Parlay X 3.0 Device Capabilities and Configuration Compliance" for details

Table 1-5 lists the Services Gatekeeper JTAPI communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-5 JTAPI Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

JTAPI

RESTful Web Service for JTAPI

Cisco UCM Driver

JTAPI v 1.2

Partial. See "RESTful Web Service for JTAPI" in Communication Services Reference Guide for details.

Cisco UCM Driver. See "RESTful Web Service for JTAPI" in Communication Services Reference Guide for details.

JTAPI v 1.2

Partial. See "RESTful Web Service for JTAPI" in Communication Services Reference Guide for details.

JTAPI

RESTful Web Service for JTAPI

Avaya JTAPI Driver

JTAPI v 1.4

Partial. See "RESTful Web Service for JTAPI" in Communication Services Reference Guide for details.

Avaya Driver.

See "RESTful Web Service for JTAPI" in Communication Services Reference Guide for details.

JTAPI v 1.4

Partial. See "RESTful Web Service for JTAPI" in Communication Services Reference Guide for details.

Table 1-6 lists the Services Gatekeeper multimedia messaging communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-6 Multimedia Messaging Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Multimedia Messaging

API: Parlay X 2.1 Multimedia Messaging/

API Interface: SOAP

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), available from the IETF website

http://www.ietf.org/rfc/rfc3261.txt

Yes. See "Parlay X 2.1 Multimedia Messaging Compliance" for details.

MM7 Schema ver: REL-5-MM7-1-0

3GPP TS 23.140 V5.3.0, available from the IETF website:

http://www.qtc.jp/3GPP/Specs/31121-530.pdf

Partial. See "Parlay X 2.1 Multimedia Messaging Compliance" for details.

Multimedia Messaging

API: Parlay X 2.1 Multimedia Messaging/MM7

API Interface: SOAP

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), available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes. See "Parlay X 2.1 Multimedia Messaging Compliance" for details

MM7 Schema ver: REL-5-MM7-1-2

3GPP TS 23.140 V5.5.0, available from the 3GPP website:

http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/23140-550.zip

Partial, see "Parlay X 2.1 Multimedia Messaging Compliance" for details.

Multimedia Messaging

API: Parlay X 2.1 Multimedia Messaging/MM7

API Interface: SOAP

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), available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes. See "Parlay X 2.1 Multimedia Messaging Compliance" for details

MM7 Schema ver: REL-5-MM7-1-3

3GPP TS 23.140 V5.6.0, available from the 3GPP website:

http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/23140-560.zip

Partial, see "Parlay X 2.1 Multimedia Messaging Compliance" for details

Multimedia Messaging

API: Parlay X 2.1 Multimedia Messaging/MM7

API Interface: SOAP

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), available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes. See "Parlay X 2.1 Multimedia Messaging Compliance" for details

MM7 Schema ver: REL-5-MM7-1-5

3GPP TS 23.140 V5.10.0, available from the IETF website:

http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/23140-5a0.zip

Partial, see "Parlay X 2.1 Multimedia Messaging Compliance" for details

Multimedia Messaging

API: Parlay X 2.1 Multimedia Messaging/MM7

API Interface: SOAP

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), available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes. See "Parlay X 2.1 Multimedia Messaging Compliance" for details

MM7Schema ver: REL-6-MM7-1-4

3GPP TS 23.140 V6.8.0, available from the 3GPP website:

http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/23140-680.zip

Yes, see "Parlay X 2.1 Multimedia Messaging Compliance" for details

Table 1-7 lists the Services Gatekeeper eMail communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-7 EMail Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

eMail

API: Parlay X 2.1 Multimedia Messaging/SMTP, POP3, and IMAP

API Interface: SOAP

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), available from the 3GPP website:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

Yes, see "Parlay X 2.1 Multimedia Messaging Compliance" for details

STMP

RFC 2821, available from the IETF website:

http://www.ietf.org/rfc/rfc2821.txt

Yes

eMail

API: Parlay X 2.1 Multimedia Messaging/SMTP, POP3, and IMAP

API Interface: SOAP

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), available from the 3GPP website:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

Yes, see "Parlay X 2.1 Multimedia Messaging Compliance" for details

POP

POP Version3, RFC 1939, available from the IETF website: https://tools.ietf.org/html/rfc1939l

https://tools.ietf.org/html/rfc1939

Yes

eMail

API: Parlay X 2.1 Multimedia Messaging/SMTP, POP3, and IMAP

API Interface: SOAP

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), available from the 3GPP website:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

Yes, see "Parlay X 2.1 Multimedia Messaging Compliance" for details

IMAP

RFC 1739, available from the IETF website: http://www.rfc-archive.org/getrfc.php?rfc=1730

http://www.rfc-archive.org/getrfc.php?rfc=1730

and RFC 2177

https://tools.ietf.org/html/rfc2177

Yes

eMail

API: RESTful eMail

API Interface: REST

NA

NA

Same as above i.e. SMTP, POP and IMAP is supported

NA

NA

Table 1-8 lists the Services Gatekeeper location communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-8 Location Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Location

API: OneAPI 2.0 Terminal Location

API Interface: REST

GSMA OneAPI TL v2.0, available from these websites:

http://technical.openmobilealliance.org/Technical/release_program/docs/ParlayREST/V2_0-20120724-A/OMA-TS-ParlayREST_TerminalLocation-V1_1-20120724-A.pdf

the API here:

http://technical.openmobilealliance.org/Technical/technical-information/oma-api-program/oma-api-inventory/api-details?API_ID=65

and the schema here:

http://technical.openmobilealliance.org/Technical/release_program/docs/ParlayREST/V2_0-20120724-A/OMA-SUP-XSD_rest_terminallocation-V1_1-20120724-A.txt

Yes, see "OneAPI Terminal Location Interface Compliance" for details.

MLP

Location Inter-operability Forum (LIF) Mobile Location Protocol, LIF TS 101 Specification Version 3.0.0, available from these websites:

http://technical.openmobilealliance.org/tech/affiliates/LicenseAgreement.asp?DocName=/lif/LIF-TS-101-v3.0.0.zip

and Mobile Location Protocol 3.2 Candidate Version 3.2 Open Mobile Alliance, OMA-TS-MLP-V3_2-20051124-C(MLP 3.2.0), available from this location:

https://docbox.etsi.org/STF/Archive/STF321_TISPAN3_EC_Emergency_Call_Location/Public/Library/OMA%20Documents/OMA%20Mobile%20Location%20Protocol%20V3_2-20051124-c.pdf

Yes, see "OneAPI Terminal Location Interface Compliance" for details.

Table 1-9 lists the Services Gatekeeper payment communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-9 Payment Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Payment

API: Parlay X 3.0 Payment/Diameter

API Interface: SOAP

API Interface: REST

ETSI ES 202 504-6 V1.1.1 (2008-05), Open Service Access (OSA);

Parlay X Web Services;

Part 6: Payment

(Parlay X 3), available from the ETSI website:

http://www.etsi.org/deliver/etsi_es/202500_202599/20250406/01.01.01_60/es_20250406v010101p.pdf

Yes, see "Parlay X 3.0 Payment Compliance" for details

Diameter Ro

Diameter Base Protocol, RFC3588 and Diameter Credit-Control Application, RFC4006, available from the IETF website:

http://www.ietf.org/rfc/rfc3588.txt

and

http://www.ietf.org/rfc/rfc4006.txt

Yes, see "Parlay X 3.0 Payment Compliance" for details

Payment

API: RESTful Payment / Diameter

API Interface: REST

NA

NA

Diameter Ro

Diameter Base Protocol, RFC3588 and Diameter Credit-Control Application, RFC4006, available from the IETF website:

http://www.ietf.org/rfc/rfc3588.txt

and

http://www.ietf.org/rfc/rfc4006.txt

Yes

Payment

API: OneAPI 2.0 Payment

API Interface: REST

GSMA OneAPI V2.0, available from these websites:

API:

http://technical.openmobilealliance.org/Technical/technical-information/oma-api-program/oma-api-inventory/api-details?API_ID=64

Specification:

http://technical.openmobilealliance.org/Technical/release_program/docs/ParlayREST/V2_0-20120724-A/OMA-TS-ParlayREST_Payment-V1_1-20120724-A.pdf

Schema:

http://technical.openmobilealliance.org/Technical/release_program/docs/ParlayREST/V2_0-20120724-A/OMA-SUP-XSD_rest_payment-V1_1-20120724-A.txt

Yes, see "OneAPI Payment Compliance" for details

Diameter Ro

Diameter Base Protocol, RFC3588 and Diameter Credit-Control Application, RFC4006, available from the IETF website:

http://www.ietf.org/rfc/rfc3588.txt

and

http://www.ietf.org/rfc/rfc4006.txt

Yes

Table 1-10 lists the Services Gatekeeper presence communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-10 Presence Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Presence

API: Parlay X 2.1 Presence/SIP

API Interface: SOAP

ETSI ES 202 391-14 V1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 14: Presence (Parlay X 2) available from the 3GPP website:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

Partial, see "Parlay X 2.1 Presence Compliance" for details

SIP

RFC 3261, available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes, see "Parlay X 2.1 Presence Compliance" for details

Table 1-11 lists the Services Gatekeeper quality of service communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-11 Quality of Service Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Quality of Service (QoS)

API*: Extended Web Service Quality of Service / Diameter

API Interface: REST

NA

NA

Diameter Rx

Policy and Charging Control over Rx reference point (3GPP TS 29.214 version 10.6.0 Release 10), available from the ETSI website:

http://www.etsi.org/deliver/etsi_ts/129200_129299/129214/10.06.00_60/ts_129214v100600p.pdf

Yes

Table 1-12 lists the Services Gatekeeper short messaging communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-12 Short Messaging Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Short Messaging

API: Parlay X 2.1 Short Messaging/SMPP

API Interface: SOAP

ETSI ES 202 391-4 V1.2.1 (2006-12) Open Service Access (OSA); Parlay X Web Services; Part 4: Short Messaging (Parlay X 2), available from the 3GPP website:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

Yes, see "Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance" for details

SMPP

Short Message Peer to Peer Protocol Specification v3.4

12-Oct-1999 Issue 1.2, available from the Open SMPP website:

http://opensmpp.org/specs/SMPP_v3_4_Issue1_2.pdf

Partial, see "Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance" for details

Short Messaging

API: Parlay X 2.1 Short Messaging/SMPP

API Interface: SOAP

ETSI ES 202 391-4 V1.2.1 (2006-12) Open Service Access (OSA); Parlay X Web Services; Part 4: Short Messaging (Parlay X 2), available from the 3GPP website:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

Yes, see "Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance" for details

SMPP

Short Message Peer-to-Peer Protocol Specification, Version 5.0 available from the Connection Software website:

http://www.csoft.co.uk/documents/smppv50.pdf

Partial, see "Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance" for details

Short Messaging

API: RESTful Short Messaging

API Interface: REST

NA

NA

SMPP

Short Message Peer-to-Peer Protocol Specification, Version 5.0, available from the Connection Software website:

http://www.csoft.co.uk/documents/smppv50.pdf

Partial, see "Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance" for details

Short Messaging

API: RESTful Binary Short Messaging

API Interface: REST

NA

NA

Same as Parlay X 2.1 SMS above. Both SMPP 3.4 and 5.0 are supported (partially)

Short Message Peer-to-Peer Protocol Specification, Versions 3.4 and 5.0, are supported (partially), available from the Open SMPP website:

http://opensmpp.org/specs/SMPP_v3_4_Issue1_2.pdf

and the Connection Software website:

http://www.csoft.co.uk/documents/smppv50.pdf

Partial, see "Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance" for details. Both SMPP 3.4 and 5.0 are partially supported.

Short Messaging

API: RESTful Binary Short Messaging

API Interface: REST

NA

NA

Same as Parlay X 2.1 SMS. Both SMPP 3.4 and 5.0 are supported (partially)

Short Message Peer-to-Peer Protocol Specification, Versions 3.4 and 5.0, are supported (partially), available from the Open SMPP website:

http://opensmpp.org/specs/SMPP_v3_4_Issue1_2.pdf

and the Connection Software website:

http://www.csoft.co.uk/documents/smppv50.pdf

Partial. See "Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance" for details. Both SMPP 3.4 and 5.0 are partially supported.

Short Messaging

API: OneAPI 2.0 Short Messaging

API Interface: REST

SMS RESTful API available from the GSMS website:

http://technical.openmobilealliance.org/Technical/technical-information/oma-api-program/oma-api-inventory/api-details?API_ID=62

The specification is available from this Open Mobile Alliance website:

http://technical.openmobilealliance.org/Technical/release_program/docs/ParlayREST/V2_0-20120724-A/OMA-TS-ParlayREST_ShortMessaging-V1_1-20120724-A.pdf

and the schema is available from this Open Mobile Alliance website:

http://technical.openmobilealliance.org/Technical/release_program/docs/ParlayREST/V2_0-20120724-A/OMA-SUP-XSD_rest_sms-V1_1-20120724-A.txt

Yes

Same as Parlay X 2.1 SMS. Both SMPP 3.4 and 5.0 are supported (partially)

Short Message Peer-to-Peer Protocol Specification, Versions 3.4 and 5.0, are supported (partially), available from the Open SMPP website:

http://opensmpp.org/specs/SMPP_v3_4_Issue1_2.pdf

and the Connection Software website:

http://www.csoft.co.uk/documents/smppv50.pdf

Partially. See "Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance". Both SMPP 3.4 and 5.0 are partially supported.)

Short Messaging

API: Native SMPP

API Interface: SMPP

Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2, available from the Open SMPP website:

http://opensmpp.org/specs/SMPP_v3_4_Issue1_2.pdf

Partial, see "Native SMPP Compliance" for details.

SMPP

Short Message Peer to Peer Protocol Specification v3.4, available from the Open SMPP website

http://opensmpp.org/specs/SMPP_v3_4_Issue1_2.pdf

Partial, see "Native SMPP Compliance" for details.

Short Messaging

API: Native UCP

API Interface: UCP

Short Message Service Centre EMI-UCP, versions 4.0, 4.6, 5.0. These EMI-UCP specifications are no longer publicly available.

Partial, see "Native SMPP Compliance" for details

SMPP

Short Message Peer to Peer Protocol Specification v3.4, available from the Open SMPP website:

http://opensmpp.org/specs/SMPP_v3_4_Issue1_2.pdf

Partial, see "Native SMPP Compliance" for details

Short Messaging

API: Extended Web Services Binary SMS/SMPP

API Interface: SOAP

NA

NA

SMPP

Short Message Peer-to-Peer Protocol Specification, Version 5.0, available from the Connection Software website:

http://www.csoft.co.uk/documents/smppv50.pdf

Partial, see "Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance" for details

Table 1-13 lists the Services Gatekeeper subscriber profile communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-13 Subscriber Profile Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Subscriber Profile

API: Extended Web Services Subscriber Profile/LDAPv3

API Interface: SOAP

NA

NA

LDAP

LDAP v3, RFC 4510, available from the IETF website:

http://tools.ietf.org/html/rfc4510">>http://tools.ietf.org/html/rfc4510

Partial, see "Extended Web Services Subscriber Profile Compliance" for details

Subscriber Profile

API: RESTful Subscriber Profile / LDAP

API Interface: REST

NA

NA

LDAP

LDAP v3, RFC 4510, available from the IETF website:

http://tools.ietf.org/html/rfc4510">>http://tools.ietf.org/html/rfc4510

Partial, see "Extended Web Services Subscriber Profile Compliance" for details

Table 1-14 lists the Services Gatekeeper subscription management communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-14 Subscription Management Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Subscription Management

API: OMA Application Subscription Management

API Interface: REST

OMS GSSM V1.0, available from the Open Mobile Alliance website:

http://technical.openmobilealliance.org/Technical/release_program/gssm_v1_0.aspx

Partial

REST

OMS GSSM V1.0, available from the Open Mobile Alliance website

http://technical.openmobilealliance.org/Technical/release_program/gssm_v1_0.aspx

Partial, see "Parlay X 3.0 Application Subscription Management Compliance" for details

Table 1-15 lists the Services Gatekeeper terminal Status communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-15 Terminal Status Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Terminal Status (deprecated)

API: Parlay X 2.1 Terminal Status/MAP

API Interface: SOAP

ETSI ES 202 391-8 V1.3.1 (2008-05), Open Service Access (OSA); Parlay X Web Services; Part 8: Terminal Status (Parlay X 2), available from the 3GPP website:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

Yes

MAP

MAP 3.1, available from the ETSI website:

http://www.etsi.org/deliver/etsi_ts/129000_129099/129002/04.18.00_60/ts_129002v041800p.pdf

Yes, see "Parlay X 2.1 Terminal Status Compliance" for details.

Terminal Status

API: Parlay X 2.1 Terminal Status/SIP

API Interface: SOAP

ETSI ES 202 391-8 V1.3.1 (2008-05), Open Service Access (OSA); Parlay X Web Services; Part 8: Terminal Status (Parlay X 2), available from the 3GPP website:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

Yes

SIP

RFC 3261, available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes

Terminal Status

API: RESTful Terminal Status / SIP

API Interface: REST

NA

NA

SIP

RFC 3261, available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes

Table 1-16 lists the Services Gatekeeper third party call communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-16 Third Party Call Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

Third Party Call

API: RESTful Third Party Call/SIP

API Interface: REST

NA

NA

SIP

RFC 3261, available from the IETF website:

http://www.ietf.org/rfc/rfc3261.txt

Yes

Third Party Call

API: Parlay X 2.1 Third Party Call/SIP

API Interface: SOAP

ETSI ES 202 391-2 V1.2.1 Open Service Access (OSA); Parlay X Web Services; Part 2: Third Party Call (Parlay X 2), available from

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

Yes, see "Parlay X 2. 1 Third Party Call Compliance" for details.

SIP

RFC 3261, available from

http://www.ietf.org/rfc/rfc3261.txt

Yes, see "Parlay X 2. 1 Third Party Call Compliance" for details.

Table 1-17 lists the Services Gatekeeper WAP push communication services, and links to the specifications they support and the chapters that have compliance details.

Table 1-17 WAP Push Communication Service Specifications

Service Type

Specification

Compliant?

Network Interface

Specification

Compliant?

WAP Push

API: Extended Web Services WAP Push/PAP

API Interface: SOAP

NA

NA

PAP

Push Access Protocol, WAP Forum, WAP-247-PAP-20010429-a available from

http://technical.openmobilealliance.org/tech/affiliates/wap/wap-247-pap-20010429-a.pdf

Partial, see "Extended Web Services WAP Push Compliance" for details.

WAP Push

API: RESTful WAP Push / PAP

API Interface: REST

NA

NA

PAP

Push Access Protocol, WAP Forum, WAP-247-PAP-20010429-a available from

http://technical.openmobilealliance.org/tech/affiliates/wap/wap-247-pap-20010429-a.pdf

Partial, see "Extended Web Services WAP Push Compliance" for details

2 OAuth Compliance

This chapter lists the security-related specifications that Oracle Communications Services Gatekeeper supports.

Supported OAuth Specification

OAuth 2.0 is an open source Web authorization protocol developed by the Internet Engineering Task Force (IETF). For detailed specifications and more information see the IETF website:

http://tools.ietf.org/html/rfc6749

Supported SAML Specification

See ”SAML APIs” in Oracle Fusion Middleware Programming Security for Oracle WebLogic Server 12c for the SAML specification that WebLogic Server (and by definition Services Gatekeeper) supports.

3 Parlay X Web Services Address List Management Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X Web Services Application Subscription Management communication service and how the interfaces and protocols comply to standards.

Parlay X Web Services Address List Management

This section describes the standards compliance for the Parlay X Web Services Part 13: Address List Management (3GPP TS 29.199-13 version 7.0.2 Release 7) communication service.

Standards Compliance

The plug-in complies with 3GPP TS 29.199-13 version 7.0.2 Release 7.

See Table 1-3, "Cross Cutting Services Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 3-1, Table 3-2, and Table 3-3 list the supported operations for the specification interfaces.

Table 3-1 Address List Management GroupManagement Interface Operations

Compliant
(Yes | No)

Operation

Yes

createGroup

Yes

deleteGroup

Yes

queryGroups

Yes

setAccess

Yes

queryAccess

Table 3-2 Address List Management Group Interface Operations

Compliant
(Yes | No)

Operation

Yes

addMember

Yes

deleteMember

Yes

deleteMembers

Yes

queryMembers

Yes

addGroupAttribute

Yes

deleteGroupAttribute

Yes

queryGroupAttributes

Yes

addGroupMemberAttribute

Yes

deleteGroupMemberAttribute

Yes

queryGroupMemberAttributes

Table 3-3 Address List Management Member Interface Operations

Compliant
(Yes | No)

Operation

Yes

addMemberAttribute

Yes

queryMemberAttributes

Yes

deleteMemberAttribute

4 Parlay X 2.1 Audio Call Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 2.1 Audio Call communication service and how the interfaces and protocols comply to standards.

Parlay X 2.1 Audio Call Statement of Compliance

This section describes the standards compliance for the Audio Call communication services for Parlay X 2.1 Audio Call:

The Parlay X 2.1 interface complies with ETSI ES 202 391-11 Open Service Access (OSA); Parlay X Web Services; Part 11: Audio Call (Parlay X 2).

See Table 1-1, "Audio Call Specification Compliance Table" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 4-1 lists the Parlay X 2.1 Audio Call methods that Services Gatekeeper supports.

Table 4-1 Statement of Compliance, Parlay X 2.1 Audio Call

Method

Compliant

Comment

Interface: Audio Call

NA

NA

PlayAudioMessage()

Yes

NA

GetMessageStatus()

Yes

NA

EndMessage()

Yes

NA

SIP for Parlay X 2.1 Audio Call

The SIP plug-in for Parlay X 2.1 Audio Call is an integration plug-in that utilizes the Oracle WebLogic SIP Server to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in WebLogic SIP Server. The SIP Servlet uses the SIP API provided by the WebLogic SIP server, which in its turn converts the API calls to SIP messages.

Standards Compliance

The SIP servlet uses the WebLogic SIP server, which conforms to RFC 3261. See Table 1-1, "Audio Call Specification Compliance Table" for the name of the supported specification and a link to its location.

Table 4-2 lists the messages that Parlay X 2.1 Audio Call SIP messages and responses that Services Gatekeeper supports.

Table 4-2 Statement of Compliance, SIP for Parlay X 2.1 Audio Call

Message/Response

Compliant?

Comment

REGISTER

NA

Not used in the context.

INVITE

Yes

NA

ACK

Yes

NA

CANCEL

Yes

NA

BYE

Yes

NA

OPTIONS

NA

Not used in the context.

INFO

NA

Not used in the context.

100 Trying

Yes

NA

180 Ringing

Yes

NA

181 Call Is Being Forwarded

NA

Not used in the context.

182 Queued

NA

Not used in the context.

183 Session Progress

NA

Not used in the context.

200 OK

Yes

NA

300 Multiple Choices

Yes

Not used in the context.

301 Moved Permanently

Yes

Not used in the context.

302 Moved Temporarily

Yes

Not used in the context.

305 Use Proxy

Yes

Not used in the context.

380 Alternative Service

Yes

Not used in the context.

400 Bad Request

Yes

Treated as an error.

401 Unauthorized

Yes

Treated as an error.

402 Payment Required

Yes

Treated as an error.

403 Forbidden

Yes

Treated as an error.

404 Not Found

Yes

Treated as an error.

405 Method Not Allowed

Yes

Treated as an error.

406 Not Acceptable

Yes

Treated as an error.

407 Proxy Authentication Required

Yes

Treated as an error.

408 Request Timeout

Yes

Treated as an error.

410 Gone

Yes

Treated as an error.

413 Request Entity Too Large

Yes

Treated as an error.

414 Request-URI Too Long

Yes

Treated as an error.

415 Unsupported Media Type

Yes

Treated as an error.

416 Unsupported URI Scheme

Yes

Treated as an error.

420 Bad Extension

Yes

Treated as an error.

421 Extension Required

Yes

Treated as an error.

423 Interval Too Brief

Yes

Treated as an error.

480 Temporarily Unavailable

Yes

Treated as an error.

481 Call/Transaction Does Not Exist

Yes

Treated as an error.

482 Loop Detected

Yes

Treated as an error.

483 Too Many Hops

Yes

Treated as an error.

484 Address Incomplete

Yes

Treated as an error.

485 Ambiguous

Yes

Treated as an error.

486 Busy Here

Yes

Treated as an error.

487 Request Terminated

Yes

Treated as an error.

488 Not Acceptable Here

Yes

Treated as an error.

491 Request Pending

Yes

Treated as an error.

493 Undecipherable

Yes

Treated as an error.

500 Server Internal Error

Yes

Treated as an error.

501 Not Implemented

Yes

Treated as an error.

502 Bad Gateway

Yes

Treated as an error.

503 Service Unavailable

Yes

Treated as an error.

504 Server Time-out

Yes

Treated as an error.

505 Version Not Supported

Yes

Treated as an error.

513 Message Too Large

Yes

Treated as an error.

600 Busy Everywhere

Yes

Treated as an error.

603 Decline

Yes

Treated as an error.

604 Does Not Exist Anywhere

Yes

Treated as an error.

606 Not Acceptable

Yes

Treated as an error.

5 Parlay X 2.1 Call Notification Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 2.1 Call Notification communication service and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Call Notification Statement of Compliance

- SIP for Parlay X 2.1 Call Notification

Parlay X 2.1 Call Notification Statement of Compliance

This section describes the standards compliance for the communication services for Parlay X 2.1 Call notification:

The Parlay X 2.1 interface complies to ETSI ES 202 391-3 Open Service Access (OSA); Parlay X Web Services; Part 3: Call Notification (Parlay X 2).

See Table 1-2, "Call Notification Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 5-1 Statement of Compliance, Parlay X 2.1 Call Notification

Method

Compliant?

Comment

Interface: CallDirection

NA

NA

handleBusy

Yes

NA

handleNotReachable

Yes

NA

handleNoAnswer

Yes

NA

handleCalledNumber

Yes

NA

Interface: CallNotification

NA

NA

notifyBusy

Yes

NA

notifyNotReachable

Yes

NA

notifyNoAnswer

Yes

NA

notifyCalledNumber

Yes

NA

Interface: CallDirectionManager

NA

NA

startCallDirectionNotification

Yes

NA

stopCallDirectionNotification

Yes

NA

Interface: CallNotificationManager

NA

NA

StartCallNotification

Yes

NA

stopCallNotification

Yes

NA

SIP for Parlay X 2.1 Call Notification

The SIP plug-in for Parlay X 2.1 Call Notification is an integration plug-in that utilizes the Oracle Converged Application Server (OCCAS) to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in WebLogic SIP Server. The SIP Servlet uses the SIP API provided by the WebLogic SIP server, which in its turn converts the API calls to SIP messages.

The SIP servlet acts as both as a SIP User Agent and a SIP Proxy. Depending on which Parlay X operation and state of the call the SIP servlet acts either as a proxy or as the calling party. This means that the calling UA must use WebLogic SIP server as a SIP Proxy.

Standards Compliance

The SIP servlet uses the WebLogic SIP server, which conforms to RFC 3261. See Table 1-1, "Audio Call Specification Compliance Table" for a link to this specification's location.

Table 5-2 Statement of Compliance, SIP for Parlay X 2.1 Call Notification

Message/Response

Compliant(Yes/No)

Comment

REGISTER

NA

Not used in the context.

INVITE

Yes

NA

ACK

Yes

NA

CANCEL

Yes

NA

BYE

Yes

NA

OPTIONS

NA

Not used in the context.

INFO

NA

Not used in the context.

100 Trying

Yes

NA

180 Ringing

Yes

NA

181 Call Is Being Forwarded

Yes

Not used in the context.

182 Queued

Yes

Not used in the context.

183 Session Progress

Yes

Not used in the context.

200 OK

Yes

NA

300 Multiple Choices

Yes

UA treated as unreachable.

301 Moved Permanently

Yes

UA treated as unreachable.

302 Moved Temporarily

Yes

UA treated as unreachable.

305 Use Proxy

Yes

UA treated as unreachable.

380 Alternative Service

Yes

UA treated as unreachable.

400 Bad Request

Yes

UA treated as unreachable

401 Unauthorized

Yes

UA treated as unreachable

402 Payment Required

Yes

UA treated as unreachable

403 Forbidden

Yes

UA treated as unreachable

404 Not Found

Yes

UA treated as unreachable

405 Method Not Allowed

Yes

UA treated as unreachable

406 Not Acceptable

Yes

UA treated as unreachable

407 Proxy Authentication Required

Yes

UA treated as unreachable

408 Request Timeout

Yes

Treated as no answer from UA.

410 Gone

Yes

UA treated as unreachable

413 Request Entity Too Large

Yes

UA treated as unreachable

414 Request-URI Too Long

Yes

UA treated as unreachable

415 Unsupported Media Type

Yes

UA treated as unreachable

416 Unsupported URI Scheme

Yes

UA treated as unreachable

420 Bad Extension

Yes

UA treated as unreachable

421 Extension Required

Yes

UA treated as unreachable

423 Interval Too Brief

Yes

UA treated as unreachable

480 Temporarily Unavailable

Yes

UA treated as unreachable

481 Call/Transaction Does Not Exist

Yes

UA treated as unreachable

482 Loop Detected

Yes

UA treated as unreachable

483 Too Many Hops

Yes

UA treated as unreachable

484 Address Incomplete

Yes

UA treated as unreachable

485 Ambiguous

Yes

UA treated as unreachable

486 Busy Here

Yes

NA

487 Request Terminated

Yes

UA treated as unreachable

488 Not Acceptable Here

Yes

UA treated as unreachable

491 Request Pending

Yes

UA treated as unreachable

493 Undecipherable

Yes

UA treated as unreachable

500 Server Internal Error

Yes

UA treated as unreachable

501 Not Implemented

Yes

UA treated as unreachable

502 Bad Gateway

Yes

UA treated as unreachable

503 Service Unavailable

Yes

UA treated as unreachable

504 Server Time-out

Yes

UA treated as unreachable

505 Version Not Supported

Yes

UA treated as unreachable

513 Message Too Large

Yes

UA treated as unreachable

600 Busy Everywhere

Yes

UA treated as unreachable

603 Decline

Yes

UA treated as unreachable

604 Does Not Exist Anywhere

Yes

UA treated as unreachable

606 Not Acceptable

Yes

UA treated as unreachable

Note:
When a Parlay X application returns ActionValues.Route in Action.actionToPerform as a response to operations in Interface: CallDirection, a record-route header is inserted in the SIP Message the in order to stay in the call path.

6 Parlay X 2.1 Multimedia Messaging Compliance

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.

- Parlay X 2.1 Multimedia Messaging Statement of compliance

- MM7 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 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

MM7 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 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.

Standards Compliance

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

MM7 v 6.8.0 for Parlay X 2.1 Multimedia Messaging

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

Table 6-7 Compliance for MM7 Delivery Report Operation

Parameter

Mandatory or Optional

Compliant?

TransactionID

Mandatory

Yes

MM7Version

Mandatory

Yes

MMSRelayServerID

Optional

Yes

MessageID

Mandatory

Yes

Recipient

Mandatory

Yes

Sender

Mandatory

Yes

Date

Mandatory

Yes

MMStatus

Mandatory

Yes

Table 6-8 Compliance for MM7 Delivery Report Response Operation

Parameter

Mandatory or Optional

Compliant

TransactionID

Mandatory

Yes

MM7Version

Mandatory

Yes

Status

Mandatory

Yes

7 Parlay X 2.1 Presence Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 2.1 Presence communication services and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Presence

- SIP for Parlay X 2.1 Presence

Parlay X 2.1 Presence

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

The Parlay X 2.1 interface complies with ETSI ES 202 391-14, Open Service Access (OSA); Parlay X Web Services; Part 14: Presence (Parlay X 2).

See Table 1-10, "Presence Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 7-1 Statement of Compliance, Parlay X 2.1 Presence

Method

Compliant?

Comment

Interface: PresenceConsumer

NA

NA

subscribePresence

Yes

NA

getUserPresence

Yes

NA

startPresenceNotification

Yes

NA

endPresenceNotification

Yes

NA

Interface: PresenceNotification

NA

NA

statusChanged

Yes

NA

statusEnd

Yes

NA

notifySubscription

Yes

NA

subscriptionEnded

Yes

NA

Interface: PresenceSupplier

NA

NA

publish

No

NA

getOpenSubscriptions

No

NA

updateSubscriptionAuthorization

No

NA

getMyWatchers

No

NA

getSubscribedAttributes

No

NA

blockSubscription

No

NA

SIP for Parlay X 2.1 Presence

The SIP plug-in for Parlay X 2.1 Presence is an integration plug-in that utilizes Oracle Converged Application Server (OCCAS) to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in OCCAS. The controller utilizes the SIP API provided by OCCAS to create and send SUBSCRIBE requests. The SIP server converts the API calls to SIP and actually sends the requests out to the network. The SIP servlet on the other hand acts as a listener for responses to the SUBSCRIB requests that were sent from the controller. In this case the SIP server receives the SIP messages an converts them to API calls invoked on the SIP servlet.

Standards Compliance

The SIP servlet uses the WebLogic SIP server, which conforms to RFC 3261. See "Audio Call Specification Compliance Table" for a link to it's location.

Additionally, the following IETF specification are used by WebLogic SIP Server

Session Initiation Protocol (IP) - specific Event Notification

The specification is here:

http://www.ietf.org/rfc/rfc3265.txt

A Presence Event package for the Session Initiation Protocol (SIP)

The specification is here:

http://www.ietf.org/rfc/rfc3856.txt

PRID: Rich Presence Extensions to Presence Information Data Format (PIDF)

The specification is here:

http://tools.ietf.org/html/rfc4480

Table 7-2 Statement of Compliance, SIP for Parlay X 2.1 Presence

Message/Response

Compliant?

Comment

ACK

NA

Not used in the context.

REGISTER

NA

Not used in the context.

INVITE

NA

NA

CANCEL

NA

NA

BYE

NA

NA

OPTIONS

NA

Not used in the context.

SUBSCRIBE

Yes

NA

NOTIFY

Yes

NA

100 Trying

NA

Not used in the context.

180 Ringing

NA

Not used in the context.

181 Call Is Being Forwarded

NA

Not used in the context.

182 Queued

NA

Not used in the context.

183 Session Progress

NA

Not used in the context.

200 OK

Yes

NA

202 Accepted

Yes

NA

300 Multiple Choices

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

301 Moved Permanently

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

302 Moved Temporarily

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

305 Use Proxy

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

380 Alternative Service

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

400 Bad Request

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

401 Unauthorized

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

402 Payment Required

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

403 Forbidden

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

404 Not Found

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

405 Method Not Allowed

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

406 Not Acceptable

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

407 Proxy Authentication Required

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

408 Request Timeout

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

410 Gone

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

413 Request Entity Too Large

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

414 Request-URI Too Long

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

415 Unsupported Media Type

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

416 Unsupported URI Scheme

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

420 Bad Extension

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

421 Extension Required

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

423 Interval Too Brief

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

480 Temporarily Unavailable

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

481 Call/Transaction Does Not Exist

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

482 Loop Detected

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

483 Too Many Hops

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

484 Address Incomplete

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

485 Ambiguous

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

486 Busy Here

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

487 Request Terminated

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

488 Not Acceptable Here

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

489 Bad Event

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

491 Request Pending

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

493 Undecipherable

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

500 Server Internal Error

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

501 Not Implemented

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

502 Bad Gateway

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

503 Service Unavailable

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

504 Server Time-out

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

505 Version Not Supported

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

513 Message Too Large

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

600 Busy Everywhere

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

603 Decline

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

604 Does Not Exist Anywhere

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

606 Not Acceptable

Yes

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

8 Parlay X 2.1 Short Messaging (including EWS Binary SMS) Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 2.1 Short Messaging communication services and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Short Messaging Statement of compliance

- SMPP v3.4/5.0 for Parlay X 2.1/Extended Web Services Binary SMS

Parlay X 2.1 Short Messaging Statement of compliance

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

The Parlay X 2.1 interface complies with ETSI ES 202 391-4 Open Service Access (OSA); Parlay X Web Services; Part 4: Short Messaging (Parlay X 2).

See Table 1-12, "Short Messaging Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 8-1 Statement of Compliance, Parlay X 2.1 Short Messaging

Method

Compliant?

Comment

Interface: SendSms

NA

NA

sendSms

Yes

NA

sendSmsLogo

Yes

Note: The image is not scaled.

sendSmsRingtone

Yes

Note: Ringtones must be in either SmartMessaging or EMS (iMelody) format

getSmsDeliveryStatus

Yes

NA

Interface: SmsNotification

NA

NA

notifySmsReception

Yes

NA

notifySmsDeliveryReceipt

Yes

NA

Interface: ReceiveSms

NA

NA

getReceivedSms

Yes

NA

Interface: SmsNotificationManager

NA

NA

startSmsNotification

Yes

NA

stopSmsNotification

Yes

NA

SMPP v3.4/5.0 for Parlay X 2.1/Extended Web Services Binary SMS

The SMPP plug-in for Parlay X 2.1 Short Messaging and for the Extended Web Services (Binary SMS) acts as an External Short Message Entity (ESME) that connects to an SMSC over TCP/IP.

The plug-in instance binds itself to the SMSC either as ESME Transmitter and an ESME Receiver or as an ESME Transceiver.

The bindings occurs when the plug-in transitions from state inactive to active. It will not reach state active until it has bound. The plug-in unbinds itself prior to becoming inactive.

When an application sends an SMS with one recipient submit_sm PDU is used and when sending an SMS with 2 or more recipients submit_sm_multi is used.

Window size is configurable.

For application-initiated requests, the plug-in supports segmented SMSs using either 7-, 8-, or 16 bit data coding. The maximum length of an SMS segment is:

- 160 Characters for 7 bit data coding (SMSC default alphabet).

- 140 Characters for 8 bit data coding (ASCII).

- 70 Characters for 16bit coding (UCS2).

For network-triggered requests, the plug-in supports segmented SMSs in the same way as for application-initiated requests if the SMPP parameter short_message contains the user data. If short_message is empty the parameter message_payload, which can contain up to 64KB of data, is used.

For network-triggered requests, the SMS is propagated to the application through the Parlay X Short Messaging interface if the SMPP parameter data_coding equals 0x00, 0x01, 0x03, 0x05, 0x06, 0x07, 0x08, 0x0A, 0x0D, or 0x0E. In other cases, the SMS is forwarded to the application through the Binary SMS interface.

Standards Compliance

This plug-in complies with the Short Message Peer to Peer, Protocol Specification. See "Audio Call Specification Compliance Table" for the supported versions of this specification and links to their locations.

Note:
The Platform Test Environment interface supports both SMPP 3.4 and 5.0 specifications, but silently ignores any 5.0-specific fields

Table 8-2 Statement of Compliance, SMPP v3.4/5.0 for Parlay X 2.1 Short Messaging

Protocol Data Units (PDUs)

Compliant(Yes | No)

Comment

Plug-in originated PDUs:

NA

NA

bind_transmitter

Yes

NA

bind_receiver

Yes

NA

unbind

Yes

NA

submit_sm

Yes

NA

submit_multi

Yes

NA

deliver_sm_resp

Yes

NA

cancel_sm

Yes

NA

enquire_link

Yes

NA

enquire_link_resp

Yes

NA

generic_nack

Yes

NA

bind_transceiver

Yes

NA

data_sm

No

NA

data_sm_resp

No

NA

query_sm

No

NA

replace_sm

No

NA

interface_version

Yes

Only with a value of 5.0.

ussd_service_operation

Yes

NA

SMSC originated PDUs:

NA

NA

bind_transmitter_resp

Yes

NA

bind_receiver_resp

Yes

NA

unbind_resp

Yes

NA

submit_sm_resp

Yes

esm_classes:

- Default message Type

- SMSC Delivery receipt

submit_multi_resp

Yes

NA

deliver_sm

Yes

NA

cancel_sm_resp

Yes

NA

enquire_link

Yes

NA

enquire_link_resp

Yes

NA

generic_nack

Yes

NA

bind_transceiver_resp

Yes

NA

outbind

No

NA

data_sm

No

NA

data_sm_resp

No

NA

query_sm_resp

No

NA

replace_sm_resp

No

NA

alert_notification

No

NA

The Parlay X 2.1 Short Messaging and EWS Binary SMS communication services support the following features, which are defined in the Short Message Peer-to-Peer Protocol Specification. Services Gatekeeper supports these features as tunneled parameters.

Table 8-3 SMPP v5.0 for Parlay X 2.1 Short Messaging Tunneled Parameters

Parameter

Section in Specification

Comments

billing_identification

4.8.4.3

NA

ussd_service_operation

4.8.4.64

Version 5.0 added support to deliver_sm for bidrectional USSD.

interface_version

4.7.13

The Native SMPP Service accepts 5.0 as well as 3.4 as the interface version number.

9 Parlay X 2.1 Terminal Location/SIP Compliance

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

- Parlay X 2.1 Terminal Location

- SIP for Parlay X 2.1 Terminal Location

Parlay X 2.1 Terminal Location

This section describes the standards compliance for the communication services for Parlay X 2.1 Terminal Location:

The Parlay X 2.1 interface complies to ETSI ES 202 391-9, Open Service Access (OSA); Parlay X Web Services; Part 9: Terminal Location (Parlay X 2) specification.

See Table 1-15, "Terminal Status Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 9-1 Statement of Compliance, Parlay X 2.1 Terminal Location

Method

Compliant?

Comment

Interface: TerminalLocation

NA

NA

GetLocation

Yes

NA

GetTerminalDistance

Yes

NA

GetLocationForGroup

Yes

NA

Interface: TerminalLocationNotificationManager

NA

NA

StartGeographicalNotification

Yes

NA

StartPeriodicNotification

Yes

NA

EndNotification

Yes

NA

Interface: TerminalLocationNotification

NA

NA

LocationNotification

Yes

NA

LocationError

Yes

NA

LocationEnd

Yes

NA

Understanding Parlay X 2.1 Terminal Location Latitude and Longitude Value Precision

See the discussion on understanding Parlay X 2.1 terminal location precision in Services Gatekeeper Application Developer's Guide for information on the precision levels of Services Gatekeeper location information in messages.

SIP for Parlay X 2.1 Terminal Location

This communication service uses the SIP protocol to connect to the Oracle Communications Converged Application Server (Converged Application Server), Service Controller product, using the IM-PSX GSM MAP interworking module. See the discussion on setting up IM-PSX GSM MAP in Oracle Communications Service Broker Modules Configuration Guide for details on configuring the IM-PSX GSM MAP module to work with this communication service.

Standards Compliance

See "Audio Call Specification Compliance Table" for the supported version of this specification, and a link to its location.

10 Parlay X 2.1 Terminal Status Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 2.1 Terminal Status communication service and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Terminal Status

- SS7/MAP Terminal Status

Parlay X 2.1 Terminal Status

This section describes the standards compliance for the Terminal Status communication services for Parlay X 2.1 Terminal Status:

The Parlay X 2.1 interface complies to ETSI ES 202 391-8, Open Service Access (OSA); Parlay X Web Services; Part 8: Terminal Status (Parlay X 2).

See Table 1-15, "Terminal Status Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 10-1 Statement of Compliance, Parlay X 2.1 Terminal Status

Method

Compliant?

Comment

Interface: TerminalStatus

NA

NA

getStatus()

Yes

NA

getStatusForGroup()

Yes

NA

Interface: TerminalStatusNotificationManager

NA

NA

startNotification()

Yes

NA

endNotification()

Yes

NA

getStatus()

Yes

NA

Interface: TerminalStatusNotification

NA

NA

statusNotification()

Yes

NA

statusError()

Yes

NA

statusEnd()

Yes

NA

SS7/MAP Terminal Status

The Terminal Status/MAP plug-in for Terminal Status acts as an MAP application client for an SS7 network. Triggered notifications are supported, and you can specify whether the Terminal Status/Map plug-in performs the status change probe itself (”push”) or directs the network to perform it (”pull”).

The plug-in connects to the TietoEnator SS7 stack.

Standards Compliance

3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification, 3GPP TS 29.002. See "Audio Call Specification Compliance Table" for the supported version of this specification, and a link to its location.

Table 10-2 Statement of Compliance, MAP 3.1 for Parlay X 2.1 Terminal Status

Message

Compliant?

Comment

anyTimeInterrogationReq()

Yes

NA

anyTimeInterrogationRes()

Yes

NA

anyTimeInterrogation()

Yes

NA

anyTimeModificationReq()

Yes

NA

anyTimeModificationRes()

Yes

NA

anyTimeModification()

Yes

NA

NoteMMEvent

Yes

NA

11 Parlay X 2. 1 Third Party Call Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 2.1 Third Party Call communication service and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Third Party Call Statement of compliance

- SIP for Parlay X 2.1 Third Party Call

- SS7/INAP for Parlay X 2.1 Third Party Call

Parlay X 2.1 Third Party Call Statement of compliance

This section describes the standards compliance for the communication services for Parlay X 2.1 Third Party call

The Parlay X 2.1 interface complies to ETSI ES 202 391-2 Open Service Access (OSA); Parlay X Web Services; Part 2: Third Party Call (Parlay X 2).

See Table 1-16, "Third Party Call Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 11-1 Statement of Compliance, Parlay X 2.1 Third Party Call

Method

Compliant?

Comment

Interface: ThirdPartyCall

NA

NA

MakeCall

Yes

NA

GetCallInformation

Yes

NA

EndCall

Yes

NA

CancelCall

Yes

NA

SIP for Parlay X 2.1 Third Party Call

The SIP plug-in for Parlay X 2.1 Third Party Call is an integration plug-in that utilizes Oracle Converged Application Server (OCCAS) to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in OCCAS. The SIP Servlet uses the SIP API provided by the OCCAS, which in its turn converts the API calls to SIP messages.

The SIP servlet acts as a Back-to-Back User Agent for all calls.

Standards Compliance

The SIP servlet uses the WebLogic SIP server, which conforms to RFC 3261.

The RFC is here:

http://www.ietf.org/rfc/rfc3261.txt

The implementation of the SIP based third party call is in compliance with RFC 3725 - Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) Flow I.

The RFC is here:

http://www.ietf.org/rfc/rfc3725.txt

Table 11-2 Statement of Compliance, SIP for Parlay X 2.1 Third Party Call

Message/Response

Compliant(Yes/No)

Comment

REGISTER

NA

Not used in the context.

INVITE

Yes

NA

ACK

Yes

NA

CANCEL

Yes

NA

BYE

Yes

NA

OPTIONS

NA

Not used in the context.

100 Trying

Yes

NA

180 Ringing

Yes

NA

181 Call Is Being Forwarded

Yes

NA

182 Queued

Yes

NA

183 Session Progress

Yes

NA

200 OK

Yes

NA

300 Multiple Choices

Yes

UA treated as unreachable.

301 Moved Permanently

Yes

UA treated as unreachable.

302 Moved Temporarily

Yes

UA treated as unreachable.

305 Use Proxy

Yes

UA treated as unreachable.

380 Alternative Service

Yes

UA treated as unreachable.

400 Bad Request

Yes

UA treated as unreachable

401 Unauthorized

Yes

UA treated as unreachable

402 Payment Required

Yes

UA treated as unreachable

403 Forbidden

Yes

UA treated as unreachable

404 Not Found

Yes

UA treated as unreachable

405 Method Not Allowed

Yes

UA treated as unreachable

406 Not Acceptable

Yes

UA treated as unreachable

407 Proxy Authentication Required

Yes

UA treated as unreachable

408 Request Timeout

Yes

Treated as no answer from UA.

410 Gone

Yes

UA treated as unreachable

413 Request Entity Too Large

Yes

UA treated as unreachable

414 Request-URI Too Long

Yes

UA treated as unreachable

415 Unsupported Media Type

Yes

UA treated as unreachable

416 Unsupported URI Scheme

Yes

UA treated as unreachable

420 Bad Extension

Yes

UA treated as unreachable

421 Extension Required

Yes

UA treated as unreachable

423 Interval Too Brief

Yes

UA treated as unreachable

480 Temporarily Unavailable

Yes

UA treated as unreachable

481 Call/Transaction Does Not Exist

Yes

UA treated as unreachable

482 Loop Detected

Yes

UA treated as unreachable

483 Too Many Hops

Yes

UA treated as unreachable

484 Address Incomplete

Yes

UA treated as unreachable

485 Ambiguous

Yes

UA treated as unreachable

486 Busy Here

Yes

UA treated as busy.

487 Request Terminated

Yes

UA treated as unreachable

488 Not Acceptable Here

Yes

UA treated as unreachable

491 Request Pending

Yes

UA treated as unreachable

493 Undecipherable

Yes

UA treated as unreachable

500 Server Internal Error

Yes

UA treated as unreachable

501 Not Implemented

Yes

UA treated as unreachable

502 Bad Gateway

Yes

UA treated as unreachable

503 Service Unavailable

Yes

UA treated as unreachable

504 Server Time-out

Yes

UA treated as unreachable

505 Version Not Supported

Yes

UA treated as unreachable

513 Message Too Large

Yes

UA treated as unreachable.

600 Busy Everywhere

Yes

UA treated as unreachable

603 Decline

Yes

UA treated as unreachable

604 Does Not Exist Anywhere

Yes

UA treated as unreachable.

606 Not Acceptable

Yes

UA treated as unreachable

SS7/INAP for Parlay X 2.1 Third Party Call

The SS7/INAP plug-in for Parlay X 2.1 Third Party Call is an integration plug-in that utilizes the TietoEnator SS7 stack to connect to a SS7 network. The plug-in uses TietoEnator's Java INAP API to connect to the SS7 stack.

The plug-in acts as an INAP Application for all calls.

Standards Compliance

The plug-in conforms to ETSI 94 INAP CS1, ETS 300 374-1RFC 3261. See "Audio Call Specification Compliance Table" for the supported version of this specification and a link to its location.

Table 11-3 Statement of Compliance, INAP/SS7 for Parlay X 2.1 Third Party Call

Operation

Compliant?

Comment

ActivateServiceFiltering

No

Not used in context.

ActivityTest

No

Not used in context.

ApplyCharging

No

Not used in context.

ApplyChargingReport

No

Not used in context.

AssistRequestInstructions

No

Not used in context.

CallGap

No

Not used in context.

CallInformationReport

No

Not used in context.

CallInformationRequest

No

Not used in context.

Cancel

No

Not used in context.

CollectInformation

No

Not used in context.

Connect

Yes

NA

ConnectToResource

No

Not used in context.

Continue

Yes

NA

DisconnectForwardConnection

No

Not used in context.

EstablishTemporaryConnection

No

Not used in context.

EventNotificationCharging

No

Not used in context.

EventReportBCSM

Yes

NA

FurnishChargingInformation

No

Not used in context.

InitialDP

No

Not used in context.

InitiateCallAttempt

Yes

NA

PlayAnnouncement

No

Not used in context.

PromptAndCollectUserInformation

No

Not used in context.

ReleaseCall

Yes

NA

RequestNotificationChargingEvent

No

Not used in context.

RequestReportBCSMEvent

Yes

NA

ResetTimer

No

Not used in context.

SendChargingInformation

No

Not used in context.

ServiceFilteringResponse

No

Not used in context.

SpecializedResourceReport

No

Not used in context.

12 Parlay X 3.0 Application Subscription Management Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 3.0 Application Subscription Management communication service and how the interfaces and protocols comply to standards.

Application Subscription Management Statement of Compliance

This section describes the standards compliance for the Application Subscription Management communication service.

The Application Subscription Management communication service complies with the OMS GSSM specification as follows:

- High-Level Requirements - no operations supported.

- Service Subscription Operations - compliant. See Table 12-1 for a list of the supported operations.

- Subscription Validation Operations - compliant. See Table 12-2 for a list of the supported operations.

- Provisioning Related Operations - no operations supported.

- Security - no operations supported.

- Authentication - no operations supported.

- Authorization - no operations supported.

- Integrity - no operations supported.

- Confidentiality - no operations supported.

- Charging - no operations supported.

- Administration and Configuration - no operations supported.

- Privacy - no operations supported.

See Table 1-14, "Subscription Management Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Supported Operations

The General Service Subscription Management communication service supports these parts of the OMA GSSM V 1.0 specification:

Table 12-1 lists the specification parts of the General Service Subscription Management specification that Services Gatekeeper supports.

Table 12-1 General Service Subscription Management Supported Parts

Feature

Description

SSO-1

The GSSM Enabler SHALL provide the principal with a mechanism to subscribe principals(s) to a service.

SSO-2

The GSSM Enabler SHALL provide the authorized principal with a mechanism to change the Subscription Profile (for example, contents, channels, valid term).

SSO-3

The GSSM Enabler SHALL provide the subscriber with the mechanism to suspend/resume the service subscription.

SSO-4

The GSSM Enabler SHALL provide the authorised principal with a mechanism to unsubscribe from a service.

SSO-5

The GSSM Enabler SHALL provide the authorized principal with a mechanism for querying the service subscriptions.

SSO-6

The GSSM Enabler SHALL support the selective retrieval of Subscription Profiles based on the criteria in the Subscription Profile (for example subscription creation time, subscriber, user, service, subscription specific parameters).

SSO-7

The GSSM Enabler SHALL be capable of delegating to related resources (such as business support systems, backend systems) using existing interfaces, part of the validation process for the new service subscription requests. Part of such validation processes to be taken by those business support systems, under a new service subscription request, could be:

- Check if the user is not in a black list.

- Check if current pricing plans or product offerings for the user allows for subscribing to this service.

- Check compatibility of requested service with other services the user has already subscribed.

Table 12-2 Supported subscription Validation Operations

Feature

Description

SV-1

The GSSM Enabler SHALL be capable of validating a subscription based on the following criteria:

- the service being requested

- the principal for whom the service is being requested

- the time when the service is being requested

- the frequency with which the service is requested, for example how many times per day

- preferred service delivery method(s), for example MMS, WAP

SV-2

The GSSM Enabler SHALL be capable of delegating to related Resources using existing interfaces, part of the evaluation process for the validation of the subscription.

SV-3

The GSSM Enabler SHALL be capable of querying and retrieving from related Resources using existing interfaces, the necessary information to validate a subscription.

SV-4

The GSSM Enabler SHALL be capable of providing in the Subscription Validation result the information necessary for the operation and execution of the service provided to the user.

SV-5

Upon completion of the Subscription Validation, the GSSM Enabler SHALL be capable of delegating to related Resources part of the Service Subscription Provisioning process required for the delivery of the service to the user in accordance with the Subscription Profile.

SV-6

The GSSM Enabler SHALL support selecting and requesting either subscription validation or retrieval of the Subscription Profile data, for example in order for the requester to perform itself the validation operations.

SV-7

The GSSM Enabler SHALL be capable of providing necessary group information (for example ID of group members) upon response to a validation request for a group subscription.

13 Parlay X 3.0 Device Capabilities and Configuration Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 3.0 communication service and how the interfaces and protocols comply to standards.

- Parlay X 3.0 Device Capabilities and Configuration

- LDAP for Device Capabilities and Configuration

Parlay X 3.0 Device Capabilities and Configuration

This section describes the standards compliance for the communication services for Parlay X 3.0 Device Capabilities and Configuration (Device Capabilities):

The Parlay X 3.0 interface complies to ETSI ES 202 504-18, Open Service Access (OSA); Parlay X Web Services; Part 18: Device Capabilities and Configuration (Parlay X 3).

See Table 1-4, "Device Capabilities Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 13-1 Statement of Compliance, Parlay X 3.0 Device Capabilities and Configuration

Method

Compliant?

Comments

Interface: DeviceCapabilities

NA

NA

getCapabilities

Yes

NA

getDeviceId

Yes

NA

Interface: DeviceCapabilitiesNotificationManager

NA

NA

startNotification

No

NA

endNotification

No

NA

Interface: DeviceCapabilitiesNotification

NA

NA

deviceNotification

No

NA

deviceError

No

NA

deviceEnd

No

NA

Interface: DeviceConfiguration

NA

NA

pushConfiguration

No

NA

getConfigurationList

No

NA

getConfigurationHistory

No

NA

LDAP for Device Capabilities and Configuration

The LDAP plug-in for Device Capabilities acts as an LDAP client toward a directory service. The plug-in connects to the directory service using LDAP.

The plug-in instance has a pool of connections.

Standards Compliance

The plug-in complies to LDAP v3, RFC 4510. See Table 1-4, "Device Capabilities Communication Service Specifications" for a link to its location.

Table 13-2 Statement of Compliance, LDAP for Device Capabilities and Configuration

Operation

Compliant

Comment

Bind

Yes

NA

Unbind

Yes

NA

Search

Yes

NA

Modify

No

Not used in the context.

Add

No

Not used in the context.

Delete

No

Not used in the context.

Modify

No

Not used in the context.

Compare

No

Not used in the context.

Abandon

No

Not used in the context.

Extended

No

Not used in the context.

StartTLS

No

Not used in the context.

14 Parlay X 3.0 Payment Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 3.0 Payment communication services and how the interfaces and protocols comply to standards.

- Parlay X 3.0 Payment

- Diameter for Parlay X 3.0 Payment

Parlay X 3.0 Payment

This section describes the standards compliance for the communication services for Parlay X 3.0 Payment:

Standards Compliance

The Parlay X 3.0 interface complies to ETSI ES 202 504-6, Open Service Access (OSA); Parlay X Web Services; Part 6: Payment (Parlay X 3).

See Table 1-9, "Payment Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 14-1 Statement of Compliance, Parlay X 3.0 Payment

Method

Compliant(Yes | No)

Interface: AmountCharging

NA

ChargeAmount

Yes

RefundAmount

Yes

ChargeSplitAmount

Yes

Interface: VolumeCharging

NA

ChargeVolume

Yes

GetAmount

Yes

RefundVolume

Yes

chargeSplitVolume

Yes

Interface: ReserveAmountCharging

NA

ReserveAmount

Yes

ReserveAdditionalAmount

Yes

ChargeReservation

Yes

ReleaseReservation

Yes

Interface: ReserveVolumeCharging

NA

GetAmount

Yes

ReserveVolume

Yes

ReserveAdditionalVolume

Yes

ChargeReservation

Yes

ReleaseReservation

Yes

Diameter for Parlay X 3.0 Payment

The Diameter plug-in for Parlay X 3.0 Payment acts as a charging application toward a Diameter server.

Standards Compliance

The plug-in complies with RFC3588 and RFC4006. See "Audio Call Specification Compliance Table" for links to the locations of these specifications.

Table 14-2 Statement of Compliance, Diameter for Parlay X 3.0 Payment

Diameter AVP

Compliant?

Comment

Subscription-Id

Yes

NA

OCSG-Charge-Description

NA

Services Gatekeeper custom.

Currency-Code

Yes

NA

Unit-Value.Exponent

Yes

NA

Unit-Value.Value-Digits

Yes

NA

Service-Context-Id

Yes

NA

OSCG-Reference-Code

NA

Services Gatekeeper custom.

Session-Id

Yes

NA

Origin-Realm

Yes

NA

Origin-Host

Yes

NA

Destination-Realm

Yes

NA

Auth-Application-Id

Yes

NA

CC-Request-Type

Yes

NA

Requested-Action

Yes

NA

CC-Request-Number

Yes

NA

User-Name

Yes

NA

OCSG-Application-Id

NA

Services Gatekeeper custom.

Result-Code

Yes

NA

Service-Identifier

Yes

NA

Called-Party-Address

NA

Services Gatekeeper custom; identifies the application or subscriber receiving the service

Calling-Party-Address

NA

Services Gatekeeper custom; identifies the application or subscriber invoking the service

15 Parlay X 4.0 Application-Driven Quality of Service /Diameter Compliance

This chapter describes the standard Oracle Communications Services Gatekeeper Parlay X 4.0 Application-driven Quality of Service (QoS)/Diameter communication service and how the interfaces and protocols comply to standards.

Parlay X 4.0 Application-Driven QoS Statement of Compliance

This section describes the standards compliance for the communication services for Parlay X 4.0 Application-Driven QoS.

The Parlay X 4.0 interface complies with ETSI ES 202 504-17 Open Service Access (OSA); Parlay X Web Services; Part 17:Application-driven Quality of Service (QoS); Parlay X 3.

See Table 1-11, "Quality of Service Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Table 15-1 Statement of Compliance, Parlay X 4.0 Application-Driven QoS

Method

Compliant

Comment

Interface: ApplicationQoS

NA

NA

applyQoSFeature

Yes

This method sets temporary QoS feature profiles, but does not apply a default QoS feature profile. See the discussion on Parlay X 4.0 Quality of Service/Diameter in Services Gatekeeper System Administrator's Guide for more information.

modifyQoSFeature

Yes

NA

removeQoSFeature

Yes

NA

getQoSStatus

Yes

NA

getQoSHistory

Yes

NA

Interface: ApplicationQoSNotificationManager

NA

NA

startQoSNotification

Yes

NA

stopQoSNotification

Yes

NA

Interface: ApplicationQoSNotification

NA

NA

notifyQoSEvent

Yes

NA

Diameter Gx Statement of Compliance

Services Gatekeeper complies with a subset of the 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control (PCC); Reference points (Release 13) 3GPP TS 29.212 V13.5.0 (2016-03).

Table 15-2 lists the Diameter Gx AVPs Supported by Services Gatekeeper.

Table 15-2 Supported Diameter GX AVPs and Messages

Diameter Gx AVP

Diameter Gx Message

Notes

endUserOpaqueId

AAR

Added to request message from UE to PCRF, and then PECF.

requiredAccessInfo

AAR

Added to request message from UE to PCRF, and then PECF.

FramedPort

AAR

Added to request message from UE to PCRF, and then PECF.

msTimeZone

AAA

Added to the answer message and returned to Services Gatekeeper through PCRF, and also sent to UE.

userLocationInfo

AAA

Added to the answer message and returned to Services Gatekeeper through PCRF, and also sent to UE.

apnAMBRUL

AAA

Added to the answer message and returned to Services Gatekeeper through PCRF, and also sent to UE.

apnAMBRDL

AAA

Added to the answer message and returned to Services Gatekeeper through PCRF, and also sent to UE.

Diameter Rx Statement of Compliance

The Parlay X 4.0 Application-Driven QoS/Diameter communication service complies with the Policy and Charging Control over Rx reference point 3GPP TS 29.214 specification. See Table 1-11, "Quality of Service Communication Service Specifications" for the name and version of the supported specification and a link to its location.

Services Gatekeeper acts as a Diameter server for quality of service, and uses your Policy Control and Charging Rules Function (PCRF) as the diameter client.

Standards Compliance

Table 15-1 lists the Rx commands supported by Policy Controller.

Table 15-3 Supported Rx Messages

Command

Status

Link to List of Supported AVPs

AA-Request (AAR)

Supported

Supported Rx AA-Request AVPs

AA-Answer (AAA)

Supported

Supported Rx AA-Answer AVPs

Re-Auth-Request (RAR)

Supported

Supported Rx Re-Auth-Request AVPs

Re-Auth-Answer (RAA)

Supported

Supported Rx Re-Auth-Answer AVPs

Session-Termination-Request (STR)

Supported

Supported Rx Session-Termination-Request AVPs

Session-Termination-Answer (STA)

Supported

Supported Rx Session-Termination-Answer AVPs

Abort-Session-Request (ASR)

Supported

Supported Rx Abort-Session-Request AVPs

Abort-Session-Answer (ASA)

Supported

Supported Rx Abort-Session-Answer AVPs

Supported Rx AA-Request AVPs

Table 15-4 lists the supported Diameter Rx AA-Request (AAR) AVPs.

Table 15-4 Supported AAR AVPs

AVP

Status

Auth-Application-Id

Supported

Origin-Host

Supported

Origin-Realm

Supported

Destination-Realm

Supported

Destination-Host

Supported

AF-Application-Identifier

Supported

---- Media-Component-Description

Supported

---- ---- Media-Component-Number

Supported

---- ---- Media-Sub-Component

Supported

---- ---- AF-Application-Identifier

Supported

---- ---- Media-Type

Supported

---- ---- Max-Requested-Bandwidth-UL

Supported

---- ---- Max-Requested-Bandwidth-DL

Supported

---- ---- Flow-Status

Supported

---- ---- Reservation-Priority

Supported

Reused from ETSI TS 183 017 V2.3.1 (2008-9)

---- ---- RS-Bandwidth

Supported

---- ---- RR-Bandwidth

Supported

---- ---- Codec-Data

Supported

---- Media-Component-Number

Supported

---- Media-Sub-Component

Supported

---- ---- Flow-Number

Supported

---- ---- Flow-Description

Supported

---- ---- Flow-Status

Supported

---- ---- Flow-Usage

Supported

---- ---- Max-Requested-Bandwidth-UL

Supported

---- ---- Max-Requested-Bandwidth-DL

Supported

---- ---- AF-Signalling-Protocol

Supported

---- AF-Application-Identifier

Supported

---- Media-Type

Supported

---- Max-Requested-Bandwidth-UL

Supported

---- Max-Requested-Bandwidth-DL

Supported

---- Flow-Status

Supported

---- Reservation-Priority

Supported

---- RS-Bandwidth

Supported

Reused from ETSI TS 183 017 V2.3.1 (2008-9)

---- RR-Bandwidth

Supported

---- Codec-Data

Supported

Service-Info-Status

Supported

AF-Charging-Identifier

Supported

SIP-Forking-Indication

Supported

Specific-Action

Supported

Subscription-Id

Supported

Reused from RFC 4006

---- Subscription-Id-Type

Supported

Reused from RFC 4006

---- Subscription-Id-Data

Supported

Reused from RFC 4006

Supported-Features

Supported

Reused from 3GPP TS 29.229

---- Vendor-Id

Supported

Reused from 3GPP TS 29.229

---- Feature-List-ID

Supported

Reused from 3GPP TS 29.229

---- Feature-List

Supported

Reused from 3GPP TS 29.229

Reservation-Priority

Supported

Reused from ETSI TS 183 017 V2.3.1 (2008-9)

Framed-IP-Address

Supported

Reused from RFC 4005

Framed-IPv6-Prefix

Supported

Reused from RFC 4005

Called-Station-Id

Supported

Reused from RFC 4005

Service-URN

Supported

Origin-State-Id

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy-State

Supported

Route-Record

Supported

Supported Rx AA-Answer AVPs

Table 15-5 lists the supported Diameter Rx AA-Answer (AAA) AVPs.

Table 15-5 Supported AAA AVPs

AVP

Status

Auth-Application-Id

Supported

Origin-Host

Supported

Origin-Realm

Supported

Result-Code

Supported

Experiment-Result

Supported

Access-Network-Charging-Identifier

Supported

---- Access-Network-Charging-Identifier-Value

Supported

---- Access-Network-Charging-Identifier-Value

Supported

---- Flows

Supported

---- ---- Media-Component-Number

Supported

---- ---- Flow-Number

Supported

---- ---- Final-Unit-Action

Supported

Reused from RFC 4006

Access-Network-Charging-Address

Supported

Acceptable-Service-Info

Supported

---- Media-Component-Description

Supported

---- ---- Media-Component-Number

Supported

---- ---- Media-Sub-Component

Supported

---- ---- Flow-Number

Supported

---- ---- Flow-Description

Supported

---- ---- Flow-Status

Supported

---- ---- Flow-Usage

Supported

---- ---- Max-Requested-Bandwidth-UL

Supported

---- ---- Max-Requested-Bandwidth-DL

Supported

---- ---- AF-Signalling-Protocol

Supported

---- ---- AF-Application-Identifier

Supported

---- ---- Media-Type

Supported

---- ---- Max-Requested-Bandwidth-UL

Supported

---- ---- Max-Requested-Bandwidth-DL

Supported

---- ---- Flow-Status

Supported

---- ---- Reservation-Priority

Supported

Reused from ETSI TS 183 017 V2.3.1 (2008-9)

---- ---- RS-Bandwidth

Supported

---- ---- RR-Bandwidth

Supported

---- ---- Codec-Data

Supported

---- Max-Requested-Bandwidth-DL

Supported

---- Max-Requested-Bandwidth-UL

Supported

IP-CAN-Type

Supported

Reused from 3GPP TS 29.212

RAT-Type

Supported

Reused from 3GPP TS 29.212

Supported-Features

Supported

Reused from 3GPP TS 29.229

---- Vendor-Id

Supported

Reused from 3GPP TS 29.229

---- Feature-List-ID

Supported

Reused from 3GPP TS 29.229

---- Feature-List

Supported

Reused from 3GPP TS 29.229

Class

Supported

Error-Message

Supported

Error-Reporting-Host

Supported

Failed-AVP

Supported

---- AVP

Supported

Origin-State-Id

Supported

Redirect-Host

Supported

Redirect-Host-Usage

Supported

Redirect-Max-Cache-Time

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy State

Supported

Supported Rx Re-Auth-Request AVPs

Table 15-6 lists the supported Diameter Rx Re-Auth-Request (RAR) AVPs.

Table 15-6 Supported RAR AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Destination-Realm

Supported

Destination-Host

Supported

Auth-Application-Id

Supported

Specific-Action

Supported

Access-Network-Charging-Identifier

Supported

---- Access-Network-Charging-Identifier-Value

Supported

---- Access-Network-Charging-Identifier-Value

Supported

---- Flows

Supported

---- ---- Media-Component-Number

Supported

---- ---- Flow-Number

Supported

---- ---- Final-Unit-Action

Supported

Reused from RFC 4006

Access-Network-Charging-Address

Supported

Flows

Supported

---- Media-Component-Number

Supported

---- Flow-Number

Supported

---- Final-Unit-Action

Supported

Reused from RFC 4006

Subscription-Id

Supported

Reused from RFC 4006

---- Subscription-Id-Type

Supported

Reused from RFC 4006

---- Subscription-Id-Data

Supported

Reused from RFC 4006

Abort-Cause

Supported

IP-CAN-Type

Supported

Reused from 3GPP TS 29.212

RAT-Type

Supported

Reused from 3GPP TS 29.212

Origin-State-Id

Supported

Class

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy-State

Supported

Route-Record

Supported

Supported Rx Re-Auth-Answer AVPs

Table 15-7 lists the supported Diameter Rx Re-Auth-Answer (RAA) AVPs.

Table 15-7 Supported RAA AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Experimental-Result

Supported

---- Vendor-Id

Supported

---- Experimental-Result-Code

Supported

Media-Component-Description

Supported

---- Media-Component-Number

Supported

---- Media-Sub-Component

Supported

---- AF-Application-Identifier

Supported

---- Media-Type

Supported

---- Max-Requested-Bandwidth-UL

Supported

---- Max-Requested-Bandwidth-DL

Supported

---- Flow-Status

Supported

---- Reservation-Priority

Supported

Reused from ETSI TS 183 017 V2.3.1 (2008-9)

---- RS-Bandwidth

Supported

---- RR-Bandwidth

Supported

---- Codec-Data

Supported

Service-URN

Supported

Origin-State-Id

Supported

Class

Supported

Error-Message

Supported

Error-Reporting-Host

Supported

Redirect-Host

Supported

Redirect-Host-Usage

Supported

Redirect-Max-Cache-Time

Supported

Failed-AVP

Supported

---- AVP

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy-State

Supported

Supported Rx Session-Termination-Request AVPs

Table 15-8 lists the supported Diameter Rx Session-Termination-Request (STR) AVPs.

Table 15-8 Supported STR AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Destination-Realm

Supported

Auth-Application-Id

Supported

Termination-Cause

Supported

Destination-Host

Supported

Class

Supported

Origin-State-Id

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy-State

Supported

Route-Record

Supported

Supported Rx Session-Termination-Answer AVPs

Table 15-9 lists the supported Diameter Rx Session-Termination-Answer (STA) AVPs.

Table 15-9 Supported STA AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Result-Code

Supported

Error-Message

Supported

Error-Reporting-Host

Supported

Failed-AVP

Supported

Origin-State-Id

Supported

Class

Supported

Redirect-Host

Supported

Redirect-Host-Usage

Supported

Redirect-Max-Cache-Time

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy-State

Supported

Supported Rx Abort-Session-Request AVPs

Table 15-10 lists the supported Diameter Rx Abort-Session-Request (ASR) AVPs.

Table 15-10 Supported ASR AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Destination-Realm

Supported

Destination-Host

Supported

Auth-Application-Id

Supported

Abort-Cause

Supported

Origin-State-Id

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy State

Supported

Route-Record

Supported

Supported Rx Abort-Session-Answer AVPs

Table 15-11 lists the supported Diameter Rx Abort-Session-Answer (ASA) AVPs.

Table 15-11 Supported ASA AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Result-Code

Supported

Origin-State-Id

Supported

Error-Message

Supported

Error-Reporting-Host

Supported

Failed-AVP

Supported

Redirect-Host

Supported

Redirect-Host-Usage

Supported

Redirect-Max-Cache-Time

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy State

Supported

Non-Standard Supported Diameter AVPs

This section lists the Diameter Rx AVPs that Services Gatekeeper supports that are not included in the Policy and Charging Control over Rx reference point 3GPP TS 29.214 specification.

Table 15-12 lists the non-standard Diameter Rx AAR AVPs supported by Services Gatekeeper.

Table 15-12 Supported Non-Standard Diameter Rx AAR AVPs

Name

Code

Vendor ID

Type

Attribute Flag

Notes

FramedPort

4001

21274

Integer32

Ox80

The source port of the UE request received by AME. Often this is a NAT assigned port.

requiredAccessInfo

536

10415

Integer32

0xc0

Used for the required access info for different access types such as USER_LOCATION or MS_TIMEZONE.

Table 15-13 lists the non-standard Diameter Rx AAA AVPs supported by Services Gatekeeper.

Table 15-13 Supported Non-Standard Diameter Rx AAA AVPs

Name

Code

Vendor ID

Type

Attribute Flag

Notes

MsTimeZone

23

10415

Byte

0xc0

Contain the hexadecimal representation of the 3GPP-MS-TimeZone defined in 3GPP TS 29.061.

userLocationInfo

22

10415

Byte

0xc0

Contain the hexadecimal representation of the 3GPP-User-Location-Info IE as defined in 3GPP TS 29.274.

endUserOpaqueId

4000

21274

Byte

0x80

Uniquely identifies a user.

apnAMBRUL

1041

10415

Unsigned32

0x80

Specifies the APN (Access point Name) Aggregate Maximum Bit Rate for Uplink.

apnAMBRDL

1040

10415

Unsigned32

0x80

Specifies the APN (Access point Name) Aggregate Maximum Bit Rate for Downlink.

16 Extended Web Services WAP Push Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Extended Web Services WAP Push communication services and how the interfaces and protocols comply to standards.

- Extended Web Services WAP Push

- WAP Push for Extended Web Services WAP Push

Extended Web Services WAP Push

This section describes the standards compliance for the communication services for Extended Web Services WAP Push:

The Extended Web Services interface is an interface defined by Oracle, but it is based on the patterns present in the Parlay X 2.1 interfaces.

The payload of a WAP Push message adhere to the specifications listed in Table 1-17, "WAP Push Communication Service Specifications". See that table for a list of the supported specifications and links to their locations.

WAP Push for Extended Web Services WAP Push

The WAP Push plug-in for Extended Web Services WAP Push acts as an Push Initiator toward a Push Proxy Gateway using the PAP interface. The plug-in connects to the Push proxy Gateway using HTTP.

The plug-in always acts as one single Push Initiator toward the Location Server.

Standards Compliance

The plug-in complies to Push Access Protocol, WAP Forum, WAP-247-PAP-20010429-a. See Table 1-1, "Audio Call Specification Compliance Table" for the supported specification and a link to its location.

Table 16-1 Statement of Compliance, WAP Push for Extended Web Services WAP Push

Operation

Compliant?

Comment

push-message

Yes

NA

push-response

Yes

NA

cancel-message

No

NA

cancel-response

No

NA

resultnotification-message

Yes

NA

resultnotification-response

Yes

NA

statusquery-message

No

NA

statusquery-response

No

NA

ccq-message

No

NA

ccq-response

No

NA

badmessage-response

Yes

NA

17 Extended Web Services Subscriber Profile Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Extended Web Services Subscriber Profile communication services and how the interfaces and protocols comply to standards.

- Extended Web Services Subscriber Profile

- LDAP for Extended Web Services Subscriber Profile

Extended Web Services Subscriber Profile

This section describes the standards compliance for the communication services for Extended Web Services Subscriber Profile:

The Extended Web Services interface is an interface defined by Oracle, but it is based on a suggestion for a Parlay X standard for Subscriber Profile.

LDAP for Extended Web Services Subscriber Profile

The LDAP plug-in for Extended Web Services Subscriber Profile acts as an LDAP client toward a directory service. The plug-in connects to the directory service using LDAP.

The plug-in instance has a pool of connections.

Standards Compliance

The plug-in complies to LDAP v3, RFC 4510.

The specification is here:

http://tools.ietf.org/html/rfc4510.

Table 17-1 Statement of Compliance, LDAP for Extended Web Services Subscriber Profile

Operation

Compliant(Yes | No)

Comment

Bind

Yes

NA

Unbind

Yes

NA

Search

Yes

NA

Modify

No

Not used in the context.

Add

No

Not used in the context.

Delete

No

Not used in the context.

Modify

No

Not used in the context.

Compare

No

Not used in the context.

Abandon

No

Not used in the context.

Extended

No

Not used in the context.

StartTLS

No

Not used in the context.

18 Native MM7 Compliance

The following chapter describes the standard Oracle Communications Services Gatekeeper Native MM7 communication services and how the interfaces and protocols comply 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 the versions of the 3rd Generation Partnership Project; Technical Specification Group Terminals; Multimedia Messaging Service (MMS); Functional description; Stage 2, 3GPP TS23.140 listed in. Table 1-6, "Multimedia Messaging Communication Service Specifications" lists the supported specification versions and includes links to their locations.

This plug-in supports authentication using HTTP Basic Authentication according to HTTP Authentication: Basic and Digest Access Authentication, IETF; RFC 2617.

Table 18-1 Statement of Compliance Native MM7Service Facade

Operation

Compliant?

Comment

MMS VAS application originated operations:

NA

NA

MM7_submit.REQ

Yes

NA

MM7_cancel.REQ

No

NA

MM7_delivery_report.RES

Yes

NA

MM7_deliver.RES

Yes

NA

MM7_replace.REQ

No

NA

MM7_read_reply.RES

Yes

NA

MM7_VASP_error.RES

No

NA

MM7 Service Facade originated operations:

NA

NA

MM7_submit.RES

Yes

NA

MM7_cancel.REQ

No

NA

MM7_delivery_report.REQ

Yes

NA

MM7_deliver.REQ

Yes

NA

MM7_replace.RES

No

NA

MM7_read_reply.REQ

Yes

NA

MM7_RS_error.RES

No

NA

Native MM7 Service Enabler Standards Compliance

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

The Service Enabler complies to the versions of the 3rd Generation Partnership Project; Technical Specification Group Terminals; Multimedia Messaging Service (MMS); Functional description; Stage 2, 3GPP TS 23.140 listed in Table 18-2. See Table 1-1, "Audio Call Specification Compliance Table" for the supported specification version and a link to its location.

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

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

Table 18-2 Statement of Compliance Native MM7Service Enabler

Operation

Compliant?

Comment

MM7 Service Enabler originated operations:

NA

NA

MM7_submit.REQ

Yes

NA

MM7_cancel.REQ

No

NA

MM7_delivery_report.RES

Yes

NA

MM7_deliver.RES

Yes

NA

MM7_replace.REQ

No

NA

MM7_read_reply.RES

Yes

NA

MM7_VASP_error.RES

Yes

NA

MMSC originated operations:

NA

NA

MM7_submit.RES

Yes

NA

MM7_cancel.RES

Yes

NA

MM7_delivery_report.REQ

Yes

NA

MM7_deliver.REQ

Yes

NA

MM7_replace.RES

No

NA

MM7_read_reply.REQ

Yes

NA

MM7_RS_error.RES

Yes

NA

19 Native SMPP Compliance

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

- Native SMPP

- Native SMPP Service Facade Standards Compliance

- Native SMPP Service Enabler Standards Compliance

Native SMPP

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

Native SMPP Service Facade Standards Compliance

The Native SMPP Service Facade acts as an SMPP SCMC. It is used by SMPP applications.

The Service Facade Complies to Short Message Peer to Peer, Protocol Specification v3.4. See Table 1-12, "Short Messaging Communication Service Specifications" for the supported specification version and a link to its location.

Table 19-1 Statement of Compliance, SMPP Service Facade

Operation

Compliant?

Comment

bind_transmitter

Yes

NA

bind_transmitter_resp

Yes

NA

bind_receiver

Yes

NA

bind_receiver_resp

Yes

NA

bind_transceiver

Yes

NA

bind_transceiver_resp

Yes

NA

outbind

No

NA

unbind

Yes

NA

unbind_resp

Yes

NA

generic_nack

Yes

NA

submit_sm

Yes

NA

submit_sm_resp

Yes

NA

submit_sm_multi

Yes

NA

submit_sm_multi_resp

Yes

NA

deliver_sm

Yes

NA

deliver_sm_resp

Yes

NA

data_sm

No

NA

data_sm_resp

No

NA

query_sm

Yes

NA

query_sm_resp

Yes

NA

cancel_sm

Yes

NA

cancel_sm_resp

Yes

NA

replace_sm

Yes

NA

replace_sm_resp

Yes

NA

enquire_link

Yes

NA

enquire_link_resp

Yes

NA

alert_notification

No

NA

Native SMPP Service Enabler Standards Compliance

The Native SMPP Service Enabler acts as an External Short Message Entity (ESME) toward an SMPP SCMC.

The Service Enabler Complies to Short Message Peer to Peer, Protocol Specification v3.4. See Table 1-1, "Audio Call Specification Compliance Table" for the supported specification version and a link to its location.

Table 19-2 Statement of Compliance, SMPP Service Enabler

Operation

Compliant?

Comment

bind_transmitter

Yes

NA

bind_transmitter_resp

Yes

NA

bind_receiver

Yes

NA

bind_receiver_resp

Yes

NA

bind_transceiver

Yes

NA

bind_transceiver_resp

Yes

NA

outbind

No

NA

unbind

Yes

NA

unbind_resp

Yes

NA

generic_nack

Yes

NA

submit_sm

Yes

NA

submit_sm_resp

Yes

NA

submit_sm_multi

Yes

NA

submit_sm_multi_resp

Yes

NA

deliver_sm

Yes

NA

deliver_sm_resp

Yes

NA

data_sm

No

NA

data_sm_resp

No

NA

query_sm

Yes

NA

query_sm_resp

Yes

NA

cancel_sm

Yes

NA

cancel_sm_resp

Yes

NA

replace_sm

Yes

NA

replace_sm_resp

Yes

NA

enquire_link

Yes

NA

enquire_link_resp

Yes

NA

alert_notification

No

NA

Native SMPP Version 5.1 Standards Compliance

The native SMPP communication service supports the following features, which are defined in the Short Message Peer-to-Peer Protocol Specification, Version 5.1. Services Gatekeeper supports these features as tunneled parameters.

Table 19-3 Statement of Compliance for Version 5.1 Features

Parameter

Section in Specification

Comments

billing_identification

4.8.4.3

ussd_service_operation

4.8.4.64

Version 5.1 added support to deliver_sm for bidrectional USSD.

interface_version

4.7.13

The Native SMPP Service accepts 5.1 as well as 3.4 as the interface version number.

20 Native UCP Compliance

The following chapter describes Oracle Communications Services Gatekeeper Native UCP Communication Service and how the interfaces and protocols comply to standards.

Native UCP

The Native UCP communication service complies with the Short Message Service Centre EMI-UCP Interface specification. See Table 1-12, "Short Messaging Communication Service Specifications" for the supported specification version and a link to its location.

Table 20-1 describes Native UCP's compliance with the Short Message Service Centre EMI-UCP specification.

Table 20-1 Statement of Compliance, Native UCP

Operation

Compliant?

Comment

51 Submit_short_message

Yes

NA

52 Deliver_short_message

Yes

NA

53 Deliver_notification

Yes

NA

54 Modify_message

No

NA

55 Inquiry_message

No

NA

56 Delete_message

No

NA

57 Response_inquiry_message

No

NA

58 Response_delete_message

No

NA

31 SMT Alert

Yes

Supports heartbeats

60 Session management

Yes

Supports authentication

61 List management

No

NA

21 OneAPI Multimedia Messaging Compliance

The following chapter describes the Oracle Communications Services Gatekeeper OneAPI multimedia messaging interface standards for RESTful web services.

OneAPI Multimedia Messaging Interface

This section describes the standards compliance for the OneAPI Multimedia Messaging interface standards for RESTful web services.

Standards Compliance - RESTful Bindings

The OneAPI Multimedia Messaging interface complies with the RESTful bindings for Parlay X Web Services – Multi-media Messaging OMA specification.

See Table 1-6, "Multimedia Messaging Communication Service Specifications" in "Services Gatekeeper Compliance Reference Table" for a link to the specification.

Standards Compliance - RESTful Bindings Schema

The RESTful web service complies with the schema definition for the XML data type definitions for OMA RESTful Network API for Messaging. See Table 1-1, "Audio Call Specification Compliance Table" for the supported version and a link to its location.

RESTful Bindings Data Structure Compliance

Table 21-1 lists the data structures that Services Gatekeeper supports from the RESTful bindings for Parlay X Web Services – Multi-media Messaging OMA specification.

Table 21-1 Multimedia Messaging ParlayREST Data Structure Compliance

API Data Structure

Compliant?

Comments

Type: InboundMessageList

Yes

NA

Type: InboundMessage

Yes

NA

Type: nboundMessageNotification

Yes

NA

Type: InboundSMSTextMessage

Yes

NA

Type: InboundMMSMessage

Yes

NA

Type: InboundMMessage

Yes

NA

Type: SubscriptionList

Yes

NA

Type: Subscription

Yes

NA

Type: InboundMessageRetrieveAndDeleteRequest

Yes

NA

Type: OutboundMessageRequestList

Yes

NA

Type: OutboundMessageRequest

Yes

NA

Type: OutboundMMSMessage

Yes

NA

Type: OutboundWAPMessage

Yes

NA

Type: OutboundSMSTextMessage

Yes

NA

Type: OutboundSMSBinaryMessage

Yes

NA

Type: OutboundSMSLogoMessage

Yes

NA

Type: OutboundSMSRingToneMessage

Yes

NA

Type: OutboundSMSMMessage

Yes

NA

Type: DeliveryInfoList

Yes

NA

Type: DeliveryInfoNotification

Yes

NA

Type: DeliveryInfo

Yes

NA

Type: DeliveryReceiptSubscriptionList

Yes

NA

Type: DeliveryReceiptSubscription

Yes

NA

Enumeration: DeliveryStatus

Yes

NA

Enumeration: IMFormat

Yes

NA

Enumeration: MessagePriority

Yes

NA

Enumeration: RetrievalOrder

Yes

NA

Enumeration: ServiceIndicationAction

Yes

NA

Enumeration: ServiceLoadingAction

Yes

NA

Enumeration: SmsFormat

Yes

NA

Enumeration: WAPContent

Yes

NA

Values of the Link rel attribute

Yes

NA

MIME multipart representation

Yes

NA

Resource: Inbound messages for a given registration

Yes

NA

Resource: Inbound messages retrieve and delete using registration

Yes

NA

Resource: Retrieval and deletion of individual inbound message using registration

Yes

NA

Resource: Inbound message for a given registration

Yes

NA

Resource: Inbound message attachment

Yes

NA

Resource: Inbound message subscriptions

Yes

NA

Resource: Individual inbound message subscription

Yes

NA

Resource: Client notification about inbound message

Yes

NA

Resource: Outbound message requests

Yes

NA

Resource: Outbound message request and delivery status

Yes

NA

Resource: Outbound message delivery status

Yes

NA

Resource: Outbound message delivery notification subscriptions

Yes

NA

Resource: Individual outbound message delivery notification subscription

Yes

NA

Resource: Client notification about outbound message delivery status

Yes

NA

22 OneAPI Terminal Location Interface Compliance

This chapter describes the Oracle Communications Services Gatekeeper OneAPI Terminal Location interface standards for RESTful web services.

OneAPI Terminal Location Interface

This section describes the standards compliance for the OneAPI Terminal Location interface standards for RESTful web services.

Standards Compliance - RESTful Bindings

The OneAPI terminal location interface complies with the RESTful bindings for Parlay X Web Services – Terminal Location specification.

Standards Compliance - RESTful Bindings Schema

The RESTful web service complies with the schema definition for the RESTfule bindings for Parlay X Web Service, Terminal Location specification. See Table 1-1, "Audio Call Specification Compliance Table" for the supported version and a link to its location.

RESTful Bindings Data Structure Compliance

Table 22-1 lists the data structures that Services Gatekeeper supports from the RESTful bindings for Parlay X Web Services, Terminal Location specification

Table 22-1 Terminal Location ParlayREST Data Structure Compliance

API Data Structure

Compliant?

Comments

Type: Terminal Location

Yes

NA

Type: TerminalLocationList

Yes

NA

Type: SubscriptionNotification

Yes

NA

Type: SubscriptionCancellationNotification

Yes

NA

Type: TerminalDistance

Yes

NA

Type: LocationInfo

Yes

NA

Type: NotificationSubscriptionList

Yes

NA

Type: CircleNotificatonSubscription

Yes

NA

Type: PeriodicNotificationSubscription

Yes

NA

Type: DistanceNotificationSubscription

Yes

NA

Enumeration: EnteringLeavingCriteria

Yes

NA

Enumeration: DistanceCriteria

Yes

NA

Enumeration: DelayToleance

Yes

NA

Values of the Link "rel" attribute

Yes

NA

Resource: Terminal Location

Yes

NA

Resource Terminal Distance

Yes

NA

Resource: Periodic location notification subscriptions

Yes

NA

Resource: Individual periodic location notification subscription

Yes

NA

Resource: Area (circle) notification subscriptions

Yes

NA

Resource: Area (circle) individual notification subscription

Yes

NA

Resource: Distance notification subscriptions

Yes

NA

Resource: Distance individual notification subscription

Yes

NA

Resource: Client notification callback resource

Yes

NA

23 OneAPI Payment Compliance

This chapter describes the Oracle Communications Services Gatekeeper OneAPI Payment interface standards for RESTful web services.

OneAPI Payment Interface

This section describes the standards compliance for the OneAPI Payment interface standards for RESTful web services.

Standards Compliance - RESTful Bindings

Services Gatekeeper complies with the RESTful web services RESTful bindings for Parlay X Web Services–Payment specification. See Table 1-1, "Audio Call Specification Compliance Table" for the supported version and a link to its location.

Standards Compliance - RESTful Bindings Schema

The OneAPI Payment interface complies with the schema definition for the XML data type definitions for OMA RESTful Network API for Payment specification. See Table 1-9, "Payment Communication Service Specifications" for the supported version and a link to its location.

RESTful Bindings Data Structure Compliance

Table 23-1 lists the data structures that Services Gatekeeper supports from the RESTful bindings for Parlay X Web Services–Payment specification.

Table 23-1 OneAPI Payment ParlayREST Data Structure Compliance

API Data Structure

Compliant?

Comments

Type: PaymentTransactionList

Yes

NA

Type: AmountTransaction

Yes

NA

Type: AmountSplitTransaction

Yes

NA

Type: VolumeTransaction

Yes

NA

Type: VolumeSplitTransaction

Yes

NA

Type: AmountReservationTransaction

Yes

NA

Type: VolumeReservationTransaction

Yes

NA

Type: PaymentAmount

Yes

NA

Type: ChargingMetaData

Yes

NA

Type: EndUserShare

Yes

NA

Type: Rating Parameter

Yes

NA

Enumeration: TransactionOperationStatus

Yes

NA

Values of the Link "rel" attribute

Yes

NA

Resource: All payment transactions for an end user

Yes

NA

Resource: All amount charge and refund transactions for an end user

Yes

NA

Resource: All amount split charge transactions for an end user

Yes

NA

Resource: Individual amount charge or refund transaction for an end user

Yes

NA

Resource: Individual amount split charge transaction for an end use

Yes

NA

Resource: All volume charge and refund transactions for an end user

Yes

NA

Resource: All volume split charge transactions for an end user

Yes

NA

24 OneAPI Short Messaging Compliance

The following chapter describes the Oracle Communications Services Gatekeeper OneAPI Short Messaging interface standards for RESTful web services.

OneAPI Short Messaging Interface

This section describes standards compliance for the Services Gatekeeper OneAPI Short Messaging interface.

Standards Compliance - RESTful Bindings

The OneAPI Short Messaging interface complies with RESTful bindings for Parlay X Web Services–Short Messaging specification. See Table 1-12, "Short Messaging Communication Service Specifications" for the supported version and a link to its location.

Standards Compliance - RESTful Bindings Schema

The OneAPI Short Messaging interface complies with the schema definition for the RESTful Bindings for Parlay X Web Services, Short Messaging specification. See Table 1-1, "Audio Call Specification Compliance Table" for the supported version and a link to its location.

RESTful Bindings Data Structure Compliance

Table 24-1 lists the data structures that Services Gatekeeper supports from the RESTful bindings for Parlay X Web Services–Short Messaging specification.

Table 24-1 OneAPI Short Messaging ParlayREST Data Structure Compliance

API Data Structure

Compliant?

Comments

Type: InboundSMSMSessageList

Yes

NA

Type: InboundSMSMessage

Yes

NA

Type: InboundSMSMessageNotification

Yes

NA

Type: SubscriptionList

Yes

NA

Type: Subscription

Yes

NA

Type: InboundSMSMessageRetrieveAndDeleteRequest

Yes

NA

Type: OutboundSMSMEssageRequestList

Yes

NA

Type: OutboundSMSMessageRequest

Yes

NA

Type: OutboundSMSTextMessage

Yes

NA

Type: OutboundSMSBinaryMessage

Yes

NA

Type: OutboundSMSLogoMessage

Yes

NA

Type: OutboundSMSRingToneMessage

Yes

NA

Type: DeliveryInfoList

Yes

NA

Type: DeliveryInfoNotification

Yes

NA

Type: DeliveryInfo

Yes

NA

Type: DeliveryReceiptSubscriptionList

Yes

NA

Type: DeliveryReceiptSubscription

Yes

NA

Enumeration: DeliveryStatus

Yes

NA

Enumeration: SmsFormat

Yes

NA

Enumeration:RetrievalOrder

Yes

NA

Values of the Link "rel" attribute

Yes

NA

Resource: Inbound SMS message requests for a given registration

Yes

NA

Resource: Inbound SMS messages Retrieve and Delete using registration

Yes

NA

Resource: Inbound SMS message for a given registration

Yes

NA

Resource: Inbound SMS message subscriptions

Yes

NA

Resource: Individual inbound SMS message subscription

Yes

NA

Resource: Client notification about inbound SMS message

Yes

NA

Resource: Outbound SMS message requests

Yes

NA

Resource: Outbound SMS message request and delivery status

Yes

NA

Resource: Outbound SMS message delivery status

Yes

NA

Resource: Outbound SMS message delivery notification subscriptions

Yes

NA

Resource: Individual outbound SMS message delivery notification subscription

Yes

NA

Resource: Client notification about outbound SMS message delivery status

Yes

NA

25 RESTful Anonymous Customer Reference Compliance

This chapter lists the Anonymous Customer Reference (ACR) specifications supported by RESTful interfaces in Oracle Communications Services Gatekeeper.

Anonymous Customer Reference Specification

See Table 1-3, "Cross Cutting Services Communication Service Specifications" for the supported ACR specification version, and a link to its location