Statement of Compliance

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

Parlay 3.3 Framework for plug-ins of Parlay type

The following chapter describes the standard Oracle Communications Services Gatekeeper communication services and how the interfaces and protocols complies to standards.

 


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

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 (Parlay 3).

A link to the specification is found on http://portal.etsi.org/docbox/TISPAN/Open/OSA/Parlay33.html

Table 16-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
 


  Back to Top       Previous  Next