TR 129 998 : 3.2.0

Foreword
1 Scope
2 References
3 Definitions and abbreviations
   3.1 Definitions
   3.2 Abbreviations
4 Virtual Home Environment and Open
   Service Architecture
   4.1 The Interface
5 General Parameter Mapping Issues
   5.1 API Parameters that do not require
       a mapping
   5.2 Protocol Operation Parameters that
       do not require a mapping
6 Generic Call Control Service CAMEL
   Call Flows
   6.1 Call Manager
   6.2 Call
7 Generic Message Transfer Service
   CAMEL Call Flows
   7.1 User Interaction
8 Generic Message Transfer Service WAP
   Call Flows
   8.1 User Interaction
9 User Status Service CAMEL Flows
   9.1 triggeredStatusReportingStartReq
   9.2 triggeredStatusReportingStop
   9.3 statusReportReq
   9.4 statusReportRes
   9.5 triggeredStatusReport
10 User Status Service core-MAP Flows
   10.1 statusReportReq
   10.2 statusReportRes
11 Network User Location Call Flows
   11.1 locationReportReq
   11.2 locationReportRes
   11.3 locationReportErr
   11.4 periodicLocationReportingStartReq
   11.5 periodicLocationReportingStop
   11.6 periodicLocationReport
   11.7 periodicLocationReportErr
   11.8 triggeredLocationReportingStartReq
   11.9 triggeredLocationReportingStop
   11.10 triggeredLocationReport
   11.11 triggeredLocationReportErr
12 Terminal Capabilities WAP Call Flows
   12.1 getTerminalCapabilities
13 Data Session Control Service CAMEL Call
   Flows
   13.1 Data Session Manager
   13.2 Data Session
14 Detailed Parameter Mappings
   14.1 TpCallMonitorMode
   14.2 TpCallReportType
   14.3 TpCallEventName
   14.4 TpCallAdditionalReportInfo
Annex A (informative): Change history

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.