> Concepts and Architectural Overview > Standards and Specifications

Concepts and Architectural Overview

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Standards and Specifications

The following appendix provides a description of the specific standards that WebLogic Network Gatekeeper supports, along with, where possible, links to the actual specifications. A detailed statement of compliance is also available.

 

Application-facing interfaces

Parlay X 2.1

The Network Gatekeeper application-facing interfaces support the following parts of the Parlay X 2.1 specification.

Note: See http://parlay.org/en/specifications/pxws.asp for links to the specifications.

Parlay X 3.0

The Network Gatekeeper application-facing interfaces support the following parts of the Draft Parlay X 3.0 specification.

Extended Web Services

The Extended Web Services are Network 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:

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:

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

Subscriber Profile LDAP

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

 

Network protocol plug-ins

Off-the shelf, Network 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.

Below 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 l
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
http://parlay.org/en/specifications/apis_archives.asp
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.
http://parlay.org/en/specifications/apis_archives.asp
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/
Parlay X 2.1 Multimedia Messaging
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 the schema defined by REL-5-MM7-1-2.xsd, http://www.3gpp.org/ftp/Specs/html-info/23140.htm

Parlay X 2.1 Terminal Location

MLP 3.0
MLP 3.2

Note: 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
http://parlay.org/en/specifications/apis_archives.asp

Parlay X 2.1 Presence

SIP
RFC 3261.
http://www.ietf.org/rfc/rfc3261.txt
Extended Web Services 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

Not applicable

Parlay 3.3 Framework

Note: 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://parlay.org/en/specifications/apis_archives.asp

 

Security

Network Gatekeeper supports the security standards listed below. The security standards are applicable for the application-facing interfaces. Network Gatekeeper leverage Web Services Security mechanisms provided by WebLogic Server. For more information, see Understanding WebLogic Security and W ebLogic Web Services: Security.

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.

 

Identity and Trust

Network Gatekeeper leverages the robust identity management capabilities of Web Logic Server, including:


  Back to Top       Previous  Next