1、 ETSI TR 102 397-2-2 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 2: Mapping to Multi-party Call ControlETSI ETSI TR 102 397-2-2 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021-02-02-OSA Keyword
2、s API, OSA, 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 pr
3、esent document 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 cas
4、e of dispute, 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 an
5、d other ETSI 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 authoriz
6、ed by written 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 Member
7、s. TIPHONTMand 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-2 V1.1.1 (2005-08) 3 Contents Intellectual Proper
8、ty Rights4 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 De
9、tailed Mapping Information.9 6.1 Operations 9 6.1.1 makeCall.9 6.1.1.1 Mapping to IpMultiPartyCallControlManager.createCall9 6.1.1.2 Mapping to IpMultiPartyCall.createAndRouteCallLegReq .10 6.1.1.3 Mapping to IpMultiPartyCall.getInfoReq.10 6.1.1.4 Mapping to IpMultiPartyCall.setChargePlan10 6.1.2 ge
10、tCallInformation11 6.1.2.1 Mapping from IpAppCallLeg.eventReportRes11 6.1.2.2 Mapping from IpAppMultiPartyCall.createAndRouteCallLegErr13 6.1.2.3 Mapping from IpAppMultiPartyCall.getInfoRes.13 6.1.2.4 Mapping from IpAppMultiPartyCall.getInfoErr.13 6.1.2.5 Mapping from IpAppCallLeg.callLegEnded.14 6.
11、1.2.6 Mapping from IpAppMultiPartyCall.callEnded .14 6.1.2.7 Mapping from IpAppMultiPartyCallControlManager.callAborted.14 6.1.3 endCall14 6.1.4 cancelCall .15 6.2 Exceptions 15 7 Additional Notes 15 History 16 ETSI ETSI TR 102 397-2-2 V1.1.1 (2005-08) 4 Intellectual Property Rights IPRs essential o
12、r potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential 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 Ess
13、ential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are 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
14、. 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 Web 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 Telecommun
15、ications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 2, sub-part 2, 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“; Par
16、t 2: “Third Party Call Mapping“; Sub-part 1: “Mapping to Generic Call Control“; Sub-part 2: “Mapping to Multi-Party Call Control“; Part 3: “Call Notification Mapping“; Part 4: “Short Messaging Mapping“; Part 5: “Multimedia Messaging Mapping“; Part 6: “Payment Mapping“; Part 7: “Account Management Ma
17、pping“; Part 8: “Terminal Status Mapping“; Part 9: “Terminal Location Mapping“; Part 10: “Call Handling Mapping“; Part 11: “Audio 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
18、 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 document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. ETSI ETSI TR 102 397-2-2 V1.1.1 (2005-08) 5 1 Scope The Parlay X Web Services
19、provide powerful yet simple, highly abstracted, imaginative, telecommunications functions that application developers and the IT community can both quickly comprehend and use to generate new, innovative applications. The Open Service Access (OSA) specifications define an architecture that enables ap
20、plication developers to make use of network functionality through an open standardized interface, i.e. the Parlay/OSA APIs. The present document specifies the mapping of the Parlay X Third Party Call Web Service to the Parlay/OSA Multi-Party Call Control Service Capability Feature (SCF). 2 Reference
21、s For the purposes of this Technical (TR), the following references apply: 1 ETSI TR 121 905: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905)“. 2 W3C Recommendation (2 May 2001): “XML Schem
22、a Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 3 ETSI TR 102 397-1: “Open Service 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
23、: Address List Management“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms 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 descri
24、ption The Third Party Call capability can be implemented with the Parlay/OSA Multi-Party Call Control SCF. It is applicable to ETSI OSA 1.x/2.x/3.x, Parlay/OSA 3.x/4.x/5.x and 3GPP Releases 4 to 6. ETSI ETSI TR 102 397-2-2 V1.1.1 (2005-08)6 5 Sequence diagrams 5.1 Completed Call Released in Network
25、Appl 3rdParty Call IpApp CallLeg:A IpApp MPCC Manager Ip MPCC Manager Ip CallLeg:B IpApp MPCall IpApp CallLeg:B Ip MPCall Ip CallLeg:A makeCallRequest “new” createCall() “new” makeCallResponse createAndRouteCallLegReq() eventReportRes() “forward event” getInfoReq() OPTIONAL: setChargePlan() createAn
26、dRouteCallLegReq() eventReportRes () “forward event” callEnded() “forward event” getInfoRes() “forward event” getCallInfoRequest getCallInfoResponse getCallInfoRequest getCallInfoResponse getCallInfoRequest getCallInfoResponse “new” “new” “new” continueProcessing() Figure 1 ETSI ETSI TR 102 397-2-2
27、V1.1.1 (2005-08)7 5.2 Completed Call Released by Application Appl 3rdParty Call IpApp CallLeg:A IpApp MPCC Manager Ip MPCC Manager Ip CallLeg:B IpApp MPCall IpApp CallLeg:B Ip MPCall Ip CallLeg:A makeCallRequest “new” createCall() “new” makeCallResponse createAndRouteCallLegReq() eventReportRes() “f
28、orward event” getInfoReq() OPTIONAL: setChargePlan() createAndRouteCallLegReq() eventReportRes () “forward event” getInfoRes() “forward event” getCallInfoRequest getCallInfoResponse endCallRequest endCallResponse getCallInfoRequest getCallInfoResponse “new” “new” “new” release() continueProcessing()
29、 Figure 2 ETSI ETSI TR 102 397-2-2 V1.1.1 (2005-08)8 5.3 Call Attempt Abandoned by Application Appl 3rdParty Call IpApp CallLeg:A IpApp MPCC Manager Ip MPCC Manager IpApp MPCall Ip MPCall Ip CallLeg:A makeCallRequest “new” createCall() “new” makeCallResponse createAndRouteCallLegReq() cancelCallRequ
30、est cancelCallResponse “new” “new” release() Figure 3 ETSI ETSI TR 102 397-2-2 V1.1.1 (2005-08) 9 6 Detailed Mapping Information 6.1 Operations 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 c
31、lients point of view. It is mapped to the following Parlay/OSA methods: IpMultiPartyCallControlManager.createCall IpMultiPartyCall.createAndRouteCallLegReq IpMultiPartyCall.getInfoReq IpMultiPartyCall.setChargePlan 6.1.1.1 Mapping to IpMultiPartyCallControlManager.createCall The IpMultiPartyCallCont
32、rolManager.createCall method is invoked with the following parameters: Name Type Comment appCall IpAppMultiPartyCallRef Reference to callback (internal) The result from IpMultiPartyCallControlManager.createCall is of type TpMultiPartyCallIdentifier and is used internally to correlate the callbacks.
33、Specifically it is correlated with the value of the CallIdentifier part returned to the application in the makeCallResponse message Parlay exceptions thrown by IpMultiPartyCallControlManager.createCall are mapped to Parlay X exceptions as defined in clause 6.2. ETSI ETSI TR 102 397-2-2 V1.1.1 (2005-
34、08) 106.1.1.2 Mapping to IpMultiPartyCall.createAndRouteCallLegReq The IpMultiPartyCall.createAndRouteCallLegReq method is invoked with the following parameters: Name Type Comment callSessionID TpSessionID Not mapped. The value provide in the result from IpMultiPartyCallControlManager.createCall eve
35、ntsRequested TpCallEventRequestSet 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_EVENT_ANSWER even
36、t 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
37、 in 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 (
38、e.g. a service provider number), the parameter may be populated with an address obtained from a pre-defined service level agreement. appInfo TpCallAppInfoSet Not mapped appLegInterface IpAppCallLegSet Not mapped. Specifies a reference to the application interface that implements the callback interfa
39、ce for the new call leg. Requested events will be reported by the eventReportRes() operation on this interface. The result from IpMultiPartyCall.createAndRouteCallLegReq is of type TpCallLegIdentifier and is used internally to correlate the callbacks. It is not mapped to the Parlay X interface. Parl
40、ay exceptions thrown by IpMultiPartyCall.createAndRouteCallLegReq are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.1.3 Mapping to IpMultiPartyCall.getInfoReq The IpMultiPartyCall.getInfoReq method is invoked with the following parameters: Name Type Comment callSessionID TpSessionID No
41、t mapped. The value provide in the result from IpMultiPartyCallControlManager.createCall callInfoRequested TpCallInfoType Not mapped. Set to a value of 03h to obtain information on relevant call times and release cause. Parlay exceptions thrown by IpMultiPartyCall.getInfoReq are mapped to Parlay X e
42、xceptions as defined in clause 6.2. 6.1.1.4 Mapping to IpMultiPartyCall.setChargePlan The IpMultiPartyCall.setChargePlan method is invoked with the following parameters: Name Type Comment callSessionID TpSessionID Not mapped. The value provide in the result from IpMultiPartyCallControlManager.create
43、Call 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-2 V1.1.1 (2005-08) 11The callChargePlan parameter is constructed as follows: Na
44、me 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 Not mapped AdditionalInfo TpOctetS
45、et 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 Not mapped. PartyToChargeAdditio
46、nalInfo TpCallPartyToChargeAdditionalInfo Not mapped Parlay exceptions thrown by IpMultiPartyCall.setChargePlan are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.2 getCallInformation The sequence diagram in clause 5.1 illustrates the flow for the getCallInformation operation. The getCa
47、llInformation operation is synchronous from the Parlay X clients point of view. It is mapped to the following Parlay/OSA methods: IpAppCallLeg.eventReportRes IpAppMultiPartyCall.createAndRouteCallLegErr IpAppMultiPartyCall.getInfoRes IpAppMultiPartyCall.getInfoErr IpAppCallLeg.callLegEnded IpAppMult
48、iPartyCall.callEnded IpAppMultiPartyCallControlManager.callAborted 6.1.2.1 Mapping from IpAppCallLeg.eventReportRes The IpAppCallLeg.eventReportRes callback method is invoked with the following parameters: Name Type Comment callLegSessionID TpSessionID Not mapped. The value provide in the result fro
49、m IpMultiPartyCall.createandRouteCallLegReq eventInfo TpCallEventInfo Specifies 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). NOTE: The CallMonitorMode element of eventInfo is not mapped. If the getCallInformationRequest message is received from the application before the eventReportRes is invoked for either the Calling Party or Called Party, then the CallInformation pa
