1、 ETSI TR 102 397-2-1 V1.1.1 (2005-08)Technical Report Open Service Access (OSA);Mapping of Parlay X Web Services to Parlay/OSA APIs;Part 2: Third Party Call Mapping;Sub-part 1: Mapping to generic controlETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021-02-01-OSA Keywords API, OS
2、A, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present doc
3、ument can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of disp
4、ute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other E
5、TSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by wri
6、tten permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2005. The Parlay Group 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHON
7、TMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08) 3 Contents Intellectual Property Rights
8、4 Foreword.4 1 Scope 5 2 References 5 3 Definitions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations .5 4 Mapping description.5 5 Sequence diagrams.6 5.1 Completed Call Released in Network 6 5.2 Completed Call Released by Application.7 5.3 Call Attempt Abandoned by Application .8 6 Detailed Ma
9、pping Information.9 6.1 Operations 9 6.1.1 makeCall.9 6.1.1.1 Mapping to IpCallControlManager.createCall.9 6.1.1.2 Mapping to IpCall.routeReq .10 6.1.1.3 Mapping to IpCall.getCallInfoReq.10 6.1.1.4 Mapping to IpCall.setCallChargePlan10 6.1.2 getCallInformation11 6.1.2.1 Mapping from IpAppCall.routeR
10、es11 6.1.2.2 Mapping from IpAppCall.routeErr12 6.1.2.3 Mapping from IpAppCall.getCallInfoRes13 6.1.2.4 Mapping from IpAppCall.getCallInfoErr.13 6.1.2.5 Mapping from IpAppCall.callFaultDetected13 6.1.2.6 Mapping from IpAppCall.callEnded.14 6.1.2.7 Mapping from IpAppCallControlManager.callAborted14 6.
11、1.3 endCall14 6.1.4 cancelCall .15 6.2 Exceptions 15 7 Additional Notes 15 History 16 ETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential
12、 IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are
13、 available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI W
14、eb server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 2, sub-
15、part 1, of a multi-part deliverable covering Open Service Access (OSA); Mapping of Parlay X Web Services to Parlay/OSA APIs, as identified below: Part 1: “Common Mapping“; Part 2: “Third Party Call Mapping“; Sub-part 1: “Mapping to Generic Call Control“; Sub-part 2: “Mapping to Multi-Party Call Cont
16、rol“; Part 3: “Call Notification Mapping“; Part 4: “Short Messaging Mapping“; Part 5: “Multimedia Messaging Mapping“; Part 6: “Payment Mapping“; Part 7: “Account Management Mapping“; Part 8: “Terminal Status Mapping“; Part 9: “Terminal Location Mapping“; Part 10: “Call Handling Mapping“; Part 11: “A
17、udio Call Mapping“; Part 12: “Multimedia Conference Mapping“; Part 14: “Presence Mapping“; NOTE: Part 13 has not been provided as there is currently no defined mapping between ES 202 391-13 4 and the Parlay/OSA APIs. If a mapping is developed, it will become part 13 of this series. The present docum
18、ent has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. ETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08) 5 1 Scope The Parlay X Web Services provide powerful yet simple, highly abstracted, imaginative, telecommunications functions that application developers and the
19、 IT community can both quickly comprehend and use to generate new, innovative applications. The Open Service Access (OSA) specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the Parlay/OSA APIs. T
20、he present document specifies the mapping of the Parlay X Third Party Call Web Service to the Parlay/OSA Generic Call Control Service Capability Feature (SCF). 2 References For the purposes of this Technical (TR), the following references apply: 1 ETSI TR 121 905: “Digital cellular telecommunication
21、s system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905)“. 2 W3C Recommendation (2 May 2001): “XML Schema - Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 3 ETSI TR 102 397-1: “Open Service
22、 Access (OSA); Mapping of Parlay X Web Services to Parlay/OSA APIs; Part 1: Common Mapping“. 4 ETSI ES 202 391-13: “Open Service Access (OSA); Parlay X Web Services; Part 13: Address List Management“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms
23、 and definitions given in TR 102 397-1 3 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 102 397-1 3 apply. 4 Mapping description The Third Party Call capability can be implemented with the Parlay/OSA Generic Call Control SCF. It is applicable to ETSI
24、 OSA 1.x/2.x/3.x, Parlay/OSA 3.x/4.x/5.x and 3GPP Releases 4/5/6.ETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08)6 5 Sequence diagrams 5.1 Completed Call Released in Network Application ThirdParty Call IpAppCall Control Manager IpAppCall IpCall Control Manager IpCall makeCallRequest “new” createCall() “new
25、” makeCallResponse routeReq() routeRes() “forward event” getCallInfoReq() OPTIONAL: setCallChargePlan() routeReq() routeRes() “forward event” callEnded() “forward event” getCallInfoRes() “forward event” getCallInfoRequest getCallInfoResponse getCallInfoRequest getCallInfoResponse ge tCallInfoRequest
26、 getCallInfoResponse Figure 1 ETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08)7 5.2 Completed Call Released by Application Application ThirdParty Call IpAppCall Control Manager IpAppCall IpCall Control Manager IpCall makeCallRequest “new” createCall() “new” makeCallResponse routeReq() routeRes() “forward e
27、vent” getCallInfoReq() OPTIONAL: setCallChargePlan() routeReq() routeRes() “forward event” release() getCallInfoRes() “forward event” endCallRequest endCallResponse getCallInfoRequest getCallInfoResponse Figure 2 ETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08)8 5.3 Call Attempt Abandoned by Application Ap
28、plication ThirdParty Call IpAppCall Control Manager IpAppCall IpCall Control Manager IpCall makeCallRequest “new” createCall() “new” makeCallResponse routeReq() release() cancelCallRequest cancelCallResponse Figure 3 ETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08) 9 6 Detailed Mapping Information 6.1 Oper
29、ations 6.1.1 makeCall The sequence diagram in clause 5.1 illustrates the flow for the makeCall operation. The makeCall operation is synchronous from the Parlay X clients point of view. It is mapped to the following Parlay/OSA methods: IpCallControlManager.createCall IpCall.routeReq IpCall.getCallInf
30、oReq IpCall.setCallChargePlan 6.1.1.1 Mapping to IpCallControlManager.createCall The IpCallControlManager.createCall method is invoked with the following parameters: Name Type Comment appCall IpAppCallRef Reference to callback (internal) The result from IpCallControlManager.createCall is of type TpC
31、allIdentifier and is used internally to correlate the callbacks. Specifically it is correlated with the value of the CallIdentifier part returned to the application in the makeCallResponse message Parlay exceptions thrown by IpCallControlManager.createCall are mapped to Parlay X exceptions as define
32、d in clause 6.2. ETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08) 106.1.1.2 Mapping to IpCall.routeReq The IpCall.routeReq method is invoked with the following parameters: Name Type Comment callSessionID TpSessionID Not mapped. The value provide in the result from IpCallControlManager.createCall responseRe
33、quested TpCallReportRequest Set Not mapped. Requests call-related event reports: i.e. including Answer, Busy, No Answer, Not Reachable. The MonitorMode element of each requested event report should have a value of P_CALL_MONITOR_MODE_NOTIFY, with the sole exception of the P_CALL_REPORT_ANSWER event
34、report on the calling party leg, which should have a value of P_CALL_MONITOR_MODE_INTERRUPT targetAddress TpAddress Specifies the destination leg to which the call should be routed. It is constructed based on the URI provided in the CallingParty or CalledParty part of makeCall, mapped as described i
35、n TR 102 397-1 3 originatingAddress TpAddress Specifies the calling party leg or a third party. To represent the calling party leg, the parameter value is constructed based on the URI provided in the CallingParty part of makeCall, mapped as described in TR 102 397-1 3. To represent a third party (e.
36、g. a service provider number), the parameter may be populated with an address obtained from a pre-defined service level agreement. originalDestination Address TpAddress Not mapped redirectingAddress TpAddress Not mapped appInfo TpCallAppInfoSet No mapped The result from IpCall.routeReq is of type Tp
37、SessionID and is used internally to correlate the callbacks. It is not mapped to the Parlay X interface. Parlay exceptions thrown by IpCall.routeReq are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.1.3 Mapping to IpCall.getCallInfoReq The IpCall.getCallInfoReq method is invoked with t
38、he following parameters: Name Type Comment callSessionID TpSessionID Not mapped. The value provide in the result from IpCallControlManager.createCall callInfoRequested TpCallInfoType Not mapped. Set to a value of 03h to obtain information on relevant call times and release cause. Parlay exceptions t
39、hrown by IpCall.getCallInfoReq are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.1.4 Mapping to IpCall.setCallChargePlan The IpCall.setCallChargePlan method is invoked with the following parameters: Name Type Comment callSessionID TpSessionID Not mapped. The value provide in the result
40、 from IpCallControlManager.createCall callChargePlan TpCallChargePlan Specifies the charge plan to use. It is constructed based on the values provided in the optional Charging part of makeCall. See the following table for details. ETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08) 11The callChargePlan parame
41、ter is constructed as follows: Name Type Comment ChargeOrderType TpCallChargeOrderCategory Not mapped TransparentCharge TpOctetSet Specifies an operator-specific charge plan. It is constructed using the value of the ChargingInformation.code element provided in the Charging part. ChargePlan TpInt32 N
42、ot mapped AdditionalInfo TpOctetSet Descriptive string sent to billing system. It is constructed using the value of the ChargingInformation.description element provided in the Charging part. (May optionally include values of other elements of the Charging part.) PartyToCharge TpCallPartyToChargeType
43、 Not mapped. PartyToChargeAdditionalInfo TpCallPartyToChargeAdditionalInfo Not mapped Parlay exceptions thrown by IpCall.setCallChargePlan are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.2 getCallInformation The sequence diagram in 5.1 illustrates the flow for the getCallInformation
44、operation. The getCallInformation operation is synchronous from the Parlay X clients point of view. It is mapped to the following Parlay/OSA methods: IpAppCall.routeRes IpAppCall.routeErr IpAppCall.getCallInfoRes IpAppCall.getCallInfoErr IpAppCall.callFaultDetected IpAppCall.callEnded IpAppCallContr
45、olManager.callAborted 6.1.2.1 Mapping from IpAppCall.routeRes The IpCall.routeRes callback method is invoked with the following parameters: Name Type Comment callSessionID TpSessionID Not mapped. The value provide in the result from IpCallControlManager.createCall eventReport TpCallReport Specifies
46、the result of the request to route the call to a call party, calling or called, as applicable. See the following discussion for details of its mapping to the getCallInformation operation (see note). callLegSessionID TpSessionID Not mapped. The value provide in the result from IpCall.routeReq NOTE: T
47、he MonitorMode and AdditionalReportInfo elements of eventReport are not mapped. If the getCallInformationRequest message is received from the application before the routeRes is invoked for either the Calling Party or Called Party, then the CallInformation part of the getCallInformationResponse messa
48、ge is constructed as follows: CallStatus has a value of CallInitial StartTime, Duration, TerminationCause are not applicable ETSI ETSI TR 102 397-2-1 V1.1.1 (2005-08) 12If the getCallInformationRequest message is received from the application after the routeRes is invoked for the Calling Party, and
49、the call attempt was unsuccessful, then the CallInformation part of the getCallInformationResponse message is constructed as follows: CallStatus has a value of CallTerminated StartTime, Duration are not applicable TerminationCause has a value mapped from the CallReportType element of the eventReport (TpCallReport) parameter as follows: - if the CallReportType has a value of P_CALL_REPORT_NO_ANSWER, then the TerminationCause has a value of CallingPartyNoAnswer - if the CallReportType has a value
