european ets 300 102-2 telecommunication · pdf fileets 300 102-2: december 1990 whilst ......
TRANSCRIPT
New
pre
sent
atio
n -
see
His
tory
box
EUROPEAN ETS 300 102-2
TELECOMMUNICATION December 1990
STANDARD
Source: ETSI TC-SPS Reference: T/S 46-31(CB)
ICS: 33.080
Key words: ISDN, layer 3, basic call control
Integrated Services Digital Network (ISDN);User network interface layer 3
Specifications for basic call controlSpecification Description Language (SDL) diagrams
ETSIEuropean Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [email protected]
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1990. All rights reserved.
Page 2ETS 300 102-2: December 1990
Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Standards Approval Dept." at the address shown on the title page.
Page 3ETS 300 102-2: December 1990
Contents
Foreword .......................................................................................................................................................5
1 Scope ..................................................................................................................................................7
2 Normative references..........................................................................................................................7
3 Explanation of symbols .......................................................................................................................7
4 User side and network side call states................................................................................................9
5 Network side SDLs - Overview..........................................................................................................105.1 Network side call states .....................................................................................................105.2 Network side SDLs - Block diagram ..................................................................................115.3 Network side SDLs - List of primitives ...............................................................................115.4 Network side SDL diagrams - Representation method .....................................................12
6 User side SDLs - Overview ...............................................................................................................156.1 User side call states...........................................................................................................156.2 User side SDLs - Block diagram........................................................................................166.3 User side SDLs - List of primitives.....................................................................................16
7 Graphical SDL diagrams ...................................................................................................................177.1 Network side SDL diagrams ..............................................................................................187.2 User side SDL diagrams....................................................................................................52
History..........................................................................................................................................................74
Page 4ETS 300 102-2: December 1990
Blank page
Page 5ETS 300 102-2: December 1990
Foreword
This European Telecommunications Standard (ETS) was produced by the Signalling, Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI),and was adopted, having passed through the ETSI standards approval procedure.
This document is part 2 of a multi-part ETS, comprised as follows:
ETS 300 102-1: ISDN; User-network interface layer 3; Specifications for basic call control.
ETS 300 102-2: ISDN; User-network interface layer 3; Specifications for basic call control;Specification Description Language (SDL) diagrams.
Page 6ETS 300 102-2: December 1990
Blank page
Page 7ETS 300 102-2: December 1990
1 Scope
This ETS specifies, using SDL representation, the circuit-switched call control procedures of the DigitalSubscriber Signalling one (DSS1) as specified in clause 5 of ETS 300 102-1 [1].
In order to describe the point-to-multipoint operation of the protocol, the concept of a "global" processrunning in parallel with a number of "individual" (dynamic) processes in the network side has beenintroduced. This approach, and the associated definition of internal primitives is intended to provide acoherent description of the protocol and does not constrain implementations. The text description inclause 5 of ETS 300 102-1 [1] is definitive.
2 Normative references
This ETS incorporates by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications listed hereafter.For dated references, subsequent amendments to, or revisions of any of these publications apply to thisETS only when incorporated in it by amendment or revision. For undated references the latest edition ofthe publication referred to applies.
[1] ETS 300 102-1 (1990): "ISDN User-network interface layer 3; Specification forbasic call control".
[2] CCITT Recommendation Z.100 (1988): "Functional Specification andDescription Language (SDL)".
[3] CCITT Recommendation Q.931 (1988): "ISDN User-network interface layer 3Specification for basic call control".
3 Explanation of symbols
The symbols and abbreviations shown below are used within this description. A full description of thesymbols and their meaning and application is given in CCITT Recommendation Z.100 [2].
State symbol
Input symbol (event occurrence)
Output symbol (signal generation - which will lead to an associated eventoccurrence)
Save symbol (save event until compilation of a transition)
Task symbol
Decision symbol
Procedure call symbol
Transition option symbol (implementation option)
Page 8ETS 300 102-2: December 1990
Procedure start symbol
Procedure return symbol
Create request symbol (used to initiate an individual network side transaction)
Stop symbol (used to end an individual network side transaction)
Connection symbol
Used to mark an input or output which is local to the Layer 3 entity and which isrequired as a result of the representation approach adopted.
Page 9ETS 300 102-2: December 1990
4 User side and network side call states
This section shows which call states are applicable at the user and network sides during the variousphases of a call.
Table 1: Call states
Call phase Call state User Network
IDLE Null U0 N0
OUTGOING CALL
(from user)
Call initiated
Overlap Sending
Outgoing Call Proceeding
Call Delivered
U1
U2
U3
U4
N1
N2
N3
N4
INCOMING CALL
(to user)
Call Present
Overlap Receiving
Incoming Call Proceeding
Call Received
Connect Request
U6
U25
U9
U7
U8
N6
N25
N9
U7
N8
ACTIVE Active U10 N10
CALL CLEARING Disconnect Request
(clearing by the user)
Disconnect Indication
(clearing by the network)
Release Request
Call Abort
U11
U12
U19
---
N11
N12
N19
N22
RESTART PROCEDURE
(see NOTE)
Null
Restart
Resume Request
REST0
REST1
U17
REST0
REST1
N17
NOTE: These states relate to global call references and are applicable when the restartprocedures are used. They may exist in both user and network side.
Page 10ETS 300 102-2: December 1990
5 Network side SDLs - Overview
5.1 Network side call states
Table 2
Number Name
N0 Null
N1 Call Initiated
N2 Overlap Sending
N3 Outgoing Call Proceeding
N4 Call Delivered
N6 Call Present
N7 Call Received
N8 Connect Request
N9 Incoming Call Proceeding
N10 Active
N11 Disconnect Request
N12 Disconnect Indication
N15 Suspend Request
N17 Resume Request
N19 Release Request
N22 Call Abort
N25 Overlap Receiving
NOTE 1: Network side timers, and the states in which they run, are specified inClause 9 of ETS 300 102-1 [1].
NOTE 2: Events in each state which lead to normal call establishment and clearingare marked with the "+" symbol.
NOTE 3: The primitives which pass to and from the call control block are shown forguidance only and are not fully specified.
NOTE 4: Internal primitives are marked by "*". These are a result of therepresentation method that has been adopted.
Page 11ETS 300 102-2: December 1990
5.2 Network side SDLs - Block diagram
Call control Resource management
Procedurecall
Q.931 Protocol Control
Messages to/fromUser side
Data link layer
Physical layer
User-networkinterface
User
Blockdescribedby the SDLdiagrams
Primit ives
*
* not described inthe SDL diagrams
NOTE: Control of B-channels is described in these SDL diagrams as part of the CCITTRecommendation Q.931 [3] protocol block.
Figure 1
5.3 Network side SDLs - List of primitives
Table 3
From Call Control Block To Call Control Block
ALERTING REQUESTDISCONNECT REQUESTINFO REQUESTMORE INFO REQUESTNOTIFY REQUESTPROCEEDING REQUESTPROGRESS REQUESTREJECT REQUESTRELEASE REQUESTRESUME REJECT REQUESTRESUME RESPONSESETUP COMPLETE REQUESTSETUP REQUESTSETUP RESPONSESTATUS ENQUIRY REQUESTSUSPEND REJECT REQUESTSUSPEND RESPONSE
ALERTING INDICATIONDISCONNECT INDICATIONINFO INDICATIONMORE INFO INDICATIONNOTIFY INDICATIONPROCEEDING INDICATIONPROGRESS INDICATIONREJECT INDICATIONRELEASE CONFIRMRELEASE INDICATIONRESUME INDICATIONSETUP CONFIRMSETUP INDICATIONSTATUS INDICATIONSUSPEND INDICATIONTIMEOUT INDICATION
Page 12ETS 300 102-2: December 1990
5.4 Network side SDL diagrams - Representation method
In order to describe the point-to-multipoint operation of the protocol, the concept of a "global" processrunning in parallel with a number of "individual" (dynamic) processes in the network side has beenintroduced. This approach, and the associated definition of internal primitives, is intended to provide acoherent description of the protocol and does not constrain implementations. The text description inclause 5 of ETS 300 102-1 [1] is definitive.
Individual processes are used to track the responses of each terminal. The global (controlling) processruns in parallel with the (dynamically created/destroyed) individual process.
The global and individual processes communicate by means of internal primitives. These are related tolayer 3 message types and are defined in Table 4. The internal primitives represent instantaneous actions.Thus there is no possibility of errors caused by the cross-over of primitives.
The global process maintains a list of recorded Connection Endpoint Suffix (CES) values to enable it tomanage the individual processes. In this representation the global process also keeps a record of thestate of the individual process associated with each responding terminal. Additionally a "preselected" CESis recorded when one terminal responds with a CONNECT message and this becomes the "selected"CES when the terminal is awarded the call.
This solution is compatible with point-to-point working. In this case the global process never creates anyindividual processes.
Individual processes may exist in the following states:
N0 Null (processes are created in this state)N7 Call ReceivedN8 Connect RequestN9 Incoming Call ProceedingN19 Release RequestN25 Overlap Receiving
Two sets of SDLs are required for these states to show the global and individual processes.
The global process handles all communications with call control. Messages from individual terminals aresent to the individual process for that terminal if one exists (i.e. if the CES is recognised). Messages withan unrecognised CES are passed to the global process. Messages with the selected CES are also sent tothe global process.
Page 13ETS 300 102-2: December 1990
Table 4: Network side layer 3 internal primitives
PRIMITIVES NAME FROM TO MEANING
INT.ALERTING REQ
INT.CONNECT REQ
INT.CALL PROC REQ
INT.SETUP ACK REQ
Global Individual When global process receives ALERTING itstarts an individual process and sends itINT.ALERTING REQ etc
INT.ALERTING IND
INT.CONNECT IND
INT.CALL PROC IND
Individual Global Sent on receipt of ALERTING (etc).
END PROCESS Global Individual Sent when the global process terminates anindividual process
INT.RELEASE REQ Global Individual Instructs individual process to release terminal(e.g., for releasing non-selected terminals)
INT.RELEASE IND Individual Global Informal global process that a terminal hasbegun to release
INT.INFO REQ Global Individual Sent on receipt of INFO REQ
INT.INFO IND Individual Global Sent on receipt of INFO
INT.PROGRESS IND Individual Global Sent on receipt of PROGRESS
INT.REL.COMP.IND Individual Global Sent to indicate that the individual has cleared
NOTE: The global process should not release the call reference until all individual processeshave completed clearing.
Figure 2 (arrow diagram) shows an example of this representation method
Page 14ETS 300 102-2: December 1990
Ter
min
al 1
Ter
min
al 2
Term
inal
3N
etw
ork
SE
TUP
(B
RO
AD
CA
ST
)0
SE
TU
P R
EQ
ALE
RT
ING
t303
ALE
RT
ING
IND
INT.
ALE
RTI
NG
RE
Q0
7iA
LER
TIN
G
ALE
RT
ING
INT
. ALE
RT
ING
RE
Q
7i
0
INT
. ALE
RT
ING
RE
Q
7i
0
INT
. CO
NN
EC
T IN
DC
ON
NE
CT
X
EN
D P
RO
CE
SS
8i
RE
LEA
SE
INT
. RE
LEA
SE
RE
Q
RE
LEA
SE
RE
LEA
SE
CO
MP
LETE
INT
. RE
LEA
SE
RE
Q19
it3
08
6
t312
CO
NN
EC
T IN
D
10
t312
exp
ires
(no
stat
e ch
ange
)19
it3
08IN
T. R
EL.
CO
MP
. IN
D
RE
LEA
SE
CO
MP
LET
EIN
T. R
EL.
CO
MP
. IN
D
CO
NN
EC
T A
CK
CO
NN
EC
T A
CK
RE
Q
7
X
X
Fig
ure
2: M
ultip
oint
cal
l est
ablis
hmen
t (an
d cl
earin
g of
non
-sel
ecte
d te
rmin
als)
8
NO
TE
: 0
= cr
eatio
n of
sta
te m
achi
ne, x
= d
elet
ion
of s
tate
mac
hine
, num
bers
indi
cate
sta
tes
of th
e st
ate
mac
hine
s sh
own.
Page 15ETS 300 102-2: December 1990
6 User side SDLs - Overview
6.1 User side call states
Table 5
Number Name
U0 Null
U1 Call Initiated
U2 Overlap Sending
U3 Outgoing Call Proceeding
U4 Call Delivered
U6 Call Present
U7 Call Received
U8 Connect Request
U9 Incoming Call Proceeding
U10 Active
U11 Disconnect Request
U12 Disconnect Indication
U15 Suspend Request
U17 Resume Request
U19 Release Request
U25 Overlap Receiving
NOTE 1: User side timers, and the states in which they run, are specified in Clause9 of ETS 300 102-1 [1].
NOTE 2: Events in each state which lead to normal call establishment/clearing areshown with the "+" symbol.
NOTE 3: Primitives passed to and from the call control (user application) block areshown for guidance only and are not fully specified.
Page 16ETS 300 102-2: December 1990
6.2 User side SDLs - Block diagram
Call control Resource management
Procedurecall
Q.931 Protocol Control
Messages to/fromUser side
Data link layer
Physical layer
User-networkinterface
Netw ork
Blockdescribedby the SDLdiagrams
Primit ives
*
* not described inthe SDL diagrams
NOTE: Control of B-channels is described in these SDL diagrams as part of the Q.931 [3]protocol block.
Figure 3
6.3 User side SDLs - List of primitives
Table 6
From Call Control Block To Call Control Block
ALERTING REQUESTDISCONNECT REQUESTINFO REQUESTMORE INFO REQUESTNOTIFY REQUESTPROCEEDING REQUESTPROGRESS REQUESTREJECT REQUESTRELEASE REQUESTRESUME REQUESTSETUP REQUESTSETUP RESPONSESTATUS ENQUIRY REQUESTSUSPEND REQUEST
ALERTING INDICATIONDISCONNECT INDICATIONERROR INDICATIONINFO INDICATIONMORE INFO INDICATIONNOTIFY INDICATIONPROCEEDING INDICATIONPROGRESS INDICATIONREJECT INDICATIONRELEASE CONFIRMRELEASE INDICATIONRESUME CONFIRMSETUP COMPLETE INDICATIONSETUP CONFIRMSETUP INDICATIONSTATUS INDICATIONSUSPEND CONFIRM
Page 17ETS 300 102-2: December 1990
7 Graphical SDL diagrams
This clause is separated into two parts:
7.1 Network side SDL diagrams (figures 4 - 40);
7.2 User side SDL diagrams (figures 41 - 62).
Figures 60 to 62, of subclause 7.2, show detailed SDL diagrams for the global call reference to be appliedto both user and network sides. Although these are drawn as user side only, the same diagrams can beapplied to the network side by changing the direction of the input and output symbols.
All references in the following diagrams are to ETS 300 102-1 [1].
Page 18ETS 300 102-2: December 1990
7.1 Network side SDL diagrams
0NULL
SETUP
ESTABLISH CR
CHNLSELECTIONSUCCESS
?
SETUPINDICATION
1
RESUME RELEASE STATUS OTHERMESSAGE
RELEASECOMPLETE
ESTABLISHCR
ESTABLISHCR
CS=0?
0
RESUMEINDICATION
RELEASECOMPLETE
17 RELEASECR
0
ESTABLISHCR
RELEASE
STARTT308
19
RELEASECOMPLETE
RELEASECR
0
0
NOTIFYREQUEST
SETUPREQUEST
INT REL *COMP
INDICATION(CES)
DELETECES
0
0RELEASE
INDICATIONSELECT
CR
CHNLSELECTIONSUCCESS
?
0 STARTT303
P-PSETUP
REQUEST?
SETUP(P-P)
6
STARTT312
SETUP(B/CAST)
6
NOTE 1.
NOTE 2.
NOTE 3.
THE USE OF THE CALL REARRANGEMENT PROCEDURE ISRESTRICTED TO BASIC ACCESS i.e. IT WILL NOT BEAVAILABLE FOR PRIMARY RATE ACCESS
THE EXPIRY OF T307 IS NOTSHOWN IN THESE SDL's AS ITRUNS IN THE CALL CONTROL BLOCK.
THIS INPUT MAY BE RECEIVEDFROM A TERMINAL COMPLETING CLEARINGIN A MULTIPOINT CONFIGURATION.THE CALL REFERENCE SHOULD NOT BE RE-USEDUNTIL ALL TERMINALS HAVE COMPLETEDCLEARING.
5.1.1 5.6.4 5.8.11 5.8.3 5.8.4
5.2.1
5.8.3.2(b)
+
NOTE 1
N
Y
+
NOTE 3
Y
N
Y
N
Y
N
+
Figure 4: Network Side SDL Diagram
Page 19ETS 300 102-2: December 1990
0INULL
INT *ALERTINGREQUEST
7I
INT *SETUP ACKREQUEST
INT *CONNECTREQUEST
STARTT304 8I
25I
INDIVIDUAL TERMINALINDIVIDUAL PROCESSESARE CREATED INTHIS STATE
IMPLEMENTATION OF TIMER T310 ININDIVIDUAL PROCESSES IS OPTIONAL.
NOTE 1.
INT *CALL PROCREQUEST
STARTT310
25I
INT *SETUP ACKREQUEST
STARTT304
19I
RELEASE
NOTE 1
Figure 5: Network side SDL diagram
+ +
1CALL
INITIATED
MOREINFO
REQUEST
STARTT302
SETUP ACK(B-CHNL)
CONNECTB-CHNL
ANYDIGITS
RECEIVED?
PROCEEDINGREQUEST
REJECTREQUEST
RELEASECOMPLETE DISCONNECT RELEASE
CALLPROCEEDING
(B-CHNL)
RELEASECOMPLETE
RELEASEB-CHANNEL IF
NOT RELEASED
DISCONNECTB-CHANNEL IFCONNECTED
RELEASEINDICATION
RELEASEINDICATION
DISCONNECTINDICATION
CONNECTB-CHNL
RELEASEB-CHANNEL
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASECALL REF
RELEASECR3 11 RELEASE
COMPLETE
0 0 RELEASECR
0
TONEOPTION
?
CONNECTDIAL
TONE
2
2
5.1.3 5.1.5.1 5.3.2a 5.8.4 5.3.3 5.8.4
Y
N
Y
N
Figure 6: Network side SDL diagram
Page 20ETS 300 102-2: December 1990
5
2OVERLAPSENDING
INFOREQUEST
INFO
2
INFO SETUPRESPONSE
RELEASECOMPLETE
PROCEEDINGREQUEST
ALERTINGREQUEST
PROGRESSREQUEST
RELEASEREQUEST
STOPT302
STOPT302
STOPT302
STOPT302
STOPT302
STOPT302PROGRESS
RELEASEALERTINGCALLPROCEEDINGCONNECT
RELEASEB-CHANNEL IF
NOT RELEASED2
RELEASEB-CHANNEL IF
NOT RELEASED
STARTT308
19
4310 RELEASEINDICATION
RELEASECR
0
FIRSTINFO
MESSAGE?
STOP ANYAPPLIED
DIAL TONE
STARTT302
INFOINDICATION
2
TIMEOUTT302 DISCONNECT RELEASE DISCONNECT
REQUEST
ISCALL INFODEFINITELY
INCOMPLETE?
TIMEOUTINDICATION
CALLPROCEEDING
3
TONEOPTION
?
DISCONNECTB-CHANNEL IFCONNECTED
DISCONNECT(PI)
STARTTONE
STARTT306
DISCONNECT
STARTT305
12
STOPT302
STOPT302
STOPT302
DISCONNECTB-CHANNEL IFCONNECTED
RELEASEINDICATION TONE
OPTION?
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASECOMPLETE
RELEASECR
0
DISCONNECTB-CHANNEL IFCONNECTED
DISCONNECT
STARTT305
12
DISCONNECTINDICATION
11 DISCONNECT(PI)
STARTTONE
STARTT306
5.1.3 5.1.8 5.8.4 5.1.5.2 5.1.7 5.1.6
5.1.5.2 5.3.3 5.8.4 5.3.4
Y
+ + + +
N
Y
N
Y
N
Y
N
Figure 7: Network side SDL diagram
Page 21ETS 300 102-2: December 1990
5
3OUTGOING CALL
PROCEEDING
INFO INFOREQUEST
INFOINDICATION
3 3 4 10
INFO ALERTING CONNECT
ALERTINGREQUEST
SETUPRESPONSE DISCONNECT RELEASE
DISCONNECTB-CHANNEL IFCONNECTED
DISCONNECTINDICATION
11
RELEASEINDICATION
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASECOMPLETE
RELEASECR
0
DISCONNECTREQUEST
RELEASEREQUEST
RELEASECOMPLETE
RELEASEB-CHANNEL IF
NOT RELEASEDRELEASE
PROGRESSREQUEST
RELEASEINDICATION
RELEASECR
0
RELEASEB-CHANNEL IF
NOT RELEASED
STARTT308
19
TONEOPTION
?
DISCONNECTB-CHANNEL IFCONNECTED
DISCONNECT
STARTT306
DISCONNECT(PI)
STARTTONE
STARTT306
12
PROGRESS
3
5 5.1.7 5.1.8 5.3.3 5.8.4
5.3.45.8.4
+
5.1.6
+
N
Y
Figure 8: Network side SDL diagram
Page 22ETS 300 102-2: December 1990
+
4CALL
DELIVERED
PROGRESSREQUEST
PROGRESS
4 4 4 10
INFOINDICATION INFO CONNECT
INFO INFOREQUEST
RELEASECOMPLETE
RELEASEB-CHANNEL IF
NOT RELEASED
DISCONNECTB-CHANNEL IFCONNECTED
RELEASEINDICATION
DISCONNECTINDICATION
DISCONNECT
RELEASECR 11
0
RELEASEREQUEST
DISCONNECTREQUESTRELEASE
RELEASEINDICATION RELEASE
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASEB-CHANNEL IF
NOT RELEASED
STARTT308
19
RELEASECOMPLETE
RELEASECR
0
TONEOPTION
?
DISCONNECTB-CHANNEL IFCONNECTED
DISCONNECT
STARTT305
12
STARTT306
STARTTONE
DISCONNECT(PI)
5.1.6 5 5 5.1.8 5.8.4 5.3.3
5.8.4 5.3.4
SETUPRESPONSE
N
Y
Figure 9: Network side SDL diagram
Page 23ETS 300 102-2: December 1990
6CALL
PRESENT
RELEASECOMPLETE
WASSETUP
B/CAST ?
STOPT303
RELEASEINDICATION
RELEASEB-CHNL IF
NECESSARY
RELEASECR
0
SAVECAUSE
6
RELEASECOMP
6
WASSETUP
B/CAST ?
RELEASE
STOPT303
RELEASEINDICATION
RELEASECOMP
RELEASEB-CHNL IF
NECESSARY
RELEASECR
0
TIMEOUTT303
FIRSTTIMEOUT
?
WASSETUP
B/CAST ?
SETUP(P-P)
STARTT303
6
RELCOMP
RCVD ?
SETUPB/CAST
STARTT303
RESTARTT312
6
RELEASEB-CHNL IF
NECESSARY
WASSETUP
B/CAST ?
DISCONNECTINDICATION
DISCONNECT
STARTT306
12
RELEASEINDICATION
22
INT *REL COMPINDICATION
(CES)
DISCONNECTREQUEST
STOPT303
STOPT303
RELEASEREQUEST
WASSETUP
B/CAST ?
RELEASE
STARTT308
RELEASEB-CHNL IF
NECESSARY
RELEASEINDICATION
22
19
WASSETUP
B/CAST ?
TONEOPTION
?
DISCONNECTB-CHANNEL IFCONNECTED
DISCONNECT(PI)
DISCONNECT
STARTT305
STARTTONE
STARTT306
12
DELETECES
6
NOTE 1.
NOTE 2.
REF. 5.2.5.4
THIS PRIMITIVE MAY BERECEIVED WHEN A TERMINALIS CLEARED DUE TO AN INVALIDCHNL ID IN RESPONSE TOTHE SETUP.
5.2.2 5.8.4 5.2.1
5.3.4
CONTD.
N Y
N
Y
Y
N
Y
N
N
Y
N
NOTE 2
N
Y
Y Y
Y
NOTE 1
Figure 10: Network side SDL diagram
Page 24ETS 300 102-2: December 1990
SETUPACK
WASSETUP
B/CAST ?
CHNLOK ?
CREATEPROCESS
(CES)
INT *RELEASEREQUEST
(CES)
6
STOPT303
MORE INFOINDICATION
CREATEPROCESS
(CES)
INT *SETUP ACKREQUEST
(CES)
STARTT304
25
STOPT303
MORE INFOINDICATION
STARTT304
25
CHNLOK ?
STOPT303
RELEASE
RELEASEINDICATION
STARTT308
19
CALLPROCEEDING
CREATEPROCESS
(CES)
WASSETUP
B/CAST ?
CHNLOK ?
STOPT303
STOPT303
STOPT303
CREATEPROCESS
(CES)
CHNLOK ?
INT *RELEASEREQUEST
(CES)
6
PROCEEDINGINDICATION
PROCEEDINGINDICATION RELEASE
INT *CALL PROCREQUEST
(CES)
STARTT310
9
STARTT310
9
RELEASEINDICATION
STARTT308
19
CONTD
STATE 6 CALL PRESENT CONTD
N
Y
Y
Y
N
N
+
N
Y
Y
NY
+
N
Figure 11: Network side SDL diagram
Page 25ETS 300 102-2: December 1990
ALERTING
WASSETUP
B/CAST ?
CREATEPROCESS
(CES)
INT *RELEASEREQUEST
(CES)
6
STOPT303
ALERTINGINDICATION
CREATEPROCESS
(CES)
INT *ALERTINGREQUEST
(CES)
STARTT301
7
STOPT303
STOPT303
ALERTINGINDICATION
STARTT301
7
RELEASE
RELEASEINDICATION
STARTT308
19
CHNLOK ?
WASSETUP
B/CAST ?
CREATEPROCESS
(CES)
STOPT303
STOPT303
CHNLOK ?
NOTE 1.
CONNECT INFOREQUEST
STOPT303
INT *RELEASEREQUEST
(CES)
6
SETUPCONFIRM
PRESELECTCES
CREATEPROCESS
(CES)
INT *CONNECTREQUEST
(CES)
8
SETUPCONFIRM
8
RELEASE
RELEASEINDICATION
STARTT308
19
CHNLOK ?
CHNLOK ?
T301 IS NOT USED IF THE NETWORK IMPLEMENTSANOTHER INTERNAL ALERTING SUPERVISIONTIMING FUNCTION.
5.2.5.2 5.2.7
STATE 6 CALL PRESENT CONTD
Y
+
Y
Y
N
N
Y
Y
N
Y
N
N
N
+
NOTE 1
NOTE 1
Figure 12: Network side SDL diagram
Page 26ETS 300 102-2: December 1990
NOTE 1
7CALL
RECEIVED
RELEASECOMPLETE
WASSETUP
B/CAST ?
7
STOPT301
IF RUNNING
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASEINDICATION
RELEASECR
0
STATUS
7
WASSETUP
B/CAST ?
DISCONNECT
STOPT301
IF RUNNING
DISCONNECTB-CHANNEL IF
NOT RELEASED
DISCONNECTINDICATION
11
INT REL COMP *INDICATION
(CES)
DELETECES
7
RELEASE
WASSETUP
B/CAST ?
RELCOMP
RELEASEINDICATION
7
RELEASECOMPLETE
STOPT301
IF RUNNING
RELEASEB-CHANNEL
RELEASECR
0
NOTE 1:
RELEASEREQUEST
DISCONNECTREQUEST CONNECT
TIMEOUTT301
WASSETUP
B/CAST ?
WASSETUP
B/CAST ?
WASSETUP
B/CAST ?
RELEASE
STOPT301
IF RUNNING
STARTT308
19
INTRELEASE *REQUEST
(ALL CES's)
RELEASEINDICATION
STOPT301
IF RUNNING
RELEASEB-CHANNEL
DISCONNECT
STOPT301
IF RUNNING
STARTT305
12
CHNLOK ?
CONNECTINDICATION
STOPT301
IF RUNNING
PRESELECTCES
CREATEPROCESS
(CES)
INTRELEASE *REQUEST
(CES)
7
CONNECTINDICATION
STOPT301
IF RUNNING
8
TIMEOUTINDICATION
7
T312RUNNING
?
22 0
CREATEPROCESS
(CES)
INTCONNECT *REQUEST
(CES)
8
IN THE CASE OF A BROADCAST SETUP,THE CALL STATE RETURNED IN THE STATUSMESSAGE SHOULD BE STATE 6.
5.8.4 5.3.3 5.8.4
5.3.4 5.2.7
Y
N
Y
N
Y
N
+
Y
N
N N Y
Y
N
N
YY
CONTD
Figure 13: Network side SDL diagram
Page 27ETS 300 102-2: December 1990
SETUPACK
CALLPROCEEDING
INT *PROGRESSINDICATION
(CES)
INT *INFO
INDICATION(CES)
WASSETUP
B/CAST ?
CHNLOK ?
CREATEPROCESS
(CES)
INT *SETUP ACKREQUEST
(CES)
7
CREATEPROCESS
(CES)
INT *RELEASEREQUEST
(CES)
7
WASSETUP
B/CAST ?
CHNLOK ?
CREATEPROCESS
(CES)
INT *CALL PROCREQUEST
(CES)
7
CREATEPROCESS
(CES)
INT *RELEASEREQUEST
(CES)
7
PROGRESSINDICATION
7
INFOINDICATION
7
STATUS
7
INFOREQUEST
INTRELEASE
INDICATION(CES)
T312
WASSETUP
B/CAST ?OTHER
CESs ABLETO
PROCEED ?
ANY CESABLE TO
PROCEED ?
T312RUNNING
?
SAVECAUSE
7
RELEASEINDICATION
(CAUSE)
STOP TIMERT301
IF RUNNING
RELEASEB-CHANNEL
RELEASECR
0
7
INT *INFO
REQUESTINFO
77
CONTD
TOALL RESPONDINGTERMINALS
STATE 7 CALL RECEIVED CONTD
5.2.4 5.2.5.2
5
Y
Y
N
NN
Y
N
Y
Y
N
N
Y
N
N
Y
Y
+ +
Figure 14: Network side SDL diagram
Page 28ETS 300 102-2: December 1990
ALERTING INT *CALL PROCINDICATION
(CES)
INT *ALERTING
INDICATION(CES)
INT *CONNECT
INDICATION(CES)
PRESELECTCES
CONNECTINDICATION
STOPT301
IF RUNNING
8
7
WASSETUP
B/CAST ?
CHNLOK ? STATUS
7CREATEPROCESS
(CES)
INT *ALERTINGREQUEST
(CES)
7
CREATEPROCESS
(CES)
INT *RELEASEREQUEST
(CES)
7
INFO
WASSETUP
B/CAST ?
INFOINDICATION
7
STATUS
7
WASSETUP
B/CAST ?
PROGRESSINDICATION
7
NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATERETURNED IN THE STATUS MESSAGE SHOULD BE STATE 6.
STATE 7 CALL RECEIVED CONTD
5.2.5.2
5.2.65
PROGRESS
+
Y
Y
N
N
+
N NNOTE 1
Y Y
Figure 15: Network side SDL diagram
Page 29ETS 300 102-2: December 1990
INDIVIDUAL TERMINAL7I
CALLRECEIVED
DISCONNECT
INT *RELEASE
INDICATION(CES)
RELEASE
STARTT308
19I
RELEASECOMPLETE RELEASE CONNECT
INT *RELEASEREQUEST
INT *RELEASE
INDICATION(CES)
INT *RELEASE
INDICATION(CES)
INT *CONNECT
INDICATION(CES)
RELEASE
INT *REL COMPINDICATION
(CES)
RELCOMP
INT *REL COMPINDICATION
(CES)
8I
STARTT308
19I
PROGRESS STATUS OTHERMESSAGE INFO
INT *INFO
REQUEST
INFO
7I
STATUS
7I
INT *INFO
INDICATION(CES)
INT *PROGRESSINDICATION
(CES)
7I
LOGERROR
7I
7I
Figure 16: Network side SDL diagram
Page 30ETS 300 102-2: December 1990
NOTE 1
8CONNECTREQUEST
RELEASECOMPLETE
WASSETUP
B/CAST ?
RELEASEB-CHANNEL IF
NOT RELEASED
8
RELEASEINDICATION
RELEASECR
0
STATUS
WASSETUP
B/CAST ?
8
DISCONNECTINDICATION
DISCONNECTB-CHANNEL IFCONNECTED
11
DISCONNECT INT *REL COMPINDICATION
(CES)
DELETECES
8
RELEASE
WASSETUP
B/CAST ?
RELEASECOMP
8
RELEASEINDICATION
RELEASECOMPLETE
RELEASEB-CHANNEL
RELEASECR
0
CONNECT SETUPACK
CALLPROCEEDING ALERTING
WASSETUP
B/CAST ?
CREATEPROCESS
(CES)
INT *RELEASEREQUEST
(CES)
8
STATUS
8
RELEASEREQUEST
WASSETUP
B/CAST ?
RELEASE
STARTT308
19
INT *RELEASEREQUEST
(ALL CES's)
RELEASEB-CHANNEL
RELEASEINDICATION
DISCONNECTREQUEST
WASSETUP
B/CAST ?
DISCONNECT
STARTT305
12
T312RUNNING
?
22 0
NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATERETURNED IN THE STATUS MESSAGE SHOULD BE STATE 6.
5.8.4 5.3.3 5.8.4
5.3.4
5.2.95.2.95.2.9 5.2.9
Y
N
Y
N
Y
N
N
Y
N
YY
Y
N
N
CONTD
Figure 17: Network side SDL diagram
Page 31ETS 300 102-2: December 1990
INT *RELEASE
INDICATION(CES)
INT *CALL PROCINDICATION
(CES)
INT *ALERTING
INDICATION(CES)
INT *CONNECT
INDICATION(CES)
SETUPCOMPLETEREQUEST
PRE-SELECTED
CES ?
RELEASEINDICATION
8
INT *RELEASEREQUEST
(ALL CESs))
RELEASEB-CHANNEL
T312RUNNING
?
22 0
CONNECTB-CHANNEL
SELECTCES
CONNECT ACK(SELECTED CES)
END PROCESS*(SELECTED CES)
INT *RELEASEREQUEST
(OTHER CESs)
10
INT *INFO
INDICATION(CES)
INT *PROGRESSINDICATION
(CES)
STATE 8 CONNECT REQUEST CONTD
INFO
WASSETUP
B/CAST ?
INFOINDICATION
8
STATUS
8
PROGRESSINDICATION
INFOINDICATION
8 8
INFOREQUEST
WASSETUP
B/CAST ?
INFO
8
INT *INFO
REQUEST
8
NOTE 1
TO ALLRESPONDINGTERMINALS
NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATERETURNED IN THE STATUS MESSAGE SHOULD BE STATE 6.
5
5.2.8
N
Y
Y
N
5
N
Y
N
Y
Figure 18: Network side SDL diagram
Page 32ETS 300 102-2: December 1990
INDIVIDUAL TERMINAL8I
CONNECTREQUEST
INT *RELEASEREQUEST
RELEASECOMPLETE RELEASEDISCONNECT END
PROCESS
INT *RELEASE
INDICATION(CES)
INT *RELEASE
INDICATION(CES)
INT *RELEASE
INDICATION(CES)
INT *REL COMPINDICATION
(CES)
INT *REL COMPINDICATION
(CES)
RELEASE RELEASECOMPLETE
STARTT308
19I
RELEASE
STARTT308
19I
STATUS OTHERMESSAGES INFO
INT *INFO
REQUEST
STATUS INT *INFO
INDICATION(CES)
INFO
8I
8I
8ILOGERROR
8I
Figure 19: Network side SDL diagram
Page 33ETS 300 102-2: December 1990
5.2.5.2
9I/C CALL
PROCEEDING
ALERTING
WASSETUP
B/CAST ?
CHNLOK ?
STOPT310
IF RUNNING
ALERTINGINDICATION
CREATEPROCESS
(CES)
CREATEPROCESS
(CES)
INT *ALERTING
(CES)
STARTT301
7
INT *RELEASEREQUEST
(CES)
9
STOPT310
IF RUNNING
ALERTINGINDICATION
STARTT301
7
WASSETUP
B/CAST ?
CHNLOK ?
CREATEPROCESS
(CES)
CREATEPROCESS
(CES)
INT *CALLPROC(CES)
9
INT *RELEASEREQUEST
(CES)
9
STATUS
9
CALLPROC
5.2.5.2 CONTD
NOTE 1. T301 IS NOT USED IF THE NETWORK IMPLEMENTS ANOTHERINTERNAL ALERTING SUPERVISION TIMING FUNCTION.
NOTE 1
NOTE 1
+ +
Y
Y
N
Y
N
N
Y
N
Figure 20: Network side SDL diagram
Page 34ETS 300 102-2: December 1990
CONNECT
WASSETUP
B/CAST ?
CHNLOK ?
STOPT310
IF RUNNING
CONNECTINDICATION
PRESELECTCES
CREATEPROCESS
(CES)
INT *CONNECT
(CES)
8
CREATEPROCESS
(CES)
INT *RELEASEREQUEST
(CES)
9
STOPT310
IF RUNNING
CONNECTINDICATION
8
INT *ALERT
INDICATION(CES)
INT *CONNECT
INDICATION(CES)
INT *REL COMPINDICATION
(CES)
STOPT310
IF RUNNING
STOPT310
IF RUNNING
DELETECES
ALERTINGINDICATION
PRESELECTCES 9
STARTT301
CONNECTINDICATION
7 8
INT *CALL PROCINDICATION
(CES)
INTRELEASE
INDICATION(CES)
T312
ANY CESABLE TO
PROCEED ?OTHERCESs
ABLE TOPROCEED ?
T312RUNNING
?
SAVECAUSE
9
STATE 9 I/C CALL PROCEEDING CONTD
RELEASEINDICATION
(CES)
STOP TIMERT310
IF RUNNING
RELEASEB-CHANNEL
RELEASECR
0
9
9
5.2.5.2CONTD
NOTE 1. T301 IS NOT USED IF THE NETWORK IMPLEMENTS ANOTHERINTERNAL ALERTING SUPERVISION TIMING FUNCTION.
+ ++
NOTE 1
Y
Y
N
N
N
Y
N
Y
N
Y
Figure 21: Network side SDL diagram
Page 35ETS 300 102-2: December 1990
Y Y
TO ALLACTIVECES
TO ALLACTIVECES
TO ALLACTIVECES
RELEASEREQUEST
STOPT310
IF RUNNING
WASSETUP
B/CAST ?
STARTT308
RELEASE
19
INT *RELEASEREQUEST
RELEASEB-CHANNEL
IF NECESSARY
RELEASEINDICATION
STATE 9 I/C CALL PROCEEDING CONTD
T312RUNNING
?
22 0
DISCONNECTREQUEST
TIMEOUTT310
WASSETUP
B/CAST ?
DISCONNECT
DISCONNECTB-CHANNEL
IF NECESSARY
STARTT305
12
INT *RELEASEREQUEST
RELEASEB-CHANNEL
IF NECESSARY
RELEASEINDICATION
T312RUNNING
?
22 0
RELEASEDISCONNECTRELEASECOMPLETE
WASSETUP
B/CAST ?
WASSETUP
B/CAST ?
WASSETUP
B/CAST ?
SAVECAUSE
9
STOPT310
IF RUNNING
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASEINDICATION
RELEASECR
0
STATUS
9
STOPT310
IF RUNNING
DISCONNECTB-CHANNEL IFCONNECTED
DISCONNECTINDICATION
11
STOPT310
IF RUNNING
RELEASEINDICATION
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASECOMPLETE
RELEASECR
0
RELEASECOMPLETE
9
INFOREQUEST
WASSETUP
B/CAST ?
INT *INFO
REQUEST
9
INFO
9
5.3.4 5.2.5.3
5.8.45.3.35.8.4
NOTE 1.
NOTE 2.
REF. 5.2.5.4
IN THE CASE OF A BROADCAST SETUP, THE CALL STATERETURNED IN THE STATUS MESSAGE SHOULD BE STATE 6.
STOPT310
IF RUNNING
Y
N
Y
N
N
Y
N
Y
CONTD
5
NOTE 1
N
NOTE 2
N
N
Y
Y
N
Figure 22: Network side SDL diagram
Page 36ETS 300 102-2: December 1990
NOTE 1 NOTE 1
INFO
WASSETUP
B/CAST ?
STATUS
9
INFOINDICATION
9
STATUS
9
STOPT310
IF RUNNING
PROGRESSINDICATION
9
PROGRESS
WASSETUP
B/CAST ?
SETUPACK
INT *INFO
INDICATION(CES)
INT *PROGRESSINDICATION
(CES)
WASSETUP
B/CAST ?
CHNLOK ?
STOPT310
IF RUNNING
INFOINDICATION
PROGRESSINDICATION
9
9
CREATEPROCESS
(CES)
CREATEPROCESS
(CES)
INT *SETUP
ACK(CES)
INT *RELEASEREQUEST
(CES)
9 9
STATUS
9
STATE 9 I/C CALL PROCEEDING CONTD
5 5.2.6
5.2.4
NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATERETURNED IN THE STATUS MESSAGE SHOULD BE STATE 6.
Y
N
Y
N
Y
Y
N
N
Figure 23: Network side SDL diagram
Page 37ETS 300 102-2: December 1990
NOTE 1 NOTE 1 NOTE 1
NOTE 1 NOTE 1
9II/C CALL
PROCEEDING
DISCONNECT
STOPT310
IF RUNNING
INT *RELEASE
INDICATION(CES)
RELEASE
STARTT308
19I
TIMEOUTT310
INT *RELEASEREQUEST
RELEASECOMP
RELEASE ALERTING
STOPT310
IF RUNNING
STOPT310
IF RUNNING
STOPT310
IF RUNNING
STOPT310
IF RUNNING
RELEASE
19I
STARTT308
INT *RELEASE
INDICATION(CES)
INT *REL COMPINDICATION
(CES)
INT *RELEASE
INDICATION(CES)
RELEASECOMPLETE
INT *REL COMPINDICATION
(CES)
INT *ALERT
INDICATION(CES)
7I
CONNECTINT *INFO
REQUESTINFOOTHER
MESSAGESTATUSPROGRESS
STOPT310
IF RUNNING
INT *PROGRESSINDICATION
(CES)
9I
LOGERROR
STATUS
9I
9I
INT *INFO
INDICATION(CES)
9I
INFO
9I
STOPT310
IF RUNNING
INT *CONNECT
INDICATION(CES)
INDIVIDUAL TERMINAL
NOTE 1. IMPLEMENTATION OF TIMER T310 IN INDIVIDUAL PROCESSES IS OPTIONAL.
NOTE 1 NOTE 1
8I
Figure 24: Network side SDL diagram
Page 38ETS 300 102-2: December 1990
5.1.8
+
NOTE 1
10ACTIVE
CONNECTACK SUSPEND NOTIFY
REQUEST NOTIFY RELEASECOMPLETE
INT *REL COMPINDICATION
(CES)
10 SUSPENDINDICATION
15
NOTIFY NOTIFYINDICATION
10 10 RELEASEINDICATION
0
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASECR
DELETECES
10
DISCONNECTREQUEST
RELEASEREQUESTRELEASEDISCONNECTINFO INFO
REQUEST
INFOINDICATION
10
INFODISCONNECTB-CHANNEL IFCONNECTED
RELEASEINDICATION RELEASE
DISCONNECTB-CHANNEL IFCONNECTED
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASEB-CHANNEL IF
NOT RELEASED
STARTT308
STARTT305
DISCONNECT
RELEASECOMPLETE
DISCONNECTINDICATION
RELEASECR
10
11
0
19 12
5.6.2
5.6.2
5.6.4
5
5.8.4
THE USE OF THE CALL REARRANGEMENT PROCEDURE IS RESTRICTEDTO BASIC ACCESS i.e. IT WILL NOT BE AVAILABLE FORPRIMARY RATE ACCESS.
5.3.45.3.3
NOTE 1.
5.8.4
+
5.6.2
5.6.4
5
5.9 5.9
Figure 25: Network side SDL diagram
Page 39ETS 300 102-2: December 1990
5.8.4
+
11DISCONNECT
REQUEST
RELEASECOMPLETE
RELEASEB-CHANNEL IF
NOTRELEASED
RELEASEINDICATION
RELEASECR
0
RELEASE
RELEASEINDICATION
RELEASEB-CHANNEL IF
NOTRELEASED
RELEASECOMPLETE
RELEASECR
0
RELEASEREQUEST INFO INFO
REQUEST
RELEASE
STARTT308
19
INFOINDICATION
11
INFO
11
5.8.4 5.3.3 5 5
Figure 26: Network side SDL diagram
5.8.4
+
12DISCONNECTINDICATION
RELEASECOMPLETE RELEASE DISCONNECT TIMEOUT
T305TIMEOUT
T306 INFO INFOREQUEST
STOPT305
OR T306
STOP TONES/ANNOUNCEMENTS
IF APPLICABLE
RELEASEB-CHANNEL IF
NOT RELEASED
STOPT305
OR T306
STOP TONES/ANNOUNCEMENTS
IF APPLICABLE
RELEASEB-CHANNEL
RELEASECOMPLETE
RELEASECALL REF
STOP TONES/ANNOUNCEMENTS
IF APPLICABLE
STOPT305
OR T306
STARTT308
RELEASE
RELEASEINDICATION
RELEASEINDICATION
19
0
RELEASECR
0
STOP TONES/ANNOUNCEMENTS
IF APPLICABLE
INFOINDICATION INFO
12 12
RELEASE
STARTT308
19
5.3.4 5.3.6 5.3.4 5.3.4 5 5
NOTE 1 : CAUSE SENT IS SAME AS INORIGINAL DISCONNECT MESSAGE.
NOTE 1
Figure 27: Network side SDL diagram
Page 40ETS 300 102-2: December 1990
+
15SUSPENDREQUEST
SUSPENDRESPONSE
SUSPENDACKNOWLEDGE
RELEASECR
0
SUSPENDREJECT
REQUEST
DISCONNECTREQUEST
SUSPENDREJECT
10
TONEOPTION
?
DISCONNECTB-CHANNEL IFCONNECTED
DISCONNECT
STARTT305
DISCONNECT(PI)
STARTTONE
STARTT306
12
RELEASEREQUEST
RELEASE
RELEASEB-CHANNEL IF
NOT RELEASED
STARTT308
19
NOTIFYREQUEST
NOTIFY
15
5.6.2 5.6.3 5.3.4 5.9
5.6.2
5.6.4
NOTE 1 :
NOTE 2 :
TIMER T307 IS RUNNINGIN THE CALL CONTROL BLOCK.
THIS PRIMITIVE IS RECEIVED WHENDOUBLE SUSPENSION OCCURS.
N
Y
NOTE 1 NOTE 2
Figure 28: Network side SDL diagram
17RESUMEREQUEST
RESUMERESPONSE
RESUMEACKNOWLEDGE
10
RESUMEREJECT
REQUEST
RESUMEREJECT
RELEASECR
0
DISCONNECT
DISCONNECTB-CHANNEL IFCONNECTED
DISCONNECTINDICATION
11
+5.3.3
Figure 29: Network side SDL diagram
Page 41ETS 300 102-2: December 1990
1 9R E L E A S ER E Q U E S T
R E L E A S EC O M P L E T E
S T O PT 3 0 8
R E L E A S EC O N F I R M
R E L E A S EB-CHNL IF
N E C E S S A R Y
R E L E A S EC A L L R E F
0
R E L E A S ET I M E O U T
T 3 0 8
F IRSTE X P I R Y
?
R E L E A S E
S T A R TT 3 0 8
1 9
P L A C EB - C H A N N E L I N AM A I N T E N A N C E
C O N D I T I O N
R E L E A S EC O N F I R M
R E L E A S EC A L L R E F
0
D I S C O N N E C T
1 9
INT *R E L C O M PINDICATION
(CES)
D E L E T EC E S
1 9
S T A T U S
C S =0 ?
S T A T U SINDICATION
( E R R O R )
S T O PT 3 0 8
R E L E A S EB - C H A N N E L
R E L E A S EC A L L R E F
0
1 9
INT *I N F O
INDICATION(CES)
I N F O
I N F OINDICATION
1 9
I N F OINDICATION
1 9
5.3 .4 5.3 .5 5.3 .4 .35 .8 .11
+
5
Y
N
Y
N
Figure 30: Network side SDL diagram
Page 42ETS 300 102-2: December 1990
INDIVIDUAL TERMINAL19I
RELEASEREQUEST
RELEASECOMPLETE
STOPT308
INT *REL COMPINDICATION
(CES)
RELEASE
STOPT308
INT *REL COMPINDICATION
(CES)
DISCONNECT
19I
TIMEOUTT308
FIRSTEXPIRY
?
RELEASE
STARTT308
19I
STATUS OTHERMESSAGE
STATUS
19ILOGERROR
19I
INFO
19I
INT *REL COMPINDICATION
(CES)
NOTE 1. THE INDIVIDUAL PROCESS MAY PASS AN INT. INFOINDICATION TO THE GLOBAL PROCESS AT THIS POINT.(REF. SECTION 5.0)
N
NOTE 1
Y
Figure 31: Network side SDL diagram
Page 43ETS 300 102-2: December 1990
22CALL
ABORT
ALERTING
CREATEPROCESS
(CES)
INT *RELEASEREQUEST
(CES)
22
CONNECT CALLPROCEEDING
SETUPACKNOWLEDGE RELEASE RELEASE
COMPLETE
RELEASECOMPLETE
22
22
TIMEOUTT312
CLEART312FLAG
0
INT *REL COMPINDICATION
(CES)
DELETECES
22
+
5.3.2(e)
5.3.2(e) 5.3.2(e) 5.3.2(e) 5.3.2(e)
NOTE 1. THE CALL REFERENCE SHOULD NOT BE RE-USEDUNTIL ALL TERMINALS HAVE COMPLETED CLEARING.
NOTE 1
Figure 32: Network side SDL diagram
Page 44ETS 300 102-2: December 1990
TO ALLACTIVECES's
NOTE 1
25OVERLAP
RECEIVING
SETUPACK
WASSETUP
B/CAST ?
CHNLOK ?
MAXEXCEEDED
?
CREATEPROCESS
(CES)
CREATEPROCESS
(CES)
INT *SETUP
ACKNOWLEDGE(CES)
INT *RELEASEREQUEST
(CES)
INFOMESSAGES
FROMQUEUE
25
25
STATUS
25ADD INFOMESSAGETO QUEUE
WASSETUP
B/CAST ?
STOPT304
MOREINFO
REQUEST
INT *INFO
REQUEST
STARTT304
25
INFO STARTT301
ALERTINGINDICATION
STOPT304
INT *ALERT
INDICATION(CES)
7
25
DELETECES
PRESELECTCES
INT *REL COMPINDICATION
(CES)
INT *CALL PROCINDICATION
(CES)
INT *CONNECT
INDICATION(CES)
T312
INTRELEASE
INDICATION(CES)
STOPT304
STOPT304
OTHERCESs ABLE
TOPROCEED ?
ANYCES ABLE
TOPROCEED ?
PROCEEDINGINDICATION
STARTT310
9
CONNECTINDICATION
8
T312RUNNING
?
25
RELEASEINDICATION
(CAUSE)
STOP TIMERT304
IF RUNNING
RELEASEB-CHANNEL
RELEASECR
0
SAVECAUSE
25
INT *INFO
INDICATION(CES)
INT *PROGRESSINDICATION
(CES)
PROGRESSINDICATION
25
INFOINDICATION
25
+
5.2.4 5.2.4
+ +
+ +
NOTE 1. T301 IS NOT USED IF THENETWORK IMPLEMENTS ANOTHERINTERNAL ALERTING SUPERVISIONTIMING FUNCTION.
N
N
Y
Y
N
CONTD
N
N
Y
N
Y
Y
N
Y
Y
Figure 33: Network side SDL diagram
Page 45ETS 300 102-2: December 1990
Y Y
CONTD.
ALERTING
WASSETUP
B/CAST ?
STOPT304
CHNLOK ?
STOPT304
ALERTINGINDICATION
CREATEPROCESS
(CES)
CREATEPROCESS
(CES)
ALERTINGINDICATION
STARTT301
7
INT *ALERTING
(CES)
STARTT301
7
INT *RELEASEREQUEST
(CES)
25
CONNECT
WASSETUP
B/CAST ?
CHNLOK ?
STOPT304
CONNECTINDICATION
PRESELECTCES
OVERLAP RECEIVING CONTD 5.2.5.2
NOTE 1.
CREATEPROCESS
(CES)
INT *CONNECT
(CES)
8
8
INT *RELEASEREQUEST
(CES)
25
CONNECTINDICATION
STOPT304
PROGRESS INFO
WASSETUP
B/CAST ?
WASSETUP
B/CAST ?
STATUS PROGRESSINDICATION
25 25 25 25
STATUS INFOINDICATION
5.2.7
+ +
5.2.6 5
CREATEPROCESS
(CES)
NOTE 2.
IN THE CASE OF A BROADCAST SETUP, THE CALL STATERETURNED IN THE STATUS MESSAGE SHOULD BE STATE 6.
T301 IS NOT USED IF THE NETWORK IMPLEMENTS ANOTHERINTERNAL ALERTING SUPERVISION TIMING FUNCTION.
NOTE 2
NOTE 1
N
NOTE 1
N
Y
Y
Y
Y
N N
N
NOTE 2
N
Figure 34: Network side SDL diagram
Page 46ETS 300 102-2: December 1990
+
Y
OVERLAP RECEIVING CONTD 5.2.5.2 5.3.3
5.8.4
CALLPROC
WASSETUP
B/CAST ?
CHNLOK ?
STOPT304
PROCEEDINGINDICATION
CREATEPROCESS
(CES)
CREATEPROCESS
(CES)
INT *RELEASEREQUEST
(CES)
STARTT310
9
INT *CALLPROC(CES)
25
5.8.4
STOPT304
PROCEEDINGINDICATION
STARTT310
9
STATUS
25
STOPT304
DISCONNECTB-CHANNEL IFCONNECTED
DISCONNECTINDICATION
11
WASSETUP
B/CAST ?
DISCONNECT
RELEASECOMPLETERELEASE
WASSETUP
B/CAST ?
WASSETUP
B/CAST ?
RELEASECOMPLETE
STOPT304
SAVECAUSE
STOPT304
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASEB-CHANNEL IF
NOT RELEASED
RELEASECR
RELEASECR
RELEASEINDICATION
RELEASECOMPLETE
RELEASEINDICATION
25
0
25
0
CONTD.
Y
NOTE 1.
NOTE 2.
IN THE CASE OF A BROADCAST SETUP, THE CALL STATERETURNED IN THE STATUS MESSAGE SHOULD BE STATE 6.
REF. 5.2.5.4
N
Y
Y
NOTE 1
NN
Y
N
NOTE 2
N
Figure 35: Network side SDL diagram
Page 47ETS 300 102-2: December 1990
NOTE 1
DISCONNECTREQUEST
STOPT304
WASSETUP
B/CAST ?
TIMEOUTT304
INT *RELEASEREQUEST
RELEASEB-CHANNEL
IF NECESSARY
RELEASEINDICATION
T312RUNNING
?
22 0
STARTT305
12
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
RELEASEREQUEST
STOPT304
WASSETUP
B/CAST ?
INT *RELEASEREQUEST
RELEASEB-CHANNEL
IF NECESSARY
RELEASEINDICATION
T312RUNNING
?
22 0
19
STARTT308
RELEASE
TO ALLCES's
TO ALLCES's
NOTE 1. IF T304 EXPIREDSEND SAVED CAUSEIN RELEASE INDICATION.
OVERLAP RECEIVING CONTD 5.3.4 5.2.4
Y
N
Y
N
Y
N
Y
N
Figure 36: Network side SDL diagram
Page 48ETS 300 102-2: December 1990
25IOVERLAP
RECEIVING
INT *INFO
REQUESTALERTING PROGRESSOTHER
MESSAGECONNECT CALLPROC
STOPT304
STOPT304
STOPT304
STOPT304
STOPTIMERT304
STATUS
INFO
STARTT304
STARTT310
INT *ALERT
INDICATION(CES)
INT *CONNECT
INDICATION(CES)
INT *CALL PROCINDICATION
(CES)
INT *PROGRESSINDICATION
(CES)
25I
7I 8I
9I
25I
25I
IMPLEMENTATION OF TIMER T310 ININDIVIDUAL PROCESSES IS OPTIONAL.
NOTE 1.
INT *RELEASEREQUEST
TIMEOUTT304 DISC RELEASE
COMP RELEASE STATUS
STOPT304
INT *RELEASE
INDICATION(CES)
STOPT304
INT *RELEASE
INDICATION(CES)
RELEASECOMP
INT *REL COMPINDICATION
(CES)
STOPT304
STOPT304
INT *RELEASE
INDICATION(CES)
INT *RELEASE
INDICATION(CES)
INT *REL COMPINDICATION
(CES)RELEASE
STARTT308
19I
LOGERROR
25I
INDIVIDUAL TERMINAL
NOTE 1
Figure 37: Network side SDL diagram
Page 49ETS 300 102-2: December 1990
NOTE 1
5.8.10, 5.8.11
5.8.85.8.85.8.8
NOTE 2
NOTE 1.
NOTE 2.
NOTE 3.
ANYGLOBALSTATE
DL-ESTABLISHINDICATION
STATEN2,N25
?
STOP ANYTIMER
SAMESTATE
TONEOPTION
?
DISCONNECTINDICATION
DISCONNECTINDICATION
DISCONNECTB-CHANNEL IFCONNECTED
STARTTONE
STARTT306
STARTT305
DISCONNECT(PI)
DISCONNECT
12
7I, 8I,9I, 25I
DL-ESTABLISHINDICATION
SAMESTATE
STATES10,11,12,
15.19
STATES8,10,11,12,
15,1925I
MESSAGE(WRONG)
(CES)
CREATEPROCESS
(CES)
INT *RELEASEREQUEST
(CES)
SAMESTATE
SAMESTATE
TIMEOUTT312
STOP T304IF
IMPLEMENTED
DL-ESTABLISHINDICATION
INT *RELEASE
INDICATION(CES)
RELEASE
STARTT308
19I
ANY STATEEXCEPT
0, 19
STATUS(CS=M)
T322RUNNING
?
CAUSE=#97
?
CAUSE=#30
?
STOPT322
SAVE CAUSEAND
CALL STATE
SAMESTATE
M=0?
RELEASECR AND
RESOURCES
STATUSINDICATION
(ERROR)
0
COMPATIBLESTATE
?
SAMESTATE
STATUSINDICATION
(ERROR)
RELEASE
STARTT308
19
FURTHER ACTIONS ARE AN IMPLEMENTATION OPTION.
TONE OPTION NOT APPLICABLE TO STATE N25.
CAUSE #41 IS SENT IN THE DISCONNECT MESSAGE.
NOTE 3
Y
N
Y
N
Y
N
Y
Y
N
Y
N
Figure 38: Network side SDL diagram
Page 50ETS 300 102-2: December 1990
5.8.9
5.8.95.8.95.8.9
5.8.9
ANY STATEEXCEPT 0,
10
DL-RELEASEINDICATION
STOPANY TIMER
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0
0
DL-RELEASEINDICATION
0
10ACTIVE
DL-RELEASEINDICATION
T309RUNNING
?
STARTT309
DL-ESTABLISHREQUEST
10ACTIVE
10ACTIVE
7I, 8I, 9I,19I, 25I
DL-RELEASEINDICATION
STOPANY TIMER
INTERNAL *RELEASE
INDICATION(CES)
INTERNAL *REL COMPINDICATION
(CES)
DL-ESTABLISHCONFIRMATION
TIMEOUTT309
STOPT309
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0
STATUS
10ACTIVE
STARTT322
STATUSENQUIRY
T322RUNNING ?
NOTE 1: T322 MUST BE STOPPED ON RECEIPT OF ACLEARING MESSAGE
N
Y
N
Y
NOTE 1
Figure 39: Network side SDL diagram
Page 51ETS 300 102-2: December 1990
ANY GLOBAL ORINDIVIDUAL
STATE EXCEPTO, OI
T322RUNNING
?
UNEXPECTEDMESSAGE
UNRECOGNISEDMESSAGE SETUP
SAMESTATE
STATUS
STATUSENQUIRY
STARTT322
SAMESTATE
NOTE 4
5.8.4 5.8.4 5.8.3.2(e)
TIMEOUTT322 STATUS
ENQUIRY
STATUSENQUIRYREQUEST
T322RUNNING
?
STATUSMESSAGERECEIVED
?
STATUS
SAMESTATE
NOTE 2
MAX No.RETRANSMISSIONS
EXCEEDED?
RELEASE(CAUSE #41)
STATUSENQUIRY
STARTT322
SAMESTATE
NOTE 4
5.8.10 5.8.10 5.8.10
RELEASEINDICATION
(ERROR)
STARTT308
19
STATUSENQUIRY
STARTT322
SAMESTATE
NOTE 4
NOTE 1 :-
NOTE 2 :-
NOTE 3 :-
NOTE 4 :-
"UNEXPECTED MESSAGE" AND"UNRECOGNISED MESSAGE" DO NOTINCLUDE RELEASE AND RELEASE COMPLETE
ACTIONS AFTER EXPIRY OF T322WHEN A STATUS MESSAGE HAS BEENRECEIVED ARE IMPLEMENTATION DEPENDENT
CAUSE #30 SHALL BE SENTIN THE STATUS MESSAGE
T322 MUST BE STOPPED IF ANY CLEARINGMESSAGE IS RECEIVED BEFORE IT EXPIRES
NOTE 1NOTE 1
Y
N
NOTE 3
Y
N
Y
N
N
Figure 40: Network side SDL diagram
Page 52ETS 300 102-2: December 1990
7.2 User side SDL diagrams
++ +
ONULL
RESUMEREQUEST
SELECTCR
RESUME
STARTT318
17
SETUPREQUEST
SELECTCR
SETCHANNELIDENTITY
SETUP
STARTT303
1
RELEASE
ESTABLISHCR
RELEASECR
RELEASECOMPLETE
0
RELEASECOMPLETE
0
SETUP
ESTABLISHCR
SETUPINDICATION
6
STATUS(CS=0)
0
UNEXPECTEDMESSAGE
STATUS(CS<>0)
5.8.115.2.15.8.35.8.35.1.15.6.4
UNRECOGNISEDMESSAGE
NOTE 3
NOTE 2
NOTE 4
NOTE 1
ESTABLISHCR
RELEASECOMPLETE
RELEASECR
0
ESTABLISHCR
RELEASE
STARTT308
19
NOTE 1 :
NOTE 2 :
NOTE 3 :
NOTE 4 :
T318 IS OPTIONAL
IF THE USER IS UNABLE TO PROCEED WITH THE CALLDUE TO THE CHANNEL IDENTITY BEING UNACCEPTABLE,A RELEASE COMPLETE MESSAGE MAY BE RETURNED AT THIS POINT(REF. SECTION 5.2.3)
THE USE OF THE CALL REARRANGEMENT PROCEDURE ISRESTRICTED TO BASIC ACCESS, i.e. IT WILL NOT BEAVAILABLE FOR PRIMARY RATE ACCESS
T303 IS ONLY APPLICABLE FOR THE PROCEDURESDEFINED IN ANNEX D
5.8.3 5.8.35.8.11
Figure 41: User side SDL diagram
Page 53ETS 300 102-2: December 1990
Y
+
5.1.15.1.25.3.2
1CALL
INITIATED
TIMEOUTT303
FIRSTTIMEOUT
?
SETUP
STARTT303
1
RELEASECR
0
DISCONNECTREQUEST
STOPT303
DISCONNECT
STOPT305
11
INFOREQUEST
CALLPROCEEDING
STOPT303
PROCEEDINGINDICATION
B-CHANNELCONTROL(REF 5.1.2)
STARTT310
3
NOTE 1
NOTE 2
NOTE 3
NOTE 4
NOTE 3
NOTE 3
5.1.5.15.1.35.3.3
RELEASERELEASECOMPLETE
SETUPACKCONNECTALERTING
STOPT303
ALERTINGINDICATION
B-CHANNELCONTROL(REF 5.1.2
5.1.6, 5.1.7)
STARTT301
4
STOPT303
SETUPCONFIRM
B-CHANNELCONTROL
(IF NOT YETEXPECTED)
CONNECTACKNOWLEDGE
10
STOPT303
MOREINFO
INDICATION
B-CHANNELCONTROL(REF 5.1.2)
STARTT304
2
0
STOPT303
RELEASECR
REJECTINDICATION
STOPT303
RELEASEINDICATION
RELEASECOMPLETE
RELEASECR
3
NOTE 3NOTE 3
NOTE 2
NOTE 1
NOTE 3
NOTE 2
NOTE 3
NOTE 1
NOTE 3
5.8.4
5.1.3
NOTE 1:
NOTE 2:
NOTE 3:
NOTE 4:
T304 & T310 ARE OPTIONAL
THE USER MAY CLEAR THE CALL AT THIS POINT IF THE CHANNEL IDENTITYRETURNED BY THE NETWORK IS UNACCEPTABLE.
ONLY APPLICABLE FOR THE PROCEDURES DEFINED IN ANNEX D.
THE SETUP ACKNOWLEDGE MESSAGE WILL NOT BE RECEIVED IF THE SENDINGCOMPLETE INFORMATION ELEMENT IS INCLUDED IN THE ORIGINATING SETUPMESSAGE.
N
Figure 42: User side SDL diagram
Page 54ETS 300 102-2: December 1990
NOTE 1
NOTE 1
NOTE 1
NOTE 1
NOTE 1 NOTE 1 NOTE 1
NOTE 2
NOTE 3
NOTE 1NOTE 1NOTE 1
NOTE 1
5.1.2 5.8.4 5.1.6 5.8.4 5
NOTE 1 :
NOTE 2 :
NOTE 3 :
2OVERLAPSENDING
TIMEOUTT304
SETUPCONFIRM(ERROR)
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
STARTT305
11
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
STARTT305
11
STOPT304
(IF RUNNING)
DISCONNECTREQUEST
INFOREQUEST ALERTING CALL
PROCEEDING CONNECT
INFO
RESTARTT304
IF RUNNING
2
STOPT304
(IF RUNNING)
ALERTINGINDICATION
B-CHANNELCONTROL(REF 5.1.2,
5.1.6)
4
STOPT304
(IF RUNNING)
PROCEEDINGINDICATION
B-CHANNELCONTROL(REF 5.1.2,
5.1.6)
3
STARTT310
STOPT304
(IF RUNNING)
SETUPCONFIRM
CONNECTB-CHANNEL(IF NOT YET
CONNECTED)
10
CONNECTACK
5.1.5.2 5.3.3 5.1.3 5.1.5.2 5.1.5.2 5.1.5.2
+ + + +
DISCONNECTINFORELEASECOMPLETE
PROGRESS(INTER-WORKING)
RELEASEPROGRESS(TONE)
STOPT304
(IF RUNNING)
DISCONNECTINDICATION
B-CHANNELCONTROL
12
INFOINDICATION
2
STOPT304
(IF RUNNING)
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0
STOPT304
(IF RUNNING)
PROGRESSINDICATION
B-CHANNELCONTROL
(REF. 5.1.2,5.1.6)
2
STOPT304
(IF RUNNING)
PROGRESSINDICATION
B-CHANNELCONTROL
(REF. 5.1.2)
2
RELEASEINDICATION
RELEASEB-CHANNEL
RELEASECOMPLETE
RELEASECR
0
5.3.4
TIMERS T304 & T310 ARE OPTIONALT304 MAY BE IMPLEMENTED BUT STOPPED DUE TORECEIPT OF PROGRESS (INTERWORKING)
IN THE CASE OF UNSUCCESSFUL TERMINATION OF THE B-CHANNELSELECTION PROCEDURE (REF. 5.3.2d) A RELEASE MESSAGE ISRETURNED BEFORE ENTERING STATE 2.
TIMER T301 IS STARTED AT THIS POINT IF THE PROCEDURESDEFINED IN ANNEX D ARE IMPLEMENTED
Figure 43: User side SDL diagram
Page 55ETS 300 102-2: December 1990
NOTE 1NOTE 1 NOTE 1
NOTE 1NOTE 1NOTE 1
NOTE 1 :
NOTE 2 :
NOTE 3 :
3O/G CALL
PROCEEDING
DISCONNECTREQUEST
STOPT310
(IF RUNNING)
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
STARTT305
11
ALERTING
STOPT310
(IF RUNNING)
ALERTINGINDICATION
B-CHANNELCONTROL
(REF. 5.1.2,5.1.6)
4
CONNECT DISCONNECT INFO PROGRESS(TONE)
STOPT310
(IF RUNNING)
STOPT310
(IF RUNNING)
INFOINDICATION
PROGRESSINDICATION
3
3
B-CHANNELCONTROL
(REF. 5.1.2)
DISCONNECTINDICATION
B-CHANNELCONTROL
12
SETUPCONFIRM
CONNECTB-CHANNEL(IF NOT YET
CONNECTED)
CONNECTACK
10
RELEASERELEASECOMPLETE
PROGRESS(INTER-WORKING)
TIMEOUTT310
INFOREQUEST
STOPT310
(IF RUNNING)INFO
DISCONNECTB-CHANNEL
IF NECESSARY
STOPT310
(IF RUNNING)
STOPT310
(IF RUNNING)
PROGRESSINDICATION 3 DISCONNECT RELEASE
B-CHANNELRELEASE
INDICATION
RELEASEB-CHANNEL
RELEASECOMPLETE
RELEASECR
0
0
RELEASECR
RELEASEINDICATION
SETUPCONFIRM(ERROR)
STARTT305
11
B-CHANNELCONTROL
(REF. 5.1.2,5.1.6)
3
NOTE 1
NOTE 1
NOTE 2
NOTE 3
5.3.3 5.1.7 5.1.8 5.3.4 5 5.1.2
+ +
5.1.6 5 5.8.45.8.4
T310 IS OPTIONALIT MAY BE IMPLEMENTED BUT STOPPED DUE TORECEIPT OF PROGRESS (INTERWORKING)
IN THE CASE OF UNSUCCESSFUL TERMINATION OF THE B-CHANNELSELECTION PROCEDURE (REF. 5.3.2d) A RELEASE MESSAGE ISRETURNED BEFORE ENTERING STATE 2.
TIMER T301 IS STARTED AT THIS POINT IF THE PROCEDURESDEFINED IN ANNEX D ARE IMPLEMENTED
Figure 44: User side SDL diagram
Page 56ETS 300 102-2: December 1990
+
4CALL
DELIVERED
DISCONNECTREQUEST
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
STARTT305
11
CONNECT
SETUPCONFIRM
CONNECTB-CHANNEL(IF NOT YET
CONNECTED)
CONNECTACK
10
DISCONNECT
DISCONNECTINDICATION
B-CHANNELCONTROL
12
INFO
INFOINDICATION
4
PROGRESS
PROGRESSINDICATION
B-CHANNELCONTROL
(REF. 5.1.2,5.1.6)
4
RELEASE
RELEASEINDICATION
RELEASEB-CHANNEL
RELEASECOMPLETE
RELEASECR
0
5.3.3 5.3.45.1.8 5 5.1.6 5.8.4
RELEASECOMPLETE
INFOREQUEST
INFO
4
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0
5 5.8.4
NOTE 1 :
NOTE 2 :
IN THE CASE OF UNSUCCESSFUL TERMINATION OF THE B-CHANNELSELECTION PROCEDURE (REF. 5.3.2d) A RELEASE MESSAGE ISRETURNED BEFORE ENTERING STATE 2.
T301 (NOT SHOWN) IS RUNNING IN THIS STATE IF THE PROCEDURESDEFINED IN ANNEX D ARE IMPLEMENTED
Figure 45: User side SDL diagram
Page 57ETS 300 102-2: December 1990
5CALL
PRESENT
ALERTINGREQUEST
B-CHANNELSELECTION
ALERTING
7
PROCEEDINGREQUEST
B-CHANNELSELECTION
CALLPROCEEDING
9
SETUPRESPONSE
B-CHANNELSELECTION
CONNECT
STARTT313
8 25
STARTT302
SETUPACK
B-CHANNELSELECTION
MOREINFO
REQUESTDISCONNECT
DISCONNECTINDICATION
12
RELEASE
RELEASEINDICATION
RELEASECOMPLETE
RELEASECR
0
5.2.5.15.2.75.2.5.1 5.2.45.2.5 5.3.4 5.3.2
+ + + +
RELEASECOMPLETE
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0
REJECTREQUEST(CAUSE)
CAUSE=INCOMPATIBLE
USER ?
WASSETUPB/CAST
?
5.8.4
5.2.5.15.2.25.2.3
RELEASECOMPLETE
(CAUSE)
RELEASECR
0
NOTE 1 :
NOTE 2 :
TIMER T302 IS OPTIONAL
IN THE CASE OF A POINT-TO-POINT CONNECTIONCONNECTION TO THE B-CHANNEL MAY BE MADE ATTHIS POINT REF. 5.2.3.1d.
NOTE 2 NOTE 2 NOTE 2 NOTE 2
NOTE 1
Y
Y
N
N
Figure 46: User side SDL diagram
Page 58ETS 300 102-2: December 1990
+
7CALL
RECEIVED
DISCONNECTREQUEST
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
STARTT305
11
8
STARTT313
CONNECT
SETUPRESPONSE
PROGRESSREQUEST
PROGRESS
7
DISCONNECTINDICATION
12 7
INFOINDICATION
DISCONNECT INFO RELEASE
RELEASEINDICATION
RELEASEB-CHANNEL
(IF NECESSARY)
RELEASECOMPLETE
RELEASECR
0
5.2.65.3.3 5.3.4 5 5.8.45.2.75.2.5.1
NOTE 1 NOTE 1
INFOREQUEST
RELEASECOMPLETE
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0
INFO
7
5 5.8.4
NOTE 1: IN THE POINT TO POINT CASECONNECTION TO THE B-CHANNELMAY BE MADE AT THIS POINT.(REF. 5.2.3.1d).
Figure 47: User side SDL diagram
Page 59ETS 300 102-2: December 1990
NOTE 1
NOTE 2
8CONNECTREQUEST
TIMEOUTT313
DISCONNECT
STARTT305
SETUPCOMPLETEINDICATION
(ERROR)
11
DISCONNECTREQUEST
STOPT313
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
STARTT305
11
CONNECTACK
STOPT313
SETUPCOMPLETEINDICATION
CONNECTB-CHANNEL(IF NOT YET
CONNECTED )
10
DISCONNECT INFO RELEASE
STOPT313
INFOINDICATION
STOPT313
DISCONNECTINDICATION 8
12
RELEASEINDICATION
RELEASEB-CHANNEL
(IF CONNECTED)
RELEASECOMPLETE
RELEASECR
0
5.3.45.2.8 5.3.3 5 5.8.4+
RELEASECOMPLETE
INFOREQUEST
5 5.8.4
INFO
8
STOPT313
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0
NOTE 1 : REF. SECTION 5.2.8
5.2.8
Figure 48: User side SDL diagram
Page 60ETS 300 102-2: December 1990
9I/C CALL
PROCEEDING
ALERTINGREQUEST
ALERTING
7
DISCONNECTREQUEST
SETUPRESPONSE
PROGRESSREQUEST
DISCONNECT INFO
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
STARTT305
11
8
STARTT313
CONNECT PROGRESS
9 12 9
DISCONNECTINDICATION
INFOINDICATION
5.2.5.1
+
5.3.3
+
5.2.6 5.3.4 55.2.75.2.5.1
RELEASERELEASECOMPLETE
INFOREQUEST
INFO
9
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0
RELEASEINDICATION
RELEASEB-CHANNEL
(IF CONNECTED)
RELEASECOMPLETE
RELEASECR
0
NOTE 1 NOTE 1 NOTE 1
5 5.8.4 5.8.4
NOTE 1 : IN THE POINT TO POINT CASE,CONNECTION TO THE B-CHANNELMAY BE MADE AT THIS POINT.(REF. 5.2.3.1d)
Figure 49: User side SDL diagram
Page 61ETS 300 102-2: December 1990
10ACTIVE
DISCONNECTREQUEST
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
STARTT305
11
INFOREQUEST
INFO
10 10
NOTIFY
NOTIFYREQUEST
SUSPENDREQUEST DISCONNECT INFO
INFOINDICATION
1012
DISCONNECTINDICATIONSUSPEND
STARTT319
15
NOTE 1
NOTE 1
55.3.3
+
5.6.1 5.3.4 5
+
5.6.75.9
NOTIFYRELEASERELEASECOMPLETE
5.8.4 5.8.45.95.6.45.6.2
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0 RELEASECR
RELEASECOMPLETE
RELEASEB-CHANNEL
RELEASEINDICATION
NOTIFYINDICATION
10
0
NOTE 1 : THE USE OF THE CALL REARRANGEMENT PROCEDURE IS RESTRICTEDTO BASIC ACCESS i.e. IT WILL NOT BE AVAILABLE FORPRIMARY RATE ACCESS.
Figure 50: User side SDL diagram
Page 62ETS 300 102-2: December 1990
+
11DISCONNECT
REQUEST
TIMEOUTT305
RELEASE
STARTT308
19
DISCONNECT INFO NOTIFY
STOPT305
INFOINDICATION
NOTIFYINDICATION
1111
19
STARTT308
RELEASE
NOTE 1
5.3.3 5.3.5 5
5.95.6.45.6.2
INFOREQUEST
RELEASECOMPLETE RELEASE
5 5.8.4 5.3.3
INFO
11
STOPT305
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0 RELEASECR
0
RELEASECOMPLETE
RELEASEB-CHANNEL
RELEASEINDICATION
STOPT305
NOTE 1 : THE SAME CAUSE IS SENT AS IN THE ORIGINALDISCONNECT MESSAGE (REF. SECTION 5.3.3).
Figure 51: User side SDL diagram
Page 63ETS 300 102-2: December 1990
+
12DISCONNECTINDICATION
RELEASEREQUEST
DISCONNECTB-CHANNEL
RELEASE
STARTT308
19
INFOREQUEST
INFO
12 12
INFOINDICATION
INFO RELEASE RELEASECOMPLETE
RELEASEINDICATION
RELEASEB-CHANNEL
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECOMPLETE
RELEASECR
0
0
RELEASECR
5.3.4 5 5 5.8.4 5.8.4
Figure 52: User side SDL diagram
Page 64ETS 300 102-2: December 1990
15SUSPENDREQUEST
TIMEOUTT319
SUSPENDCONFIRM(TIMEOUTERROR)
10
DISCONNECT
STOPT319
DISCONNECTINDICATION
12
15 15
INFOINDICATION
NOTIFYINDICATION
INFO NOTIFY RELEASE
STOPT319
RELEASEINDICATION
RELEASEB-CHANNEL
RELEASECOMPLETE
RELEASECR
0
5.6.3 5.3.4 5.3.5 5.8.4
5.95.6.45.6.2
SUSPENDREJECT
RELEASECOMPLETE
SUSPENDACKNOWLEDGE
5.6.2
+
5.6.3 5.8.4
STOPT319
STOPT319
STOPT319
SUSPENDCONFIRM
SUSPENDCONFIRM(ERROR)
RELEASEB-CHANNEL
RELEASEINDICATION
RELEASECR
0
10RELEASEB-CHANNEL
RELEASECR
0
Figure 53: User side SDL diagram
Page 65ETS 300 102-2: December 1990
+
17RESUMEREQUEST
TIMEOUTT318
RELEASE
STARTT308
19 STARTT308
19
RELEASE
STOPT318
DISCONNECT RELEASE RELEASECOMPLETE
RESUMEACK
RESUMEREJECT
STOPT318
STOPT318
STOPT318
STOPT318
RELEASEINDICATION
RELEASEB-CHANNEL
RESUMECONFIRM
RESUMECONFIRM(TIMEOUTERROR)
RELEASECR
0
RELEASECR
RELEASECR
0 0
10
CONNECTTO
B-CHANNEL
RELEASECOMPLETE
RELEASEINDICATION
NOTE 1
5.6.5 5.3.4 5.6.55.6.45.8.45.8.4
NOTE 1: CAUSE #102 "RECOVERY ON TIMER EXPIRY"SENT IN THE RELEASE MESSAGE(REF. 5.3.2f)
Figure 54: User side SDL diagram
Page 66ETS 300 102-2: December 1990
NOTE 2
NOTE 1
+
19RELEASEREQUEST
TIMEOUTT308
FIRSTTIMEOUT
RELEASE RELEASECOMPLETE DISCONNECT STATUS
(CS) INFO
CAUSEVALUE #30
?
STOP T322IF RUNNING
19
0
STOPT308
STOPT308
RELEASECONFIRM
RELEASEB-CHANNEL
IF NECESSARY
RELEASECR
0
RELEASECR
RELEASEB-CHANNEL
IF NECESSARY
RELEASECONFIRM
19
CS=0?
STOPT308
STATUSINDICATION
(ERROR)
RELEASEB-CHANNEL
IF NECESSARY
RELEASECR
0
INFOINDICATION
19
PLACEB-CHANNEL INMAINTENANCE
CONDITION
RELEASECONFIRM(ERROR)
RELEASE
RESTARTT308
19
RELEASEB-CHANNEL
IF NECESSARY
RELEASECR
0
5.3.4.3 5.3.5 5.3.4 5.8.11 5
NOTE 1:
NOTE 2:
THIS MESSAGE MAY BE RECEIVEDIN THE CASE OF CLEAR COLLISION.
THE OPTION OF PLACING THE B-CHANNEL IN THE MAINTENANCE CONDITIONIS NOT APPLICABLE IN THE CASE OF POINT-TO-MULTIPOINT CONFIGURATIONS(REF SECTION 5.3.4.3)
Y
N
Y
N
N
Y
Figure 55: User side SDL diagram
Page 67ETS 300 102-2: December 1990
25OVERLAP
RECEIVING
TIMEOUTT302
DISCONNECTREQUEST
ALERTINGREQUEST
PROCEEDINGREQUEST
SETUPRESPONSE
PROGRESSREQUEST
STOPT302
IF RUNNING
STOPT302
IF RUNNING
STOPT302
IF RUNNING
STOPT302
IF RUNNING
STOPT302
IF RUNNING
DISCONNECTB-CHANNEL
IF NECESSARYALERTING CALL
PROCEEDING CONNECT PROGRESS
DISCONNECT 7 9 STARTT313
8
25
STARTT305
11
ISCALL INFODEFINITELY
INCOMPLETE?
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
STARTT306
11
WHICHMESSAGE
?
ALERTING CALLPROCEEDING
97
8
STARTT313
CONNECT
NOTE 1 NOTE 1 NOTE 1 NOTE 1
NOTE 2NOTE 2NOTE 2NOTE 2
NOTE 2 NOTE 2 NOTE 2
CONN ALERT CALL PROC
NOTE 1
5.2.4 5.2.4 5.2.4 5.2.4 5.2.65.2.75.2.4
+ + +
DISCONNECTINFORELEASERELEASECOMPLETE
INFO
INFOREQUEST
25
STOPT302
IF RUNNING
STOPT302
IF RUNNING
STOPT302
IF RUNNING
RELEASEB-CHANNEL
INFOINDICATION
DISCONNECTINDICATION
1225
RESTARTT302
RELEASEINDICATION
RELEASEB-CHANNEL
RELEASECOMPLETE
RELEASECR
0
RELEASEINDICATION
RELEASECR
0
5.2.45.8.45.8.45
NOTE 1 NOTE 1 NOTE 1
NOTE 1
NOTE 1 :
NOTE 2 :
T302 IS OPTIONAL
IN THE POINT TO POINT CASE,CONNECTION TO THE B-CHANNELMAY BE MADE AT THIS POINT.(REF. 5.2.3.1d)
5.3.4
Y
N
Figure 56: User side SDL diagram
Page 68ETS 300 102-2: December 1990
2 25
DL-ESTABLISHINDICATION
DL-ESTABLISHINDICATION
STOPT304
STOPT302
ERRORINDICATION
DISCONNECTB-CHANNEL
IF NECESSARY
DISCONNECT
STARTT305
11
ANY STATEEXCEPT
2, 25
DL-ESTABLISHINDICATION
SAMESTATE
ANY STATEEXCEPT
0
UNEXPECTEDMESSAGE
UNRECOGNISEDMESSAGE SETUP
SAMESTATE
T322RUNNING
? STATUS
STATUSENQUIRY
STARTT322
SAMESTATE
5.8.3.2(e)5.8.45.8.45.8.85.8.85.8.8
TIMEOUTT322
STATUSENQUIRY
STATUSENQUIRYREQUEST
5.8.10 5.8.10 5.8.10
STATUS
SAMESTATE
T322RUNNING
?
STATUSENQUIRY
STARTT322
SAMESTATE
STATUSMESSAGERECEIVED
?
NOTE 6
NOTE 6
NOTE 4
MAX No.RETRANSMISSIONS
EXCEEDED?
RELEASE(CAUSE #41) STATUS
ENQUIRY
STARTT322
SAMESTATE
NOTE 6
RELEASEINDICATION
(ERROR)
STARTT308
19
NOTE 1 :-
NOTE 2 :-
NOTE 3 :-
NOTE 4 :-
NOTE 5 :-
NOTE 6 :-
T304 IS OPTIONAL
CAUSE #41 IS SENT IN THEDISCONNECT MESSAGE
"UNEXPECTED MESSAGE" AND"UNRECOGNISED MESSAGE" DO NOTINCLUDE RELEASE AND RELEASE COMPLETE
ACTIONS AFTER EXPIRY OF T322WHEN A STATUS MESSAGE HAS BEENRECEIVED ARE IMPLEMENTATION DEPENDENT
CAUSE #30 SHALL BE SENTIN THE STATUS MESSAGE
T322 MUST BE STOPPED IF ANY CLEARINGMESSAGE IS RECEIVED BEFORE IT EXPIRES
NOTE 2
NOTE 3 NOTE 3
NOTE 1
Y
N
NOTE 5
Y
N
NN
YY
Figure 57: User side SDL diagram
Page 69ETS 300 102-2: December 1990
NOTE 2
2OVERLAPSENDING
DL-RELEASEINDICATION
SETUPCONFIRM(ERROR)
STOPT304
RELEASEB-CHANNEL
IF NECESSARY
RELEASECR
0
0NULL
DL-RELEASEINDICATION
0
25OVERLAP
RECEIVING
DL-RELEASEINDICATION
RELEASEINDICATION
(ERROR)
STOPT302
DL-RELEASEINDICATION
RELEASECR
0
ANY STATEEXCEPT
0, 2, 10, 25
DL-RELEASEINDICATION
ERRORINDICATION
STOP ALL TIMERS
RELEASEB-CHANNEL
IF NECESSARY
RELEASECR
0
10ACTION
T309RUNNING
?
STARTT309
DL-ESTABLISHREQUEST
10ACTIVE
RELEASEB-CHANNEL
IF NECESSARY
T309 IS OPTIONAL IN THE USER SIDE
NO TEXT FOR THIS EVENT
NOTE 1
5.8.9 5.8.9 5.8.9 5.8.9
NOTE 1:
NOTE 2:
N
Y
Figure 58: User side SDL diagram
Page 70ETS 300 102-2: December 1990
T322RUNNING
?
STATUSENQUIRY
STARTT322
STATUS
STOPT309
IF RUNNING
DL-ESTABLISHCONFIRMATION
10ACTIVE
TIMEOUTT309
10ACTIVE
ERRORINDICATION
RELEASEB-CHANNEL
IF NECESSARY
RELEASECR
0
NOTE 3
5.8.9 5.8.9
ANY STATEEXCEPT
0, 19
STATUS(CS=M)
T322RUNNING
?
CAUSE=#97
?
CAUSE=#30
?
STOPT322
SAMESTATE
SAVE CAUSEAND
CALL STATE
M=0?
COMPATIBLESTATE
ERRORINDICATION
ERRORINDICATION
RELEASE
STARTT308
19
0
RELEASEB-CHANNEL
IF NECESSARY
RELEASECR
NOTE 2
5.8.10, 5.8.11
NOTE 1:
NOTE 2:
NOTE 3:
T309 IS OPTIONAL IN THE USER SIDE
ACTION ON RECEIPT OF STATUS INDICATING A COMPATIBLECALL STATE IS IMPLEMENTATION DEPENDENT
T322 MUST BE STOPPED ON RECEIPT OF A CLEARINGMESSAGE
NOTE 1
N
Y
N
N
Y
Y
Y
N
Y
N
Y
N
Figure 59: User side SDL diagram
Page 71ETS 300 102-2: December 1990
GLOBAL CALL REFERENCE
STATUS
REST 0
RESTART
REST 0NULL
UNEXPECTEDMESSAGE
MANAGEMENTRESTARTREQUEST
STATUS
REST 0
N=0
RESTART
STARTT316
AREANY OF THE
INDICATED CHANNELSALLOWED TO BE
RESTARTED ?
TRANSLATE INTOINDIVIDUAL CALL
REFERENCESSTATUS
REST 0
ANYESTABLISHED CALL
REFERENCE ASSOCIATEDWITH THE
INDICATEDCHANNEL ?
RESTARTREQUEST
T317STARTED ?
STARTT317
RESTARTCONFIRM
ALLINDICATED
CHANNELS ?
REST 2
TO Q.931 PROTOCOL CONTROLSPECIFIED CALLREFERENCES
5.8.3.2 (f)5.5.2 5.5.1
+ +
FROM SYSTEMMANAGEMENT
THE IDENTITYOF THECHANNEL TOBE RESTARTIS INCLUDED
ANYESTABLISHED CALL
REFERENCE ASSOCIATEDWITH THE
INDICATEDCHANNEL ?
RESTARTREQUEST
T317STARTED ?
STARTT317
RESTARTCONFIRM
ALLINDICATED
CHANNELS ?
REST 1
TO Q.931PROTOCOLCONTROLSPECIFIED CALLREFERENCES
ANYSTATE
STOPANY TIMERS
RELEASEINDICATION
FROM GLOBAL CALLREFERENCE CONTROL
RELEASEB-CHANNEL
IF NECESSARY
RELEASECR
RESTARTCONFIRM
0
TO GLOBAL CALLREFERENCE CONTROL
NOTE 1: REF. SECTION 5.5
ALL FLAGS (e.g. "REST ACK, T317 EXPIRED, REST RESP") CLEAREDALL TIMERS STOPPED
RESTARTREQUEST
Y
N
Y
N
N
Y
N
Y
Y
N
Y
N
Y
N
NOTE 1
Figure 60: User side SDL diagram
Page 72ETS 300 102-2: December 1990
GLOBAL CALL REFERENCE
STATUS TIMEOUTT316
N=N+1INCOMPATIBLE
CALL STATE?
STOP ALLTIMERS, IF ANYARE RUNNING
INCLUDE ANYRELEVANT INFO
RECEIVED IN STATUS
MANAGEMENTRESTART CONFIRM
REST 0
N=2
INDICATE THATRESTART HAS
FAILED
MANAGEMENTRESTARTCONFIRM
REST 0
RESTART
STARTT316
REST 1
INFORM LAYERMANAGEMENT
REST 1
MANAGEMENTRESTART CONFIRM
REST 0
RESTARTACKNOWLEDGE
STOPT316
REST RESPON ?
AREALL REQUESTED
CHANNELSACKNOWLEDGED
?
T317 EXPIREDON ?
INDICATE RESTARTSUCCESSFULLY
COMPLETED
INCLUDE THEIDENTITY OF THE
NON-RESTARTED CH.
UNEXPECTEDMESSAGE
STATUS
REST 1
STORE CHANNEL ID.RECEIVED IN THE
RESTART ACKNOWLEDGE
REST ACK ON
REST 1
RESTARTCONFIRM
ALLRESPONSES
?
STOPT317
STORECHANNEL ID.
REST 1
RESTACKON
REST RESPON
REST 1
AREALL REQUESTED
CHANNELSACKNOWLEDGED
?
INDICATE RESTARTSUCCESSFULLY
COMPLETED
INCLUDE THEIDENTITY OF THENON-RESTARTED
CHANNEL
MANAGEMENTRESTARTCONFIRM
REST 0
REST 1
T317 EXPIRED ON
RESTACK ON
?
TIMEOUTT317
REST 1RESTARTREQUEST
NOTE 1:
NOTE 2:
DEFAULT MAXIMUM VALUE OF N IS 2
T317 IS OPTIONAL (REF. SECTION 9.2)
5.8.3.2 (f)5.5.15.5.1
5.5.2
N
NOTE 1
Y
Y
N
Y
N
Y
Y
N
N
Y
N
N
Y
Y
NN
Y
Figure 61: User side SDL diagram
Page 73ETS 300 102-2: December 1990
GLOBAL CALL REFERENCE
REST 2R E S T A R T
S T A T U S
INCOMPATIBLECALL STATE
?
I N F O R ML A Y E R
M A N A G E M E N T
REST 2
T I M E O U TT317
R E S T A R TC O N F O R M
UNEXPECTED
MESSAGE
S T A T U S
REST 2
ALLR E S P O N S E S
?
S T O PT317 S T O R E
CHANNEL ID.ANY
C H A N N E LR E S T A R T E D
?
MAINTENANCEACTION
REST 0
INCLUDE ID.OF RESTARTED
C H A N N E L S
R E S T A R TA C K N O W L E D G E
REST 0
REST 2
5.8.3.2 (f)5.5.25.5.2
N
Y
Y
N
Y
N
Figure 62: User Side SDL Diagram
Page 74ETS 300 102-2: December 1990
History
Document history
December 1990 First Edition
February 1996 Converted into Adobe Acrobat Portable Document Format (PDF)