1、 ETSI ES 202 915-4-4 V1.4.1 (2006-12)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 4: Call Control;Sub-part 4: Multi-Media Call Control SCF(Parlay 4)floppy3 ETSI ETSI ES 202 915-4-4 V1.4.1 (2006-12) 2 Reference RES/TISPAN-01028-04-04-OSA Keywords API, IDL, OSA,
2、 UML 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 document
3、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 dispute, t
4、he 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 ETSI do
5、cuments 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 written p
6、ermission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2006. The Parlay Group 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand
7、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 ES 202 915-4-4 V1.4.1 (2006-12) 3 Contents Intellectual Property Rights5 Fore
8、word.5 1 Scope 7 2 References 7 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 MultiMedia Call Control Service Sequence Diagrams 8 4.1 Barring for media combined with call routing, alternative 18 4.2 Barring for media combined with call routing, alternative 29 4.3 Barring
9、for media, simple.11 4.4 Call Volume charging supervision .12 5 Class Diagrams.14 6 MultiMedia Call Control Service Interface Classes.15 6.1 Interface Class IpMultiMediaCallControlManager16 6.1.1 Method createMediaNotification() .16 6.1.2 Method destroyMediaNotification() .17 6.1.3 Method changeMedi
10、aNotification()17 6.1.4 Method getMediaNotification()18 6.2 Interface Class IpAppMultiMediaCallControlManager .18 6.2.1 Method reportMediaNotification() .18 6.3 Interface Class IpMultiMediaCall 19 6.3.1 Method superviseVolumeReq()19 6.4 Interface Class IpAppMultiMediaCall .20 6.4.1 Method superviseV
11、olumeRes() 20 6.4.2 Method superviseVolumeErr() .20 6.5 Interface Class IpMultiMediaCallLeg21 6.5.1 Method mediaStreamAllow() .21 6.5.2 Method mediaStreamMonitorReq()21 6.5.3 Method getMediaStreams() 22 6.6 Interface Class IpAppMultiMediaCallLeg .22 6.6.1 Method mediaStreamMonitorRes() 22 6.7 Interf
12、ace Class IpMultiMediaStream23 6.7.1 Method subtract()23 7 MultiMedia Call Control Service State Transition Diagrams 23 8 Multi-Media Call Control Data Definitions .24 8.1 Event Notification Data Definitions.24 8.1.1 TpMediaStreamRequestSet 24 8.1.2 TpMediaStreamRequest24 8.1.3 TpMediaStreamDirectio
13、n .24 8.1.4 TpMediaStreamDataTypeRequest25 8.1.5 TpMediaStreamDataTypeRequestType25 8.1.6 TpAudioCapabilitiesType.25 8.1.7 TpVideoCapabilitiesType.26 8.1.8 TpDataCapabilities .26 8.1.9 TpMediaStreamEventType.26 8.1.10 TpMediaStreamSet .26 8.1.11 TpMediaStream 26 8.1.12 TpMediaStreamDataType.26 8.2 M
14、ulti-Media Call Control Data Definitions .26 8.2.1 IpMultiMediaCall .26 ETSI ETSI ES 202 915-4-4 V1.4.1 (2006-12) 4 8.2.2 IpMultiMediaCallRef26 8.2.3 IpAppMultiMediaCall 27 8.2.4 IpAppMultiMediaCallRef.27 8.2.5 IpMultiMediaCallLeg .27 8.2.6 IpMultiMediaCallLegRef .27 8.2.7 IpAppMultiMediaCallLeg 27
15、8.2.8 IpAppMultiMediaCallLegRef.27 8.2.9 TpAppMultiMediaCallLegRefSet 27 8.2.10 TpMultiMediaCallIdentifier .27 8.2.11 TpMultiMediaCallIdentifierSet 27 8.2.12 TpMultiMediaCallLegIdentifier .27 8.2.13 TpMultiMediaCallLegIdentifierSet 27 8.2.14 IpAppMultiMediaCallControlManager 28 8.2.15 IpAppMultiMedi
16、aCallControlManagerRef 28 8.2.16 TpAppMultiMediaCallBack .28 8.2.17 TpAppMultiMediaCallBackRefType .28 8.2.18 TpAppMultiMediaCallLegCallBack 28 8.2.19 TpCallSuperviseVolume.29 8.2.20 TpNotificationMediaRequest29 8.2.21 TpMediaNotificationRequested29 8.2.22 TpMediaNotificationsRequestedSet .29 Annex
17、A (normative): OMG IDL Description of Multi-Media Call Control SCF.30 Annex B (informative): W3C WSDL Description of Multi-Media Call Control SCF .31 Annex C (informative): Java API Description of the Call Control SCFs32 Annex D (informative): Contents of 3GPP OSA Rel-5 Call Control .33 Annex E (inf
18、ormative): Record of changes 34 E.1 Interfaces 34 E.1.1 New 34 E.1.2 Deprecated34 E.1.3 Removed.34 E.2 Methods35 E.2.1 New 35 E.2.2 Deprecated35 E.2.3 Modified.35 E.2.4 Removed.35 E.3 Data Definitions .36 E.3.1 New 36 E.3.2 Modified.36 E.3.3 Removed.36 E.4 Service Properties.37 E.4.1 New 37 E.4.2 De
19、precated37 E.4.3 Modified.37 E.4.4 Removed.37 E.5 Exceptions 38 E.5.1 New 38 E.5.2 Modified.38 E.5.3 Removed.38 E.6 Others .38 History 39 ETSI ETSI ES 202 915-4-4 V1.4.1 (2006-12) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to
20、 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 Essential, IPRs notified to ETSI in respect of ETSI standards“, which is ava
21、ilable 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. No guarantee can be given as to the existence of other IPRs not referen
22、ced 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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networki
23、ng (TISPAN). The present document is part 4, sub-part 4 of a multi-part deliverable covering Open Service Access (OSA); Application Programming Interface (API), as identified below. The API specification (ES 202 915) is structured in the following parts: Part 1: “Overview“; Part 2: “Common Data Defi
24、nitions“; Part 3: “Framework“; Part 4: “Call Control“; Sub-part 1: “Call Control Common Definitions“; Sub-part 2: “Generic Call Control SCF“; Sub-part 3: “Multi-Party Call Control SCF“; Sub-part 4: “Multi-Media Call Control SCF“; Sub-part 5: “Conference Call Control SCF“; Part 5: “User Interaction S
25、CF“; Part 6: “Mobility SCF“; Part 7: “Terminal Capabilities SCF“; Part 8: “Data Session Control SCF“; Part 9: “Generic Messaging SCF“; Part 10: “Connectivity Manager SCF“; Part 11: “Account Management SCF“; Part 12: “Charging SCF“; Part 13: “Policy Management SCF“; Part 14: “Presence and Availabilit
26、y Management SCF“. ETSI ETSI ES 202 915-4-4 V1.4.1 (2006-12) 6 The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP, in co-operation with a number of JAIN Community (http:/ member companies. The present document forms part of the Parlay 4.3
27、 set of specifications. The present document is equivalent to 3GPP TS 29.198-4-4 V5.9.0 (Release 5). ETSI ETSI ES 202 915-4-4 V1.4.1 (2006-12) 7 1 Scope The present document is part 4, sub-part 4 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA
28、). The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The present document specifies the Multi-Media Call Control Service Capability Feature (SCF) aspects of the interface.
29、All aspects of the Multi-Media Call Control SCF are defined here, these being: Sequence Diagrams. Class Diagrams. Interface specification plus detailed method descriptions. State Transition diagrams. Data Definitions. IDL Description of the interfaces. WSDL Description of the interfaces. Reference t
30、o the Java API description of the interfaces. The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML). 2 References The references listed in clause 2 of ES 202 915-1 contain provisions which, through reference
31、 in this text, constitute provisions of the present document. ETSI ES 202 915-1: “Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 4)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions give
32、n in ES 202 915-1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in ES 202 915-1 apply. ETSI ETSI ES 202 915-4-4 V1.4.1 (2006-12) 8 4 MultiMedia Call Control Service Sequence Diagrams 4.1 Barring for media combined with call routing, alternative 1 This s
33、equence illustrates how one application can influence both the call routing and the media stream establishment of one call. In this sequence there is one application handling both the media barring and the routing of the call. : (Lo gical View:IpAppLogic): IpAppMultiMediaCallControlManager: IpMultiM
34、ediaCallControlManager: IpMultiMediaCall: IpMultiMediaCallLeg: IpAppMultiMediaCallLeg1: new()2: createNotification( )3: reportNotification( )4: “forward event“10: createAndRouteCallLegReq( )6: mediaStreamMonitorReq( )9: mediaStreamAllow( )7: mediaStreamMonitorRes( )5: new()8: “forward event“11: medi
35、aStreamMonitorRes( )12: “forward event“13: mediaStreamAllow( )1: The application creates a AppMultiMediaCallControlManager interface in order to handle callback methods. 2: The application expresses interest in all calls from subscriber A. Since createNotification is used and not createMediaNotifica
36、tion all calls are reported regardless of the media used. 3: A makes a call with the SIP INVITE with SDP media stream indicating video. The application is notified. 4: The event is forwarded to the application. 5: The application creates a new AppMultiMediaCallLeg interface to receive callbacks. 6:
37、The application sets a monitor on video media streams to be established (added) for the indicated leg. 7: Since the video media stream was included in the SIP invite, the media streams monitored will be returned in the monitor result. ETSI ETSI ES 202 915-4-4 V1.4.1 (2006-12) 9 8: The event is forwa
38、rded to the application. 9: The application denies the video media stream, i.e. it is not included in the allowed media streams. This corresponds to removing the media stream from the setup. 10: The application requests to reroute the call to a different destination (or the same one, etc.). 11: Late
39、r in the call the A party tries to establish a lower bandwidth video media stream. This is again reported with MediaStreamMonitorRes. 12: The event is forwarded. 13: This time the application allows the establishment of the media stream by including the media stream in the allowed list. 4.2 Barring
40、for media combined with call routing, alternative 2 This sequence illustrates how one application can influence both the call routing and the media establishment of one call. Media establishment and call establishment are regarded separately by the application. From the gateway point of view it can
41、actually be regarded as two separately triggered applications, one for media control and one for routing. This is also the way that it is shown here, for clarity. However, an implementation of the application could combine the media logic and call logic in one object. ETSI ETSI ES 202 915-4-4 V1.4.1
42、 (2006-12) 10callLogic : (Logical View:IpAppLogic)callAppLogic : IpAppMultiMediaCallControlManag er: IpMultiMediaCallControlManager: IpMultiMediaCallPartyA : IpMultiMediaCallLegPartyB : IpAppCallLegPartyB : IpAppCallLegPartyA : IpMultiMedi.: IpAppMultiMediaCall mediaAppLogic : IpAppMultiMediaCallCon
43、trolManagermediaLogic : (Logic.1: new()2: createNotification( )5: reportNotification( )6: “forward event“12: createAndRouteCallLeg Req( )7: new()9: reportMediaNotification( )19: reportMediaNotification( )3: new()4 : c r eat eM e di aN o ti f ic at io n ( )10: “forward event“14: mediaStreamAllow( )15
44、: deassignCall( )20: “forward event“21: mediaStreamAllow( )22: deassignCall( )8: new()11: new()13: new()1 6: e ven t R e p or t R es ( )17: “forwa rd event“18: deassignCall( )1: The application creates a new AppMultiMediaCallControlManager interface. 2: The application expresses interest in all call
45、s from subscriber A for rerouting purposes. 3: The application creates a new AppMultiMediaCallControlManager interface. This is to be used for the media control only. 4: Separately the application expresses interest is some media streams for calls from and to A. The request indicates interrupt mode.
46、 5: Subscriber A makes a call with the SIP INVITE with SDP media stream indicating video. Since the media establishment is combined with the SIP INVITE message, both applications are triggered (not necessarily in the order shown). Here the call application is notified about the call setup. 6: The ev
47、ent is forwarded to the call control application. 7: The call control application creates a new AppMultiMediaCall interface. 8: The call control application creates a new AppMultiMediaCallLeg interface. 9: The media application is notified about the call setup. All media streams from the setup will
48、be indicated. 10: The event is forwarded to the media application. 11: The call control application creates a new AppMultiMediaCallLeg interface. 12: The call application decides to reroute the call to another address. Included in the request are monitors on answer and call end. However, since the m
49、edia was also triggered in mode interrupt the call will not proceed until the media streams are confirmed or rejected. ETSI ETSI ES 202 915-4-4 V1.4.1 (2006-12) 1114: The application allows the audio media stream, but refuses the high bandwidth video, by excluding it from the allowed list. Since both call processing and media handling is now acknowledged, the call routing can continue (with a changed SDP parameter reflecting the manipulated media). 15: The Media application is no longer interested in the ca
