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