1、 ETSI TR 102 397-12 V1.1.1 (2005-08)Technical Report Open Service Access (OSA);Mapping of Parlay X Web Services to Parlay/OSA APIs;Part 12: Multimedia Conference MappingETSI ETSI TR 102 397-12 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021-12-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles
2、 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 document can be downloaded from: http:/ww
3、w.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 dispute, the reference shall be the printi
4、ng 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 ETSI documents is available at http:/po
5、rtal.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 written permission. The copyright and the
6、 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. TIPHONTMand the TIPHON logo are Trade Marks
7、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-12 V1.1.1 (2005-08) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2 References 5 3
8、 Definitions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations .5 4 Mapping Description5 5 Sequence Diagrams 6 5.1 Create Conference 6 5.2 End Conference 7 5.3 Invite Participant 8 5.4 Invite Participant Alternative Mapping .9 5.5 Disconnect Participant10 5.6 Add Media For Participant .11 5.7 D
9、elete Media For Participant12 6 Detailed Mapping Information.13 6.1 Operations 13 6.1.1 createConference 13 6.1.1.1 Mapping to IpMultiMediaCallControlManager.createCall .13 6.1.1.2 Mapping to IpMultiMediaCall.setChargePlan13 6.1.2 getConferenceInfo 14 6.1.2.1 Mapping from IpAppMultiMediaCallLeg.even
10、tReportRes14 6.1.2.2 Mapping from IpAppMultiMediaCall.getInfoRes.15 6.1.2.3 Mapping from IpAppMultiMediaCallLeg.callLegEnded.16 6.1.2.4 Mapping from IpAppMultiMediaCall.callEnded .16 6.1.3 endConference 16 6.1.3.1 Mapping to IpMultiMediaCall.release17 6.1.4 inviteParticipant17 6.1.4.1 Mapping to IpM
11、ultiMediaCall.createAndRouteCallLegReq .17 6.1.4.1.1 Alternative Mapping to IpMultiMediaCall.createCallLeg.18 6.1.4.1.2 Alternative Mapping to IpMultiMediaCallLeg.eventReportReq18 6.1.4.1.3 Alternative Mapping to IpMultiMediaCallLeg.routeReq 18 6.1.5 disconnectParticipant 18 6.1.5.1 Mapping to IpMul
12、tiMediaCallLeg.release.19 6.1.6 addMediaForParticipant19 6.1.6.1 Mapping to IpMultiMediaCallLeg.mediaStreamMonitorReq .19 6.1.6.2 Mapping from IpAppMultiMediaCallLeg.mediaStreamMonitorRes20 6.1.6.3 Mapping to IpMultiMediaCallLeg.mediaStreamAllow .21 6.1.7 deleteMediaForParticipant22 6.1.7.1 Mapping
13、to IpMultiMediaCallLeg.getMediaStreams22 6.1.7.2 Mapping to IpMultiMediaStream.subtract.22 6.1.8 getParticipantInfo .23 6.1.8.1 Mapping to IpMultiMediaCallLeg.getMediaStreams23 6.1.9 getParticipants.23 6.2 Exceptions 24 6.2.1 Mapping from TpCallError24 6.2.2 Mapping from Parlay/OSA Method Exceptions
14、 .24 7 Additional Notes 24 History 25 ETSI ETSI TR 102 397-12 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 publicly available for ETSI mem
15、bers 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 ETSI Web server (http:/webapp.e
16、tsi.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, or may be, or may become, e
17、ssential 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 12 of a multi-part deliverable covering Open Service Acc
18、ess (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“; Part 6: “Payment Mapping“; Part 7: “Accou
19、nt Management Mapping“; 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
20、 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 document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. ETSI ETSI TR 102 397-12 V1.1.1 (2005-08) 5 1 Scope The Parlay
21、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 Service Access (OSA) specifications define an architecture
22、that enables application 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 Multimedia Conference Web Service to the Multi-Party Call Control and Multi-Media Call Control Service
23、 Capability Features (SCFs). 2 References 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
24、 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); Mapping of Parlay X Web Services to Parlay/OSA APIs; Part 1: Common Mapping“. 4 ETSI ES 202 391-13: “Open Service Acce
25、ss (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 and definitions given in TR 102 397-1 3 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given i
26、n TR 102 397-1 3 apply. 4 Mapping Description The Call Handling capability can be implemented with Parlay/OSA Multi-Party Call Control and Multi-Media Call Control. It is applicable to ETSI 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-12 V1.1.1 (2005-08) 6 5
27、Sequence Diagrams 5.1 Create Conference Appl Multimedia Conference IpApp MMCC Manager Ip MMCC Manager IpApp MMCall Ip MMCall createConferenceRequest “new” createCall() “new” createConferenceResponse setChargePlan() getInfoReq() getConferenceInfoRequest getConferenceInfoResponse: “Initial” Figure 1 E
28、TSI ETSI TR 102 397-12 V1.1.1 (2005-08) 7 5.2 End Conference Appl Multimedia Conference IpApp MMCallLeg:A IpApp MMCC Manager Ip MMCC Manager IpApp MMCall Ip MMCall Ip MMCallLeg:A getConferenceInfoRequest getConferenceInfoResponse: “Terminated, conference duration” getConferenceInfoRequest getConfere
29、nceInfoResponse: “Active, multiple participants connected” endConferenceRequest endConferenceResponse release() “destroy” getInfoRes() “forward event” Figure 2 ETSI ETSI TR 102 397-12 V1.1.1 (2005-08) 8 5.3 Invite Participant Appl Multimedia Conference IpApp MMCallLeg:A IpApp MMCC Manager Ip MMCC Ma
30、nager IpApp MMCall Ip MMCall Ip MMCallLeg:A getConferenceInfoRequest getConferenceInfoResponse: “Initial” inviteParticipantRequest createAndRouteCallLegReq() eventReportRes():P_CALL_EVENT_ANSWER “forward event” “new” “new” inviteParticipantResponse getConferenceInfoRequest getConferenceInfoResponse:
31、 “Initial” getParticipantInfoRequest getParticipantInfoResponse: “Invited” getConferenceInfoRequest getConferenceInfoResponse: “Active” getParticipantInfoRequest getParticipantInfoResponse: “Connected” getMediaStreams() Figure 3 ETSI ETSI TR 102 397-12 V1.1.1 (2005-08) 9 5.4 Invite Participant Alter
32、native Mapping There is also another option for mapping inviteParticipant operation on Parlay interfaces; this option is presented in the following sequence diagram: Appl Multimedia Conference IpApp MMCallLeg:A IpApp MMCC Manager Ip MMCC Manager IpApp MMCall Ip MMCall Ip MMCallLeg:A getConferenceInf
33、oRequest getConferenceInfoResponse: “Initial” inviteParticipantRequest createCallLeg() PCALL EVENT ANSWER“forward event” “new” “new” inviteParticipantResponse getConferenceInfoRequest getConferenceInfoResponse: “Initial” getParticipantInfoRequest getParticipantInfoResponse: “Invited” getConferenceIn
34、foRequest getConferenceInfoResponse: “Active” getParticipantInfoRequest getParticipantInfoResponse: “Connected” eventReportReq() routeReq() getMediaStreams() Figure 4 ETSI ETSI TR 102 397-12 V1.1.1 (2005-08) 105.5 Disconnect Participant Appl Multimedia Conference IpApp MMCall Leg:A IpApp MMCC Manage
35、r Ip MMCC Manager IpApp MMCall Ip MMCall Ip MMCall Leg:A getConferenceInfoRequest getConferenceInfoResponse: “Active” getParticipantInfoRequest getParticipantInfoResponse: “Disconnected” getConferenceInfoRequest getConferenceInfoResponse: “Active, multiple participants connected” getParticipantInfoR
36、equest getParticipantInfoResponse: “Connected” disconnectParticipantRequest disconnectParticipantResponse release() “destroy” getMediaStreams() Figure 5 ETSI ETSI TR 102 397-12 V1.1.1 (2005-08) 115.6 Add Media For Participant Appl Multimedia Conference IpApp MMCallLeg:A IpAppMMCC Manager Ip MMCC Man
37、ager IpApp MMCall Ip MMCall Ip MMCallLeg:A getConferenceInfoRequest getConferenceInfoResponse: “Active” getParticipantInfoRequest getParticipantInfoResponse: “Connected, with Audio IN/OUT depending on the media and mediaDirection parameters in addMediaForParticipant, the web service invokes the IpMu
38、ltiMediaCallLeg.mediaStreamAllow method in order to allow or deny the permission for adding the new media stream on the participants terminal. The addMediaForParticipant operation maps to/from the following Parlay/OSA methods: IpMultiMediaCallLeg.mediaStreamMonitorReq IpAppMultiMediaCallLeg.mediaStr
39、eamMonitorRes IpMultiMediaCallLeg.mediaStreamAllow 6.1.6.1 Mapping to IpMultiMediaCallLeg.mediaStreamMonitorReq The method IpMultiMediaCallLeg.mediaStreamMonitorReq is invoked with the following parameters: Name Type Comment callLegSessionID TpSessionID Not mapped: the result returned from the invoc
40、ation of IpMultiMediaCall.create(AndRoute)CallLeg(Req) mediaStreamEventCriteria TpMediaStream RequestSet Consists of a single set element defining the media stream for which to monitor. It is constructed based on the values provided in the media and mediaDirection parts of the addMediaForParticipant
41、Request message. See the following table for details. ETSI ETSI TR 102 397-12 V1.1.1 (2005-08) 20The mediaStreamEventCriteria parameter is constructed as follows: Name Type Comment Direction TpMediaStreamDirection MediaDirection values map to Direction values as follows: In maps to P_RECEIVE_ONLY Ou
42、t maps to P_SEND_ONLY InOut maps to P_SEND_RECEIVE DataTypeRequest TpMediaStreamDataType Request Media values map to DataTypeRequest values as follows: Audio maps to P_AUDIO_CAPABILITIES. There is no mapping to the associated Audio element, which identifies the audio codec capabilities. This element
43、 value is defined by policy. Video maps to P_VIDEO_CAPABILITIES. There is no mapping to the associated Video element, which identifies the video codec capabilities. This element value is defined by policy. Chat maps to P_DATA_ CAPABILITIES. There is no mapping to the associated Data element, which d
44、efines the lower threshold for the maxBitRate parameter. This element value is defined by policy. Data maps to P_DATA_CAPABILITIES. There is no mapping to the associated Data element, which defines the lower threshold for the maxBitRate parameter. This element value is defined by policy. MediaMonito
45、rMode TpCallMonitorMode Not mapped. Set to a value of P_CALL_MONITOR_MODE_INTERRUPT if the web service is required by policy to explicitly authorize addition of the multimedia stream (i.e. by invoking the IpMultiMediaCallLeg.mediaStreamAllow method). Otherwise set to a value of P_CALL_MONITOR_MODE_N
46、OTIFY. EventType TpMediaStreamEvent Type Not mapped. Set to a value of P_MEDIA_STREAM_ADDED Parlay exceptions thrown by IpMultiMediaCallLeg.mediaStreamMonitorReq are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.6.2 Mapping from IpAppMultiMediaCallLeg.mediaStreamMonitorRes The method I
47、pAppMultiMediaCallLeg.mediaStreamMonitorRes is invoked with the following parameters: Name Type Comment callLegSessionID TpSessionID Not mapped: the result returned from the invocation of IpMultiMediaCall.create(AndRoute)CallLeg(Req) streams TpMediaStreamSet Specifies all the media streams that are
48、added. Note that this can be more than one media stream, if multiple invocations of IpMultiMediaCallLeg. mediaStreamMonitorReq have occurred for this participant. For each set element the validation of the TpMediaStream data type is specified in the following table. Validated streams are “allowed“ b
49、y the web service by invoking the mediaStreamMonitorReq method (ref 0). type TpMediaStreamEventType Not mapped. Set to a value of P_MEDIA_STREAM_ADDED ETSI ETSI TR 102 397-12 V1.1.1 (2005-08) 21Each element of the streams set is of type TpMediaStream and is validated against the media and mediaDirection parts of a previously received addMediaForParticipantRequest message, as follows: Name Type Comment Direction TpMediaStreamDirection Direction matches with MediaDirection as follows: P_RECEIVE_ONLY matches with In or InOut P_SEND_ONLY matches with Out
