11 Exception Classes

29.198-033GPPOpen Service Access (OSA) Application Programming Interface (API)Part 3: FrameworkTS

The following are the list of exception classes which are used in this interface of the API.

Name

Description

P_ACCESS_DENIED

The client is not currently authenticated with the framework

P_DUPLICATE_PROPERTY_NAME

A duplicate property name has been received

P_ILLEGAL_SERVICE_ID

Illegal Service ID

P_ILLEGAL_SERVICE_TYPE

Illegal Service Type

P_INVALID_ACCESS_TYPE

The framework does not support the type of access interface requested by the client.

P_INVALID_ACTIVITY_TEST_ID

ID does not correspond to a valid activity test request

P_INVALID_ADDITION_TO_SAG

A client application cannot be added to the SAG because this would imply that the client application has two concurrent service profiles at a particular moment in time for a particular service.

P_INVALID_AGREEMENT_TEXT

Invalid agreement text

P_INVALID_ENCRYPTION_CAPABILITY

Invalid encryption capability

P_INVALID_AUTH_TYPE

Invalid type of authentication mechanism

P_INVALID_CLIENT_APP_ID

Invalid Client Application ID

P_INVALID_DOMAIN_ID

Invalid client ID

P_INVALID_ENT_OP_ID

Invalid Enterprise Operator ID

P_INVALID_PROPERTY

The framework does not recognise the property supplied by the client

P_INVALID_SAG_ID

Invalid Subscription Assignment Group ID

P_INVALID_SAG_TO_SERVICE_PROFILE_ASSIGNMENT

A SAG cannot be assigned to the service profile because this would imply that a client application has two concurrent service profiles at a particular moment in time for a particular service.

P_INVALID_SERVICE_CONTRACT_ID

Invalid Service Contract ID

P_INVALID_SERVICE_ID

Invalid service ID

P_INVALID_SERVICE_PROFILE_ID

Invalid service profile ID

P_INVALID_SERVICE_TOKEN

The service token has not been issued, or it has expired.

P_INVALID_SERVICE_TYPE

Invalid Service Type

P_INVALID_SIGNATURE

Invalid digital signature

P_INVALID_SIGNING_ALGORITHM

Invalid signing algorithm

P_MISSING_MANDATORY_PROPERTY

Mandatory Property Missing

P_NO_ACCEPTABLE_ENCRYPTION_CAPABILITY

No encryption mechanism, which is acceptable to the framework, is supported by the client

P_NO_ACCEPTABLE_AUTHENTICATION_MECHANISM

No authentication mechanism, which is acceptable to the framework, is supported by the client

P_NO_ACCEPTABLE_SIGNING_ALGORITHM

No signing algorithm, which is acceptable to the framework, is supported by the client

P_PROPERTY_TYPE_MISMATCH

Property Type Mismatch

P_SERVICE_ACCESS_DENIED

The client application is not allowed to access this service.

P_SERVICE_NOT_ENABLED

The service ID does not correspond to a service that has been enabled

P_SERVICE_TYPE_UNAVAILABLE

The service type is not available according to the Framework.

P_UNKNOWN_SERVICE_ID

Unknown Service ID

P_UNKNOWN_SERVICE_TYPE

Unknown Service Type

Each exception class contains the following structure:

Structure Element Name

Structure Element Type

Structure Element Description

ExtraInformation

TpString

Carries extra information to help identify the source of the exception, e.g. a parameter name

Annex A (normative):
OMG IDL Description of Framework

The OMG IDL representation of this interface specification is contained in text files (fw_data.idl, fw_if_access.idl, fw_if_app.idl, fw_if_service.idl contained in archive 2919803V800IDL.ZIP) which accompany the present document.

Annex B (informative):
W3C WSDL Description of Framework

The W3C WSDL representation of this interface specification is contained in zip file 2919803V800WSDL.ZIP, which accompanies the present document.

Annex C (informative):
Java™ API Description of the Framework

The Java™ API realisation of this interface specification is produced in accordance with the Java™ Realisation rules defined in Part 1 of this specification series. These rules aim to deliver for Java™, a developer API, provided as a realisation, supporting a Java™ API that represents the UML specifications. The rules support the production of both J2SE™ and J2EE™ versions of the API from the common UML specifications.

The J2SE™ representation of this interface specification is provided as Java™, contained in archive 2919803V800J2SE.ZIP that accompanies the present document.

The J2EE™ representation of this interface specification is provided as Java™, contained in archive 2919803V800J2EE.ZIP that accompanies the present document.

Annex D (informative):
Description of the Framework for 3GPP2 cdma2000 networks

This annex is intended to define the OSA API Stage 3 interface definitions and it provides the complete OSA specifications for cdma2000-based systems. It is an extension of OSA API specifications capabilities to enable operation in cdma2000 systems environment. They are in alignment with 3GPP2 Stage 1 requirements and Stage 2 architecture defined in

[1] 3GPP2 P.S0001-B: "Wireless IP Network Standard", Version 1.0, September 2000;

[2] 3GPP2 S.R0037-0: "IP Network Architecture Model for cdma2000 Spread Spectrum Systems", Version 2.0, May 14, 2002;

[3] 3GPP2 X.S0013: "All-IP Core Network Multimedia Domain", December 2003.

These requirements are expressed as additions to and/or exclusions from the 3GPP Release 8 specification. The information given here is to be used by developers in 3GPP2 cdma2000 network architecture to interpret the 3GPP OSA specifications.