TR 29.998
Open Services Architecture (OSA) Application Programming Interface (API) part 2
V3.2.0 (PDF)
2001/01 81 p.
- Rapporteur:
- Mr. Unmehopa, Musa
full Table of Contents for TR 29.998 Word version: 3.2.0
1 Scope p. 6
The present document investigates how the OSA Interface Class methods can be mapped onto CAMEL Application Part operations and MAP Application Part operations. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative.
The Open Service Architecture (OSA) defines an architecture that enables operator and third party applications to make use of network functionality through an open standardized interface (the OSA Interface). OSA provides the glue between applications and service capabilities provided by the network. In this way applications become independent from the underlying network technology. The applications constitute the top level of the Open Service Architecture (OSA). This level is connected to the Service Capability Servers (SCSs) via the OSA interface. The SCSs map the OSA interface onto the underlying telecommunications specific protocols (e.g. MAP, CAP, etc.) and are therefore hiding the network complexity from the applications.
The specific Service Capability Server under consideration in this technical report is the CSE. In this case, the OSA API provides the operator or third party applications access to the CAMEL Application Part protocol operations, via the OSA Interface Class methods. On the gsmSCF, the OSA Interface Class methods need to be mapped, or translated, onto the relevant CAP and/or MAP operations. Only the non-framework Service Capability Features will be taken into account for the mapping. This document is not exhaustive in covering all the mappings that can be expected. It provides several examples, but it should be noted that several other possibilities exist. In particular, only general cases of normal operations are covered and exception scenarios are not within the scope of the document.
In addition to the configuration of SCS and CSE, this technical report contains some recommendations for a configuration consisting of SCS and HLR. On the HLR, the OSA Interface Class methods need to be mapped, or translated, onto the relevant MAP protocol operations. The mappings contained in this technical report for the SCS/HLR case are not intended to be exhaustive.
The OSA API to CAP and MAP mapping is part of Release99.
2 References p. 6
3 Definitions and abbreviations p. 7
3.1 Definitions p. 7
3.2 Abbreviations p. 7
4 Virtual Home Environment and Open Service Architecture p. 8
4.1 The Interface p. 8
5 General Parameter Mapping Issues p. 9
5.1 API Parameters that do not require a mapping p. 9
5.2 Protocol Operation Parameters that do not require a mapping p. 10
6 Generic Call Control Service CAMEL Call Flows p. 10
6.1 Call Manager p. 10
6.1.1 enableCallNotification p. 10
6.1.2 disableCallNotification p. 12
6.1.3 changeCallNotification p. 12
6.1.4 p. 13
6.1.5 getCriteria p. 13
6.1.6 p. 14
6.1.7 callNotificationInterrupted p. 14
6.1.8 callNotificationContinued p. 15
6.1.9 callAborted p. 15
6.1.10 callEventNotify p. 16
6.2 Call p. 18
6.2.1 routeReq p. 18
6.2.2 routeRes p. 23
6.2.3 routeErr p. 24
6.2.4 release p. 25
6.2.5 deassignCall p. 26
6.2.6 getCallInfoReq p. 27
6.2.7 getCallInfoRes p. 27
6.2.8 getCallInfoErr p. 28
6.2.9 superviseCallReq p. 29
6.2.10 superviseCallRes p. 30
6.2.11 superviseCallErr p. 31
6.2.12 setAdviceOfCharge p. 32
6.2.13 setCallChargePlan p. 33
6.2.14 callFaultDetected p. 34
6.2.14a callEnded p. 35
7 Generic Message Transfer Service CAMEL Call Flows p. 36
7.1 User Interaction p. 36
7.1.1 createUI p. 36
7.1.2 createUICall p. 37
7.1.3 enableUINotification p. 37
7.1.4 disableUINotification p. 38
7.1.5 userInteractionEventNotify p. 38
7.1.6 userInteractionAborted p. 39
7.1.7 userInteractionNotificationInterrupted p. 40
7.1.8 userInteractionNotificationContinued p. 40
7.1.9 userInteractionFaultDetected p. 41
7.1.10 sendInfoReq p. 42
7.1.11 sendInfoRes p. 45
7.1.12 sendInfoErr p. 47
7.1.13 sendInfoAndCollectReq p. 48
7.1.14 sendInfoAndCollectRes p. 51
7.1.15 sendInfoAndCollectErr p. 52
7.1.16 release p. 53
7.1.17 abortActionReq p. 54
7.1.18 abortActionRes p. 55
7.1.19 abortActionErr p. 55
8 Generic Message Transfer Service WAP Call Flows p. 56
8.1 User Interaction p. 56
9 User Status Service CAMEL Flows p. 57
9.1 triggeredStatusReportingStartReq p. 57
9.2 triggeredStatusReportingStop p. 58
9.3 statusReportReq p. 59
9.4 statusReportRes p. 59
9.5 triggeredStatusReport p. 60
10 User Status Service core-MAP Flows p. 61
10.1 statusReportReq p. 61
10.2 statusReportRes p. 62
11 Network User Location Call Flows p. 63
11.1 locationReportReq p. 63
11.2 locationReportRes p. 64
11.3 locationReportErr p. 65
11.4 periodicLocationReportingStartReq p. 65
11.5 periodicLocationReportingStop p. 66
11.6 periodicLocationReport p. 67
11.7 periodicLocationReportErr p. 68
11.8 triggeredLocationReportingStartReq p. 69
11.9 triggeredLocationReportingStop p. 70
11.10 triggeredLocationReport p. 70
11.11 triggeredLocationReportErr p. 72
12 Terminal Capabilities WAP Call Flows p. 72
13 Data Session Control Service CAMEL Call Flows p. 73
13.1 Data Session Manager p. 73
13.1.1 enableDataSessionNotification p. 73
13.1.2 disableDataSessionNotification p. 74
13.1.3 dataSessionEventNotify p. 75
13.1.4 dataSessionAborted p. 76
13.1.5 dataSessionNotificationInterrupted p. 76
13.1.6 dataSessionNotificationContinued p. 77
13.2 Data Session p. 77
13.2.1 ConnectReq p. 77
13.2.2 connectRes p. 78
13.2.3 connectErr p. 79
13.2.4 release p. 80
13.2.5 superviseDataSessionReq p. 81
13.2.6 superviseDataSessionRes p. 81
13.2.7 superviseDataSessionErr p. 82
13.2.8 dataSessionFaultDetected p. 83
13.2.9 setAdviceOfCharge p. 84
13.2.10 setDataSessionChargePlan p. 85
14 Detailed Parameter Mappings p. 86
14.1 TpCallMonitorMode p. 86
14.2 TpCallReportType p. 86
14.3 TpCallEventName p. 86
14.4 TpCallAdditionalReportInfo p. 87
$ Change history p. 88
