ETSI TR 102 397-11-2-2005 Open Service Access (OSA) Mapping of Parlay X Web Services to Parlay OSA APIs Part 11 Audio Call Mapping Sub-part 2 Mapping to Multi-Party Call Control an.pdf

《ETSI TR 102 397-11-2-2005 Open Service Access (OSA) Mapping of Parlay X Web Services to Parlay OSA APIs Part 11 Audio Call Mapping Sub-part 2 Mapping to Multi-Party Call Control an.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 102 397-11-2-2005 Open Service Access (OSA) Mapping of Parlay X Web Services to Parlay OSA APIs Part 11 Audio Call Mapping Sub-part 2 Mapping to Multi-Party Call Control an.pdf（13页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 102 397-11-2 V1.1.1 (2005-08)Technical Report Open Service Access (OSA);Mapping of Parlay X Web Services to Parlay/OSA APIs;Part 11: Audio Call Mapping;Sub-part 2: Mapping to Multi-Party Call Control and User InteractionETSI ETSI TR 102 397-11-2 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021

2、-11-02-OSA Keywords 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 Individua

3、l copies of the present 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 Fo

4、rmat (PDF). In case 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

5、 status of this and 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

6、except as authorized 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 ben

7、efit of its Members. 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-11-2 V1.1.1 (2005-08) 3 Contents

8、Intellectual Property 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 Play message and get message play status .6 5.2 Abandon playing of message7 6 Detailed mapping information8 6.1

9、Operations 8 6.1.1 playTextMessage, playAudioMessage, playVoiceXmlMessage 8 6.1.1.1 Mapping to IpMultiPartyCallControlManager.createCall .8 6.1.1.2 Mapping to IpMultiPartyCall.createAndRouteCallLegReq .8 6.1.1.2.1 Alternative Mapping to IpMultiPartyCall.createCallLeg.9 6.1.1.2.2 Alternative Mapping

10、to IpCallLeg.eventReportReq .9 6.1.1.2.3 Alternative Mapping to IpCallLeg.routeReq10 6.1.1.3 Mapping to IpUIManager.createUICall10 6.1.1.4 Mapping to IpUICall.sendInfoReq .10 6.1.1.5 Mapping of text 11 6.1.1.6 Mapping of voiceXmlUrl .11 6.1.1.7 Mapping of audioURL.11 6.1.2 getMessageStatus12 6.1.3 e

11、ndMessage.12 6.2 Exceptions 12 7 Additional notes .12 History 13 ETSI ETSI TR 102 397-11-2 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 IPRs, if any, is pu

12、blicly 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 available on the ET

13、SI 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 Web server) which are

14、, 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 11, sub-part 2 of a multi-p

15、art 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“; Part 3: “Call Notification Mapping“; Part 4: “Short Messaging Mapping“; Part 5: “Multimedia Messaging Mapping“;

16、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: “Audio Call Mapping“; Sub-part 1: “Mapping to Generic Call Control and User Interaction“; Sub-part 2: “Mapping to Multi-

17、Party Call Control and User Interaction“; 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 ser

18、ies. The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. ETSI ETSI TR 102 397-11-2 V1.1.1 (2005-08) 5 1 Scope The present document specifies the mapping of the Parlay X Audio Call Web Service to the Multi-Party Call Control and User Inter

19、action Service Capability Features (SCFs). The Parlay X Web Services 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 Servi

20、ce 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. 2 References For the purposes of this Technical Report (TR), the following references apply: 1 ETSI TR 121

21、905: “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 Access (OSA); Ma

22、pping 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“. 5 ISO 639: “Codes for the representation of names of languages“. 3 Definitions and abbreviations 3.1 Definitions For

23、 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 description The Audio Call capability can be implemented with Parlay/OSA Multi-Party

24、Call Control and User Interaction. 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-11-2 V1.1.1 (2005-08) 6 5 Sequence diagrams 5.1 Play message and get message play status Audio Call IpApp CallLeg: A MPCC Manager Ip MPCC Manager IpApp M

25、PCall Ip MPCall Ip CallLeg: A IpApp UICall IpUI Manager Ip UICall “new“ createUICall “new“ sendInfoReq sendInfoRes release“destroy“ “notify“ createCall “new“ createAndRouteCallLegReq “new“ eventReportRes, P_CALL_EVENT_ANSWER “notify“ “new“ “new“ playXxxMessageRequest playXxxMessageResponse getMessag

26、eStatusRequest getMessageStatusResponse :PLAYING getMessageStatusRequestgetMessageStatusResponse :PENDINGgetMessageStatusRequestgetMessageStatusResponse :PLAYED Appl IpApp Figure 1 ETSI ETSI TR 102 397-11-2 V1.1.1 (2005-08) 7 5.2 Abandon playing of message Audio Call IpApp CallLeg: A IpApp MPCC Mana

27、ger Ip MPCC Manager IpApp MPCall Ip MPCall Ip CallLeg: AAppl IpApp UICall IpUI Manager Ip UICall release“destroy“ createCall “new“ createAndRouteCallLegReq “new“ eventReportRes, P_CALL_EVENT_ANSWER “notify“ “new“ “new“ playXxxMessageRequest playXxxMessageResponse endMessageRequest endMessageResponse

28、:PENDING Figure 2 ETSI ETSI TR 102 397-11-2 V1.1.1 (2005-08) 8 6 Detailed mapping information 6.1 Operations 6.1.1 playTextMessage, playAudioMessage, playVoiceXmlMessage These operations interact with a call control service to establish a call, where the call is associated with a user interaction se

29、rvice context in which the audio is generated on the call. The sequence diagram in clause 5.1 illustrates the flow for these operations. The playXxxMessage operation is synchronous from the Parlay X clients point of view. It is mapped to the following Parlay/OSA methods: IpMultiPartyCallControlManag

30、er.createCall IpMultiPartyCall.createAndRouteCallLegReq; OR IpMultiPartyCall.createCallLeg, IpCallLeg.eventReportReq,IpCallLeg.routeReq; IpUIManager.createUICall; IpUICall.sendInfoReq. 6.1.1.1 Mapping to IpMultiPartyCallControlManager.createCall The IpMultiPartyCallControlManager.createCall method i

31、s 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. Specifically it is correlated

32、 with the value of the correlator part returned to the application in the playXxxMessageResponse message Parlay exceptions thrown by IpMultiPartyCallControlManager.createCall are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.1.2 Mapping to IpMultiPartyCall.createAndRouteCallLegReq The

33、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. eventsRequested TpCallEventRequestSet Not mapped. Requests call-related e

34、vent reports: i.e. including Answer, Busy, No Answer, Not Reachable. targetAddress TpAddress Specifies the destination leg to which the call should be routed. It is constructed based on the URI provided in the address part of playXxxMessageRequest, mapped as described in TR 102 397-1 3. originatingA

35、ddress TpAddress Not mapped. Specifies the calling party leg. appInfo TpCallAppInfoSet Not mapped. appLegInterface IpAppCallLegRef Not mapped . Specifies a reference to the application interface that implements the callback interface for the new call leg. Requested events will be reported by the eve

36、ntReportRes() operation on this interface. ETSI ETSI TR 102 397-11-2 V1.1.1 (2005-08) 9 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. Parlay exceptions thrown by

37、IpMultiPartyCall.createAndRouteCallLegReq are mapped to Parlay X exceptions as defined in clause 6.2. An alternative to mapping to the IpMultiPartyCall.createAndRouteCallLegReq convenience method is a mapping to the following discrete method invocations: IpMultiPartyCall.createCallLeg; IpCallLeg.eve

38、ntReportReq; IpCallLeg.routeReq. 6.1.1.2.1 Alternative Mapping to IpMultiPartyCall.createCallLeg The IpMultiPartyCall.createCallLeg method is invoked with the following parameters. Name Type Comment callSessionID TpSessionID Not mapped: the result from the invocation of IpMultiPartyCallControlManage

39、r.createCall, as described in clause 6.1.1.1. appCallLeg IpAppCallLegRef Not mapped: Specifies a reference to the application interface that implements the callback interface for the new call leg. Requested events will be reported by the eventReportRes() operation on this interface. The result from

40、IpMultiPartyCall.createCallLeg is of type TpCallLegIdentifier and is not mapped to the Parlay X interface. Parlay exceptions thrown by IpMultiPartyCall.createCallLeg are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.1.2.2 Alternative Mapping to IpCallLeg.eventReportReq The IpCallLeg.ev

41、entReportReq method is invoked with the following parameters. Name Type Comment callLegSessionID TpSessionID Not mapped: the result returned from the invocation of IpMultiPartyCall.createCallLeg, as described in clause 6.1.1.2.1. eventsRequested TpCallEventRequest Set Not mapped. Requests call-relat

42、ed event reports: i.e. including Answer, Busy, No Answer, Not Reachable. Parlay exceptions thrown by IpCallLeg.eventReportReq are mapped to Parlay X exceptions as defined in clause 6.2. ETSI ETSI TR 102 397-11-2 V1.1.1 (2005-08) 106.1.1.2.3 Alternative Mapping to IpCallLeg.routeReq The IpCallLeg.rou

43、teReq method is invoked with the following parameters. Name Type Comment callLegSessionID TpSessionID Not mapped: the result returned from the invocation of IpMultiPartyCall.createCallLeg, as described in clause 6.1.1.2.1. targetAddress TpAddress Specifies the destination leg to which the call shoul

44、d be routed. It is constructed based on the URI provided in the address part of playXxxMessageRequest, mapped as described in TR 102 397-1 3. originatingAddress TpAddress Not mapped. Specifies the calling party leg. appInfo TpCallAppInfoSet Not mapped. connectionProperties TpCallLegConnectionPropert

45、ies Not mapped. Specifies the properties of the connection: i.e. AttachMechanism = P_CALLLEG_ATTACH_IMPLICITLY. Parlay exceptions thrown by IpCallLeg.routeReq are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.1.3 Mapping to IpUIManager.createUICall The IpUIManager.createUICall method i

46、s invoked with the following parameters. Name Type Comment appUI IpAppUICallRef Not mapped: reference to callback (internal) uiTargetObject TpUITargetObject Not mapped. The value provide in the result from IpMultiPartyCallControlManager.createCall The result from IpUIManager.createUICall is of type

47、TpUICallIdentifier and is used internally to correlate the callbacks. Specifically it is correlated with the value of the correlator part returned to the application in the playXxxMessageResponse message Parlay exceptions thrown by IpUIManager.createUICall are mapped to Parlay X exceptions as define

48、d in clause 6.2. 6.1.1.4 Mapping to IpUICall.sendInfoReq The IpUICall.sendInfoReq method is invoked with the following parameters. Name Type Comment userInteraction SessionID TpSessionID Not mapped: reference to callback (internal). info TpUIInfo variableInfo TpUIVariableInfo Set For The mapping fro

49、m the text part is described in clause 6.1.1.5 The mapping from the voiceXmlUrl part is described in clause 6.1.1.6 The mapping from the audioURL part is described in clause 6.1.1.7 Some mapping support for the optional charging part: i.e. it could be mapped to a VariablePartPrice element(s) of the variableInfo parameter. language TpLanguage The language part is mapped to the language parameter;both part and parameter conform to ISO 639 5. repeatIndicator TpInt32 Not mapped. response Requested TpUIResponse Request Not ma