Oracle® Communications Services Gatekeeper

Statement of Compliance

Release 5.1

E37532-01

June 2013

Oracle Communications Services Gatekeeper Statement of Compliance, Release 5.1

E37532-01

Copyright © 2007, 2013, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

1 Parlay X 2. 1 Third Party Call

- Parlay X 2.1 Third Party Call Statement of compliance

- SIP for Parlay X 2.1 Third Party Call

- Standards Compliance

- SS7/INAP for Parlay X 2.1 Third Party Call

- Standards Compliance

2 Parlay X 3.0 Third Party Call

- Parlay X 3.0 Third Party Call Statement of Compliance

- Parlay 3.3 MultiParty Call Control plug-in for Parlay X 3.0 Third Party Call

- Standards Compliance

3 Parlay X 2.1 Call Notification

- Parlay X 2.1 Call Notification Statement of Compliance

- SIP for Parlay X 2.1 Call Notification

- Standards Compliance

4 Parlay X 3.0 Call Notification

- Parlay X 3.0 Call Notification Statement of Compliance

- Parlay 3.3 MultiParty Call Control for Parlay X 3.0 Call Notification

- Standards Compliance

5 Parlay X 2.1 Short Messaging (including EWS Binary SMS)

- Parlay X 2.1 Short Messaging Statement of compliance

- SMPP v3.4 for Parlay X 2.1/Extended Web Services Binary SMS

- Standards Compliance

6 Parlay X 2.1 Multimedia Messaging

- Parlay X 2.1 Multimedia Messaging Statement of compliance

- MM7 v 5.3 for Parlay X 2.1 Multimedia Messaging

- Standards Compliance

- MM7 v 6.8.0 for Parlay X 2.1 Multimedia Messaging

7 Parlay X 3.0 Payment

- Parlay X 3.0 Payment

- Diameter for Parlay X 3.0 Payment

- Standards Compliance

8 Parlay X 2.1 Terminal Status

- Parlay X 2.1 Terminal Status

- SS7/MAP Terminal Status

- Standards Compliance

9 Parlay X 2.1 Terminal Location

- Parlay X 2.1 Terminal Location

- MLP 3.0/3.2 for Parlay X 2.1 Terminal Location

- Standards Compliance

10 Parlay X 2.1 Audio Call

- Parlay X 2.1 Audio Call Statement of Compliance

- SIP for Parlay X 2.1 Audio Call

- Standards Compliance

11 Parlay X 3.0 Audio Call

- Parlay X 3.0 Audio Call

- Parlay 3.3 User Interaction and MultiParty Call Control for Parlay X 3.0 Audio Call

- Standards Compliance

12 Parlay X 2.1 Presence

- Parlay X 2.1 Presence

- SIP for Parlay X 2.1 Presence

- Standards Compliance

13 Parlay X 3.0 Device Capabilities and Configuration

- Parlay X 3.0 Device Capabilities and Configuration

- LDAP for Device Capabilities and Configuration

- Standards Compliance

14 Parlay X 3.0 Application Subscription Management

- Application Subscription Management Statement of Compliance

- Supported Operations

15 Extended Web Services WAP Push

- Extended Web Services WAP Push

- WAP Push for Extended Web Services WAP Push

- Standards Compliance

16 Extended Web Services Subscriber Profile

- Extended Web Services Subscriber Profile

- LDAP for Extended Web Services Subscriber Profile

- Standards Compliance

17 Native MM7

- Native MM7

- Native MM7 Service Facade Standards Compliance

- Native MM7 Service Enabler Standards Compliance

18 Native SMPP

- Native SMPP

- Native SMPP Service Facade Standards Compliance

- Native SMPP Service Enabler Standards Compliance

- Native SMPP Version 5.1 Standards Compliance

19 Native UCP

- Native UCP

20 Parlay 3.3 Framework for plug-ins of Parlay type

- Parlay 3.3 Framework for Parlay plug-ins

- Standards Compliance

21 Parlay X Web Services Address List Management

- Parlay X Web Services Address List Management

- Standards Compliance

22 QoS Diameter Policy and Charging Control Over Diameter Rx

- QoS Diameter Policy and Charging Control Over Rx

- Standards Compliance

- Supported Rx AA-Request (AAR) AVPs

- Supported Rx AA-Answer (AAA) AVPs

- Supported Rx Re-Auth-Request (RAR) AVPs

- Supported Rx Re-Auth-Answer (RAA) AVPs

- Supported Rx Session-Termination-Request (STR) AVPs

- Supported Rx Session-Termination-Answer (STA) AVPs

- Supported Rx Abort-Session-Request (ASR) AVPs

- Supported Rx Abort-Session-Answer (ASA) AVPs

Preface

This document is a statement of compliance for the communication services supported by Oracle Communications Services Gatekeeper.

Audience

This document is for system administrators who manage Oracle Communications Services Gatekeeper, as well as managers, support engineers, sales, and marketing.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documents in this documentation set:

- Oracle Communications Services Gatekeeper Accounts and SLAs Guide

- Oracle Communications Services Gatekeeper Alarm Handling Guide

- Oracle Communications Services Gatekeeper Application Developer's Guide

- Oracle Communications Services Gatekeeper Communication Service Guide

- Oracle Communications Services Gatekeeper Concepts Guide

- Oracle Communications Services Gatekeeper Installation Guide

- Oracle Communications Services Gatekeeper Licensing Guide

- Oracle Communications Services Gatekeeper Partner Relationship Management Guide

- Oracle Communications Services Gatekeeper Platform Development Studio Developer's Guide

- Oracle Communications Services Gatekeeper Platform Test Environment Guide

- Oracle Communications Services Gatekeeper RESTful Application Developer's Guide

- Oracle Communications Services Gatekeeper SDK User's Guide

- Oracle Communications Services Gatekeeper System Administrator's Guide

- Oracle Communications Services Gatekeeper System Backup and Restore Guide

1 Parlay X 2. 1 Third Party Call

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 2.1 Third Party Call communication service and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Third Party Call Statement of compliance

- SIP for Parlay X 2.1 Third Party Call

- SS7/INAP for Parlay X 2.1 Third Party Call

Parlay X 2.1 Third Party Call Statement of compliance

This section describes the standards compliance for the communication services for Parlay X 2.1 Third Party call

The Parlay X 2.1 interface complies to ETSI ES 202 391-2 V1.2.1 Open Service Access (OSA); Parlay X Web Services; Part 2: Third Party Call (Parlay X 2)

See

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

for links to the specification.

Table 1-1 Statement of Compliance, Parlay X 2.1 Third Party Call

Method

Compliant(Yes | No)

Comment

Interface: ThirdPartyCall

N/A

MakeCall

Y

N/A

GetCallInformation

Y

N/A

EndCall

Y

N/A

CancelCall

Y

N/A

SIP for Parlay X 2.1 Third Party Call

The SIP plug-in for Parlay X 2.1 Third Party Call is an integration plug-in that utilizes Oracle Converged Application Server (OCCAS) to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in OCCAS. The SIP Servlet uses the SIP API provided by the OCCAS, which in its turn converts the API calls to SIP messages.

The SIP servlet acts as a Back-to-Back User Agent for all calls.

Standards Compliance

The SIP servlet uses the WebLogic SIP server, which conforms to RFC 3261.

The RFC is found on http://www.ietf.org/rfc/rfc3261.txt

The implementation of the SIP based third party call is in compliance with RFC 3725 - Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) Flow I.

The RFC is found on http://www.ietf.org/rfc/rfc3725.txt

Table 1-2 Statement of Compliance, SIP for Parlay X 2.1 Third Party Call

Message/Response

Compliant(Yes/No)

Comment

REGISTER

-

Not used in the context.

INVITE

Y

N/A

ACK

Y

N/A

CANCEL

Y

N/A

BYE

Y

N/A

OPTIONS

-

Not used in the context.

100 Trying

Y

N/A

180 Ringing

Y

N/A

181 Call Is Being Forwarded

Y

N/A

182 Queued

Y

N/A

183 Session Progress

Y

N/A

200 OK

Y

N/A

300 Multiple Choices

Y

UA treated as unreachable.

301 Moved Permanently

Y

UA treated as unreachable.

302 Moved Temporarily

Y

UA treated as unreachable.

305 Use Proxy

Y

UA treated as unreachable.

380 Alternative Service

Y

UA treated as unreachable.

400 Bad Request

Y

UA treated as unreachable

401 Unauthorized

Y

UA treated as unreachable

402 Payment Required

Y

UA treated as unreachable

403 Forbidden

Y

UA treated as unreachable

404 Not Found

Y

UA treated as unreachable

405 Method Not Allowed

Y

UA treated as unreachable

406 Not Acceptable

Y

UA treated as unreachable

407 Proxy Authentication Required

Y

UA treated as unreachable

408 Request Timeout

Y

Treated as no answer from UA.

410 Gone

Y

UA treated as unreachable

413 Request Entity Too Large

Y

UA treated as unreachable

414 Request-URI Too Long

Y

UA treated as unreachable

415 Unsupported Media Type

Y

UA treated as unreachable

416 Unsupported URI Scheme

Y

UA treated as unreachable

420 Bad Extension

Y

UA treated as unreachable

421 Extension Required

Y

UA treated as unreachable

423 Interval Too Brief

Y

UA treated as unreachable

480 Temporarily Unavailable

Y

UA treated as unreachable

481 Call/Transaction Does Not Exist

Y

UA treated as unreachable

482 Loop Detected

Y

UA treated as unreachable

483 Too Many Hops

Y

UA treated as unreachable

484 Address Incomplete

Y

UA treated as unreachable

485 Ambiguous

Y

UA treated as unreachable

486 Busy Here

Y

UA treated as busy.

487 Request Terminated

Y

UA treated as unreachable

488 Not Acceptable Here

Y

UA treated as unreachable

491 Request Pending

Y

UA treated as unreachable

493 Undecipherable

Y

UA treated as unreachable

500 Server Internal Error

Y

UA treated as unreachable

501 Not Implemented

Y

UA treated as unreachable

502 Bad Gateway

Y

UA treated as unreachable

503 Service Unavailable

Y

UA treated as unreachable

504 Server Time-out

Y

UA treated as unreachable

505 Version Not Supported

Y

UA treated as unreachable

513 Message Too Large

Y

UA treated as unreachable.

600 Busy Everywhere

Y

UA treated as unreachable

603 Decline

Y

UA treated as unreachable

604 Does Not Exist Anywhere

Y

UA treated as unreachable.

606 Not Acceptable

Y

UA treated as unreachable

SS7/INAP for Parlay X 2.1 Third Party Call

The SS7/INAP plug-in for Parlay X 2.1 Third Party Call is an integration plug-in that utilizes the TietoEnator SS7 stack to connect to a SS7 network. The plug-in uses TietoEnator's Java INAP API to connect to the SS7 stack.

The plug-in acts as an INAP Application for all calls.

Standards Compliance

The plug-in conforms to ETSI 94 INAP CS1, ETS 300 374-1RFC 3261.

The specification is found on http://webapp.etsi.org/workprogram/Report_WorkItem.asp?WKI_ID=1394

Table 1-3 Statement of Compliance, INAP/SS7 for Parlay X 2.1 Third Party Call

Operation

Compliant(Yes/No)

Comment

ActivateServiceFiltering

N

Not used in context.

ActivityTest

N

Not used in context.

ApplyCharging

N

Not used in context.

ApplyChargingReport

N

Not used in context.

AssistRequestInstructions

N

Not used in context.

CallGap

N

Not used in context.

CallInformationReport

N

Not used in context.

CallInformationRequest

N

Not used in context.

Cancel

N

Not used in context.

CollectInformation

N

Not used in context.

Connect

Y

ConnectToResource

N

Not used in context.

Continue

Y

DisconnectForwardConnection

N

Not used in context.

EstablishTemporaryConnection

N

Not used in context.

EventNotificationCharging

N

Not used in context.

EventReportBCSM

Y

FurnishChargingInformation

N

Not used in context.

InitialDP

N

Not used in context.

InitiateCallAttempt

Y

PlayAnnouncement

N

Not used in context.

PromptAndCollectUserInformation

N

Not used in context.

ReleaseCall

Y

RequestNotificationChargingEvent

N

Not used in context.

RequestReportBCSMEvent

Y

ResetTimer

N

Not used in context.

SendChargingInformation

N

Not used in context.

ServiceFilteringResponse

N

Not used in context.

SpecializedResourceReport

N

Not used in context.

2 Parlay X 3.0 Third Party Call

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 3.0 communication service and how its interfaces and protocols comply with standards.

- Parlay X 3.0 Third Party Call Statement of Compliance

- Parlay 3.3 MultiParty Call Control plug-in for Parlay X 3.0 Third Party Call

Parlay X 3.0 Third Party Call Statement of Compliance

This section describes the standards compliance for the communication service for Parlay X 3.0 Third Party call:

The Parlay X 3.0 interface complies to 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.0).

See ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-02/29199-02-740.zip for links to the specification.

Table 2-1 Statement of Compliance, Parlay X 3.0 Third Party Call

Method

Compliant(Yes | No)

Comment

Interface: ThirdPartyCall

makeCallSession

Y

mediaInfo parameter not supported; changeMediaNotAllowed always true. Media always negotiated by underlying network.

addCallParticipant

Y

mediaInfo parameter not supported

transferCallParticipant

Y

getCallParticipantInformation

Y

getCallSessionInformation

Y

deleteCallParticipant

Y

endCallSession

Y

Parlay 3.3 MultiParty Call Control plug-in for Parlay X 3.0 Third Party Call

The Parlay 3.3 MultiParty Call Control plug-in for Parlay X 3.0 Third Party Call acts as a OSA/Parlay application towards an OSA/Parlay Gateway. It uses the OSA/Parlay Framework to get hold of the MultiParty Call Control SCS. This is done via the OSA Access Service, see "Parlay 3.3 Framework for plug-ins of Parlay type".

Standards Compliance

The plug-in complies to 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.

A link to the specification is found at ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-02/29199-02-740.zip

Table 2-2 Statement of Compliance, Parlay 3.1 MultiParty Call Control for Parlay X 3.0 Third Party Call

Method

Compliant(Yes | No)

Comment

Interface: IpMultiPartyCallControlManager

createCall

Y

createNotification

N

Not used in the context

destroyNotification

N

Not used in the context

changeNotification

N

Not used in the context

getNotification

N

Not used in the context

setCallLoadControl

N

Not used in the context

Interface: IpMultiPartyCall

getCallLegs

N

Not used in the context

createCallLeg

Y

createAndRouteCallLegReq

N

Not used in the context

release

Y

deassignCall

N

Not used in the context

getInfoReq

Y

setChargePlan

N

Not used in the context

setAdviceOfCharge

N

Not used in the context

superviseReq

N

Not used in the context

Interface: IpCallLeg

routeReq

Y

eventReportReq

Y

release

Y

getInfoReq

Y

getCall

N

Not used in the context

attachMediaReq

N

Not used in the context

detachMediaReq

N

Not used in the context

getCurrentDestinationAddress

N

Not used in the context

continueProcessing

Y

setChargePlan

N

Not used in the context

setAdviceOfCharge

N

Not used in the context

superviseReq

N

Not used in the context

deassign

N

Not used in the context

Interface: IpAppMultiPartyCallControlManager

reportNotification

N

Not used in the context

callAborted

N

Not used in the context

managerInterrupted

N

Not used in the context

managerResumed

N

Not used in the context

callOverloadEncountered

N

Not used in the context

callOverloadCeased

N

Not used in the context

Interface: IpAppMultiPartyCall

getInfoRes

Y

getInfoErr

Y

superviseRes

N

Not used in the context

superviseErr

N

Not used in the context

callEnded

Y

createAndRouteCallLegErr

N

Not used in the context

Interface: IpAppCallLeg

eventReportRes

Y

eventReportErr

Y

attachMediaRes

N

Not used in the context

attachMediaErr

N

Not used in the context

detachMediaRes

N

Not used in the context

detachMediaErr

N

Not used in the context

getInfoRes

Y

getInfoErr

Y

routeErr

Y

Not used in the context

superviseRes

N

Not used in the context

superviseErr

N

Not used in the context

callLegEnded

Y

3 Parlay X 2.1 Call Notification

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 2.1 Call Notification communication service and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Call Notification Statement of Compliance

- SIP for Parlay X 2.1 Call Notification

Parlay X 2.1 Call Notification Statement of Compliance

This section describes the standards compliance for the communication services for Parlay X 2.1 Call notification:

The Parlay X 2.1 interface complies to 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). See

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

for links to the specification.

Table 3-1 Statement of Compliance, Parlay X 2.1 Call Notification

Method

Compliant(Yes | No)

Comment

Interface: CallDirection

handleBusy

Y

handleNotReachable

Y

handleNoAnswer

Y

handleCalledNumber

Y

Interface: CallNotification

notifyBusy

Y

notifyNotReachable

Y

notifyNoAnswer

Y

notifyCalledNumber

Y

Interface: CallDirectionManager

startCallDirectionNotification

Y

stopCallDirectionNotification

Y

Interface: CallNotificationManager

StartCallNotification

Y

stopCallNotification

Y

SIP for Parlay X 2.1 Call Notification

The SIP plug-in for Parlay X 2.1 Call Notification is an integration plug-in that utilizes the Oracle Converged Application Server (OCCAS) to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in WebLogic SIP Server. The SIP Servlet uses the SIP API provided by the WebLogic SIP server, which in its turn converts the API calls to SIP messages.

The SIP servlet acts as both as a SIP User Agent and a SIP Proxy. Depending on which Parlay X operation and state of the call the SIP servlet acts either as a proxy or as the calling party. This means that the calling UA must use WebLogic SIP server as a SIP Proxy.

Standards Compliance

The SIP servlet uses the WebLogic SIP server, which conforms to RFC 3261.

The specification is found on http://www.ietf.org/rfc/rfc3261.txt

Table 3-2 Statement of Compliance, SIP for Parlay X 2.1 Call Notification

Message/Response

Compliant(Yes/No)

Comment

REGISTER

-

Not used in the context.

INVITE

Y

ACK

Y

CANCEL

Y

BYE

Y

OPTIONS

-

Not used in the context.

INFO

-

Not used in the context.

100 Trying

Y

180 Ringing

Y

181 Call Is Being Forwarded

Y

Not used in the context.

182 Queued

Y

Not used in the context.

183 Session Progress

Y

Not used in the context.

200 OK

Y

300 Multiple Choices

Y

UA treated as unreachable.

301 Moved Permanently

Y

UA treated as unreachable.

302 Moved Temporarily

Y

UA treated as unreachable.

305 Use Proxy

Y

UA treated as unreachable.

380 Alternative Service

Y

UA treated as unreachable.

400 Bad Request

Y

UA treated as unreachable

401 Unauthorized

Y

UA treated as unreachable

402 Payment Required

Y

UA treated as unreachable

403 Forbidden

Y

UA treated as unreachable

404 Not Found

Y

UA treated as unreachable

405 Method Not Allowed

Y

UA treated as unreachable

406 Not Acceptable

Y

UA treated as unreachable

407 Proxy Authentication Required

Y

UA treated as unreachable

408 Request Timeout

Y

Treated as no answer from UA.

410 Gone

Y

UA treated as unreachable

413 Request Entity Too Large

Y

UA treated as unreachable

414 Request-URI Too Long

Y

UA treated as unreachable

415 Unsupported Media Type

Y

UA treated as unreachable

416 Unsupported URI Scheme

Y

UA treated as unreachable

420 Bad Extension

Y

UA treated as unreachable

421 Extension Required

Y

UA treated as unreachable

423 Interval Too Brief

Y

UA treated as unreachable

480 Temporarily Unavailable

Y

UA treated as unreachable

481 Call/Transaction Does Not Exist

Y

UA treated as unreachable

482 Loop Detected

Y

UA treated as unreachable

483 Too Many Hops

Y

UA treated as unreachable

484 Address Incomplete

Y

UA treated as unreachable

485 Ambiguous

Y

UA treated as unreachable

486 Busy Here

Y

487 Request Terminated

Y

UA treated as unreachable

488 Not Acceptable Here

Y

UA treated as unreachable

491 Request Pending

Y

UA treated as unreachable

493 Undecipherable

Y

UA treated as unreachable

500 Server Internal Error

Y

UA treated as unreachable

501 Not Implemented

Y

UA treated as unreachable

502 Bad Gateway

Y

UA treated as unreachable

503 Service Unavailable

Y

UA treated as unreachable

504 Server Time-out

Y

UA treated as unreachable

505 Version Not Supported

Y

UA treated as unreachable

513 Message Too Large

Y

UA treated as unreachable

600 Busy Everywhere

Y

UA treated as unreachable

603 Decline

Y

UA treated as unreachable

604 Does Not Exist Anywhere

Y

UA treated as unreachable

606 Not Acceptable

Y

UA treated as unreachable

Note:
When a Parlay X application returns ActionValues.Route in Action.actionToPerform as a response to operations in Interface: CallDirection, a record-route header is inserted in the SIP Message the in order to stay in the call path.

4 Parlay X 3.0 Call Notification

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 3.0 Call Notification communication services and how their interfaces and protocols comply to standards.

- Parlay X 3.0 Call Notification Statement of Compliance

- Parlay 3.3 MultiParty Call Control for Parlay X 3.0 Call Notification

Parlay X 3.0 Call Notification Statement of Compliance

This section describes the standards compliance for the communication service for Parlay X 3.0 Call Notification to Parlay 3.3 MultipParty Call Control:

The Parlay X 3.0 interface complies to 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).

See

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-02/29199-02-740.zip

for links to the specification.

Table 4-1 Statement of Compliance, Parlay X 3.0 Call Notification

Method

Compliant(Yes | No)

Comment

Interface: CallDirection

handleBusy

Y

handleNotReachable

Y

handleNoAnswer

Y

handleCalledNumber

Y

Interface: CallNotification

notifyBusy

Y

notifyNotReachable

Y

notifyNoAnswer

Y

notifyCalledNumber

Y

notifyAnswer

Y

notifyPlayAndCollectEvent

Y

notifyPlayAndRecordEvent

N

Interface: CallDirectionManager

startCallDirectionNotification

Y

stopCallDirectionNotification

Y

Interface: CallNotificationManager

StartCallNotification

Y

stopCallNotification

Y

startPlayAndCollectNotification

Y

startPlayAndRecordNotification

N

stopMediaInteractionNotification

Y

Parlay 3.3 MultiParty Call Control for Parlay X 3.0 Call Notification

The Parlay 3.3 MultiParty Call Control plug-in for Parlay X 3.0 Call Notification acts as a OSA/Parlay application towards an OSA/Parlay Gateway. It uses the OSA/Parlay Framework to get hold of the MultiParty Call Control SCS. This is done using the OSA Access Service, see "Parlay 3.3 Framework for plug-ins of Parlay type".

Standards Compliance

The plug-in complies to 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.

It also complies with 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).

Links to the specifications are found at:

http://www.etsi.org/deliver/etsi_es/201900_201999/20191505/01.04.01_60/es_20191505v010401p.pdf

Table 4-2 Statement of Compliance, Parlay 3.3 MultiParty Call Control for Parlay X 2.1 Call Notification

Method

Compliant(Yes | No)

Comment

Interface: IpMultiPartyCallControlManager

createCall

N

Not used in the context

createNotification

Y

destroyNotification

Y

changeNotification

N

Not used in the context

getNotification

N

Not used in the context

setCallLoadControl

N

Not used in the context

Interface: IpMultiPartyCall

getCallLegs

N

Not used in the context

createCallLeg

N

Not used in the context

createAndRouteCallLegReq

Y

release

Y

deassignCall

N

Not used in the context

getInfoReq

N

Not used in the context

setChargePlan

N

Not used in the context

setAdviceOfCharge

N

Not used in the context

superviseReq

N

Not used in the context

Interface: IpCallLeg

routeReq

N

Not used in the context

eventReportReq

N

Not used in the context

release

N

Not used in the context

getInfoReq

N

Not used in the context

getCall

N

Not used in the context

attachMediaReq

N

Not used in the context

detachMediaReq

N

Not used in the context

getCurrentDestinationAddress

N

Not used in the context

getLastRedirectedAddress

N

Not used in the context

continueProcessing

Y

setChargePlan

N

Not used in the context

setAdviceOfCharge

N

Not used in the context

superviseReq

N

Not used in the context

deassign

N

Not used in the context

Interface: IpAppMultiPartyCallControlManager

reportNotification

Y

callAborted

Y

Consumed without action.

managerInterrupted

Y

Consumed without action.

managerResumed

Y

Consumed without action.

callOverloadEncountered

Y

Consumed without action.

callOverloadCeased

Y

Consumed without action.

Interface: IpAppMultiPartyCall

getInfoRes

Y

getInfoErr

Y

Consumed without action.

superviseRes

Y

Consumed without action.

superviseErr

Y

Consumed without action.

callEnded

Y

createAndRouteCallLegErr

Y

Consumed without action.

Interface: IpAppCallLeg

eventReportRes

Y

Consumed without action.

eventReportErr

Y

Consumed without action.

attachMediaRes

Y

Consumed without action.

attachMediaErr

Y

Consumed without action.

detachMediaRes

Y

Consumed without action.

detachMediaErr

Y

Consumed without action.

getInfoRes

Y

Consumed without action.

getInfoErr

Y

Consumed without action.

routeErr

Y

Consumed without action.

superviseRes

Y

Consumed without action.

superviseErr

Y

Consumed without action.

callLegEnded

Y

Table 4-3 Statement of Compliance, Parlay 3.3 User Interaction for Parlay X 2.1 Call Notification

Method

Compliant(Yes | No)

Comment

Interface: IpUIManager

createUI

N

Not used in the context

createUICall

N

Not used in the context

createNotification

N

Not used in the context

destroyNotification

N

Not used in the context

changeNotification

N

Not used in the context

getNotification

N

Not used in the context

Interface: IpAppUIManager

userInteractionAborted

N

Not used in the context

reportNotification

N

Not used in the context

userInteractionNotificationInterrupted

N

Not used in the context

userInteractionNotificationContinued

N

Not used in the context

reportEventNotification

N

Not used in the context

Interface: IpUI

sendInfoReq

N

Not used in the context

sendInfoAndCollectReq

N

Not used in the context

release

N

Not used in the context

Interface: IpAppUI

sendInfoRes

N

Not used in the context

sendInfoErr

N

Not used in the context

sendInfoAndCollectRes

Y

sendInfoAndCollectErr

N

Not used in the context

userInteractionFaultDetected

N

Not used in the context

Interface: IpUICall

recordMessageReq

N

Not used in the context

deleteMessageReq

N

Not used in the context

abortActionReq

N

Not used in the context

Interface: IpAppUICall

recordMessageRes

N

Not used in the context

recordMessageErr

N

Not used in the context

deleteMessageRes

N

Not used in the context

deleteMessageErr

N

Not used in the context

abortActionRes

N

Not used in the context

abortActionErr

N

Not used in the context

5 Parlay X 2.1 Short Messaging (including EWS Binary SMS)

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 2.1 Short Messaging communication services and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Short Messaging Statement of compliance

- SMPP v3.4 for Parlay X 2.1/Extended Web Services Binary SMS

Parlay X 2.1 Short Messaging Statement of compliance

This section describes the standards compliance for the communication services for Parlay X 2.1:

The Parlay X 2.1 interface complies with 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).

See

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

for links to the specification.

Table 5-1 Statement of Compliance, Parlay X 2.1 Short Messaging

Method

Compliant(Yes | No)

Comment

Interface: SendSms

sendSms

Y

sendSmsLogo

Y

Note: The image is not scaled.

sendSmsRingtone

Y

Note: Ringtones must be in either SmartMessaging or EMS (iMelody) format

getSmsDeliveryStatus

Y

Interface: SmsNotification

notifySmsReception

Y

notifySmsDeliveryReceipt

Y

Interface: ReceiveSms

getReceivedSms

Y

Interface: SmsNotificationManager

startSmsNotification

Y

stopSmsNotification

Y

SMPP v3.4 for Parlay X 2.1/Extended Web Services Binary SMS

The SMPP v3.4 plug-in for Parlay X 2.1 Short Messaging and for the Extended Web Services (Binary SMS) acts as an External Short Message Entity (ESME) that connects to an SMSC over TCP/IP.

The plug-in instance binds itself to the SMSC either as ESME Transmitter and an ESME Receiver or as an ESME Transceiver.

The bindings occurs when the plug-in transitions from state inactive to active. It will not reach state active until it has bound. The plug-in unbinds itself prior to becoming inactive.

When an application sends an SMS with one recipient submit_sm PDU is used and when sending an SMS with 2 or more recipients submit_sm_multi is used.

Window size is configurable.

For application-initiated requests, the plug-in supports segmented SMSs using either 7-, 8-, or 16 bit data coding. The maximum length of an SMS segment is:

- 160 Characters for 7 bit data coding (SMSC default alphabet).

- 140 Characters for 8 bit data coding (ASCII).

- 70 Characters for 16bit coding (UCS2).

For network-triggered requests, the plug-in supports segmented SMSs in the same way as for application-initiated requests if the SMPP parameter short_message contains the user data. If short_message is empty the parameter message_payload, which can contain up to 64KB of data, is used.

For network-triggered requests, the SMS is propagated to the application via the Parlay X Short Messaging interface if the SMPP parameter data_coding equals 0x00, 0x01, 0x03, 0x05, 0x06, 0x07, 0x08, 0x0A, 0x0D, or 0x0E. In other cases, the SMS is forwarded to the application via the Binary SMS interface.

Standards Compliance

The plug-in complies to Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2.

Table 5-2 Statement of Compliance, SMPP v3.4 for Parlay X 2.1 Short Messaging

Protocol Data Units (PDUs)

Compliant(Yes | No)

Comment

Plug-in originated PDUs:

bind_transmitter

Y

bind_receiver

Y

unbind

Y

submit_sm

Y

submit_multi

Y

deliver_sm_resp

Y

cancel_sm

Y

enquire_link

Y

enquire_link_resp

Y

generic_nack

Y

bind_transceiver

Y

data_sm

N

data_sm_resp

N

query_sm

N

replace_sm

N

SMSC originated PDUs:

bind_transmitter_resp

Y

bind_receiver_resp

Y

unbind_resp

Y

submit_sm_resp

Y

esm_classes:

- Default message Type

- SMSC Delivery receipt

submit_multi_resp

Y

deliver_sm

Y

cancel_sm_resp

Y

enquire_link

Y

enquire_link_resp

Y

generic_nack

Y

bind_transceiver_resp

Y

outbind

N

data_sm

N

data_sm_resp

N

query_sm_resp

N

replace_sm_resp

N

alert_notification

N

The Parlay X 2.1 Short Messaging and EWS Binary SMS communication services support the following features, which are defined in the Short Message Peer-to-Peer Protocol Specification, Version 5.1. Services Gatekeeper supports these features as tunneled parameters.

Table 5-3 Statement of Compliance for Version 5.1 Features

Parameter

Section in Specification

Comments

billing_identification

4.8.4.3

ussd_service_operation

4.8.4.64

Version 5.1 added support to deliver_sm for bidrectional USSD.

interface_version

4.7.13

The Native SMPP Service accepts 5.1 as well as 3.4 as the interface version number.

6 Parlay X 2.1 Multimedia Messaging

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 2.1 communication services and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Multimedia Messaging Statement of compliance

- MM7 v 5.3 for Parlay X 2.1 Multimedia Messaging

Parlay X 2.1 Multimedia Messaging Statement of compliance

This section describes the standards compliance for the communication services for Parlay X 2.1 Multimedia Messaging:

The Parlay X 2.1 interface complies to 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).

See ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip for links to the specification.

Table 6-1 Statement of Compliance, Parlay X 2.1 Multimedia Messaging

Method

Compliant(Yes | No)

Comment

Interface: SendMessage

SendMessage

Y

GetMessageDeliveryStatus

Y

Interface: ReceiveMessage

GetReceivedMessages

Y

GetMessageURIs

N

throws an exception 'not supported'

GetMessage

Y

Interface: MessageNotification

NotifyMessageReception

Y

NotifyMessageDeliveryReceipt

Y

Interface: MessageNotificationManager

StartMessageNotification

Y

StopMessageNotification

Y

MM7 v 5.3 for Parlay X 2.1 Multimedia Messaging

The MM7 plug-in for Parlay for Parlay X 2.1 Multimedia Messaging acts as an MMS VAS Application towards an MMS Relay/Server using the MM7 interface. It connects to the MMS/Relay Server using SOAP 1.1 over HTPP. It supports HTTP Basic Authentication for authentication.

The plug-in itself may act as one single MMS VAS Application, or, alternatively, the Service Provider ID acts as the VASP (Value Added Service Provider) ID and the Application ID/Application Instance Group ID combination acts as the VAS (Value Added Service) ID.

Standards Compliance

The plug-in complies to 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 XSD schemes defined with name space http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2

It also supports the 7-1-0 XSD, adapted to support delivery notifications, Rel5-mm7-1-2.xsd, and 7-1-5 XSD.

A link to the specification is found on http://www.3gpp.org/ftp/Specs/html-info/23140.htm

The plug-in support MSISDN (E.164) addresses and mail to URIs.

It supports authentication using HTTP Basic Authentication according to HTTP Authentication: Basic and Digest Access Authentication, IETF; RFC 2617.

Table 6-2 Statement of Compliance,MM7 v 5.3 for Parlay X 2.1 Multimedia Messaging

Operation

Compliant(Yes | No)

Comment

Plug-in originated operations:

MM7_submit.REQ

Y

MM7_cancel.REQ

N

Not used in this context

MM7_delivery_report.RES

Y

MM7_deliver.RES

Y

MM7_replace.REQ

N

Not used in this context

MM7_read_reply.RES

N

Not used in this context

MM7_VASP_error.RES

N

Not used in this context

MMSC originated operations:

MM7_submit.RES

Y

MM7_cancel.RES

N

Not used in this context

MM7_delivery_report.REQ

Y

MM7_deliver.REQ

Y

MM7_RS_error.RES

Y

MM7_replace.RES

N

Not used in this context

MM7_read_reply.REQ

N

Not used in this context

MM7 v 6.8.0 for Parlay X 2.1 Multimedia Messaging

This section describes the MM7 plug-in's compliance with the specification. See

http://www.3gpp.org/ftp/Specs/html-info/23140.htm

for the version 6.8.0 specification.

Services Gatekeeper supports all mandatory parameters described in the MM7 specification. It also supports some optional parameters through plug-in mbean attributes or as context attributes as part of the Parlay X request.

The plug-in supports the following operations and parameters.

Table 6-3 Compliance for MM7 Submit Operation

Parameter

Mandatory or Optional

Compliant

TransactionID

Mandatory

Y

MM7Version

Mandatory

Y

MessageType

Mandatory

Y

Sender Identification

Optional

Y-SenderAddress,VASPID,VASID

RecipientAddress

Mandatory

Y

ServiceCode

Optional

Y

LinkedID

Optional

N

MessageClass

Optional

N

TimeStamp

Optional

N

ReplyChargingID

Optional

N

EarliestDeliveryTime

Optional

N

ExpiryDate

Optional

N

DeliveryReport

Optional

Y

ReadReply

Optional

N

Priority

Optional

Y

Subject

Optional

Y

ChargedParty

Optional

Y

ChargedPartyID

Optional

Y

DistributionIndicator

Optional

N

Content

Optional

N

Content-Type

Mandatory

Y

Table 6-4 Compliance for MM7 Submit Response Operation

Parameter

Mandatory, Conditional,or Optional

Compliant

TransactionID

Mandatory

Y

MM7Version

Mandatory

Y

Status

Mandatory

Y

MessageID

Conditional

Y

Table 6-5 Compliance for MM7 Deliver Operation

Parameter

Mandatory or Optional

Compliant

TransactionID

Mandatory

Y

MM7Version

Mandatory

Y

MMSRelayServerID

Optional

Y

LinkedID

Optional

N

Sender

Mandatory

Y

Recipients

Optional

Y

TimeStamp

Optional

Y

ReplyChargingID

Optional

N

Priority

Optional

Y

Subject

Optional

Y

Content

Optional

Y

Content-Type

Mandatory

Y

Table 6-6 Compliance for MM7 Deliver Response Operation

Parameter

Mandatory or Optional

Compliant

TransactionID

Mandatory

Y

MM7Version

Mandatory

Y

ServiceCode

Optional

Y

Status

Mandatory

Y

Table 6-7 Compliance for MM7 Delivery Report Operation

Parameter

Mandatory or Optional

Compliant

TransactionID

Mandatory

Y

MM7Version

Mandatory

Y

MMSRelayServerID

Optional

Y

MessageID

Mandatory

Y

Recipient

Mandatory

Y

Sender

Mandatory

Y

Date

Mandatory

Y

MMStatus

Mandatory

Y

Table 6-8 Compliance for MM7 Delivery Report Response Operation

Parameter

Mandatory or Optional

Compliant

TransactionID

Mandatory

Y

MM7Version

Mandatory

Y

Status

Mandatory

Y

7 Parlay X 3.0 Payment

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 3.0 Payment communication services and how the interfaces and protocols comply to standards.

- Parlay X 3.0 Payment

- Diameter for Parlay X 3.0 Payment

Parlay X 3.0 Payment

This section describes the standards compliance for the communication services for Parlay X 3.0 Payment:

- Diameter for Parlay X 3.0 Payment

- Standards Compliance

The Parlay X 3.0 interface complies to ETSI ES 202 504-6 v0.0.4 (2007-06), Open Service Access (OSA); Parlay X Web Services; Part 6: Payment (Parlay X 3).

For links to the specification, see:

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-02/29199-02-740.zip

Table 7-1 Statement of Compliance, Parlay X 3.0 Payment

Method

Compliant(Yes | No)

Interface: AmountCharging

ChargeAmount

Y

RefundAmount

Y

ChargeSplitAmount

Y

Interface: VolumeCharging

ChargeVolume

Y

GetAmount

Y

RefundVolume

Y

chargeSplitVolume

Y

Interface: ReserveAmountCharging

ReserveAmount

Y

ReserveAdditionalAmount

Y

ChargeReservation

Y

ReleaseReservation

Y

Interface: ReserveVolumeCharging

GetAmount

Y

ReserveVolume

Y

ReserveAdditionalVolume

Y

ChargeReservation

Y

ReleaseReservation

Y

Diameter for Parlay X 3.0 Payment

The Diameter plug-in for Parlay X 3.0 Payment acts as a charging application towards a Diameter server.

Standards Compliance

The plug-in complies with RFC3588 and RFC4006.

The specifications are at http://www.ietf.org/rfc/rfc3588.txt and http://www.ietf.org/rfc/rfc4006.txt.

Table 7-2 Statement of Compliance, Diameter for Parlay X 3.0 Payment

Diameter AVP

Compliant(Yes/No)

Comment

Subscription-Id

Y

OCSG-Charge-Description

N/A

Oracle Communications Services Gatekeeper custom.

Currency-Code

Y

Unit-Value.Exponent

Y

Unit-Value.Value-Digits

Y

Service-Context-Id

Y

OSCG-Reference-Code

N/A

Oracle Communications Services Gatekeeper custom.

Session-Id

Y

Origin-Realm

Y

Origin-Host

Y

Destination-Realm

Y

Auth-Application-Id

Y

CC-Request-Type

Y

Requested-Action

Y

CC-Request-Number

Y

User-Name

Y

OCSG-Application-Id

N/A

Oracle Communications Services Gatekeeper custom.

Result-Code

Y

Service-Identifier

Y

Called-Party-Address

N/A

Oracle Communications Services Gatekeeper custom; identifies the application or subscriber receiving the service

Calling-Party-Address

N/A

Oracle Communications Services Gatekeeper custom; identifies the application or subscriber invoking the service

8 Parlay X 2.1 Terminal Status

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 2.1 Terminal Status communication service and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Terminal Status

- SS7/MAP Terminal Status

Parlay X 2.1 Terminal Status

This section describes the standards compliance for the Terminal Status communication services for Parlay X 2.1 Terminal Status:

The Parlay X 2.1 interface complies to 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).

See the ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip for a links to this specification.

Table 8-1 Statement of Compliance, Parlay X 2.1 Terminal Status

Method

Compliant(Yes | No)

Comment

Interface: TerminalStatus

N/A

N/A

getStatus()

Y

N/A

getStatusForGroup()

Y

N/A

Interface: TerminalStatusNotificationManager

N/A

N/A

startNotification()

Y

N/A

endNotification()

Y

N/A

getStatus()

Y

N/A

Interface: TerminalStatusNotification

N/A

N/A

statusNotification()

Y

N/A

statusError()

Y

N/A

statusEnd()

Y

N/A

SS7/MAP Terminal Status

The Terminal Status/MAP plug-in for Terminal Status acts as an MAP application client for an SS7 network. Triggered notifications are supported, and you can specify whether the Terminal Status/Map plug-in performs the status change probe itself (“push”) or directs the network to perform it (“pull”).

The plug-in connects to the Tieto Enator SS7 stack.

Standards Compliance

3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification; (Release 4), 3GPP TS 29.002 v4.18.0 (2007-09).

See the MAP specification at this 3GPP website: http://www.3gpp.org/ftp/Specs/html-info/29002.htm.

Table 8-2 Statement of Compliance, MAP 3.1 for Parlay X 2.1 Terminal Status

Message

Compliant(Yes | No)

Comment

anyTimeInterrogationReq()

Y

N/A

anyTimeInterrogationRes()

Y

N/A

anyTimeInterrogation()

Y

N/A

anyTimeModificationReq()

Y

N/A

anyTimeModificationRes()

Y

N/A

anyTimeModification()

Y

N/A

NoteMMEvent

Y

N/A

9 Parlay X 2.1 Terminal Location

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Terminal Location communication services and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Terminal Location

- MLP 3.0/3.2 for Parlay X 2.1 Terminal Location

Parlay X 2.1 Terminal Location

This section describes the standards compliance for the communication services for Parlay X 2.1 Terminal Location:

The Parlay X 2.1 interface complies to 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).

See

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip

for links to the specification.

Table 9-1 Statement of Compliance, Parlay X 2.1 Terminal Location

Method

Compliant(Yes | No)

Comment

Interface: TerminalLocation

GetLocation

Y

GetTerminalDistance

Y

GetLocationForGroup

Y

Interface: TerminalLocationNotificationManager

StartGeographicalNotification

Y

StartPeriodicNotification

Y

EndNotification

Y

Interface: TerminalLocationNotification

LocationNotification

Y

LocationError

Y

LocationEnd

Y

MLP 3.0/3.2 for Parlay X 2.1 Terminal Location

The MPL 3.0/3.2 plug-in for Parlay X 2.1 Terminal Location acts as an LCS/MLS Client towards a location server using the MLP interface. It is possible to use either version 3.0 or version 3.2 of MLP. When using MLP 3.2, triggered notifications are supported. It is configurable on plug-in instance level wether tit shall operate in Standard Location or Emergency Location Immediate mode.

The plug-in connects to the Location Server using HTTP. The plug-in always acts as one single LCS/MLS Client towards the location server.

Standards Compliance

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.2.0).

A link to the MLP 3.0 specification is found on http://www.openmobilealliance.org/tech/affiliates/lif/lifindex.html

A link to the MLP 3.2 specification is found on http://www.openmobilealliance.org

Table 9-2 Statement of Compliance, MLP 3.0/3.2 for Parlay X 2.1 Terminal Location

Message

Compliant(Yes | No)

Comment

Standard Location Immediate Service

Standard Location Immediate Request

Y

Standard Location Immediate Answer

Y

Emergency Location Immediate Service

Emergency Location Immediate Request

Y

Emergency Location Immediate Answer

Y

Triggered Location Reporting Service

Triggered Location Reporting Request

Y

Only when the plug-in operates in MLP 3.2 mode.

Triggered Location Reporting Answer

Y

Only when the plug-in operates in MLP 3.2 mode.

Triggered Location Report

Y

Only when the plug-in operates in MLP 3.2 mode.

Triggered Location Reporting Stop Request

Y

Only when the plug-in operates in MLP 3.2 mode.

Triggered Location Reporting Stop Answer

Y

Only when the plug-in operates in MLP 3.2 mode.

The attribute subclient is populated with the ID of the application instance group that the request originated from.

10 Parlay X 2.1 Audio Call

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 2.1 Audio Call communication service and how the interfaces and protocols comply to standards.

Parlay X 2.1 Audio Call Statement of Compliance

This section describes the standards compliance for the Audio Call communication services for Parlay X 2.1 Audio Call:

The Parlay X 2.1 interface complies with 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).

See the ETSI OSA Parlay X web site at: ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip for a links to this specification.

Table 10-1 Statement of Compliance, Parlay X 2.1 Audio Call

Method

Compliant

Comment

Interface: Audio Call

N/A

N/A

PlayAudioMessage()

Yes

N/A

GetMessageStatus()

Yes

N/A

EndMessage()

Yes

N/A

SIP for Parlay X 2.1 Audio Call

The SIP plug-in for Parlay X 2.1 Audio Call is an integration plug-in that utilizes the Oracle WebLogic SIP Server to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in WebLogic SIP Server. The SIP Servlet uses the SIP API provided by the WebLogic SIP server, which in its turn converts the API calls to SIP messages.

Standards Compliance

The SIP servlet uses the WebLogic SIP server, which conforms to RFC 3261.

The RFC is found at

http://www.ietf.org/rfc/rfc3261.txt

Table 10-2 Statement of Compliance, SIP for Parlay X 2.1 Audio Call

Message/Response

Compliant

Comment

REGISTER

-

Not used in the context.

INVITE

Yes

ACK

Yes

CANCEL

Yes

BYE

Yes

OPTIONS

-

Not used in the context.

INFO

-

Not used in the context.

100 Trying

Yes

180 Ringing

Yes

181 Call Is Being Forwarded

-

Not used in the context.

182 Queued

-

Not used in the context.

183 Session Progress

-

Not used in the context.

200 OK

Yes

300 Multiple Choices

Yes

Not used in the context.

301 Moved Permanently

Yes

Not used in the context.

302 Moved Temporarily

Yes

Not used in the context.

305 Use Proxy

Yes

Not used in the context.

380 Alternative Service

Yes

Not used in the context.

400 Bad Request

Yes

Treated as an error.

401 Unauthorized

Yes

Treated as an error.

402 Payment Required

Yes

Treated as an error.

403 Forbidden

Yes

Treated as an error.

404 Not Found

Yes

Treated as an error.

405 Method Not Allowed

Yes

Treated as an error.

406 Not Acceptable

Yes

Treated as an error.

407 Proxy Authentication Required

Yes

Treated as an error.

408 Request Timeout

Yes

Treated as an error.

410 Gone

Yes

Treated as an error.

413 Request Entity Too Large

Yes

Treated as an error.

414 Request-URI Too Long

Yes

Treated as an error.

415 Unsupported Media Type

Yes

Treated as an error.

416 Unsupported URI Scheme

Yes

Treated as an error.

420 Bad Extension

Yes

Treated as an error.

421 Extension Required

Yes

Treated as an error.

423 Interval Too Brief

Yes

Treated as an error.

480 Temporarily Unavailable

Yes

Treated as an error.

481 Call/Transaction Does Not Exist

Yes

Treated as an error.

482 Loop Detected

Yes

Treated as an error.

483 Too Many Hops

Yes

Treated as an error.

484 Address Incomplete

Yes

Treated as an error.

485 Ambiguous

Yes

Treated as an error.

486 Busy Here

Yes

Treated as an error.

487 Request Terminated

Yes

Treated as an error.

488 Not Acceptable Here

Yes

Treated as an error.

491 Request Pending

Yes

Treated as an error.

493 Undecipherable

Yes

Treated as an error.

500 Server Internal Error

Yes

Treated as an error.

501 Not Implemented

Yes

Treated as an error.

502 Bad Gateway

Yes

Treated as an error.

503 Service Unavailable

Yes

Treated as an error.

504 Server Time-out

Yes

Treated as an error.

505 Version Not Supported

Yes

Treated as an error.

513 Message Too Large

Yes

Treated as an error.

600 Busy Everywhere

Yes

Treated as an error.

603 Decline

Yes

Treated as an error.

604 Does Not Exist Anywhere

Yes

Treated as an error.

606 Not Acceptable

Yes

Treated as an error.

11 Parlay X 3.0 Audio Call

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 3.0 communication service and how its interfaces and protocols comply to standards.

- Parlay X 3.0 Audio Call

- Parlay 3.3 User Interaction and MultiParty Call Control for Parlay X 3.0 Audio Call

Parlay X 3.0 Audio Call

This section describes the standards compliance for the communication services for Parlay X 3.0 Audio Call:

The Parlay X 3.0 interface complies with 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).

See

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zipml

for links to the specification.

Table 11-1 Statement of Compliance, Parlay X 3.0 Audio Call

Method

Compliant(Yes | No)

Comment

Interface: PlayMedia

PlayTextMessage

N

PlayAudioMessage

Y

PlayVoiceXmlMessage

N

PlayVideoMessage

N

GetMessageStatus

Y

EndMessage

Y

Interface: CaptureMedia

StartPlayAndCollectInteraction

Y

StartPlayAndRecordInteraction

N

StopMediaInteraction

Y

Interface: MultiMedia

AddMediaForParticipants

N

DeleteMediaForParticipants

N

GetMediaForParticipant

N

GetMediaForCall

N

Parlay 3.3 User Interaction and MultiParty Call Control for Parlay X 3.0 Audio Call

The Parlay 3.3 User Interaction and MultiParty Call Control plug-in for Parlay X 3.0 Audio Call acts as a OSA/Parlay application towards an OSA/Parlay Gateway. It uses the OSA/Parlay Framework to get hold of the Call User Interaction and MultiParty Call Control SCSs. This is done via the OSA Access Service, see "Parlay 3.3 Framework for plug-ins of Parlay type"

The call session is not created by this plug-in but uses call sessions established by the following plug-ins:

- Parlay 3.3 MultiParty Call Control plug-in for Parlay X 3.0 Third Party Call

- Parlay 3.3 MultiParty Call Control for Parlay X 3.0 Call Notification

Standards Compliance

The plug-in complies to 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).

It also complies to 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).

Table 11-2 Statement of Compliance, Parlay 3.3 User Interaction and MultiParty Call Control for Parlay X 3.0 Audio Call

Method

Compliant(Yes | No)

Comment

Interface: IpMultiPartyCallControlManager

createCall

N

Not used in the context

createNotification

N

Not used in the context

destroyNotification

N

Not used in the context

changeNotification

N

Not used in the context

getNotification

N

Not used in the context

setCallLoadControl

N

Not used in the context

Interface: IpMultiPartyCall

getCallLegs

N

Not used in the context

createCallLeg

N

Not used in the context

createAndRouteCallLegReq

N

Not used in the context

release

N

Not used in the context

deassignCall

N

Not used in the context

getInfoReq

N

Not used in the context

setChargePlan

N

Not used in the context

setAdviceOfCharge

N

Not used in the context

superviseReq

N

Not used in the context

Interface: IpCallLeg

routeReq

N

Not used in the context

eventReportReq

N

Not used in the context

release

N

Not used in the context

getInfoReq

N

Not used in the context

getCall

N

Not used in the context

attachMediaReq

N

Not used in the context

detachMediaReq

N

Not used in the context

getCurrentDestinationAddress

N

Not used in the context

getLastRedirectedAddress

N

Not used in the context

continueProcessing

N

Not used in the context

setChargePlan

N

Not used in the context

setAdviceOfCharge

N

Not used in the context

superviseReq

N

Not used in the context

deassign

N

Not used in the context

Interface: IpAppMultiPartyCallControlManager

reportNotification

N

Not used in the context

callAborted

N

Not used in the context

managerInterrupted

N

Not used in the context

managerResumed

N

Not used in the context

callOverloadEncountered

N

Not used in the context

callOverloadCeased

N

Not used in the context

Interface: IpAppMultiPartyCall

getInfoRes

N

Not used in the context

getInfoErr

N

Not used in the context

superviseRes

N

Not used in the context

superviseErr

N

Not used in the context

callEnded

N

Not used in the context

createAndRouteCallLegErr

N

Not used in the context

Interface: IpAppCallLeg

eventReportRes

N

Not used in the context

eventReportErr

N

Not used in the context

attachMediaRes

Y

attachMediaErr

Y

detachMediaRes

Y

detachMediaErr

Y

getInfoRes

N

Not used in the context

getInfoErr

N

Not used in the context

routeErr

N

Not used in the context

superviseRes

N

Not used in the context

superviseErr

N

Not used in the context

callLegEnded

N

Not used in the context

Table 11-3 Statement of Compliance, Parlay 3.3 User Interaction for Parlay X 2.1 Audio Call

Method

Compliant(Yes | No)

Comment

Interface: IpUIManager

createUI

N

Not used in the context

createUICall

Y

createNotification

N

Not used in the context

destroyNotification

N

Not used in the context

changeNotification

N

Not used in the context

getNotification

N

Not used in the context

Interface: IpAppUIManager

userInteractionAborted

N

Not used in the context

reportNotification

N

Not used in the context

userInteractionNotificationInterrupted

N

Not used in the context

userInteractionNotificationContinued

N

Not used in the context

reportEventNotification

N

Not used in the context

Interface: IpUI

sendInfoReq

Y

sendInfoAndCollectReq

Y

release

Y

Interface: IpAppUI

sendInfoRes

Y

sendInfoErr

Y

sendInfoAndCollectRes

Y

sendInfoAndCollectErr

Y

userInteractionFaultDetected

N

Not used in the context

Interface: IpUICall

recordMessageReq

N

Not used in the context

deleteMessageReq

N

Not used in the context

abortActionReq

N

Not used in the context

Interface: IpAppUICall

recordMessageRes

N

Not used in the context

recordMessageErr

N

Not used in the context

deleteMessageRes

N

Not used in the context

deleteMessageErr

N

Not used in the context

abortActionRes

Y

abortActionErr

Y

12 Parlay X 2.1 Presence

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 2.1 Presence communication services and how the interfaces and protocols comply to standards.

- Parlay X 2.1 Presence

- SIP for Parlay X 2.1 Presence

Parlay X 2.1 Presence

This section describes the standards compliance for the communication services for Parlay X 2.1 Presence:

The Parlay X 2.1 interface complies with ETSI ES 202 391-14 V1.2.1 (2006-12), Open Service Access (OSA); Parlay X Web Services; Part 14: Presence (Parlay X 2).

See ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-04/29199-04-650.zip for links to the specification.

Table 12-1 Statement of Compliance, Parlay X 2.1 Presence

Method

Compliant(Yes | No)

Comment

Interface: PresenceConsumer

subscribePresence

Y

getUserPresence

Y

startPresenceNotification

Y

endPresenceNotification

Y

Interface: PresenceNotification

statusChanged

Y

statusEnd

Y

notifySubscription

Y

subscriptionEnded

Y

Interface: PresenceSupplier

publish

N

getOpenSubscriptions

N

updateSubscriptionAuthorization

N

getMyWatchers

N

getSubscribedAttributes

N

blockSubscription

N

SIP for Parlay X 2.1 Presence

The SIP plug-in for Parlay X 2.1 Presence is an integration plug-in that utilizes Oracle Converged Application Server (OCCAS) to connect to a SIP/IMS network. The plug-in connects to a SIP servlet executing in OCCAS. The controller utilizes the SIP API provided by OCCAS to create and send SUBSCRIBE requests. The SIP server converts the API calls to SIP and actually sends the requests out to the network. The SIP servlet on the other hand acts as a listener for responses to the SUBSCRIB requests that were sent from the controller. In this case the SIP server receives the SIP messages an converts them to API calls invoked on the SIP servlet.

Standards Compliance

The SIP servlet uses the WebLogic SIP server, which conforms to RFC 3261.

The specification is found on http://www.ietf.org/rfc/rfc3261.txt

Additionally the following IETF specification are used by WebLogic SIP Server

Session Initiation Protocol (IP) - specific Event Notification

The specification is found on http://www.apps.ietf.org/rfc/rfc3265.html

A Presence Event package for the Session Initiation Protocol (SIP)

The specification is found on http://www.apps.ietf.org/rfc/rfc3856.html

PRID: Rich Presence Extensions to Presence Information Data Format (PIDF)

The specification is found on http://www.apps.ietf.org/rfc/rfc4480.html

Table 12-2 Statement of Compliance, SIP for Parlay X 2.1 Presence

Message/Response

Compliant(Yes/No)

Comment

ACK

-

Not used in the context.

REGISTER

-

Not used in the context.

INVITE

-

CANCEL

-

BYE

-

OPTIONS

-

Not used in the context.

SUBSCRIBE

Y

NOTIFY

Y

100 Trying

-

Not used in the context.

180 Ringing

-

Not used in the context.

181 Call Is Being Forwarded

-

Not used in the context.

182 Queued

-

Not used in the context.

183 Session Progress

-

Not used in the context.

200 OK

Y

202 Accepted

Y

300 Multiple Choices

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

301 Moved Permanently

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

302 Moved Temporarily

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

305 Use Proxy

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

380 Alternative Service

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

400 Bad Request

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

401 Unauthorized

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

402 Payment Required

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

403 Forbidden

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

404 Not Found

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

405 Method Not Allowed

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

406 Not Acceptable

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

407 Proxy Authentication Required

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

408 Request Timeout

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

410 Gone

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

413 Request Entity Too Large

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

414 Request-URI Too Long

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

415 Unsupported Media Type

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

416 Unsupported URI Scheme

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

420 Bad Extension

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

421 Extension Required

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

423 Interval Too Brief

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

480 Temporarily Unavailable

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

481 Call/Transaction Does Not Exist

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

482 Loop Detected

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

483 Too Many Hops

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

484 Address Incomplete

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

485 Ambiguous

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

486 Busy Here

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

487 Request Terminated

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

488 Not Acceptable Here

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

489 Bad Event

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

491 Request Pending

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

493 Undecipherable

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

500 Server Internal Error

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

501 Not Implemented

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

502 Bad Gateway

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

503 Service Unavailable

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

504 Server Time-out

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

505 Version Not Supported

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

513 Message Too Large

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

600 Busy Everywhere

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

603 Decline

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

604 Does Not Exist Anywhere

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

606 Not Acceptable

Y

From a Parlay X 2.1 Presence standpoint the subscription will not be established.

13 Parlay X 3.0 Device Capabilities and Configuration

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 3.0 communication service and how the interfaces and protocols comply to standards.

- Parlay X 3.0 Device Capabilities and Configuration

- LDAP for Device Capabilities and Configuration

Parlay X 3.0 Device Capabilities and Configuration

This section describes the standards compliance for the communication services for Parlay X 3.0 Device Capabilities and Configuration (Device Capabilities):

The Parlay X 3.0 interface complies to Draft ETSI ES 202 504-18 v.0.0.1 (2007-06), Open Service Access (OSA); Parlay X Web Services; Part 18: Device Capabilities and Configuration (Parlay X 3).

See

ftp://ftp.3gpp.org/Specs/archive/29_series/29.199-02/29199-02-740.zip

for links to the specification.

Table 13-1 Statement of Compliance, Parlay X 3.0 Device Capabilities and Configuration

Method

Compliant

Comments

Interface: DeviceCapabilities

-

getCapabilities

Yes

-

getDeviceId

Yes

-

Interface: DeviceCapabilitiesNotificationManager

startNotification

No

-

endNotification

No

-

Interface: DeviceCapabilitiesNotification

deviceNotification

No

-

deviceError

No

-

deviceEnd

No

-

Interface: DeviceConfiguration

pushConfiguration

No

-

getConfigurationList

No

-

getConfigurationHistory

No

-

LDAP for Device Capabilities and Configuration

The LDAP plug-in for Device Capabilities acts as an LDAP client towards a directory service. The plug-in connects to the directory service using LDAP.

The plug-in instance has a pool of connections.

Standards Compliance

The plug-in complies to LDAP v3, RFC 4510.

The specification is found on the LDAP web site at:

http://tools.ietf.org/html/rfc4510

Table 13-2 Statement of Compliance, LDAP for Device Capabilities and Configuration

Operation

Compliant

Comment

Bind

Yes

Unbind

Yes

Search

Yes

Modify

No

Not used in the context.

Add

No

Not used in the context.

Delete

No

Not used in the context.

Modify

No

Not used in the context.

Compare

No

Not used in the context.

Abandon

No

Not used in the context.

Extended

No

Not used in the context.

StartTLS

No

Not used in the context.

14 Parlay X 3.0 Application Subscription Management

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X 3.0 Application Subscription Management communication service and how the interfaces and protocols comply to standards.

Application Subscription Management Statement of Compliance

This section describes the standards compliance for the Application Subscription Management communication service.

The Application Subscription Management communication service complies with the OMS GSSM V1.0 specification as follows:

- High-Level Requirements - no operations supported.

- Service Subscription Operations - compliant. See Table 14-1 for a list of the supported operations.

- Subscription Validation Operations - compliant. See Table 14-2 for a list of the supported operations.

- Provisioning Related Operations - no operations supported.

- Security - no operations supported.

- Authentication - no operations supported.

- Authorization - no operations supported.

- Integrity - no operations supported.

- Confidentiality - no operations supported.

- Charging - no operations supported.

- Administration and Configuration - no operations supported.

- Privacy - no operations supported.

See

http://technical.openmobilealliance.org/Technical/release_program/gssm_v1_0.aspx

for links to the specification.

Supported Operations

The General Service Subscription Management communication service supports these parts of the OMA GSSM V 1.0 specification:

Table 14-1 lists the specification parts of the General Service Subscription Management specification that Services Gatekeeper supports.

Table 14-1 General Service Subscription Management Supported Parts

Feature

Description

SSO-1

The GSSM Enabler SHALL provide the principal with a mechanism to subscribe principals(s) to a service.

SSO-2

The GSSM Enabler SHALL provide the authorized principal with a mechanism to change the Subscription Profile (e.g., contents, channels, valid term).

SSO-3

The GSSM Enabler SHALL provide the subscriber with the mechanism to suspend/resume the service subscription.

SSO-4

The GSSM Enabler SHALL provide the authorised principal with a mechanism to unsubscribe from a service.

SSO-5

The GSSM Enabler SHALL provide the authorized principal with a mechanism for querying the service subscriptions.

SSO-6

The GSSM Enabler SHALL support the selective retrieval of Subscription Profiles based on the criteria in the Subscription Profile (e.g. subscription creation time, subscriber, user, service, subscription specific parameters).

SSO-7

The GSSM Enabler SHALL be capable of delegating to related resources (such as business support systems, backend systems) using existing interfaces, part of the validation process for the new service subscription requests. Part of such validation processes to be taken by those business support systems, under a new service subscription request, could be:

- Check if the user is not in a black list.

- Check if current pricing plans or product offerings for the user allows for subscribing to this service.

- Check compatibility of requested service with other services the user has already subscribed.

Table 14-2 Supported subscription Validation Operations

Feature

Description

SV-1

The GSSM Enabler SHALL be capable of validating a subscription based on the following criteria:

- the service being requested

- the principal for whom the service is being requested

- the time when the service is being requested

- the frequency with which the service is requested, e.g. how many times per day

- preferred service delivery method(s), e.g. MMS, WAP

SV-2

The GSSM Enabler SHALL be capable of delegating to related Resources using existing interfaces, part of the evaluation process for the validation of the subscription.

SV-3

The GSSM Enabler SHALL be capable of querying and retrieving from related Resources using existing interfaces, the necessary information to validate a subscription.

SV-4

The GSSM Enabler SHALL be capable of providing in the Subscription Validation result the information necessary for the operation and execution of the service provided to the user.

SV-5

Upon completion of the Subscription Validation, the GSSM Enabler SHALL be capable of delegating to related Resources part of the Service Subscription Provisioning process required for the delivery of the service to the user in accordance with the Subscription Profile.

SV-6

The GSSM Enabler SHALL support selecting and requesting either subscription validation or retrieval of the Subscription Profile data, for example in order for the requestor to perform itself the validation operations.

SV-7

The GSSM Enabler SHALL be capable of providing necessary group information (e.g. ID of group members) upon response to a validation request for a group subscription.

15 Extended Web Services WAP Push

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Extended Web Services WAP Push communication services and how the interfaces and protocols comply to standards.

- Extended Web Services WAP Push

- WAP Push for Extended Web Services WAP Push

Extended Web Services WAP Push

This section describes the standards compliance for the communication services for Extended Web Services WAP Push:

The Extended Web Services interface is an interface defined by Oracle, but it is based on the patterns present in the Parlay X 2.1 interfaces.

The payload of a WAP Push message shall adhere to:

- WAP Service Indication Specification, as specified in Service Indication Version 31-July-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.

See http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.html for links to the specifications.

WAP Push for Extended Web Services WAP Push

The WAP Push plug-in for Extended Web Services WAP Push acts as an Push Initiator towards a Push Proxy Gateway using the PAP interface. The plug-in connects to the Push proxy Gateway using HTTP.

The plug-in always acts as one single Push Initiator towards the Location Server.

Standards Compliance

The plug-in complies to Push Access Protocol, WAP Forum™, WAP-247-PAP-20010429-a.

The specification is found on http://www.openmobilealliance.org

Table 15-1 Statement of Compliance, WAP Push for Extended Web Services WAP Push

Operation

Compliant(Yes | No)

Comment

push-message

Y

push-response

Y

cancel-message

N

cancel-response

N

resultnotification-message

Y

resultnotification-response

Y

statusquery-message

N

statusquery-response

N

ccq-message

N

ccq-response

N

badmessage-response

Y

16 Extended Web Services Subscriber Profile

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Extended Web Services Subscriber Profile communication services and how the interfaces and protocols comply to standards.

- Extended Web Services Subscriber Profile

- LDAP for Extended Web Services Subscriber Profile

Extended Web Services Subscriber Profile

This section describes the standards compliance for the communication services for Extended Web Services Subscriber Profile:

The Extended Web Services interface is an interface defined by Oracle, but it is based on a suggestion for a Parlay X standard for Subscriber Profile.

LDAP for Extended Web Services Subscriber Profile

The LDAP plug-in for Extended Web Services Subscriber Profile acts as an LDAP client towards a directory service. The plug-in connects to the directory service using LDAP.

The plug-in instance has a pool of connections.

Standards Compliance

The plug-in complies to LDAP v3, RFC 4510.

The specification is found on http://tools.ietf.org/html/rfc4510.

Table 16-1 Statement of Compliance, LDAP for Extended Web Services Subscriber Profile

Operation

Compliant(Yes | No)

Comment

Bind

Y

Unbind

Y

Search

Y

Modify

N

Not used in the context.

Add

N

Not used in the context.

Delete

N

Not used in the context.

Modify

N

Not used in the context.

Compare

N

Not used in the context.

Abandon

N

Not used in the context.

Extended

N

Not used in the context.

StartTLS

N

Not used in the context.

17 Native MM7

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Native MM7 communication services and how the interfaces and protocols comply to standards.

- Native MM7

- Native MM7 Service Facade Standards Compliance

- Native MM7 Service Enabler Standards Compliance

Native MM7

This section describes the standards compliance for the communication service for Native MM7.

Native MM7 Service Facade Standards Compliance

The MM7 Service Facade acts as an MMS Relay/Server. It is used by MMS VAS applications.

The Service Facade complies to 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 XSD schemes defined with name space http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2.

A link to the specification is found on http://www.3gpp.org/ftp/Specs/html-info/23140.htm

It supports authentication using HTTP Basic Authentication according to HTTP Authentication: Basic and Digest Access Authentication, IETF; RFC 2617.

Table 17-1 Statement of Compliance Native MM7Service Facade

Operation

Compliant(Yes | No)

Comment

MMS VAS application originated operations:

MM7_submit.REQ

Y

MM7_cancel.REQ

N

MM7_delivery_report.RES

Y

MM7_deliver.RES

Y

MM7_replace.REQ

N

MM7_read_reply.RES

Y

MM7_VASP_error.RES

N

MM7 Service Facade originated operations:

MM7_submit.RES

Y

MM7_cancel.REQ

N

MM7_delivery_report.REQ

Y

MM7_deliver.REQ

Y

MM7_replace.RES

N

MM7_read_reply.REQ

Y

MM7_RS_error.RES

N

Native MM7 Service Enabler Standards Compliance

The Native MM7 Service Enabler acts as an MMS VAS application.

The Service Enabler complies to 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 XSD schemes defined with name space: http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0

It supports the 7-1-0 XSD, adapted to support delivery notifications and 7-1-2 XSD.

A link to the specification is found on http://www.3gpp.org/ftp/Specs/html-info/23140.htm

It supports authentication using HTTP Basic Authentication according to HTTP Authentication: Basic and Digest Access Authentication, IETF; RFC 2617.

Table 17-2 Statement of Compliance Native MM7Service Enabler

Operation

Compliant(Yes | No)

Comment

MM7 Service Enabler originated operations:

MM7_submit.REQ

Y

MM7_cancel.REQ

N

MM7_delivery_report.RES

Y

MM7_deliver.RES

Y

MM7_replace.REQ

N

MM7_read_reply.RES

Y

MM7_VASP_error.RES

Y

MMSC originated operations:

MM7_submit.RES

Y

MM7_cancel.RES

Y

MM7_delivery_report.REQ

Y

MM7_deliver.REQ

Y

MM7_replace.RES

N

MM7_read_reply.REQ

Y

MM7_RS_error.RES

Y

18 Native SMPP

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Native SMPP communication services and how the interfaces and protocols comply to standards.

- Native SMPP

- Native SMPP Service Facade Standards Compliance

- Native SMPP Service Enabler Standards Compliance

Native SMPP

This section describes the standards compliance for the communication service for Native SMPP.

Native SMPP Service Facade Standards Compliance

The Native SMPP Service Facade acts as an SMPP SCMC. It is used by SMPP applications.

The Service Facade Complies to Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2.

The specification is found on http://www.smsforum.net/.

Table 18-1 Statement of Compliance, SMPP Service Facade

Operation

Compliant(Yes | No)

Comment

bind_transmitter

Y

bind_transmitter_resp

Y

bind_receiver

Y

bind_receiver_resp

Y

bind_transceiver

Y

bind_transceiver_resp

Y

outbind

N

unbind

Y

unbind_resp

Y

generic_nack

Y

submit_sm

Y

submit_sm_resp

Y

submit_sm_multi

Y

submit_sm_multi_resp

Y

deliver_sm

Y

deliver_sm_resp

Y

data_sm

N

data_sm_resp

N

query_sm

Y

query_sm_resp

Y

cancel_sm

Y

cancel_sm_resp

Y

replace_sm

Y

replace_sm_resp

Y

enquire_link

Y

enquire_link_resp

Y

alert_notification

N

Native SMPP Service Enabler Standards Compliance

The Native SMPP Service Enabler acts as an External Short Message Entity (ESME) towards an SMPP SCMC.

The Service Enabler Complies to Short Message Peer to Peer, Protocol Specification v3.4, Document Version:- 12-Oct-1999 Issue 1.2.

The specification is found on http://www.smsforum.net/.

Table 18-2 Statement of Compliance, SMPP Service Enabler

Operation

Compliant(Yes | No)

Comment

bind_transmitter

Y

bind_transmitter_resp

Y

bind_receiver

Y

bind_receiver_resp

Y

bind_transceiver

Y

bind_transceiver_resp

Y

outbind

N

unbind

Y

unbind_resp

Y

generic_nack

Y

submit_sm

Y

submit_sm_resp

Y

submit_sm_multi

Y

submit_sm_multi_resp

Y

deliver_sm

Y

deliver_sm_resp

Y

data_sm

N

data_sm_resp

N

query_sm

Y

query_sm_resp

Y

cancel_sm

Y

cancel_sm_resp

Y

replace_sm

Y

replace_sm_resp

Y

enquire_link

Y

enquire_link_resp

Y

alert_notification

N

Native SMPP Version 5.1 Standards Compliance

The native SMPP communication service supports the following features, which are defined in the Short Message Peer-to-Peer Protocol Specification, Version 5.1. Services Gatekeeper supports these features as tunneled parameters.

Table 18-3 Statement of Compliance for Version 5.1 Features

Parameter

Section in Specification

Comments

billing_identification

4.8.4.3

ussd_service_operation

4.8.4.64

Version 5.1 added support to deliver_sm for bidrectional USSD.

interface_version

4.7.13

The Native SMPP Service accepts 5.1 as well as 3.4 as the interface version number.

19 Native UCP

The following chapter describes Oracle Communications Services Gatekeeper (Services Gatekeeper) Native UCP Communication Service and how the interfaces and protocols comply to standards.

Native UCP

The Native UCP communication service is compliant with the following versions of the Short Message Service Centre EMI-UCP Interface specification:

- UCP 4.0

- UCP 4.6

- UCP 5.0

Table 19-1 describes Native UCP's compliance with the Short Message Service Centre EMI-UCP specification.

Table 19-1 Statement of Compliance, Native UCP

Operation

Compliant

Comment

51 Submit_short_message

Yes

52 Deliver_short_message

Yes

53 Deliver_notification

Yes

54 Modify_message

No

55 Inquiry_message

No

56 Delete_message

No

57 Response_inquiry_message

No

58 Response_delete_message

No

31 SMT Alert

Yes

Supports heartbeats

60 Session managment

Yes

Supports authentication

61 List management

No

20 Parlay 3.3 Framework for plug-ins of Parlay type

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay 3.3 Framework for Parlay Plug-ins communication services and how the interfaces and protocols comply to standards.

- Parlay 3.3 Framework for Parlay plug-ins

Parlay 3.3 Framework for Parlay plug-ins

Connecting to the telecommunications network via an OSA/Parlay SCS, involves an Authentication, Service Discovery, and Load Management phase towards an OSA/Parlay Framework.

The OSA/Parlay plug-ins does not communicate directly with the OSA/Parlay Framework, instead they use Oracle Communications Services Gatekeeper's Parlay Access service.

- Standards Compliance

Standards Compliance

The OSA Access service complies to ETSI ES 201 915-3 V1.4.1 (2003-07), Open Service Access (OSA); Application Programming Interface (API); Part 3: Framework.

The specification is found at

http://www.etsi.org/deliver/etsi_es/201900_201999/20191503/01.04.01_50/es_20191503v010401m.pdf

Table 20-1 Statement of Compliance, Parlay 3.3 Framework

Method

Compliant(Yes| No)

Comment

Interface: IpInitial

initiateAuthentication

Y

Supported authentication methods:

- P_AUTHENTICATION

Interface: IpAuthentication

requestAccess

Y

Interface: IpAPILevelAuthentication

selectEncryptionMethod

Y

Supported encryption methods:

- RSA 512

- RSA 1024

- none

authenticate

Y

abortAuthentication

Y

authenticationSucceeded

Y

Interface: IpClientAPILevelAuthentication

authenticate

Y

abortAuthentication

Y

authenticationSucceeded

Y

Interface: IpAccess

obtainInterface

Y

obtainInterfaceWithCallback

Y

endAccess

Y

listInterfaces

Y

releaseInterface

Y

Interface: IpClientAccess

terminateAccess

Y

Interface: IpServiceDiscovery

listServiceTypes

N

describeServiceType

N

discoverService

Y

Configurable list of service properties along with service types

listSubscribedServices

N

Interface: IpServiceAgreementManagement

signServiceAgreement

Y

terminateServiceAgreement

Y

selectService

Y

initiateSignServiceAgreement

Y

Interface: IpAppServiceAgreementManagement

signServiceAgreement

Y

terminateServiceAgreement

Y

Interface: IpFaultManager

activityTestReq

N

appActivityTestRes

N

svcUnavailableInd

N

genFaultStatsRecordReq

N

appActivityTestErr

N

appUnavailableInd

N

genFaultStatsRecordRes

N

genFaultStatsRecordErr

N

Interface: IpAppFaultManager

activityTestRes

N

appActivityTestReq

N

fwFaultReportInd

N

fwFaultRecoveryInd

N

svcUnavailableInd

N

genFaultStatsRecordRes

N

fwUnavailableInd

N

activityTestErr

N

genFaultStatsRecordErr

N

appUnavailableInd

N

genFaultStatsRecordReq

N

Interface: IpHeartBeatMgmt

enableHeartBeat

N

disableHeartBeat

N

changeInterval

N

Interface: IpAppHeartBeatMgmt

enableAppHeartBeat

N

disableAppHeartBeat

N

changeInterval

N

Interface: IpHeartBeat

pulse

N

Interface: IpAppHeartBeat

pulse

N

Interface: IpLoadManager

reportLoad

N

queryLoadReq

N

queryAppLoadRes

N

queryAppLoadErr

N

createLoadLevelNotification

Y

destroyLoadLevelNotification

N

resumeNotification

N

suspendNotification

N

Interface: IpAppLoadManager

queryAppLoadReq

N

queryLoadRes

Y

queryLoadErr

N

loadLevelNotification

Y

resumeNotification

N

suspendNotification

N

createLoadLevelNotification

N

destroyLoadLevelNotification

N

21 Parlay X Web Services Address List Management

The following chapter describes the standard Oracle Communications Services Gatekeeper (Services Gatekeeper) Parlay X Web Services Application Subscription Management communication service and how the interfaces and protocols comply to standards.

Parlay X Web Services Address List Management

This section describes the standards compliance for the Parlay X Web Services Part 13: Address List Management (3GPP TS 29.199-13 version 7.0.2 Release 7) communication service.

Standards Compliance

The plug-in complies with 3GPP TS 29.199-13 version 7.0.2 Release 7)

The specification is available here:

http://www.etsi.org/deliver/etsi_ts/129100_129199/12919913/07.00.02_60/ts_12919913v070002p.pdf

Table 21-1, Table 21-2, and Table 21-3 list the supported operations for the specification interfaces.

Table 21-1 Address List Management GroupManagement Interface Operations

Compliant (Yes | No)

Operation

Yes

createGroup

Yes

deleteGroup

Yes

queryGroups

Yes

setAccess

Yes

queryAccess

Table 21-2 Address List Management Group Interface Operations

Compliant (Yes | No)

Operation

Yes

addMember

Yes

deleteMember

Yes

deleteMembers

Yes

queryMembers

Yes

addGroupAttribute

Yes

deleteGroupAttribute

Yes

queryGroupAttributes

Yes

addGroupMemberAttribute

Yes

deleteGroupMemberAttribute

Yes

queryGroupMemberAttributes

Table 21-3 Address List Management Member Interface Operations

Compliant (Yes | No)

Operation

Yes

addMemberAttribute

Yes

queryMemberAttributes

Yes

deleteMemberAttribute

22 QoS Diameter Policy and Charging Control Over Diameter Rx

The following chapter describes the supported Oracle Communications Services Gatekeeper (Services Gatekeeper) Diameter Rx communication service and how the interfaces and protocols comply to standards.

QoS Diameter Policy and Charging Control Over Rx

This section describes the standards compliance for the Policy and Charging Control over Rx reference point 3GPP TS 29.214 V.9.9.0 (2011-12) (Release 9) communication service.

Standards Compliance

The specification is available here:

http://www.etsi.org/deliver/etsi_ts/129200_129299/129214/09.04.01_60/ts_129214v090401p.pdf

Table 22-1 lists the Rx commands supported by Policy Controller.

Table 22-1 Supported Rx Commands

Command

Status

Link to List of Supported AVPs

AA-Request (AAR)

Supported

Supported AA-Request AVPs

AA-Answer (AAA)

Supported

Supported AA-Answer AVPs

Re-Auth-Request (RAR)

Supported

Supported Re-Auth-Request AVPs

Re-Auth-Answer (RAA)

Supported

Supported Re-Auth-Answer (RAA) AVPs

Session-Termination-Request (STR)

Supported

Supported Session-Termination-Request AVPs

Session-Termination-Answer (STA)

Supported

Supported STA Application AVPs

Abort-Session-Request (ASR)

Supported

Supported Abort-Session-Request AVPs

Abort-Session-Answer (ASA)

Supported

Supported Abort-Session-Answer AVPs

Supported Rx AA-Request (AAR) AVPs

Table 22-2 lists the supported Diameter Rx AA-Request AVPs.

Table 22-2 Supported AA-Request AVPs

AVP

Status

Auth-Application-Id

Supported

Origin-Host

Supported

Origin-Realm

Supported

Destination-Realm

Supported

Destination-Host

Supported

AF-Application-Identifier

Supported

---- Media-Component-Description

Supported

---- ---- Media-Component-Number

Supported

---- ---- Media-Sub-Component

Supported

---- ---- AF-Application-Identifier

Supported

---- ---- Media-Type

Supported

---- ---- Max-Requested-Bandwidth-UL

Supported

---- ---- Max-Requested-Bandwidth-DL

Supported

---- ---- Flow-Status

Supported

---- ---- Reservation-Priority

Supported.

Reused from ETSI TS 183 017 V2.3.1 (2008-9)

---- ---- RS-Bandwidth

Supported

---- ---- RR-Bandwidth

Supported

---- ---- Codec-Data

Supported

---- Media-Component-Number

Supported

---- Media-Sub-Component

Supported

---- ---- Flow-Number

Supported

---- ---- Flow-Description

Supported

---- ---- Flow-Status

Supported

---- ---- Flow-Usage

Supported

---- ---- Max-Requested-Bandwidth-UL

Supported

---- ---- Max-Requested-Bandwidth-DL

Supported

---- ---- AF-Signalling-Protocol

Supported

---- AF-Application-Identifier

Supported

---- Media-Type

Supported

---- Max-Requested-Bandwidth-UL

Supported

---- Max-Requested-Bandwidth-DL

Supported

---- Flow-Status

Supported

---- Reservation-Priority

Supported

---- RS-Bandwidth

Supported

Reused from ETSI TS 183 017 V2.3.1 (2008-9)

---- RR-Bandwidth

Supported

---- Codec-Data

Supported

Service-Info-Status

Supported

AF-Charging-Identifier

Supported

SIP-Forking-Indication

Supported

Specific-Action

Supported

Subscription-Id

Supported

Reused from RFC 4006.

---- Subscription-Id-Type

Supported

Reused from RFC 4006.

---- Subscription-Id-Data

Supported

Reused from RFC 4006

Supported-Features

Supported

Reused from 3GPP TS 29.229

---- Vendor-Id

Supported

Reused from 3GPP TS 29.229

---- Feature-List-ID

Supported

Reused from 3GPP TS 29.229

---- Feature-List

Supported

Reused from 3GPP TS 29.229

Reservation-Priority

Supported

Reused from ETSI TS 183 017 V2.3.1 (2008-9)

Framed-IP-Address

Supported

Reused from RFC 4005

Framed-IPv6-Prefix

Supported

Reused from RFC 4005

Called-Station-Id

Supported

Reused from RFC 4005

Service-URN

Supported

Origin-State-Id

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy-State

Supported

Route-Record

Supported

Supported Rx AA-Answer (AAA) AVPs

Table 22-3 lists the supported Diameter Rx AA-Answer AVPs.

Table 22-3 Supported AA-Answer AVPs

AVP

Status

Auth-Application-Id

Supported

Origin-Host

Supported

Origin-Realm

Supported

Result-Code

Supported

Experiment-Result

Supported

Access-Network-Charging-Identifier

Supported

---- Access-Network-Charging-Identifier-Value

Supported

---- Access-Network-Charging-Identifier-Value

Supported

---- Flows

Supported

---- ---- Media-Component-Number

Supported

---- ---- Flow-Number

Supported

---- ---- Final-Unit-Action

Supported

Reused from RFC 4006

Access-Network-Charging-Address

Supported

Acceptable-Service-Info

Supported

---- Media-Component-Description

Supported

---- ---- Media-Component-Number

Supported

---- ---- Media-Sub-Component

Supported

---- ---- Flow-Number

Supported

---- ---- Flow-Description

Supported

---- ---- Flow-Status

Supported

---- ---- Flow-Usage

Supported

---- ---- Max-Requested-Bandwidth-UL

Supported

---- ---- Max-Requested-Bandwidth-DL

Supported

---- ---- AF-Signalling-Protocol

Supported

---- ---- AF-Application-Identifier

Supported

---- ---- Media-Type

Supported

---- ---- Max-Requested-Bandwidth-UL

Supported

---- ---- Max-Requested-Bandwidth-DL

Supported

---- ---- Flow-Status

Supported

---- ---- Reservation-Priority

Supported

Reused from ETSI TS 183 017 V2.3.1 (2008-9)

---- ---- RS-Bandwidth

Supported

---- ---- RR-Bandwidth

Supported

---- ---- Codec-Data

Supported

---- Max-Requested-Bandwidth-DL

Supported

---- Max-Requested-Bandwidth-UL

Supported

IP-CAN-Type

Supported

Reused from 3GPP TS 29.212

RAT-Type

Supported

Reused from 3GPP TS 29.212

Supported-Features

Supported

Reused from 3GPP TS 29.229

---- Vendor-Id

Supported

Reused from 3GPP TS 29.229

---- Feature-List-ID

Supported

Reused from 3GPP TS 29.229

---- Feature-List

Supported

Reused from 3GPP TS 29.229

Class

Supported

Error-Message

Supported

Error-Reporting-Host

Supported

Failed-AVP

Supported

---- AVP

Yes

Origin-State-Id

Supported

Redirect-Host

Supported

Redirect-Host-Usage

Supported

Redirect-Max-Cache-Time

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy State

Supported

Supported Rx Re-Auth-Request (RAR) AVPs

Table 22-4 lists the supported Diameter Rx Re-Auth-Request AVPs.

Table 22-4 Supported Re-Auth-Request AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Destination-Realm

Supported

Destination-Host

Supported

Auth-Application-Id

Supported

Specific-Action

Supported

Access-Network-Charging-Identifier

Supported

---- Access-Network-Charging-Identifier-Value

Supported

---- Access-Network-Charging-Identifier-Value

Supported

---- Flows

Supported

---- ---- Media-Component-Number

Supported

---- ---- Flow-Number

Supported

---- ---- Final-Unit-Action

Supported

Reused from RFC 4006

Access-Network-Charging-Address

Supported

Flows

Supported

---- Media-Component-Number

Supported

---- Flow-Number

Supported

---- Final-Unit-Action

Supported

Reused from RFC 4006

Subscription-Id

Supported

Reused from RFC 4006

---- Subscription-Id-Type

Supported

Reused from RFC 4006

---- Subscription-Id-Data

Supported

Reused from RFC 4006

Abort-Cause

Supported

IP-CAN-Type

Supported

Reused from 3GPP TS 29.212

RAT-Type

Supported

Reused from 3GPP TS 29.212

Origin-State-Id

Supported

Class

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy-State

Supported

Route-Record

Supported

Supported Rx Re-Auth-Answer (RAA) AVPs

Table 22-5 lists the supported Diameter Rx Re-Auth-Answer AVPs.

Table 22-5 Supported Re-Auth-Answer (RAA) AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Experimental-Result

Supported

---- Vendor-Id

Supported

---- Experimental-Result-Code

Supported

Media-Component-Description

Supported

---- Media-Component-Number

Supported

---- Media-Sub-Component

Supported

---- AF-Application-Identifier

Supported

---- Media-Type

Supported

---- Max-Requested-Bandwidth-UL

Supported

---- Max-Requested-Bandwidth-DL

Supported

---- Flow-Status

Supported

---- Reservation-Priority

Supported

Reused from ETSI TS 183 017 V2.3.1 (2008-9)

---- RS-Bandwidth

Supported

---- RR-Bandwidth

Supported

---- Codec-Data

Supported

Service-URN

Supported

Origin-State-Id

Supported

Class

Supported

Error-Message

Supported

Error-Reporting-Host

Supported

Redirect-Host

Supported

Redirect-Host-Usage

Supported

Redirect-Max-Cache-Time

Supported

Failed-AVP

Supported

---- AVP

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy-State

Supported

Supported Rx Session-Termination-Request (STR) AVPs

Table 22-6 lists the supported Diameter Rx Session-Termination-Request AVPs.

Table 22-6 Supported Session-Termination-Request AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Destination-Realm

Supported

Auth-Application-Id

Supported

Termination-Cause

Supported

Destination-Host

Supported

Class

Supported

Origin-State-Id

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy-State

Supported

Route-Record

Supported

Supported Rx Session-Termination-Answer (STA) AVPs

Table 22-7 lists the supported Diameter Rx Session-Termination-Answer (STA) AVPs.

Table 22-7 Supported STA Application AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Result-Code

Supported

Error-Message

Supported

Error-Reporting-Host

Supported

Failed-AVP

Supported

Origin-State-Id

Supported

Class

Supported

Redirect-Host

Supported

Redirect-Host-Usage

Supported

Redirect-Max-Cache-Time

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy-State

Supported

Supported Rx Abort-Session-Request (ASR) AVPs

Table 22-8 lists the supported Diameter Rx Abort-Session-Request (ASR) AVPs.

Table 22-8 Supported Abort-Session-Request AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Destination-Realm

Supported

Destination-Host

Supported

Auth-Application-Id

Supported

Abort-Cause

Supported

Origin-State-Id

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy State

Supported

Route-Record

Supported

Supported Rx Abort-Session-Answer (ASA) AVPs

Table 22-9 lists the supported Diameter Rx Abort-Session-Answer (ASA) AVPs.

Table 22-9 Supported Abort-Session-Answer AVPs

AVP

Status

Origin-Host

Supported

Origin-Realm

Supported

Result-Code

Supported

Origin-State-Id

Supported

Error-Message

Supported

Error-Reporting-Host

Supported

Failed-AVP

Supported

Redirect-Host

Supported

Redirect-Host-Usage

Supported

Redirect-Max-Cache-Time

Supported

Proxy-Info

Supported

---- Proxy-Host

Supported

---- Proxy State

Supported

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.