Open Service Access (OSA); Application Programming Interface (API); Part 4: Call Control SCF (Parlay 3)

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 )

Odprti dostop do storitve (OSA) – Vmesnik za aplikacijsko programiranje (API) – 4. del: Krmiljenje klica SCF

General Information

Status
Published
Publication Date
31-Dec-2004
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Jan-2005
Due Date
01-Jan-2005
Completion Date
01-Jan-2005

Buy Standard

Standardization document
ES 201 915-4 V1.4.1:2005
English language
197 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ES 201 915-4 V1.4.1:2005
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
SIST ES 201 915-4 V1.4.1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ES 201 915-4 V1.4.1:2005

---------------------- Page: 2 ----------------------

SIST ES 201 915-4 V1.4.1:2005

ETSI ES 201 915-4 V1.4.1 (2003-07)
ETSI Standard


Open Service Access (OSA);
Application Programming Interface (API);
Part 4: Call Control SCF
(Parlay 3)





---------------------- Page: 3 ----------------------

SIST ES 201 915-4 V1.4.1:2005
 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.: +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 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:
editor@etsi.org
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

---------------------- Page: 4 ----------------------

SIST ES 201 915-4 V1.4.1:2005
 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

---------------------- Page: 5 ----------------------

SIST ES 201 915-4 V1.4.1:2005
 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

---------------------- Page: 6 ----------------------

SIST ES 201 915-4 V1.4.1:2005
 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.
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.