SIST ES 201 915-4 V1.4.1:2005

• Abstract:

  Maintenance update of ES 201 915-4 v.1.3.1. Updated document will also be known as Parlay 3.3. Only those parts requiring modification will be updated ( most parts require maintenance fixes )

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.01 - Telecommunication systems in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI ES 201 915-4 V1.4.1 (2003-07) - Open Service Access (OSA); Application Programming Interface (API); Part 4: Call Control SCF (Parlay 3)

SIST ES 201 915-4 V1.4.1:2005 is the Slovenian adoption of ETSI ES 201 915-4 Version 1.4.1, published by SIST. It specifies the Open Service Access (OSA) Application Programming Interface (API) for the Call Control Service Capability Feature (SCF), covering generic, multi-party, multi-media and conference call control for application developers and network service implementers. The document is part of the Parlay 3 line and is written for systems that expose network call functions through a standard interface.

What does SIST ES 201 915-4 V1.4.1:2005 specify?

SIST ES 201 915-4 V1.4.1:2005 specifies the Call Control SCF aspects of the OSA API. In practice, it defines how an application can be notified about call events, control calls and call legs, request call information, and work with media and conference handling through standard interface classes and data types.

The document is organized as a Stage 3 specification. It moves from the scope and references to definitions, then to the service descriptions for generic call control, multi-party call control, multi-media call control and conference call control, followed by common call control data types and the annexes.

Annex	What it covers
A (normative)	OMG IDL description of the Call Control SCF
B (informative)	Contents of 3GPP OSA R4 Call Control
C	Change tracking for interfaces, methods, data definitions, service properties, exceptions and other items

What are the key requirements of SIST ES 201 915-4 V1.4.1:2005?

Generic call control and basic API behavior

Clause 4 sets out the call model used by the API. A call is modeled as a relation between parties, and the generic call control service works with the call as a whole rather than exposing every leg and media channel. For a reader, that means the generic service is suited to basic call setup, control and monitoring, but not to detailed leg-by-leg media management.

Clause 4.2 requires that if an implementation supports a method, it shall implement the functionality for at least one valid set of parameter values. If a method is not supported, the implementation shall return P_METHOD_NOT_SUPPORTED. In practice, this gives a clear rule for interoperability testing: supported operations must work as described, and unsupported ones must fail in a predictable way.

Clause 5 defines the interface specification format using Unified Modelling Language (UML). It also establishes the base interface IpInterface and the generic service interface IpService. This matters because the document is written as an interface contract, not as a narrative description of call processing.

Generic Call Control Service

Clause 6 describes the Generic Call Control Service (GCCS), including its manager and application callback interfaces. The application first enables notifications, then receives call events through callbacks such as callEventNotify, callNotificationInterrupted, callOverloadEncountered and callOverloadCeased. In practice, the application uses these callbacks to discover network calls, react to overload or interruption, and keep its call state aligned with the network.

Clause 6 also defines the main call operations used in ordinary call handling, including release, deassignCall, setChargePlan, setAdviceOfCharge, getCallInfoReq, getMoreDialledDigitsReq and superviseCallReq. This means the service supports routing, charging, supervision and user interaction in the same call session.

Clause 6.5 and 6.6 add service properties and data definitions that affect how call control behaves. One example is P_CHARGEPLAN_MAPPING, which limits allowed charge plans, and the data types include monitor mode, load control, call event criteria and release cause. For implementers, these definitions are what turn high-level call control into concrete configuration, event filtering and reporting behavior.

MultiParty Call Control Service

Clause 7 extends call control with explicit leg management and multi-party calls. It adds interfaces such as IpMultiPartyCallControlManager, IpMultiPartyCall and IpCallLeg, and it supports creating calls, creating and routing call legs, releasing calls, detaching media and retrieving the set of call legs in a call. In practice, this is the part to use when the application must know and manage individual parties in the call.

Clause 7 also defines event request and notification handling for call legs. The event model includes call attempt, address collection, alerting, answer, redirect, service code and release events, and overlapping notification criteria can be refused with P_INVALID_CRITERIA. That matters when several application functions monitor the same call, because event subscriptions must be planned so they do not conflict.

Clause 7.4 and 7.6 define call states, service properties and data types for multi-party control. The document uses states for the manager, the call and the originating and terminating call legs, and it defines types such as TpCallEventType, TpReleaseCause and call-leg identifiers. For a test or integration team, these definitions are the basis for state-machine testing and for checking that notifications arrive in the expected order.

MultiMedia Call Control Service and Conference Call Control Service

Clause 8 extends multi-party call control with media stream handling through interfaces such as IpMultiMediaCallControlManager, IpMultiMediaCall, IpMultiMediaCallLeg and IpMultiMediaStream. The data types cover media stream direction, audio, video and data capabilities, and media stream events. In practice, this is the part to use when the application must work with media content, not only with call signaling.

Clause 9 extends multi-media call control to conference handling. It introduces subconferences, where only parties in the same subconference have a bearer or media connection to each other, and it defines conference policies, search criteria and resource reservation. For readers, that means the document covers not only conference setup but also how a conference is grouped and controlled during the call.

What terms does SIST ES 201 915-4 V1.4.1:2005 define?

• Open Service Access (OSA) - an architecture that lets application developers use network functionality through a standardized interface.
• Application Programming Interface (API) - the defined interface that applications use to call network services.
• Service Capability Feature (SCF) - the call-control service family specified here, including generic, multi-party, multi-media and conference control.
• Generic Call Control Service (GCCS) - the basic two-party call control service used for ordinary call routing and management.
• MultiParty Call Control Service (MPCCS) - the service that adds explicit call-leg management and multi-party calls.
• MultiMedia Call Control Service (MMCCS) - the service that extends multi-party control with media stream handling.
• Conference Call Control Service (CCCS) - the service that adds subconference control on top of multi-media call control.

Who uses SIST ES 201 915-4 V1.4.1:2005?

SIST ES 201 915-4 V1.4.1:2005 is used by telecom application developers, platform integrators, network engineers and system suppliers that implement OSA or Parlay call control. It is relevant where applications need to monitor calls, route calls, control charging, supervise call duration, or manage call legs and media streams.

It is also useful for quality and test teams validating interoperability between applications and network service interfaces. The document supports work on switched telephony networks, packet-based networks and Intelligent Network (IN) style services, and it names the CAMEL Service Environment in the service properties and data definitions.

What changed in SIST ES 201 915-4 V1.4.1:2005 from the previous edition?

SIST ES 201 915-4 V1.4.1:2005 is a maintenance update of ES 201 915-4 v1.3.1. The updated document is also known as Parlay 3.3. Only the parts requiring modification were updated, and most of the document received maintenance fixes.

Which standards are used with SIST ES 201 915-4 V1.4.1:2005?

Standard	What it contributes
ES 201 915-1	The overview part, including the references, definitions and abbreviations that apply to this part
ES 201 915-2	Common data definitions used when a referenced data type is not defined in this part
ES 201 915-5	Provides TpUIInfo, which is referenced in the common call control data types

Clause 2 states that the references in ES 201 915-1 apply as provisions for this part. Clause 10 also points to ES 201 915-2 for other common data definitions and to ES 201 915-5 for TpUIInfo.

What does the SIST ES 201 915-4 V1.4.1:2005 document contain?

The document contains UML-based interface specifications, method descriptions and parameter descriptions for the call control services. It includes sequence diagrams for call setup, barring, number translation, prepaid handling, multimedia barring and conference scenarios, so readers can see how the API is meant to be used in practice.

It also contains state transition diagrams for the generic and multi-party call control services, together with service properties and detailed data definitions for events, reports, load control, charging, supervision, media streams and conference policies. Annex A provides the OMG IDL representation, while Annex C records the changes by interface, method, data definition, service property and exception category.

SLOVENSKI STANDARD
01-januar-2005
Odprti dostop do storitve (OSA) – Vmesnik za aplikacijsko programiranje (API) – 4.
del: Krmiljenje klica SCF
Open Service Access (OSA); Application Programming Interface (API); Part 4: Call
Control SCF (Parlay 3)
Ta slovenski standard je istoveten z: ES 201 915-4 Version 1.4.1
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Open Service Access (OSA);
Application Programming Interface (API);
Part 4: Call Control SCF
(Parlay 3)
�
2 ETSI ES 201 915-4 V1.4.1 (2003-07)

Reference
RES/SPAN-120095-4
Keywords
API, OSA, IDL, UML
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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 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 documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
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 Telecommunications Standards Institute 2003.
© The Parlay Group 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 201 915-4 V1.4.1 (2003-07)
Contents
Intellectual Property Rights.9
Foreword.9
1 Scope.10
2 References.10
3 Definitions and abbreviations.10
3.1 Definitions.10
3.2 Abbreviations.10
4 Call Control SCF.10
4.1 Call Model Description .11
4.2 General requirements on support of methods.12
5 The Service Interface Specifications.12
5.1 Interface Specification Format .12
5.1.1 Interface Class.12
5.1.2 Method descriptions.12
5.1.3 Parameter descriptions.12
5.1.4 State Model.12
5.2 Base Interface.12
5.2.1 Interface Class IpInterface .12
5.3 Service Interfaces.13
5.3.1 Overview.13
5.4 Generic Service Interface .13
5.4.1 Interface Class IpService .13
6 Generic Call Control Service .14
6.1 Sequence Diagrams.14
6.1.1 Additional Callbacks.14
6.1.2 Alarm Call.16
6.1.3 Application Initiated Call.18
6.1.4 Call Barring 1 .20
6.1.5 Number Translation 1 .22
6.1.6 Number Translation 1 (with callbacks).24
6.1.7 Number Translation 2 .26
6.1.8 Number Translation 3 .28
6.1.9 Number Translation 4 .30
6.1.10 Number Translation 5 .32
6.1.11 Prepaid.33
6.1.12 Pre-Paid with Advice of Charge (AoC) .35
6.2 Class Diagrams.38
6.3 Generic Call Control Service Interface Classes.39
6.3.1 Interface Class IpCallControlManager .40
6.3.2 Interface Class IpAppCallControlManager .43
6.3.3 Interface Class IpCall.46
6.3.4 Interface Class IpAppCall.50
6.4 Generic Call Control Service State Transition Diagrams.54
6.4.1 State Transition Diagrams for IpCallControlManager.54
6.4.1.1 Active State.55
6.4.1.2 Notification terminated State .55
6.4.2 State Transition Diagrams for IpCall.56
6.4.2.1 Network Released State .56
6.4.2.2 Finished State.56
6.4.2.3 Application Released State.57
6.4.2.4 No Parties State.57
6.4.2.5 Active State.57
6.4.2.6 1 Party in Call State.57
ETSI
4 ETSI ES 201 915-4 V1.4.1 (2003-07)
6.4.2.7 2 Parties in Call State .57
6.4.2.8 Routing to Destination(s) State .58
6.5 Generic Call Control Service Properties .58
6.5.1 List of Service Properties.58
6.5.2 Service Property values for the CAMEL Service Environment.59
6.6 Generic Call Control Data Definitions .59
6.6.1 Generic Call Control Event Notification Data Definitions .60
6.6.1.1 TpCallEventName.60
6.6.1.2 TpCallNotificationType.60
6.6.1.3 TpCallEventCriteria.61
6.6.1.4 TpCallEventInfo.61
6.6.1.5 Generic Call Control Data Definitions.61
6.6.1.6 IpCall.61
6.6.1.7 IpCallRef.61
6.6.1.8 IpAppCall.61
6.6.1.9 IpAppCallRef.61
6.6.1.10 TpCallIdentifier.61
6.6.1.11 IpAppCallControlManager.62
6.6.1.12 IpAppCallControlManagerRef.62
6.6.1.13 IpCallControlManager.62
6.6.1.14 IpCallControlManagerRef.62
6.6.1.15 TpCallAppInfo.62
6.6.1.16 TpCallAppInfoType.63
6.6.1.17 TpCallAppInfoSet.63
6.6.1.18 TpCallEndedReport.63
6.6.1.19 TpCallFault.63
6.6.1.20 TpCallInfoReport.63
6.6.1.21 TpCallReleaseCause.64
6.6.1.22 TpCallReport.64
6.6.1.23 TpCallAdditionalReportInfo.65
6.6.1.24 TpCallReportRequest.65
6.6.1.25 TpCallAdditionalReportCriteria.65
6.6.1.26 TpCallReportRequestSet.66
6.6.1.27 TpCallReportType.66
6.6.1.28 TpCallTreatment.66
6.6.1.29 TpCallEventCriteriaResultSet.66
6.6.1.30 TpCallEventCriteriaResult.66
7 MultiParty Call Control Service.67
7.1 Sequence Diagrams.67
7.1.1 Application initiated call setup .67
7.1.2 Call Barring 2 .69
7.1.3 Call forwarding on Busy Service.70
7.1.4 Call Information Collect Service .71
7.1.5 Complex Card Service .74
7.1.6 Hotline Service.77
7.1.7 Use of the Redirected event .80
7.2 Class Diagrams.80
7.3 MultiParty Call Control Service Interface Classes.82
7.3.1 Interface Class IpMultiPartyCallControlManager .82
7.3.2 Interface Class IpAppMultiPartyCallControlManager .86
7.3.3 Interface Class IpMultiPartyCall .88
7.3.4 Interface Class IpAppMultiPartyCall.93
7.3.5 Interface Class IpCallLeg .95
7.3.6 Interface Class IpAppCallLeg.101
7.4 MultiParty Call Control Service State Transition Diagrams .106
7.4.1 State Transition Diagrams for IpMultiPartyCallControlManager.106
7.4.1.1 Active State.106
7.4.1.2 Interrupted State.106
7.4.1.3 Overview of allowed methods.106
7.4.2 State Transition Diagrams for IpMultiPartyCall.107
7.4.2.1 IDLE State.107
ETSI
5 ETSI ES 201 915-4 V1.4.1 (2003-07)
7.4.2.2 ACTIVE State.108
7.4.2.3 RELEASED State.108
7.4.2.4 Overview of allowed methods.108
7.4.3 State Transition Diagrams for IpCallLeg.108
7.4.3.1 Originating Call Leg .109
7.4.3.1.1 Initiating State.110
7.4.3.1.2 Analysing State.111
7.4.3.1.3 Active State.112
7.4.3.1.4 Releasing State.114
7.4.3.1.5 Overview of allowed methods, Originating Call Leg STD .116
7.4.3.2 Terminating Call Leg .117
7.4.3.2.1 Idle (terminating) State.117
7.4.3.2.2 Active (terminating) State .118
7.4.3.2.3 Releasing (terminating) State .121
7.4.3.2.4 Overview of allowed methods and trigger events, Terminating Call Leg STD.123
7.5 Multi-Party Call Control Service Properties .123
7.5.1 List of Service Properties.123
7.5.2 Service Property values for the CAMEL Service Environment.124
7.6 Multi-Party Call Control Data Definitions .125
7.6.1 Event Notification Data Definitions .125
7.6.2 Multi-Party Call Control Data Definitions.125
7.6.2.1 IpCallLeg.125
7.6.2.2 IpCallLegRef.125
7.6.2.3 IpAppCallLeg.125
7.6.2.4 IpAppCallLegRef.125
7.6.2.5 IpMultiPartyCall.125
7.6.2.6 IpMultiPartyCallRef.125
7.6.2.7 IpAppMultiPartyCall.125
7.6.2.8 IpAppMultiPartyCallRef.126
7.6.2.9 IpMultiPartyCallControlManager.126
7.6.2.10 IpMultiPartyCallControlManagerRef.126
7.6.2.11 IpAppMultiPartyCallControlManager.126
7.6.2.12 IpAppMultiPartyCallControlManagerRef.126
7.6.2.13 TpAppCallLegRefSet.126
7.6.2.14 TpMultiPartyCallIdentifier.126
7.6.2.15 TpAppMultiPartyCallBack.126
7.6.2.16 TpAppMultiPartyCallBackRefType.127
7.6.2.17 TpAppCallLegCallBack.127
7.6.2.18 TpMultiPartyCallIdentifierSet.127
7.6.2.19 TpCallAppInfo.127
7.6.2.20 TpCallAppInfoType.128
7.6.2.21 TpCallAppInfoSet.128
7.6.2.22 TpCallEventRequest.128
7.6.2.23 TpCallEventRequestSet.128
7.6.2.24 TpCallEventType.129
7.6.2.25 TpAdditionalCallEventCriteria.131
7.6.2.26 TpCallEventInfo.131
7.6.2.27 TpCallAdditionalEventInfo.132
7.6.2.28 TpCallNotificationRequest.132
7.6.2.29 TpCallNotificationScope.132
7.6.2.30 TpCallNotificationInfo.133
7.6.2.31 TpCallNotificationReportScope.133
7.6.2.32 TpNotificationRequested.133
7.6.2.33 TpNotificationRequestedSet.133
7.6.2.34 TpReleaseCause.133
7.6.2.35 TpReleaseCauseSet.133
7.6.2.36 TpCallLegIdentifier.134
7.6.2.37 TpCallLegIdentifierSet.134
7.6.2.38 TpCallLegAttachMechanism.134
7.6.2.39 TpCallLegConnectionProperties.134
7.6.2.40 TpCallLegInfoReport.134
7.6.2.41 TpCallLegInfoType.135
ETSI
6 ETSI ES 201 915-4 V1.4.1 (2003-07)
7.6.2.42 TpCallLegSuperviseTreatment.135
8 MultiMedia Call Control Service.135
8.1 Sequence Diagrams.135
8.1.1 Barring for media combined with call routing, alternative 1 .135
8.1.2 Barring for media combined with call routing, alternative 2 .137
8.1.3 Barring for media, simple .139
8.1.4 Call Volume charging supervision.140
8.2 Class Diagrams.142
8.3 MultiMedia Call Control Service Interface Classes .143
8.3.1 Interface Class IpMultiMediaCallControlManager .144
8.3.2 Interface Class IpAppMultiMediaCallControlManager .146
8.3.3 Interface Class IpMultiMediaCall.147
8.3.4 Interface Class IpAppMultiMediaCall.148
8.3.5 Interface Class IpMultiMediaCallLeg .149
8.3.6 Interface Class IpAppMultiMediaCallLeg.150
8.3.7 Interface Class IpMultiMediaStream.151
8.4 MultiMedia Call Control Service State Transition Diagrams .152
8.5 Multi-Media Call Control Data Definitions .152
8.5.1 Event Notification Data Definitions .152
8.5.1.1 TpMediaStreamRequestSet.152
8.5.1.2 TpMediaStreamRequest.152
8.5.1.3 TpMediaStreamDirection.153
8.5.1.4 TpMediaStreamDataTypeRequest.153
8.5.1.5 TpAudioCapabilitiesType.153
8.5.1.6 TpVideoCapabilitiesType.154
8.5.1.7 TpDataCapabilities.154
8.5.1.8 TpMediaStreamEventType.154
8.5.1.9 TpMediaStreamSet.154
8.5.1.10 TpMediaStream.154
8.5.1.11 TpMediaStreamDataType.154
8.5.2 Multi-Media Call Control Data Definitions.154
8.5.2.1 IpMultiMediaCall.154
8.5.2.2 IpMultiMediaCallRef.154
8.5.2.3 IpAppMultiMediaCall.155
8.5.2.4 IpAppMultiMediaCallRef.155
8.5.2.5 IpMultiMediaCallLeg.155
8.5.2.6 IpMultiMediaCallLegRef.155
8.5.2.7 IpAppMultiMediaCallLeg.155
8.5.2.8 IpAppMultiMediaCallLegRef.155
8.5.2.9 TpAppMultiMediaCallLegRefSet.155
8.5.2.10 TpMultiMediaCallIdentifier.155
8.5.2.11 TpMultiMediaCallIdentifierSet.155
8.5.2.12 TpMultiMediaCallLegIdentifier.155
8.5.2.13 TpMultiMediaCallLegIdentifierSet.155
8.5.2.14 IpAppMultiMediaCallControlManager.156
8.5.2.15 IpAppMultiMediaCallControlManagerRef.156
8.5.2.16 TpAppMultiMediaCallBack.156
8.5.2.17 TpAppMultiMediaCallBackRefType.156
8.5.2.18 TpAppMultiMediaCallLegCallBack.156
8.5.2.19 TpCallSuperviseVolume.157
8.5.2.20 TpNotificationMediaRequest.157
8.5.2.21 TpMediaNotificationRequested.157
8.5.2.22 TpMediaNotificationsRequestedSet.157
9 Conference Call Control Service.157
9.1 Sequence Diagrams.157
9.1.1 Meet-me conference without subconferencing .157
9.1.2 Non-add hoc add-on with subconferencing .159
9.1.3 Non-addhoc add-on multimedia.161
9.1.4 Resource Reservation.164
9.2 Class Diagrams.165
ETSI
7 ETSI ES 201 915-4 V1.4.1 (2003-07)
9.3 Conference Call Control Service Interface Classes.166
9.3.1 Interface Class IpConfCallControlManager .167
9.3.2 Interface Class IpAppConfCallControlManager.170
9.3.3 Interface Class IpConfCall.171
9.3.4 Interface Class IpAppConfCall.172
9.3.5 Interface Class IpSubConfCall .174
9.3.6 Interface Class IpAppSubConfCall.177
9.4 Conference Call Control Service State Transition Diagrams .178
9.5 Conference Call Control Data Definitions .178
9.5.1 Event Notification Data Definitions .179
9.5.2 Conference Call Control Data Definitions.179
9.5.2.1 IpConfCall.179
9.5.2.2 IpConfCallRef.179
9.5.2.3 IpAppConfCall.179
9.5.2.4 IpAppConfCallRef.179
9.5.2.5 IpSubConfCall.179
9.5.2.6 IpSubConfCallRef.179
9.5.2.7 IpAppSubConfCall.179
9.5.2.8 IpAppSubConfCallRef.179
9.5.2.9 TpSubConfCallIdentifierSet.179
9.5.2.10 TpConfCallIdentifier.180
9.5.2.11 TpSubConfCallIdentifier.180
9.5.2.12 IpAppConfCallControlManager.180
9.5.2.13 IpAppConfCallControlManagerRef.180
9.5.2.14 TpConfPolicyType.180
9.5.2.15 TpConfPolicy.180
9.5.2.16 TpMonoMediaConfPolicy.181
9.5.2.17 TpJoinEventInfo.181
9.5.2.18 TpConfSearchCriteria.181
9.5.2.19 TpConfSearchResult.181
9.5.2.20 TpMultiMediaConfPolicy.182
9.5.2.21 TpResourceReservation.182
9.5.2.22 TpVideoHandlingType.182
10 Common Call Control Data Types.182
10.1 TpCallAlertingMechanism.
...