29.198-023GPPOpen Service Access (OSA) Application Programming Interface (API)Part 2: Common data definitionsRelease 9TS
Defines the Quality of Service (QoS) classes. This could be for a data session or multi media call session, for example.
Specifies the Conversational QoS class, as specified in 3G TS 23.107.
Specifies the Streaming QoS class, as specified in 3G TS 23.107.
Specifies the Interactive QoS class, as specified in 3G TS 23.107.
Specifies the Background QoS class, as specified in 3G TS 23.107.
Note: Because of commonality across multiple interface specifications, this data type is promoted from Data Session Control Data Types to Common Data Types. For backward compatibility reasons, the naming of the data type remains unmodified, and hence continues to refer to Data Session Control.
Annex A (normative):
OMG IDL Description of the Common Data definitions
The OMG IDL representation of the present document is contained in a text file (osa.idl contained in archive 2919802V800IDL.ZIP) which accompanies the present document.
Annex B (informative):
W3C WSDL Description of the Common Data definitions
The W3C WSDL representation of this specification is contained in a zip file 2919802V800WSDL.ZIP, which accompanies the present document.
Annex C (informative):
Java™ API Description of the Common Data definitions
The Java™ API realisation of this 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 specification is provided as Java™ Code, contained in archive 2919802V800J2SE.ZIP that accompanies the present document.
The J2EE™ representation of this specification is provided as Java™ Code, contained in archive 2919802V800J2EE.ZIP that accompanies the present document.
Annex D (normative):
This clause arranges the OSA exceptions as a set of hierarchies that, depending upon the technology realisation, may or may not be utilised to simplify software developers’ code.
If the exception hierarchy is used in a particular realisation, the following lists all the OSA abstract exceptions:
If the exception hierarchy is being used in a particular realisation, a software developer will have the option to catch these abstract exceptions and/or the detailed exceptions which extend them.
The following diagrams show all the OSA detailed exceptions, and how they relate to the abstract exceptions shown previously.
It should be noted that for those OSA methods that raise TpCommonExceptions, the P_RESOURCES_UNAVAILABLE, P_TASK_CANCELLED, P_TASK_REFUSED, P_METHOD_NOT_SUPPORTED, P_INVALID_STATE, P_POLICY_VIOLATION and P_NO_CALLBACK_ADDRESS_SET detailed exceptions should be raised individually in the method signature. The software developer will thus have the option of catching them individually or catching the TpCommonExceptions abstract exception.
Annex E (informative):
Description of the Common Data definitions for 3GPP2 cdma2000 networks
This annex is intended to define the OSA API Stage 3 interface definitions and it provides the complete OSA specifications. 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:
 3GPP2 P.S0001-B: "Wireless IP Network Standard", Version 1.0, September 2000.
 3GPP2 S.R0037-0: "IP Network Architecture Model for cdma2000 Spread Spectrum Systems", Version 2.0, May 14, 2002.
 3GPP2 X.S0013: "All-IP Core Network Multimedia Domain", December 2003.
These requirements are expressed as additions to and/or exclusions from the 3GPP specification.
The information given here is to be used by developers in 3GPP2 cdma2000 network architecture to interpret the 3GPP OSA specifications.