ETSI EN 300 403-2 V1.3.1 (2000-11)European Standard (Telecommunications series)

Integrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;

Signalling network layer for circuit-mode basic call control;Part 2: Specification and Description

Language (SDL) diagrams

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)2

ReferenceREN/SPAN-05210-2

KeywordsISDN, DSS1, layer 3, SDL

ETSI

650 Route des LuciolesF-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 CAssociation à but non lucratif enregistrée à laSous-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 orperceived 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 drivewithin 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://www.etsi.org/tb/status/

If you find errors in the present document, send your comment to:editor@etsi.fr

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 2000.All rights reserved.

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)3

Contents

Intellectual Property Rights ..........................................................................................................................4

Foreword......................................................................................................................................................4

1 Scope..................................................................................................................................................5

2 References ..........................................................................................................................................5

3 Definitions, symbols and abbreviations ...............................................................................................63.1 Definitions .................................................................................................................................................. 63.2 Symbols ...................................................................................................................................................... 73.3 Abbreviations.............................................................................................................................................. 7

4 User side and network side call states..................................................................................................8

5 Network side SDL diagrams - overview..............................................................................................95.1 Call states.................................................................................................................................................... 95.2 Block diagram............................................................................................................................................. 95.3 List of primitives ....................................................................................................................................... 105.4 Representation method .............................................................................................................................. 10

6 User side SDL diagrams - overview ..................................................................................................136.1 Call states.................................................................................................................................................. 136.2 Block diagram........................................................................................................................................... 136.3 List of primitives ....................................................................................................................................... 146.4 Representation method .............................................................................................................................. 14

7 Restart SDL diagrams - overview......................................................................................................147.1 States related to the restart procedure ......................................................................................................... 147.2 Block diagram........................................................................................................................................... 157.3 List of primitives exchanged with system management .............................................................................. 157.4 Representation method .............................................................................................................................. 15

8 Graphical SDL diagrams...................................................................................................................168.1 Network side SDL diagrams...................................................................................................................... 178.2 User side SDL diagrams ...........................................................................................................................1028.3 Restart SDL diagrams...............................................................................................................................158

Annex A (informative): Relevant differences to ETS 300 102-2.................................................... 166

A.1 Structural changes........................................................................................................................... 166

A.2 Technical changes........................................................................................................................... 167

History ..................................................................................................................................................... 168

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)4

Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI inrespect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Webserver (http://www.etsi.org/ipr).

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Webserver) which are, or may be, or may become, essential to the present document.

ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee Services andProtocols for Advanced Networks (SPAN).

The present document which is based on ITU-T Recommendation Q.931 (1993) [7] is an extended and updated versionof ETS 300 102-2 (1990) which was based on ITU-T Recommendation Q.931 (1988). Annex A identifies the relevantdifferences between the present document and ETS 300 102-2.

The present document is part 2 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) signalling network layer for circuit-mode basic call control, as described below:

Part 1: "Protocol specification [ITU-T Recommendation Q.931 (1993), modified]";

Part 2: "Specification and Description Language (SDL) diagrams";

Part 3: "Protocol Implementation Conformance Statement (PICS) proforma specification";

Part 4: "Test Suite Structure and Test Purposes (TSS&TP) specification for the user";

Part 5: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the user";

Part 6: "Test Suite Structure and Test Purposes (TSS&TP) specification for the network";

Part 7: "Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the network".

National transposition dates

Date of adoption of this EN: 27 October 2000

Date of latest announcement of this EN (doa): 31 January 2001

Date of latest publication of new National Standardor endorsement of this EN (dop/e): 31 July 2001

Date of withdrawal of any conflicting National Standard (dow): 31 July 2001

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)5

1 ScopeThe present document specifies the stage three of circuit-mode on-demand basic telecommunication services for thepan-European Integrated Services Digital Network (ISDN) as provided by European telecommunications operators atthe T reference point or coincident S and T reference point (as defined in ITU-T Recommendation I.411 [3]) by meansof the Digital Subscriber Signalling System No. one (DSS1). Stage three identifies the protocol procedures andswitching functions needed to support a telecommunication service (see ITU-T Recommendation I.130 [2]).

In addition, the present document specifies the protocol requirements at the T reference point where the service isprovided to the user via a private ISDN.

NOTE 1: Procedures at the T reference point, to support the access of a private ISDN to the public ISDN, are notexplicitly identified in the present document, however some procedures are applicable only to the Treference point.

The present document does not specify the additional protocol requirements where the service is provided to the uservia a telecommunication network that is not an ISDN.

The present document is specified using the Specification and Description Language (SDL) as specified inITU-T Recommendation Z.100 [4].

In order to describe the point-to-multipoint operation of the protocol, the concept of a "global" process running inparallel with a number of "individual" (dynamic) processes has been introduced. This approach, and the associateddefinition of internal primitives is intended to provide a coherent description of the protocol and does not constrainimplementations. The SDL diagrams in this part, and the text of clause 5 of ETS 300 403-1 [1], together provide acomplete specification of the protocol within the scope of the present document.

A basic telecommunication service is a fundamental type of service. It forms the basis on which supplementary servicesmay be added.

NOTE 2: Specific requirements of individual circuit-mode basic telecommunication services are not covered in thepresent document. However, ETR 018 [5] gives guidance on the use of service specific informationelements to implement individual basic telecommunication services.

The method of testing of the present document is common with that for ETS 300 403-1 [1]. Further parts of the presentdocument specify the method of testing and detailed application specific requirements to determine conformance basedon the present document.

The present document is applicable to equipment supporting circuit-mode on-demand basic telecommunicationservices, to be attached at either side of a T reference point or coincident S and T reference point when used as anaccess to the public ISDN.

2 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.

• References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.

• For a specific reference, subsequent revisions do not apply.

• For a non-specific reference, the latest version applies.

• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.

[1] ETSI ETS 300 403-1 (1995): "Integrated Services Digital Network (ISDN); Digital SubscriberSignalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic callcontrol; Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)6

[2] ITU-T Recommendation I.130 (1988): "Method for the characterization of telecommunicationservices supported by an ISDN and network capabilities of an ISDN".

[3] ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".

[4] ITU-T Recommendation Z.100 (1988): "Specification and description language (SDL)".

[5] ETSI ETR 018: "Integrated Services Digital Network (ISDN); Application of the BearerCapability (BC), High Layer Compatibility (HLC) and Low Layer Compatibility (LLC)information elements by terminals supporting ISDN services".

[6] ETSI ETS 300 102-2: "Integrated Services Digital Network (ISDN); User-network interfacelayer 3; Specifications for basic call control; Specification Description Language (SDL)diagrams".

[7] ITU-T Recommendation Q.931: "ISDN user-network interface layer 3 specification for basic callcontrol".

3 Definitions, symbols and abbreviations

3.1 DefinitionsFor the purposes of the present document, the following terms and definitions apply in addition to those given inETS 300 403-1 [1]:

point-to-multipoint configuration; multipoint terminal configuration; multipoint configuration: terminalconfiguration in which there is more than one signalling entity

point-to-multipoint data link; broadcast data link: data link connection with the capability to support more than twoconnection endpoints

point-to-point configuration; single-point terminal configuration; single-point configuration: terminalconfiguration in which there is one signalling entity

point-to-point data link: data link on which a frame is directed to a single endpoint

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)7

3.2 SymbolsFor the purposes of the present document, the following symbols apply. A full description of the symbols and theirmeaning and application is given in ITU-T Recommendation Z.100 [4].

State symbol

Input symbol (event occurrence)

Output symbol (signal generation which will lead to an associated eventoccurrence)

Save symbol (save event until completion of a transition)

Task symbol

Decision symbol

Procedure call symbol

Transition option symbol (implementation option)

Procedure start symbol

Procedure return symbol

Create request symbol (used to initiate an individual network sidetransaction)

Stop symbol (used to end an individual network side transaction)

Connection symbol

Used mark (an input which is local to the layer 3 entity and whichis required as a result of the representation approach adopted)

3.3 AbbreviationsFor the purposes of the present document, the following abbreviations apply:

CES Connection Endpoint SuffixDSS1 Digital Subscriber Signalling System No. oneISDN Integrated Services Digital NetworkSDL Specification and Description Language

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)8

4 User side and network side call statesTable 1 shows which call states are applicable at the user and network sides during the various phases of a call.

Table 1: Call states

Call phase Call state User NetworkIDLE Null U0 N0OUTGOING CALL(from user)

Call initiatedOverlap sendingOutgoing call proceedingCall delivered

U1U2U3U4

N1N2N3N4

INCOMING CALL(to user)

Call presentOverlap receivingIncoming call proceedingCall receivedConnect request

U6U25U9U7U8

N6N25N9N7N8

ACTIVE Active U10 N10CALL CLEARING Disconnect request (clearing by the user)

Disconnect indication (clearing by the network)Release requestCall abort

U11U12U19-

N11N12N19N22

CALL SUSPEND/RESUME

Suspend requestResume request

U15U17

N15N17

RESTARTPROCEDURE (note)

Restart nullRestart requestRestart

REST0REST1REST2

REST0REST1REST2

NOTE: These states relate to global call references and are applicable when the restart procedures are used.They may exist in both user and network sides.

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)9

5 Network side SDL diagrams - overview

5.1 Call states

Table 2: Network side call states

Call state NameN0 NullN1 Call initiatedN2 Overlap sendingN3 Outgoing call proceedingN4 Call deliveredN6 Call presentN7 Call receivedN8 Connect requestN9 Incoming call proceedingN10 ActiveN11 Disconnect requestN12 Disconnect indicationN15 Suspend requestN17 Resume requestN19 Release requestN22 Call abortN25 Overlap receiving

NOTE 1: Network side timers, and the states in which they run, are specified in clause 9 of ETS 300 403-1 [1].NOTE 2: Events in each state which lead to normal call establishment and clearing are marked with the "+" symbol.NOTE 3: The primitives which pass to and from the call control block are shown for guidance only and are not fully

specified.NOTE 4: Internal primitives are marked by "*". These are a result of the representation method that has been

adopted.

5.2 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

Primitives

(note 1)

NOTE 1: Interface not described in the SDL diagrams.NOTE 2: Control of B-channels is described in these SDL diagrams as part of the Q.931 protocol block.

Figure 1: Block diagram for the network side

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)10

5.3 List of primitives

Table 3: List of primitives

From call control block To call control blockALERTING REQUESTDISCONNECT REQUESTINFO REQUESTMORE INFO REQUESTNOTIFY REQUESTPROCEEDING REQUESTPROGRESS REQUESTREJECT REQUESTRELEASE REQUESTRESUME REJECT REQUESTRESUME RESPONSESETUP COMPLETE REQUESTSETUP REQUESTSETUP RESPONSESTATUS ENQUIRY REQUESTSUSPEND REJECT REQUESTSUSPEND RESPONSERESTART REQUEST (note 1)

ALERTING INDICATIONCONNECT INDICATIONDISCONNECT INDICATIONINFO INDICATIONMORE INFO INDICATIONNOTIFY INDICATIONPROCEEDING INDICATIONPROGRESS INDICATIONRELEASE CONFIRMRELEASE INDICATIONRESUME INDICATIONSETUP CONFIRMSETUP INDICATIONSTATUS INDICATIONSUSPEND INDICATIONTIMEOUT INDICATIONRESTART CONFIRM (note 2)

NOTE 1: This primitive may be received from global call reference control.NOTE 2: This primitive is sent to global call reference control.

5.4 Representation methodIn order to describe the point-to-multipoint operation of the protocol, the concept of a "global" process running inparallel with a number of "individual" (dynamic) processes in the network side has been introduced. This approach, andthe associated definition of internal primitives, is intended to provide a coherent description of the protocol and does notconstrain implementation. The textual description in clause 5 of ETS 300 403-1 [1] is definitive.

Individual processes are used to track the responses of each terminal. The global (controlling) process runs in parallelwith the (dynamically created/destroyed) individual process.

The global and individual processes communicate by means of internal primitives. These are related to layer 3 messagestypes and are defined in table 4. The internal primitives represent instantaneous actions. Thus, there is no possibility oferrors caused by the crossover of primitives.

The global process maintains a list of recorded Connection Endpoint Suffix (CES) values to enable it to manage theindividual processes. In this representation the global process also keeps a record of the state of the individual processassociated with each responding terminal. Additionally a "preselected" CES is recorded when one terminal respondswith a CONNECT message and this becomes the "selected" CES when the terminal is awarded the call.

This solution is compatible with point-to-point configurations. In this case the global process never creates anyindividual processes, and the timers defined in ETS 300 403-1 [1] for the relevant states are handled by the globalprocess, including timer T322 which may run in any state except the Null state. Also, ever since a transition to the Nullstate occurs, the stopping of this timer (if running) should be regarded as an implicit statement, as it is not shown inorder not to extend the SDL representation.

In a point-to-multipoint configuration, individual processes may exist in the following states:

N0 Null (processes are created in this state);

N7 Call received;

N8 Connect request;

N9 Incoming call proceeding;

N19 Release request;

N25 Overlap receiving.

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)11

Two sets of SDL diagrams are required for these states to show the global and individual processes.

The global process handles all communications with call control. Messages from individuals terminals are sent to theindividual process for that terminal if one exists (i.e. if the CES is recognized). Messages with an unrecognized CES arepassed to the global process. Messages with the selected CES are also sent to the global process.

In a point-to-multipoint configuration, the handling of the timers defined in ETS 300 403-1 [1] has been done accordingto the following principles:

a) timers T301 and T310 only run in the global process when an incoming call is being offered;

b) timers T304, T308 and T322 only run in the individual processes when an incoming call is being offered. Thestopping of timer T322 (if running) when an individual process is destroyed should be regarded as an implicitstatement as it is not shown in order not to extend the SDL representation;

c) in the other phases of a call, the timers associated with each state, as well as timer T322 which may run in anystate except the Null state, are all handled by the global process. Once again, the stopping of this timer (ifrunning) should be regarded as an implicit statement because it extends the SDL representation.

Table 4: Network side layer 3 internal primitives

Primitive name From To MeaningINT. ALERTING REQINT. CONNECT REQINT. CALL PROC REQINT. SETUP ACK REQ

Global Individual When global process receives ALERTING it starts anindividual process and sendsINT. ALERTING REQ to it(etc.)

INT. ALERTING INDINT. CONNECT INDINT. CALL PROC IND

Individual Global Sent on receipt of ALERTING(etc.)

END PROCESS Global Individual Sent when the global process terminates an individualprocess

INT. RELEASE REQ Global Individual Instructs individual process to release terminal (e.g. forreleasing non-selected terminals)

INT. RELEASE IND Individual Global Informs global process that a terminal has begun torelease

INT. INFO REQ Global Individual Sent on receipt of INFO REQINT. INFO IND Individual Global Sent on receipt of INFOINT. STAT. ENQ. REQ Global Individual Sent on receipt of STATUS ENQUIRY REQINT. PROGRESS IND Individual Global Sent on receipt of PROGRESSINT. REL. COMP. IND Individual Global Sent to indicate that the individual process has been

clearedNOTE: The global process should not release the call reference until all individual processes have completed

clearing.

Figure 2 (an arrow diagram) shows an example of this representation method.

ET

SI

ET

SIE

N300

403- 2V

1.3.1(2000-11)

12

Terminal 1 Terminal 2 Terminal 3 Network

SETUP (BROADCAST)0

SETUP REQ

ALERTINGT303ALERTING IND

INT. ALERTING REQ

7iALERTING

ALERTING

INT. ALERTING REQ

7i

INT. ALERTING REQ

7i INT. CONNECT INDCONNECT

END PROCESS

8i

RELEASE INT. RELEASE REQ

RELEASE

RELEASE COMPLETE

INT. RELEASE REQ19i T308

6

T312

CONNECT IND

10T312 expires(no state change)

19i T308INT. REL. COMP. IND

RELEASE COMPLETE INT. REL. COMP. IND

CONNECT ACK

CONNECT ACK REQ

7

Figure 2: Multipoint call establishment (and clearing of non-selected terminals)

8

NOTE: o = creation of state machine, x = deletion of state machine; numbers indicate states of the state machines shown.

x

x

x

o

o

o

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)13

6 User side SDL diagrams - overview

6.1 Call states

Table 5: User side call states

Call state NameU0 NullU1 Call initiatedU2 Overlap sendingU3 Outgoing call proceedingU4 Call deliveredU6 Call presentU7 Call receivedU8 Connect requestU9 Incoming call proceedingU10 ActiveU11 Disconnect requestU12 Disconnect indicationU15 Suspend requestU17 Resume requestU19 Release requestU25 Overlap receiving

NOTE 1: User side timers, and the states in which they run, are specified in clause 9 of ETS 300 403-1 [1].NOTE 2: Events in each state which lead to normal call establishment/clearing are shown by the "+" symbol.NOTE 3: Primitives passed to and from the call control (user application) block are shown for guidance only and are

not fully specified.

6.2 Block diagram

Call control Resource management

Procedurecall

Q.931 protocol control

Messages to/fromUser side

Data link layer

Physical layer

User-networkinterface

Network

Blockdescribedby the SDLdiagrams

Primitives

(note 1)

NOTE 1: Interface not described in the SDL diagrams.NOTE 2: Control of B-channels is described in these SDL diagrams as part of the Q.931 protocol block.

Figure 3: Block diagram for the user side

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)14

6.3 List of primitives

Table 6: List of primitives

From call control block To call control blockALERTING REQUESTDISCONNECT REQUESTINFO REQUESTMORE INFO REQUESTNOTIFY REQUESTPROCEEDING REQUESTPROGRESS REQUESTREJECT REQUESTRELEASE REQUESTRESUME REQUEST (note 1)SETUP REQUESTSETUP RESPONSESTATUS ENQUIRY REQUESTSUSPEND REQUEST (note 1)RESTART REQUEST (note 2)

ALERTING INDICATIONDISCONNECT INDICATIONINFO INDICATIONMORE INFO INDICATIONNOTIFY INDICATIONPROCEEDING INDICATIONPROGRESS INDICATIONRELEASE CONFIRMRELEASE INDICATIONRESUME CONFIRMSETUP COMPLETE INDICATIONSETUP CONFIRMSETUP INDICATIONSTATUS INDICATIONSUSPEND CONFIRMRESTART CONFIRM (note 3)

NOTE 1: These primitives are not defined for a primary rate access, i.e. the use of the callrearrangement procedure is restricted to basic access.

NOTE 2: This primitive may be received from global call reference control.NOTE 3: This primitive is sent to global call reference control.

6.4 Representation methodThe representation method of user side SDL diagrams has not followed the concept of a global process running inparallel with a number of individual processes, because from a signalling point of view only one call is handled by theglobal process at each time. Therefore, the global process never creates any individual processes, and only one set ofSDL diagrams is required to represent the user side call states.

As a consequence, the timers associated with each state, as well as timer T322 which may run in any state except theNull state, are all handled by the global process. Also, as mentioned for the network side, the stopping of this timer (ifrunning) should be regarded as an implicit statement because it extends the SDL representation.

7 Restart SDL diagrams - overview

7.1 States related to the restart procedure

Table 7: States related to the restart procedure

Call state NameREST0 Restart nullREST1 Restart requestREST2 RestartNOTE 1: Timers related to the restart procedure, and the states in which they run, are specified in clause 9 of

ETS 300 403-1 [1].NOTE 2: The primitives which pass to and from the system management block (see table 8) and the protocol

control block (see tables 3 and 6) are shown for guidance only and are not fully specified.

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)15

7.2 Block diagram

Call control Resource management

Procedurecall

Q.931 protocol control

Data link layer

Physical layer

User/Network

Blockdescribedby the SDLdiagrams

Global call reference control

(note)

NOTE: Interface not described in the SDL diagrams.

Figure 4: Block diagram for the restart procedure

7.3 List of primitives exchanged with system management

Table 8: List of primitives

From system management block To system management blockMANAGEMENT RESTART REQUEST TIMEOUT MANAGEMENT INDICATION

STATUS MANAGEMENT INDICATIONMANAGEMENT RESTART CONFIRM

NOTE: Primitives related to the restart procedure which may be sent or received to/from protocolcontrol block are already indicated in tables 3 and 6.

7.4 Representation methodThe representation method of the restart SDL diagrams follows the concept of a single finite state machine running inthe global call reference control block (see figure 4), in order to describe the restart procedure and the associated statesdefined in ETS 300 403-1 [1] subclause 5.5 and subclause 2.4, respectively.

Whenever a collision of restart procedures initiated by either side of the interface may occur, it shall be handled by aseparate finite state machine approach.

NOTE: Due to the complexity of the representation, this approach is not presented.

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)16

In this subset of diagrams, reference is made to some flags in order to make the SDL representation more transparent.The flags have the following meaning:

a) REST RESP: either by initiative of the management entity or because a RESTART message has been received,the global call reference control entity has sent primitives RESTART REQUEST to each protocol entityassociated with an active call reference, and is waiting for a reply from them. The flag is set when they all haveresponded;

b) REST ACK: by initiative of the management entity, the global call reference entity has sent a RESTARTmessage to its peer entity (in the network side or in the user side), and is waiting for a RESTARTACKNOWLEDGE. The flag is set when this message is received;

c) T317 EXPIRED: either by initiative of the management entity or because a RESTART message has beenreceived, the global call reference control entity has sent primitives RESTART REQUEST to each protocolentity associated with an active call reference, and is waiting for a reply from them. The flag is set if they havenot responded in due time, and timer T317 has expired.

8 Graphical SDL diagramsThis clause is separated into three subclauses:

- network side SDL diagrams (figure 5, sheets 1 to 85);

- user side SDL diagrams (figure 6, sheets 1 to 57);

- restart SDL diagrams (figure 7, sheets 1 to 7).

All references in the following diagrams are to ETS 300 403-1 [1].

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)17

8.1 Network side SDL diagrams

Process NETWORK_SIDE 1(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. THE EXPIRY OF TIMER T307 IS NOT SHOWN IN THESE SDLs AS IT RUNS IN THE CALL CONTROL BLOCK.

0NULL

RELEASE

5.8.3.2 (b)

ESTABLISHCR

RELEASECOMPLETE(CAUSE #81)

RELEASECR

0

RESUME

ACCESS?

ESTABLISHCR

RELEASECOMPLETE(CAUSE #81)

RELEASECR

0

ESTABLISHCR

RELEASE(CAUSE #81)

STARTT308

19

ESTABLISHCR

RESUMEINDICATION

17

5.65.6.45.6.5+

SETUP

5.1.15.1.2+

ESTABLISHCR

CHNLSELECTIONSUCCESS

?

RELEASECOMPLETE(CAUSE #34 OR #44)

RELEASECR

0

SETUPINDICATION

1

PRA

BRA

N

Y

Figure 5 (sheet 1 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)18

Process NETWORK_SIDE 2(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. ANY OTHER MESSAGE EXCEPT STATUS ENQUIRY, SEE PAGES DEALING WITH DIAGRAMS RELATED TO ANY GLOBAL OR INDIVIDUAL STATE.NOTE 2. CAUSE #101 IS RETURNED IF A STATUS MESSAGE IS RECEIVED, WHILE CAUSE #81 APPLIES FOR OTHER MESSAGES.

0NULL

RELEASECOMPLETE

5.8.3.2 (c)

0

OTHERMESSAGE

ESTABLISHCR

RELEASECOMPLETE(CAUSE #81 OR #101)

NOTE 2

RELEASECR

0

ESTABLISHCR

RELEASE(CAUSE #81 OR #101)

NOTE 2

STARTT308

19

5.8.3.2 (a),NOTE 1STATUS

5.8.11

CS=0?

0

N

Y

Figure 5 (sheet 2 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)19

Process NETWORK_SIDE 3(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. THIS INPUT MAY BE RECEIVED FROM A TERMINAL COMPLETING CLEARING IN A POINT-TO-MULTIPOINT CONFIGURATION. THE CALL REFERENCE SHOULD NOT BE RE-USED UNTILL ALL TERMINALS HAVE COMPLETED CLEARING.

0NULL

INT *REL COMPINDICATION(CES)

DELETECES

0

NOTE 1NOTIFYREQUEST

0

SETUPREQUEST

5.2.1+

CHNLSELECTIONSUCCESS

?

RELEASEINDICATION

0

SELECTCR

STARTT303

P-PSETUP

REQUEST?

STARTT312

SETUP(B/CAST)

6

SETUP(P-P)

6

N

Y

N

Y

Figure 5 (sheet 3 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)20

Process NETWORK_SIDE 4(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. INDIVIDUAL PROCESSES ARE CREATED IN THIS STATE.

OINULL

INT *ALERTINGREQUEST

7I

INT *RELEASEREQUEST(CAUSE)

STARTT308

RELEASE(CAUSE)

19I

INT *CALL PROCREQUEST

9I

INT *CONNECTREQUEST

8I

INT *SETUP ACKREQUEST

STARTT304

25I

INDIVIDUAL PROCESS,NOTE 1

Figure 5 (sheet 4 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)21

Process NETWORK_SIDE 5(85)

NETWORK SIDE SDL DIAGRAMS

1CALL

INITIATED

REJECTREQUEST(CAUSE)

RELEASECOMPLETE(CAUSE)

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

5.3.2 (a)PROCEEDINGREQUEST

CALLPROCEEDING(B-CHNL)

CONNECTB-CHNL

3

5.1.5.1+MORE INFO

REQUEST

5.1.3+

STARTT302

SETUP ACK(B-CHNL)

CONNECTB-CHNL

ANYDIGITS

RECEIVED?

2TONE

OPTION?

2

CONNECTDIALTONE

Y

N

N

Y

Figure 5 (sheet 5 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)22

Process NETWORK_SIDE 6(85)

NETWORK SIDE SDL DIAGRAMS

1CALL

INITIATED

RELEASECOMPLETE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

DISCONNECT

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECTINDICATION

11

5.3.3

Figure 5 (sheet 6 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)23

Process NETWORK_SIDE 7(85)

NETWORK SIDE SDL DIAGRAMS

2OVERLAPSENDING

PROCEEDINGREQUEST

STOPT302

CALLPROCEEDING

3

5.1.5.2+ ALERTING

REQUEST

STOPT302

ALERTING

4

5.1.7+ SETUP

RESPONSE

5.1.8+

STOPT302

CONNECT

10

Figure 5 (sheet 7 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)24

Process NETWORK_SIDE 8(85)

NETWORK SIDE SDL DIAGRAMS

2OVERLAPSENDING

INFOREQUEST

INFO

2

5PROGRESSREQUEST

5.1.6

PROGRESS

2

DISCONNECTREQUEST(CAUSE)

STOPT302

TONEOPTION

?

DISCONNECT(PI, CAUSE)

STARTTONE

STARTT306

12

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECT(CAUSE)

STARTT305

5.1.5.25.3.4

Y

N

Figure 5 (sheet 8 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)25

Process NETWORK_SIDE 9(85)

NETWORK SIDE SDL DIAGRAMS

2OVERLAPSENDING

RELEASECOMPLETE

STOPT302

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

STOPT302

RELEASEINDICATION

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECOMPLETE

RELEASECR

0

5.8.4

DISCONNECT

STOPT302

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECTINDICATION

11

5.3.3

Figure 5 (sheet 9 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)26

Process NETWORK_SIDE 10(85)

NETWORK SIDE SDL DIAGRAMS

2OVERLAPSENDING

TIMEOUTT302

CALL INFOINCOMPLETE

?

RELEASEINDICATION

TONEOPTION

?

DISCONNECT(PI, CAUSE #28)

STARTTONE

STARTT306

12

RELEASEB-CHANNEL IFNOT RELEASED

DISCONNECT(CAUSE #28)

STARTT305

TIMEOUTINDICATION

CALLPROCEEDING

3

5.1.5.2

INFO

5.1.3+

STOPT302

FIRSTINFO

MESSAGE?

INFOINDICATION

STARTT302

2

STOP ANYAPPLIED

DIAL TONE

Y

Y

N

N

N

Y

Figure 5 (sheet 10 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)27

Process NETWORK_SIDE 11(85)

NETWORK SIDE SDL DIAGRAMS

3OUTGOING CALL

PROCEEDING

DISCONNECTREQUEST(CAUSE)

TONEOPTION

?

DISCONNECT(PI, CAUSE)

STARTTONE

STARTT306

12

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECT(CAUSE)

STARTT305

5.1.5.15.3.4SETUP

RESPONSE

CONNECT

10

5.1.8+ALERTING

REQUEST

ALERTING

4

5.1.7+

Y

N

Figure 5 (sheet 11 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)28

Process NETWORK_SIDE 12(85)

NETWORK SIDE SDL DIAGRAMS

3OUTGOING CALL

PROCEEDING

INFO

5

INFOINDICATION

3

INFOREQUEST

INFO

3

5PROGRESSREQUEST

PROGRESS

3

5.1.6

Figure 5 (sheet 12 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)29

Process NETWORK_SIDE 13(85)

NETWORK SIDE SDL DIAGRAMS

3OUTGOING CALL

PROCEEDING

RELEASE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

DISCONNECT

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECTINDICATION

11

5.3.3RELEASECOMPLETE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

Figure 5 (sheet 13 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)30

Process NETWORK_SIDE 14(85)

NETWORK SIDE SDL DIAGRAMS

4CALL

DELIVERED

DISCONNECTREQUEST(CAUSE)

TONEOPTION

?

DISCONNECT(PI, CAUSE)

STARTTONE

STARTT306

12

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECT(CAUSE)

STARTT305

5.3.4SETUPRESPONSE

CONNECT

10

5.1.8+ PROGRESS

REQUEST

PROGRESS

4

5.1.6

Y

N

Figure 5 (sheet 14 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)31

Process NETWORK_SIDE 15(85)

NETWORK SIDE SDL DIAGRAMS

4CALL

DELIVERED

INFO

INFOINDICATION

4

5INFOREQUEST

INFO

4

5

Figure 5 (sheet 15 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)32

Process NETWORK_SIDE 16(85)

NETWORK SIDE SDL DIAGRAMS

4CALL

DELIVERED

DISCONNECT

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECTINDICATION

11

5.3.3RELEASECOMPLETE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

Figure 5 (sheet 16 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)33

Process NETWORK_SIDE 17(85)

NETWORK SIDE SDL DIAGRAMS

6CALL

PRESENT

SETUP ACK

5.2.35.2.45.3.2+

WASSETUPB/CAST

?

CHNLOK

?

STOPT303

MORE INFOINDICATION

STARTT304

25

STOPT303

RELEASE(CAUSE #6)

RELEASEINDICATION

STARTT308

19

CHNLOK

?

STOPT303

MORE INFOINDICATION

CREATEPROCESS

(CES)

INT *SETUP ACKREQUEST(CES)

25

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

6

N

Y

N

Y

Y

N

Figure 5 (sheet 17 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)34

Process NETWORK_SIDE 18(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. TIMER T301 IS NOT USED IF THE NETWORK IMPLEMENTS ANOTHER INTERNAL ALERTING SUPERVISION TIMING FUNCTION.

6CALL

PRESENT

ALERTING

5.2.35.2.5.25.3.2+

WASSETUPB/CAST

?

CHNLOK

?

STOPT303

RELEASE(CAUSE #6)

RELEASEINDICATION

STARTT308

19

STOPT303

ALERTINGINDICATION

STARTT301

NOTE 1

7

CHNLOK

?

STOPT303

ALERTINGINDICATION

CREATEPROCESS

(CES)

INT *ALERTINGREQUEST(CES)

STARTT301

NOTE 1

7

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

6

N

N

Y

Y

Y

N

Figure 5 (sheet 18 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)35

Process NETWORK_SIDE 19(85)

NETWORK SIDE SDL DIAGRAMS

6CALL

PRESENT

CONNECT

WASSETUPB/CAST

?

CHNLOK

?

STOPT303

SETUPCONFIRM

PRESELECTCES

CREATEPROCESS

(CES)

INT *CONNECTREQUEST(CES)

8

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

6

CHNLOK

?

STOPT303

SETUPCONFIRM

8

STOPT303

RELEASE(CAUSE #6)

RELEASEINDICATION

STARTT308

19

5.2.35.2.75.3.2+

Y

Y

N

N

Y

N

Figure 5 (sheet 19 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)36

Process NETWORK_SIDE 20(85)

NETWORK SIDE SDL DIAGRAMS

6CALL

PRESENT

CALLPROCEEDING

WASSETUPB/CAST

?

CHNLOK

?

STOPT303

PROCEEDINGINDICATION

STARTT310

9

STOPT303

RELEASE(CAUSE #6)

RELEASEINDICATION

STARTT308

19

CHNLOK

?

STOPT303

PROCEEDINGINDICATION

CREATEPROCESS

(CES)

INT *CALL PROCREQUEST(CES)

STARTT310

9

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

6

5.2.35.2.5.25.3.2+

N

Y

N

Y

Y

N

Figure 5 (sheet 20 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)37

Process NETWORK_SIDE 21(85)

NETWORK SIDE SDL DIAGRAMS

6CALL

PRESENT

RELEASE

WASSETUPB/CAST

?

STOPT303

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

RELEASECOMPLETE

6

5.8.4RELEASECOMPLETE

WASSETUPB/CAST

?

SAVECAUSE

6

STOPT303

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.2.25.2.5.3

N

Y Y

N

Figure 5 (sheet 21 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)38

Process NETWORK_SIDE 22(85)

NETWORK SIDE SDL DIAGRAMS

6CALL

PRESENT

INFOREQUEST

DISCONNECTREQUEST(CAUSE)

STOPT303

WASSETUPB/CAST

?

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

22

TONEOPTION

?

DISCONNECT(PI, CAUSE)

STARTTONE

STARTT306

12

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECT(CAUSE)

STARTT305

5.3.2 (e)5.3.4

Y

N

Y

N

Figure 5 (sheet 22 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)39

NETWORK SIDE SDL DIAGRAMS

Process NETWORK_SIDE 23(85)

NOTE 1. THIS PRIMITIVE MAY BE RECEIVED WHEN A TERMINAL IS CLEARED DUE TO AN INVALID CHANNEL IDENTITY IN RESPONSE TO THE SETUP.NOTE 2. THIS MESSAGE IS IDENTICAL TO THE ORIGINAL SETUP MESSAGE.

6CALL

PRESENT

INT *REL COMPINDICATION(CES)

NOTE 1

DELETECES

6

TIMEOUTT303

5.2.15.2.5.35.2.5.4

FIRSTTIMEOUT

?

WASSETUPB/CAST

?

SETUP(P−P)

NOTE 2

STARTT303

6

RELCOMPRCVD

?

SETUP(B/CAST)

NOTE 2

STARTT303

RESTARTT312

6

RELEASEB−CHANNEL IFNOT RELEASED

RELEASEINDICATION

22

WASSETUPB/CAST

?

DISCONNECTINDICATION

DISCONNECT(CAUSE #102)

STARTT305

12

Y

N

Y

N

Y

N

Y

N

Figure 5 (sheet 23 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)40

Process NETWORK_SIDE 24(85)

NETWORK SIDE SDL DIAGRAMS

7CALL

RECEIVED

SETUPACK

WASSETUPB/CAST

?

REPORTSTATUS

(CAUSE #97,#98 OR #101)

7

CHNLOK

?

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

7

CREATEPROCESS

(CES)

INT *SETUP ACKREQUEST(CES)

7

5.2.3, 5.2.45.3.2, 5.8.4+

CALLPROCEEDING

WASSETUPB/CAST

?

CHNLOK

?

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

7

CREATEPROCESS

(CES)

INT *CALL PROCREQUEST(CES)

7

5.2.3, 5.2.5.25.3.2, 5.8.4+

N

Y

N

Y

N

Y

N

Y

Figure 5 (sheet 24 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)41

Process NETWORK_SIDE 25(85)

NETWORK SIDE SDL DIAGRAMS

7CALL

RECEIVED

CONNECT

5.2.35.2.75.3.2+

WASSETUPB/CAST

?

CONNECTINDICATION

STOP T301IF IMPLEMENTED

8

CHNLOK

?

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

7

CONNECTINDICATION

STOP T301IF IMPLEMENTED

PRESELECTCES

CREATEPROCESS

(CES)

INT *CONNECTREQUEST(CES)

8

ALERTING

WASSETUPB/CAST

?

REPORTSTATUS

(CAUSE #97,#98 OR #101)

7

CHNLOK

?

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

7

CREATEPROCESS

(CES)

INT *ALERTINGREQUEST(CES)

7

5.2.3, 5.2.5.25.3.2, 5.8.4+

N

Y

N

Y

N

Y

N

Y

Figure 5 (sheet 25 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)42

Process NETWORK_SIDE 26(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, A STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY ALSO BE FOLLOWED. IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322 AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDTIONAL INFORMATION TO THE NETWORK.

7CALL

RECEIVED

PROGRESS

WASSETUPB/CAST

?

STATUSNOTE 2

7

PROGRESSINDICATION

7

5.2.65.8.4,NOTE 1INFO

WASSETUPB/CAST

?

INFOINDICATION

7

55.8.4,NOTE 1

Y

N

Y

N

Figure 5 (sheet 26 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)43

Process NETWORK_SIDE 27(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, A STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY ALSO BE FOLLOWED. IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322 AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDITIONAL INFORMATION TO THE NETWORK.

7CALL

RECEIVED

RELEASE

5.8.4

WASSETUPB/CAST

?

RELEASEINDICATION

RELEASECOMPLETE

STOP T301IF IMPLEMENTED

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

RELEASECOMPLETE

7

DISCONNECT

WASSETUPB/CAST

?

STOP T301IF IMPLEMENTED

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECTINDICATION

11

STATUS

NOTE 2

7

5.3.35.8.4,NOTE 1

RELEASECOMPLETE

5.8.4

WASSETUPB/CAST

?

STOP T301IF IMPLEMENTED

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

7

N

Y

N

Y

N

Y

Figure 5 (sheet 27 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)44

NETWORK SIDE SDL DIAGRAMS

Process NETWORK_SIDE 28(85)

NOTE 1. IF TIMER T301 EXPIRED, CAUSE #102 SHOULD BE SENT IN THE APPROPRIATE MESSAGE.

7CALL

RECEIVED

DISCONNECTREQUEST(CAUSE)

5.3.2 (e)5.3.4

STOP T301IF IMPLEMENTED

WASSETUPB/CAST

?

INT *RELEASEREQUEST

TO ALLACTIVE CESs,CAUSE,NOTE 1

T312RUNNING

?

RELEASEB−CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

RELEASEB−CHANNEL IFNOT RELEASED

22

DISCONNECT(CAUSE)

NOTE 1

STARTT305

12

TIMEOUTT301

5.2.5.4

RELEASEINDICATION

INFOREQUEST

5

WASSETUPB/CAST

?

INFO

7

INT *INFOREQUEST

TO ALLACTIVE CESs

7

Y

N

Y

N

N

Y

Figure 5 (sheet 28 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)45

Process NETWORK_SIDE 29(85)

NETWORK SIDE SDL DIAGRAMS

7CALL

RECEIVED

INT *PROGRESSINDICATION(CES)

PROGRESSINDICATION

7

INT *INFOINDICATION(CES)

INFOINDICATION

7

INT *CONNECTINDICATION(CES)

+

PRESELECTCES

CONNECTINDICATION

STOP T301IF IMPLEMENTED

8

INT *CALL PROCINDICATION(CES)

7

INT *ALERTINGINDICATION(CES)

Figure 5 (sheet 29 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)46

Process NETWORK_SIDE 30(85)

NETWORK SIDE SDL DIAGRAMS

7CALL

RECEIVED

INT *REL COMPINDICATION(CES)

DELETECES

7

INT *RELEASEINDICATION(CES)

5.2.5.3

OTHERCESs ABLE TO

PROCEED?

SAVECAUSE

7

T312RUNNING

?

RELEASEINDICATION

STOP T301IF IMPLEMENTED

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

TIMEOUTT312

5.2.5.3

ANYCES ABLE TO

PROCEED?

7

Y

N

Y N

N

Y

Figure 5 (sheet 30 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)47

Process NETWORK_SIDE 31(85)

NETWORK SIDE SDL DIAGRAMS

7ICALL

RECEIVED

RELEASECOMPLETE

INT *RELEASEINDICATION(CES)

INT *REL COMPINDICATION(CES)

RELEASE

INT *RELEASEINDICATION(CES)

RELEASECOMPLETE

INT *REL COMPINDICATION(CES)

DISCONNECT

INT *RELEASEINDICATION(CES)

RELEASE

STARTT308

19I

PROGRESS

INT *PROGRESSINDICATION(CES)

7I

CONNECT

INT *CONNECTINDICATION(CES)

8I

INFO

INT *INFOINDICATION(CES)

7I

INDIVIDUAL PROCESS

Figure 5 (sheet 31 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)48

Process NETWORK_SIDE 32(85)

NETWORK SIDE SDL DIAGRAMS

7ICALL

RECEIVED

INDIVIDUAL PROCESS

INT *INFOREQUEST

INFO

7I

INT *RELEASEREQUEST(CAUSE)

RELEASE(CAUSE)

STARTT308

19I

Figure 5 (sheet 32 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)49

NETWORK SIDE SDL DIAGRAMS

Process NETWORK_SIDE 33(85)

8CONNECTREQUEST

SETUPCOMPLETEREQUEST

5.2.8,5.2.95.3.2 (b)+

CONNECTB−CHANNEL

WASSETUPB/CAST

?

SELECTCES

CONNECT ACK(SELECTED CES)

END PROCESS *(SELECTED CES)

INT *RELEASEREQUEST(OTHER CESs, CAUSE #26)

10

CONNECTACK

10

DISCONNECTREQUEST(CAUSE)

5.3.2 (e)5.3.4

WASSETUPB/CAST

?

DISCONNECT

STARTT305

12

INT *RELEASEREQUEST(TO ALL ACTIVE CESs, CAUSE)

T312RUNNING

?

RELEASEB−CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

RELEASEB−CHANNEL IFNOT RELEASED

22

INFOREQUEST

5

WASSETUPB/CAST

?

INFO

8

INT *INFOREQUEST

TO ALLACTIVE CESs

8

Y

N

N

Y

N

Y

N

Y

Figure 5 (sheet 33 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)50

Process NETWORK_SIDE 34(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, A STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY ALSO BE FOLLOWED. IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322 AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDITIONAL INFORMATION TO THE NETWORK.

8CONNECTREQUEST

INFO

55.8.4,NOTE 1

WASSETUPB/CAST

?

INFOINDICATION

8

STATUSNOTE 2

8

CALLPROCEEDING

5.2.95.3.2 (b)5.8.4

WASSETUPB/CAST

?

REPORTSTATUS

(CAUSE #97,#98 OR #101)

8

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #26)

8

CONNECTALERTINGSETUP ACK

N

Y

N

Y

Figure 5 (sheet 34 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)51

Process NETWORK_SIDE 35(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, A STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY ALSO BE FOLLOWED. IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322 AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDITIONAL INFORMATION TO THE NETWORK.

8CONNECTREQUEST

RELEASECOMPLETE

5.8.4

WASSETUPB/CAST

?

8RELEASE

B-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

RELEASE

WASSETUPB/CAST

?

RELEASEINDICATION

RELEASECOMPLETE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

RELEASECOMPLETE

8

5.8.4

DISCONNECT

WASSETUPB/CAST

?

STATUS

NOTE 2

8

RELEASEB-CHANNEL IFNOT RELEASED

DISCONNECTINDICATION

11

5.3.35.8.4,NOTE 1

Y

NN

YY

N

Figure 5 (sheet 35 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)52

NETWORK SIDE SDL DIAGRAMS

Process NETWORK_SIDE 36(85)

8CONNECTREQUEST

INT *ALERTINGINDICATION(CES)

8

INT *CONNECTINDICATION(CES)

INT *CALL PROCINDICATION(CES)

INT *RELEASEINDICATION(CES)

PRE−SELECTED

CES?

RELEASEINDICATION

INT *RELEASEREQUEST

TO ALL ACTIVE CESs,CAUSE #26

T312RUNNING

?

RELEASEB−CHANNEL IFNOT RELEASED

RELEASECR

0

RELEASEB−CHANNEL IFNOT RELEASED

22

INT *INFOINDICATION(CES)

INFOINDICATION

8

INT *PROGRESSINDICATION(CES)

PROGRESSINDICATION

8

INT *REL COMPINDICATION(CES)

DELETECES

8

N

Y

N

Y

Figure 5 (sheet 36 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)53

Process NETWORK_SIDE 37(85)

NETWORK SIDE SDL DIAGRAMS

8ICONNECTREQUEST

RELEASECOMPLETE

INT *RELEASEINDICATION(CES)

INT *REL COMPINDICATION(CES)

RELEASE

INT *RELEASEINDICATION(CES)

RELEASECOMPLETE

INT *REL COMPINDICATION(CES)

DISCONNECT

INT *RELEASEINDICATION(CES)

RELEASE

STARTT308

19I

INFO

INT *INFOINDICATION(CES)

8I

INT *INFOREQUEST

INFO

8I

INDIVIDUAL PROCESS

END *PROCESS

INT *RELEASEREQUEST(CAUSE)

RELEASE(CAUSE)

STARTT308

19I

Figure 5 (sheet 37 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)54

Process NETWORK_SIDE 38(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. TIMER T301 IS NOT USED IF THE NETWORK IMPLEMENTS ANOTHER INTERNAL ALERTING SUPERVISION TIMING FUNCTION.

9I/C CALL

PROCEEDING

CALLPROCEEDING

WASSETUPB/CAST

?

REPORTSTATUS

(CAUSE #97,#98 OR #101)

9

CHNLOK

?

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

9

CREATEPROCESS

(CES)

INT *CALL PROCREQUEST(CES)

9

5.2.3, 5.2.5.25.3.2, 5.8.4+ALERTING

WASSETUPB/CAST

?

STOP T310IF RUNNING

ALERTINGINDICATION

STARTT301

7

NOTE 1

CHNLOK

?

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

9

STOP T310IF RUNNING

ALERTINGINDICATION

CREATEPROCESS

(CES)

INT *ALERTINGREQUEST(CES)

STARTT301

NOTE 1

7

5.2.35.2.5.25.3.2+

N

Y

N

Y

N

Y

N

Y

Figure 5 (sheet 38 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)55

Process NETWORK_SIDE 39(85)

NETWORK SIDE SDL DIAGRAMS

9I/C CALL

PROCEEDING

SETUPACK

5.2.45.8.4

WASSETUPB/CAST

?

REPORTSTATUS

(CAUSE #97,#98 OR #101)

9

CHNLOK

?

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

9

CREATEPROCESS

(CES)

INT *SETUP ACKREQUEST(CES)

9

CONNECT

WASSETUPB/CAST

?

STOP T310IF RUNNING

CONNECTINDICATION

8

CHNLOK

?

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

9

STOP T310IF RUNNING

CONNECTINDICATION

PRESELECTCES

CREATEPROCESS

(CES)

INT *CONNECTREQUEST(CES)

8

5.2.35.2.5.25.3.2+

N

Y

N

Y

N

Y

N

Y

Figure 5 (sheet 39 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)56

Process NETWORK_SIDE 40(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, THE STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY BE FOLLOWED. IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322 AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDITIONAL INFORMATION TO THE NETWORK.

9I/C CALL

PROCEEDING

PROGRESS

5.2.65.8.4,NOTE 1

WASSETUPB/CAST

?

PROGRESSINDICATION

9

STATUSNOTE 2

9

INFO

55.8.4,NOTE 1

WASSETUPB/CAST

?

INFOINDICATION

9

N

Y

N

Y

Figure 5 (sheet 40 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)57

Process NETWORK_SIDE 41(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, A STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY BE FOLLOWED. IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322 AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDITIONAL INFORMATION TO THE NETWORK.

9I/C CALL

PROCEEDING

RELEASE

5.8.4

WASSETUPB/CAST

?

RELEASECOMPLETE

9

STOP T310IF RUNNING

RELEASEINDICATION

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECOMPLETE

RELEASECR

0

DISCONNECT

5.3.35.8.4,NOTE 1

WASSETUPB/CAST

?

STOP T310IF RUNNING

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECTINDICATION

11

STATUS

NOTE 2

9

RELEASECOMPLETE

5.2.5.35.8.4

WASSETUPB/CAST

?

9STOP T310IF RUNNING

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

Y

NN

Y Y

N

Figure 5 (sheet 41 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)58

NETWORK SIDE SDL DIAGRAMS

Process NETWORK_SIDE 42(85)

NOTE 1. IF TIMER T310 EXPIRED, CAUSE #102 SHOULD BE SENT IN THE APPROPRIATE MESSAGE.

9I/C CALL

PROCEEDING

DISCONNECTREQUEST(CAUSE)

5.3.2 (e)5.3.4

STOP T310IF RUNNING

WASSETUPB/CAST

?

INT *RELEASEREQUEST

TO ALLACTIVE CESs,CAUSE,NOTE 1

T312RUNNING

?

RELEASEB−CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

RELEASEB−CHANNEL IFNOT RELEASED

22

DISCONNECT(CAUSE)

NOTE 1

RELEASEB−CHANNEL IFNOT RELEASED

STARTT305

12

TIMEOUTT310

5.2.5.4

RELEASEINDICATION

INFOREQUEST

5

WASSETUPB/CAST

?

INFO

9

INT *INFOREQUEST

TO ALLACTIVE CESs

9

Y

N

Y

N

N

Y

Figure 5 (sheet 42 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)59

Process NETWORK_SIDE 43(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. TIMER T301 IS NOT USED IF THE NETWORK IMPLEMENTS ANOTHER INTERNAL ALERTING SUPERVISION TIMING FUNCTION.

9I/C CALL

PROCEEDING

INT *CALL PROCINDICATION(CES)

9

INT *PROGRESSINDICATION(CES)

PROGRESSINDICATION

9

INT *INFOINDICATION(CES)

INFOINDICATION

9

INT *CONNECTINDICATION(CES)

+

STOP T310IF RUNNING

PRESELECTCES

CONNECTINDICATION

8

INT *ALERTINGINDICATION(CES)

+

STOP T310IF RUNNING

ALERTINGINDICATION

STARTT301

NOTE 1

7

Figure 5 (sheet 43 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)60

Process NETWORK_SIDE 44(85)

NETWORK SIDE SDL DIAGRAMS

9I/C CALL

PROCEEDING

INT *REL COMPINDICATION(CES)

DELETECES

9

INT *RELEASEINDICATION(CES)

5.2.5.3

OTHERCESs ABLE TO

PROCEED?

SAVECAUSE

9

T312RUNNING

?

RELEASEINDICATION

STOP T310IF RUNNING

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

TIMEOUTT312

5.2.5.3

ANYCES ABLE TO

PROCEED?

9

Y

N

Y N

N

Y

Figure 5 (sheet 44 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)61

Process NETWORK_SIDE 45(85)

NETWORK SIDE SDL DIAGRAMS

9II/C CALL

PROCEEDING

INFO

INT *INFOINDICATION(CES)

9I

CONNECT

INT *CONNECTINDICATION(CES)

8I

RELEASE

INT *RELEASEINDICATION(CES)

RELEASECOMPLETE

INT *REL COMPINDICATION(CES)

DISCONNECT

INT *RELEASEINDICATON(CES)

RELEASE

STARTT308

19I

PROGRESS

INT *PROGRESSINDICATION(CES)

9I

ALERTING

INT *ALERTINGINDICATION(CES)

7I

INDIVIDUAL PROCESS

RELEASECOMPLETE

INT *RELEASEINDICATION(CES)

INT *REL COMPINDICATION(CES)

Figure 5 (sheet 45 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)62

Process NETWORK_SIDE 46(85)

NETWORK SIDE SDL DIAGRAMS

9II/C CALL

PROCEEDING

INDIVIDUAL PROCESS

INT *RELEASEREQUEST(CAUSE)

RELEASE(CAUSE)

STARTT308

19I

INT *INFOREQUEST

INFO

9I

Figure 5 (sheet 46 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)63

Process NETWORK_SIDE 47(85)

NETWORK SIDE SDL DIAGRAMS

10ACTIVE

CONNECTACK

10

5.1.8

SUSPEND

ACCESS?

REPORTSTATUS

(CAUSE #97,#98 OR #101)

10

SUSPENDREJECT(CAUSE #29)

10

SUSPENDINDICATION

15

5.65.6.25.6.3

PRA

BRA

Figure 5 (sheet 47 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)64

Process NETWORK_SIDE 48(85)

NETWORK SIDE SDL DIAGRAMS

10ACTIVE

INFO

INFOINDICATION

10

5

NOTIFY

NOTIFYINDICATION

10

5.6.25.6.45.9

Figure 5 (sheet 48 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)65

Process NETWORK_SIDE 49(85)

NETWORK SIDE SDL DIAGRAMS

10ACTIVE

RELEASECOMPLETE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

RELEASEINDICATION

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECOMPLETE

RELEASECR

0

5.8.4

DISCONNECT

DISCONNECTB-CHANNEL IFCONNECTED

DISCONNECTINDICATION

11

5.3.3+

Figure 5 (sheet 49 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)66

Process NETWORK_SIDE 50(85)

NETWORK SIDE SDL DIAGRAMS

10ACTIVE

INT *REL COMPINDICATION(CES)

DELETECES

10

INFOREQUEST

INFO

10

5NOTIFYREQUEST

NOTIFY

10

5.6.25.6.45.9

DISCONNECTREQUEST(CAUSE)

TONEOPTION

?

DISCONNECT(PI, CAUSE)

STARTTONE

STARTT306

12

DISCONNECTB-CHANNEL IFCONNECTED

DISCONNECT(CAUSE)

STARTT305

5.3.4+

Y

N

Figure 5 (sheet 50 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)67

Process NETWORK_SIDE 51(85)

NETWORK SIDE SDL DIAGRAMS

11DISCONNECT

REQUEST

INFO

5

INFOINDICATION

11

RELEASE

5.8.4

RELEASEINDICATION

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECOMPLETE

RELEASECR

0

RELEASECOMPLETE

5.8.4

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

Figure 5 (sheet 51 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)68

Process NETWORK_SIDE 52(85)

NETWORK SIDE SDL DIAGRAMS

11DISCONNECT

REQUEST

RELEASEREQUEST

RELEASE

STARTT308

19

5.3.3+ INFO

REQUEST

INFO

11

5

Figure 5 (sheet 52 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)69

Process NETWORK_SIDE 53(85)

NETWORK SIDE SDL DIAGRAMS

12DISCONNECTINDICATION

DISCONNECT

STOPT305

OR T306

STOP TONES/ANNOUNCEMENTS

IF AVAILABLE

RELEASE

STARTT308

19

5.3.6

RELEASE

RELEASEINDICATION

STOPT305

OR T306

STOP TONES/ANNOUNCEMENTS

IF AVAILABLE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECOMPLETE

RELEASECR

0

5.3.4+ RELEASE

COMPLETE

STOPT305

OR T306

STOP TONES/ANNOUNCEMENTS

IF AVAILABLE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

Figure 5 (sheet 53 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)70

Process NETWORK_SIDE 54(85)

NETWORK SIDE SDL DIAGRAMS

12DISCONNECTINDICATION

INFOREQUEST

INFO

12

5

INFO

5

INFOINDICATION

12

Figure 5 (sheet 54 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)71

Process NETWORK_SIDE 55(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. THE CAUSE SENT IS THE SAME AS IN THE ORIGINAL DISCONNECT MESSAGE.

12DISCONNECTINDICATION

TIMEOUTT306

STOP TONES/ANNOUNCEMENTS

IF AVAILABLE

RELEASE(CAUSE)

NOTE 1

STARTT308

19

5.3.5TIMEOUTT305

5.3.5

Figure 5 (sheet 55 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)72

Process NETWORK_SIDE 56(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. TIMER T307 IS RUNNING IN THE CALL CONTROL BLOCK.

15SUSPENDREQUEST

SUSPENDREJECTREQUEST(CAUSE)

SUSPENDREJECT(CAUSE #50 OR #84)

10

5.6.3SUSPENDRESPONSE

SUSPENDACK

RELEASECR

0

5.6.2+,NOTE 1

Figure 5 (sheet 56 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)73

Process NETWORK_SIDE 57(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. THIS PRIMITIVE IS RECEIVED WHEN DOUBLE SUSPENSION OCCURS.

15SUSPENDREQUEST

NOTIFYREQUEST

NOTIFY

15

5.6.25.6.45.9,NOTE 1

DISCONNECTREQUEST(CAUSE)

TONEOPTION

?

DISCONNECT(PI, CAUSE)

STARTTONE

STARTT306

12

DISCONNECTB-CHANNEL IFCONNECTED

DISCONNECT(CAUSE)

STARTT305

5.3.4

Y

N

Figure 5 (sheet 57 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)74

Process NETWORK_SIDE 58(85)

NETWORK SIDE SDL DIAGRAMS

17RESUMEREQUEST

DISCONNECT

DISCONNECTB-CHANNEL IFCONNECTED

DISCONNECTINDICATION

11

5.3.3RESUMEREJECTREQUEST(CAUSE)

5.6.5

RESUMEREJECT(CAUSE #83, #85 OR #86)

RELEASECR

0

RESUMERESPONSE

RESUMEACK

10

5.6.4+

Figure 5 (sheet 58 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)75

Process NETWORK_SIDE 59(85)

NETWORK SIDE SDL DIAGRAMS

19RELEASEREQUEST

DISCONNECT

19

5.3.6

RELEASE

STOPT308

RELEASECONFIRM

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

5.3.6RELEASECOMPLETE

5.3.3+

Figure 5 (sheet 59 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)76

Process NETWORK_SIDE 60(85)

NETWORK SIDE SDL DIAGRAMS

19RELEASEREQUEST

INFO

5

INFOINDICATION

19

STATUS

CS=0?

19STATUSINDICATION(ERROR)

STOPT308

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

5.8.11

N

Y

Figure 5 (sheet 60 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)77

Process NETWORK_SIDE 61(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. THIS MESSAGE IS IDENTICAL TO THE ORIGINAL RELEASE MESSAGE, EXCEPT THAT AN ADDITIONAL CAUSE #102 MAY BE ADDED.NOTE 2. THE OPTION OF PLACING THE B-CHANNEL IN THE MAINTENANCE CONDITION IS NOT APPLICABLE IN THE CASE OF POINT-TO-MULTIPOINT CONFIGURATIONS.

19RELEASEREQUEST

TIMEOUTT308

FIRSTTIMEOUT

?

RELEASE

NOTE 1

STARTT308

19

TYPEOF

CONFIG.?

PLACEB-CHANNEL IN AMAINTENANCE

CONDITION

RELEASECONFIRM

RELEASECR

0

RELEASEB-CHANNEL IFNOT RELEASED

NOTE 2

5.3.5INT *RELCOMPINDICATION

19

INT *INFOINDICATION

19

Y

N

P-P

P-MP

Figure 5 (sheet 61 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)78

Process NETWORK_SIDE 62(85)

NETWORK SIDE SDL DIAGRAMS

19IRELEASEREQUEST

DISCONNECT

19I

INDIVIDUAL PROCESS

RELEASE

STOPT308

INT *REL COMPINDICATION(CES)

RELEASECOMPLETE

Figure 5 (sheet 62 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)79

Process NETWORK_SIDE 63(85)

NETWORK SIDE SDL DIAGRAMS

19IRELEASEREQUEST

TIMEOUTT308

FIRSTTIMEOUT

?

INT *REL COMPINDICATION(CES)

RELEASE

STARTT308

19I

INFO

19I

INT *INFOINDICATION(CES)

INDIVIDUAL PROCESS

STATUS

CS=0?

19ISTOPT308

INT *REL COMPINDICATION(CES)

N

Y

N

Y

Figure 5 (sheet 63 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)80

Process NETWORK_SIDE 64(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. THE CAUSE SENT DEPENDS ON WHETHER T312 IS STILL RUNNING OR NOT, WHICH IS INDICATED BY T312 FLAG. IF T312 IS STILL RUNNING, THE CAUSE SENT ALSO DEPENDS ON WHETHER A NETWORK DISCONNECT INDICATION HAS BEEN RECEIVED OR NOT.

22CALL

ABORT

CALLPROCEEDING

5.2.5.45.3.2 (e)

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE)

NOTE 1

22

CONNECTALERTINGSETUPACK

Figure 5 (sheet 64 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)81

Process NETWORK_SIDE 65(85)

NETWORK SIDE SDL DIAGRAMS

22CALL

ABORT

INT *REL COMPINDICATION(CES)

DELETECES

ANYCES ACTIVE

?

NETWORKDISCONNECTINDICATION

?

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

RELEASEINDICATION

22

TIMEOUTT312

5.3.2 (e)+

CLEART312FLAG

RELEASECOMPLETE

22

RELEASE

RELEASECOMPLETE

22

N

N

Y

Y

Figure 5 (sheet 65 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)82

Process NETWORK_SIDE 66(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. TIMER T301 IS NOT USED IF THE NETWORK IMPLEMENTS ANOTHER INTERNAL ALERTING SUPERVISING TIMING FUNCTION.

25OVERLAPRECEIVING

CONNECT

WASSETUPB/CAST

?

STOPT304

CONNECTINDICATION

8

CHNLOK

?

CONNECTINDICATION

PRESELECTCES

CREATEPROCESS

(CES)

INT *CONNECTREQUEST(CES)

8

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

25

5.2.35.2.75.3.2+

ALERTING

WASSETUPB/CAST

?

STOPT304

ALERTINGINDICATION

STARTT301

NOTE 1

7

CHNLOK

?

ALERTINGINDICATION

CREATEPROCESS

(CES)

INT *ALERTINGREQUEST(CES)

STARTT301

NOTE 1

7

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

25

5.2.35.2.5.25.3.2+

N

Y

Y

N

N

Y

Y

N

Figure 5 (sheet 66 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)83

Process NETWORK_SIDE 67(85)

NETWORK SIDE SDL DIAGRAMS

25OVERLAPRECEIVING

SETUPACK

5.2.3, 5.2.45.3.2, 5.8.4+

WASSETUPB/CAST

?

REPORTSTATUS

(CAUSE #97,#98 OR #101)

25

CHNLOK

?

CREATEPROCESS

(CES)

INT *SETUP ACKREQUEST(CES)

25

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

25

CALLPROCEEDING

WASSETUPB/CAST

?

STOPT304

PROCEEDINGINDICATION

STARTT310

9

CHNLOK

?

PROCEEDINGINDICATION

CREATEPROCESS

(CES)

INT *CALL PROCREQUEST(CES)

STARTT310

9

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES, CAUSE #6)

25

5.2.35.2.5.25.3.2+

N

Y

Y

N

N

Y

Y

N

Figure 5 (sheet 67 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)84

Process NETWORK_SIDE 68(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, A STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY BE FOLLOWED. IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322 AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDITIONAL INFORMATION TO THE NETWORK.

25OVERLAPRECEIVING

PROGRESS

WASSETUPB/CAST

?

STATUSNOTE 2

25

PROGRESSINDICATION

25

5.2.65.8.4,NOTE 1INFO

WASSETUPB/CAST

?

INFOINDICATION

25

55.8.4,NOTE 1

Y

N

Y

N

Figure 5 (sheet 68 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)85

Process NETWORK_SIDE 69(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE CALL STATE RETURNED IN THE STATUS MESSAGE SHOULD BE 6.NOTE 2. AS AN ALTERNATIVE, A STATUS ENQUIRY PROCEDURE ACCORDING TO SUBCLAUSE 5.8.4 OF ETS 300403-1 MAY BE FOLLOWED. IN THIS CASE, AN INDIVIDUAL PROCESS SHOULD BE CREATED FOR THE RESPONDING TERMINAL IN ORDER TO CONTROL TIMER T322 AND THE APPROPRIATE RESPONSE. THIS PROCEDURE IS NOT DOCUMENTED IN THIS ETS AS IT INCREASES THE COMPLEXITY OF THE REPRESENTATION. USE OF THE STATUS ENQUIRY PROCEDURE IN THIS CIRCUMSTANCE DOES NOT PROVIDE USEFUL ADDITIONAL INFORMATION TO THE NETWORK.

25OVERLAPRECEIVING

DISCONNECT

WASSETUPB/CAST

?

STATUS

NOTE 2

25

STOPT304

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECTINDICATION

11

5.3.35.8.4+,NOTE 1

RELEASECOMPLETE

WASSETUPB/CAST

?

25STOPT304

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.2.5.35.8.4RELEASE

5.8.4

WASSETUPB/CAST

?

RELEASECOMPLETE

25

STOPT304

RELEASEINDICATION

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECOMPLETE

RELEASECR

0

Y

N

Y

N

Y

N

Figure 5 (sheet 69 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)86

NETWORK SIDE SDL DIAGRAMS

Process NETWORK_SIDE 70(85)

NOTE 1. IN THE CASE OF A BROADCAST SETUP, THE EXPIRY OF TIMER T304 DOESN’T APPLY AS IT RUNS ONLY IN INDIVIDUAL PROCESSES.NOTE 2. IN THE CASE OF A BROADCAST SETUP, THE STOPPING OF TIMER T304 DOESN’T APPLY AS IT RUNS ONLY IN INDIVIDUAL PROCESSES.NOTE 3. IF TIMER T304 EXPIRED, CAUSE #102 SHOULD BE SENT IN THE APPROPRIATE MESSAGE.

25OVERLAP

RECEIVING

DISCONNECTREQUEST(CAUSE)

5.3.4

STOPT304

NOTE 2

WASSETUPB/CAST

?

INT *RELEASEREQUEST

TO ALLACTIVE CESs,CAUSE,NOTE 3

T312RUNNING

?

RELEASEB−CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

RELEASEB−CHANNEL IFNOT RELEASED

22

DISCONNECT(CAUSE)

NOTE 3

DISCONNECTB−CHANNEL IF

NOT DISCONNECTED

STARTT305

12

TIMEOUTT304

5.2.4,NOTE 1

RELEASEINDICATION

MORE INFOREQUEST

5.2.4+

WASSETUPB/CAST

?

STOPT304

INFO

STARTT304

25

INT *INFOREQUEST

TO ALLACTIVE CESs

Y

N

Y

N

N

Y

Figure 5 (sheet 70 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)87

Process NETWORK_SIDE 71(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. TIMER T301 IS NOT USED IF THE NETWORK IMPLEMENTS ANOTHER INTERNAL ALERTING SUPERVISION TIMING FUNCTION.

25OVERLAPRECEIVING

INT *ALERTINGINDICATION(CES)

ALERTINGINDICATION

STARTT301

7

NOTE 1

+ INT *CALL PROCINDICATION(CES)

PROCEEDINGINDICATION

STARTT310

9

+INT *CONNECTINDICATION(CES)

PRESELECTCES

CONNECTINDICATION

8

+

Figure 5 (sheet 71 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)88

Process NETWORK_SIDE 72(85)

NETWORK SIDE SDL DIAGRAMS

25OVERLAPRECEIVING

INT *PROGRESSINDICATION(CES)

PROGRESSINDICATION

25

INT *INFOINDICATION(CES)

INFOINDICATION

25

TIMEOUTT312

5.2.5.3

ANYCES ABLE TO

PROCEED?

RELEASEINDICATION

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

25

INT *RELEASEINDICATION(CES)

5.2.5.3

OTHERCESs ABLE TO

PROCEED?

SAVECAUSE

25

T312RUNNING

?

INT *REL COMPINDICATION(CES)

DELETECES

25

N

YY

N

NY

Figure 5 (sheet 72 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)89

Process NETWORK_SIDE 73(85)

NETWORK SIDE SDL DIAGRAMS

25IOVERLAPRECEIVING

RELEASECOMPLETE

STOPT304

INT *RELEASEINDICATION(CES)

INT *REL COMPINDICATION(CES)

RELEASE

STOPT304

INT *RELEASEINDICATION(CES)

RELEASECOMPLETE

INT *REL COMPINDICATION(CES)

DISCONNECT

STOPT304

INT *RELEASEINDICATION(CES)

RELEASE

STARTT308

19I

INDIVIDUAL PROCESS

PROGRESS

INT *PROGRESSINDICATION(CES)

25I

CALLPROCEEDING

STOPT304

INT *CALL PROCINDICATION(CES)

9I

CONNECT

STOPT304

INT *CONNECTINDICATION(CES)

8I

ALERTING

STOPT304

INT *ALERTINDICATION(CES)

7I

Figure 5 (sheet 73 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)90

Process NETWORK_SIDE 74(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. IF TIMER T304 EXPIRED, CAUSE #102 SHOULD BE SENT IN THE RELEASE MESSAGE.

25IOVERLAPRECEIVING

INT *INFOREQUEST

STOPT304

INFO

STARTT304

25I

INDIVIDUAL PROCESS

INT *RELEASEREQUEST(CAUSE)

STOPT304

RELEASE(CAUSE)

NOTE 1

STARTT308

19I

TIMEOUTT304

INT *RELEASEINDICATION(CES)

Figure 5 (sheet 74 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)91

Process NETWORK_SIDE 75(85)

NETWORK SIDE SDL DIAGRAMS

GLOBALSTATE

25

DL-ESTABLISHINDICATION

WASSETUPB/CAST

?

25RELEASEINDICATION

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECT(CAUSE #41)

STARTT305

12

5.8.8

ANY GLOBALSTATE EXCEPT

2, 25

DL-ESTABLISHINDICATION

SAMESTATE

5.8.8

GLOBALSTATE

2

DL-ESTABLISHINDICATION

5.8.8

STOP ANYTIMER

TONEOPTION

?

DISCONNECTINDICATION

DISCONNECT(PI, CAUSE #41)

STARTTONE

STARTT306

12

DISCONNECTINDICATION

DISCONNECTB-CHANNEL IF

NOT DISCONNECTED

DISCONNECT(CAUSE #41)

STARTT305

Y

N

Y

N

Figure 5 (sheet 75 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)92

Process NETWORK_SIDE 76(85)

NETWORK SIDE SDL DIAGRAMS

INDIVIDUALSTATES

7I, 8I, 9I, 19I

DL-ESTABLISHINDICATION

5.8.8

SAMESTATE

INDIVIDUALSTATE

25I

DL-ESTABLISHINDICATION

STOPT304

INT *RELEASEINDICATION(CES)

RELEASE(CAUSE #41)

STARTT308

19I

5.8.8

Figure 5 (sheet 76 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)93

Process NETWORK_SIDE 77(85)

NETWORK SIDE SDL DIAGRAMS

GLOBALSTATE

10

DL-RELEASEINDICATION

5.8.9

T309RUNNING

?

STOPT309

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECR

0

STARTT309

DL-ESTABLISHREQUEST

10

GLOBALSTATE

0

DL-RELEASEINDICATION

5.8.9

0

ANY GLOBALSTATE EXCEPT

0, 10

DL-RELEASEINDICATION

WASSETUPB/CAST

?

STOPANY TIMER

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

STATEN6?

SAMESTATE

5.8.9

Y

NN

Y

Y

(N)

Figure 5 (sheet 77 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)94

Process NETWORK_SIDE 78(85)

NETWORK SIDE SDL DIAGRAMS

GLOBALSTATE

10

TIMEOUTT309

5.8.9

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECR

0

DL-ESTABLISHCONFIRM

5.8.9

STOPT309

REPORTSTATUS

(CAUSE #31)

10

INDIVIDUALSTATES

7I,8I,9I,19I,25I

DL-RELEASEINDICATION

STOP ANYTIMER

INT *RELEASEINDICATION(CES)

INT *REL COMPINDICATION(CES)

5.8.9

Figure 5 (sheet 78 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)95

Process NETWORK_SIDE 79(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. IN A POINT-TO-MULTIPOINT CONFIGURATION, TIMER T322 DOESN’T RUN IN THE GLOBAL PROCESS FOR STATES N7, N8, N9 AND N25.NOTE 2. FURTHER ACTIONS ARE AN IMPLEMENTATION OPTION.

1

M=0?

STATUSINDICATION(ERROR)

STOPANY TIMER

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

COMPATIBLESTATE

?

SAME STATE

NOTE 2STATUSINDICATION(ERROR)

STOPANY TIMER

RELEASEINDICATION

RELEASE(CAUSE #101)

STARTT308

19

ANY GLOBALSTATE EXCEPT

0,19

STATUS(CS=M)

T322RUNNING

?

1

CAUSE#97 OR #98

?

SAVE CAUSEAND

CALL STATE

SAMESTATE

CAUSE#30

?

STOPT322

5.8.105.8.11,NOTE 1

Y

N

Y

N

N

Y

Y

N

N

Y

Figure 5 (sheet 79 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)96

Process NETWORK_SIDE 80(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. FURTHER ACTIONS ARE AN IMPLEMENTATION OPTION.

2

M=0?

STATUSINDICATION(ERROR)

STOPANY TIMER

INT *RELEASEINDICATION(CES)

INT *REL COMPINDICATION(CES)

COMPATIBLESTATE

?

SAME STATE

NOTE 1STATUSINDICATION(ERROR)

STOPANY TIMER

INT *RELEASEINDICATION(CES)

RELEASE(CAUSE #101)

STARTT308

19I

ANY INDIVIDUALSTATE EXCEPT

0I,19I

STATUS(CS=M)

T322RUNNING

?

2

CAUSE#97

?

SAVE CAUSEAND

CALL STATE

SAMESTATE

CAUSE#30

?

STOPT322

5.8.105.8.11

Y

N

Y

N

N

Y

Y

N

N

Y

Figure 5 (sheet 80 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)97

Process NETWORK_SIDE 81(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. UNEXPECTED MESSAGE AND UNRECOGNIZED MESSAGE DO NOT INCLUDE RELEASE AND RELEASE COMPLETE.

ANY GLOBALOR INDIVIDUALSTATE EXCEPT

0, 0I

SETUP

SAMESTATE

5.8.3.2(e)UNRECOGNIZEDMESSAGE

REPORTSTATUS

(CAUSE #97,#98 OR #101)

SAMESTATE

5.8.4,NOTE 1UNEXPECTED

MESSAGE

5.8.4,NOTE 1

Figure 5 (sheet 81 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)98

Process NETWORK_SIDE 82(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. A STATUS ENQUIRY MESSAGE RECEIVED IN A POINT-TO-MULTIPOINT CONFIGURATION FROM A TERMINAL FOR WHICH AN INDIVIDUAL PROCESS EXISTS IS TREATED BY THAT PROCESS.NOTE 2. THE RESTART PROCEDURE IS NOT APPLICABLE FOR POINT-TO-MULTIPOINT CONFIGURATIONS.NOTE 3. THIS PRIMITIVE MAY BE RECEIVED FROM GLOBAL CALL REFERENCE CONTROL.NOTE 4. THIS PRIMITIVE IS SENT TO GLOBAL CALL REFERENCE CONTROL.

GLOBALSTATES

10,11,12,15,19

ANY MESSAGEWITH WRONGCES

CREATEPROCESS

(CES)

INT *RELEASEREQUEST(CES)

SAMESTATE

GLOBALSTATES

8,10,11,12,15,19

TIMEOUTT312

SAMESTATE

ANY GLOBALOR INDIVIDUAL

STATE

STATUSENQUIRY

STATUS(CAUSE #30)

SAMESTATE

5.8.3.2 (h)5.8.10,NOTE 1

ANYGLOBALSTATE

NOTE 2

RESTARTREQUEST

STOPANY TIMER

RELEASEINDICATION

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

RESTARTCONFIRM

NOTE 4

0

5.5,NOTE 3

Figure 5 (sheet 82 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)99

Process NETWORK_SIDE 83(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. FOR THOSE GLOBAL STATES FOR WHICH AN INDIVIDUAL PROCESS EXISTS, THE TIMEOUT IS HANDLED BY THAT PROCESS.NOTE 2. ACTIONS AFTER EXPIRY OF TIMER T322 WHEN A STATUS MESSAGE WITH CAUSE #97 OR #98 HAS BEEN RECEIVED ARE IMPLEMENTATION DEPENDENT.NOTE 3. TIMER T322 MUST BE STOPPED IF ANY CLEARING MESSAGE IS RECEIVED BEFORE IT EXPIRES.

ANY GLOBALSTATE EXCEPT

0

TIMEOUTT322

STATUSRCVD WITHCAUSE #97

OR #98?

?

NOTE 2MAX No.RETRANSMISSIONS

EXCEEDED?

STATUSENQUIRY

STARTT322

NOTE 3

SAMESTATE

RELEASE(CAUSE #41)

RELEASEINDICATION

STARTT308

19

5.8.10,NOTE 1

INDIVIDUALSTATES

7I,8I,9I,19I,25I

TIMEOUTT322

STATUSRCVD WITHCAUSE #97

OR #98?

?

NOTE 2

MAX No.RETRANSMISSIONS

EXCEEDED?

STATUSENQUIRY

STARTT322

NOTE 3

SAMESTATE

RELEASE(CAUSE #41)

INT *RELEASEINDICATION(CES)

STARTT308

19I

5.8.10

Y

N

N

Y

Y

N

N

Y

Figure 5 (sheet 83 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)100

Process NETWORK_SIDE 84(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. TIMER T322 MUST BE STOPPED IF ANY CLEARING MESSAGE IS RECEIVED BEFORE IT EXPIRES.NOTE 2. IN THIS CASE, THERE IS NO DATA LINK AVAILABLE.

GLOBALSTATES

6,7,8,9,19,25

STATUSENQUIRYREQUEST

WASSETUPB/CAST

?

STATE N6?

SAMESTATE

NOTE 2

CESSPECIFIED

IN REQUEST?

INT *STATENQREQUEST

SAMESTATE

TO ALLACTIVE CESs

INT *STATENQREQUEST(CES)

T322RUNNING

?

SAMESTATE

STATUSENQUIRY

STARTT322

NOTE 1

5.8.10

INDIVIDUALSTATES

7I,8I,9I,19I,25I

INT *STATENQREQUEST

5.8.10

ANY GLOBALSTATE EXCEPT0,6,7,8,9,19,25

STATUSENQUIRYREQUEST

5.8.10

Y

Y

N

N

Y

N

Y

N

Figure 5 (sheet 84 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)101

Process NETWORK_SIDE 85(85)

NETWORK SIDE SDL DIAGRAMS

NOTE 1. TIMER T322 MUST BE STOPPED IF ANY CLEARING MESSAGE IS RECEIVED BEFORE IT EXPIRES.

REPORTSTATUS(CAUSE)

STATUS(CAUSE)

T322RUNNING

?

STATUSENQUIRY

STARTT322

NOTE 1

Y

N

Figure 5 (sheet 85 of 85): Network side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)102

8.2 User side SDL diagrams

Process USER_SIDE 1(57)

USER SIDE SDL DIAGRAMS

0NULL

SETUP

5.2.15.2.35.3.2+

ESTABLISHCR

O/GCALLS ONLY

?

TYPEOF

CONFIG.?

RELEASECOMPLETE(CAUSE #88)

RELEASECR

0RELEASECR

0

RELEASECOMPLETE(CAUSE #88)

CHNLSELECTIONSUCCESS

?

RELEASECOMPLETE(CAUSE #34 OR #44)

RELEASECR

0

SETUPINDICATION

6

NOTE 1

RELEASE5.8.3.2 (b)

ESTABLISHCR

RELEASECOMPLETE

RELEASECR

0

Y

P-P

P-MP

N

N

Y

Figure 6 (sheet 1 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)103

Process USER_SIDE 2(57)

USER SIDE SDL DIAGRAMS

NOTE 1. ANY OTHER MESSAGE EXCEPT STATUS ENQUIRY, SEE PAGES DEALING WITH DIAGRAMS RELATED TO ANY STATE.NOTE 2. CAUSE #101 IS RETURNED IF A STATUS MESSAGE IS RECEIVED, WHILE CAUSE #81 APPLIES FOR OTHER MESSAGES.

0NULL

OTHERMESSAGE

ESTABLISHCR

RELEASECOMPLETE(CAUSE #81 OR #101)

NOTE 2

RELEASECR

0

ESTABLISHCR

RELEASE(CAUSE #81 OR #101)

NOTE 2

STARTT308

19

5.8.3.2 (a),NOTE 1STATUS

CS=0?

0

5.8.11RELEASECOMPLETE

0

5.8.3.2 (c)

N

Y

Figure 6 (sheet 2 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)104

Process USER_SIDE 3(57)

USER SIDE SDL DIAGRAMS

NOTE 1. THE RESUME REQUEST PRIMITIVE IS NOT DEFINED FOR PRIMARY RATE ACCESS, i.e. THE USE OF THE CALL REARRANGEMENT PROCEDURE IS RESTRICTED TO BASIC ACCESS.NOTE 2. TIMER T303 IS OPTIONAL.

0NULL

SETUPREQUEST

SELECTCR

SETCHANNELIDENTITY

SETUP

STARTT303

1

NOTE 2

5.1.1+ RESUME

REQUEST

SELECTCR

RESUME

STARTT318

17

5.6.4+,NOTE 1

Figure 6 (sheet 3 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)105

Process USER_SIDE 4(57)

USER SIDE SDL DIAGRAMS

NOTE 1. THE SETUP ACKNOWLEDGE MESSAGE SHALL NOT BE RECEIVED IF THE SENDING COMPLETE INFORMATION ELEMENT IS INCLUDED IN THE ORIGINATING SETUP MESSAGE.NOTE 2. TIMERS T303 AND T304 ARE OPTIONAL.

1CALL

INITIATED

SETUPACK

STOPT303

CHNLOK

?

RELEASEINDICATION

RELEASE(CAUSE #6)

STARTT308

19

MOREINFOINDICATION

B-CHANNELCONTROL

STARTT304

2

NOTE 2

NOTE 2

5.1.35.1.25.3.2 (d)+,NOTE 1

CALLPROCEEDING

STOPT303

CHNLOK

?

PROCEEDINGINDICATION

B-CHANNELCONTROL

3

NOTE 2

5.1.5.15.1.25.3.2 (d)+

N

Y

N

Y

Figure 6 (sheet 4 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)106

Process USER_SIDE 5(57)

USER SIDE SDL DIAGRAMS

NOTE 1. TIMER T303 IS OPTIONAL.

1CALL

INITIATED

RELEASE

STOPT303

NOTE 1

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4RELEASECOMPLETE

STOPT303

NOTE 1

REJECTINDICATION

RELEASECR

0

5.1.15.1.25.3.2 (a)

Figure 6 (sheet 5 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)107

Process USER_SIDE 6(57)

USER SIDE SDL DIAGRAMS

NOTE 1. TIMER T303 IS OPTIONAL.

1CALL

INITIATED

TIMEOUTT303

NOTE 1

FIRSTTIMEOUT

?

RELEASECOMPLETE(CAUSE #102)

RELEASECR

0

SETUP

STARTT303

NOTE 1

1

INFOREQUEST

5.1.3DISCONNECTREQUEST(CAUSE)

STOPT303

DISCONNECT(CAUSE)

STARTT305

11

NOTE 1

5.3.3

N

Y

Figure 6 (sheet 6 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)108

Process USER_SIDE 7(57)

USER SIDE SDL DIAGRAMS

NOTE 1. TIMER T304 IS OPTIONAL. IT MAY BE IMPLEMENTED BUT STOPPED DUE TO RECEIPT OF PROGRESS (INTERWORKING).

2OVERLAPSENDING

CALLPROCEEDING

STOPT304

IF RUNNING

PROCEEDINGINDICATION

B-CHANNELCONTROL

3

NOTE 1

5.1.5.25.1.25.1.6+

CONNECT

STOPT304

IF RUNNING

SETUPCONFIRM

CONNECTB-CHANNEL IF NOTYET CONNECTED

CONNECTACK

10

NOTE 1

5.1.5.2+ALERTING

STOPT304

IF RUNNING

ALERTINGINDICATION

B-CHANNELCONTROL

4

NOTE 1

5.1.5.25.1.25.1.6+

Figure 6 (sheet 7 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)109

Process USER_SIDE 8(57)

USER SIDE SDL DIAGRAMS

NOTE 1. TIMER T304 IS OPTIONAL. IT MAY BE IMPLEMENTED BUT STOPPED DUE TO RECEIPT OF PROGRESS (INTERWORKING).

2OVERLAPSENDING

PROGRESS(INTERWORKING)

STOPT304

IF RUNNING

PROGRESSINDICATION

B-CHANNELCONTROL

2

NOTE 1

5.1.25.1.6PROGRESS

(TONE)

PROGRESSINDICATION

B-CHANNELCONTROL

2

5.1.2

INFO

INFOINDICATION

2

5

Figure 6 (sheet 8 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)110

Process USER_SIDE 9(57)

USER SIDE SDL DIAGRAMS

NOTE 1. TIMER T304 IS OPTIONAL. IT MAY BE IMPLEMENTED BUT STOPPED DUE TO RECEIPT OF PROGRESS (INTERWORKING).

2OVERLAPSENDING

RELEASE

STOPT304

IF RUNNING

RELEASEINDICATION

RELEASEB-CHANNEL

RELEASECOMPLETE

RELEASECR

0

NOTE 1

5.8.4

DISCONNECT

STOPT304

IF RUNNING

NOTE 1

DISCONNECTINDICATION

B-CHANNELCONTROL

12

5.3.4RELEASECOMPLETE

STOPT304

IF RUNNING

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECR

0

NOTE 1

5.8.4

Figure 6 (sheet 9 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)111

Process USER_SIDE 10(57)

USER SIDE SDL DIAGRAMS

NOTE 1. TIMER T304 IS OPTIONAL. IT MAY BE IMPLEMENTED BUT STOPPED DUE TO RECEIPT OF PROGRESS (INTERWORKING).

2OVERLAPSENDING

INFOREQUEST

INFO

RESTARTT304

IF RUNNING

2

NOTE 1

5.1.3+DISCONNECT

REQUEST(CAUSE)

STOPT304

IF RUNNING

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE)

STARTT305

11

NOTE 1

5.3.3TIMEOUTT304

SETUPCONFIRM(ERROR)

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE #102)

STARTT305

11

5.1.5.2,NOTE 1

Figure 6 (sheet 10 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)112

Process USER_SIDE 11(57)

USER SIDE SDL DIAGRAMS

3O/G CALL

PROCEEDING

CONNECT

SETUPCONFIRM

CONNECTB-CHANNEL IF NOTYET CONNECTED

CONNECTACK

10

5.1.8+ALERTING

ALERTINGINDICATION

B-CHANNELCONTROL

4

5.1.25.1.65.1.7+

Figure 6 (sheet 11 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)113

Process USER_SIDE 12(57)

USER SIDE SDL DIAGRAMS

3O/G CALL

PROCEEDING

PROGRESS

PROGRESSINDICATION

B-CHANNELCONTROL

3

5.1.2

INFO

INFOINDICATION

3

5

Figure 6 (sheet 12 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)114

Process USER_SIDE 13(57)

USER SIDE SDL DIAGRAMS

3O/G CALL

PROCEEDING

DISCONNECT

DISCONNECTINDICATION

B-CHANNELCONTROL

12

5.3.4

RELEASE

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4RELEASECOMPLETE

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECR

0

5.8.4

Figure 6 (sheet 13 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)115

Process USER_SIDE 14(57)

USER SIDE SDL DIAGRAMS

3O/G CALL

PROCEEDING

DISCONNECTREQUEST(CAUSE)

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE)

STARTT305

11

5.3.3INFOREQUEST

INFO

3

5

Figure 6 (sheet 14 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)116

Process USER_SIDE 15(57)

USER SIDE SDL DIAGRAMS

4CALL

DELIVERED

PROGRESS

PROGRESSINDICATION

B-CHANNELCONTROL

4

5.1.2

INFO

5

INFOINDICATION

4

CONNECT

SETUPCONFIRM

CONNECTB-CHANNEL IF NOTYET CONNECTED

CONNECTACK

10

5.1.8+

Figure 6 (sheet 15 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)117

Process USER_SIDE 16(57)

USER SIDE SDL DIAGRAMS

4CALL

DELIVERED

DISCONNECT

DISCONNECTINDICATION

B-CHANNELCONTROL

12

5.3.4RELEASECOMPLETE

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

Figure 6 (sheet 16 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)118

Process USER_SIDE 17(57)

USER SIDE SDL DIAGRAMS

4CALL

DELIVERED

INFOREQUEST

INFO

4

5DISCONNECTREQUEST(CAUSE)

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE)

STARTT305

11

5.3.3

Figure 6 (sheet 17 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)119

Process USER_SIDE 18(57)

USER SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A POINT-TO-POINT CONFIGURATION, CONNECTION TO THE B-CHANNEL MAY BE MADE AT THIS POINT.

6CALL

PRESENT

PROCEEDINGREQUEST

B-CHANNELSELECTION

CALLPROCEEDING

9

NOTE 1

5.2.3.1 (d)5.2.5.1+

SETUPRESPONSE

B-CHANNELSELECTION

CONNECT

STARTT313

8

NOTE 1

5.2.3.1 (d)5.2.5.15.2.7+

ALERTINGREQUEST

B-CHANNELSELECTION

ALERTING

7

NOTE 1

5.2.3.1 (d)5.2.5+

Figure 6 (sheet 18 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)120

Process USER_SIDE 19(57)

USER SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A POINT-TO-POINT CONFIGURATION, CONNECTION TO THE B-CHANNEL MAY BE MADE AT THIS POINT.

6CALL

PRESENT

REJECTREQUEST(CAUSE)

CAUSE=INCOMPATIBLE

USER ?

RELEASECOMPLETE(CAUSE)

RELEASECR

0

WASSETUPB/CAST

?

5.2.25.2.35.2.5.1

MOREINFOREQUEST

B-CHANNELSELECTION

SETUP ACK

STARTT302

25

NOTE 1

5.2.3.1 (d)5.2.4+

N

Y

N

Y

Figure 6 (sheet 19 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)121

Process USER_SIDE 20(57)

USER SIDE SDL DIAGRAMS

6CALL

PRESENT

RELEASECOMPLETE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.3.25.8.4DISCONNECT

DISCONNECTINDICATION

12

5.3.4

Figure 6 (sheet 20 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)122

Process USER_SIDE 21(57)

USER SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A POINT-TO-POINT CONFIGURATION, CONNECTION TO THE B-CHANNEL MAY BE MADE AT THIS POINT.

7CALL

RECEIVED

INFOREQUEST

INFO

7

5PROGRESSREQUEST

PROGRESS

7

NOTE 1

5.2.3.1 (d)5.2.6+

SETUPRESPONSE

CONNECT

STARTT313

8

NOTE 1

5.2.3.1 (d)5.2.5.15.2.7+

Figure 6 (sheet 21 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)123

Process USER_SIDE 22(57)

USER SIDE SDL DIAGRAMS

7CALL

RECEIVED

DISCONNECT REQUEST(CAUSE)

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE)

STARTT305

11

5.3.3

INFO

INFOINDICATION

7

5

Figure 6 (sheet 22 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)124

Process USER_SIDE 23(57)

USER SIDE SDL DIAGRAMS

7CALL

RECEIVED

DISCONNECT

DISCONNECTINDICATION

12

5.3.4RELEASECOMPLETE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

Figure 6 (sheet 23 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)125

Process USER_SIDE 24(57)

USER SIDE SDL DIAGRAMS

8CONNECTREQUEST

INFO

INFOINDICATION

8

5CONNECTACK

STOPT313

SETUPCOMPLETEINDICATION

CONNECTB-CHANNEL IF NOTYET CONNECTED

10

5.2.8+

Figure 6 (sheet 24 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)126

Process USER_SIDE 25(57)

USER SIDE SDL DIAGRAMS

8CONNECTREQUEST

DISCONNECT

STOPT313

DISCONNECTINDICATION

12

5.3.4RELEASECOMPLETE

STOPT313

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

STOPT313

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

Figure 6 (sheet 25 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)127

Process USER_SIDE 26(57)

USER SIDE SDL DIAGRAMS

8CONNECTREQUEST

INFOREQUEST

INFO

8

5DISCONNECTREQUEST(CAUSE)

STOPT313

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE)

STARTT305

11

5.3.3TIMEOUTT313

SETUPCOMPLETEINDICATION(ERROR)

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE #102)

STARTT305

11

5.2.8

Figure 6 (sheet 26 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)128

Process USER_SIDE 27(57)

USER SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A POINT-TO-POINT CONFIGURATION, CONNECTION TO THE B-CHANNEL MAY BE MADE AT THIS POINT.

9I/C CALL

PROCEEDING

SETUPRESPONSE

CONNECT

STARTT313

8

NOTE 1

5.2.3.1 (d)5.2.5.15.2.7+

DISCONNECTREQUEST(CAUSE)

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE)

STARTT305

11

5.3.3ALERTINGREQUEST

ALERTING

7

NOTE 1

5.2.3.1 (d)5.2.5.1+

Figure 6 (sheet 27 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)129

Process USER_SIDE 28(57)

USER SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A POINT-TO-POINT CONFIGURATION, CONNECTION TO THE B-CHANNEL MAY BE MADE AT THIS POINT.

9I/C CALL

PROCEEDING

INFOREQUEST

INFO

9

5PROGRESSREQUEST

PROGRESS

9

NOTE 1

5.2.3.1 (d)5.2.6 INFO

INFOINDICATION

9

5

Figure 6 (sheet 28 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)130

Process USER_SIDE 29(57)

USER SIDE SDL DIAGRAMS

9I/C CALL

PROCEEDING

DISCONNECT

STOPT313

DISCONNECTINDICATION

12

5.3.4RELEASECOMPLETE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

Figure 6 (sheet 29 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)131

Process USER_SIDE 30(57)

USER SIDE SDL DIAGRAMS

10ACTIVE

NOTIFYREQUEST

NOTIFY

10

5.6.75.9INFO

REQUEST

INFO

10

5DISCONNECTREQUEST(CAUSE)

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE)

STARTT305

11

5.3.3+

Figure 6 (sheet 30 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)132

Process USER_SIDE 31(57)

USER SIDE SDL DIAGRAMS

NOTE 1. THE SUSPEND REQUEST PRIMITIVE IS NOT DEFINED FOR A PRIMARY RATE ACCESS, i.e. THE USE OF THE CALL REARRANGEMENT PROCEDURE IS RESTRICTED TO BASIC ACCESS.

10ACTIVE

NOTIFY

NOTIFYINDICATION

10

5.6.25.6.45.9 INFO

INFOINDICATION

10

5SUSPENDREQUEST

SUSPEND

STARTT319

15

5.6.1,NOTE 1

Figure 6 (sheet 31 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)133

Process USER_SIDE 32(57)

USER SIDE SDL DIAGRAMS

10ACTIVE

DISCONNECT

DISCONNECTINDICATION

12

5.3.4RELEASECOMPLETE

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

Figure 6 (sheet 32 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)134

Process USER_SIDE 33(57)

USER SIDE SDL DIAGRAMS

11DISCONNECT

REQUEST

DISCONNECT

STOPT305

RELEASE

STARTT308

19

5.3.6RELEASECOMPLETE

STOPT305

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

STOPT305

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.3.3+

Figure 6 (sheet 33 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)135

Process USER_SIDE 34(57)

USER SIDE SDL DIAGRAMS

11DISCONNECT

REQUEST

NOTIFY

NOTIFYINDICATION

11

5.6.25.6.45.9 INFO

5

INFOINDICATION

11

Figure 6 (sheet 34 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)136

Process USER_SIDE 35(57)

USER SIDE SDL DIAGRAMS

NOTE 1. THE CAUSE SENT IS THE SAME AS IN THE ORIGINAL DISCONNECT MESSAGE.

11DISCONNECT

REQUEST

INFOREQUEST

INFO

11

5TIMEOUTT305

RELEASE(CAUSE)

STARTT308

19

NOTE 1

5.3.5

Figure 6 (sheet 35 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)137

Process USER_SIDE 36(57)

USER SIDE SDL DIAGRAMS

12DISCONNECTINDICATION

INFO

5

INFOINDICATION

12

RELEASEREQUEST

RELEASEB-CHANNEL IFNOT RELEASED

RELEASE

STARTT308

19

5.3.4+ INFO

REQUEST

INFO

12

5

Figure 6 (sheet 36 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)138

Process USER_SIDE 37(57)

USER SIDE SDL DIAGRAMS

12DISCONNECTINDICATION

RELEASECOMPLETE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

Figure 6 (sheet 37 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)139

Process USER_SIDE 38(57)

USER SIDE SDL DIAGRAMS

15SUSPENDREQUEST

SUSPENDREJECT

STOPT319

SUSPENDCONFIRM(ERROR)

10

5.6.3SUSPENDACK

STOPT319

SUSPENDCONFIRM

RELEASEB-CHANNEL

RELEASECR

0

5.6.2+

Figure 6 (sheet 38 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)140

Process USER_SIDE 39(57)

USER SIDE SDL DIAGRAMS

15SUSPENDREQUEST

DISCONNECT

STOPT319

DISCONNECTINDICATION

12

5.3.4RELEASECOMPLETE

STOPT319

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

STOPT319

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

Figure 6 (sheet 39 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)141

Process USER_SIDE 40(57)

USER SIDE SDL DIAGRAMS

15SUSPENDREQUEST

NOTIFY

NOTIFYINDICATION

15

5.6.25.6.45.9 INFO

INFOINDICATION

15

5TIMEOUTT319

SUSPENDCONFIRM(TIMEOUTERROR)

10

5.6.3

Figure 6 (sheet 40 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)142

Process USER_SIDE 41(57)

USER SIDE SDL DIAGRAMS

17RESUMEREQUEST

RESUMEREJECT

STOPT318

RESUMECONFIRM(ERROR)

RELEASECR

0

5.6.5RESUMEACK

STOPT318

RESUMECONFIRM

CONNECTTO

B-CHANNEL

10

5.6.4+ TIMEOUT

T318

RESUMECONFIRM(TIMEOUT ERROR)

RELEASE(CAUSE #102)

STARTT308

19

5.3.2 (f)5.6.5

Figure 6 (sheet 41 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)143

Process USER_SIDE 42(57)

USER SIDE SDL DIAGRAMS

17RESUMEREQUEST

DISCONNECT

STOPT318

RELEASE

STARTT308

19

5.3.4RELEASECOMPLETE

STOPT318

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

STOPT318

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

Figure 6 (sheet 42 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)144

Process USER_SIDE 43(57)

USER SIDE SDL DIAGRAMS

19RELEASEREQUEST

DISCONNECT

19

5.3.6RELEASECOMPLETE

STOPT308

RELEASECONFIRM

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

5.3.4+ RELEASE

5.3.6

Figure 6 (sheet 43 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)145

Process USER_SIDE 44(57)

USER SIDE SDL DIAGRAMS

19RELEASEREQUEST

INFO

INFOINDICATION

19

5

STATUS

CS=0?

STATUSINDICATION(ERROR)

STOPT308

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

19

5.8.11

Y

N

Figure 6 (sheet 44 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)146

Process USER_SIDE 45(57)

USER SIDE SDL DIAGRAMS

NOTE 1. THIS MESSAGE IS IDENTICAL TO THE ORIGINAL RELEASE MESSAGE, EXCEPT THAT AN ADDITIONAL CAUSE #102 MAY BE ADDED.NOTE 2. THE OPTION OF PLACING THE B-CHANNEL IN THE MAINTENANCE CONDITION IS NOT APPLICABLE IN THE CASE OF POINT-TO-MULTIPOINT CONFIGURATIONS.

19RELEASEREQUEST

TIMEOUTT308

FIRSTTIMEOUT

?

TYPEOF

CONFIG.?

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECONFIRM

RELEASECR

0

RELEASEB-CHANNEL IFNOT RELEASED

PLACEB-CHANNEL IN AMAINTENANCE

CONDITION

NOTE 2

RELEASE

NOTE 1

STARTT308

19

5.3.5

N

P-MP

P-P

Y

Figure 6 (sheet 45 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)147

Process USER_SIDE 46(57)

USER SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A POINT-TO-POINT CONFIGURATION, CONNECTION TO THE B-CHANNEL MAY BE MADE AT THIS POINT.

25OVERLAPRECEIVING

PROCEEDINGREQUEST

STOPT302

IF RUNNING

CALLPROCEEDING

NOTE 1

9

5.2.3.1 (d)5.2.4+

SETUPRESPONSE

STOPT302

IF RUNNING

CONNECT

STARTT313

8

NOTE 1

5.2.3.1 (d)5.2.45.2.7+

ALERTINGREQUEST

STOPT302

IF RUNNING

ALERTING

NOTE 1

7

5.2.3.1 (d)5.2.4+

Figure 6 (sheet 46 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)148

Process USER_SIDE 47(57)

USER SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A POINT-TO-POINT CONFIGURATION, CONNECTION TO THE B-CHANNEL MAY BE MADE AT THIS POINT.

25OVERLAPRECEIVING

PROGRESSREQUEST

STOPT302

IF RUNNING

PROGRESS

NOTE 1

25

5.2.3.1 (d)5.2.6DISCONNECT

REQUEST(CAUSE)

STOPT302

IF RUNNING

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE)

STARTT305

11

5.2.45.3.3

Figure 6 (sheet 47 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)149

Process USER_SIDE 48(57)

USER SIDE SDL DIAGRAMS

25OVERLAPRECEING

INFO

5.2.4

INFOINDICATION

RESTARTT302

25

INFOREQUEST

INFO

25

5

Figure 6 (sheet 48 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)150

Process USER_SIDE 49(57)

USER SIDE SDL DIAGRAMS

25OVERLAPRECEIVING

RELEASECOMPLETE

STOPT302

IF RUNNING

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECR

0

5.8.4

RELEASE

STOPT302

IF RUNNING

RELEASEB-CHANNEL IFNOT RELEASED

RELEASEINDICATION

RELEASECOMPLETE

RELEASECR

0

5.8.4

DISCONNECT

STOPT302

IF RUNNING

DISCONNECTINDICATION

12

5.3.4

Figure 6 (sheet 49 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)151

Process USER_SIDE 50(57)

USER SIDE SDL DIAGRAMS

NOTE 1. IN THE CASE OF A POINT-TO-POINT CONFIGURATION, CONNECTION TO THE B-CHANNEL MAY BE MADE AT THIS POINT.

25OVERLAPRECEIVING

TIMEOUTT302

CALL INFOINCOMPLETE

?

DISCONNECTINDICATION

DISCONNECTB-CHANNEL

IF NECESSARY

DISCONNECT(CAUSE #28)

STARTT305

11

WHICHMESSAGE

?

CONNECT

NOTE 1

STARTT313

8

CALLPROCEEDING

NOTE 1

9

ALERTING

NOTE 1

7

5.2.3.1 (d)5.2.4

Y

N

CONNECTCALL PROCEEDING

ALERTING

Figure 6 (sheet 50 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)152

Process USER_SIDE 51(57)

USER SIDE SDL DIAGRAMS

NOTE 1. TIMER T304 IS OPTIONAL.

ANYSTATE

DL-ESTABLISHINDICATION

STATEU2,U25

?

SAMESTATE

U2?

STOPT304

NOTE 1

DISCONNECTINDICATION

RELEASEB-CHANNEL IFNOT RELEASED

DISCONNECT(CAUSE #41)

STARTT305

11

STOPT302

5.8.8

0NULL

DL-RELEASEINDICATION

5.8.9

0

ANY STATEEXCEPT

0, 10

DL-RELEASEINDICATION

RELEASEINDICATION

STOPANY TIMER

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

5.8.9

N

Y

Y

N

Figure 6 (sheet 51 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)153

Process USER_SIDE 52(57)

USER SIDE SDL DIAGRAMS

STATE10

TIMEOUTT309

RELEASEINDICATION

RELEASEB-CHANNEL

RELEASECR

0

5.8.9DL-ESTABLISHCONFIRM

STOPT309

IF RUNNING

REPORTSTATUS

(CAUSE #31)

10

5.8.9DL-RELEASEINDICATION

T309RUNNING

?

STOPT309

RELEASEB-CHANNEL

RELEASEINDICATION

RELEASECR

0

STARTT309

DL-ESTABLISHREQUEST

10

5.8.9

Y

N

Figure 6 (sheet 52 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)154

Process USER_SIDE 53(57)

USER SIDE SDL DIAGRAMS

NOTE 1. FURTHER ACTIONS ARE AN IMPLEMENTATION OPTION.

1

M=0?

STATUSINDICATION(ERROR)

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

0

COMPATIBLESTATE

?

SAMESTATENOTE 1

STATUSINDICATION(ERROR)

RELEASE(CAUSE #101)

STARTT308

19

ANY STATEEXCEPT

0, 19

STATUS(CS=M)

T322RUNNING

?

CAUSE#97 OR #98

?

SAVE CAUSEAND

CALL STATE

SAMESTATE

CAUSE#30

?

1

STOPT322

5.8.105.8.11

Y

N

Y

N

Y

Y

N

N

Y

N

Figure 6 (sheet 53 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)155

Process USER_SIDE 54(57)

USER SIDE SDL DIAGRAMS

NOTE 1. UNEXPECTED MESSAGE AND UNRECOGNIZED MESSAGE DO NOT INCLUDE RELEASE AND RELEASE COMPLETE.

ANY STATEEXCEPT

0

SETUP

SAMESTATE

5.8.3.2 (e)UNEXPECTEDMESSAGE

REPORTSTATUS

(CAUSE #97,#98 OR #101)

SAMESTATE

5.8.4,NOTE 1 UNRECOGNIZED

MESSAGE

5.8.4,NOTE 1

Figure 6 (sheet 54 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)156

Process USER_SIDE 55(57)

USER SIDE SDL DIAGRAMS

NOTE 1. THE RESTART PROCEDURE IS OPTIONAL IN A POINT-TO-MULTIPOINT CONFIGURATION.NOTE 2. THIS PRIMITIVE MAY BE RECEIVED FROM GLOBAL CALL REFERENCE CONTROL.NOTE 3. TIMER T322 MUST BE STOPPED IF ANY CLEARING MESSAGE IS RECEIVED BEFORE IT EXPIRES.NOTE 4. THIS PRIMITIVE IS SENT TO GLOBAL CALL REFERENCE CONTROL.

ANY STATEEXCEPT

0

STATUSENQUIRYREQUEST

T322RUNNING

?

SAMESTATE

STATUSENQUIRY

STARTT322

NOTE 3

5.8.10

ANYSTATE

STATUSENQUIRY

STATUS(CAUSE #30)

SAMESTATE

5.8.3.2(h)5.8.10

ANYSTATE

NOTE 1

RESTARTREQUEST

STOPANY TIMER

RELEASEINDICATION

RELEASEB-CHANNEL IFNOT RELEASED

RELEASECR

RESTARTCONFIRM

NOTE 4

0

5.5,NOTE 2

Y

N

Figure 6 (sheet 55 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)157

Process USER_SIDE 56(57)

USER SIDE SDL DIAGRAMS

NOTE 1. ACTIONS AFTER EXPIRY OF TIMER T322 WHEN A STATUS MESSAGE WITH CAUSE #97 OR #98 HAS BEEN RECEIVED ARE IMPLEMENTATION DEPENDENT.NOTE 2. TIMER T322 MUST BE STOPPED IF ANY CLEARING MESSAGE IS RECEIVED BEFORE IT EXPIRES.

ANY STATEEXCEPT

0

TIMEOUTT322

STATUSRCVD WITHCAUSE #97

OR #98?

?

NOTE 1MAX No.RETRANSMISSIONS

EXCEEDED?

STATUSENQUIRY

STARTT322

SAMESTATE

NOTE 2

RELEASE(CAUSE #41)

RELEASEINDICATION

STARTT308

19

5.8.10

Y

N

N

Y

Figure 6 (sheet 56 of 57): User side SDL diagram

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)158

Process USER_SIDE 57(57)

USER SIDE SDL DIAGRAMS

NOTE 1. TIMER T322 MUST BE STOPPED ON RECEIPT OF A CLEARING MESSAGE.

REPORTSTATUS(CAUSE)

STATUS(CAUSE)

T322RUNNING

?

STATUSENQUIRY

STARTT322

NOTE 1

Y

N

Figure 6 (sheet 57 of 57): User side SDL diagram

8.3 Restart SDL diagramsThis subclause shows detailed SDL diagrams for the global call reference to be applied to both user and network sides.Although these are drawn as user side only, the same diagrams can be applied to the network side by changing thedirection of the input and output symbols.

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)159

Process RESTART 1(7)

RESTART SDL DIAGRAMS

NOTE 1. ALL FLAGS CLEARED (REST RESP, REST ACK, T317 EXPIRED). ALL TIMERS STOPPED.NOTE 2. THIS PRIMITIVE IS SENT TO THE GLOBAL CALL REFERENCE CONTROL BLOCK, WHERE THESE PROCEDURES ARE TAKING PLACE.NOTE 3. THIS PRIMITIVE IS SENT TO Q.931 PROTOCOL CONTROL SPECIFIED CALL REFERENCES.

REST 0RESTART

NULL

STATUS

5.8.11

REST 0

UNEXPECTEDMESSAGE

STATUS(CAUSE #81)

REST 0

5.8.3.2 (f)

RESTART

5.5.2+

ANYINDICATED CHs.ALLOWED TO BE

RESTARTED?

STATUS(CAUSE #82)

REST 0

TRANSLATE INTOINDIVIDUAL CALLREFERRENCES

ANY CRASSOCIATED WITH

THE INDICATEDCH ?

RESTARTCONFIRM

NOTE 2

ALLINDICATEDCHANNELS

?

REST 2

RESTARTREQUEST

NOTE 3

T317RUNNING

?

STARTT317

NOTE 1

N

Y

N

N

Y

Y

Y

N

Figure 7 (sheet 1 of 7): Restart SDL diagrams

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)160

Process RESTART 2(7)

RESTART SDL DIAGRAMS

NOTE 1. THIS PRIMITIVE IS RECEIVED FROM SYSTEM MANAGEMENT.NOTE 2. THE IDENTITY OF THE CHANNELS TO BE RESTARTED IS INCLUDED.NOTE 3. THIS PRIMITIVE IS SENT TO THE GLOBAL CALL REFERENCE CONTROL BLOCK, WHERE THESE PROCEDURES ARE TAKING PLACE.NOTE 4. THIS PRIMITIVE IS SENT TO Q.931 PROTOCOL CONTROL SPECIFIED CALL REFERENCES.

REST 0RESTART

NULL

MANAGEMENTRESTARTREQUEST

N=0

RESTART

STARTT316

ANY CRASSOCIATED WITH

THE INDICATEDCH ?

RESTARTCONFIRMNOTE 3

ALLINDICATEDCHANNELS

?

REST 1

RESTARTREQUEST

T317RUNNING

?

STARTT317

NOTE 4

5.5.1+,NOTE 1,NOTE 2

N

N

Y

Y

Y

N

Figure 7 (sheet 2 of 7): Restart SDL diagrams

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)161

Process RESTART 3(7)

RESTART SDL DIAGRAMS

NOTE 1. ACTIONS ON RECEIPT OF A STATUS MESSAGE INDICATING A COMPATIBLE STATE ARE IMPLEMENTATION DEPENDENT.

REST 1RESTARTREQUEST

STATUS

COMPATIBLESTATE

?

STATUSMANAGEMENTINDICATION(ERROR)

REST 1

?

NOTE 1

5.8.11UNEXPECTEDMESSAGE

STATUS(CAUSE #81)

REST 1

5.8.3.2 (f)RESTARTACK

STOPT316

REST RESPON

?

T317 EXPIREDON

?

STORE CH. ID.RECEIVED IN THE

RESTART ACK

REST ACK ON

REST 1

ALLREQ. CH.

ACK?

INCLUDE THEID. OF THE NON-RESTARTED CH.

MANAGEMENTRESTARTCONFIRM

REST 0

INDICATE RESTARTSUCCESSFULLY

COMPLETED

5.5.1

N

Y

N

N

Y

N

Y

Y

Figure 7 (sheet 3 of 7): Restart SDL diagrams

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)162

Process RESTART 4(7)

RESTART SDL DIAGRAMS

REST 1RESTARTREQUEST

RESTARTCONFIRM

ALLRESPONSES

?

STORECH. ID.

REST 1

STOPT317

RESTACK ON

?

REST RESPON

REST 1

ALLREQ. CH.

ACK?

INCLUDE THEID. OF THE NON-RESTARTED CH.

MANAGEMENTRESTARTCONFIRM

REST 0

INDICATE RESTARTSUCCESSFULLY

COMPLETED

N

Y

N

Y

N

Y

Figure 7 (sheet 4 of 7): Restart SDL diagrams

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)163

Process RESTART 5(7)

RESTART SDL DIAGRAMS

NOTE 1. DEFAULT MAXIMUM VALUE OF N IS 2.

REST 1RESTARTREQUEST

TIMEOUTT316

N=N+1

N=2?

RESTART

STARTT316

REST 1

INDICATE THATRESTART HAS

FAILED

MANAGEMENTRESTARTCONFIRM

REST 0

NOTE 1

5.5.1TIMEOUTT317

5.5.1

RESTACK ON

?

ALLREQ. CH.

ACK?

INCLUDE THEID. OF THE NON-RESTARTED CH.

MANAGEMENTRESTARTCONFIRM

REST 0

INDICATE RESTARTSUCCESSFULLY

COMPLETED

T317 EXPIRED ON

REST 1

N

Y

Y

N

Y

N

Figure 7 (sheet 5 of 7): Restart SDL diagrams

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)164

Process RESTART 6(7)

RESTART SDL DIAGRAMS

REST 2RESTART

RESTARTCONFIRM

ALLREFERENCES

?

STORECH. ID.

REST 2

STOPT317

INCLUDE ID.OF RESTARTED

CHANNELS

RESTARTACK

REST 0

5.5.2TIMEOUTT317

TIMEOUTMANAGEMENTINDICATION

ANYCH.

RESTARTED?

REST 0INCLUDE ID.

OF RESTARTEDCHANNELS

RESTARTACK

REST 0

5.5.2

N

Y

N

Y

Figure 7 (sheet 6 of 7): Restart SDL diagrams

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)165

Process RESTART 7(7)

RESTART SDL DIAGRAMS

NOTE 1. ACTIONS ON RECEIPT OF A STATUS MESSAGE INDICATING A COMPATIBLE STATE ARE IMPLEMENTATION DEPENDENT.

REST 2RESTART

UNEXPECTEDMESSAGE

STATUS(CAUSE #81)

REST 2

5.8.3.2 (f)

STATUS

5.8.11

COMPATIBLESTATE

?

STATUSMANAGEMENTINDICATION(ERROR)

REST 2

?

NOTE 1

N

Y

Figure 7 (sheet 7 of 7): Restart SDL diagrams

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)166

Annex A (informative):Relevant differences to ETS 300 102-2

A.1 Structural changesThe following structural changes have been made:

a) the text part of the present document has been aligned with the PNE rules and, as such, an adequate scope hasbeen added; new clauses have also been created concerning normative references, definitions, symbols andabbreviations;

b) in subclause 5.4, some guidelines have been included explaining the basis on which the representation of SDLdiagrams related to the management of timers in point-to-point and point-to-multipoint configurations for thenetwork side of the interface is supported;

c) a new subclause 6.4 has been created explaining the representation method adopted for the user side SDLdiagrams;

d) a new clause 7 has been created entirely dedicated to the handling of the SDL diagrams applicable for the restartprocedure. It has been structured according to the same approach followed for the previous clauses related to thenetwork side and user side (states related to the restart procedure, block diagram, list of primitives exchangedwith system management and representation method). In this last subclause, some explanatory text is alsoprovided concerning the flags which are used in these SDL diagrams;

e) a new subclause 8.3 has been created in order to clearly separate the SDL diagrams related to the restartprocedure from those related to the user side. The restart procedure diagrams are applicable, as inETS 300 102-2, for both the network side and the user side of the interface;

f) the lists of internal primitives between call control and protocol control in either the network side and the userside, which are represented in table 3 of subclause 5.3 and in table 6 of subclause 6.3, have been updatedaccording to the new set of SDL diagrams. Some of them have been deleted because they are no longer used,while others related to the restart SDL diagrams have been added;

g) the SDL diagrams have been entirely redrafted using a software tool and, as such, there has been a generalrearrangement in the sequence of their appearance;

h) furthermore, and regarding the redraft of the SDL diagrams, the following targets have been tried to be achieved:

1) inclusion of all relevant cross-references to subclauses of ETS 300 403-1 [1] as a comment to all inputsymbols;

2) inclusion of cause values which might be contained in the relevant ETS 300 403-1 [1] messages in the outputsymbols sent to the interface environment by either the network or by the user side;

3) alignment of the user side SDL diagrams with those of the network side.

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)167

A.2 Technical changesThe following technical changes have been made:

a) throughout clause 8, the SDL diagrams have been aligned with the technical changes agreed forETS 300 403-1 [1]. As an exception to this, the new note 2 in subclause 5.5 of ETS 300 403-1 [1] concerning thepossible occurrence of collision of restart procedures initiated by either side of the interface has not beencovered, due to the complexity of the representation;

b) in the network side and in the user side SDL diagrams, the input symbols related to the primitives RELEASEREQUEST received from call control have been removed from all states, except N11 and U12, as there is nosupport in ETS 300 403-1 [1];

c) in the network side and in the user side SDL diagrams, a new subroutine REPORT STATUS has been createdwhich is invoked according to ETS 300 403-1 [1] subclause 5.8.4 whenever unexpected and unrecognizedmessages are received, and which allows the option of sending a STATUS ENQUIRY message or a STATUSmessage. As an exception to this principle, and as explained by an appropriate note in the diagrams, thissubroutine is not represented in the SDL diagrams which handle the reception of unexpected DISCONNECT,PROGRESS or INFO messages by the global process when an incoming call is being offered in states Callreceived (N7), Connect request (N8), Incoming call proceeding (N9) and Overlap receiving (N25), as it increasesthe complexity of the representation. In these cases, although not precluded for implementations, only thetransmission of the STATUS message is shown as the utilization of the status enquiry procedure does notprovide any useful additional information to the network;

d) on the network side, the SDL diagrams related to the management of timers both in the global process (statesCall received (N7), Connect request (N8), Incoming call proceeding (N9) and Overlap receiving (N25)) and inindividual processes (states Call received (7I), Connect request (8I), Incoming call proceeding (9I) and Overlapreceiving (25I)), when an incoming call is being offered, have been rearranged according to the principlesdefined in subclause 5.4;

e) on the network side, also as a consequence of the principle defined in subclause 5.4 related to the handling oftimer T322 only in individual processes when an incoming call is being offered, a single diagram has beencreated valid for all the relevant states;

f) on the network side, the input symbols STATUS and OTHER MESSAGES which were applicable for theindividual processes have been deleted from the correspondent states, and have been replaced by two newdiagrams valid for all states;

g) on the network side, a new diagram representing the handling of the expiry of timer T301 in state Call received(N7) has replaced the existing one. This new diagram is similar to the one which already represented thehandling of the expiry of timer T310 in state Incoming call proceeding (N9), as it is supported bysubclause 5.2.5.4 of ETS 300 403-1 [1];

h) on the user side, all references to timers T301 and T310 have been deleted due to the removal of annex D fromETS 300 403-1 [1].

ETSI

ETSI EN 300 403-2 V1.3.1 (2000-11)168

History

Document history

Edition 1 November 1995 Publication as ETS 300 403-2

V1.3.1 December 1999 Public Enquiry PE 200016: 1999-12-22 to 2000-04-21

V1.3.1 August 2000 Vote V 20001027: 2000-08-28 to 2000-10-27

V1.3.1 November 2000 Publication