|
|
This appendix describes the specific standards that Gatekeeper supports, and provides, where possible, links to the actual specifications. A detailed statement of compliance is also available.
The Oracle Communications Services Gatekeeper application-facing interfaces support the following parts of the Parlay X 2.1 specification.
| Note: | See http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX21.html for links to the specifications. |
The Oracle Communications Services Gatekeeper application-facing interfaces support the following parts of the Draft Parlay X 3.0 specification.
| Note: | See http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX30.html for links to the specifications |
The Extended Web Services are Oracle Communications Services Gatekeeper’s proprietary application-facing interfaces. These interfaces are implementations of commonly requested functionality, including, in this release, WAP Push, Binary SMS, and Subscriber Profile. Although the interfaces themselves are not standardized, they use standardized elements.
| Note: | See http://www.3gpp.org/ftp/Specs/html-info/23040.htm for links to the specification. |
The payload, protocol identifier, and validity period rely on:
| Note: | See http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.html for links to the specifications. |
The payload of a WAP Push message shall adhere to:
| Note: | The Extended Web Services WAP Push communication service does not verify the payload; it passes it on to the underlying network node. |
There is no current specifications covering subscriber-profile LDAP access, although a draft version exists. Gatekeeper’s implementation is based on that draft.
There are no current specifications covering RESTful access to underlying telephony network functionality.
Gatekeeper also supports some native telephony messaging application-facing interfaces. The following specifications are supported:
Off-the shelf, Oracle Communications Services Gatekeeper supports the network protocols listed in Table 10-1 through the use of network plug-ins. Although each plug-in is a part of a given communication service, certain protocols can be used by multiple communication services for different purposes. In these cases there may be multiple implementations of the same protocol for use in different communication services.
Table 10-1 is a list of supported network protocols organized per communication service.
ETSI ES 201 915-4 V1.4.1 (2003-07), Open Service Access (OSA); Application Programming Interface (API); Part 4: Call Control SCF (Parlay 3), part MultiParty Call Control Service. Section MultiParty Call Control Service
See
http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX30.html for links to the specifications
|
||
ETSI ES 201 915-4 V1.4.1 (2003-07), Open Service Access (OSA); Application Programming Interface (API); Part 4: Call Control SCF (Parlay 3), part MultiParty Call Control Service. Section MultiParty Call Control Service.
See
http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX30.html for links to the specifications
|
||
3rd Generation Partnership Project; Technical Specification Group Terminals; Multimedia Messaging Service (MMS); Functional description; Stage 2 (Release 5), 3GPP TS 23.140 V5.3.0.
Messages are compliant with the schema defined by one of REL-5-MM7-1-0.xsd, REL-5-MM7-1-2.xsd, or REL-5-MM7-1-5.xsd, depending on management settings.
http://www.3gpp.org/ftp/Specs/html-info/23140.htm
|
||
3rd Generation Partnership Project; Technical Specification Group Terminals; Multimedia Messaging Service (MMS); Functional description; Stage 2 (Release 5), 3GPP TS 23.140 V5.3.0.
Messages are compliant with the schema defined by one of REL-5-MM7-1-0.xsd, REL-5-MM7-1-2.xsd, or REL-5-MM7-1-5.xsd, depending on management settings.
http://www.3gpp.org/ftp/Specs/html-info/23140.htm
|
||
Location Inter-operability Forum (LIF) Mobile Location Protocol, LIF TS 101 Specification Version 3.0.0
Mobile Location Protocol 3.2 Candidate Version 3.2 Open Mobile Alliance, OMA-TS-MLP-V3_2-20051124-C.
MLP 3.2:
http://www.openmobilealliance.org
|
||
Location Inter-operability Forum (LIF) Mobile Location Protocol, LIF TS 101 Specification Version 3.0.0
Mobile Location Protocol 3.2 Candidate Version 3.2 Open Mobile Alliance, OMA-TS-MLP-V3_2-20051124-C.
MLP 3.2:
http://www.openmobilealliance.org
|
||
ETSI ES 201 915-5 V1.4.1 (2003-07), Open Service Access (OSA); Application Programming Interface (API); Part 5: User Interaction SCF (Parlay 3). Call user interaction parts.
ETSI ES 201 915-4 V1.4.1 (2003-07), Open Service Access (OSA); Application Programming Interface (API); Part 4: Call Control SCF (Parlay 3). Section MultiParty Call Control Service
See
http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX30.html for links to the specifications
|
||
3rd Generation Partnership Project; Technical Specification Group Terminals; Multimedia Messaging Service (MMS); Functional description; Stage 2 (Release 5), 3GPP TS 23.140 V5.3.0.
Messages are compliant with one of two schemas: either REL-5-MM7-1-2.xsd or a slightly modified version of REL-5-MM7-1-0.xsd, both available at: http://www.3gpp.org/ftp/Specs/html-info/23140.htm |
||
Oracle Communications Services Gatekeeper supports the security standards listed below. The security standards are applicable for the application-facing interfaces. Oracle Communications Services Gatekeeper leverages Web Services Security mechanisms provided by WebLogic Server. For more information, see:
| Note: | See http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss for links to the specifications. |
In addition, the following standards are also supported:
Transport-level security mechanisms such as 1- or 2-way SSL or VPN tunneling can be used for the PRM interfaces.
Oracle Communications Services Gatekeeper leverages the robust identity management capabilities of Web Logic Server, including:
|