ETSI TS 129 198-4-4-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmi_1.pdf

1、 ETSI TS 129 198-4-4 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA)Application Programming Interface (API);Part 4: Call control;Subpart 4: Multimedia call controlService Cap

2、ability Feature (SCF) (3GPP TS 29.198-04-4 version 9.0.0 Release 9)floppy3ETSI ETSI TS 129 198-4-4 V9.0.0 (2010-01) 13GPP TS 29.198-04-4 version 9.0.0 Release 9 Reference RTS/TSGC-0029198-04-4v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4

3、 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:/www.etsi.org The present document may be made availabl

4、e 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 printing on ETSI printers of the PDF version kept on a spe

5、cific 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:/portal.etsi.org/tb/status/status.asp If you find error

6、s 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 foregoing restriction extend to reproduction in all

7、 media. European Telecommunications Standards Institute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and

8、of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 198-4-4 V9.0.0 (2010-01) 23GPP TS 29.

9、198-04-4 version 9.0.0 Release 9 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 members and non-members, and can be found in ETSI S

10、R 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.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR

11、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, essential to the present document. Foreword This

12、Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding

13、 ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 198-4-4 V9.0.0 (2010-01) 33GPP TS 29.198-04-4 version 9.0.0 Release 9 Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3

14、Introduction 5g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 MultiMedia Call Control Service Sequence Diagrams 8g34.1 Barring for media combined with call routing, alternative 1 8g34.2 Barring for media combined with call routing, altern

15、ative 2 10g34.3 Barring for media, simple . 11g34.4 Call Volume charging supervision . 12g35 Class Diagrams . 14g36 MultiMedia Call Control Service Interface Classes . 15g36.1 Interface Class IpMultiMediaCallControlManager 16g36.1.1 Method createMediaNotification() . 16g36.1.2 Method destroyMediaNot

16、ification() . 17g36.1.3 Method changeMediaNotification() 17g36.1.4 Method getMediaNotification() 18g36.2 Interface Class IpAppMultiMediaCallControlManager . 18g36.2.1 Method reportMediaNotification() . 18g36.3 Interface Class IpMultiMediaCall 19g36.3.1 Method superviseVolumeReq() 20g36.4 Interface C

17、lass IpAppMultiMediaCall . 20g36.4.1 Method superviseVolumeRes() 20g36.4.2 Method superviseVolumeErr() . 21g36.5 Interface Class IpMultiMediaCallLeg 21g36.5.1 Method mediaStreamAllow() . 21g36.5.2 Method mediaStreamMonitorReq() 22g36.5.3 Method getMediaStreams() 22g36.6 Interface Class IpAppMultiMed

18、iaCallLeg . 23g36.6.1 Method mediaStreamMonitorRes() 23g36.7 Interface Class IpMultiMediaStream 23g36.7.1 Method subtract() 24g37 MultiMedia Call Control Service State Transition Diagrams 24g38 Multi-Media Call Control Data Definitions . 25g38.1 Event Notification Data Definitions . 25g38.1.1 TpMedi

19、aStreamRequestSet 25g38.1.2 TpMediaStreamRequest 25g38.1.3 TpMediaStreamDirection . 25g38.1.4 TpMediaStreamDataTypeRequest 26g38.1.5 TpMediaStreamDataTypeRequestType 26g38.1.6 TpAudioCapabilitiesType . 26g38.1.7 TpVideoCapabilitiesType . 27g38.1.8 TpDataCapabilities . 27g38.1.9 TpMediaStreamEventTyp

20、e . 27g38.1.10 TpMediaStreamSet . 27g38.1.11 TpMediaStream 27g3ETSI ETSI TS 129 198-4-4 V9.0.0 (2010-01) 43GPP TS 29.198-04-4 version 9.0.0 Release 9 8.1.12 TpMediaStreamDataType . 27g38.2 Multi-Media Call Control Data Definitions . 28g38.2.1 IpMultiMediaCall . 28g38.2.2 IpMultiMediaCallRef 28g38.2.

21、3 IpAppMultiMediaCall 28g38.2.4 IpAppMultiMediaCallRef . 28g38.2.5 IpMultiMediaCallLeg . 28g38.2.6 IpMultiMediaCallLegRef . 28g38.2.7 IpAppMultiMediaCallLeg 28g38.2.8 IpAppMultiMediaCallLegRef. 28g38.2.9 TpAppMultiMediaCallLegRefSet 28g38.2.10 TpMultiMediaCallIdentifier . 28g38.2.11 TpMultiMediaCall

22、IdentifierSet 28g38.2.12 TpMultiMediaCallLegIdentifier . 29g38.2.13 TpMultiMediaCallLegIdentifierSet 29g38.2.14 IpAppMultiMediaCallControlManager 29g38.2.15 IpAppMultiMediaCallControlManagerRef 29g38.2.16 TpAppMultiMediaCallBack . 29g38.2.17 TpAppMultiMediaCallBackRefType . 29g38.2.18 TpAppMultiMedi

23、aCallLegCallBack 29g38.2.19 TpCallSuperviseVolume . 30g38.2.20 TpNotificationMediaRequest 30g38.2.21 TpMediaNotificationRequested 30g38.2.22 TpMediaNotificationsRequestedSet . 30g3Annex A (normative): OMG IDL Description of Multi-Media Call Control SCF . 31g3Annex B (informative): W3C WSDL Descripti

24、on of Multi-Media Call Control SCF . 32g3Annex C (informative): Java API Description of the Call Control SCFs . 33g3Annex D (informative): Description of Call Control Sub-part 4: Multimedia call control SCF for 3GPP2 cdma2000 networks 34g3D.1 General Exceptions. 34g3D.2 Specific Exceptions 34g3D.2.1

25、 Clause 1: Scope 34g3D.2.2 Clause 2: References 34g3D.2.3 Clause 3: Definitions and abbreviations . 34g3D.2.4 Clause 4: MultiMedia Call Control Service Sequence Diagrams . 34g3D.2.5 Clause 5: Class Diagrams . 34g3D.2.6 Clause 6: MultiMedia Call Control Service Interface Classes . 35g3D.2.7 Clause 7:

26、 MultiMedia Call Control Service State Transition Diagrams . 35g3D.2.8 Clause 8: Multi-Media Call Control Data Definitions 35g3D.2.9 Annex A (normative): OMG IDL Description of Multi-Media Call Control SCF . 35g3D.2.10 Annex B (informative): W3C WSDL Description of Multi-Media Call Control SCF . 35g

27、3D.2.11 Annex C (informative): Java API Description of the Call Control SCF 35g3Annex E (informative): Change history . 36g3History 37g3ETSI ETSI TS 129 198-4-4 V9.0.0 (2010-01) 53GPP TS 29.198-04-4 version 9.0.0 Release 9 Foreword This Technical Specification has been produced by the 3rdGeneration

28、Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an

29、 increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhan

30、cements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part 4, sub-part 4 of a multi-part TS covering the 3rdGeneration Partnership Project: Technical Specification Group Core Netwo

31、rk; Open Service Access (OSA); Application Programming Interface (API), as identified below. The API specification (3GPP TS 29.198) is structured in the following Parts: Part 1: “Overview“; Part 2: “Common Data Definitions“; Part 3: “Framework“; Part 4: “Call Control“; Sub-part 1: “Call Control Comm

32、on 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“; (new in 3GPP Release 7) Part 5: “User Interaction SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal Capabilities S

33、CF“; Part 8: “Data Session Control SCF“; Part 9: “Generic Messaging SCF“; (not part of 3GPP Release 7) Part 10: “Connectivity Manager SCF“; (not part of 3GPP Release 7) Part 11: “Account Management SCF“; Part 12: “Charging SCF“. Part 13: “Policy Management SCF“; Part 14: “Presence and Availability M

34、anagement SCF“; Part 15: “Multi Media Messaging SCF“; Part 16: “Service Broker SCF“. (new in 3GPP Release 7) The Mapping specification of the OSA APIs and network protocols (3GPP TR 29.998) is also structured as above. A mapping to network protocols is however not applicable for all Parts, but the n

35、umbering of Parts is kept. Also in case a Part is not supported in a Release, the numbering of the parts is maintained. ETSI ETSI TS 129 198-4-4 V9.0.0 (2010-01) 63GPP TS 29.198-04-4 version 9.0.0 Release 9 Table: Overview of the OSA APIs Part 1: Overview“. 2 3GPP TS 22.127: “Service Requirement for

36、 the Open Services Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TS 22.002: “Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)“. 5 void ETSI ETSI TS 129 198-4-4 V9.0.0 (2010-01) 83GPP TS 29.198-04-4 version 9.0.0 Release 9 6 3GPP T

37、S 24.002: “GSM-UMTS Public Land Mobile Network (PLMN) Access Reference Configuration“. 7 3GPP TS 22.003: “Circuit Teleservices supported by a Public Land Mobile Network (PLMN)“ 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given i

38、n TS 29.198-1 1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TS 29.198-1 1 apply. 4 MultiMedia Call Control Service Sequence Diagrams 4.1 Barring for media combined with call routing, alternative 1 This sequence illustrates how one application can inf

39、luence 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. ETSI ETSI TS 129 198-4-4 V9.0.0 (2010-01) 93GPP TS 29.198-04-4 version 9.0.0 Release 9 : (Lo gical View:IpAppLogic): IpA

40、ppMultiMediaCallControlManager: IpMultiMediaCallControlManager: IpMultiMediaCall: IpMultiMediaCallLeg: IpAppMultiMediaCallLeg1: new()2: createNotification( )3: reportNotification( )4: “forward event“10: createAndRouteCallLegReq( )6: mediaStreamMonitorReq( )9: mediaStreamAllow( )7: mediaStreamMonitor

41、Res( )5: new()8: “forward event“11: mediaStreamMonitorRes( )12: “forward event“13: mediaStreamAllow( )1: The application creates an AppMultiMediaCallControlManager interface in order to handle callback methods. 2: The application expresses interest in all calls from subscriber A. Since createNotific

42、ation is used and not createMediaNotification 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 AppMultiMediaCa

43、llLeg interface to receive callbacks. 6: 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. 8: The event is forwarde

44、d 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). 11: Later in the

45、call the A party tries to establish a lower bandwidth video media stream. This is again reported with MediaStreamMonitorRes. 12: The event is forwarded. ETSI ETSI TS 129 198-4-4 V9.0.0 (2010-01) 103GPP TS 29.198-04-4 version 9.0.0 Release 9 13: This time the application allows the establishment of t

46、he media stream by including the media stream in the allowed list. 4.2 Barring 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

47、 regarded separately by the application. From the gateway point of view it can 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 combin

48、e the media logic and call logic in one object. callLogic : (Logical View:IpAppLogic)callAppLogic : IpAppMultiMediaCallControlManag er: IpMultiMediaCallControlManager: IpMultiMediaCallPartyA : IpMultiMediaCallLegPartyB : IpAppCallLegPartyB : IpAppCallLegPartyA : IpMultiMedi.: IpAppMultiMediaCall med

49、iaAppLogic : IpAppMultiMediaCallControlManagermediaLogic : (Logic.1: new()2: createNotification( )5: reportNotification( )6: “forward event“12: createAndRouteCallLegReq( )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: 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 AppM