1、 ETSI ES 204 915-4-1 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 4: Call Control;Sub-part 1: Call Control Common Definitions(Parlay 6)floppy3 ETSI ETSI ES 204 915-4-1 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01032-4-01-OSA Keywords API, IDL, OS
2、A, 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 documen
3、t 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,
4、 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 status of this and other ETSI
5、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 except as authorized by written
6、 permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2008. The Parlay Group 2008. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
7、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 204 915-4-1 V1.1.1 (2008-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 7 2 References 7 3 Definitions and abbreviations.7 3
8、.1 Definitions7 3.2 Abbreviations .7 4 Call Control SCF7 4.1 Call Model Description 8 4.2 Structure of Call Control SCF Documentation.8 4.3 General requirements on support of methods.9 4.4 Application Control of a Call or Session9 4.4.1 Introduction.9 4.4.2 Concept of Multiple Points of Control9 4.4
9、.2.1 Cascaded Chain Model .9 4.4.3 Service Interactions.11 4.4.4 Multiple services - applicability of MPC for Parlay/OSA 11 5 The Service Interface Specifications11 5.1 Interface Specification Format .11 5.1.1 Interface Class 11 5.1.2 Method descriptions12 5.1.3 Parameter descriptions12 5.1.4 State
10、Model.12 5.2 Base Interface.12 5.2.1 Interface Class IpInterface 12 5.3 Service Interfaces .12 5.3.1 Overview 12 5.4 Generic Service Interface .13 5.4.1 Interface Class IpService 13 5.4.1.1 Method setCallback()13 5.4.1.2 Method setCallbackWithSessionID()13 6 Common Call Control Data Types.14 6.1 TpC
11、allAlertingMechanism.14 6.2 TpCallBearerService 14 6.3 TpCallChargePlan 14 6.4 TpCallPartyToChargeAdditionalInfo.15 6.5 TpCallPartyToChargeType 15 6.6 TpCallChargeOrderCategory .15 6.7 TpCallEndedReport15 6.8 TpCallError 15 6.9 TpCallAdditionalErrorInfo.16 6.10 TpCallErrorType 16 6.11 TpCallInfoRepo
12、rt .16 6.12 TpCallInfoType17 6.13 TpCallLoadControlMechanism17 6.14 TpCallLoadControlIntervalRate.17 6.15 TpCallLoadControlMechanismType17 6.16 TpCallMonitorMode 17 6.17 TpCallNetworkAccessType .18 6.18 TpCallPartyCategory18 6.19 TpCallServiceCode 18 6.20 TpCallServiceCodeSet .18 6.21 TpCallServiceC
13、odeType 19 ETSI ETSI ES 204 915-4-1 V1.1.1 (2008-05) 4 6.22 TpCallSuperviseReport 19 6.23 TpCallSuperviseTreatment.19 6.24 TpCallTeleService20 6.25 TpCallTreatment 20 6.26 TpCallTreatmentType 20 6.27 TpCallAdditionalTreatmentInfo.21 6.28 TpMediaType .21 Annex A (normative): OMG IDL Description of Co
14、mmon Call Control Data Types.22 Annex B (informative): W3C WSDL Description of Common Call Control Data Types .23 Annex C (informative): Java API Description of the Call Control SCFs24 Annex D (informative): Contents of 3GPP OSA Rel-7 Call Control .25 Annex E (informative): Description of Call Contr
15、ol Sub-part 1: Call Control Common Definitions for 3GPP2 cdma2000 networks.26 E.1 General Exceptions.26 E.2 Specific Exceptions26 E.2.1 Clause 1: Scope 26 E.2.2 Clause 2: References 26 E.2.3 Clause 3: Definitions and abbreviations.26 E.2.4 Clause 4: Call Control SCF 26 E.2.5 Clause 5: The Service In
16、terface Specifications 26 E.2.6 Clause 6: Common Call Control Data Types .26 E.2.7 Annex A (normative): OMG IDL Description of Common Call Control Data Types .27 E.2.8 Annex B (informative): W3C WSDL Description of Common Call Control Data Types .27 E.2.9 Annex C (informative): Java API Description
17、of the Call Control SCFs.27 Annex F (informative): Record of changes 28 F.1 Interfaces 28 F.1.1 New 28 F.1.2 Deprecated28 F.1.3 Removed.28 F.2 Methods28 F.2.1 New 28 F.2.2 Deprecated28 F.2.3 Modified.29 F.2.4 Removed.29 F.3 Data Definitions .29 F.3.1 New 29 F.3.2 Modified.29 F.3.3 Removed.29 F.4 Ser
18、vice Properties.29 F.4.1 New 29 F.4.2 Deprecated29 F.4.3 Modified.30 F.4.4 Removed.30 F.5 Exceptions 30 F.5.1 New 30 F.5.2 Modified.30 F.5.3 Removed.30 F.6 Others .30 History 31 ETSI ETSI ES 204 915-4-1 V1.1.1 (2008-05) 5 Intellectual Property Rights IPRs essential or potentially essential to the pr
19、esent 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 Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
20、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, including IPR searches, has been carried out by ETSI. No guarantee can be given as to
21、 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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Serv
22、ices and Protocols for Advanced Networking (TISPAN). The present document is part 4, sub-part 1 of a multi-part deliverable covering Open Service Access (OSA); Application Programming Interface (API), as identified below. The API specification (ES 204 915) is structured in the following parts: Part
23、1: “Overview“; 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 C
24、ontrol SCF“; 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“; Part 10: “Connectivity Manager SCF“; Part 11: “Account Management SCF“; Part 12: “Charging SCF“; Part 13: “Policy Management
25、SCF“; Part 14: “Presence and Availability Management SCF“; Part 15: “Multi-Media Messaging SCF“ Part 16: “Service Broker SCF“. ETSI ETSI ES 204 915-4-1 V1.1.1 (2008-05) 6 The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP, in co-operation
26、 with a number of JAIN Community (http:/ member companies. The present document forms part of the Parlay 6.0 set of specifications. The present document is equivalent to 3GPP TS 29.198-4-1 V7.0.0 (Release 7). ETSI ETSI ES 204 915-4-1 V1.1.1 (2008-05) 7 1 Scope The present document is part 4, sub-par
27、t 1 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA). 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
28、 document specifies the common definitions used by the Call Control Service Capability Features (SCF). 2 References The references listed in clause 2 of ES 204 915-1 contain provisions which, through reference in this text, constitute provisions of the present document. ETSI ES 204 915-1: “Open Serv
29、ice Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 6)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 204 915-1 apply. 3.2 Abbreviations For the purposes of the present document, the ab
30、breviations given in ES 204 915-1 apply. 4 Call Control SCF Four flavours of call control APIs are specified in ES 204 915, Parlay 6. Three of these have been included in 3GPP Release 6. These are the Generic Call Control (GCC), the Multi-Party Call Control (MPCC) and the Multi-Media Call Control (M
31、MCC). The generic call control is the same API as was already present in the previous specification for 3GPP Release 99 (TS 129 198 V3). Multi-Party Call Control was introduced in the Release 4 specifications, and Multi-Media Call Control was introduced in Release 5. All four have been included in E
32、S 201 915, Parlay 3 and ES 202 915, Parlay 4. The joint work between 3GPP CN5, ETSI TISPAN and the Parlay Call Control Working group with collaboration from JAIN has been focussed on the Multi-party and Multi-Media call control APIs. A number of improvements on call control functionality have been m
33、ade and are reflected in these APIs. For this it was necessary to break the inheritance that previously existed between Generic and Multi-party call control. The joint call control group has furthermore decided that the multi-party call control is to be considered as the future base call control fam
34、ily and the technical work will not be continued on Generic Call control. Errors or technical flaws will of course be corrected. ETSI ETSI ES 204 915-4-1 V1.1.1 (2008-05) 8 4.1 Call Model Description The call model used for the Call Control SCFs has the following objects: A call object. A call is a
35、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 applications can have different views on the same physical call, e.g. one application for the or
36、iginating 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 API currently does not specify any feature interaction mechanisms. A call leg object. The leg obje
37、ct 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 routed. Before that the leg object is IDLE and not yet associated with the address. An address. The
38、 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 is used to establish a relation between a number of parties by creating a leg for each party within the
39、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 media channels (in multi-media networks). A leg can be attached to the call or detached from the call. When
40、 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 legs that are attached can speak to each other. A leg can have a number of states, depending on the signall
41、ing 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 the call (i.e. the connection is established). Also, there usually is a limit to the number of legs that
42、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. All other legs are called passive legs. There can be at most one controlling leg per call. However, there is
43、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 notified of calls that meet certain criteria. When a call occurs in the network that meets these criteria, the app
44、lication 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. 4.2 Structure of Call Control SCF Documentation Each of the Call Control SCFs is specified under the following headings: The Seque
45、nce 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 diag
46、ram part. The State Transition Diagrams (STD) show transition between states in the SCF. The states and transitions are well-defined; either methods specified in the Interface specification or events occurring in the underlying networks cause state transitions. The Data definitions clause shows a de
47、tailed expansion of each of the data types associated with the methods within the classes. Note that some data types are used in other methods and classes and are therefore defined within the Common Data types part ES 204 915-2. ETSI ETSI ES 204 915-4-1 V1.1.1 (2008-05) 9 4.3 General requirements on
48、 support of methods An implementation of one of the call control APIs which supports or implements a method described in one of the sub-parts of ES 204 915-4, shall support or implement the functionality described for that method, for at least one valid set of values for the parameters of that metho
49、d. Where a method is not supported by an implementation of a Service interface, the exception P_METHOD_NOT_SUPPORTED shall be returned to any call of that method. Where a method is not supported by an implementation of an Application interface, a call to that method shall be possible, and no exception shall be returned. 4.4 Application Control of a Call or Session 4.4.1 Introduction Services should be provision-able by multiple independent parties and therefore multiple applications may apply control to the same instance
