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

1、 ETSI TS 129 198-4-1 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 1: Call control common definitions (3

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

3、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 available in more than one elect

4、ronic 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 specific network drive with

5、in 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 errors in the present documen

6、t, 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 media. European Telecom

7、munications 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 of the 3GPP Organization

8、al 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-1 V9.0.0 (2010-01) 23GPP TS 29.198-04-1 version 9.0.0 R

9、elease 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 SR 000 314: “Intellectual

10、 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 Policy, no investigation

11、, 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 Technical Specification

12、(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 ETSI deliverables. The

13、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-1 V9.0.0 (2010-01) 33GPP TS 29.198-04-1 version 9.0.0 Release 9 Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope

14、7g32 References 7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Call Control SCF 8g34.1 Call Model Description 8g34.2 Structure of Call Control SCF Documentation . 9g34.3 General requirements on support of methods . 9g34.4 Application Control of a Call or Session

15、9g34.4.1 Introduction. 9g34.4.2 Concept of Multiple Points of Control 9g34.4.2.1 Cascaded Chain Model . 10g34.4.3 Service Interactions. 11g34.4.4 Multiple services - applicability of MPC for Parlay/OSA 11g35 The Service Interface Specifications 12g35.1 Interface Specification Format . 12g35.1.1 Inte

16、rface Class 12g35.1.2 Method descriptions 12g35.1.3 Parameter descriptions 12g35.1.4 State Model . 12g35.2 Base Interface . 12g35.2.1 Interface Class IpInterface 12g35.3 Service Interfaces . 13g35.3.1 Overview 13g35.4 Generic Service Interface . 13g35.4.1 Interface Class IpService 13g35.4.1.1 Method

17、 setCallback() 13g35.4.1.2 Method setCallbackWithSessionID() 14g36 Common Call Control Data Types . 14g36.1 TpCallAlertingMechanism . 14g36.2 TpCallBearerService 14g36.3 TpCallChargePlan 15g36.4 TpCallPartyToChargeAdditionalInfo . 15g36.5 TpCallPartyToChargeType 15g36.6 TpCallChargeOrderCategory . 1

18、6g36.7 TpCallEndedReport 16g36.8 TpCallError 16g36.9 TpCallAdditionalErrorInfo . 16g36.10 TpCallErrorType 17g36.11 TpCallInfoReport . 17g36.12 TpCallInfoType 17g36.13 TpCallLoadControlMechanism 18g36.14 TpCallLoadControlIntervalRate . 18g36.15 TpCallLoadControlMechanismType 18g36.16 TpCallMonitorMod

19、e 18g36.17 TpCallNetworkAccessType . 19g3ETSI ETSI TS 129 198-4-1 V9.0.0 (2010-01) 43GPP TS 29.198-04-1 version 9.0.0 Release 9 6.18 TpCallPartyCategory 19g36.19 TpCallServiceCode 19g36.20 TpCallServiceCodeSet . 19g36.21 TpCallServiceCodeType 20g36.22 TpCallSuperviseReport 20g36.23 TpCallSuperviseTr

20、eatment . 20g36.24 TpCallTeleService 21g36.25 TpCallTreatment 21g36.26 TpCallTreatmentType 22g36.27 TpCallAdditionalTreatmentInfo . 22g36.28 TpMediaType . 22g3Annex A (normative): OMG IDL Description of Common Call Control Data Types . 23g3Annex B (informative): W3C WSDL Description of Common Call C

21、ontrol Data Types . 24g3Annex C (informative): Java API Description of the Call Control SCFs 25g3Annex D (informative): Description of Call Control Sub-part 1: Call Control Common Definitions for 3GPP2 cdma2000 networks . 26g3D.1 General Exceptions. 26g3D.2 Specific Exceptions 26g3D.2.1 Clause 1: Sc

22、ope 26g3D.2.2 Clause 2: References 26g3D.2.3 Clause 3: Definitions and abbreviations . 26g3D.2.4 Clause 4: Call Control SCF 26g3D.2.5 Clause 5: The Service Interface Specifications 26g3D.2.6 Clause 6: Common Call Control Data Types . 27g3D.2.7 Annex A (normative): OMG IDL Description of Common Call

23、Control Data Types . 27g3D.2.8 Annex B (informative): W3C WSDL Description of Common Call Control Data Types . 27g3D.2.9 Annex C (informative): Java API Description of the Call Control SCFs . 27g3Annex E (informative): Change history . 28g3History 29g3ETSI ETSI TS 129 198-4-1 V9.0.0 (2010-01) 53GPP

24、TS 29.198-04-1 version 9.0.0 Release 9 Foreword This Technical Specification has been produced by the 3rdGeneration 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 c

25、ontents of the present document, it will be re-released by the TSG with an identifying change of release date and an 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

26、 document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, 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, su

27、b-part 1 of a multi-part TS covering the 3rdGeneration Partnership Project: Technical Specification Group Core Network; 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: “Overv

28、iew“; Part 2: “Common Data Definitions“; 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 SC

29、F“; Part 5: “User Interaction SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal Capabilities SCF“; Part 8: “Data Session Control SCF“; Part 9: “Generic Messaging SCF“; (not part of 3GPP Release 8) Part 10: “Connectivity Manager SCF“; (new in 3GPP Release 8) Part 11: “Account Management SCF“; Part 12:

30、“Charging SCF“. Part 13: “Policy Management SCF“; Part 14: “Presence and Availability Management SCF“; Part 15: “Multi Media Messaging SCF“; Part 16: “Service Broker SCF“. The Mapping specification of the OSA APIs and network protocols (3GPP TR 29.998) is also structured as above. A mapping to netwo

31、rk protocols is however not applicable for all Parts, but the numbering 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-1 V9.0.0 (2010-01) 63GPP TS 29.198-04-1 version 9.0.0 Release 9 Table: Overview of the OSA API

32、s Part 1: Overview“. 2 3GPP TS 22.127: “Service Requirement for 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 ISO 4217 (1995): “Codes for the repre

33、sentation of currencies and funds “. 6 3GPP TS 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)“. 8 ITU-T Recommendation Q.1238-2 (2000): “Interface Recommendation for Intelli

34、gent Network Capability Set 3: SCF - SSF interface“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 29.198-1 1 apply. ETSI ETSI TS 129 198-4-1 V9.0.0 (2010-01) 83GPP TS 29.198-04-1 version 9.0.0 Release 9 3.2 Abbreviati

35、ons For the purposes of the present document, the abbreviations given in TS 29.198-1 1 apply. 4 Call Control SCF Four flavours of Call Control (CC) APIs have been included in 3GPP Release 7. These are Generic Call Control (GCC), Multi-Party Call Control (MPCC), Multi-Media Call Control (MMCC) and Co

36、nference Call Control (CCC). The GCC is the same API as was already present in the Release 99 specification (TS 29.198 v3.3.0). Multi-Party Call Contorl was introduced in the Release 4 specifications, and Multi-Media Call Control is introduced in Release 5. Conference Call Control was introduced in

37、Release 7. The joint work between 3GPP CT5, ETSI TISPAN and the Parlay CC Working group with collaboration from JAIN has been focussed on the MPCC and MMCC APIs. A number of improvements on CC functionality have been made and are reflected in these APIs. For this it was necessary to break the inheri

38、tance that previously existed between GCC and MPCC. The joint CC group has furthermore decided that the MPCC is to be considered as the future base CC family and the technical work will not be continued on GCC. Errors or technical flaws will of course be corrected. 4.1 Call Model Description The cal

39、l model used for the Call Control SCFs has the following objects. * a call object. A call is a relation between a number of parties. The call object relates to the entire call view from the application. E.g., the entire call will be released when a release is called on the call. Note that different

40、applications can have different views on the same physical call, e.g., one application for the originating side and another application for the terminating side. The applications will not be aware of each other, all communication between the applications will be by means of network signalling. The A

41、PI currently does not specify any feature interaction mechanisms. * a call leg object. The leg object represents a logical association between a call and an address. The relationship includes at least the signalling relation with the party. The relation with the address is only made when the leg is

42、routed. Before that the leg object is IDLE and not yet associated with the address. * an address. The address logically represents a party in the call. * a terminal. A terminal is the end-point of the signalling and/or media for a party. This object type is currently not addressed. The call object i

43、s used to establish a relation between a number of parties by creating a leg for each party within the call. Associated with the signalling relationship represented by the call leg, there may also be a bearer connection (e.g., in the traditional voice only networks) or a number (zero or more) of med

44、ia channels (in multi-media networks). A leg can be attached to the call or detached from the call. When the leg is attached, this means that media or bearer channels related to the legs are connected to the media or bearer channels of the other legs that are attached to the same call. I.e., only le

45、gs that are attached can speak to each other. A leg can have a number of states, depending on the signalling received from or sent to the party associated with the leg. Usually there is a limit to the number of legs that are in being routed (i.e., the connection is being established) or connected to

46、 the call (i.e., the connection is established). Also, there usually is a limit to the number of legs that can be simultaneously attached to the same call. Some networks distinguish between controlling and passive legs. By definition the call will be released when the controlling leg is released. Al

47、l other legs are called passive legs. There can be at most one controlling leg per call. However, there is currently no way the application can influence whether a Leg is controlling or not. There are two ways for an application to get the control of a call. The application can request to be notifie

48、d of calls that meet certain criteria. When a call occurs in the network that meets these criteria, the application is notified and can control the call. Some legs will already be associated with the call in this case. Another way is to create a new call from the application. ETSI ETSI TS 129 198-4-

49、1 V9.0.0 (2010-01) 93GPP TS 29.198-04-1 version 9.0.0 Release 9 4.2 Structure of Call Control SCF Documentation Each of the Call Control SCFs is specified under the following headings: The Sequence diagrams give the reader a practical idea of how each of the SCF is implemented. The Class relationships clause shows how each of the interfaces applicable to the SCF, relate to one another. The Interface specification clause describes in detail each of the interfaces shown within the Class diagram part. The State Transition Diagrams (STD) show trans