ETSI ES 202 915-4-1-2006 Open Service Access (OSA) Application Programming Interface (API) Part 4 Call Control Sub-part 1 Call Control Common Definitions (Parlay 4) (V1 4 1 Include.pdf

1、 ETSI ES 202 915-4-1 V1.4.1 (2006-12)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 4: Call Control;Sub-part 1: Call Control Common Definitions(Parlay 4)floppy3 ETSI ETSI ES 202 915-4-1 V1.4.1 (2006-12) 2 Reference RES/TISPAN-01028-04-01-OSA Keywords API, IDL, O

2、SA, 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 docume

3、nt 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 writte

6、n permission. 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. TIPHONTMa

7、nd 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-1 V1.4.1 (2006-12) 3 Contents Intellectual Property Rights5 F

8、oreword.5 1 Scope 7 2 References 7 3 Definitions and abbreviations.7 3.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 5 The Service Interface Specifications9 5.1 I

9、nterface Specification Format .9 5.1.1 Interface Class 9 5.1.2 Method descriptions9 5.1.3 Parameter descriptions9 5.1.4 State Model.9 5.2 Base Interface.9 5.2.1 Interface Class IpInterface 9 5.3 Service Interfaces .10 5.3.1 Overview 10 5.4 Generic Service Interface .10 5.4.1 Interface Class IpServic

10、e 10 5.4.1.1 Method setCallback()10 5.4.1.2 Method setCallbackWithSessionID()11 6 Common Call Control Data Types.11 6.1 TpCallAlertingMechanism.11 6.2 TpCallBearerService 11 6.3 TpCallChargePlan 12 6.4 TpCallPartyToChargeAdditionalInfo.12 6.5 TpCallPartyToChargeType 12 6.6 TpCallChargeOrderCategory

11、.13 6.7 TpCallEndedReport13 6.8 TpCallError 13 6.9 TpCallAdditionalErrorInfo.13 6.10 TpCallErrorType 14 6.11 TpCallInfoReport .14 6.12 TpCallInfoType14 6.13 TpCallLoadControlMechanism15 6.14 TpCallLoadControlIntervalRate.15 6.15 TpCallLoadControlMechanismType15 6.16 TpCallMonitorMode 15 6.17 TpCallN

12、etworkAccessType .16 6.18 TpCallPartyCategory16 6.19 TpCallServiceCode 16 6.20 TpCallServiceCodeSet .16 6.21 TpCallServiceCodeType 17 6.22 TpCallSuperviseReport 17 6.23 TpCallSuperviseTreatment.17 6.24 TpCallTeleService18 6.25 TpCallTreatment 18 6.26 TpCallTreatmentType 18 6.27 TpCallAdditionalTreat

13、mentInfo.19 ETSI ETSI ES 202 915-4-1 V1.4.1 (2006-12) 4 6.28 TpMediaType .19 Annex A (normative): OMG IDL Description of Common Call Control Data Types.20 Annex B (informative): W3C WSDL Description of Common Call Control Data Types .21 Annex C (informative): Java API Description of the Call Control

14、 SCFs22 Annex D (informative): Contents of 3GPP OSA Rel-5 Call Control .23 Annex E (informative): Record of changes 24 E.1 Interfaces 24 E.1.1 New 24 E.1.2 Deprecated24 E.1.3 Removed.24 E.2 Methods25 E.2.1 New 25 E.2.2 Deprecated25 E.2.3 Modified.25 E.2.4 Removed.25 E.3 Data Definitions .26 E.3.1 Ne

15、w 26 E.3.2 Modified.26 E.3.3 Removed.26 E.4 Service Properties.27 E.4.1 New 27 E.4.2 Deprecated27 E.4.3 Modified.27 E.4.4 Removed.27 E.5 Exceptions 28 E.5.1 New 28 E.5.2 Modified.28 E.5.3 Removed.28 E.6 Others .28 History 29 ETSI ETSI ES 202 915-4-1 V1.4.1 (2006-12) 5 Intellectual Property Rights IP

16、Rs 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 Property Rights (IPRs); Essential, or p

17、otentially 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, including IPR searches, has been carri

18、ed 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 ETSI Standard (ES) has been produced by ETSI Technical Committee

19、 Telecommunications and Internet converged Services 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 202 9

20、15) 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 Common Definitions“; Sub-part 2: “Generic Call Control SCF“; Sub-part 3: “Multi-Party Call Control SCF“; Sub-part 4: “Multi-Media Ca

21、ll Control SCF“; Sub-part 5: “Conference Call Control 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 1

22、2: “Charging SCF“; Part 13: “Policy Management SCF“; Part 14: “Presence and Availability Management SCF“. ETSI ETSI ES 202 915-4-1 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 JAI

23、N Community (http:/ member companies. The present document forms part of the Parlay 4.3 set of specifications. The present document is equivalent to 3GPP TS 29.198-4-1 V5.8.0 (Release 5). ETSI ETSI ES 202 915-4-1 V1.4.1 (2006-12) 7 1 Scope The present document is part 4, sub-part 1 of the Stage 3 sp

24、ecification 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 document specifies t

25、he common definitions used by the Call Control Service Capability Features (SCF). 2 References The references listed in clause 2 of ES 202 915-1 contain provisions which, through reference in this text, constitute provisions of the present document. ETSI ES 202 915-1: “Open Service Access (OSA); App

26、lication 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 given in ES 202 915-1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined i

27、n ES 202 915-1 apply. 4 Call Control SCF Four flavours of call control APIs are specified in ES 202 915, Parlay 4. Three of these have been included in 3GPP Release 5. These are the Generic Call Control (GCC), the Multi-Party Call Control (MPCC) and the Multi-Media Call Control (MMCC). The generic c

28、all 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 is introduced in Release 5. All four have been included in ETSI ES 201 915, Parl

29、ay 3. The joint work between 3GPP CN5, ETSI SPAN 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 made and are reflected in these APIs. For t

30、his 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 family and the technical work will not be con

31、tinued on Generic Call control. Errors or technical flaws will of course be corrected. ETSI ETSI ES 202 915-4-1 V1.4.1 (2006-12) 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 relation between a number of parties. The

32、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 originating side and another application for

33、 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 object represents a logical association betwee

34、n 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 address logically represents a party in t

35、he 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 call. Associated with the signalling relat

36、ionship 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 the leg is attached, this means that medi

37、a 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 signalling received from or sent to the party ass

38、ociated 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 can be simultaneously attached to the same

39、 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 currently no way the application can influ

40、ence 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 application is notified and can control the c

41、all. 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 Sequence diagrams give the reader a practical i

42、dea 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 (S

43、TD) 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 show a detailed expansion of each of the data types

44、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 202 915-2. ETSI ETSI ES 202 915-4-1 V1.4.1 (2006-12) 9 4.3 General requirements on support of methods An implementation of on

45、e of the call control APIs which supports or implements a method described in one of the sub-parts of ES 202 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 method. Where a method is not supported by an im

46、plementation 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. 5 The Service Interfa

47、ce Specifications 5.1 Interface Specification Format This clause defines the interfaces, methods and parameters that form a part of the API specification. The Unified Modelling Language (UML) is used to specify the interface classes. The general format of an interface specification is described belo

48、w. 5.1.1 Interface Class This shows a UML interface class description of the methods supported by that interface, and the relevant parameters and types. The Service and Framework interfaces for enterprise-based client applications are denoted by classes with name Ip. The callback interfaces to the a

49、pplications are denoted by classes with name IpApp. For the interfaces between a Service and the Framework, the Service interfaces are typically denoted by classes with name IpSvc, while the Framework interfaces are denoted by classes with name IpFw. 5.1.2 Method descriptions Each method (API method “call“) is described. Both synchronous and asynchronous methods are used in the API. Asynchronous methods are identified by a Req suffix for a method request, and, if applicable, are served by asynchronous methods identifie