# Concepts and Architectural Overview

# Standards and Specifications

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.

## Application-Facing Interfaces

### Parlay X 2.1

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.

- Common, ETSI ES 202 391-1 V1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 2).
- Third Party Call, ETSI ES 202 391-2 V1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 2: Third Party Call (Parlay X 2).
- Call Notification, 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).
- Short Messaging, 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).
- Multimedia Messaging, ETSI ES 202 391-5 V1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 5: Multimedia Messaging (Parlay X 2).
- Terminal Location, ETSI ES 202 391-9 V1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 9: Terminal Location (Parlay X 2).
- Presence, ETSI ES 202 391-14 V1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 14: Presence (Parlay X 2).

### Parlay X 3.0

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

- Common, Draft ETSI ES 202 504-1 v.0.0.3 (2007-06), Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 3).
- Third Party Call, Draft ETSI ES 202 504-2 v0.0.5 (2007-06), Open Service Access (OSA); Parlay X Web Services; Part 2; Third Party Call (Parlay X 3).
- Call Notification, Draft ETSI ES 202 504-3 v0.0.3 (2007-06), Open Service Access (OSA); Parlay X Web Services; Part 3: Call Notification (Parlay X 3).
- Audio Call, Draft ETSI ES 202 504-11 v.0.0.3 (2007-06), Open Service Access (OSA); Parlay X Web Services; Part 11: Audio Call (Parlay X 3).
- Payment, 3GPP TS 29.199-6 V7.2.2 (2007-06), Open Service Access (OSA); Parlay X Web Services; Part 6: Payment (Release 7)

### Extended Web Services

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.

#### Binary SMS

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:

- 3GPP TS 23.040 version 6.5.0, Technical realization of Short Message Service (SMS)

#### WAP Push

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:

- WAP Service Indication Specification, as specified in Service Indication Version 31-Jul-2001 Wireless Application Protocol WAP-167-ServiceInd-20010731-a.
- WAP Service Loading Specification, as specified in Service Loading Version 31-Jul-2001 Wireless Application Protocol WAP-168-ServiceLoad-20010731-a.
- WAP Cache Operation Specification, as specified in Cache Operation Version 31-Jul-2001 Wireless Application Protocol WAP-175-CacheOp-20010731-a.

Note: | The Extended Web Services WAP Push communication service does not verify the payload; it passes it on to the underlying network node.

#### Subscriber Profile LDAP

There is no current specifications covering subscriber-profile LDAP access, although a draft version exists. Gatekeeper’s implementation is based on that draft.

### RESTful APIs

There are no current specifications covering RESTful access to underlying telephony network functionality.

### Native

Gatekeeper also supports some native telephony messaging application-facing interfaces. The following specifications are supported:

- MM7: 3GPP TS 23.140 V5.3.0 (REL-5-MM7-1-2.xsd)
- SMPP: SMPP v3.4

## Network Protocol Plug-Ins

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.

Table 10-1 Network Plug-Ins Organized per Communication Service
Communication service | Network protocol plug-in | Specification
--- | --- | ---
Parlay X 2.1 Third Party Call | SIP | RFC 3261. http://www.ietf.org/rfc/rfc3261.txt
INAP/SS7 | ETSI 94 INAP CS1, ETS 300 374-1, Intelligent Network (IN); Intelligent Network Capability Set 1 (CS1); Core Intelligent Network Application Protocol (INAP) http://pda.etsi.org/pda/queryform.asp
Parlay X 3.0 Third Party Call | Parlay 3.3 MultiParty Call Control | 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
RESTful Third Party Call | SIP | RFC 3261. http://www.ietf.org/rfc/rfc3261.txt
Parlay X 2.1 Call Notification | SIP | RFC 3261. http://www.ietf.org/rfc/rfc3261.txt
Parlay X 3.0 Call Notification | Parlay 3.3 MultiParty Call Control | 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
RESTful Call Notification | SIP | RFC 3261. http://www.ietf.org/rfc/rfc3261.txt
Parlay X 2.1 Short Messaging | SMPP v3.4 | Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2. http://smsforum.net/
RESTful Short Messaging | SMPP v3.4 | Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2. http://smsforum.net/
Parlay X 2.1 Multimedia Messaging | MM7 v 5.5.0 | 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
RESTful Multimedia Messaging | MM7 v 5.5.0 | 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
Parlay X 2.1 Terminal Location | MLP 3.0 MLP 3.2 Only one of the above listed protocols can be used at the same moment for a given node in a domain. | Location Inter-operability Forum (LIF) Mobile Location Protocol, LIF TS 101 Specification Version 3.0.0 and Mobile Location Protocol 3.2 Candidate Version 3.2 Open Mobile Alliance, OMA-TS-MLP-V3_2-20051124-C. MLP 3.0: http://www.openmobilealliance.org/tech/affiliates/lif/lifindex.html MLP 3.2: http://www.openmobilealliance.org
RESTful Terminal Location | MLP 3.0 MLP 3.2 Only one of the above listed protocols can be used at the same moment for a given node in a domain. | Location Inter-operability Forum (LIF) Mobile Location Protocol, LIF TS 101 Specification Version 3.0.0 and Mobile Location Protocol 3.2 Candidate Version 3.2 Open Mobile Alliance, OMA-TS-MLP-V3_2-20051124-C. MLP 3.0: http://www.openmobilealliance.org/tech/affiliates/lif/lifindex.html MLP 3.2: http://www.openmobilealliance.org
Parlay X 3.0 Audio Call | Parlay 3.3 Call User Interaction and Parlay 3.3 MultiParty Call Control | 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
Parlay X 2.1 Presence | SIP | RFC 3261. http://www.ietf.org/rfc/rfc3261.txt
RESTful Presence | SIP | RFC 3261. http://www.ietf.org/rfc/rfc3261.txt
Parlay X 3.0 Payment | Diameter | RFC3588 http://tools.ietf.org/html/rfc3588 RFC4006 http://tools.ietf.org/html/rfc4006 3GPP TS 32.299 version 6.6.0 Release 6. http://www.3gpp.org/ftp/Specs/html-info/32299.htm
RESTful Payment | Diameter | RFC3588 http://tools.ietf.org/html/rfc3588 RFC4006 http://tools.ietf.org/html/rfc4006 3GPP TS 32.299 version 6.6.0 Release 6. http://www.3gpp.org/ftp/Specs/html-info/32299.htm
Extended Web Services WAP Push | PAP 2.0 | Push Access Protocol, WAP Forum, WAP-247-PAP-20010429-a. http://www.openmobilealliance.org
RESTful WAP Push | PAP 2.0 | Push Access Protocol, WAP Forum, WAP-247-PAP-20010429-a. http://www.openmobilealliance.org
Extended Web Services Binary SMS | SMPP v3.4 | Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2. http://smsforum.net/
Extended Web Services Subscriber Profile | LDAPv3 | Lightweight Directory Access Protocol, RFC 4510: June 2006 http://tools.ietf.org/html/rfc4510
Native MM7 | MM7 v 5.3.0 | 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
Native SMPP | SMPP v3.4 | Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2. http://smsforum.net/
Not applicable | Parlay 3.3 Framework This is a network-facing protocol that does not belong to a certain communication service. It is used by all Parlay plug-ins. | ETSI ES 201 915-3 V1.4.1 (2003-07), Open Service Access (OSA); Application Programming Interface (API); Part 3: Framework (Parlay 3). http://portal.etsi.org/docbox/TISPAN/Open/OSA/Parlay33.html

## Security

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:

- Securing WebLogic Server at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage
- Securing WebLogic Web Services at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/webserv_sec/

Note: | See http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss for links to the specifications.

- WS-Security Core Specification 1.1
- WS-Security 1.0 and 1.1
- UsernameToken Profile 1.1
- X.509 Certificate Token Profile 1.1
- SAML Token Profile 1.1
- SOAP Message Security 1.0
- SOAP with Attachments (SWA) 1.1

In addition, the following standards are also supported:

- WS-Addressing 1.0, http://www.w3.org/2002/ws/addr/
- WS-Policy 1.1
- WS-SecurityPolicy 1.2, http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702
- WS-Trust 1.3, http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-os.html
- WS-SecureConversation 1.3, http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3-os.html
- WS-ReliableMessaging 1.0
- WS-PolicyAttachment 1.0

Transport-level security mechanisms such as 1- or 2-way SSL or VPN tunneling can be used for the PRM interfaces.

## Identity and Trust

Oracle Communications Services Gatekeeper leverages the robust identity management capabilities of Web Logic Server, including:

- Private Keys
- X.509 v3 Digital Certificates
- Symmetric & Asymmetric Key Algorithms

- DES-CBC
- Two-Key Triple DES
- RC4
- RSA

- Message Digest:

- MD5
- SHA

- JEE 5 & Weblogic Security Packages

- Java Secure Socket Extension (JSSE)
- Java Authentication & Authorization Services (JAAS)
- Java Security Manager
- Java Cryptography Architecture and Java Cryptography Extensions (JCE)
- Java Authorization Contract for Containers (JACC)
- Common Secure Interoperability Version 2 (CSIv2)