| Oracle® Communications Services Gatekeeper Concepts Guide Release 5.0 Part Number E16613-02 |
|
|
View PDF |
| Oracle® Communications Services Gatekeeper Concepts Guide Release 5.0 Part Number E16613-02 |
|
|
View PDF |
This appendix describes the specific standards that Services Gatekeeper supports, and provides, where possible, links to the actual specifications.
The standards supported by application-facing interfaces are described here.
The Services Gatekeeper application-facing interfaces support the following parts of the Parlay X 2.1 specification. For links to the specifications, see:
http://docbox.etsi.org/TISPAN/Open/OSA/ParlayX21.html
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).
Terminal Status, ETSI ES 202 391-8 V1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 8: Terminal Status (Parlay X 2).
Audio Call, ETSI ES 202 391-11 v.1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 11: Audio Call (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).
The Services Gatekeeper application-facing interfaces support the following parts of the Draft Parlay X 3.0 specification.
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)
Device Capabilities, 3GPP TS 29.199-18 V7.0.0 (2007-06), Open Service Access (OSA); Parlay X Web Services; Part 18: Device capabilities and configuration (Release 7)
The Extended Web Services are 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:
For links to the specification, seeThe payload, protocol identifier, and validity period rely on:
3GPP TS 23.040 version 6.5.0, Technical realization of Short Message Service (SMS)
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.By default, Services Gatekeeper supports the network protocols listed in Table A-1 through the use of network plug-ins. Although each plug-in is a part of a communication service, certain protocols can be used by multiple communication services for different purposes. There may be multiple implementations of the same protocol for use in different communication services.
Table A-1 is a list of supported network protocols organized per communication service.
Table A-1 Network Plug-Ins Organized by Communication Service
| Communication service | Network protocol plug-in | Specification |
|---|---|---|
|
Parlay X 2.1 Third Party Call (Part 2) |
SIP |
RFC 3261. See |
|
Parlay X 2.1 Third Party Call (Part 2) |
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) |
|
Parlay X 3.0 Third Party Call (Part 2) |
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 |
|
RESTful Third Party Call |
SIP |
RFC 3261. See |
|
Parlay X 2.1 Call Notification (Part 3) |
SIP |
RFC 3261. See |
|
Parlay X 3.0 Call Notification (Part 3) |
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. |
|
RESTful Call Notification |
SIP |
RFC 3261. See |
|
Parlay X 2.1 Short Messaging (Part 4) |
SMPP v3.4 |
Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2. |
|
RESTful Short Messaging |
SMPP v3.4 |
Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2. See |
|
Parlay X 2.1 Multimedia Messaging (Part 5) |
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. See |
|
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. See |
|
Parlay X 2.1 Terminal Location (Part 9) |
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. For information on MLP 3.0, see For information on MLP 3.2, see |
|
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. For information on MLP 3.0, see For information on MLP 3.2, see |
|
Parlay X 2.1 Terminal Status (Part 8) |
MAP |
3rd Generation Partnership Project;Technical Specifications Group Core Network; Mobile Application Part (MAP) specification; (Release 4) 3GPP TS 29.002 v4.18.0. See
|
|
RESTful Terminal Status |
MAP |
3rd Generation Partnership Project;Technical Specifications Group Core Network; Mobile Application Part (MAP) specification; (Release 4) 3GPP TS 29.002 v4.18.0. See
|
|
Parlay X 2.1 Audio Call (Part 11) |
SIP |
Session Initiation Protocol RFC 3261. See |
|
RESTful ParlayX 2.1 Audio Call |
SIP |
Session Initiation Protocol RFC 3261. See |
|
Parlay X 3.0 Audio Call (Part 11) |
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 |
|
Parlay X 2.1 Presence (Part 14) |
SIP |
RFC 3261. See |
|
RESTful Presence |
SIP |
RFC 3261. See |
|
Parlay X 3.0 Device Capabilities and Configuraton (Part 18) |
LDAP |
ETSI ES 202 504-18 V0.0.1 (2006-2007), Open Service Access (OSA); Parlay X Web Services; Part 18: Device Capabilities and Configuration (Parlay X 3). See |
|
Parlay X 3.0 Payment |
Diameter |
RFC3588. See
RFC4006. See
3GPP TS 32.299 version 6.6.0 Release 6. See |
|
RESTful Payment |
Diameter |
RFC3588. See
RFC4006. See
3GPP TS 32.299 version 6.6.0 Release 6. See |
|
Extended Web Services WAP Push |
PAP 2.0 |
Push Access Protocol, WAP Forum, WAP-247-PAP-20010429-a. See |
|
RESTful WAP Push |
PAP 2.0 |
Push Access Protocol, WAP Forum, WAP-247-PAP-20010429-a. See |
|
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. |
|
Extended Web Services Subscriber Profile |
LDAPv3 |
Lightweight Directory Access Protocol, RFC 4510: June 2006. See |
|
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: |
|
Native SMPP |
SMPP v3.4 |
Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2. See |
|
Native UCP |
EMI-UCP Interface 5.0 |
Short Message Service Center EMI-UCP Interface 5.0 specification |
|
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). |
Services Gatekeeper supports the security standards listed below. The security standards are applicable for the application-facing interfaces. Services Gatekeeper leverages Web Services Security mechanisms provided by WebLogic Server. For more information, see:
Oracle® Fusion Middleware Securing Oracle WebLogic Server at: http://download.oracle.com/docs/cd/E15523_01/web.1111/e13707/toc.htm
"Securing Web Services" in Oracle® Fusion Middleware Security and Administrator's Guide for Web Services at: http://download.oracle.com/docs/cd/E15523_01/web.1111/b32511/intro_security.htm
Note:
Seehttp://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.
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)
|
 Copyright © 2007, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|